I'm not 100% sure but I think you can check if you have publish /mavros/companion_process/status with component value 196 correctly, it should be publish by px4 avoidance automatically if your setup is good.

Hey @Steve-Turner, thanks for your answer, I will take a look into it!

@Enstrom1, I would have to direct you to either @RichieRich or @Jeremy-Schmidt. I do know that VIO needs to be able to see contrasts and objects fairly clearly to work at it's best.

Hi Alex, I have noticed following things: When I am using camera-configuration of stereo+tracking, camera server is not stopping after enabling and starting dfs server. When I am using camera-configuration of tof+stereo+tracking, camera server is stopping after enabling and starting dfs server. Tof sensor is working fine when not using dfs server. So, the problem of camera server getting stop with the configuration of tof+stereo+tracking and after enabling and starting dfs server a hardware issue? Does collision prevention works without the depth from stereo server instead just with the depth from tof sensor? Thanks! Anubhav

@Zachary-Lowell, I am sorry for video part. I have linked them respectively again below, 1, 2, and 3, I hope you can see them now. I am using voxl-cam, and the error still arises when I don't open QGC. As you can see in first case, I was not using QGC to implement the MAVSDK example but the error still came.

@Zachary-Lowell, Yes I am leveraging iris_vision in hitl_hiris.world file. Isn't it required to fly drone in VIO mode in simulation considering there is no GPS?

That degradation is voxl-portal reducing the resolution because its data link bandwidth is reduced. If you are using Wifi, can you try better wifi coverage or less interference? If you want unchanged video files for processing, try voxl-logger

Hey @jamiek, I can't give an exact timeline on the next stable voxl-mapper release, but it should be coming very soon with a lot of major improvements! The dev release for mapper does require the dev versions of its dependencies as well, including voxl-portal and voxl-vision-px4 so that may be why you are hitting a white screen with that version.

Hi @Alex-Gardner, The problem is solved and TOF camera is working fine now, previously I have flashed voxl system image 3.8 and now I have again re-flashed it with 3.3 system image. Thanks for your input!

Hi @modaltb, The output of voxl-version is shown below. voxl:~$ voxl-version -------------------------------------------------------------------------------- system-image: 3.8.0 kernel: #1 SMP PREEMPT Tue Apr 26 18:08:39 UTC 2022 3.18.71-perf -------------------------------------------------------------------------------- hw version: VOXL -------------------------------------------------------------------------------- voxl-suite: 0.8.1 0.7.0 -------------------------------------------------------------------------------- No, I am not building code myself, and running standard VOXL SDK. I have flashed new image of voxl because I was getting issue posted here. And the reason for choosing 3.8 system image was because of voxl-mavlink-server which is present in voxl-suite v0.7 and v0.8 and both requires voxl system image 3.8+. Thanks!

I've made great progress. I have finally started getting my brain rapped around this VOXL. Funny it's so complicated. I was able to cut the cord. Remove the usb cable that is. I focused on understanding the VOXL wifi and understanding softap and logging into via wifi, This allowed me to get some imagery to the browser utility. I went down the list of utilities then inspect tools in technical docs on the website. This allowed me to get a bigger picture of the components. I have logged my experience and will post a work flow I follow to get up and running. I'm still working on the 4g connection but reading the VPN stuff and working with the instructions makes more sense now I have gotten the wifi configured . I have it configured but qgc is still not connecting I understand it's hard to ask for technical support with such complexity. I just believe it's worth the investment in time because this is a real solution and the voxl2 will be eaiser to work with now I have a grasp of the voxl. I hope to be flying my custom designed 3d printed drone soon.

@Chad-Sweet I have GPS mounted over VoxlCam hardware with distance of approximately 10 cms. I also tried moving GPS towards backside similar to seeker but still I wasn't able to get fix. I have waited for an hour to get fix but still facing issues. Do I need to configure GPS module by any chance with u-center : https://www.u-blox.com/en/product/u-center ? As far as electromagnetic interference is concerned I don't think there is anything in very close vicinity of GPS.

This rx: 0.000 kB/s instance 2 tells me it's not getting any data from VOXL.... This is the connection that provides that link: [image: 1662047065492-c24bf1be-8000-458a-9380-a633cdb51ab3-image.png] Can you confirm that this connection is in place? You have px4_uart_bus: 5 px4_uart_baudrate: 921600 For voxl-mavlink-server which is correct. 5 = BLSP5 = J12 on VOXL1. It's configured for 921600. Your Flight Core is configured correctly too. So the last thing I would think to do is to probe with an oscilliscope if possible on that connector I pointed out and see if you have bi-directional data.

Hi, The bugfix for this is in VOXL SDK 0.8 and newer. If for some reason you need to change the imu that qvio uses from the default configured by voxl-configure-mpa then you can edit the config file /etc/modalai/voxl-qvio-server.conf manually or use one of the shortcut command line arguments listed in the voxl-configure-qvio --help text such as: voxl-configure-qvio factory_enable_imu0 voxl-configure-qvio factory_enable_imu1 Hope this helps, James

Hi, It looks like your network is the issue here for the blurry image. Voxl-portal will compress images when it detects a poor network connection, and you can see that in the debug stats it's only able to pass through 40% quality image.

@tom I don't see wwan0 interface after doing ifconfig so couldn't ping google.com as well.

@Alex-Gardner Thank you for your help