Command Sequence Formatting And Protocol; Confirmation Command Echo; Command Completion Indicator - Sutter Instrument LAMBDA 10-B Operation Manual

70

7.8 Command Sequence Formatting and Protocol:

Each command sequence consists of at least one byte, the first of which is the "command
byte". Those commands that have parameters or arguments require a sequence of bytes that
follow the command byte. No delimiters are used between command sequence arguments,
and command sequence terminators are not used. Although most command bytes can be
expressed as ASCII displayable/printable characters, the rest of a command sequence must
generally be expressed as a sequence of unsigned byte values (0-255 decimal; 00 – FF
hexadecimal, or 00000000 – 11111111 binary). Each byte in a command sequence
transmitted to the controller must contain an unsigned binary value. Attempting to code
command sequences as "strings" is not advisable. Any command data returned by the
controller should be initially treated as a sequence of unsigned byte values upon reception.

7.8.1 Confirmation Command Echo

When the host computer sends a command, each byte received is immediately echoed back to
the host computer. This echoing back of each sent byte is a confirmation that the byte has
been received and will be acted upon shortly. A short period after the last byte of a command
has been echoed back, the device sends a confirmation byte (described next) that indicates
the operation associated with the command completed.

7.8.2 Command Completion Indicator

When this device completes the operation associated with the command it has just received,
it transmits back to the host computer a byte value of 13 decimal (0D hexadecimal, 00001101
binary). This byte value corresponds to an ASCII carriage return (often abbreviated as
"CR").
LAMBDA 10-B OPERATION MANUAL – REV. 1.20Q (20230227)