@tom lol. Thanks!

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)

@Jeremy-Schofield No, FPV goggles are not supported.

@tom said in Has anyone integrated Starling 2 with Sylvus radios?: M0130 Wonderful! Thank you. That answers my question.

@Sasha-Bagan , actually the noise not too bad, on average under 2m/s/s which is 0.2G, which is considered low. Are you able to create a video of QVIO overlay which can be viewed through voxl-portal? As well as post a px4 log. It is better not to fly in VIO control mode until this is resolved (fly in manual thrust/roll/pitch/yaw mode and collect the log + video).

@tom Got it to bind again. Thank you for your help.

@Alex-Kushleyev I tested it and it works nice (I didn't test the 255 but I expect that should work). I already figured that the frequencies are now multiples of 10Hz with some minimum value (I don't know which one but at least below -p 10 I don't hear the frequency drop anymore). So it ranges up to 2550Hz. And I think you also adjusted the duration to be multiples of 10ms to match with the format of the ESC parameters? Regarding the usage change, I understand if you don't want to create a breaking change. But I think it would be good when the print_usage matches with the actual use. It took me some trial and error to get it working. Maybe also an idea to use -f for the frequency because -p refers to period which is not correct anymore and it is now already changing the functionality of the tone generation (you could even let -p in it to keep it backwards compatible but that maybe makes it unnecessarily complicated). And also good to allow the ESC mapping to go up to 15. For us it is sufficient to use the startup tone. But I played around a little bit with the tone generation and if you use it using the qshell commands you need to wait the duration of the tone to send a new tone (as the qshell command immediately returns and it doesn't accept a command while the sound is still playing) which makes it difficult to get the timing right in playing a tune. I don't know what the end goal should be of this but if it is playing custom tunes using the commands this is something to keep in mind I think. I had some fun trying to play the Imperial March on the ESCs which kind of works but not as smooth as the startup sound can play.

@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

@tom Thank you very much.

@Jetson-Nano , OK it seems we have two parallel threads going. please see my reply to the other thread https://forum.modalai.com/topic/3688/vision-sensors-not-detected-in-voxl2 and test it step by step as I suggested (reducing fps of imx214 camera first, then disabling sensors one by one) Alex

@Eric-Katzfey Thak you for your information. Should I check following DOCS?right? https://docs.modalai.com/voxl2-rc-configs/

Hi @Judoor-0 We have had one other report of something similar where the ToF connector flex comes loose from it's connector located on the M0173 board from high vibe or several hard landings. If you can see whether or not the connector from the M0177 ToF flex looks like it is not planar on the mating M0173 board, try to use something rather benign electrically (like plastic tweezers) and see if you can reseat the connector into the M0173 board. We have a good description of these connections shown here: https://docs.modalai.com/voxl2-coax-camera-bundles/ We are going to add in some additional mechanical support here to make sure this issue does not happen long term, despite high vibe/shock scenarios. If this does not seem to be your problem, please let us know and I'll have to tag someone from the SW team to help you debug further. Thanks!