Requirements:

  1. PC
  2. Aerotech Software (A3200, Ensemble, Soloist)
  3. “External” third-party client program (ex. PuTTY)

Refer to the ASCII Command Interface page in the Help File for more information on the ASCII Command Interface options and setup.

A3200 Example

The ASCII command interface is not enabled by default. To enable the interface:

  1. Open A3200 Configuration Manager
  2. Under System > Communication > ASCII in the parameter file, find the CommandSetup and CommandPort parameters.
  3. Check the Enabled box in the Editor for the CommandSetup parameter.
  4. Use the CommandPort parameter to set the TCP/IP port that A3200 will use to listen for incoming client connections. The default is 8000.

NOTE: You must reset the controller for these changes to have an effect.

From PuTTY (as an example client):

  1. Enter Host Name (ex. “Localhost”)
  2. Set Connection Type = Raw
  3. Enter Port. Port value must match the CommandPort parameter
  4. Click Open to open the port connection


Ensemble/Soloist Example

The ASCII command interface is not enabled by default. To enable the interface, use the following procedure.

  1. In Configuration Manager, right-click on the connected controller and select Retrieve Parameters.
  2. Expand the controller tree to Parameters > System > Communication > ASCII and find the CommandSetup parameter.
  3. In the ASCII Command Active Port section of the Editor pane, select one or more of the communication interfaces that you want to use for the ASCII command interpreter.
    1. For example, RS232 or Ethernet Sockets

  4. For each interface selected above, use the parameters that correspond to that interface under the Parameters > System > Communication tree to configure communication.
    (ex. Use the parameters under Ethernet Sockets (Socket2Port, Socket3Setup, etc.) to configure communication if an Ethernet Socket was enabled in the CommandSetup parameter).

    • It is recommended to configure them to be a server instead of a client on the Ensemble/Soloist (this applies to the Socket2Setup and Socket3Setup parameters)

    • It is recommended to use TCP/IP instead of UDP/IP. Data loss in UDP sockets can occur with UDP/IP. If you must use a UDP socket, decrease the risk of losing data by using a cross-over cable between the devices (recommended) or by using a closed network such as a hub or switch with only the client and server devices connected.

    • The IP address for the TCP/IP connection uses the IP address that is set under Controller > Connection Settings in Configuration Manager.


NOTE: You must reset the controller for these changes to have an effect.


From PuTTY (as an example client):

  1. Enter Host Name (ex. The IP address of the controller, located under Controller > Connection Settings in Configuration Manager)
  2. Set Connection Type = Raw
  3. Enter Port. Port value must match the corresponding parameter based on the interface chosen (ex. Socket2Port, Socket3Port)
  4. Click Open to open the port connection