I am using a Navigator or with a 128 GB SD card. I am running Rover FW 4.6.2 and blueOS 1.4. I am doing a lot of testing the different serial ports that require a reboot of the Navigator for settings to take effect. Today and yesterday it is taking a long time for the Navigator to boot, up to 15 min after a autopilot restart. I know it takes longer to reboot the entire apparatus (including Raspberry Pi4b). Last week it would boot up in a couple of minutes. Right now I have about half the parameters loaded in QGC, and it has just stalled….The yellow light on the Navigator is solid as well as the green (3.5) and blue (5V) leds. Lights are flashing on the Raspberry Pi, and the ethernet is flashing…Any idea what could be taking so long for a restart?
Hi Ian -
Generally it is very fast to restart only the autopilot process, via the power button in the lower left or on the Autopilot Firmware page. Restarting the entire vehicle should not be necessary, for things like serial port settings the autopilot uses or general autopilot parameters just the autopilot process restart is necessary…
You should be using the latest stable BlueOS - 1.4.2?
If you’re able to share system logs (from the gear in lower left of BlueOS) that would let us see what may be delaying startup…. to resolve, re-flashing the SD card may be the best solution?
Greetings Tony,
Yes, I am using the stable Blue OS. I installed BlueOS on a different SD card to see if that was the problem, and after re-setting all my serial ports:
| Serial Ports | Device | Protocol | Baud | Options | Works? |
|---|---|---|---|---|---|
| Serial 1 | MR72 Rangefinder | (24) | 115200 (115) | ||
| Serial 2 | |||||
| Serial 3 | ArduSimple GPS | GPS (5) | 115200 (115) | 0 | YES |
| Serial 4 | HCU Controller | Mavlink2 (2) | 57600 (57) | 0 | YES |
| Serial 5 | RFD 900 x | Mavlink1 (1) | 57600 (57) | 0 | YES |
| USB | PING SONAR | UDP Bridge 9090 | YES |
I had the same issue with just restarting the Autopilot (not rebooting everything). When I disconnected the RFD 900x telemetry radio the lag went away, so at the moment I am just keeping this unplugged as I continue to setup the Navigator.
Hi @FairweatherIT -
If you can send over those BlueOS system logs, and also include the autopilot .BIN logs, we can try to dig into what’s going wrong here. Thanks!
Hey Tony,
I was going to send you the logs, but I have no BlueOS or autopilot BIN logs available in QGC. I have not armed this vehicle yet as we do not have the RC working yet.
Cheers,
Ian
Hi @FairweatherIT -
That’s because QGC is not the correct place to go to retrieve those logs! The BlueOS interface is used - the gear in the lower left for system logs, and Autopilot Logs menu for .BIN logs.
Got it…I just emailed them to you…
I think all the issues were due to the 5 V BEC. I replaced this and the Navigator boots up normally and no problems with the RFD Serial radio connection.