Aim-TTi products are using TCP port 9221.

Use command: edcmde-i386 /aimtti /ip 192.168.1.21 /cmd V1o?;I2o?;V2o?;I2o?;V3o?;I3o?; to read actual voltage and current from all outputs. Connection is to IP address 192.168.1.21, port 9221.

MX TP Command Format

Commands must be sent as specified in the commands list and must be terminated with the command terminator code 0AH (Line Feed, LF) except for commands over the TCP socket where the terminator is allowed but not required. Commands may be sent in groups with individual commands separated from each other by the code 3BH (;). The group must be terminated with command terminator 0AH (Line Feed, LF).

Responses from the instrument to the controller are sent as specified in the commands list. Each response is terminated by a which is 0DH (Carriage Return, CR) followed by 0AH (Line Feed, LF).

is defined as character codes 00H to 20H and is ignored except in command identifiers. e.g. ‘*C LS’ is not equivalent to ‘*CLS’.

The high bit of all characters is ignored. The commands are case insensitive

Error and Status Reporting

A separate error and status model is maintained for each interface instance; an interface instance is defined as a potential connection. USB, RS232 and GPIB are inherently single connections so represent one interface instance each. LAN, however, allows for multiple simultaneous connections so represents multiple interface instances. Two interface instances are allocated to the two TCP socket interfaces and one more is allocated to the Web page interface. Having a separate model for each interface instance ensures that data does not get lost as many commands e.g. ‘*ESR?’ clear the contents on read.

Error status is maintained using a set of registers as shown below.

Event Status Register "ESR" and Event Status Enable Register "ESE"

The Event Status Register is read and cleared by the ‘*ESR?’ command.

It is a bit field where each bit has the following significance.

Limit Event Status Registers ‘LSR?’ and Limit Event Enable Status ‘LSE’

There are two Limit Event Status Registers; These are read and cleared using ‘LSR1?’ and ‘LSR2’ respectively. On power up these registers are set to 0 then immediately set to show new limit status.

Execution Error Register ‘EER?’

This register contains a number representing the last error encountered over the current interface. The Execution Error register is read and cleared using the ‘EER?’ command. On power up this register is set to 0 for all interface instances.

Error messages defined to date are.

Parallel Poll Enable Register ‘*PRE, *PRE?’

This register is of limited use when the interface being used is not GPIB.

This register controls which bits of the Status byte register form the ist local message: If the result of bitwise ANDing The Status Bye Register with this register is zero then the value of ist is 0 otherwise it is 1.

Interface Locking

All interfaces are live at all times; this removes the need to select the active interface and is also a LXI requirement. To reduce the risk of the instrument being inadvertently under the control of two interfaces at once a simple lock and release mechanism is provided in the instruction set. The lock is automatically released where it is possible to detect disconnection and when the local button is pressed. Access to the interfaces may also be limited using the web page.

Any interface may request to have exclusive control of the interface by sending a ‘IFLOCK’ command. The lock may only be released by the interface instance that has the lock by sending an ‘IFUNLOCK’ command and may be queried by sending a ‘IFLOCK?’ command. The reply for any of these commands will be ‘-1’ if the lock is owned by another interface instance, ‘0’ if the interface is free and ‘1’ if the lock is owned by the requesting interface instance. Sending any command that changes the instrument status will set bits 4 and 6 of the Event Status Register and put 200 into the Execution Error Register to indicate that you do not have sufficient privileges for the required action.

Note: it is also possible to configure the maximum privileges for a particular interface to either ‘read only’ or ‘no access’ from the Web page interface.

Operating Modes

There are 6 operating modes defined for the unit as listed in the following table. Of which 4 may be selected under digital remote control.

The operating mode can be queried using the ‘CONFIG?’ and set using the ‘CONFIG’ commands

Note: Entry to modes 3 and 4 is only possible if both ontputs are switched off. On entry output 2 voltage range, voltage set point, current setpoint, OVP limit and OCP limit will be set to match the settings for output 1.

Commands

Nomenclature

This section lists commands and queries implemented in this instrument. The commands are listed in alphabetical order within the function groups.

There are no dependent parameters, coupled parameters, overlapping commands, expression program data elements or compound command program headers; each command is completely executed before the next command is started.

All commands that send a reply are terminated with the remote message terminator (ASCII 0DH, 0AH carriage return, line feed).

Parameter Ranges

All voltages are in volts and all currents are in amps. For ‘RATIO’ the figure is in percent

The maximum output voltage that can be requested is either 60V volts or 80V depending on the range selected; The minimum is 0V. The limits however may change when operationg in linked mode as for example if outputs are linked with V2 set to 200% of V1 then the allowable range for V1 is now 0 to 30 in low range as otherwise V2 would be set to an illegal value.

When operating in link mode the ratio between the two outputs can be 5% to 2000%.Changing the ratio changes V2. However, this is simlarly limited depending on what V1 is set to. If for example V1 were set to 10V and V2 is operating in the low range 60V. The range for ratio becomes 5 to 600 as otherwise V2 would be set to an illegal value.

The maximum output current that can be requested is either 50A; the minimum is 0.01A

The Commands

Common System and Status Commands

Instrument Specific Commands

Komunikácia so zdrojom MX100TP.