Skip to content

Integrated Navigation & GNSS Command and Programming Manual

Rev 1.0

Applicable to the CH3xx / HI30 / HI32 series

Document Revision History

VersionDateAuthorChanges
V1.0Oct 1, 2023HiPNUCInitial version

Module Configuration Commands

Module configuration uses ASCII string commands. Each command must end with a carriage return + line feed \r\n (similar to AT commands) before the system can recognize it.

Command Overview

CommandDescription
REBOOTReset
LOGRequest message output from the device
CONFIGConfigure the module
UNLOGALLCancel all message output
SAVECONFIGSave configuration to Flash
SETBASELINESet the dual-antenna baseline length / tilt constraint, lever-arm compensation, etc.; takes effect after save + reboot.
SERIALCONFIGSet the serial-port baud rate

Command Reference

REBOOT

Reset and reboot, effective immediately. Equivalent to a power cycle.

LOG

ENABLE/DISABLE: turn data output on/off globally
  • LOG ENABLE - globally enable data-frame output (default)
  • LOG DISABLE - globally disable data-frame output
VERSION: show module version

LOG VERSION - print firmware version information

COMCONFIG: show serial-port configuration

LOG COMCONFIG - print serial port and output-protocol configuration

INSCONFIG: show integrated-navigation configuration

LOG INSCONFIG - show the integrated-navigation configuration, including the current kinematic model, dual-antenna parameters and the NMEA Talker ID.

MOTION_MODEL=CAR
ANTA=0.0,0.0,0.0
ANTB=0.0,1.0,0.0
NMEATID=GP
OK
MSG: configure data-frame output and rate

Format: LOG <MSG> <TYPE> <PERIOD>

  • MSG: GGA, RMC, SXT, HI81, etc.
  • TYPE: ONTIME means periodic output
  • PERIOD: output-frame period in seconds; allowed values: 1 (1 Hz), 0.5 (2 Hz), 0.1 (10 Hz), 0.02 (50 Hz), 0.01 (100 Hz), 0.005 (200 Hz)

Examples:

  • LOG HI81 ONTIME 0.01 - set the HI81 packet output period on the current serial port to 0.01 s (100 Hz)
  • LOG SXT ONTIME 0.05 - set the SXT packet output period on the current serial port to 0.05 s (20 Hz)
  • LOG SXT ONTIME 0 - turn off SXT packet output on the current serial port

CONFIG

Configures the module's working parameters. Most commands take effect immediately, and SAVECONFIG is required to persist them across power cycles.

Configure the integrated-navigation kinematic model
  • CONFIG MODEL CAR (factory default) - set the model constraint to vehicle mode. In this mode the solver applies NHC (non-holonomic constraints), which significantly reduces accumulated error in GNSS-outage scenarios such as tunnels and underground garages.
  • CONFIG MODEL SHIP - set the model constraint to marine/ship mode, reducing accumulated error during outages on ships.
  • CONFIG MODEL PLANE - set the model constraint to aircraft mode. This mode applies no kinematic constraint and suits airborne use.
  • CONFIG MODEL BASE - set the module to base-station mode. After this, the module locks its own position within 60 s (position no longer changes); commonly used to build a self-hosted RTK base station. The antenna must be in a good observation environment when configuring base mode.

Use LOG INSCONFIG to view the current user configuration.

Configure NTRIP differential account

This device can drive certain vendors' 4G DTU terminals or an Ethernet interface to provide network RTK: it automatically configures the DTU/Ethernet interface and feeds in RTK differential data. Steps:

  1. Connect COM2 to the DTU. COM2 is dedicated to the DTU and uses the 4G DTU for NTRIP RTK differential.
  2. The currently supported DTU model is TAS-LTE-364 (Tas 4G transparent DTU). Make sure the model is correct and that a working 4G SIM card is inserted.
  3. Configure the differential account: CONFIG NTRIP <SERVER_IP> <PORT> <MNT_POINT> <USER_NAME> <PASSWD>, where:
  • SERVER_IP: CORS server address, a domain name or IP.
  • PORT: CORS server port
  • MNT_POINT: mount point, e.g. AUTO for Qianxun, or RTCM33_GRCE for China Mobile.
  • USER_NAME: CORS account username
  • PASSWD: CORS account password

