@Alex-Kushleyev @Eric-Katzfey I would appreciate any updates or recommendations regarding the integration and availability of the M0189 VOXL 2 Mini ToF sensor. Thank you for your continued support.

@Samuel-Marchetti Perhaps this can help with the odometry? https://forum.modalai.com/topic/3341/odometry-message/3?_=1782862595827

@Eric-Katzfey Thank you so much this fixed the issue!

Regarding the feature track tab, I recommend upgrading to the latest available SDK, features should show on voxl-portal. The correct overlay is under VIO indeed

@LukeNow This worked, thanks.

@mkriesel It's possible the kernel you're flashing is incorrect. Can you provide the full terminal output of the install?

Hi Cbay, There is a small clock buffer on the edge of the PCB. An RMA can only replace the whole board, not replace a single device. The part to check would be here: [image: 1779297839725-image-1.png]

@Alex-Kushleyev Thanks so much, we have the resistors on the way, will let you know how this goes. Once this has been done, I would assume we would have no issues getting all of the cameras working with OpenVins

@cbay voxl-fpv-px4 is based on voxl-px4 but has some custom tuning code / parameters for our fpv drones that isn't in voxl-px4. So, it's kind of a superset. But there isn't anything related to low level i2c drivers so I have no idea how that could be causing this issue.

@Morten-Nissov , Is it just the specific camera (tracking) not working in a specific port? what if you connect TOF or IMX214 camera there? For your configuration using the M0135 interposer, kernel variant 2.0.0 is the correct one to use. Using kernel 2.0.2 will result in some cameras not working due to different pins used for camera reset (which get properly routed in M0188 and M0195 camera adapter boards for the coax cameras). So i would suggest using the correct kernel 2.0.0, then test one camera at a time and see if you can narrow it down to a camera or port not working. Alex

@Vansh-Aggarwal , sorry for the delay in response. Can you please specify which exact tracking cameras you have and which camera adapters / cables you might already have? Alex

@jeremyrbrown5 We have figured it out. It was the parameters SYS_HAS_MAG and SYS_HAS_GPS. Will be testing autonomous flight tomorrow!

Hello @SKA, Thank you for the details. I can't think of anything right now, but will double check this. I know that there is one potential issue in voxl-camera-server - the SPS header (which is part of the H264 / H265 stream) is only sent by the video encoder once (at the beginning of the stream). I believe that voxl-streamer will cache the SPS packet (which contains things like resolution, etc) and i think when clients connect to voxl-streamer, then it will send that SPS header to the clients. However, if voxl-streamer does not get that first header, it will not be able to forward it to the clients. This is a guess for now, but could be related to the issue that you are seeing. I can look into this issue. Can you please let me know how exactly to set up VLC for 0ms cache? I want to make sure that my test is the same. Also, which version of VLC are you using? Also, i noticed one thing - you are using hires_misp_color stream from camera server, which is not actually encoded, but YUV. Then voxl-streamer will take those YUVs and encode them (using hardware encoder). Is there a reason why you are not using the hires_misp_encoded stream to get H264 directly from camera server and serve it using voxl-streamer without re-encoding? I wonder if in the old SDK you were using _color or _encoded stream? Alex

@jeremyrbrown5 we figured it out, we just changed the name of the model to yolov8n_float16.tflite. Pretty spot on now!

@jeremyrbrown5 , it is possible that overheating VOXL2 cpu could be causing your SoftAP performance slowdown. You can run voxl-inspect-cpu which is a tool that will show you cpu usage, temps and other stats. If the CPU cores reach 95 deg C, the thermal management will slow down the cpu clock, so all the processes will run slower, including SoftAP. Alex

@Robbie-McCue worked, thanks so much!

@jeremyrbrown5 Ah, yes, that'll do it.

@psafi Unfortunately, the Mavlink module is not available on the DSP side. We tried it in the past and there were a lot of issues so we only have it on the apps side. You are welcome to try to add it into the DSP side and see how it goes.