Make/Model  Device VersionConnection Type
CQS/GirderN/ASerial

Description:

This driver allows you to control the Girder program from CQC. Girder allows you to control programs on your computer easily, which many people want to do if they are using the computer itself as a device instead of, or in addition to, being a controller. Girder provides a simple, one way, TCP/IP based protocol for external control from other applications. This driver uses that interface. You must have at least Girder version 3.2.

This driver's server side component is CML based. The server driver classes for this device are in the MEng.System.CQC.Drivers.Girder scope. This driver was provided by Ken Lidster.

There is some setup required on the Girder side before you install this driver on the CQC side. CQC uses the Internet Event Server facility of Girder, which you must configure to accept commands. This is described in detail in the file 'help\ievent_readme.txt' within the Girder installation directory, but here is a brief overview of the steps involved.

Note the password and port that you entered, since you will use these in the CQC Girder driver installation. When you install the driver, you will be prompted for these values. You will be given a change to set the target IP address, in which case you will chose the address of the machine on which Girder is running, and the port number which you set above. You will also be prompted for the password.

Quirks and Limitations:

None at this time.

Connection Details

The Girder connection is a TCP/IP socket based connection. When you install the driver, you will be given a chance to set the TCP/IP settings. You will need to set the address of the target machine where Girder is running. You can use the host name, which is optimal since it won't be affected by address changes, but you can also provide the numeric address if the target machine has a fixed address.

You will also need to set the port number to whatever port you configured Girder to listen on for Internet Events.

Driver Fields

This section lists the fields that the driver makes available, their types, minimum and maximum values, etc...

NameTypeR/WDescription/Limits
CommandStringWThis is the only field available. Since the Girder interface is one way, you can only send it commands, and you do so by writing to this field. The format details are discussed below.

The format of the strings you send to the Command field are in the following format:

event [param1 param2 ... param9]

So there is an event name, followed by up to nine optional payload values and whose values depend on the requirements of the event you are sending. Each time you write to the Command field, Girder event is created with eventnam being the name of the event, the CQC machine's IP address automatically in the first payload field (pld1 - see the Girder documentation), and any parameters specified loaded into the remaining payload fields (pld2 through pld10.)

Each of the values in the string, i.e. the event and each payload, must be a either a string of non-whitespace characters, or a quoted string if they have any spaces, such as:

FooBarEvent Param1 "Param 2" "the 3rd Param"

Creates an event within Girder with the event name "FooBarEvent", the CQC server's IP address in pld1, "Param1" in pld2, "Param 2" in pld3, and "The third Param" in pld4.