Download xOEMcore User Manual

xOEMcore User Manual
For example Table 11 shows some sequences of packets and whether they work or not.
Table 11. CCOM_TYP_COMMAND packet sub-types
Packets (hexadecimal)
Payload in
ASCII
Effect
40 00 18 95 10 00 01 02 0A 21 72 65 73 65 74 0A
\n!reset\n
Accepted "!reset"
40 00 35 7B 0D 00 01 02 0A 21 72 65 73
40 00 A6 04 13 00 01 02 65 74 0D
\n!res
et\r
None
Accepted "!reset"
40 00 AE FC 13 00 01 02 0A 31 32 33 21 72 65 73 65 74 0A
\n123!reset\n
Accepted "!reset"
40 00 C2 EB 10 00 01 02 0A 21 72 65
40 00 0E 9C 13 00 01 02 21 72 65 73 65 74 0A
\n!re
!reset\n
None
Rejected "!re!reset"
If NCOM or MCOM is being output then the interpretation of the command messages
by the xOEMcore can be seen in the status message fields "command characters
received", "command characters skipped", "command packets received" and "command
packet errors".
CCOM_TYP_CONFIG
The CCOM_TYP_CONFIG packet type is used to send and manage the NAV
configuration files that configure the xOEMcore. Historically all the OxTS products
were configured using a set of files, which were generated by NAVconfig. This scheme
has been carried forward to the xOEMcore. Since the xOEMcore does not have a file
system, the NAV configuration files must be stored (or created) by the external
application and sent to the xOEMcore after it boots. NAV configuration files can only
be sent at start-up.
Within the CCOM_TYP_CONFIG packet type there are several sub-types, which are
listed in Table 12.
Table 12. CCOM_TYP_CONFIG packet sub-types
Packet
sub-type
Packet name
Description
01h
CCOM_SUB_HWCFG
Used to send hardware configuration file to the xOEMcore.
02h
CCOM_SUB_FILE
Used to send normal or "mobile" NAV configuration files to
the xOEMcore.
FFh
CCOM_SUB_END
Used to tell the xOEMcore that all the NAV configuration
files have been sent.
Revision: 150709
21