Spi Protocol; Table 10. Asynchronous Inertial Message (0X0D Data Format) - Honeywell HG1120 Installation And Interface Manual

Inertial measurement unit
Table of Contents

Advertisement

HG1120 Installation and Interface Manual

Table 10. Asynchronous Inertial Message (0x0D Data Format)

POSITION
PARAMETER
1
IMU Address
2
Message ID
3-13
Control Data
14
Delta Angle X
15
Delta Angle Y
16
Delta Angle Z
17
Delta Velocity X
18
Delta Velocity Y
19
Delta Velocity Z
20
Checksum
Sum of all message data (positions
1-19 of this table), taken as 16 bit
words, and summed without regard for
rollover.
Total

SPI Protocol

The SPI 1800/300 Hz data protocol is as specified in Table 10 – SPI Control Message and
Table 11 – Inertial Message.
The SPI 600/100 Hz data protocol is as specified in Table 12 – Control Message Format and
Table 13 – SPI Inertial Message.
These messages are identical in content to the asynchronous HG1120 Control/Inertial messages
except that Position 0 will be added and contain a 1 byte field containing the number of bytes of
data (not including spare bytes) in the message.
The SPI clock frequency must be at least 2 MHz or no faster than 9 Mhz.
The SPI clock polarity and phase are set to one (1).
SPI data order is MSB first.
A 4-wire SPI implementation is used.
The DATA_RDY signal must be used to synchronize your application to the data being produced to
ensure a consistent data set. The DATA_RDY signal must trigger an SPI fetch, and the clock rate
must be fast enough to fetch an entire message within the Control data rate (either 1800 or 600 Hz).
The SPI_SS signal should be set, then the application should clock 408 (51*8) SPI bits before
resetting the SPI_SS signal.
The External SPI device will be coming in asynchronous to the Control/Inertial message sequence.
Each SPI message in the Control/Inertial set will be a constant length. The Control message will have
spare bytes at the end, NOT included in the checksum, to match the length of the Inertial Message.
aerospace.honeywell.com/HG1120
|
LENGTH
LSB WEIGHT
(BYTES)
1
N/A
1
N/A
22
N/A
4
2
-33
4
2
-33
4
2
-33
4
2
-27
4
2
-27
4
2
-27
2
N/A
50
UNITS OR CONTENTS
Constant 0x0E
Constant 0x0D
Contents same as Message 0x0C
Positions 3-13.
radians/LSB
or equivalently,
radians/second/Hz/LSB
0.3048 meters/sec/LSB
or equivalently,
0.3048 meters/sec
/Hz/LSB
2
// this pseudo code illustrates the
checksum algorithm
u16sum = 0;
for (i=0; i<24; i++) // (50-2)/2=24
{ u16sum += u16_msg_array[i]; }
Checksum = u16_msg_array[24];
if (Checksum != u16sum) {checksum
error}
11

Advertisement

Table of Contents
loading

Table of Contents