Kind of. I'd just like to know where the origin is of the IMU data reported by the voxl-imu-server MPA service (as quoted above). If it's at the center of one of the specific IMUs then that link is comprehensive to figure out the dimensions. But I haven't been able to find where that origin is. My guess is at the center of the board, but I'd like to confirm.

@Matt-Turi Thanks !!

That is not well supported in PX4 1.12. We are working on a PX4 1.14 port which should be much better supported. We hope to have an early access beta release of that in the end of March or so

In the end the issue was my laptop which was not powerful enough to support the graphics of the 3D visualization.

You need to use a supported camera configuration. You cannot plug different sensors into different locations. C6 and C9 are supported for TOF. https://docs.modalai.com/voxl2-camera-configs/ If different sensors are plugged into different locations, undetermined behavior will occur

@張為超 It worked. I setup my Pc as the master this time, and it worked in that way.

@Kyungtaek-Oh-0 In your first screenshot PX4 is not crashing. It is trying to detect if an external px4io board is connected on one of the serial ports. In this case it is not detecting it (so you see all of those error messages) and it goes on to start a Spektrum RC driver instead. In the second screenshot PX4 is not crashing. The first error about client not being able to reset all parameters is actually mis-classified as an error. It is really just an informational message and can be safely ignored. The script is assuming you have an external Holybro GPS / Magnetometer / LED unit attached and those i2c failure messages are indicating that it isn't detecting the Holybro unit. In the third screenshot PX4 is not crashing either. When you start PX4 for the first time it will look for the standard parameters file in /data/px4/param/parameters. If it does not find that file it will set a bunch of default parameters for you but it will not start the DSP portion of PX4 to do this and so you see those timeout errors which are completely expected for this process. All of this behavior is controlled by the files /usr/bin/voxl-px4 and /etc/modalai/voxl-px4.config. Both of these are bash scripts and are only provided as reference. You can modify these however you want to fit your particular use case.

Thanks, but I was referring if there is something already built in to do this task. IN the docs you guys have a VOXL MPA to ROS. Is this feature still planned?

Hi @dlee Can you please double check SW2. From that photo you posted, it seems as if it may stay be in the "ON" position, which would keep it in "EDL" mode and show up as "QUSB_BULK..." instead of an ADB debug device. Please be sure to follow this step carefully when performing QDL updates: https://docs.modalai.com/voxl2-qdl/ [image: 1676437032805-e7393327-f780-48b8-8b20-4c18a36639ff-image.png] We do not have many HW failures on Voxl2 in the field from routine use, so to have one so soon is surprising. However, if you are confident you are following all instructions and still wish to RMA it, we'll test it again to check for all basic functionality and debug the root cause of the failure, if any, and prompt you for further actions. Thanks!

@modaltb Thanks for your info.

Hi @Jose-Alfredo-Rosas-Cordova , Sorry for the confusion, "native" meaning nothin special "extra" should be needed when compared to desktop Ubuntu, e.g. --> you should be able to follow this: https://docs.docker.com/engine/install/ubuntu/ For VOXL1, we needed to do some special sauce for Docker, but VOXL2 it should work like you're used to on desktop (from my experience).

Have you tried voxl-streamer instead of trying to visualize using voxl-portal? I've not tried this myself but I would next try voxl-streamer.

Hi @Alex-Gardner , @tom, Thanks for your information, I have another question about SUPPORTED SENSOR SETTINGS . I saw IMX412/577 only support 1920X1080@30fps now, may I know what Resolution@FPS will be supported at IMX577 in the future and its schedule

Hi @Vinny , Thanks for your information, I already know current GPIO status.

Hi Vinny, Got it, this schematic will be helpful to me, thank a lot.

Hi Vinny, Got it, very thank.

Hi @Byron_Ch , It's 5A, and the 60 pin B2B 5V output is rated to 3A max so there is plenty of margin for routine 5V use throughout the system.

@Chad-Sweet Thanks Chad.