After a pretty flawless OpenSolo Green Cube upgrade, I am trying to configure an LW20 LIDAR for SLAM mapping and ran into a snag . I indvertenty set the wrong baud rate on Serial2, which leaves the controller Waiting for Solo.
I'm on Green Cube/OpenSolo RC2
I can't connect via Mission Planner or Solex to do the parameter reset or reinstall any firmware.
I can connect to the bird and controller via FTP or shell, but see heartbeat timeouts in python_stderr.
Is there a way to programatically flash 3.5.3 parameters without Mission Planner/Solex, or do I need to reinstall the stock cube and factory reset to 3DRs Solo branch? I'm basically looking for the cleanest way to recover from a bad parameter change
I currently have the patient's chest cavity cracked with access to the Pixhawk USB and IMX6 SD card.
If I have to factory reset to 3DR v 2.4.2, do I need to flash the original Solo/Artoo images to both controller/drone, or just mount the original cub and reset
One more really dumb question: My green cube came with a small piece of black foam. I assume it's for vibrations, but where does it go?
Thanks in advance
I'm on Green Cube/OpenSolo RC2
I can't connect via Mission Planner or Solex to do the parameter reset or reinstall any firmware.
I can connect to the bird and controller via FTP or shell, but see heartbeat timeouts in python_stderr.
Is there a way to programatically flash 3.5.3 parameters without Mission Planner/Solex, or do I need to reinstall the stock cube and factory reset to 3DRs Solo branch? I'm basically looking for the cleanest way to recover from a bad parameter change
I currently have the patient's chest cavity cracked with access to the Pixhawk USB and IMX6 SD card.
If I have to factory reset to 3DR v 2.4.2, do I need to flash the original Solo/Artoo images to both controller/drone, or just mount the original cub and reset
One more really dumb question: My green cube came with a small piece of black foam. I assume it's for vibrations, but where does it go?
Thanks in advance