I used zed-f9r-01b for our system which output GPS and IMU data which works properly. Recently, we ordered the same part, but we received zed-f9r-03b this time which I copied the configuration of zed-f9r-01b which doesn’t output IMU data from MEAS message.
I attached the configuration file which works for zed-f9r-01b but not working for zed-f9r-03b. The results of zed-f9r-03b
The ZED-F9R-01B is End-Of-Life. It has been replaced by the -03B which will probably be running newer firmware. I suspect your issue is due to a change in firmware version?
Please check the UBX-MON-VER version information on both your old -01B modules and the new -03B modules.
How are you connecting to the ZED-F9R? Over its built-in USB port? From your config file, I can see that you have ESF-MEAS enabled on USB, but only USB. It is not enabled on UART1, UART2, I2C or SPI.
Firstly, both 01b and 03b modules ordered from sparkfun:
Secondly, we read the data via USB port to our IPC where we are now trying to get the data with u-center, and I found the firmware version are the same for both 01b and 03b:
That is puzzling. HPS 1.00 is very old firmware. I would have expected the -03B to have HPS 1.30 installed.
I suggest upgrading to HPS 1.30 and build your configuration again, starting from the defaults, just in case your old, saved configuration is causing problems.
After further testing, we found our 03b module will stop output GPS data after running for over 10 mins. I compared with the configuration of 01b and I found the ESF-MEAS data output around 20Hz while 01b is 10Hz where I am not sure whether it will affect the module not output GPS data after long run.
Check your UART1 baud rate. Make sure it is high enough to cope with the data rate at 20Hz. Like Clive says, watch out for “$GxTXT warnings about data buffers, ie “txbuf,alloc””. If you see those, you are trying to transmit more data that the baud rate will support.
clive1 is onto something with the UART default baud rate being too low for IMU and other messages. It should be increased accordingly as verified when speaking to a U-blox representative. Just wanted to reiterate on this.
Jason, if you could monitor the UBX-MON-IO message and keep an eye out for TXT errors. If you could record a log via testing to thru time of failure we can relay it back to U-blox and they can check for errors and other prompts once played back.
It is also recommended to utilize UART1 as if too many messages are sent to UART2 it can be taxing to the CPU and cause issues.
I run many testings in these days and I found the GPS module doesn’t output any messages when I run it in my vehicle. I disabled the IMU output so that I could separate the problem for message output and IMU data. Even I disabled the IMU outputs the problem still occurs, and I used U-Center for testing which U-Center will hang up when no messag output. I re-open the U-Center and reconnect the GPS module, it returns error for connecting until I replug the USB cable. The following captured the moment for connect error after re-open U-Center:
Do you guys have any ideas for this problem? I used the same USB cable connect to 01b module which works fine, so I am not sure whether it is configuration problem.
Thanks for your reply, and I solved that problem by updated the firmware to v1.4 with the same hardware configuration.
However, we met another problem after updated to v1.4 is that we cannot save the manual IMU alignment configuration in EEPROM which reset to zero after power up the module. We have called the CFG tp save configuration which worked in previous firmware version.
