Topics created by Jetson Nano

@Jetson-Nano Regarding question #1, Yes, you can attach an external FC over the UART.

Hi @Jetson-Nano
Here is our info for Doodle Labs support:
https://docs.modalai.com/cable-datasheets/#mcbl-00085
Sorry it's buried in a cable page, but it makes the case clear (we think) how to support Doodle 🙂
b1fa4a9a-f883-4566-b3e2-ae9ab14b7264-image.png

regarding probing USB signals, unless you had a USB decoder on the scope, I do not think that will prove anything useful. You may be better off running usbview:
Windows:
USBTreeView by Uwe Sieber — uwe-sieber.de/usbtreeview_e.html
It shows enumeration hierarchy, configuration descriptors, endpoints, VID/PID, power requirements, etc.
Linux equivalent:
Use usbview — it’s essentially the same utility (GTK front-end to lsusb).

Hope that helps!

@Vinny Thank you for your valuable feedback.

I’ll keep the points you mentioned in mind while doing the bench testing.

@tom Thank you for the support.

@Vinny Thank you for reverting back, I will follow the steps you mentioned along with the ESD safe method.

@Eric-Katzfey thank you for reverting back, it was very helpful, i was able to get multiple streams.

@Eric-Katzfey I am using VOXL 2 to Flight Core v2 to VOXL FPV ESC, will this change affect any performance of the flight or any other abilities.

@Eric-Katzfey Thank you for reverting back, I am able to get the turtle mode working now, The error was due to the safety parameters, once i changed it to the FPV setup, it was working.

Once again thank you for the support. It was really helpful.

@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

@Jetson-Nano Can you please start a new thread for this new topic?

@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

@Jetson-Nano
YES!!! So happy to hear that.