The rover shut off suddenly during a survey, I assume due to the excessive heat (104°F/40°C). I let it cool off and after restarting, it was unable to open the project or download points. I can download logs, but Survey data seems to be corrupted.
So I started a new project and repeated the survey with a new project. The second project seemed to go normally, however after I was done, I was unable to open or download the points from the second project as well. I used both the Android app and the http endpoint. The dev tools console shows no errors.
Is there a way to access at a minimum the epochs of my shots through some other means than the onboard app, such as SSH, file system, etc.?
In the future, is there a way to monitor the temperature to prevent a catastrophic failure in the field?
Firmware image and ReachView version. v 2.22.3
I have been able to SSH into the receiver, but it’s very unresponsive. The command line is frozen and I haven’t even been able to ls the directory once it’s connected, and the connection is lost after about a minute. I’m concerned that the hardware is permanently damaged.
I also tried sftp and it timeouts after 20 seconds, retires and get:
Long time ago (I guess on firmware v2.14 or something) I also had a corrupted project, but I didn’t investigate it further (data wasn’t that crucial).
What I would try to pull data off: connect with USB-cable to your pc. I think you should be able to run ethernet over usb then and if it’s wifi-issues, it should work better.
If you’re able to log in through ssh, check free space on the device asap. Maybe there is no more free space which will probably result in strange failure/behavior
The wifi connection is working fine because the app updates with satellite data and I can read other projects without any issue. The log shows a ton of free space. But SSH itself is spotty. I’ll try the USB method to rule it out. It would be nice if plugging in the USB opened up the device filesystem like a flash drive, but that didn’t work.