@Thomas-Müller interesting. i'm just experience the very same thing. have you by chance figured out what was the issue?

@cguzikowski Yes, very odd. Hopefully it just works now

@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).

@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

@Eric-Katzfey Thank you! I now use journalctl and write to a file in a logger service, for example: voxl-mapper-logger.service [Unit] Description=Logs voxl-mapper log output to file After=voxl-wait-for-fs.service network.target network-online.target Requires=voxl-wait-for-fs.service network.target network-online.target voxl-mapper.service [Service] Type=simple ExecStart=/bin/bash -c "sleep 45 && journalctl -f -u voxl-mapper.service >> /data/logs/voxl_mapper.log" StartLimitInterval=0 Restart=always RestartSec=2s [Install] WantedBy=multi-user.target