Topics created by McMason

@Zachary-Lowell-0 Am I using the wrong serial port? Currently set up with TTYHS0 on J10

f1e6e745-20ab-415b-bb6e-e5a1074ab810-image.png

In the guide its showing the QUPs on J19 being connected

9f406335-3fc6-45cc-a78e-43062a6c2d7b-image.png

Hi @McMason ,

What's your hardware setup like, image sensor (imx214/412/678?) and flex extensions (none, short M0074, long M0036) and port being used? J7/J8?

System image version 1.4.1 or 1.5.5? https://docs.modalai.com/voxl2-system-image/#changelog

And what about your setup in /etc/modalai/voxl-camera-server.conf ?

Lots of times intermittencies like this are flex related (e.g. length, or kinks or connection), in general we have this setup the IMX214 setup in our Sentinel drone which is running continuously so it's not expected behaviour to crash!

Hi @modaltb, we are having that issue on a certain VOXL2 board. We had an extra Voxl2 we put in and the issue isnt there as expected. Once i get a free moment ill dig back into the problem board. as of now its ok.

@McMason Can you please guide me on how to solve this issue?

I am having a similar problem with the Sentinel drone, when I run the voxl-mavlink-server -r command, there is no main loop being triggered.

Hence, I am also unable to see the drone connected to the QGround controller.

Hello @McMason ,
Have you successfully connected VOXL2 and NV Trip2? Currently, I am using Ethernet and the Microhard Add-on board to connect VOXL2 and NV Trip2, and I can confirm successful connection using the ping command. However, I am unable to perform image transmission. Do you have any suggestions on how to resolve this issue?

Hi @Chase-Riley
Your best bet might be to start a new thread, that will help ensure you get more eyes on it for the best person on our side to help you along!
Thanks!

Hi @modaltb Travis, it took me a bit to have time to get back to this, but I've confirmed the problem. There was a short between input and ground in the small 4-pin GH connector I was using to connect to the VOXL2 IO board. Given I just found that laying around, I should have caught this earlier. Thanks for your help! I can confirm that the PX4IO app does see the R9SX input now. I'll also refer to your other post soon about trying to setup the Graupner GR-16 as I'll be moving to that this summer.

@McMason That is how we usually calibrate our sensors, you should have no issue doing so. I will send your camera calibration files to the email you have registered with the forum.

MPA Config took care of it.

Hi @tom,
Thank you for your help, I got it going and is now back to a usable state!

Thank you @Chad-Sweet. Have you seen any issues with connecting a graupner receiver output to pin11(uart rx) on J19? Just looking for RC input without taking up more space with the IO board, and due to specifics we cant use certain radios. I cant find too much data on if the receiver has an inverted signal like the FrSky does.