Example - configure a Qianxun CORS account (sample username qxxrli003, password 123456):

Example: CONFIG NTRIP rtk.ntrip.qxwz.com 8002 AUTO qxxrli003 123456. This is saved across power cycles; configure it once.

  1. Restart the module.
  2. Use LOG NTRIPCONFIG to view the current configuration. If DTU NAME shows TAS-LTExxx, the module has established a link with the DTU (the module auto-negotiates the baud rate; an empty NAME means the DTU link failed). Note that a non-empty NAME only confirms the module-to-DTU link, not whether the DTU-to-network link is healthy.
DTU     NAME:  Revision: TAS-LTE-C_C4002L242_
NTRIP SERVER:  xxxxxxx.com:xxxx
NTRIP  MOUNT:  AUTO
NTRIP  UNAME:  xxxxxxx
NTRIP PASSWD:  xxxxxxx
  1. If the RTK IP/account details are correct, RTK is typically reached within ~30 s.

Save the configuration and reboot for it to take effect.

Enable the built-in SD-card data logging

Some products have an internal SD card for data logging. On each power-up a .jog file named after the power-up UTC time is created automatically. You can use an FTP tool (e.g. FileZilla) to view all files on the internal card.

  • CONFIG FLOG COM1 1 - enable COM1 logging; all data output on the main serial port COM1 is also copied to a log file on the SD card.
  • CONFIG FLOG COM1 0 - disable COM1 logging.

UNLOGALL

Set the output rate of all periodic messages to 0 (no output).

SAVECONFIG

Save all configuration to Flash. Usually used together with REBOOT, i.e. save everything then reboot to apply.

SETBASELINE

Sets antenna A's position relative to the IMU (lever-arm compensation) and the angle of the secondary (B / heading) antenna relative to antenna A, for dual-antenna installation.

Set antenna A's position relative to the IMU (lever-arm compensation): X, Y, Z are antenna A's position relative to the IMU in the IMU body frame, in meters.

SETBASELINE ANTA <X,Y,Z>

Set the B (heading) antenna position: like antenna A, X, Y, Z are the antenna's position relative to the IMU in the IMU body frame, in meters.

SETBASELINE ANTB <X,Y,Z>

Example: to set the angle between the A→B vector and the vehicle forward direction (IMU +Y axis) to 90° (clockwise positive, as shown below), where antenna A relative to the IMU is X=-1.5,Y=-1.2,Z=-0.3 and antenna B relative to the IMU is X=1.5,Y=-1.2,Z=-0.3:

SETBASELINE ANTA -1.5,-1.2,-0.3
SETBASELINE ANTB  1.5,-1.2,-0.3

After installing/setting the antenna positions, power-cycle or reboot the module.

  1. After setting antenna parameters, use LOG INSCONFIG to verify.
  2. Integrated navigation also works without lever-arm compensation, but correct, valid compensation greatly improves position accuracy when turning after a GNSS outage.

SERIALCONFIG

Set the serial-port baud rate; 115200 / 460800 / 921600 are supported.

SERIALCONFIG <BAUD>

Example - set the current port to 115200: SERIALCONFIG 115200.

Output Data Protocol (RS232/422, Ethernet)

Overview

This product supports two output protocol families: ASCII and binary. ASCII messages use the NMEA format; binary messages use HiPNUC's custom binary format. The NMEA format follows NMEA 0183.

  • Output latitude/longitude is referenced to antenna A.
  • Antenna B is used only for dual-antenna heading and is unrelated to positioning.

