Resolved

It is likely that driver is not supported. You may need to add it to the VOXL 2 PX4 build if you want to use the integrated flight controller. It may be easier to use an external flight controller if you want to use a broader set of inputs https://docs.modalai.com/voxl-px4-developer-guide/

@Chad-Sweet I have used both dev as well stable packages "name": "hires", "enabled": true, "frame_rate": 30, "type": "imx214", "camera_id": 2, "preview_width": 640, "preview_height": 480, "record_width": 1920, "record_height": 1080, "snapshot_width": 3840, "snapshot_height": 2160, "ae_mode": "isp" In the camera configuration file type of camera is "imx214". Is it correct?

@Chad-Sweet any suggestion?

@modaltb Sorry for the delay in replying. apt-get install jq, worked and fixed the problem. I am about to update the system image. Many thanks.

@Vinny Side note: I'm slicing off the little retention nubs on every DF13 connector I own today. I would suggest anyone planning on doing a lot of detachment-insertions consider this. I really don't think DF13's were ever meant for a lot of In-Out especially in awkward placements. Long live GH 1.25's..

Hi @liftedsystems I just saw this now.. sorry for our delays on this... We respond better when you start a new thread because we ALL get notified of it internally ... Thread replies are on a "best effort" basis to check so we miss some.... but if you wish to do so, please just tag us using the "@" like you did to get Chad and we will see that at a higher level too, but new threads are always the best! Thanks, and I hope Travis gave you the info you were hoping for!!

Are the sensors mounted rigidly on the same plane, facing exactly the same direction? Can you make sure they are both well in focus?

Hi @jonathankampia, After running voxl-mpa-to-ros, you should see the /tflite_data and /tflite topics created as they just mirror the existing pipe names from the tflite-server. I am not sure what you are referencing with the tflite_detections topic, but if you could share the output of voxl-version, voxl-list-pipes, as well as a rostopic list with the two services running I can help debug.

@bendraper in other words, what factors/scripts affect the generation of that conf file?

Hi @Anubhav , Docker should natively work on VOXL2... so the voxl-configure-docker-support shouldn't be used at all on VOXL2.... Should be able to use this directly: https://docs.docker.com/engine/install/ubuntu/ If VOXL2 isn't booting... you can reflash with the platform release, and please just don't run voxl-configure-docker-support (and we need to fix this script to not run on VOXL2.....) To reflash: https://docs.modalai.com/platform-releases/#install

@Adrian-Hidalgo I redesigned the mounting piece for the cameras, used new refocused cameras, and fixed some errors in my general camera extrinsics file (although I'm not sure that last one is related)

It seems no data has been received by modal_esc module, but it also seems that the ESCs have not been armed yet. Let's try to query the individual ESC version information: modalai_esc -i 0 version and modalai_esc -i 0 version-ext (you can replace -i 0 with ESC ID 0..3) These commands will explicitly send a request to each ESC and get information about its version and should print. version-ext is the extended version information, but basic version command should be sufficient for checking communication.

@Dobry-Kolacz I think I'm getting close. Im pretty consistently getting a reprojection error ~0.6 at this point so still have yet to successfully calibrate stereo extrinsics. Tried new stereo cams, refocusing, different lighting, different scales of checkerboards, but can't get sub 0.5

Hi Tamas, it seems like something you could add to voxl-mpa-to-ros?

After some digging, I came across the qtiqmmfsrc GStreamer element. If I use this to get the video stream at 4000x3000 (video/x-raw, format=NV12), I get the same distortion shown above. However, if I request the H.264 stream (video/x-h264, format=NV12), I get a clear picture. Below are the pipelines that I tested using the IMX412. # Distorted Output gst-launch-1.0 -e qtiqmmfsrc name=qmmf ! video/x-raw,format=NV12,width=4000,height=3000,framerate=30/1 ! \ omxh264enc control-rate=2 target-bitrate=6000000 ! h264parse ! \ matroskamux ! filesink location=43_raw.mkv # Good Output gst-launch-1.0 -e qtiqmmfsrc name=qmmf ! video/x-h264,format=NV12,width=4000,height=3000,framerate=30/1 ! \ h264parse ! \ matroskamux ! filesink location=43_h264.mkv On a side note, the video's white balance from qtiqmmfsrc is better than when requesting images through voxl-camera-server. The video is extremely warm when delivered through voxl-camera-server, though I admit that I never looked into the configuration for this. In any case, it looks like this is maybe an issue with Qualcomm's libs. I haven't yet looked further into the voxl-camera-server source, though I don't suppose there's been an update to the qmmfsrc or related libs that can be updated on the VOXL2, is there?