Doc. Title
Author
Page of Pages
ST310U OPERATION MANUAL
JH KIM
9 of 66
Concerning
Doc. No.
Rev.
Date
Features and How to set parameters
1.08
2017/7/13
Suntech International Ltd.
Confidential Document
3. Communication string format
All the communication messages exchanged between device and its server should be in the form of STRING as
described below. Each
‘Report’ can be compressed in ZIP. Every ‘Filed’ is separated with semicolon. All the report
string triggered by device ends with a mark,
‘
＼
r’ (0x0d).
3-1. Command format
The following format is used when the server sends command message to the device(s) as shown in the below
table. The
“Value”(or Indicating Mark) and its “Meaning” are described individually.
The parts consisting of
‘Fields’ are capitalized for naming like:
“HDR” stands for the header, ‘DEV_ID’ for device’ identification number, “VER” for version, Field 1, Field 2, etc.
HDR DEV_ID VER Field 1 Field 2
… Field n
Field
Value (or Mark)
Meaning
HDR
String
“
ST300
” + Command type
DEV_ID
9 char.
Device ID
VER
“02”
Protocol Version. This is fixed with
“02”.
Field 1 ~ n
String
Contents
The
‘Device ID’ is a unique number that each device should have. It is equal to the last 9 digits of IMEI numbers
shown on the back label of the device. Whenever the server sends a command message, it designates a specific
device along with the unique identification number of the device as a command receiver. And then, the device
recognizes a fact that it has received the command message and responds to the server with a relevant response
or a relevant action to be taken. This is how a normal communication is made between the server and its device.
On the other hand, sometimes, a very bad GPRS connection between a device and the server may consequently
bring about a bad result that the specified command message would be delivered NOT to the targeted device BUT
to other device. In such a situation, the wrong device does not accept the command message because the device
ID number of the message does not match the ID number of the wrong device.
However, we might consider a situation in which a command message is delivered to a device via RS232. In such
a situation the device accepts the command message even though the device ID number of that command
message is NOT its own one.
3-2. Report format
The contents of the following table show what messages and how they are delivered to the server in response to
the command that the server has sent to the device(s) by requesting the device(s) to respond with.
HDR DEV_ID SW_VER Field 1 Field 2
… Field n
Field
Value (or Mark)
Meaning
HDR
String
“
ST300
” + Report type
DEV_ID
9 char
.
Device ID
SW_VER
“001”
Software version that the device has.
Field 1 ~ n
String
Contents
