Hardware | Software | Services | Information | Special Offers

NV08C-RTK

Documents

General Information

NV08C-RTK website* by manufacturer NVS
NV08C-RTK thread * in "Geospector" board (German language)
New firmware features: GLONASS Inter-Channel Bias fully automated real-time recalibration (in parallel with GPS & GLONASS Fix), NMEA output and RTCM input on the same serial port (thus single Bluetooth interface devices possible) etc.
Vasily Engelsberg (NVS Switzerland):
"NV08C-RTK modules are preconfigured to work with NV08C-RTK base. It means the GLONASS Inter-Channel Bias is set for NV08C-RTK base. If you or your customers plan to use another module as a base then a correct bias should be set. To calibrate the NV08C-RTK module for another base receiver two options are available:1. For example, if a Trimble receiver is your RTCM data source then you can send NMEA message $PNVGRTK,ICBGLO,0.138. This command will set GLONASS Inter-Channel Bias to 0.138 that was measured by our engineers for a Trimble base receiver. The bias value can be saved along with other settings by PNVGCFG NMEA message.2. To provide the best results we can measure GLONASS Inter-Channel Bias for your base station. If you wish to do so then please advise.At the moment we’re working on an on-the-fly calibration algorithm that will be included in to the FW release we’ll release ASAP. Then you won’t have to care on the GLONASS Inter-Channel Bias since it will be done by the receiver on-the-fly.
NV08C-RTK modules are preconfigured to work with NV08C-RTK base. It means the GLONASS inter-channel bias is set for NV08C-RTK base. If you ... plan to use another module as a base then a correct bias should be set. To calibrate the NV08C-RTK module for another base receiver ... options are available:
For example, if a Trimble receiver is your RTCM data source then you can send NMEA message $PNVGRTK,ICBGLO,0.138. This command will set GLONASS inter-channel bias to 0.138 that was measured by our engineers for a Trimble base receiver. The bias value can be saved along with other settings by PNVGCFG NMEA message.
At the moment we’re working on an on-the-fly calibration algorithm that will be included into the FW release we’ll release ASAP. Then you won’t have to care on the GLONASS inter-channel bias since it will be done by the receiver on-the-fly.
... We’ve tested our RTK solution on the baseline up to 15 km."
Nikolay Bulavsky (NVS HQ):
"NV08C-RTK supports decoding of RTCM messages #1002, #1004, #1005, #1006, #1010, #1012 in Rover mode.
NV08C-RTK automatically generates RTCM messages #1002, #1006, #1010 in Base mode.
...
NV08C-RTK FW is initially configured to have close to zero ICB with Novatel and Leica HW.
Based on our test Trimble has quite significant ICB relative NV08C (and Novatel and Leica of course).
$PNVGRTK,ICBMODE,2 is only useful after initial calibration.
It allows to compensate little variations of ICB in parallel with RTK calculations.
Therefore if initial calibration is not good enough this command can't help.
$PNVGRTK,ICBMODE,1 allows to do initial calibration of GLONASS ICB using GPS only RTK Fix as reference.
Therefore you can try to use this command.
...
Yes, we recommend to use $PNVGRTK,ICBMODE,1 any time you start to work with VRS.
In case of wrong operation please try to use GPS only mode(it's not sensitive to current ICB setting).
If GPS only mode works but GPS + GLONASS can't fix therefore current ICB is not good enough."

SAPOS HEPS SN

German VRS provider (federal state Saxony): SAPOS HEPS SN*

Trimble Pivot Platform, RTCM 3.1 (1004, 1005, 1007), GPS + GLONASS, Mountpoint: VRS_3_2G_SN, GCG*
VRS computed to nearly zero baseline (about 0-3 m)
GLONASS inter-channel bias at about 0.025 close to zero ( $PNVGRTK,ICBGLO,0.025*67 )

SAPOS HEPS BY

German VRS provider (federal state Bavaria): SAPOS HEPS BY*

Trimble Pivot Platform, RTCM 3.1, GPS + GLONASS, Mountpoint: VRS_3_2G_BY, ETRS89*
VRS computed to nearly zero baseline (about 0-3 m)
GLONASS inter-channel bias at about 0.16 ( $PNVGRTK,ICBGLO,0.16*57 )

SAPOS HEPS BW

German VRS provider (federal state Baden-Wurttemberg): SAPOS HEPS BW*

RTCM 3.1, GPS + GLONASS, Mountpoint: VRS_3_2G_BW, ETRS89*
VRS computed to nearly zero baseline (about 0-3 m)
GLONASS inter-channel bias probably at about 0.18 ( $PNVGRTK,ICBGLO,0.18*59 )

SAPOS HEPS BB

German VRS provider (federal state Brandenburg): SAPOS HEPS BB*

RTCM 3, GPS + GLONASS, Mountpoint: VRS_3_2G_BB, ETRS89*

SAPOS HEPS ST

German VRS provider (federal state Saxony-Anhalt): SAPOS HEPS ST*

RTCM 3, GPS + GLONASS, Mountpoint: VRS_3_2G_ST, ETRS89*

SAPOS HEPS TH

German VRS provider (federal state Thuringia): SAPOS HEPS TH*

RTCM 3.1, GPS + GLONASS, Mountpoint: VRS_3_2G_TH, ETRS89*
VRS computed to nearly zero baseline (about 0-3 m)

AXIO-NET PED

German VRS provider (available throughout Germany): AXIO-NET PED*

RTCM 3.1, GPS + GLONASS, Mountpoint: 07-AXIO, ETRS89*
VRS computed with about 5 km baseline
GLONASS inter-channel bias at about 0.16 ( $PNVGRTK,ICBGLO,0.16*57 )

Use cases and practical experiences