I just want to start by sending a big thanks to the modalai dev team for your great support over the last year. Special thanks to @Alex-Gardner who went above and beyond.

I spent most of the last year putting a system together with your voxl m500 drone to perform autonomous visual inspections, fully onboard with no offboard processes. I just wanted to share the final result with you all. Please let me know if there is a blog or anywhere else where you may like this posted

A few details...the snapdragon is performing the flight control and has the information pipeline (all through the great modal pipe architecture). The snapdragon sends an rtsp stream from the hires camera to a Jetson NX, mounted to the bottom of the drone. The jetson is running inference on the video stream from the snapdragon, and sends detection information back. This is then used to alter the path of the drone and snap a hires photo.

Thanks again to the ModalAI dev team!

https://www.youtube.com/watch?v=nTiyL_NfBCo

I just want to start by sending a big thanks to the modalai dev team for your great support over the last year. Special thanks to @Alex-Gardner who went above and beyond.

I spent most of the last year putting a system together with your voxl m500 drone to perform autonomous visual inspections, fully onboard with no offboard processes. I just wanted to share the final result with you all. Please let me know if there is a blog or anywhere else where you may like this posted

A few details...the snapdragon is performing the flight control and has the information pipeline (all through the great modal pipe architecture). The snapdragon sends an rtsp stream from the hires camera to a Jetson NX, mounted to the bottom of the drone. The jetson is running inference on the video stream from the snapdragon, and sends detection information back. This is then used to alter the path of the drone and snap a hires photo.

Thanks again to the ModalAI dev team!

https://www.youtube.com/watch?v=nTiyL_NfBCo

Hi all,

I was wondering if there was anything already in place to log the battery information from voxl-inspect-battery to a file. There doesn't seem to be any options to do something like this listed under the -h help flag like I've noticed with a few of your other packages.

Cheers,

Pawel

@m4v3r said in Turn off ESC Beep:

e

Oh that's great news! Thanks a bunch, I'll have to try this out

Thanks for the ideas, I now have options passed the noise cancelling headphones

Hi all,

I was wondering if there was any way of turning off the ESC beeping that turns on after 10 minutes of standby. My current solution is power cycling the voxl through QGroundControl, but this isn't ideal during development.

Cheers,

Pawel

Thanks @Alex-Gardner that did the trick. I can get the cam-server and rtsp server running at the same time now. Is there a way to get voxl-rtsp to run at aspect ratios other than 3:4? When I try to change it I keep getting the following error

/ # voxl-rtsp -s 832x832
voxl-rtsp version 1.0.4
Setting resolution: 832x832
Connected
Started camera 0
Created session
Video track created
in setGainAndExposure: Unable to get camera parameters
rtsp://192.168.86.215:8900/live
Camera Control FIFO starting: /dev/camera0_control
Unable to connect to start session: -19
Unable to delete video track: -19

If I maintain the 3:4 AR it works as expected.

HI @Alex-Kushleyev ,

Thanks for the advice, using the voxl-rtsp server to a specified port and using adb port forwarding worked quite nicely. How would you recommend disabling the hires camera in the voxl-camera-server? I removed it from the config and changed my tflite-server to use the stereo-cameras, but the camera-server throws an error about the J2 port missing.
ERROR: object missing port_J2

Cheers,

Pawel

Is there a way to access the h.264 stream instead of the yuv images from the 4k camera? I am working on sending a video stream from the 4k camera offboard to a jetson NX over the adb port (previous forum post) at a resolution of 832x832. I have a simple message being sent from a server on the voxl to a client on the jetson over the adb port with some adb port forwarding commands. I am working through the process of implementing the h.264 encoding / decoding, however I notice that there is an h264 stream used in voxl-rtsp. Unfortunately I require the voxl-camera-server as I am using vvpx4, and @Alex-Kushleyev mentioned in a prior post of mine that you cannot run the voxl-camera-server and voxl-rtsp at the same time. I am still working my way through the voxl-rtsp code to sort out where the h264 stream is created / accessible from, as I am trying to sort out if there is a way to access the h264 stream without voxl-rtsp, or if that is something created in that service from the raw YUV images.

Thanks, I just wanted to check if I was totally off track. I'll let you know how it goes, the potential of over the air adb updates are very tantalizing

Thanks for the details Eric. Just to make sure I'm following for the adb scenario, would the flow be something like...

-> C application on voxl forwards h264 stream to port x
-> jetson, connected over adb, would run something along the lines of adb forward tcp:x tcp:y
which would forward port x on the voxl to port y on the jetson
-> C or python application on the jetson reads the h264 stream from port y

Cheers