X

simpleRTK2Blite stops sending messages in simpleRTK2B+heading setup

Q&A forumCategory: QuestionssimpleRTK2Blite stops sending messages in simpleRTK2B+heading setup
bb asked 1 month ago
Hello,
I have the simpleRTK2B+heading setup consisting of a simpleRTK2B and a simpleRTK2Blite (as can be seen here: https://www.ardusimple.com/simplertk2heading-hookup-guide/)
I flashed both boards with the newest firmware version 1.32. Then, I “uploaded” the recommended config files (from here: https://www.ardusimple.com/configuration-files/).
For the simpleRTK2B board I used the config 1Hz simpleRTK2B (Rover) of a simpleRTK2B+heading kit (for firmware version 1.30).
And for the simpleRTK2Blite board I used the 1Hz simpleRTK2Blite (Moving Base) of a simpleRTK2B+heading kit (also for firmware version 1.30).
My problem is that the simpleRTK2Blite board stops sending messages once it reaches an “accurate enough position”
The problem seems to be the same as described in this thread (https://www.ardusimple.com/question/simplertk2bheading-xbee-lr-not-enough-rtk-accuracy/). Unfortunately the solution is not stated other than it was due to a misconfiguration. But in my case I am using the given configurations as described above.
The following GitHub issue also seems to be referring to the same problem (https://github.com/ros-agriculture/ublox_f9p/issues/3).
I also have the same problem when using firmware 1.13 and the corresponding configs.
Sometimes the messages from the simpleRTK2Blite board keep coming for longer than usual and if so the setup seems to work as expected, including RTK.
Thanks in advance

 

Ardusimple
Staff replied 1 month ago

The behavior somehow doesn’t match with the behavior you should get with these configurations. A few ideas to check:
1. If you played around with the u-blox 9 configuration view at some point, you might have changed settings that are not overwritten by configuration files. If this is your case, start from zero, upload fw, upload config file, store in flash.
2. Don’t miss the step of uploading the configuration file 2 times to the Lite board.
3. Make sure both antennas have complete view of the sky.
4. Check the hookup guide, with our configuration files, all data to the user is provided by the simpleRTK2B board, the simpleRTK2Blite board has all visualization messages disabled, so it is normal that you don’t receive messages from it if you connect with XBEE+POWER to u-center: https://www.ardusimple.com/simplertk2heading-hookup-guide/
5. Check that the Lite board is not resetting, you can see this from its LEDs.

1 Answers
clive1 answered 1 month ago
Perhaps read the uBlox App Note / White Paper on Moving Base applications and understand the actual requirements and expectations. There’s perhaps half a dozen messages involved.
The GitHub complaint seems to be for a device configured as a Fixed Base, ie one where you run a Survey-In operation, the receiver goes into TIME mode after it has resolved its static location, and is sending 1005 position message.
This is NOT suitable for a Moving-Base device, where two units are bound together, and are Moving, not Static. You need the 4072 message and the MSM7 ones, the MSM4 probably work in te current firmwares, but the things are wired together, so bandwidth really isn’t a massive concern.
https://www.u-blox.com/en/docs/UBX-19009093
 
In the STATIC/TIME mode the receiver will stop outputting RTCM when you move it beyond the threshold you defined for it.

Want to learn more about GPS/RTK?

1. Our engineering team will contact you to solve any questions
2. We will keep you updated about promotions and new product releases
3.You will only hear from us when we have important news, we won’t spam your email