Topics created by Jetson Nano

@Alex-Kushleyev Thank you for the support. I will make the changes you have mentioned.

@Alex-Kushleyev, I using voxl2 with M0173 board with camera config 29.
The errors are now solved, I made the necessary changes and reconfigured every server and pipeline and calibrated the cameras.

@Jetson-Nano We have never used Microhard on windows but it's possible your firewall is blocking UDP data on that port

Hi @Alex-Kushleyev @modaltb @Eric-Katzfey
I still have the same error when i use my custom board. Could you verify my board pinouts.

image (2).png

@Jetson-Nano To install the new voxl-io-server try dpkg --force-all -i voxl-io-server_0.0.5-202502191136_arm64.deb.

@tom thank you for reverting , I sorted out the issue, the file name in the voxl-qvio-server was opencv_tracking_front_intrinsics.yml instead of opencv_tracking_intrinsics.yml
and in the voxl-vision-hub the name was tracking_front which i renamed in tracking. After the above mentioned changed the voxl-qvio-server is working fine.
thank you for the support.

@Jetson-Nano Here's some example code: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub/-/blob/master/src/autopilot_monitor.c?ref_type=heads#L514

@Jetson-Nano It should be no different than with any other flight controller hardware running PX4. The PX4 documentation should be able to explain how to do that.

@Alex-Kushleyev @Eric-Katzfey can you check it out and help with the code.

I am also interested what kind of signal is send to the neopixel LEDs to turn it ON.
And with addition to that what is the command to turn ON only blue lights.

@Jetson-Nano , I am sorry, I don't have this hardware set up right now, so I can't actually test what you are trying to do. I will check with the team regarding who can test it.

Alex

Hi @Jetson-Nano
Please see this cable page for more guidance.
https://docs.modalai.com/cable-datasheets/#mcbl-00085
Doodle is one of those applications which we give customers enough to start trying it, but we encourage a custom solution to fit your application(s).
Thanks!
Vinny

Hi @Jetson-Nano
No difference in data rate on any MH board. They are all USB2 rates.

Hope that helped!

@Jetson-Nano The M0173 kits include the IR filter on all sensors.

@Jetson-Nano Have you looked at voxl-inspect-cpu?

@Zachary-Lowell-0 as mentioned I have set offboard-mode in voxl-vision-hub.conf to "off".

I did a flight test shifting to offboard-mode,

The drone was able to execute the script in a stable way without any jittery motions or trying to come back to home position.

These are the flight logs,
https://review.px4.io/plot_app?log=e32a28df-cbba-4765-8499-6fe46e2ff890

@Jetson-Nano Instead of listening to the input_rc topic with the listener function you can now monitor the RC_CHANNELS Mavlink message from the FC v2.

@Zachary-Lowell-0 Thank you for your reply. I will test it out and let you of any developments.

@Jetson-Nano , just to add to what Vinny said and answer your specific question about vibration affecting the micro coax connectors. The difficulty associated with removal is separate from the connector’s robustness under vibration. Once the connectors are inserted (mated), they are difficult to disconnect without applying significant force that might actually break the connector (that is why a tool is required, which correctly separates the connector). This type of stress is very unlikely in typical applications, unless the drone crashes and camera or board is somehow ejected from the vehicle.

@Jetson-Nano

Please take a look at the following links:

https://docs.modalai.com/M0169/
https://docs.modalai.com/M0178/#requirements
https://docs.modalai.com/voxl2-coax-camera-bundles/#mdk-m0173-1-01

M0173 config

M0169 was built to support the new TOF sensor using the existing (at that time) flex cables and interposers, but those were not designed to carry 5V from VOXL2, therefore M0169 requires additional connector to supply 5V (which can be taken from the same APM that is supplying 5V to VOXL2). TOF V2 sensor can output much higher IR power compared to TOF V1, and the existing interposers / power rails were not designed for that, so an additional 5V input to M0169 is required.

Now, with M0173 (aka Starling 2 Front End), the front end plugs into VOXL2 and makes use of the available 5V on VOXL2 (which was not possible using older interposers and extension cables). M0171 / M0178 is able to pull 5V directly from VOXL via the Starling 2 Front End.

M0178 is basically an M0171 with a tab for mounting.

In order to use M0178 / M0171, you have to use M0177 flex that is connected to M0173 camera front end (which plugs into VOXL2).

So there is basically two options for connecting TOF V2 to VOXL2:

VOXL2 -> (M0135 or M0076) -> (M0074 or M0036 extender) - > (M0169 + 5V power) -> TOF V2 VOXL2 -> M0173 -> M0177 - > (M0171 or M0178) -> TOF V2

I know that is a lot of board numbers, but hopefully that makes sense..

Alex