GNSS failed after Express plus firmware update

GPS/GNSS Enclosed Products
1

kind of panicing right now
updated my express plug to 4.2 and tried to update the F9R but that gave a “Unable to read the receiver and software version. Aborting…”
now on startup i get a GNSS failed message and the position fix is “N/A” and Sat number is “X”

any method to try to get it back to old F9R firmware?

2

Don’t worry, you can always revert.

You updated your ESP32 to RTK Firmware 4.2, and the ZED-F9R to what version? I believe the latest ZED-F9R firmware we support is HPG 1.30. I recommend you use u-center to be sure you have v1.30 loaded on the F9R.

3

i already reverted to 4.1 but still nothing from the F9R, even packet view on u-center is blank

i was trying to upgrade to HPG 1.40 but F9R isnt working at all to let me downgrade back to 1.30

4

image
image355×391 5.08 KB

5

I suspect you’ve got the F9R into a corrupt/fail-safe state. Try these settings:

image
image442×230 6.44 KB

6

thanks that worked
working again and back on 1.30

1 Like
7

Glad to hear it!

Do you know where the release notes are for the HPG 1.40 firmware? I can’t find them on u-blox’s site. What changed from 1.30?

8

think its listed as 1.30 release notes as its dated jan 15 2025 when 1.40 was released

9

That’s a bad typo!

Thanks, this is just what I needed.

10

This is strange. HPS1.40 is supposed to add train support. Release notes for HPS1.30 don’t talk about it (but Interface Description 1.30 contains support for RAIL).

1 Like
11

Alex also mentioned to me that they are now public describing the level-arm support keys (relating antenna and vehicle reference points/frames). I need to go back through some of the u-Blox forum tickets and fish out the people asking.

1 Like
12

Great !!!

I was part of people asking for it. I’ll be able to move my logger away from the centre of my car’s trunk. :rofl:

We will need its support in the SparkFun_u-blox_GNSS_v3. Will write a Feature Request.

1 Like
13

Feature request for lever-arm.

2 Likes
14

Just to follow up here, new versions (v25.03) of uCenter Classic and 2.0 have been posted this week supporting the configuration keys publicly

0x30060020 CFG-SFIMU-IMU2ANT_LA_X
0x30060021 CFG-SFIMU-IMU2ANT_LA_Y
0x30060022 CFG-SFIMU-IMU2ANT_LA_Z

0x10060027 CFG-SFIMU-AUTO_MNTALG_ENA

0x30070012 CFG-SFODO-IMU2VRP_LA_X
0x30070013 CFG-SFODO-IMU2VRP_LA_Y
0x30070014 CFG-SFODO-IMU2VRP_LA_Z

0x30080002 CFG-SFCORE-IMU2CRP_LA_X
0x30080003 CFG-SFCORE-IMU2CRP_LA_Y
0x30080004 CFG-SFCORE-IMU2CRP_LA_Z
1 Like
15

In u-center release note, they are only talking of CFG-SFODO-IMU2VRP and not of CFG-SFCORE-IMU2CRP and CFG-SFIMU-IMU2ANT, that are all about the different reference points. In addition to IMU, antenna and vehicle reference point (middle of rear axle) one can define an additional Configurable reference point (CRP). Will need to install this version. :rofl:

BTW, I’ve update flawlessly my device to firmware 1.40.

1 Like