I had the issue that (only) my rover module would not boot up, but get stuck with the violet LED and is not reachable. That happens always when the base module is powered up and telemetry is connected. Please tell me if you need logs / vids and I get some. It`s 100% consistent.
The rover will then automatically reset to “single_default” and stopped. Very annoying…
Telemetry is 868MHz jDrones, air baud 57600, serial baud 38400. Rover output serial at 38400 / NMEA for Pixhawk.
Could you please test configuration where you connect only GND and 5V lines to the radio, but do not connect other lines (tx,rx etc…). If it does not boot and shows violet led, than you are having power issues. If it stops booting when TX and RX lines are added than it probably is trying to interpret data coming from the radio as user input during boot.
If you could help us debug this further it will greatly help us provide a fast fix to the issue.
Thank you for the update!
Sorry, I had no time today to do more testing myself.
If that happens to all users then it`s quiet a bug! It took me a long time to figure out why my module sometimes (apperently randomly) was not booting. Testing takes even longer since every possible error takes a minute or to to test.
I write a short warning in the Github wiki. Otherwise more people are going to pull their hair…
Hi @igor.vereninov, I already flash one of my Reach units with the fresh image (ReachImage_v1.1.zip) but when I try to connect my PC to Reach hotspot (reach:a3:36), I receive a message from my PC that password is invalid, also I try from my mobile and the system answer is identically (password is invalid) then could you confirm if is the password to access is
Hi @igor.vereninov after post the message I try to go back with the previus version of the reach image that I downloaded on 14-12-2015, well I made all the flashing procedure… and I got the conection to the reach hotspot and my PC get connection with reach, after that I typed the address 192.168.42.1 and Intels page open and allow me to change the setings to my local network, then I made those changes I wait for wifi connection and It works… Then I reflash to the latest version again but unfortunaltelly no access behaviour still happen.
But here doesnt finish my troubleshooting, then I follow the USB ethernet access procedure on http://docs.emlid.com/reach/software-development/#connecting-to-reach-via-ssh and then @egor.fedorov on the post Reach is not creating Wi-Fi hotspot but I got the following answer when I type:
sudo wpa_cli status
Failed to connect to non-global ctrl_ifname: (null) error: No such file or directory
here the password that I use was reach
So Could you help to me to solved?
Thanks for the debugging work! While flashing the new image, have you waited until led turns green without removing power or you plugged it out right after Intel Flash tool showed “success”? I am trying to find out what we are doing differently.
Hi @igor.vereninov … yes off course I wait till led turns solid green without disconnect the usb cable during all the process…uhm could you guide tome where on which file i can check which password reach is waiting for?