Posts made by claw

@tom That completed successfully, but still doesn't provide adb. Also, lsusb still shows the fastboot device whereas the other Starlings that are working show a qualcom device.

@tom thank you. I'll give that a shot.

@tom yes, 22.04

@tom i did check that initially and again before I loaded it this last time. We have the older version boards.

@tom I tried to install the SDK but it failed.
I did re-read the instructions for unbricking which do say that ADB should be available after installing the flat build. Is there a mechanism for returning the boards for repair?

@tom oh, ok. I thought I'd have adb from the firmware. My mistake. Thanks for the help.

@Moderator here is a screenshot before and after plugging the usb cable in:

I have two VOXL2 boards as parts of Starling drones. They were both unresponsive to ADB so I reinstalled the base firmware using the unbrick procedures. I was able to get a successful result from QDL for both the provisioning and flat build install, however, ADB from my Linux machine does not find the devices. How do I troubleshoot this further?

Thank you

@Zachary-Lowell-0 Thank you for your help and guidance. Is there a way to get the status information like battery voltage using Python?

@Zachary-Lowell-0 No, we're novices and trying to just focus on the Starling. HITL, would be a distraction (unless you say differently) from the task at hand.

@Zachary-Lowell-0 Any luck recreating this?

@teddy-zaremba We were able to pull your suggested version and the deserialization errors are gone. Thank you for your help.

@Zachary-Lowell-0 If you won't be able to help here, is there someone that can? Thanks

Hi @Zachary-Lowell-0 I'm working with @GlennTee on his capstone project as an advisor. We are hoping to use Starlings as infrastructure for algorithm research and development in our labs. In order to sell the idea to our sponsors we'll need basic (working) examples for researchers to get started with that don't require weeks of work to sort through just to establish a baseline. I've seen other posts with similar deserialization errors so I'm hoping that you can help to resolve this easily. We very much appreciate your help and eagerly await direction.
Best Regards,
Bill

@teddy-zaremba Your help is very much appreciated.

Ok, so some of the confusion was related to editing the Python example, but it's actually running the cpp code. With that corrected, it shows all of the expected topics in the "ros2 topic list" and the code sends the arm command to the correct topic according to "ros2 topic echo /uav_4/fmu/in/vehicle_command", however, the Starling doesn't arm. We're trusting the example code as to the data structure that is actually populated and sent to that topic. Is there a reference as to what that should be?

@Kessie Great. Thank you for your help.

@Kessie The good news is that removing the prefix allows the px4 to see the messages and arm. Thank you! The bad news is that we weren't sure this would work so the drone wasn't in our flying lab and we had to physically grab it and disconnect the battery.

We tried powering on the RC controller to push the kill switch, but even though it connected to the receiver, the drone didn't respond to any of the RC controls including the mode and motor disable switches.

How do we operate in offboard mode while preserving the ability to take over manually? Would it have worked if we powered on the drone in manual or position hold and then switched to offboard? Do we launch our code before or after the mode change?

@claw said in unbrick proceedure not finding flat build:

@Nathan-Raras

I bought a high-speed cable and the flat build passed. Thank you for your help. I need to install both the SDK now and migrate to ROS2. Are there plans to update the SDK with ROS2 as the default so that the extra step isn't required?

@Nathan-Raras That's fantastic! Thank you. I will try it tomorrow when I'm back in the lab and let you know how it goes.

@Nathan-Raras BTW, the terminal window displays a "500 internal server error"