![Memsic AHRS380ZA-200 Скачать руководство пользователя страница 62](http://html1.mh-extra.com/html/memsic/ahrs380za-200/ahrs380za-200_user-manual_1770428062.webp)
DMU380ZA Series
User’s Manual
________________________________________________________________________
Doc# 7430-3810 Rev. 02
Page 54
7.2.9
Error Response
Error Response (ASCII NAK, NAK = 0x1515)
Preamble
Packet Type
Length
Payload
Termination
0x5555
0x1515
0x02
<NAK payload>
<CRC (U2)>
The unit will send this packet in place of a normal response to a
faiiledInputPacketType
request if it could not be completed successfully.
NAK Payload Contents
Byte Offset
Name
Format
Scaling
Units
Description
0
failedInputPacketType
U2
-
-
the failed request
Output Packets (Polled)
7.3
The following packet formats are special informational packets which can be requested
using the ‘GP’ command.
7.3.1
Identification Data Packet
Identification Data (‘ID’ = 0x4944)
Preamble
Packet Type
Length
Payload
Termination
0x5555
0x4944
5+N
<ID payload>
<CRC (U2)>
This packet contains the unit
serialNumber
and
modelString
. The model string is
terminated with 0x00. The model string contains the programmed versionString (8-bit
Ascii values) followed by the firmware part number string delimited by a whitespace.
ID Payload Contents
Byte Offset
Name
Format
Scaling
Units
Description
0
serialNumber
U4
-
-
Unit serial number
4
modelString
SN
-
-
Unit Version String
4+N
0x00
U1
-
-
Zero Delimiter
7.3.2
Version Data Packet
Version Data (‘VR’ = 0x5652)
Preamble
Packet Type
Length
Payload
Termination
0x5555
0x5652
5
<VR payload>
<CRC (U2)>
This packet contains firmware version information.
majorVersion
changes may introduce
serious incompatibilities.
minorVersion
changes may add or modify functionality, but
maintain backward compatibility with previous minor versions.
patch
level changes
reflect bug fixes and internal modifications with little effect on the user. The build
stage
is one of the following: 0=release candidate, 1=development, 2=alpha, 3=beta. The
buildNumber
is incremented with each engineering firmware build. The
buildNumber
and
stage
for released firmware are both zero. The final beta candidate is v.w.x.3.y, which is
then changed to v.w.x.0.1 to create the first release candidate. The last release candidate
is v.w.x.0.z, which is then changed to v.w.x.0.0 for release.
VR Payload Contents