@Moderator Thanks for the update and the datasheet. I have not tried building the code since I don't have a reason to until the module itself becomes available and hopefully the code will be out of beta by then. Is there an updated timeline on when this module and its adapters are likely to hit the store?
Posts made by msberk
-
RE: Next-gen TOF sensor specs
-
RE: Next-gen TOF sensor specs
@Eric-Katzfey Thanks for the update, we are anxiously awaiting the data and even more the release of the replacement sensor!
-
RE: Next-gen TOF sensor specs
@Moderator Following up on this, are there any updates on this sensor? We completed a prototype that relies on the last-gen sensor in the fall and this limbo has hung us up on moving forward, or even making additional prototypes due to lack of availability. We're now a couple weeks into 2024 without updates and I'm getting concerned about the fragility of the Modal AI supply chain unless a good roadmap can be provided.
-
Want-to-buy M0040 ToF
All,
We are interested in procuring 2 extra M0040 ToF sensors, and are reaching out to the community since they are not currently available new. If you have old, fully functional stock that you would like to sell, please send me a message at apparel_bismuth0v@icloud.com
Thanks
-
Custom pipe server, client can connect if client starts first but not vice-versa
We have developed a custom MPA server to read from our own external serial sensor and output a point cloud stream through MPA. If we start voxl-vision-hub, voxl-inspect-points, or open Voxl Portal to the sensor page first, then it works as expected. However, if we start our custom server first then begin any of those clients, they do not connect.
Unfortunately we can't share the code here but we followed the normal MPA server opening procedure seen in voxl-camera-server and can't find any differences in our setup and run. Have you seen this issue before and have a suggestion as to a direction we could go for debugging?
Thanks
-
RE: cannot connect usb camera over USB - C adb port
@Moderator Thanks for the clarification, we will not expect a solution to this then.
-
RE: cannot connect usb camera over USB - C adb port
Hi there, just checking in if there have been any updates to this and whether the USBC port can be used for connecting peripherals. We have multiple USB devices and this would greatly simplify our integration.
Thanks
-
Multiple simultaneous VIO solutions, or other redundant localization methods
Was searching around for info on this and found from ~6mos ago: Re: Redundant VIO via AprilTags?
Are there any status updates on this? @Evan-Hertafeld's idea of configuring two simultaneous VIO services is something we've been considering over here, in addition to other redundant feature based localization solutions. Alternately, have you run EKF-SLAM or similar onboard the VOXL or just made maps based on VIO position and voxblox as implied in this article?
-
VOXL ESC Mini with VOXL2
Am I correct that the new ESC mini could be used with the original VOXL 2 if the correct wiring harness would be made? The extra camera lanes of the original VOXL 2 are nice for some of our applications, but being able to consolidate the ESC and power module together would be a great SWaP win even with the original VOXL 2.
Thanks
-
RE: Changing VOXL2 DSP PX4 Orientation
@Eric-Katzfey
Ok, that worked. Thanks!How would you advise setting it up to run at boot? I found the target script here but it's set up differently than a typical Pixhawk board target.
-
Changing VOXL2 DSP PX4 Orientation
Note, this is exact issue is referenced here and never answered, but we have also run into it:
While testing we had the voxl2 mounted with an 180 degrees roll. We were able to change the extrinsics file for qvio, and vision-px4, but when calibrating the sensors with QGroundcontrol the system was unable to calibrate, because the px4 could not discern the right orientation it was in. The px4 was configures to have a roll of 180 degrees, and when calibrating the sensors while the drone was standing on the ground, px4 still thought it was upside down, and after trying to calibrate that orientation, it gave an error saying the z readout was in the wrong direction. Is it possible that there is a setting on the voxl2 that needs to be set when the voxl is mounted upside down?
-
RE: No option for dual TOF sensor on voxl2
Hey there - I am facing a similar issue where I would like to use 3 or 4 ToF sensors to provide nearly complete vision around the drone. Is there a limit to only having 2 ToF sensors at the same time? When I try to run 3 ToFs then I get preview errors upon start of
voxl-camera-server
and it crashes. On1.4.1-M0054-14.1a-perf
I am trying to use the cameras in this ordering:
HW0: ToF
HW1: ToF
HW2: Tracking
HW3: HiRes
HW4: ToFBut when I do that I get an error on either the ToF or the Tracking (depending on the order I arrange them in
voxl-camera-server.conf
about not being able to find the correct preview upon starting the camera server. See configuration below:{ "version": 0.1, "cameras": [{ "name": "tof_backright", "enabled": true, "frame_rate": 5, "type": "pmd-tof", "camera_id": 0 }, { "name": "tof_backleft", "enabled": true, "frame_rate": 5, "type": "pmd-tof", "camera_id": 1 }, { "name": "tracking", "enabled": true, "frame_rate": 30, "type": "ov7251", "camera_id": 2, "ae_desired_msv": 60, "ae_filter_alpha": 0.600000023841858, "ae_ignore_fraction": 0.20000000298023224, "ae_slope": 0.05000000074505806, "ae_exposure_period": 1, "ae_gain_period": 1 }, { "name": "hires", "enabled": true, "frame_rate": 30, "type": "imx214", "camera_id": 3, "preview_width": 640, "preview_height": 480, "snapshot_width": 3840, "snapshot_height": 2160 }, { "name": "tof_front", "enabled": true, "frame_rate": 5, "type": "pmd-tof", "camera_id": 4 }, ] }
-
IMX412 Restock?
Is there any date on when the IMX412 module may come back into stock?
Thanks.