Zed-f9r-03b IMU data

GPS/GNSS
1

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

03b
03b1576×1016 43.3 KB

Therefore, I would like to ask how to output the IMU data for zed-f9r-03b?

Thank you very much

20251011_config_file.txt (20.6 KB)

2

Is this a sparkfun part or a F9R module you ordered from another source?

3

Hi Jason (@jason011984 ),

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.

I hope this helps,
Paul

4

Thanks Both,

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:

ScreenHunter 2375
ScreenHunter 2375692×576 5.84 KB

Thank you very much.

5

Hi Jason (@jason011984 ),

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.

I hope this helps,
Paul

2 Likes
6

Yes, seems mismatched firmware for ZED-F9P-03B

1 Like
7

I tried to update the firmware to HPS 1.30 and HPS 1.40 which also failed and it has no message output now:

ScreenHunter 2378
ScreenHunter 2378599×488 3.78 KB

Would you provide any idea for updating it?

Thank you very much

8

I replug USB, it output message again, but update firmware always failed.

Thanks

9

Try permutations and combinations of “Enter safeboot before update” and “Send training sequence”. Sometimes you need none, one or both…

I hope this helps,
Paul

1 Like
10

I would concur on the UBX-ESF-MEAS to USB from the configure file, and nothing is jumping out as being incorrect or disabled.

Should be at 2 Hz and it’s not a priority measurement. Would double check if you’re getting any $GxTXT warnings about data buffers, ie “txbuf,alloc”

UART1 is at 115200, but that and UART2 might choke on the 10 Hz priority NMEA messages.

11

Dear Paul,

Safeboot before update and send training sequence already ticked:

image
image1299×993 27.7 KB

Do you have any idea?

Thanks

12

He’s suggesting to un-tick one, then the other, then both….try all combinations of ticked/unticked and see if one works, one combination at a time

1 Like
13

For USB (native) attached I’d not bother with Safe Boot or Training. USB should be baud rate agnostic.

If the firmware is invalid it should fail integrity checking and default to ROM operation.

I might try Chip Erase option.

But generally it’s a fight with settings/options until the upload works/takes.

Try 38400 baud, it should be default for UART1/UART2 in most circumstances. And 9600 when jumpered for SAFEBOOT

1 Like
14

Dear all,

I sucessfully update the firmware by untick both and I got IMU output after firmware updated.

Thanks for all helping.

2 Likes