RANGECMP2
Compressed version of the RANGE log
|
Platform: |
OEM719, OEM729, OEM7500, OEM7600, OEM7700, OEM7720, PwrPak7, CPT7, CPT7700, SMART7, SMART2 |
This log contains the RANGE data in a compressed format. RANGECMP2 is more compressed than RANGECMP.
|
|
For dual antenna receivers, a RANGECMP2_1 log can be requested to get RANGECMP2 data from the second antenna. As described in Table: Binary message header structure, the message type indicates the log is from the second antenna. To request an ASCII log enter RANGECMP2A_1, and for a binary log enter RANGECMP2B_1. The RANGECMP2 and RANGECMP2_1 logs use the same message ID. |
|
|
|
Message ID: 1273
Log type: Synch
Recommended input:
log rangecmp2a ontime 10
Example:
#RANGECMP2A,USB1,0,55.0,FINESTEERING,2209,512524.000,02000020,1fe3,16809;2256,0
01a00a09fbc856c0540e1ffff6dd8c80c004201d1ffe4ffff4578e87c983d82d1ffe5ffff0dd8c8
75308082d1ffe7ffff0d5a667570f102faff01020010405f8592fb2fe1ffff2dbda41eb81980160
0e4ffff055ce61e0806001600021200542192852b0650e1ffff2dbc860f50e280ffffe4ffff0579
6655c83a820000e5ffff0dbc865f4800820000e7ffff0d3f62ad3033040900efffff097cc61e009
681fcff030c00ecf8b58551f83fe1ffff6dda06508021800d00e4ffff457948a400aa800c00e5ff
...
5cdfe3fe1ffff291f8417b01900d5ffe3ffff0d7f001b285f00d6ffedffff0d3e041ef86680deff
3c0c600078ef05cafa3fe1ffff29796829181500e5ffe3ffff4d9c6449685f80f5ffedffff0d79c
647307b80f6ff3e0e6018ff1306cc0630e1ffff2977e80f203a011100e3ffff4db80669d069830b
00edffff0d954856b8c88200003f176024e7f2057efb5fe1ffff293d0466980501dffff3ffff0db
be63bf81b02d6fff4ffff0d3f226fd0e380e2fff5ffff031ca45db89d80e9ffedffff0d784636b8
3900eaff*e438ba70
|
Field |
Field type |
Description |
Format |
Binary bytes |
Binary offset |
|
1 |
Log header |
RANGECMP2 header For information about log headers, see ASCII, Abbreviated ASCII or Binary. |
|
H |
0 |
|
2 |
# bytes |
Number of bytes in the compressed binary range data. The maximum is 2880 bytes for 120 channels or 5760 bytes for 240 channels. |
Uchar |
4 |
H |
|
3 |
RangeData |
Compressed binary range data in the format of Table: Satellite block of the range record format (RANGECMP2 only) and Table: Signal block of the range record format (RANGECMP2 only). The compressed binary range data is organized into satellite blocks, one for each satellite. Each satellite block is followed by a variable number of signal blocks corresponding to the same satellite. For example, a Satellite Block for GPS PRN 17 may be followed by two Signal Blocks for the L1 C/A and L2C signals. |
Uchar |
#bytes |
H+4 |
|
4 |
xxxx |
32-bit CRC (ASCII and binary only) |
Hex |
4 |
H+4+ |
|
5 |
[CR][LF] |
Sentence terminator (ASCII only) |
- |
- |
- |
|
Data |
Description |
Bits first to last |
Length (bits) |
Scale factor |
Units |
|
SV Channel Number |
Receiver SV channel number |
0-7 |
8 |
- |
- |
|
Satellite Identifier |
Satellite identifier specific to the satellite system Refer to PRN numbers |
8-15 |
8 |
- |
- |
|
GLONASS Frequency Identifier |
GLONASS frequency channel offset by +7 |
16-19 |
4 |
(7+Ch#) |
- |
|
Satellite System Identifier |
Defined in Table: Satellite system |
20-24 |
5 |
- |
Enum |
|
Reserved |
25 |
1 |
- |
- |
|
|
Pseudorange Base |
Pseudorange base value to be combined with PSR Diff and Phaserange Diff in each following Signal Block |
26-54 |
29 |
1 |
m |
|
Doppler Base |
Doppler base value to be combined with the Scaled Doppler Diff value in each following Signal Block |
55-75 |
21 |
1 |
Hz |
|
Number of Signal Blocks |
The number of Signal Blocks to follow this Satellite Block. See Table: Signal block of the range record format (RANGECMP2 only) for Signal Block definition |
76‑79 |
4 |
- |
- |
|
Data |
Description |
Bits first to last |
Length (bits) |
Scale factor |
Units |
|
Signal Type |
Defined in Table: Signal type (only in RANGECMP2) |
0-4 |
5 |
- |
Enum |
|
Phase Lock |
Phase Lock: 0 = Not locked, 1 = Locked |
5 |
1 |
- |
Bool |
|
Parity Known |
Parity Known: 0 = Not known, 1 = Known |
6 |
1 |
- |
Bool |
|
Code Lock |
Code Lock: 0 = Not locked, 1 = Locked |
7 |
1 |
- |
Bool |
|
Locktime |
Time of continuous tracking with no cycle slips. The locktime value saturates at a maximum of 131071 ms |
8-24 |
17 |
1 |
ms |
|
Correlator Type |
Correlator type: (see Table: Correlator Type) |
25-28 |
4 |
- |
Enum |
|
Primary Signal |
Primary signal: 0 = Not primary, |
29 |
1 |
- |
Bool |
|
Carrier Phase Measurement |
Carrier phase measurement: |
30 |
1 |
- |
Bool |
|
Reserved |
31 |
1 |
- |
- |
|
|
C/No |
Carrier to Noise density ratio |
32-36 |
5 |
(20 + n) |
dB-Hz |
|
StdDev PSR |
Pseudorange Standard Deviation (defined Table: Std Dev PSR scaling) |
37-40 |
4 |
Bit Field in Table: Std Dev PSR scaling |
- |
|
StdDev ADR |
Carrier-Phase Standard Deviation (defined Table: Std Dev ADR scaling) |
41-44 |
4 |
Bit Field in Table: Std Dev ADR scaling |
- |
|
PSR Diff |
Pseudorange Diff to be combined with Pseudorange base i.e., |
45-58 |
14 |
1/128 |
m (unsigned) |
|
Phaserange Diff |
Phaserange Diff to be combined with Pseudorange Base i.e., |
59-78 |
20 |
1/2048 |
m (unsigned) |
|
Scaled Doppler Diff1 |
Doppler Diff to be combined with Doppler Base. Note that all Doppler values are scaled to the L1/E1 equivalent value. (refer to Table: L1/E1/B1 scaling) i.e., Note: The Scaled Doppler Diff field is the only field in the RANGECMP2 log that should be parsed as Two's Complement. The most significant byte (MSB) determines whether the number will be positive (< 0x7) or negative (> 0x7). Two's complement should be applied prior to AND, right bit shift computations. |
79‑95 |
17 |
1/256 |
Hz (signed) |