ModalAI Forum

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

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

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

@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

@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

@tom Thank you! I am adding an imx214 on J8L.

@Dronodev Using the M0065 on a UART on the WiFi add-on board may be the most straightforward way to do this. We've never tried to set one up like that but, in theory, it should work if configured correctly in px4. There is no direct way right now to send the RC channel PWM input out the VOXL esc PWM output. There are a number of different ways to approach that so we'll take a look and see if we can come up with something in the next couple of weeks.

@jacob-yaacubov We have some add-on boards that would allow connection of 2 USB cameras. For example: https://www.modalai.com/collections/voxl-2-add-ons/products/voxl-microhard-modem-usb-hub and https://www.modalai.com/collections/voxl-2-add-ons/products/voxl-lte?variant=32449203601459

@Eric-Katzfey we are using A doodle radio Just found that reboot -f works. It's interesting weird that the network interface seems to not go down but all the services do - and don't come back.

UPDATE I've simplified my snippet and I'm now able to "connect" to the VOXL2 via MAVSDK. It's still now working as I would expect it to, but first, here's my new script: #!/usr/bin/env python3 import asyncio from mavsdk import System target_ip="192.168.1.187" target_port=14550 async def connect_to_drone(): print("Connecting to VOXL2...") # Create a System object with specific system ID and component ID # These match the IDs we're using in the heartbeat sender print("Creating System object...") drone = System() # Different connection string formats to try print("Connecting to drone...") await drone.connect(system_address=f"udp://{target_ip}:{target_port}") print("Waiting for drone to connect...") timeout = 60 # Extended timeout start_time = asyncio.get_event_loop().time() try: async for state in drone.core.connection_state(): print(f"Connection state: {state}") if state.is_connected: print(f"Connected to drone!") return drone # Check if we've timed out current_time = asyncio.get_event_loop().time() if current_time - start_time > timeout: print(f"Connection timed out after {timeout} seconds") break await asyncio.sleep(1) except Exception as e: print(f"Connection error: {e}") return None async def main(): # Try to connect to the drone drone = await connect_to_drone() # If connected, do something with the drone if drone and drone.core: try: # Print basic information info = await drone.info.get_version() print(f"Version Info: {info}") except Exception as e: print(f"Could not get info: {e}") if __name__ == "__main__": # Run the asyncio loop asyncio.run(main()) When I run this script I see only 3 logs: Connecting to VOXL2... Creating System object... Connecting to drone... When I adb shell and run voxl-inspect-mavlink mavlink_from_gcs I now see that the VOXL2 is receiving a heartbeat: ID Mavlink MSG Name Counter Hz 0 heartbeat 5 1.1 But like I mentioned above, the code doesn't execute past await drone.connect(system_address=f"udp://{target_ip}:{target_port}"). I've tried udpout and nothing changes.