@Eric-Katzfey I see. Thanks for the response.

@Riccardo Okay, thanks for the confirmation. I'll look into increasing that limit to 16 or so.

HI @teddy-zaremba That is the correct approach. We have no mentions of direct servo support from VOXL 2 or any HW. All servos, just like an ESC, need power from an independent battery source not from VOXL 2. Thanks for clarifying here on the Forum.

@tom Is there a way to voxl-logger the outputs from voxl-inspect-cpu and play it so that I can see the graphs on voxl-portal? Currently I can only voxl-inspect-cpu or view the graphs in real-time on voxl-portal, but I would like to record the data when the drone flies and review it post-flight

@tonygurney , please see the doc page regarding GPIO and the offset: https://docs.modalai.com/voxl2-linux-user-guide/#gpios specifically, Starting SDK 1.2.X/System Image 1.7.3, GPIOs are exported by default in /sys/class/gpio, the GPIO have an offest of 1100 (e.g. GPIO 84 = 1184).

@Sarika-Sharma Okay that should be fine, was just double checking the voltage wasn't too high for that ESC. I'd recommend submitting an RMA: https://www.modalai.com/pages/rma

@Rajamani , Yes you can connect a raspberry pi to VOXL2 via a USB C cable (using the USB C port next to the VOXL2 power connector). The RPI will be the "host" in this case, and you can use ADB from RPI to access voxl2 (just like connecting VOXL2 to a laptop or a desktop computer). Please make sure to use the USB 3.0 port on the raspberry pi and test the cable / usb port before doing any further design plans (just to make sure it works for you). Alex

@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

@KnightHawk What are you trying to do? Why would you want to communicate with your FC via i2c?

@claw That is definitely not the expected behavior, I recommend going through the RMA process

@v_v_ramarao voxl-streamer does not support multicast

Hi @voxltester Apologies you are having issues with the power cable. We have expressed in several forum posts that care must be employed when removing and inserting any power cables to not tug on the cables themselves, but rather the large shroud/connector housing. Pulling on any cable repeatedly will dramatically reduce it's service life as it results in frayed conductors at the pin crimp contacts. This is not an MCBL-00001 issue, but all cables in all electronics not just from ModalAI. There are no plans to change this solution as it has been tried and true for over a decade. Some of my power cables are nearing 13 years old and every one can last that long if handled properly. If needed, I can try to search through some forum posts where I think we have a picture showing the recommended methods of grabbing onto the plastic shroud instead of the cable conductors themselves. Our team is trained on this method as well. Hope this helps.

@swickliff Interesting, have you had success with this hardware setup before?

@kestrelsystemsbp Take a look at Python MPA interface: https://gitlab.com/voxl-public/voxl-sdk/core-libs/libmodal-pipe/-/tree/dev/python?ref_type=heads

Hi @dougmiller If your VOXL 2 Mini is TrustZone Configured for UART over J10, then yes, there are 2 pins available as inputs. https://docs.modalai.com/voxl2-mini-connectors/#j10---external-uart You can see GPIO_40, GPIO_46 and GPIO_64 are input capable. GPIO_40 and GPIO_64 are able to be configured to do wake events in the SoC so they have extra configuration to route to a power manager. Depending on how you write your IRQ routine, that may or may not help. Hope this helps!

@h3robotics , Thank you, you are right again. We will update!