Hardware Interfaces

  • RS232 / RS422 / RS485: essentially all serial ports; both ends must use the same baud rate. Factory default is 115200.
  • Ethernet: some products have Ethernet with an internal TCP/IP stack and DHCP client enabled by default. Connect the Ethernet port to a router LAN port on the same subnet as the PC; it obtains an IP automatically after connecting. Connect as a TCP client on default port 5944. Once connected, all commands and behavior are identical to the serial port.

Factory Default Output

By default this product outputs the binary HI81 protocol at 100 Hz.

NMEA Messages (ASCII)

The NMEA protocol starts with $, followed by the descriptor, ID and data fields. The data section ends with *, followed by a two-digit checksum and finally a carriage return + line feed (0x0D, 0x0A).

NMEA message format (ASCII structure):
$--<message-id>,<field>,<field>,...,<field>*<checksum><CR><LF>
FieldDescription
$Start delimiter (ASCII 0x24). Marks the beginning of a message.
---Satellite-system class, used to distinguish BeiDou / GPS / combined output.
BD - BeiDou
GP - GPS
GN - combined
message-idIdentifies the message type and function. Fixed 3-character ASCII; uppercase letters recommended.
,Field delimiter (ASCII 0x2C). Separates multiple fields in a message.
data fieldEach message can contain multiple fields separated by ,. Unless noted otherwise, only printable ASCII is allowed in fields. Field position within a message is determined by counting the , delimiters.
*Checksum delimiter, between the data content and the checksum field.
checksumThe checksum is the byte-wise XOR of all characters between $ and * (exclusive). The high and low nibbles are each expressed as a hex ASCII character (0-9, A-F), high nibble first.
<CR><LF>Terminator (ASCII 0x0D, 0x0A). Marks the end of a message.

NMEA Message List

NMEADescriptionSource
GGAFix data, RTC time, fix quality, satellites in viewGNSS only
RMCRecommended minimum positioning informationGNSS only
VTGCurrent ground speedGNSS only
SXTIntegrated-navigation informationIntegrated nav

GGA

Receiver time, position and fix-related data. Note: this sentence outputs the GNSS-only fix, not the integrated-navigation result.

$GPGGA,062134.00,2813.9908005,N,11252.6285300,E,1,28,0.5,83.684,M,-17.038,M,0.000,0000*60
IDExampleFormatDescription
1$GPGGAheader
2062134.00hhmmss.ssUTC time
32813.9908005ddmm.mmmmLatitude, 28°13.9908005′, range 0°-90°. First two digits are degrees, the rest minutes.
4N-Latitude direction N/S (N = north, S = south)
511252.6285300ddmm.mmmmLongitude, 112°52.6285300′, range 0°-180°. First three digits are degrees, the rest minutes.
6E-Longitude direction E/W (E = east, W = west)
71x0: invalid; 1: single-point; 2: pseudorange differential; 4: fixed; 5: float or PPP.
828xxNumber of satellites used in the fix
90.5x.xHDOP: horizontal dilution of precision
1083.684x.xxxAltitude
11MUAltitude unit: m
12-17.038x.xGeoid undulation: difference between the WGS84 ellipsoidal height and altitude; "-" means the geoid is below the WGS84 ellipsoid.
13MUUndulation unit: m
140.000xxxxDifferential age, in s
150000x.xDifferential station ID
1660hhChecksum

About the lat/long format in GGA:

Latitude: expressed as degrees and minutes (no seconds), as ddmm.mmmm, where dd is degrees (two digits) and mm.mmmm is minutes (two integer digits and up to four decimals), followed by N (north) or S (south). Longitude: similar to latitude, but degrees are three digits, as dddmm.mmmm, followed by E (east) or W (west).

Converting to decimal degrees: although GGA natively uses degrees and minutes, you sometimes need decimal degrees. The formula:

  • decimal degrees = degrees + (minutes / 60)

    For example, converting 4807.038 to decimal degrees: 48 + (07.038 / 60) = 48.1173°

RMC

Recommended minimum navigation data. Note: this sentence outputs the GNSS-only fix, not the integrated-navigation result.

