Detailed problem description. How does observed behavior differ from the expected one?
Board randomly hangs up after the boot process is over. Flashing yellow led turns off completely, or stops flashing. No power issues. Ssh access is not compromised. All the processes seem to be running without issues. No clue records in logs (although I don’t know if I am actually checking the right place for those)
Your step by step actions.
Connect the battery, wait for boot up completion.
When Led starts flashing yellow, connect CGS over UDP (tried both, Mission Planner and APM Planner)
After a while board hangs up, either with the led switched off or led solid yellow light. ESCs are not happy (lost control signal constant beeping)
GCS tries to reconnect and times out eventually.
Board never comes back online.
RPi3 works fine - no hiccups, nothing.
arducopter processes are alive (htop)
Executing sudo killall -9 arducopter
board reboots and gets back online for awhile. ESCs are now become silent. This time, the period board is alive, seem to be longer than when it boots for the first time.
Eventually it hangs again. Led is off or not flashing - ESCs are beeping…
Scratching a rather bald head in frustration, and starting the process all over again…
Need your help with troubleshooting. Please… I was never able to finish the setup and arm the copter at least once, and I already have this board for about a week.
Same thing if RPi is just powered over usb port.
Here is the photo of the setup as requested (the board is mounted temporary like that, until I am sure it works properly)
I am beginning to regret purchasing this board…
Guys - perhaps you have some tools I could use to further diagnose the issue, when board is in this state. I would at least want to know it this is a hardware related problem or not. What can I do to query the board? All the h/w test are passing when using emlidtool, however, perhaps it gets hot or something, and fails later on?
Maybe I could try to re-flash it? I know it might sound silly but who knows, right?
Please get back to me with suggestions. I really would appreciate the support from community out there…
Difficult to diagnose. Sometimes we have some clues…
If default appear when Pi is connected to 2A external plug or when Navio is powered from Emlid power module, we can rule out this item.
You can try to remove the Navio module and extender, spray some contact fluid on the plugs then reassemble it. If problem is still there, try with another SD card with fresh Emlid image. The latest is fit and I did not have problems with it on my unit.
thanks Marc,
this is not it. Took the trouble cleaning up everything and although the fleemzy Navio2 connector type is a rather poor choice for this board (reliability wise) it seem to me that this is not the cause.
Perhaps I need to flush the board still? How do I do that?
That example only can be executed if APM is not running. pi@navio:~/Navio2/Python $ python ADC.py APM is running. Can't launch the example
Besides, I actually ran all those examples couple of days ago and have not seen any obvious issue.
When motors started to beep, this is the output you’ve asked: pi@navio:~/Navio2/Python $ cat /sys/kernel/rcio/adc/ch1 19316
Disconnecting everything on servo rail, does not fix the problem. After a while, (randomly) board’s LED goes solid or switches off - with, or without servo rail components attached.
sure, Tatiana, no problem (it was one of the first troubleshooting I’ve done with this board anyway).
All disconnected. Powered from micro USB on RPi. Same behaviour. No signs of overheating.
Although, now that you brought this up, I remember when I first plugged the board in, I checked the chips and it felt rather hot to the touch on the top side. Not on a particular chip. I even looked underneath and decided that it might be due to a poor air flow between the RPi and Navio. After that, every time I checked the boards, they were just warm to the touch, (as they are now). Just FYI…
pi@navio:~/Navio2/Python $ sudo emlidtool test 2019-04-18 19:44:37 navio root[905] INFO mpu9250: Passed 2019-04-18 19:44:37 navio root[905] INFO gps: Passed 2019-04-18 19:44:37 navio root[905] INFO lsm9ds1: Passed 2019-04-18 19:44:37 navio root[905] INFO ms5611: Passed 2019-04-18 19:44:37 navio root[905] INFO pwm: Passed 2019-04-18 19:44:37 navio root[905] INFO adc: Passed 2019-04-18 19:44:37 navio root[905] INFO rcio_status_alive: Passed 2019-04-18 19:44:37 navio root[905] INFO rcio_firmware: Passed
