@tom said in Voxl-camera-server crashing in rb5: camera flex for your tracking camera Hi Tom, What would be the best approach to debug this camera flex? Thank you, Best Regards Dominik

@dlee So you shouldn't expect to see a wlan0 as you have no WiFi add-on. But you should expect to see either a usb0 or eth0 network interface from the Microhard modem enumerating. Did you run through the voxl-configure-modem steps for Microhard?

@Subramanian First, check which version of PX4 you are using. Then configure PX4 for indoor flight, params for 1.11 can be found here Then, follow the documentation https://docs.modalai.com/flying-with-vio/

@tiralonghipol You shouldn't have to start dsp_hitl. If you start px4 with the voxl-px4-hitl command then it will be started automatically.

@Eric-Katzfey Oh, do you mean I can see the "RTC time" by timedatectl, but it doesn't mean voxl2 has the RTC? I see. Thank you for your answer.

@hmlow I was flying over the weekend, and saw some inconsistencies as well tbh. The quality of the QVIO was reporting not as high as it was in version 0.9.5 SDK release. I will ask the devs and see what they say. First, I need to compile some logs from voxl-qvio.

resolved

@José-Quintanilla https://adbshell.com/commands/adb-pull

@tom This fix works fine. Thanks!

@Brandon-Wightman Can you upgrade to SDK 0.9.5?

@martongonczy You'll need to use an MPA based client in order to read from the pipe, like in voxl-inspect-cam : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/master/tools/voxl-inspect-cam.c?ref_type=heads what you're seeing is voxl-tflite-server reading from the hires pipe

@Moderator thank you for your help. When I run cmake it throws an error saying that it cannot locate OpenCV, I am using Find the OpenCV package find_package(OpenCV REQUIRED) include_directories( ${OpenCV_INCLUDE_DIRS} ) This is from the OpenCV documentation but it does not work for me. What could be the solution?

@Eric-Katzfey said in Starling infinite loop switching between Position and Manual mode: And if you start voxl-camera-server and then put it into position mode is that okay? Not immediately. The longer the system was in the endlessly switching state the longer it takes for it to recover even after voxl-camera-server is started. Can be in the order of minutes. My guess is that you stopped voxl-camera-server but not some of the other services that depend on it like voxl-qvio-server, voxl-vision-hub, etc. and so they are sending erroneous data to px4 which confuses it. During this weird behavior I have attempted to turn off all other services that might be doing this, which includes the 2 that you have mentioned. The only exception is voxl-mavlink-server which obviously I can't turn it off but after restarting it, it's still weird behavior is still present. You are, obviously, trying some non-standard stuff here. Yes I do understand that. I'm just wondering why it appears only when the WiFi interface is used for communication and not when cellular 5G is used... Also, with respect to the RC, make sure you set RC=EXTERNAL in /etc/modalai/voxl-px4.conf so that the RC drivers are not started needlessly. Ok will do so thanks