$GPRMC,020550.00,A,2813.9891299,N,11252.6278784,E,0.033,315.7,161117,0.0,E,A,V*4A
IDExampleFormatDescription
1$GPRMCheaderStart delimiter + message ID
2020250.00hhmmss.ssUTC time
3Ax.xFix status: A = valid, V = invalid
42813.9891299ddff.ffLatitude, same format as GGA
5N-Latitude direction, same as GGA
611252.6278784dddff.ffLongitude, same format as GGA
7E-Longitude direction, same as GGA
80.033x.xGround speed, in knots
9315.7x.xGround course, referenced to true north, clockwise (0°-360°)
10161117ddmmyyDate (day, month, year)
110.0x.xMagnetic declination, in degrees
12E-Declination direction
13A-Mode indicator: N = invalid; A = autonomous; E = estimated; D = differential; M = manual input
14V-S = Safe, C = Caution, U = Unsafe, V = Not valid
154AhhChecksum

VTG

Outputs ground-speed information.

$GPVTG,134.395,T,134.395,M,0.019,N,0.035,K,A*33
IDExampleFormatDescription
1$GPVTGheader
2134.395xxx.xxxGround course referenced to true north, 000-359.999°
3TUTrue-north indicator
4134.395xxx.xxxGround course referenced to magnetic north, 000-359.999°
5MUMagnetic-north indicator
60.019xxx.xxxHorizontal speed 000-999, in knots
7NUUnit: N = knots
80.035xxx.xxxHorizontal speed 000-999, in km/h
9KUUnit: K = km/h
10AUA = autonomous; D = differential; E = estimated; M = manual input; N = invalid.
1133hhChecksum

SXT

Outputs integrated-navigation information.

$GPSXT,20230310090529.59,116.45784882,39.90572287,158.2289,359.87,-4.99,359.87,0.001,171.25,1,0,15,15,0.056,-0.040,0.017,-0.001,-0.000,0.002,8,0*43
IDExampleFormatDescription
1$GPSXTheader
220230310090529.59yyyy/mm/dd/hh/mm/ss.ssUTC time
3116.45784882ddd.ddddddddFused longitude (deg)
439.90572287ddd.ddddddddFused latitude (deg)
5158.2289ddd.ddddFused altitude (m)
6359.87ddd.ddYaw (deg), 0-360°
7-4.99ddd.ddPitch (deg), -90:90°
8359.87ddd.ddVelocity course (deg)
90.001ddd.dddHorizontal speed (m/s)
10171.25ddd.ddRoll (deg), -180:180°
111GNSS-only fix flag: 0 invalid; 1 single-point; 2 pseudorange differential; 4 fixed; 5 float/PPP.
Relates to antenna A only, not B.
120GNSS-only heading flag: 4 fixed (heading valid); other values: heading not locked, invalid.
Relates to antennas A and B; heading is meaningful only with a fixed solution (4).
1315Satellites used by antenna A (positioning)
1415Satellites used by antenna B (heading)
150.056X-axis angular rate (deg/s)
16-0.040Y-axis angular rate (deg/s)
170.017Z-axis angular rate (deg/s)
18-0.001ddd.dddEast velocity (m/s)
19-0.000ddd.dddNorth velocity (m/s)
200.002ddd.dddUp velocity (m/s)
218Integrated-navigation status:
0: invalid - no GNSS, cannot initialize position
1: aligning - position initialized, but some motion is needed to finish filter initialization and enter integrated navigation
3: navigating - integrated navigation engaged
6: inertial dead-reckoning - integrated navigation engaged but GNSS lost, in pure-inertial mode (tunnel, garage, etc.)
22antenna status0: A normal, B normal
1: A abnormal (not inserted, feeder open/short), B normal
2: A normal, B abnormal
3: A abnormal, B abnormal
Valid only with our dedicated measurement antenna.
2308hhChecksum

Binary Messages (HiPNUC)

