@psafi ,

There was a libmodal-pipe library update earlier this week, so if you have updated that library on your VOXL2, then any other library or app (which uses libmodal-pipe) that you deploy to that VOXL2 needs to be built against the same version of libmodal-pipe.

So if you want use the latest dev version, you would update the drone.

make sure you are using dev for apt sources:
in /etc/apt/sources.list.d/modalai.list:

deb [trusted=yes] http://voxl-packages.modalai.com/ ./dists/qrb5165/dev/binary-arm64/

then update libmodal-pipe on VOXL2, this should also update any other packages that depend on it.

apt update apt install libmodal-pipe

When building your application using voxl-cross docker, make sure you run the following in order to get the latest deps from dev:

./install_build_deps.sh qrb5165 dev

Most of the time you can get away not doing this, but this time there was an interface change in libmodal-pipe, so a mismatch occurred.

Alex

Hi @smiley
We don't offer longer ones and we have not tested them.
Sorry I can't be of much more help here.

Usually in this situation, I suggest our customers to go and challenge their Mechanical and Industrial Design Engineers to better constraint image sensor placement in the drone given these fundamental constraints.

@Eric-Katzfey got it, thank you for the info.

@tom Thank you for the support.

@Alex-Kushleyev Thank you for sharing the files and the support, I was able to flip the video by using the flip file for camera 1. Now it is working fine.

@Tutu-Wen

No, stinger has no GPS Yes Yes, all compute is onboard and the VOXL SDK is open source:https://gitlab.com/voxl-public/voxl-sdk

@Huynh-Gremsy No, there is no way to do that. There is no display output

@Muhammad-Faraz We do have PX4 HITL: https://docs.modalai.com/voxl2-PX4-hitl/

@Eric-Katzfey Thanks for the reply. You’ve correctly identified my problem.
Due to time constraints, I need to deploy my system soon. I hope to have a solution that works on your hardware or to wait for the Ubuntu 20 update.

@aheyne ,

Thank you for the update.

Please note that our standard configuration 50 has the IMX664 camera in slot 3, as shown in the link below ( J7 upper = slot ID 3). Since it is the only camera connected in this config, it would still show up as ID 0 in the voxl-camera-server.conf file.

https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/misc_files/usr/share/modalai/voxl-camera-server/standard_configs/platform_config_2/50 - MVX-T0001 voxl2 mini hires imx664

Also, i think you meant that you copied the com.qti.sensormodule.imx664_1.bin file, not 3 after running voxl-configure-cameras.

The extra sensormodule file for slot number 3 in this case does not do anything because there is no camera actually connected in slot 3, so the camera pipeline will just try to probe the camera in this slot and will fail and move on. In general. I would recommend having only the sensormodule files that you are actually using in /usr/lib/camera in order to avoid any confusion in the future.

Also, thank you for letting me know what happened when you connected the camera to the wrong ucoax port (J1L, which is designed for a Boson camera, which needs 5V). Yes, the camera shorted the 5V rail to ground inside the camera, but it seems it has survived? Don't try it again 🙂

By the way, did you have to update the kernel?

Is there anything else I can help you with, so you can get the most use of the IMX664 camera?

Alex

@Aaron-Porter Most likely jump is due to NTP aligning the clock. The other device that is time stamping using real time clock really should move to monotonic.

@tomverstappen I am unable to recreate the issue with a starling running 1.5.0 - the output from voxl-vision-hub shows the relative coordinate frame from the tag relative to the camera and was able to get the drone to offset correctly.

Are there any logs you can paste in here or video?

@Alex-Kushleyev

Thanks for the explanation — I now understand how to use the TOF sensor.
I’ll use the ROS point cloud directly for my research.

Hi @czarsimon
J10 pin 9 is a Voltage for Spektrum Style RC modules that require a power ON/OFF/ON sequence to bind.
GPIO_159 is the GPIO that enables this feature. If held static ON, this is a reverse protected 3.3V pin, up to 1A of support.

6ca43c92-9147-4f70-836d-093ca968c2a7-image.png
83491011-d3ab-4314-8704-5bb92ddfe9d3-image.png

All Board-to-Cable (JST's) connectors are on the DSP since they are purpose designed for Flight Control features.
You'll need to use the Board-to-Board connectors (J3 and J5) for Apps GPIOs.

https://docs.modalai.com/voxl2-connectors/#j3---legacy-board-to-board-connector-b2b

https://docs.modalai.com/voxl2-connectors/#j5---high-speed-board-to-board-connector-hsb2b

Hope this helps!

@Moderator thank you for the recommendation. I will try out this.

@jonathankampia There is some relevant info here: https://docs.modalai.com/voxl2-external-flight-controller/
M0062 is more rare of a product for us so isn't listed there but you can find more info here: https://docs.modalai.com/m0062-datasheet/#j9---2w-uart--i2c-port

We have updated the M0129 in the past few months to support 2S-6S, it looks like the datasheet is out of date. Thanks for pointing that out.

If it is marked M0129-63 or M0129-65 it supports 6S

M0129-3 and M0129-5 are the older version and they only go up to 4S

@Andrew-Jue , you can find the latest firmware for the IO board in /usr/share/modalai/voxl2-io-tools/firmware/modalai_m0065_firmware_v0_2_RC1_f94baad1.bin on your VOXL2 or on gitlab: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl2-io/-/tree/master/voxl2-io-tools/firmware

You can update the firmware using our voxl-esc tools, as documented here : https://docs.modalai.com/voxl2-io-firmware/#how-to-update-firmware

This version of the firmware is the latest and has been stable for over one year.

Alex