The Combine Forum banner

1 - 6 of 6 Posts

·
Registered
Joined
·
55 Posts
Discussion Starter #1
Hi all,

i have noticed an scratched my head over this problem for a while. While doing the boundary AOG seeming tracks great, but when working with the section on it paints the line in jumps that do not follow the course taken in relation the boundary.

i happened to notice tonight while watching one of Brian's latest video's his incoming GPS information was MUCH smoother then the output i get.

I have now changed the rate from 1 hz to 10 on the ublox M8p this helped.

now i would like to adjust the NEMA sets sent to the tablet to only send the ones i need and stop the rest as they are not required.

My options are attached in the image.

(steering not currently in use, just guidance)

Thoughts?
Cheers, Joe
 

Attachments

·
Registered
Joined
·
21 Posts
When configuring U-Blox ZED F9P, do I have to change same settings on both units (base and rover) or only on rover side? I'm talking about Hz, baud rate and NMEA settings. And for GGA and VTG messages, do I select them from all satellites or some specific constellation? Default is same as in the first post by crash5291 - GNGGA and GNVTG. And what are last messages in each group that starts with dash ( _GGA, _VTG for example)?
 

·
Registered
Joined
·
375 Posts
When configuring U-Blox ZED F9P, do I have to change same settings on both units (base and rover) or only on rover side? I'm talking about Hz, baud rate and NMEA settings. And for GGA and VTG messages, do I select them from all satellites or some specific constellation? Default is same as in the first post by crash5291 - GNGGA and GNVTG. And what are last messages in each group that starts with dash ( _GGA, _VTG for example)?
As I see it, the base and rover are performing different functions. The base is gathering satellite data to output correction data for the rover to use. The rover is applying this correction to it's satellite data to output accurate position data for your application/use. The only two main things common between them is the satellite constellations that they are tracking and the format of the correction data. The base has to track the same satellite constellations as the rover in order to output relevant correction data and the format of that correction data needs to be compatible with both.

Otherwise, the rest of the settings should be set according to the function they are performing.
Baud rate is a setting specific to a serial data link, the sender/receiver baud (and other settings) have to match and it has to be fast enough to keep up with the volume of data. Your base probably (but not necessarily) has a serial output for it's correction data to a radio or ntrip castor, those serial settings could be completely different than the rover's correction input serial port. Your base probably does not need to output any NMEA data but most likely your rover does. My Piski Multi base station only outputs it's RTCM (correction data) every second and I have it's solution frequency set to 10hz but I suspect it would only need to calculate it's own position at the same rate as the RTCM output. On my rover though, I want a minimum of 5hz.
 

·
Registered
Joined
·
21 Posts
Thanks m_elias, I'm thinking by the same line, but as both boards had these settings identical when I received them, I thought better to ask. I will change what is needed for rover and leave base as is for the moment. Later I will check what happens when I turn off NMEA sentences for base, cause constellations are set in different settings.

Maybe someone can chime in about different GGA and VTG sentences - need all of them, some of them or only one? I'm thinking that, if I use multiple constellations, then I need to use appropriate GGA and VTG sentences as well.
 
1 - 6 of 6 Posts
Top