Thanks for posting that video Ronan. U-center is not U-ser friendly. I liked seeing the attempted multitasking of riding a motorbike while recording a video looking at your tablet, literally laughing out loud here. It was delightfully honest and I’m glad you left it in the video.
About the 10Hz thing, the reason a lot of the configs using the F9P are set to 8Hz is so that all of the Satellite constellations are available to the F9P. It looks like you’re having a pretty good RTK fix though.
One other tip I’ve picked up is using a ground plane for your antenna, this helps a bunch in improving a consistent RTK fix. Something as simple as a steel paint can lid can make a big difference.
No worries! Glad i could already help someone. Thanks to NorthernFarmer and SjaaKA for the info, Thanks Wilbert, will see how it goes once we have the autosteer in.
I just have downloaded the latest version of u-center and installed the latest firmware on my C099-F9P, that was working so far.
In a second step i have tried to transfer above mentioned config from Andreas, but no chance to get it working. I got a message that the versions are different.
Have also tried to change the generation from 9 to M8/8 but still does not work.
Some idea what to try or do i have to set all settings manually in the end?
I have already tried to do the settings in configuration view but when i click sent, a clock starts in the right top corner but nothing will be saved.
In the end i want to sent the position via USB to the tablett and use the C099 onboard bluetooth module to get NTRIP corrections via Lefebure on the mobile.
But at the moment i am miles away from a running system.
Would be so thankfull if somebody could help me.
Regards
Update: After playing around for hours, i was able to install the Andreas mentioned firmware and than i was also able to transfer the config file.
For me its seams there is some problem with SBAS in the new firmware.
However i was also able to set the latest firmware on the built in BT modul and connect via s-center with my mobile.
Using the u-center integrated Ntrip caster i get a RTK-fix.
To be honest i have no idea about the ports and protocolls.
Maybe someone can give me some advise to get corrections from lefebure on the mobile to the F9P.
Hope this is a common use for people do not want to connect the tablett to internet due to data traffic.
Connect S-center to com. of ODIN-W2
with these parameters
To access the ODIN-W2 CLI use the following default serial settings:
Baud rate: 460800
Serial frame: 8 bits, 1 stop bit, no parity
Flow control: None
Now reset c099-f9p with the button next to the gps antenna.
Now you should see in S-center as in figure 16
now type / help / run and send
now type / bt_visible / run and send
Now search with the cellphone Bluetooth for the ODIN-W2 of the C099-F9P
you should find it and connect it
now open the app. Ntrip Client and try to configure it and send the data to the C099-F9P
When you turn off C099-F9P ODIN-W2 it loses the configuration
to make the configuration permanent you must give the command / mem_store / run 1
To give this command I had to press the testp near the Bluetooth antenna.
test.
Sorry I’m Italian and I use google translator
Hi.
Think i got it working.
Maybe somebody can confirm my settings are correct.
F9P connected via USB, Ntrip via bluetooth.
Changed the baudrate from recommended 640800 to 115200 used in AOG.
Ports
USB
In UBX RCTM3 NMEA
Out UBX RCTM3 NMEA
UART1
In RCTM3
Out UBX RCTM3 NMEA
Messages
GGA, VTG enabled
Rest disabled
Sometimes the NMEA string in AOG shows me some strage symbols instead of numbers.
U-center trial with the various configurations, I also would try the original configuration, GitHub - u-blox/ublox-C099_F9P-uCS (F9P rover config c99.txt) and the NTRIP u-center if reach in a short time and fixed well. You can also use the internal NTRIP aog and use the Bluetooth connection to the hotspot tethering bluetooth phone. to see how you feel better. Hi
Hello,
I connected my GPS receiver to AG
Do you think that the connection is ok ?
Because when I try to upload an configuration file from U-center, it don’t work
I have a RTK base not so far of the farm but what I need to see “RTK” on AG ?
My receiver is ZED F9P with ardusimple RTK2Blite
Hi Jean,
The ZED-F9P is detected by AOG, which means it works (it’s not broken at least). However, the position is refreshed once per second (it’s the “1” next to "GPS single). To use AOG, it needs to be 8 to 10 Hz.
To do so, follow the guide from Andreas : Ublox F9P - Config for rover
If you still have an issue with U-center, we’ll give a look at it.
Hi Valentin
Thanks for your answer.
So now it’s good ?
I have set NMEA to 10Hz
And what do you think about this message in U-center :
Can you send me a configuration file ?
For the Firmware version I think it’s ok because I download it directly from Ublox
As said @m_elias, the message pops because the config file was generated from an older firmware version. It shouldn’t be an issue though.
The configuration in AOG looks okay. What’s weird is that you only have position at a frequency of 2 Hz, while it should be 8 Hz. You used the configuration file suggested by Andreas, right ?
We can use U-center to check the rate parameter. Go to View > Gen 9 configuration view > Advanced configuration > CFG-RATE > CFG-EATE-MEAS. Here the value should be 125 (which means 125 ms between two positions, or a refresh rate of 8 Hz). If it’s not, weird. You can set it manually, then Set in RAM / BBR / Flash, Send config changes. Finally, save the config settings with: Configuration view > cfg > cfg and click sen (as said by Andreas)
Yes, I get that too because of the different firmware versions as I mentioned earlier. This config was shared with me on the Telegram group just a few days ago.simpleRTK2B_FW113_Rover_AOrtner_10Hz-01.txt (20.9 KB)
You might have to look through the settings and make changes according to what you need.
Hi Jean
These buttons are accessible when you modify the ZED-F9P configuration via View > Gen 9 configuration view > Advanced configuration. There, look for any parameter you want (there are a lot of them). For example, to you had an issue with the refresh rate at 2 Hz, which is why I suggested to look at CFG-RATE > CFG-EATE-MEAS. There, you can change the value (for ex. 125) and send the modification to the non-volatile memory of the ZED-F9P. Here is an example view of the panel in U-center taken from the U-Blox guide :
I highlighted the buttons.
At the end, you have to go to Configuration view > cfg > cfg and click send to make the change permanent :
This is only useful if you want to change a specific parameter by yourself. If you want to configure everything at once you can use a configuration file with a .txt extension. Follow the guide of aortner : Ublox F9P - Config for rover. I used the config file given by aortner, which worked well. The config of m_elias should be more up to date though.
When you say without success, what do you mean ? Do you have feedback from the module ? Can you change settings and send them in the config view ?
thanks for the explaination
Now, when i open AOG I have "GPS single : 93 but after few seconds, I have nothing just “GPS single”
Is it a bug or I loss the connection ?
Other thing, when I want to Update firmware with u-center, it don’t work
Because When I go see the version, it’s the old one
Can you send screenshots of the main page and of the NTRIP page ?
Maybe you don’t get NTRIP in AOG, which is why you can’t get rtk fix. When the NTRIP stream is coming in, you should see a little button on the left side of AOG 4.3.10, saying “écoute”, otherwise saying “attente” (in french at least). Is the base station you’re using also made with a ZED-F9P ? How far is it ? It shouldn’t be more than about 50 km away.
About the firmware update issue, do hou have error messages or log files to share ? Did you set the baud rate to 115200 (see here) ? If still stucked, you can also ask on the ArduSimple forums, they have people to address this kind of issue.
El protocolo de salida en el puerto que conecta con ag debe ser solo NMEA.
UBX+NMEA o UBX+RTCM3+NMEA producen la aparicion de simbolos en la cadena de mensajes.