This is HiPNUC's custom binary protocol. It can output all sensor information and is supported by products with UART (RS-232/TTL), USB and RS-485 interfaces. Default serial format is N-8-N-1 (8 data bits, 1 stop bit, no parity).

Frame Format

After power-up, the module outputs frame data at the default rate (100 Hz). The frame format:

FieldValueLength (bytes)Description
Frame header0x5A10x5A
Frame type0xA510xA5
Payload len1-5122Length of the payload, LSB first.
Counts the payload only (excludes header, type, length, CRC).
CRC-216-bit CRC over all fields except CRC itself (header, type, length, payload).
LSB first.
Payload-1-512Data carried in one frame, made of several sub-packets. Each packet has a tag and data; the tag determines the data type and length.

Payload Content

Integrated Navigation Data (HI81)

The payload is 104 bytes and contains all navigation information.

OffsetNameTypeSize (Byte)UnitScaleDescription
0taguint8_t1--Packet tag: 0x81
1statusuint16_t2--Status word, reserved
3ins_statusuint8_t1--Integrated-navigation status:
0: invalid - no GNSS, cannot initialize position
1: aligning
3: navigating
6: inertial dead-reckoning (GNSS lost)
4gpst_wnuint16_t2week1GPS time, week
6gpst_towuint32_t4s0.001GPS time, time of week
10reserveduint16_t2--Reserved
12gyr_bint16_t*36rad/s0.001Body-frame angular rate: X, Y, Z (factory calibrated)
18acc_bint16_t*36m/s^(2)0.0048828Body-frame acceleration: X, Y, Z (factory calibrated)
24mag_bint16_t*36uT0.030517Body-frame magnetic field: X, Y, Z (factory calibrated)
30air_pressureint16_t2Pa1Air pressure + 100000 Pa: e.g. 2000 means 102000 Pa
32od_speedint16_t2m/s0.01Odometer speed (vehicle OBD-II speed)
34temperatureint8_t1°C1System average temperature
35utc_yearuint8_t1year1UTC year, e.g. 24 = 2024
36utc_mouthuint8_t1month1UTC month
37utc_dayuint8_t1day1UTC day
38utc_houruint8_t1hour1UTC hour
39utc_minuint8_t1min1UTC minute
40utc_secuint16_t2s0.001UTC second
42rollint16_t2deg0.01Integrated-nav roll, range -180:180
44pitchint16_t2deg0.01Integrated-nav pitch, range -90:90
46yawuint16_t2deg0.01Integrated-nav yaw, range 0-360, north-to-east positive
48quatint16_t*48-0.0001Quaternion: W, X, Y, Z
56ins_lonint32_t4deg1e-7Fused longitude
60ins_latint32_t4deg1e-7Fused latitude
64ins_mslint32_t4m0.001Fused altitude
68pdopuint8_t1-0.1GNSS position dilution of precision
69hdopuint8_t1-0.1GNSS horizontal dilution of precision
70solq_posuint8_t1--GNSS-only fix flag: 0 invalid; 1 single-point; 2 pseudorange differential; 4 fixed; 5 float/PPP.
Antenna A only.
71nv_posuint8_t1--Satellites used for GNSS positioning
72solq_headinguint8_t1--GNSS-only heading flag: 4 fixed (heading valid); other values: not locked.
Relates to A and B; only fixed makes heading meaningful.
73nv_headinguint8_t1--Satellites used for GNSS heading
74diff_ageuint8_t1s1RTK differential age
75undulationint16_t2m0.01Geoid undulation
77ant_statusuint8_t1--Antenna status flag
0: A normal, B normal
1: A abnormal (not inserted, feeder open/short), B normal
2: A normal, B abnormal
3: A abnormal, B abnormal
Valid only with our dedicated measurement antenna.
78vel_enuint16_t*36m/s0.01ENU velocity in the navigation frame (integrated-nav output)
84acc_enuint16_t*36m/s^(2)0.0048828ENU acceleration in the navigation frame (integrated-nav output)
90reservedint16_t2Reserved
92reservedint16_t2Reserved
94reservedint16_t2Reserved
96reservedint16_t2Reserved
98reserved-6--Reserved

