Topics created by Jetson Nano

@Eric-Katzfey Also, there is a parameter called VOXL_ESC_T_ON. How is that set? It determines which button will be used for turtle mode. The code is here: https://github.com/modalai/px4-firmware/blob/ea098200d3c09b7af548bf7be29fda245fad8f17/src/modules/mavlink/mavlink_receiver.cpp#L2083

@Alex-Kushleyev Thank you for reverting back.

@Jetson-Nano you could just use the CPP mavsdk instance to grab the TOF data from a MPA pipe and then leverage that to do your controls via mavsdk (I am assuming just offboard movement). You can connect over port 14551 just ensure you have localhost comms set to true in voxl-vision-hub.

@Jetson-Nano , 60C is not an issue for embedded devices (throttling limit is around 95C, at which point the CPU will start reducing frequency to avoid overheating).

However, you mention that the temperature can reach 90C. Please note that the camera server itself most likely is not the main cause of the CPU temperature, but the consumers of the image frames may be using significant CPU.

You should identify the main causes of temperature rise by looking at output of top to see rough cpu usage of each process, but also try disabling mapper or openvins or hires image processing (if any).

Also, without any cooling, it is not a surprise that VOXL2 could overheat if its cpu / gpu load is very high. The SoC cannot run without cooling at full power. Airflow during flight usually provides significant cooling and you can manage the system load when not in flight or add cooling for stationary use cases (lack of air flow from propellers),

Alex

@zauberflote1 @Cliff-Wong @James-Strawson
guys, can you help me with the error mentioned.
now i have an another error where, if I arm the drone, the vio is drifting, and i can see the values increasing without any movement.
what would cause this kind of errors, earlier the drone was flying fine, then it started drifting, even when just armed.

@Alex-Kushleyev Thank you for reverting, I will check this out and get back to you

Hey @Alex-Kushleyev , for the same setup I mentioned above my esc is not starting by default, while I run voxl_esc start in mavlink console, it starts and works.
what could be the reason for such behaviour. Please could you help me out

@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 @Jetson-Nano
Sch updates look correct. I'd still add a pull-up on the Lepton Reset to help control it during initial power-ON before the IO expander is configured.

To help further debug your existing setup, I'd need more tangible info such as pictures with all your cables, etc. Do you have a DMM handy showing the voltages of 1.2V and 2.8V, and an O-scope for the 25MHz?
Can you also post a pic of your board without components installed (so I can review the layout as best as possible)?
It's hard to give much further guidance without actual hardware in my hands.
Thanks!

@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