ModalAI Forum

@Zachary-Lowell-0

Hello! I was able to reinstall 1.3.5 and that somehow fixed it! I am not going to question it lol.

Now I'm trying to find out how to install voxl-mapper and I can't find documentation for it. I am flying the drone inside a test lab. Today when I was flying it around the room, the drone was not mapping anything. The 2D/3D map was blank when I went to plan a point. I think it's blank because I am missing voxl-mapper especially since I have camera-server, vision hub, voxl-px4 and qvio enabled/running. All I have seen is that I have to change "offboard_mode": "trajectory", in order to plan a point on the map and have the drone fly to it.

Is there any documentation on getting voxl-mapper and planning a point?

@Zachary-Lowell-0 @Eric-Katzfey

So i went into the voxl-configure-cameras and saw the list:

• 26 - M0173 with Tof imx412 and dual AR0144
• 27 - M0173 with Tof imx412 and triple AR0144
• 28 - M0173 with Dual IMX412 and Dual AR0144
• 29 - M0173 with TOF dual IMX412 and Dual AR0144
• 30 - M0173 with Dual TOF DUAL IMX412 and dual AR0144
• 36 - M0173 with imx412 and dual AR0144
• 37 - M0173 with Tof imx412, dual AR0144, and boson
• c - use user defined custom camera config in
• q - quit

I selected 26 and 27 then ran voxl-camera-server and it said "ERROR: Found zero cameras connected, need at least one" after each selection.

hmmmm I'm a little lost now

@Zachary-Lowell-0 @Eric-Katzfey

Hello!

So I have updated the starling to VOXL Suite 1.3.5. However when it was done updating it said:

"FAILED TO EXECUTE THE FOLLOWING STEPS: VOXL-CONFIGURE-CAMERAS 6"

Which I temporarily ignored until I checked the web portal camera, the qvio overlay was blank and it was the only option that showed up. The feed said "ERR: CAM_MISSING_STALLED". Also, in QGC it said
"SWITCHING TO POSITION CONTROL IS CURRENTLY NOT POSSIBLE. NO VALID LOCAL POSITION ESTIMATE."

The drone flew fine in manual mode, but its not arming in position mode. How can I fix this?

@Zachary-Lowell-0

Awesome! Thank you! I will do that then!

@Eric-Katzfey

Ok! Will do? How might I go about a fresh installation on a package I already have?

@Eric-Katzfey

Yes!

I had several good flights with 1.3.3. I also had good flights with 1.1.3 as well.

@Eric-Katzfey

Yes the drone operated normal. I got to a point where I would arm it in position mode have it hover 7 feet, and then perform figure eights. In practicing landing it would the floor but the floor in my lab is foam matting which is better than hitting the concrete. To be honest it has 2 or 3 rough landings but after checking after each landing, I nor my colleagues inspected any physical damage. The SDK has been updated 1.3.3. it originally had 1.1.3. I think until I updated it last month.

@Eric-Katzfey

@Eric-Katzfey said in Starling Position and Manual Mode dysfunctional:

You need to keep the throttle all the way down and then slowly increase to takeoff.

Yes but after arming the drone, the drone would no longer receive any input from the controller. That was what I was originally doing but once I and few of my other colleagues gave it try, moving the sticks in every direction, the drone was not responding. Even when we would try to unarm it right stick down the drone was not responding.

@Eric-Katzfey

Hey!

Here is the flight log in manual mode. I also uploaded the videos of the drone in Manual mode they are really short simply because it would flip violently then I had to stop it really quickly. Also on the last attempt at the drone in manual it flipped then 2 of the propellers snapped off. So I have to change those along with the torn one. I hope this helps!

Thanks

@ijones2

Hey!

Here is a link to videos of the drone veering to the left when flying. The new propellers have arrived and I will be replacing all the current ones. I don't think that will fix it though. A colleague of mine checked the amps of the motors and found that the back right motor from the camera was producing lower amps than the others. We hypothesized that the reason the drone kept flipping to the left is because the right motors were overcompensating maybe? I have no clue any advice would be appreciated.

1 - .05 amp Camera right front

2 - .031 amp camera right back

3 - .046 amp camera left back

4 - .045 amp camera left front

Starling Drone flight video: https://photos.app.goo.gl/RxEaN8YGxXUdh1j87

Thanks!

Hello,

My name is Ivy and I am using the Starling drone for research at my university. So, whenever I would arm it in position mode, it would immediately take off and hover 2 inches above the ground-would not get any higher than that-and hover to the left and would not receive any input from the commando 8 controller. Then, if you put it in manual mode and arm the drone, it would rise 2 inches off the ground and do an aggressive flip and crash-again not receiving any input from the controller. I recalibrated the drone through QGC and recalibrated the commando 8 controller and it would still veer to the left. Before, it worked as normal where you arm it and just the propellers would spin and received input from the controller. Before I flew the drone I looked for physical damage to the propellers or motors and there was not any. During the flights where it kept flipping I was checking the propellers and it was fine. Then after many flips and crashes one of the propellers tore a little bit on the front right motor. But the drone was veering to the left and flipping way before the propeller tore. I honestly have no clue how to fix the reason its veering to the left and immediately taking off when armed. I ordered new propellers but I don't think that is the solution for what's going on any help would be great!

Thanks,

Ivy

Here is the tear in the front right propeller

Here is the left side of the drone

@tom

Hey Tom! good news!

I got new cables for the drone now and when I connected the drone it shows up on the lsusb and I am able to run the adb shell. Would I have to unbrick it or because the adb shell is running I would not need to unbrick it? Essentially I'm asking what my next steps should be?

@tom

Hey Tom! i think this is progress?
I tried 3 different USB-C to USB-A cords and the third one gave me " Bus 002 Device 002: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode) "

so I guess it was the cord? Or is it my lab laptop?

I kind of don't know what to make of this??

@tom

Hey Tom!

I have ordered another USB-C to USB-A cable and made sure that it included data transfer and should be here tomorrow. The cable I am currently using has/had worked but I am starting to think it might be the cord. I will find out tomorrow when it arrives and will update you then! If the new cords do not work on my lab laptop, I will try the cords on a different PC and if THAT does not work...

@tom

Hey Tom!

Here'd what I got!

@tom

Hey Tom!

I ran the code and I got a lot of input but I went and scrolled specifically to the usb part and here's what I got

I can send a picture of all the output it's a lot but let me know if that will be helpful.

@ijones2 @tom

@tom

Hey Tom!

I do have the switch flipped on!

@Vinny @tom

Yep! Solid green, no flickering!

I tried the unbrick guide but then I got to this step:

Initiate flash
While in the ufs sub-directory of the image release, run the following qdl command in order to flash the device:

$ sudo qdl --debug --storage ufs --include . prog_firehose_ddr.elf rawprogram_unsparse0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml

and it would say waiting for device and I left that on the screen because it said that the qdl flash will take some time. I had to end the process because it was going on 4+ hours of waiting for device. I restarted it and it was still taking hours. I never got to the point of seeing the completion output.

when I would run this $ lsusb the starling would not show up.

@Vinny