CRC

16-bit CRC reference implementation:

/*
	currectCrc: previous crc value, set 0 if it's first section
	src: source stream data
	lengthInBytes: length
*/
static void crc16_update(uint16_t *currectCrc, const uint8_t *src, uint32_t lengthInBytes)
{
    uint32_t crc = *currectCrc;
    uint32_t j;
    for (j=0; j < lengthInBytes; ++j)
    {
        uint32_t i;
        uint32_t byte = src[j];
        crc ^= byte << 8;
        for (i = 0; i < 8; ++i)
        {
            uint32_t temp = crc << 1;
            if (crc & 0x8000)
            {
                temp ^= 0x1021;
            }
            crc = temp;
        }
    } 
    *currectCrc = crc;
}

Data Protocol (CAN - SAE J1939)

The CAN interface supports both CANopen and SAE J1939. The module defaults to SAE J1939; contact technical support for a CANopen version. The default CAN baud rate is 500 Kbps.

SAE J1939 Protocol

J1939 uses a 29-bit extended frame ID: 3 bits of priority, 1 reserved bit, an 8-bit page that defines its function via the PGN, with the first 8 of the lower 24 bits being the source address (SA), the middle 8 the specific PGN (describing the data function/content), and the last 8 the destination address (DA) or a further-refined PGN. This structure supports prioritized message transmission, a wide range of parameter-group identifiers, and source/destination addressing on the network.

PGNDescription
Communication modeBroadcast
Default interval100 ms
Data length8 bytes per PGN
PF (PDU format)0xFF
PS (PDU specific)Extended PGN address (GE) when PF > 0xF0, otherwise the destination address (DA)
Priority3
Default J1939 address0x08
Data formatAll frames use LSB (little-endian); unless noted, signed integers

PGN Message List

PGN65296 (FF10) Latitude/Longitude

CANID=0x0CFF1008

SPN nameSPN position (byte)Description
Latitude0-3Unit: deg, scale: 0.0000001
Longitude4-7Unit: deg, scale: 0.0000001

PGN65300 (FF14) Altitude and Differential Age

CANID=0x0CFF1408

SPN nameSPN position (byte)Description
Altitude0-3Unit: m, scale: 0.01
UNDULATION4-5Unit: m, scale: 0.01
Diff age6-7Unit: s, scale: 0.01

PGN65304 (FF18) Fix Status and Satellite Count

CANID=0x0CFF1808

SPN nameSPN position (byte)Description
GNSS-only fix quality00 invalid; 1 single-point; 2 pseudorange differential; 4 fixed; 5 float/PPP.
GNSS-only heading qual10 invalid; 4 fixed (only a fixed solution makes heading meaningful)
Positioning sat count2Satellites used for positioning
Heading sat count3Satellites used for heading
Integrated-nav status41: aligning, 3: navigating
Reserved5-7-

PGN65318 (FF26) Velocity

CANID=0x0CFF2608

SPN nameSPN position (byte)Description
East velocity0-1Unit: m/s, scale: 0.01
North velocity2-3Unit: m/s, scale: 0.01
Up velocity4-5Unit: m/s, scale: 0.01
Ground speed (E/N resultant magnitude)6-7Unit: m/s, scale: 0.01

PGN65327 (FF2F) Time

CANID=0x0CFF2F08

SPN nameSPN position (byte)Description
UTC year020 = 2020, and so on
UTC month1
UTC day2
UTC hour3
UTC min4
UTC sec5
UTC ms6-7Unit: ms, scale: 1

PGN65332 (FF34) Acceleration

CANID=0x0CFF3408

SPN nameSPN position (byte)Description
Accel X0-1Unit: G (1G = gravity), scale: 0.00048828
Accel Y2-3Unit: G (1G = gravity), scale: 0.00048828
Accel Z4-5Unit: G (1G = gravity), scale: 0.00048828
Reserved6-7-

