ModalAI Forum

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.

Hi @Roy-Wood , Natively, the RC and PX4IO drivers are looking at UART on J19. The ESC driver natively looks to J18 (E in the diagram). We've not tried RC on that UART and it's not "easily" configurable through a PX4 param, although I'm pretty sure modifying code could get it going... let me know if you are opening the hood up to the code base and I can point ya towards areas.

@Jetson-Nano, can you please clarify what exactly you are asking?

I assume you are referring to VOXL 2? If so, there is no PWM output on VOXL 2 as the Snapdragon processor onboard does not have PWM output. If you already have another flight controller you can use VOXL 2 as the companion computer to that flight controller https://docs.modalai.com/voxl2-external-flight-controller/

@Eloi This is great feedback and thanks so much for sharing with our community. Your experience and willingness to share with us is very much appreciated, so thanks!!! We will definitely NOT delete this post I know our Mech Engineers have their nuances with SolidWorks, and I think keeping models in separate directories, and also local hard-drives (not in a cloud location) makes sense since there is a lot of overlap with individual parts and DSS likes fast un-metered access to data as far as I know. Glad you got it all worked out, and let us know if you need anything else.