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!

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.

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

@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?

@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.

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

@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.

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

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.

Hi,

What software version are you running? This was an issue we saw commonly on some of our older software versions but fixed in our release of SDK 0.7 with the addition of a new exposure algorithm. You can check the software version on the drone by running voxl-version.

just updated datasheet link to https://www.ovt.com/wp-content/uploads/2022/01/OV7251-PB-v1.9-WEB.pdf
thanks for pointing out

@yhcho61 If you're asking where to plug in the antennas to the Voxl-Cam, then most times the Voxl-Cam has extensions from which to attach the LTE antennas to. If it didn't, you would just need to take the backpack off and thread the antenna through the slot of the backpack and plug them in to the modem. Reattach the backpack and then initialize the modem to use it.

It's possible that the lens has been knocked out of focus. See @Dobry-Kolacz 's write-up here on addressing that issue: https://forum.modalai.com/topic/1362/sentinel-stereo-camera-calibration-inconsistency/4?_=1674364904154

"To adjust the focus on our stereo cameras twist the lens housing clockwise or counterclockwise similarly to how you would on a DSLR lens. Look closely at the stereo cams and you will see 4 flat edges. I recommend using a 6mm wrench to engage 2 of the flat edges; from there you'll be able to rotate and adjust the lens as needed. It is possible to use something like tweezers or small pliers to accomplish this however I recommend against that method because it is too easy for the tool to slip off and end up scratching the lens.

To clean the lens I recommend using a clean microfiber cloth, a lens tissue, or a fresh q-tip"

It is on the roadmap! Hopefully in the next 6 months or so

The VOXL CAM is a development kit for SLAM that comes with a number of reference implementations.

None of the reference implementations require a closed loop.

voxl-qvio-server provides a dead reckoning service based on visual inertial odometry

voxl-mapper provides a mapping and planning service for navigating congested spaces

@Adrian-Hidalgo said in rx-tx from v2 to voxl:

px4_uart_bus": 12, for J11 connection

worked transmitting data now