F9P detected as u-blox_AG_-_www.u-blox.com_u-blox_GNSS_receiver when using only "detect"

[Stefal]

Describe the bug When detecting the receiver from the GUI, a usb connected F9P is detected as u-blox_AG_-_www.u-blox.com_u-blox_GNSS_receiver and the receiver format isn't set

To Reproduce Steps to reproduce the behavior:

1. Go to 'SETTINGS'
2. Click on 'DETECT'
3. Accept the result
4. See error

Expected behavior The receiver should be detected as U-Blox_F9P, and receiver format set to ubx

Software/Hardware (please complete the following information):

• RTKBase release number 2.6.3
• OS: Armbian 64bits
• SBC Orange Pi Zero
• GNSS Device: Ublox F9P
• Connection type: usb

Additional context The behavior is ok with detect&configure

[MikeJWillis]

I am having the same issue. RTKBase release 2.6.3 OS Ubunut Jammy Server SBC Orange PI 3B GNSS: Tried Ublox F9R (does not configure) and UBlox F9P - does configure, but produces no output. Connection: usb

Can detect receiver as above. F9R Does not allow configuration . F9P allows configuration, but does not track satellites.

[PavaniVitor]

Any news on this? I'm facing the same issue with multiple F9P units.

[Stefal]

Any news on this? I'm facing the same issue with multiple F9P units.

With "Detect & Configure" or only with "Detect" ?

[PavaniVitor]

With "Detect & Configure" or only with "Detect" ?

I was having connection issues using the 2.0 usb port from the odroid SBC. solved after changing to 3.0 ports, detect & configure works just fine now.

I'm using F9P-EVK receivers if anyone is interested.

Sorry about the fuzz.