PGN65335 (FF37) Angular Rate

CANID=0x0CFF3708

SPN nameSPN position (byte)Description
Rate X0-1Unit: deg/s, scale: 0.061035
Rate Y2-3Unit: deg/s, scale: 0.061035
Rate Z4-5Unit: deg/s, scale: 0.061035
Reserved6-7

PGN65341 (FF3D) Integrated-Nav Attitude (Pitch/Roll)

CANID=0x0CFF3D08

SPN nameSPN position (byte)Description
Roll0-3Unit: °, scale: 0.001
Pitch4-7Unit: °, scale: 0.001

PGN65345 (FF41) Integrated-Nav Attitude (Heading)

CANID=0x0CFF4108

SPN nameSPN position (byte)Description
Yaw0-30-360, unit: °, scale: 0.001
Reserved4-7

PGN65347 (FF43) Temperature and Air Pressure

CANID=0x0CFF4308

SPN nameSPN position (byte)Description
Temperature0-1Unit: ℃, scale: 0.01
Reserved2-3
Air pressure4-7Unit: Pa, scale: 0.01

Module Configuration (CAN)

Configuration Format

Host sends: ADDR + CMD + STATUS + VAL; device replies: ADDR + CMD + STATUS + VAL.

FieldSize (Byte)Description
ADDR2Register address
CMD10x06: write, 0x03: read
STATUS1Reserved
VAL4Value written or read

Common Command Examples

29-bit CAN ext. frame IDCAN dataDescriptionNotes
0x0CEF08xx10 01 06 00 [VAL]VAL: 4 bytes (LE)PGN FF10 (lat/long) interval, ms, range 10-1000
0x0CEF08xx14 01 06 00 [VAL]VAL: 4 bytesPGN FF14 (altitude & diff age) interval, ms, range 10-1000
0x0CEF08xx18 01 06 00 [VAL]VAL: 4 bytesPGN FF18 (fix status & sats) interval, ms, range 10-1000
0x0CEF08xx2F 01 06 00 [VAL]VAL: 4 bytesPGN FF2F (time) interval, ms, range 10-1000
0x0CEF08xx34 01 06 00 [VAL]VAL: 4 bytesPGN FF34 (acceleration) interval, ms, range 10-1000
0x0CEF08xx37 01 06 00 [VAL]VAL: 4 bytesPGN FF37 (angular rate) interval, ms, range 10-1000
0x0CEF08xx3D 01 06 00 [VAL]VAL: 4 bytesPGN FF3D (pitch/roll) interval, ms, range 10-1000
0x0CEF08xx41 01 06 00 [VAL]VAL: 4 bytesPGN FF41 (heading) interval, ms, range 10-1000
0x0CEF08xx43 01 06 00 [VAL]VAL: 4 bytesPGN FF43 (temp & pressure) interval, ms, range 10-1000
0x0CEF08xx9A 00 06 00 [VAL]VAL: 4 bytesSet baud rate (saved, effective on reset): 0:1000K, 1:800K, 2:500K, 3:250K, 4:125K
0x0CEF08xx9C 00 06 00 [VAL]VAL: 4 bytesJ1939 device ID, 1-64 (default 8). Caution: changing the ID also requires updating the destination address in all J1939 frame IDs.
0x0CEF08xx00 00 06 00 00 00 00 00-Save all configuration to Flash
0x0CEF08xx00 00 06 00 01 00 00 00-Restore factory defaults
0x0CEF08xx00 00 06 00 FF 00 00 00-Reset

xx in the ID field: the J1939 source address, any byte. xx in the data field: any byte.

Example: ID=0x0CEF0855, DATA = 37 01 06 00 64 00 00 00 sets PGN FF37 to a 100 ms period (10 Hz).

Firmware Upgrade

This product supports firmware upgrades. Use the CHCenter host software and follow the steps below; request the firmware file (.hex) from our technical support.

Technical Support

New product and document information is available via our website and WeChat official account. WeChat:

Telegram: