Agilent 1100 Series Autosampler G1367A Labview Control

[Jdavidson559]

The lab I am working with is attempting to control an Agilent 1100 series G1367A autosampler entirely with LabView. We are communicating with the instrument via an Agilent G1369C lan interface network card. We have attempted to use the ag1100 driver hosted by NI; however, we are having a terrible time communicating with it after the TCP/IP VISA resource is set up.

In any event, we are now trying to develop our own LabView driver for communication, but we are finding that the firmware commands that this specific agilent machine uses are not tradition SCPI commands or anything of the sort. I cannot find any documentation on these commands or the language they are using. Does anyone have any insight as to how we may be able to control this instrument??? Say with ICF or I/O libraries. Thank you and any help will be appreciated.

P.S. The closest post I could find related to this issue is viewtopic.php?t=24303.

[antonk]

Install the Chemstation and run Wireshark, play with sequence and watch what CS uploads to LC.

report here

[Jdavidson559]

I captured these packets about a week ago attempting to see the commands; however, since I am specifically interested in syntax (particularly End-of-line characters which seem to be a big problem with other Agilent instruments), I didn't see too great of a use for them. The two packets "record" the communications from a sequence of MOVE commands and then VLVE commands (which is valve up/down). It seems that each command is finished with the following string being sent to the instrument: MONA:NVM?.

Thanks again for all of your help and please do let me know if more info is needed.

MOVE: https://drive.google.com/open?id=0B_16rpVQ0xVlQmpHN1JDODV3NHM
VLVE: https://drive.google.com/open?id=0B_16rpVQ0xVlQkQ0YU9tdElwOUU

[antonk]

Thank you for filling my collection of 1100 logs (hope it help me finish someday 1100 cross-platform driver)

MONA - probably monitoring file A
:NDLE? - query needle status

In wireshark - follow TCP stream and view it as HEX.

You will see - every packet prefixed with the word length in big-endian and word destination address (all 1100 devices are actually CAN nodes).

Then it can be considered as normal conversation - slightly asynchronous (response does not come immediately but can be identified by repeated query) and mixed with ES (external states)

Q: VLVE 2,0,1
A: RA 0000 VLVE 2,0.0,3

Q: MONA:NMV?
A: RA 0000 MONA:NMV 10002,707,2

I would be very grateful if you document your sampler discoveries and share with me to unichrom at unichrom dot com