SOFTWARE MANUAL C32
8.3 EXAMPLE
Example: Answer to requesting the parameter value 18,10, Value = 2000
[
A
R
:
0x0000002C
#[
0x004CE0C7
ms
0x001D0000
:(FIRM): 18,10: 2000
#i__]#
0x9624A77E
:
A
R
]
Message start and end identifier
The first and the last character of a message are the opening and closing brackets.
Original identifier
The second character of a message indicates the origin of the message.
•
"A" or "a"
application
•
"B" or "b"
bootloader
In order to recognize missing messages, the original identifier comes with alternating capital letters and small letters.
Bootloader and application send their first message with capital letter as original identifier.
Type classification
The third character of a message is meant to identify the kind of message. Capital letters inform you that the use data
contain printable ASCII characters only. Small letters mean there is no such limitation.
•
"I" or "i"
information (e.g. spontaneous status message)
•
"C" or "c"
cyclic message
•
"R" or "r"
response message
•
"P" or "p"
protocol or syntax error
Printer operation status #i_
(see system status)
indicates general system status
# divider
e most serious system status.. "i" = information, "w" = warning, "e" = error
2. status level
(not yet implemented, to be replaced by _ )
+ further lower levels are planned
(not yet implemented, to be replaced by _ )
Length specification
and
CRC
The length specification relates to mere use data (without general system status and without Modulo 4 fill-in-bytes). The
CRC relates to the complete use data range between start and end identifier of the data. Like all other embedded use data
they are always output as 32 bit values ASCII Hex Coding format 0x12345678. This is also true for messages containing
binary data.
Use data start and end identifiers
Hash key and brackets "#["bzw."]#" enclose the data. This makes them easily visible for the user and they start at a fixed
offset divisible by 4 (important for the CRC) within the message.
Use data
Use data begin with a 32 bit time stamp followed by a distinct 32 bit message ID plus a ":". If the use data do not solely
consist of printable ASCII characters, timestamp and message ID are output as Little Endian Unsigned Integers. Otherwise
the timestamp is output as ASCII Hex Coding format 0x12345678ms and the ID is output as ASCII Hex Coding format
0x12345678. Depending on the message ID further data may follow.
To form a 32 bit CRC the use data must be 4 byte aligned. If necessary the data are completed with fill in bytes (in case of
ASCII Hex Coding these are spaces).
The use data length is not fixed and can be customized at any time!
Therefore it is absolutely necessary to evaluate the indicated length.
GeBE Elektronik und
phone
+49.89.894141-0
GeBE-document-no. SoMAN-C32-E-V2.2-0793
Feinwerktechnik GmbH
fax
+49.89.894141-33
date
July 7, 2020
Beethovenstraße 15
page 40 | 166
82110 Germering
Our general terms of business are to be applied.
Germany
Internet
www.gebe.net
Errors and changes reserved.
