User's Manual

http://www.microcyber.cn
22
Table 4-4 Own Protocol Format
Control
Byte
Node ID Device
Status
Extended
Device Status
Command
ID
Number
of Byte
Payload CRC
Parity
1Byte 8Byte 1Byte 1Byte 2Byte 1Byte N Byte 2Byte
Among them:
Control byte: 1 byte
bit0 -- 0: Response 1: Request
bit1 -- 0: Unicast 1: Broadcast
bit2~bit7 : Default value is 0.
Node ID: Device long address, 8-byte hexadecimal numbers.
Device status: 1 byte, please refer to details in Table 4-2.
Extended device status: 1 byte, please refer to details in HCF_SPEC_183.
Command ID: 2-bytes ,Command number.
Payload: Data packets corresponding to the command ID.
CRC parity: 2 bytes, CRC parity code for control byte to load.
Master device or client-side may use TCP/IP interface way, to receive field device report
information via private protocol format.
Example:
Example of data frame with node ID 00-1B-1E-2A-01-6A-E0-69 :
4.4.2 Downward Communication Protocol
Downward communication protocol can let user send read-write command to field device via
TCP/IP interface mode of master device or client-side, convenient for user to flexibly operate field
device with wireless mode via gateway. Port number of downward communication protocol is 8881.
Transmit command format: Use "," to separate transmit data, device address is aggregated into
character string.
Request Data
Name Length Description
Device Address 1 Address of communication device
When short address communicates, address is "0", only