Flight Deck USB not connecting to QGroundControl
-
@modaltb The LED Will flash for a few seconds when the USB is attached and not flash when there is no USB connected so I'm assuming that the board is detecting some sort of connection. Also, we have done nothing else to modify the board or parameter since we have done nothing with the ADB and have not been able to even connect via USB at all unless inserting our blank SD card did something which I doubt.
-
@DillonAllen Sorry I just saw that you posted that above and I missed it.... OK let me think of some options here, if needed I'll email you and we can connect for a screen share.
-
@modaltb Okay, that sounds good thank you!
-
The only thing on the line there are diodes (D59, D60)... otherwise it's a straight connection into the microcontroller.
You could visually inspect D59 and D60, although it's under the board (look fur the U7 silkscreen).
-
@modaltb I visually inspected the board and didn't see anything wrong with any components. I wasn't able to locate U7 on the flight deck board, but I was able to find it on our separate flight core.
-
OK. One last thing and then I'd have to think we may need an RMA to check it out... If the cables and host machine running QGC functions on other Flight Cores, than the remaining item is that connector/connection to the microcontroller...
We can try to see a status of the MAVLink connection on the USB port by connecting over WiFi.
Get the connection up to QGC, and then go to the MAVLink terminal and run
mavlink statuscommand (I think that's what it's called, I don't have HW up right now to verify) and check for the connection on/dev/ttyACM0(this is auto started here) -
@modaltb Sorry for the late reply I got caught up in something, but we ended up managing to get it to connect via usb, but now my next question is that now do we just set up the flight deck just following the VOXL guide then the Flight Core guide?
-
The VOXL Flight Deck should come mainly pre-configured (we calibrate cameras on that assembly, so we configure the computer vision features (VIO by default) to startup out of the box, and Flight Core's internal TELEM port is pre-configured, so you should have a MAVLink connection between the VOXL 'side' and FlightCore 'side'.
You have QGC over WiFi which means you've got voxl-vision-px4 up, so you are good.
Are you using the computer vision features? Most of that is configured through this: https://docs.modalai.com/voxl-vision-px4/
You'll want to update the PX4 params for your particular vehicle, and do the calibration and tuning as normal (I'm not a skilled pilot so that's out of my realm), but the basic setup is captured roughly starts here: https://docs.modalai.com/flight-core-connections/
If you are stuck on particular items feel free to keep 'em coming.
-
@modaltb Now that I am retrying to connect via wifi the VOXL will no longer show up on my list of possible internet connections, I've even checked the two connections on the bottom of the board.
-
@DillonAllen Are you able to connect via. ADB?
-
@tom We have not tried ADB, but we managed to get it connected via a SIK radio. We have calibrated everything and installed the parameters package and now we are just assuming that once collision detection is enabled the drone will be good, the only thing is that I am unable to find the Odometry in the MAVlink inspector. When I run the listener vehicle_visual_odometry command it just returns "Never Published" so I'm concerned I'm not getting VIO Data.
-
@DillonAllen Without WiFi, the only way you'll be able to debug VOXL related things is via. ADB so I would follow this guide: https://docs.modalai.com/setup-adb/ in order to setup ADB on your host computer.
-
This post is deleted!
