tecan cavro xlp 6000 Operating Manual page 46

3 - Software Communication
Communication Protocols
3 - 14
6 Report current valve position
10 Report buffer status
13 Report status of input #1
14 Report status of input #2
15 Report the number of pump initializations
16 Report the number of plunger movements
17 Report the number of valve movements
18 Report the number of valve movements since last report
20 Report checksum
23 Report firmware version
24 Report zero gap increments
29 Report current status
When the pump responds to a query, the first two bytes of the data block are the
status bytes. The first byte contains an error code (same error codes used with
the RS-232 and RS-485 protocols) added to Ox20h. The second byte contains the
value Ox60h and is not used. The remaining six bytes are for the response in
ASCII. If the pump is only reporting current status, the message is only two bytes
long. If the reply consists of more than six bytes, multi-frame messages are used.
CAN Data Block
The data block tells the pump what to do. Pump commands are sent in ASCII just
like in RS-232 or RS-485. For command strings that are more than eight bytes in
length, multi-frame messages are used. This permits long program strings to be
sent as with the other communications interfaces (remember that the XLP 6000
buffer size is 255 characters).
Handling of Pump Boot Requests
When the pump is first powered up or receives a system reset command (frame
type 2, command 0), the pump notifies the host of this condition by sending a boot
request message at 100 millisecond intervals until it receives a proper response.
The group number is 1 for the boot request message. The frame type is 2 when
the pump sends messages to the host, and the frame type must be 0 when the
host replies to the boot request.
Cavro® XLP 6000 Modular Syringe Pump Operating Manual, 734237-C, en