Advanced Wireless Solutions EMO-500 ユーザーズマニュアル
AW Company 8809 Industrial Drive, Franksville, WI 53126 à web: www.awcompany.com
Tel: 262-884-9800 Fax: 262-884-9810 | Email: aw@awcompany.com
REV. 4 10/05 EMO-500 Manual.DOC
27
The answer received back from the EMO 500 will look like this:
A03E36712XXcr
^...............all answers start with A
^^............low byte (at address 0F34)
^^..........next byte(at address 0F35)
^^........next byte(at address 0F36)
^^......high byte(at address 0F37)
^^....checksum
......carriage return ends the string
A03E36712XXcr
^...............all answers start with A
^^............low byte (at address 0F34)
^^..........next byte(at address 0F35)
^^........next byte(at address 0F36)
^^......high byte(at address 0F37)
^^....checksum
......carriage return ends the string
The protocol format for writing to the EMO 500 is as follows:
>01J03340F3587XXcr
^.....................start of string must use the > sign
^^..................unit number
^..................write command J (use K to read)
^^^^...........address to write into
^^...........byte written to 0334
^^.........byte written to 0335
^^.......byte written to 0336
^^.....checksum
.....carriage return
If the operation was successful the EMO 500 answers with: Acr.
The following error messages have been implemented in the EMO 500 protocol.
NO1cr - Undefined command (something other than K/J)
NO2cr - Checksum error
NO3cr - Non printable ASCII character
There is a booklet published by OPTO 22 on the protocol format.
>01J03340F3587XXcr
^.....................start of string must use the > sign
^^..................unit number
^..................write command J (use K to read)
^^^^...........address to write into
^^...........byte written to 0334
^^.........byte written to 0335
^^.......byte written to 0336
^^.....checksum
.....carriage return
If the operation was successful the EMO 500 answers with: Acr.
The following error messages have been implemented in the EMO 500 protocol.
NO1cr - Undefined command (something other than K/J)
NO2cr - Checksum error
NO3cr - Non printable ASCII character
There is a booklet published by OPTO 22 on the protocol format.
Checksum Calculation
The calculation for the string variables in the read command would be as follows:
>01K0F3404XXcr
^^^^^^^^^.......these characters are used in the calculation.
Add the values for the ASCII Decimal variables.
HEX 0 + 1 + K + 0 + F + 3 + 4 + 0 + 4
ASCII 48 + 49 + 75 + 48 + 70 + 51 + 52 + 48 + 52 = 493
>01K0F3404XXcr
^^^^^^^^^.......these characters are used in the calculation.
Add the values for the ASCII Decimal variables.
HEX 0 + 1 + K + 0 + F + 3 + 4 + 0 + 4
ASCII 48 + 49 + 75 + 48 + 70 + 51 + 52 + 48 + 52 = 493