Unexpected reboot

[Eric-FR]

Express.
RTK_Surveyor_Firmware_v15RC-Aug13

I was doing some testing in static conditions with Lefebure client on my smartphone. Then, I saw in Lefebure "No data" for several seconds followed by GPS, DGPS, FloatRTTK and RTK. This appended several times. Looking at the Express's screen, the Express was restarting each time, first this splash screen, second with "Rover" and back to recording.

The attached picture is the ubx file opened in RTKLib/RTKPlot as a solution. One can see missing data.

If we convert the ubx file to rinex with RTKConv and look at it with RTKPlot as observation data, data are also missing time to time.

Looking at dynamic recording, missing data were also observed (open field road).

UBX file zipped:

SFE_Express_210828_222211.zip

Express settings:

SFE_Express_Settings.txt

Investigation are under way to check if the same problem was present in earlier recording.

[Eric-FR]

Looking at a former recording (August 8) in static condition on my balcony without NTRIP corrections, I can also find missing data time to time:

[nseidle]

Thanks for reporting!

Can you interpret the time scale for me - is there five gaps of data between ~22:27 to ~22:38? So 5 reboots in about 11 minutes?

From your settings file: You have SBAS enabled but QZSS disabled (that's interesting). Why?

You have SFRBX and RAWX enabled and you are logging. You are sending NTRIP over Bluetooth. You have the latest ZED firmware (v1.13).

Is there anything else I should know to try to replicate?

[Eric-FR]

Yes, I had several reboots in a couple of minutes.
I recorded SBAS because because we are receiving EGNOS signal in Europe and I may use it for post-processing.
I'm not supposed to receive QZSS.

After reviewing past data, it seems that the problem appear on August 8th. Looking at my download folder, I downloaded "RTK_Surveyor_Firmware_v15RC-Aug6.bin" on August 7th evening. I found first missing data on August 7th at 22:31. So, I'm quite sure that reboots appear after this firmware update.

[Eric-FR]

Yesterday, I made measurement WITHOUT external power. I still have reboot:

Forward and backward travels with NTRIP corrections.
Static stay on parking without correction nor connexion.

Zoom on the previous figure:

So external powering is not the source of the trouble. NTRIP/BT connexion seems also not to be the problem.

[nseidle]

I also see lots of reboots with RC-Aug13, with RAWX logging, 4Hz updates, and BT connected with NTRIP. While I am not yet certain why Aug13 is such a problematic version, I am having very good stability with Aug23 and Sept2 binaries. I'll keep looking at the file diffs to see if I can see why Aug13 became problematic. In the mean time, please try RC-Sept2.

[nseidle]

I did not know, but should have known there is a Lefebure desktop version. This will allow me to run much longer tests (multi-day) with Bluetooth connected.

[Eric-FR]

I just made a 2 hours trial on my balcony without BT connexion. I still can see missing data. So BT is not the problem.

I think the problem appears with Aug6.

Will make a try with Sept2.

[Eric-FR]

Update to Sept2 done.

Indeed, as I'm no staying in front of the Express display, I'm not sure about what's happening.

Fore sure, quite often (~1 mn?), I can see the SD icon blinking (instead of the progress bar inside).

On Lefebure client, I can see connection lost:

And I didn't see reboot on the Express at the same time. I will look at data later.

[Eric-FR]

Data are also missing at the same time:

[Eric-FR]

I downgraded to firmware 1.4.
I ran a 8 hours test this night with 4 Hz rate and NMEA+RAWX+NAV messages with BT/NTRIP correction. Data are fine. So, the problem is in the v1.5.

[nseidle]

I'm trying hard to reproduce this but I'm having problems. I ran a 4 day log + Lefebure desktop without a single reset. I realize you are logging (and using the logs to detect system resets). Do you have any idea if the system is resetting when then microSD card is not inserted? It would help me pin down where to look.

[Eric-FR]

I did several runs without µSD. Antenna was installed on top a tripod on my balcony, the receiver being just below. No physical interactions during measurements.
Receiver connected with Lefebure on smartphone.
I usually used wifi connection to get NTRIP correction but I also tried with cellular.
I tried with defaults parameters but also adjustment to my usual parameters using wifi configuration.
Soon or later, I observe restart in the reception on smartphone. See attached picture.

At 10:35:28, you see that BT connection with receiver is lost. We get it back several seconds latter.

[nseidle]

Good feedback! Thanks. It's helpful to know the reset occurs regardless of microSD presence.

[pyrog]

It seem an BT issue?
Is it possible to send RTCM stream by WIFI or USB?

[nseidle]

Yes it is possible to send RTCM over USB. WiFi would be far more complicated than BT.