@keil said in Voxl cam to qgc: voxl-camera-server | Enabled | Not Running | Not Running Hi, It looks like the camera server has encountered an error when trying to start since it's enabled but not running, this is usually due to either a misconfiguration or a hardware issue. Can you show what journalctl -u voxl-camera-server and cat /etc/modalai/voxl-camera-server.conf look like. These are the camera server logs and config file respectively.

@keil, Errors referencing the tf ringbuffer in voxl-mapper typically mean there is an issue getting position data back from the voxl-vision-px4 service. Please read through the user guide before getting started, as you will need a few other services active in order to use voxl-mapper without errors.

Or VOXL System Image 3.8 as mentioned here (https://docs.modalai.com/voxl-suite/#v070) We would like to be up-to-date with the latest updates as the changelogs might fix some problems we are having.

@Alex-Gardner Thank you. I have been trying the same instructions but I did not realize that I was having problems because of my mobile hotspot's name. Just fixed it. Thanks.

Some options are: https://docs.modalai.com/voxl-uvc-server/ https://docs.modalai.com/voxl-libgphoto2/

@Chad-Sweet - thanks, that's my experience with it, I just wanted to know for sure what it was doing. I think in the documentation it would be helpful to be specific about what direction is normal operation mode, or an off-on type label.

Please see the documentation for voxl-camera-server here: https://docs.modalai.com/voxl-camera-server/ There are many examples in our SDK code base of how to consume that data. Here is a good place to look for each of our services: https://gitlab.com/voxl-public/voxl-sdk/services Here is some exact code here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/server/main.cpp#L474 And another example here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tflite-server/-/blob/master/src/main.cpp#L208

@Alex-Gardner Thank for your reply, could you maybe look at my question I still have?

@kitkatSG @LudwigBAH Copying my response from another thread: Here is an example of how to send an AT command to the Quectel modem: echo -ne "AT+QNWPREFCFG=\"mode_pref\",LTE:NR5G\r" | busybox microcom -t 1000 /dev/ttyUSB2 The above gets ran as part of rb5-modem in order to set the network preference to allow both LTE and 5G. Here is a link to the Quectel RM5* series modem AT command manual, you can probably find a relevant AT command to use there: https://www.quectel.com/wp-content/uploads/2021/05/Quectel_RG50xQRM5xxQ_Series_AT_Commands_Manual_V1.2.pdf

Yes there's a lot of interference there, I will change the Wi-Fi mode to softap and give it a further test see if it happen again. Thanks for your response.

I am also facing same issue, tried multiple times yet unable to download, please help

@Sam-Armstrong awesome!

OK got it. If it's not showing up via lsusb, typically we would solve that by rebuilding our open source public facing kernel with some new USB ids (we even give a docker container that is ready to build the kernel) along with instructions on how to safely test the kernel before flashing it. Check it out here: https://docs.modalai.com/voxl2-kernel-build-guide/ I haven't looked around much, but surely if this DJI drone is a development drone, they should also provide such convenience to their developers, so I'd give DJI a shout and see what's up!

VOXL 2 uses apt, and not opkt. Check out the docs here: https://docs.modalai.com/voxl2-platform-release/ You should just need to run apt update apt upgrade

And @tom, also thank you.

Thank you. I could not get video from the uvc device over voxl-streamer, though I could access the test video and the stereo cameras/anything plugged into the MIPI ports. I've had a problem with the newer UVC-server program. I need to check my notes it was a few weeks ago but somehow it wasn't working so I fell back on the ffmpeg due to time limits with the intent of going back to the UVC server application as it's a better solution. I will post a specific issue after looking it over again.

We got maybe 1/10 mile in an urban setting, and have had reliability issues. We placed the antennae as far away from power and more than 2.6" from each other on both transmitter and drone. Any recommendations would be helpful. Thank you.

So it sounds like Dan bought the wrong cameras