BSA Flow Software Installation and User's Guide - CSI

Examples
Typically the RS232 communication is event driven. Whenever data is
arriving to the port the OS is informed. The controller software can be
notified using events or messages depending on the architecture chosen. The
protocol is designed so that the & character can be used as end character in
the incoming data flow.
It is important that the controller answers the commands send from the driver
using the right protocol. If the driver cannot understand the incoming answer
it fails (see error code 1-5).
If the controller needs to make time consuming operations, it must answer
the incoming command before stating this. In this case the controller can
choose to ignore incoming commands by answering them quickly.
Example 1
The user needs to change settings in his program every time the traverse is
used, in this example max. speed set to 100 and a calibration constant to 333.
He can use the initialisation string to set the settings from time to time, saved
in the project.
SendToSerialPort( "#INIT:SPEED100,CALIB333&" )
IF ( ReceivedFromSerialPort() == "#INIT:0&" ) -> OK
Example 2
When the application wants to move to a position the co-ordinates are scaled
from mm, used in the application, to µm used in traverse communication.
x = 2.34594, y = 0.145, z = 2.5 (mm)
SendToSerialPort( "#MOVE:2346,145,2500&" )
IF ( ReceivedFromSerialPort() == "#MOVE:0&" ) -> OK
We loose precision on the x co-ordinate, but it has no relevance.
Example 3
Reading the position can be done by calling
SendToSerialPort( "#READ&" )
6.5.2 Use of External Traverse files
IF ( ReceivedFromSerialPort() == "#READ:0&" ) -> OK
Other errors e>100 can be found by examining the return string.
The External Traverse file can be enabled in the Region(s) menu in the
region list.
6-74 BSA Flow Software: Options and Add-ons