You are here: Overview > Client Implementations

Client Implementations

Multiple clients can connect to the Automation Server. Once a connection is established with the server, the client communicates with the server using delimited ASCII strings. The delimiting token is the ‘;’ character. The ASCII strings are formatted as follows:

<COMMAND>;<PARAM 1>;<PARAM 2>;<PARAM X>

An example of a complex command requiring a named, value pair parameter format is the HTML Export command.

HTML Export;Summary=0;Data Bytes=1;File=htmlexport1.htm

The <PARAM> is sometimes a named, value pair of the format:

<PARAM NAME>=<PARAM VALUE>

Some simpler commands only have one parameter that is either on or off. These commands do not require naming. An example of this is the SYNC STATUS command.

Sync Status;ON

An optional parameter exists that one can use in cases with multiple data sources, (e.g. Wi-Fi Coexistence), to identify the desired data source. This parameter applies to the commands Config Settings, Start Sniffing, and Stop Sniffing.

<COMMAND>;<DATASOURCE>;<PARAM 1>;<PARAM 2>;<PARAM 3>

Config Settings; Datasource=0;IOParameters;Channel=3

Config Settings; Datasource=1;IOParameters;EncryptionSelection=5

When the data source parameter is missing, the value is 0.

The valid commands accepted by the server are discussed in detail in "Commands".