Banner iVu Plus BCR, User Manual

Page: 85 / 155

For example, the following is a series of command requests and responses. The first request sets the trigger mode to command and,
once the sensor responds with an "OK," the next command request is issued to do (or execute) the trigger.
>> set trigger mode command \x0D\x0A
<< OK\x0D\x0A
>> do trigger \x0D\x0A
<< OK\x0D\x0A
8.1.2 String Delimiters and Escaping
By default setting, all strings used in commands are enclosed in quotation marks (""). All text in quotes is part of the command. Quotes (")
or back-slashes (\) that are part of the string must be escapted with a back-slash. For example:
"abc\"def\"ghi\\jkl"
Set the String Delimiter parameters to 'None' if strings should not be enclosed in quotation marks.
8.1.3 Command Channel Command Synopsis
There are a number of general types of commands to do, set, and get sensor data.
Command Channel Response Frames
The iVu responds to all request frames with one or two responses depending on the type of command.
Do commands
All do commands are followed by one response that identifies the command status. For example:
>> do trigger \x0D\x0A
<< OK\x0D\x0A
Get commands
All get commands are followed by two responses: the first identifies the status of the command, and the second con-
tains the retrieved information. For example:
>> get bcr_input comparedata \x0D\x0A
<< OK\x0D\x0A
<< "012345ABCDEF"\x0D\x0A
Set commands
All set commands are followed by one response that identifies the command status. For example:
>> set bcr_input comparedata "012345ABCDEF" \x0D\x0A
<< OK\x0D\x0A
iVu Plus BCR User's Manual
Rev. B www.bannerengineering.com - tel: 763-544-3164 85