We recently purchased multiple Sparkfun GPS-15136 for use on rovers, but in bench testing we have been unable to produce U-Center log files which are able to be converted to RINEX in Emlid Studio or in RTKConv. We have tried logging at 1 and 10 Hz, multiple different antennas and coax cables, and multiple different GPS-15136 boards, but to no avail. With an older GPS-16481 board, we have been able to produce convertible .ubx files.
We are using U-Center v 25.03 and Emlid Studio v 1.9.
Do you see any satellites in u-center?
Yes. In 1hz mode we consistently see satellites, but in 10hz mode it flickers. Unfortunately I didn’t take note of how many we saw but I believe it was around 12-15
By default, the ZED-F9P module is configured to receive NMEA protocol messages only.
You need to enable the reception of RAW messages.
For example, for the USB port in u-center application in Configuration View:
MSG(Messages) → Message = 02-15 RXM-RAWX
USB → On
Send
MSG(Messages) → Message = 02-13 RXM-SFRBX
USB → On
Send
CFG(Configuration) → Save current configuration
Send
Need to make sure UBX-RXM-RAWX (Observations) and UBX-RXM-SFRBX (Navigation) messages are enabled, and present in the feed.
At higher rates you’ll want to make sure data volume and baud rates align, especially for the lowest bandwidth output. If you get “$GxTXT txbuf,alloc” warnings you’ve got a data log-jam and will be losing messages.
1 Like
Don’t forget to check the firmware is up to date:
Run u-center app
Connect the application to the module:
Click on the menu Receiver->Baudrate->115’200
Click on the menu Reveiver->Connection->COM
Click on the menu View->Messages view
Navigate to UBX → MON → VER (Version)
Please note: the ZED-F9P default UART baud rate is 38400 baud, not 115200.
1 Like
I found that one of our ZED-F9P’s had a current firmware version of HPG-1.13. However, when following Sparkfun’s tutorial to update the firmware ( How to Upgrade Firmware of a u-blox GNSS Receiver - SparkFun Learn), I receive Exit code 2. Full log copied below:
Setup pipes
Process launched
-p STDIO -b 38400:9600:38400 --no-fis 1 -s 1 -t 1 -v 1 “C:\Users\matth\Downloads\UBX_F9_100_HPG151_ZED_F9P.6c43b30ccfed539322eccedfb96ad933.bin”
----------CMD line arguments-----------
Image file: C:\Users\matth\Downloads\UBX_F9_100_HPG151_ZED_F9P.6c43b30ccfed539322eccedfb96ad933.bin
Flash:
Fis: flash.xml
Port: STDIO
Baudrates: 38400/9600/38400
Safeboot: 1
Reset: 1
AutoBaud: 0
Verbose: 1
Erase all: 1
Erase only: 0
Training sequence: 1
Chip erase: 0
Merging FIS: 1
Update RAM: 0
Use USB alt: 0
0.0 u-blox Firmware Update Tool version 24.11
0.0 Updating Firmware ‘C:\Users\matth\Downloads\UBX_F9_100_HPG151_ZED_F9P.6c43b30ccfed539322eccedfb96ad933.bin’ of receiver over ‘STDIO’
0.0 - Opening and buffering image file
0.0 - Verifying image
0.0 - Got an encrypted image with footer info
0.0 - CRC Value : FFEE16BA
0.0 - Footer Version : 0
0.0 - Number of Images : 2
0.0 - Footer Size : 28
0.0 - Image Config Size : 0
0.0 - Image 0 Size : 766056
0.0 - Image 1 Size : 588540
0.0 - Trying to open port STDIO
0.0 - Setting baudrate to 38400
0.3 - Received Version information
0.3 - Receiver currently running SW ‘EXT CORE 1.00 (f10c36)’
0.3 - Receiver HW ‘00190000’, Generation 9.0
0.3 - Sending ROM CRC Poll0.3 ROM CRC: 0x118B2060
0.3 u-blox9 ROM1.02 hardware detected (0x118B2060)
0.3 Getting Port connection to receiver0.4 - Connected port is: USB
0.4 Commanding Safeboot
4.2 - Re-enumerating…
8.2 - Sending training sequence
9.2 - Retry poll
10.2 - Retry poll
11.2 - Retry poll
11.2 ERROR: Version is null
11.2 Firmware Update FAILED
11.2 - Transfer time duration: 11.187778 sec
Firmware Update Utility has unexpectedly terminated
Exit code (2)
Hi @MJS_FRF ,
Please give it another try, using permutations and combinations of the enter safeboot, training sequence and chip erase… Try deselecting all three first.
I hope this helps,
Paul
Unfortunately, I believe the board is now inaccessible, as it does not appear in the COM port dropdown.
I am going to try updating the messages only without the firmware update on another board, and will report back when i get the chance to test outside.
Firmware HPG 1.13 should have been more than capable of outputting UBX-RXM-RAWX/SFRBX for months on end. I’d suggest not updating the firmware until establishing what the issue is.
Now you might need to connect via UART1 using a USB-to-CMOS Serial adapter.
1 Like
I understand how people are trying to be helpful, but it’s a poor practice to introduce yet another potentially confusing step, especially when there’s no specific indication that this step is necessary (e.g., a known firmware bug similar to “postcard” missing message output option completely).
A good practice is to stay on the most likely issue (e.g., missing setting, mismatched baudrate, etc.) until a positive confirmation of successful completion of a certain step is achieved (with a positive or negative result for the entire solution).
Suggesting to try a bunch of different things at the same time is unproductive at best.
1 Like
I didn’t suggest anything. I said DO IT.
Sorry, realized I forgot to update here. I needed to enable the RAWX and SFRBX messages. By enabling these messages and disabling the default NMEA messages I was able to log at 10Hz without data loss.
1 Like