ModalAI Forum

@minhthinh The params are in our voxl-px4-params repo. For example: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/blob/master/params/v1.13/Platforms/M500_FCV2.params?ref_type=heads

@tom thank you for your assistance. I'll do that.

@Zachary-Lowell-0 thanks for the help. it works now, but it says "no offboard signal". do you have any idea why? [image: 1731370641982-offboard1.png] [image: 1731370647905-offboard.png]

this should be helpful as well : https://docs.modalai.com/voxl-serial-io/ , which points to a uart loop back test app for DSP-based UART ports (https://gitlab.com/voxl-public/libvoxl_io/blob/master/lib/apps/voxl-uart-loopback.c)

@Samuel-Bryan said in Tracking Camera Stream: I need to stream it through an rtsp python script Can you please clarify the statement above? Are you trying to use your own python script to receive images from the tracking camera and send it using rtsp protocol?

@Samuel-Bryan , you may have an older version of the voxl-mpa-tools package. You can try upgrading it from here (you may also need to upgrade libmodal-pipe to 2.10.1). Alex

@Samuel-Bryan To test if it's connected to the internet, try pinging a website like: ping google.com If connected you'll see something like this: ~ ping google.com ok | 09:39:00 AM PING google.com (142.250.217.142) 56(84) bytes of data. 64 bytes from lax31s19-in-f14.1e100.net (142.250.217.142): icmp_seq=1 ttl=56 time=5.12 ms 64 bytes from lax31s19-in-f14.1e100.net (142.250.217.142): icmp_seq=2 ttl=56 time=5.65 ms 64 bytes from lax31s19-in-f14.1e100.net (142.250.217.142): icmp_seq=3 ttl=56 time=5.41 ms 64 bytes from lax31s19-in-f14.1e100.net (142.250.217.142): icmp_seq=4 ttl=56 time=4.83 ms ^C --- google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 4.830/5.253/5.653/0.309 ms ~ See here for info on connecting your VOXL to the internet: https://docs.modalai.com/voxl-wifi-setup/#configuration-and-connection

@Eric-Katzfey I am using SoftAP mode in Wifi.

@boga , Can you please double check the following: amount of free space in the /data partition: df | grep data check the write speed to the data partition : dd if=/dev/urandom of=/data/test.bin bs=1M count=1024 (this will write a test file of size 1GB). For example, using voxl2 i result i got was (on VOXL1 it will be a bit slower): #set cpu mode to perf voxl-set-cpu-mode perf #perform the write test using randomly generated data (may be limited by speed of /dev/urandom) voxl2:/data$ dd if=/dev/urandom of=/data/test.bin bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 2.85171 s, 377 MB/s (you can / should remove /data/test.bin after the test to free up the space) Alex

@tom @spitkowsky I'm wondering if this may be a HW issue on the VOXL board. Possible the USB or the USB VBUS control is now no longer working correctly, thus not allowing the MH modem USB hub to enumerate (eth0 never seems to be detected, implying a USB hub path issue, but on the VOXL side since the MH HW is known good on another system). https://docs.modalai.com/expansion-design-guide/#modalai-usb-hub-example This may be cause for an RMA.

@spitkowsky For others who are seeing similar issues, the magnetometer rotation isn't being specified correctly in the newer SDK. The rotation should be set to the value 10. If you are seeing these issues try setting the CAL_MAG0_ROT parameter to 10.

@Samuel-Bryan There are some examples here: https://docs.modalai.com/mpa-camera-interface/#sending-commands-back-to-the-server

Thank you for the info! After messing with it some more, I think it might have to do with the batteries I am using. Because the drone is currently turned on and my laptop is connected to the drone's wifi, but it is no longer connecting to QGC, even with a micro USB connection too. The battery I am using is a "14.8V, 45C, 4S1P, 3300, 4 Cell battery". And it will only read on the QGC when it is around 30-50%. Any ideas what I should try next?

Following up here. We upgraded to a voxl2 and stopped since this error. we think it might have been an issue with voxl flight on the newest SDK for auto exposure