Skip to content

VOXL 2 IO

25 Topics 176 Posts

VOXL 2 I/O (M0065) Support

  • VOXL 2 I/O and GPS

    2
    0 Votes
    2 Posts
    795 Views
    VinnyV
    @Moderator Yes, we can build a custom one and get it listed soon. However, in the meantime, you can start with our MCBL-00061 and add in additional contacts needed for the uBlox module. Here is MCBL-00061: https://docs.modalai.com/cable-datasheets/#mcbl-00061 and a purchase link: https://www.modalai.com/products/mcbl-00061 and then you can follow the tips here to help you add in extra contacts and the shroud for your uBlox module (we are making more updates to this site weekly) https://docs.modalai.com/cable-userguides/ Let us know if this helps!! Thanks
  • px4io failed to start

    6
    0 Votes
    6 Posts
    1k Views
    A
    @Eric-Katzfey I updated to release 0.9 and that solved the topic. Thanks!
  • TBS Crossfire on VOXL 2 IO

    4
    0 Votes
    4 Posts
    1k Views
    modaltbM
    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.
  • PWM ESC control without IO expansion

    2
    0 Votes
    2 Posts
    676 Views
    Chad SweetC
    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/
  • 3D Model VOXL 2 IO

    7
    0 Votes
    7 Posts
    2k Views
    VinnyV
    @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.