Hi @shlee853 ,

Although there's a MIPI/CSI2 standard, pinouts can vary and the connectors on the VOXL are semi-specific, so it's not likely to find something off the shelf that can plug in.

If you want to share specs here, perhaps we can point to something.

Thanks!

Hi @Prasad-Pawar ,

Might be better to post QGC queries on their forum: https://discuss.px4.io/

Thanks!

Oh yes, this would absolutely cause a problem. Glad you found it.

You can find just the stereo flex cables here : https://www.modalai.com/collections/accessories/products/voxl-replacement-stereo-flex-cable

Yes,

I've tried tracking->hires->stereo, that does not work. How would it be hardware if each of the cameras can run fine on their own and any combination of the two work at the same time?

Thank you @Chad-Sweet for your reply.

It is glued to hold the focus. Turn gently, but forcefully, and the glue will break

Understood. Thank you again!

@Chad-Sweet Hi Chad, I go further and for the accelerometer calibration I have another issue.

With Rotation None, the QGC see my aircraft on left side instead of level position, and so on.
When I test to arm and take off, it see the vehicle as turn on right side and have failsafe issue.

If I put Rotation = Roll 270 is much better, and I can arm and takeoff (just simulate for now).
Still, I have two positions that are not right, aka it show the vehicle on:

left side instead of noise up right side instead of noise down

I would really appreciate your help to indicate me the right value for the Rotation to well calibrate this sensor.

Thank you!

Hi @Alex-Gardner,

I followed to tune params which you suggested in above, but still am not able get optimal dense pointcloud points. Is there any alternative approach in need to follow or i need combine any other depth sensor along with existing stereo..

No answer from Chad, so I put the problem again here hoping someone can advice me how to advance with this topic.

I took a look at the parameters send over, but there is nothing about the rotation of the board. These params are installed on my board, but the results are the same:

whenever I use it for indoor, I do the accel & gyro calibration with ROTATION-NONE, but I have a roll failure detected once I try to arm and I got the visio for local position whenever I use it for outdoor, I add a M8N GPS with compass, I can't calibrate de compass because the position indicated on the QGC is different as the position of the drone if ROTATION-NONE is selected.

By the modalai doc. is ROTATION-NONE that it should be used. Did I get it correctly, or do I need to select another ROTATION value of the board for calibration?

Thanks!

Voxl and it's software build image use ros indigo, not kinetic. You'll either need to install the indigo version of this package or use an ubuntu 18.04 docker image with ros kinetic installed (and use this on voxl). A sample such image for using kinetic on voxl can be found near the bottom of our downlods page (roskinetic-xenial docker image)

@Zeev-Mindali apq8096

@Adrian-Hidalgo @Eric-Katzfey Thanks for the reply, much appreciated. I'll give that a go.

@janis_blank No, the needed SPI driver for the Lepton that goes in that socket has not yet been created.

voxl-mapper is an example of taking TOF point cloud data and exercising path planning

Thank you for your reply. Its working now

It should be possible to plug in the hires cam to j4 and have frames appear, but vio server and the camera calibrator are not set up to handle the non-fisheye color images, I'd strongly recommend getting a new tracking camera from here

Hi, i think your issue is the board size, it's counting the number of inside corners not the number of squares so it should be 6x8 not 7x9

okay,Thank you