ModalAI Forum

As far as I know no one has ever tried this. I don't think HITL is supported by ardupilot (was in the past) but there may be some sort of Simulation on Hardware (SoH) that you could try to get running on VOXL2. I'm guessing it wouldn't be easy.

Thanks for responding, and if that board should have any other issues, refer to this post in an RMA where we will waive the removal of the IMU from consideration of other failures. Thanks!

MPA to ROS2 can be found here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros2

Hello there, @RoyAzriel said: 2d Lidar 50gram above the gps bridge 2 x light ilumination (front, down - we are flying and dark tunnels next to tracking cameras) props guards the are seen by the tracking camera we have added tof camera, moving from C28 to C29 ( currently its not working or wired in sw), we have changed the extrinsix.conf file in /etc/modalai accordingly. all of those changes did not effect our filght and we had good flight with good vio during the flight If the platform we are discussing has this added elements, it is a custom frame. @RoyAzriel said: we are exploting a tunnel for the first time.we use the poshold durung junction turns to hold in place during turbolance. my answer would be we can live with resets assuming we can accumulate the positions for mapping between the resets. Yes, so that is a mapping/loop closure software responsibility, not VIO. @RoyAzriel said: how do we make sure what you are saying is right and we are passing estimates to px4 ? Check your voxl-vision-hub.conf, if en_vio is set to true, it passes to PX4 as external vision estimates. Also rectified by: @RoyAzriel said: HGT_REF=3 //VIO EKF2_EV_QMIN=16 EKF2_EV_CTRL=15 For now, our PX4 flavour doesn't handle VIO resets gracefully always. We currently have overcome this issue by using VFC. Hence, the reason I suggested that you should try to repeat the same maneuver under VFC position. If you have any questions on how to enable VFC, please feel free to ask. @RoyAzriel said: what should I expect ? Likely more robust performance under resets at the potential cost of manually hover thrust, PID/PD tuning. PS: I wanted to try reproducing your setup here with non-modded Starling2 Max, but I am unable to match your setup without logs

Hi @Eric-Katzfey Thank you for your help! I got it to work on J19 through PX4.

@Raiyan-Alam said in Is there a way to power this Wi-Fi Adapter + Radio using this specific ModalAI UART adapter board?: rfd900x Hi @Raiyan-Alam, My suggestion: keep the Wi-Fi adapter on USB and feed the RFD900X separately. You can pull an extra 5V feed using this power module cable, which splices off a 5V red JST SFHR connector: https://docs.modalai.com/cable-datasheets/#mcbl-00095 Splice from that into the RFD900X's 5V input. For the M0151, don't power the RFD900X off USB but pull it directly from the power module supplying VOXL 2 instead.

@Robbie-McCue Thank you for your feedback I will look into this.

@andrek Thanks for catching it! We just updated flat builds and now it contains m0054-2!

@WesleyHavocAI Thanks for catching it! We just updated flat builds and now it contains m0054-2!

Hi @isagmz That is indeed a cap. It is a 4.7uF 25V 0603 in support of the 5V input rail when sourced by J5. [image: 1782190949170-0a20b27c-498c-4971-be16-f9c02719c08f-image.png] We have so much margin on the 5V power rail, I would not worry about one cap missing. My best advice is to clean up that area to make sure there is no FOD or ripped up pads that can cause a short on that 5V rail from the broken cap, and just keep developing. Let us know if you have any other issues. Thanks!

@PatkirkMartin No, as I said a UART mapped to the applications processor would also work. PX4 has a split architecture on VOXL2 with all flight critical operations happening on the DSP and support functions such as Mavlink, logging, and data manager are on the applications processor. But there is flexibility to move functions between them as needed. So, to match the ELRS receiver with the Mavlink module you could run it on the applications processor instead of the DSP. However, you would need an expansion board that exposes such a connector.

@Engineer123 You can download all the necessary flat build files from our page: [modalai.filecloudonline.com](link url). Go into flat builds folder and download the m0054(154-1) flat build file With regards to actually flashing the flat build, and using modal-qdl repo: Make sure to put the flat build file properly in a correct folder as mentioned by the doc (./qdl/qfil_app/modalai). Make sure the file is unzipped (it should be m0054(154-1)/ all the files, NOT m0054(154-1)/m0054(154-1)/....) Some users have seen a higher qdl success rate when they ran install_dependencies.sh and run.sh with sudo commands. So sudo might work better Confirm that the voxl is in edl mode

Thanks @Eric-Katzfey ! Here is the pinout for the dev board "UART" port that includes i2C_SCL and I2C_SDA. [image: 1778773646212-0cda71eb-2c0f-4b1b-ba91-8b3862fc9763-image.png] The dev board pins 1-6 matching to J19 pins 1-6 We will give the COMPASS_DISBLMSK parameter a shot and see if that works.

@Plingaas02 Regarding odometry in voxl-mavlink-server, it will not modify timestamps on this message. There will be, potentially, VIO odometry messages going to the flight controller from voxl-vision-hub via voxl-mavlink-server and flight controller odometry messages being routed out to the GCS and to the onboard stream. The odometry messages coming from PX4 will have the DSP monotonic timestamp which is different than the Linux monotonic clock and these will drift with respect to each other over time. PX4 runs the timesync service so it can correct the incoming messages from VIO.

What commands did you use to start each one? I would try qshell mb12xx start -X -b 4 -a 0x66 and qshell mb12xx start -X -b 4 -a 0x70

Hi @austin-c Sorry I missed this message somehow. I will email you to kick this off with your team.