...
Parameter name | Description | Default |
|---|---|---|
type | Data output format for gnss data source. Currently only | NMEA |
port | Serial port number for gnss source. | |
baudrate | Serial port baudrate to connect to GNSS source.
| /dev/ttyUSB0 |
rtcm | Set true to enable RTCM correction data forwarding from RTCM source to gnss module. | false |
For details about the overall configuration of the RTK-GPS system refer to this section.
Odometry
The vehicle source is the data source that reads raw CAN data messages from a given CAN bus interface and parses the vehicle data using to the provided CAN protocol.
...
If you managed to get an RTK-GPS fix, your LPVR-POS system is now ready to operate with RTK-GPS as global centimeter-accurate position reference.
Using Alternate NTRIP Servers
In principle the FusionHub RTCM node can be used with any NTRIP server. We’ve so far only tested it using the Emlid caster described above and the Softbank Ichimili service in Japan. When configuring FusionHub for an alternate NTRIP server make sure to correctly modify all fields of the RTCM node. Make sure that the initialLatitude and initialLongitude coordinates point roughly to the area where you would like to operate the system. Check the command line output of FusionHub, if the connection to the NTRIP server was successful:
There should be a line saying "Output to NTRIP server: .." with the initial GET command that's sent to the NTRIP server
The output "Successfully connected to NTRIP Caster" should follow a few lines further on
If you see these messages, we know that FusionHub connected correctly to the NTRIP server. Check the GnssData message as described above for connection state.
References
...