Skip to content

Latest SF FW and uBlox FW Breaks Bluetooth #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
cgorski opened this issue Apr 19, 2022 · 5 comments
Closed

Latest SF FW and uBlox FW Breaks Bluetooth #100

cgorski opened this issue Apr 19, 2022 · 5 comments

Comments

@cgorski
Copy link

cgorski commented Apr 19, 2022

Subject of the issue

Upgrading to
RTK Express Firmware: v1.11-Apr 12 2022
ZED-F9P Firmware: HPG 1.30

or

RTK Express Plus Firmware: v1.11-Apr 12 2022
ZED-F9R Firmware: HPS 1.21

Breaks bluetooth
v1.10 works fine

Your workbench

Have an Express and Express+ - v1.11 on Express+ w latest ublox firmware also does not work, as well as does not work on Express

Steps to reproduce

Install versions above

Expected behavior

Use SWMaps on Android or cat /dev/tty.bluetooth - should have data

Actual behavior

No data - sw maps will freeze and cat /dev/tty.bluetoothdevice won't show any data

@cgorski
Copy link
Author

cgorski commented Apr 19, 2022

Additional info - Bluetooth connects both on sw maps kindle device as well as Mac book, but can't get data on either

@nseidle
Copy link
Member

nseidle commented Apr 19, 2022

Thanks for reporting! I am able to get it to fail as well, but not all the time. Seems to be worse after a full system reset. I will get digging and get you a binary shortly.

@nseidle
Copy link
Member

nseidle commented Apr 19, 2022

The error arose because after a factory reset, the ZED's UART gets reset to 38400bps. The ESP32 is expecting 460800 but v1.11 firmware was not correctly re-configuring the ZED. I've added the systems check to correctly detect and configure the ZED's UART. 

Additionally, I was a bit concerned that the changing of the serialTimeout(0) for ESF could have caused some problems. I no longer think it is part of the problem, but I did move the GNSS serial timeout setting to a user reachable debug menu (9) and increased the default from 0ms to 1ms, just in case we need to modify it in the future. 

All is working well for me. Please give v1.12 RC a try and let me know if it fixes the issue.

@cgorski
Copy link
Author

cgorski commented Apr 20, 2022

Awesome! I’m taking the units out for some surveying work tomorrow but once I finish up I’ll give the RC a go.

@nseidle
Copy link
Member

nseidle commented May 11, 2022

I believe this has been fixed. Please re-open if you continue to see problems.

@nseidle nseidle closed this as completed May 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants