Robustel GoRugged M1000 Pro User Guide
RT_M1000 Pro_UG_v01.01
27.12.2011
58 / 59
Confidential
5.5
Robustel DI and DO over TCP Protocol
DI over TCP and DO over TCP are using private protocol.
User can easily integrate Robustel DI and DO over TCP Protocol into their SCADA or system.
Data format:
Start Device Name
Data Type
Time Stamp I/O Channel
Data
End
Part 1 Part 2
$
8 bytes
2 byte 2 byte
12 bytes
2 bytes
N bytes
#
Start
: 1 byte starts with $
End
: 1 byte ends with #
Device Name
: 8 bytes, such as 00000001, indicates ”Device Name” from GatewayConfigurator (maximum 8
characters)
Part 1
: Can be “DI” or “DO”
Part 2
: Can be “00” and “01”, 00=Single DI/DO channel, 01=Multi DI/DO channel from the 1
st
channel (M1000 just
has 1 DI and 1 DO)
Time Stamp
: 12 bytes, format is yyMMddHHmmSS, such as 111028174532=28
th
Oct. 2011, 17:45:32
I/O Channel
: When Part 2=00, indicates the specify DI/DO channel, such as 00=1
st
DI/DO, 01=2
nd
DI/DO; When Part
2=01, indicates continuous multi DI/DO channel, such as 01=1
st
DI/DO, 02=1
st
to 2
nd
DI/DO, 03=1
st
to 3
rd
DI/DO
Data
: Each DI or DO occupies one byte. When Part 1=DI, it can be 0 or 1, 0=recovering alarm, 1=triggering alarm;
When Part 1=DO, it can be 0, 1 or 2, 0=recovering alarm, 1=triggering alarm, 2=output pulse.
For example:
Start
Device
Name
Data Type
Time
Stamp
I/O
Chann
el
Data
End
$
10000001 D O 0 1
11-06-18
17:28:48
0
2
21
#
Data: $
10000001
DO01
110618172848
02
21
#
$: Start byte
10000001: Device Name
DO01: multi-channel DO
110618172848: time is 18
th
Jun. 2011, 17:28:48
02: 2 continuous DO from the first channel
21: DO_0=output pulse, DO_1=recovering alarm
#: End byte
