I am experiencing the same issue with the new TOF in cam config 6, which is also selection 21 in configure-cameras. I cannot get the beta tof sensor to work with the hires and tracking although hires/tracking and tof all work when configured independently. I tried changing the id:0 type to "pmd-tof-liow2" as suggested in the tof datasheet for the config file but that didn't work either. the only config that gets the new beta tof to work for me is #24.
Latest posts made by Gary Holmgren
-
RE: Camera server keep crashing everytime it is launched
-
HiRes camera extrinsics config
Hi, I am setting up the extrinsic on my Voxl 2 with front stereo, hires, and track, but I cannot find any information on the name of the hires sensor in the config file so that it uses the sensor correctly. I have seen someone refer to the name as 'RGB camera,' and some configs show 'lepton.'
Is the Hires sensor normally not used in the extrinsic config as it's not used for odometry? I am using the 4k MSU-M0024 camera for my hires.
-
RE: Stereo Camera Orientation
I am curious what the convention would be for both extrinsics and camera server configs if you have stereo cameras that need to be rotated 90 degrees
-
RE: Tracking camera won’t initialize when configured with stereo
Hi, thank you for the input, I have attempted to reflash the SDK 1.2.0 and then reboot after configuring the voxl to option #03. I disassembled everything to ensure camera MIPIs were connected properly and in the corresponding J6 and J7 connectors where hi-res and tracking flex are indeed on J7 and the front stereo/interposer is on J6.
voxl2:/$ ls /usr/lib/camera/sensormodule
/usr/lib/camera/com.qti.sensormodule.imx214_3.bin
/usr/lib/camera/com.qti.sensormodule.ov7251_2.bin
/usr/lib/camera/com.qti.sensormodule.ov7251_combo_0.bin
/usr/lib/camera/com.qti.sensormodule.ov7251_combo_1.binvoxl2:/$ voxl-camera-server -l
an existing instance of voxl-camera-server found, attempting to stop it
DEBUG: Attempting to open the hal module
DEBUG: SUCCESS: Camera module opened on attempt 0
DEBUG: ----------- Number of cameras: 3DEBUG: Cam idx: 0, Cam slot: 0, Slave Address: 0x00E2, Sensor Id: 0x7750
DEBUG: Cam idx: 1, Cam slot: 2, Slave Address: 0x00E2, Sensor Id: 0x7750
DEBUG: Cam idx: 2, Cam slot: 3, Slave Address: 0x0020, Sensor Id: 0x0214
DEBUG: Note: This list comes from the HAL module and may not be indicative
DEBUG: of configurations that have full pipelinesDEBUG: Number of cameras: 3
Now fore camera config #04 with Hi-Res and Tracking immediately after these tests I will paste the same commands:
voxl2:/$ voxl-camera-server -l
an existing instance of voxl-camera-server found, attempting to stop it
DEBUG: Attempting to open the hal module
DEBUG: SUCCESS: Camera module opened on attempt 0
DEBUG: ----------- Number of cameras: 2DEBUG: Cam idx: 0, Cam slot: 2, Slave Address: 0x00E2, Sensor Id: 0x7750
DEBUG: Cam idx: 1, Cam slot: 3, Slave Address: 0x0020, Sensor Id: 0x0214
DEBUG: Note: This list comes from the HAL module and may not be indicative
DEBUG: of configurations that have full pipelinesDEBUG: Number of cameras: 2
voxl2:/$ ls /usr/lib/camera/sensormodule
/usr/lib/camera/com.qti.sensormodule.imx214_3.bin
/usr/lib/camera/com.qti.sensormodule.ov7251_2.binAs per the Voxl portal, I can see both tracking and hi res working in this config 04, but in camera config 03 I can see only the Hires and stereo showing up.
-
RE: Tracking camera won’t initialize when configured with stereo
@Alex-Kushleyev Hi, I have the dual stereo C11 kit but I am trying it with single stereo, configuration 03 on voxl-configure-cameras
I cannot get the tracking camera to initialize when the stereo is configured simultaneously not matter what I try. It did used to work fine but something must haver been changed. I am on the latest SDK as well.
-
Tracking camera won’t initialize when configured with stereo
Hello, I have the stereo, tracking, and hi res dev kit and all the cameras have been working fine together until just recently. The tracking camera will not appear in the stream and is not recognized at all by the voxl2. When I configure the cameras to only be hi-res and tracking then the tracking is recognized and works fine. Configuring it to tracking and stereo then tracking does not initialize. What could be causing this as I don’t see how that makes any sense.
-
Stereo camera bit rate customization?
Hi, Can the bit rate of stereo cameras be lowered to support longer a MIPI extension?
I am trying to add rear stereo capability to our drone but we cannot run it without using two MIPI extensions and have come to discover that it just won’t work at 30cm of MIPI in the stock configuration. Is it possible to lower the bit rate to allow for the stereo signal to not fail and if so would it still be feasible for object avoidance functionality? When the stereo pair is on the dual extensions it will not function at all but with a single extension it works fine.
-
Stereo cameras not working with 14.5cm extension cable
Hi, I have the c11 dev kit and have assembled everything onto my custom drone all the cameras work, front rear stereo, tracking, and hi-res. Due to the length of my drone, the rear stereo needs a MIPI extension. I have two of the 14.5 cm MIPI extensions but neither works as the camera server fails to start when using either extension. I have never even used these extensions so I am a little confused why this would happen. The stereo works fine when using one smaller 6cm extension off the interposer. What is the absolute maximum MIPI length a stereo pair would support? Any suggestions would be appreciated.
-
RE: Camera server dying with new MIPI extension cables.
I am having this exact issue, the rear stereo pair works fine and the camera server starts up without the extension cable and when booting up with the extension in place(correct pin orientation and cable direction) it fails. I have two brand new unused MIPI cables as well, both dont work...
-
Stereo pair front and rear custom application baseline
Hello, I am using the VOXL 2/FCv2 with front and rear stereo on a custom dev drone, I am curious if the baseline is recommended to be at 80mm for the stereo camera pairs or if it will affect it much if the baseline is closer to 40mm.
I am also curious if the front and rear baselines need to be the same for good results. Ideally, we would like to have high precision on closer objects so that would require a smaller baseline.
I have looked through the camera calibration process in the setup docs and searched the forum here haven't seen any information or elaboration on customizing the baseline from what's used in the m500 flight deck.Any suggestions or feedback would be appreciated!