ModalAI Forum

@Moderator That port is capable of providing 2A at 5V from a SW controlled GPIO (GPIO_157). I'm surprised you would experience a brown-out from a USB to ETH adapter. On Voxl2, we provide a 10uF and a 1uF cap right at the 60-pin J3 connector. If you are doing a custom adapter, and to meet USB3 specs, you should not need much more capacitance. However, if you have a long length before your mating connector, a good 10-22uF would be wise. We provide a 100uF cap on all of our USB ports that mate to Voxl2 (M0090 5G Modem Plug-in card, for example), but it is also due to a USB switch to help manage the ON time during enumeration. Back to your specific issue, I would double check you are not toggling GPIO_157, or that your connection is solid and not intermittent. I cannot find specific ETH dongle power consumption specs online, but it is likely using a LAN7801 or similar type device plus a PHY, which would not exceed more than a few hundred mA combined with magnetics: [image: 1689623049484-a50456c1-db0d-4702-ab52-693715163dfb-image.png] [image: 1689623071606-b4d29526-d5e9-4dff-aeb6-760e4808daa0-image.png] So a brown out does not seem likely here. Even a 500mA USB2 rated device has no issue powering these types of dongles.

@Eric-Katzfey said in VOXL2 IO (M0065) support on PX4 1.14 in SDK 1.0.0: @Jon305Johnson I would estimate about a month for RC functionality (SBus) and another month for PWM @Eric-Katzfey any updates or projections on the M0065 integration into 1.14?

@James-Strawson Thanks for reply, Will look into it and get back.

@tom Thank you for your response! I'll look forward to the new documentation when it becomes available, thanks for the hard work. Cheers!

@Vinny Ah I did not know that. Thank you for informing me, I will not put PCBs on ESD bags anymore. I don't want to risk breaking any boards Also, it turns out that the 2023 model of doodle radio has a separate port for power and USB. So we chose to power the doodle separately instead of daisy chaining one port on the VOXL2 to two ports on the doodle.

@Achyut-Sapariya That all looks normal, I'd recommend submitting an RMA and our team can diagnose the issue: https://www.modalai.com/pages/rma

For future reference, this is the doc to follow https://docs.modalai.com/voxl2-image-sensors/

Hey @user887 I attempted to QDL flash a "golden unit" rb5 but wasn't able to replicate the error you're experiencing. I would remove and reattach the SOM ensuring there isn't a loose connection to the rb5 board, remove any cameras or connectors, and trying a different USB cable in the case of a loose connection between the USB cable and rb5. Hope these tips help!

@relevinsky You're right, we are going through an overhaul of the docs at the moment, here's an archived link: https://docs.modalai.com/voxl-logger-0_9/

@tom Thank you for the info. We have custom drone designed with Carbon fiber chamber inside which voxl2 resides over a dampner platform and we have camera bay towards front of the UAV which has CSI connection with VOXL2. We do not have fan over VOXL2 but we have kept fan towards backside of this carbon fiber chamber to act as exhaust but I guess it isnt working out well to cooldown CPU.

Hi @wilkinsaf I was just thinking about your issue was going to ping you for an update. Well, yes, good that it is not repeatable, but bummer we do not know why you had it in the first place so we can all learn why. More importantly, I hope that Voxl2 is functioning correct given the error condition from the non-Quectel modem that was introduced. I also hope you verified your PDB board has the correct grounding scheme. Ping on us again if you need any extra help/tips/etc. Best option is always a new thread, or make sure to tag me on on existing threads. Thanks!

@Jyotish-Kumar There could've been an ESD issue induced by not having the board on an ESD mat or not using proper ESD protection, check out https://www.modalai.com/pages/rma

@Anubhav Great!

@Hersch-Nathan A quick google gave me: sudo apt update sudo apt install python3-opencv

@Chad-Sweet You are correct. Swapped the IMX214 for a different one and it worked. Thank you for the help!

@brycek did you eventually figure out? I need to create a full image as well

@황인호 It isn't required to use voxl-modem to interact with the modems if you'd like to do a custom config. In your case, I'd recommend using voxl-configure-modem with the quectel option to handle Quectel bringup and then creating a custom script / service file (or modifying the existing one) to handle doodle bringup. Although doodle bringup is very basic, if you follow the code path here in the startup script: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/blob/master/scripts/voxl-modem-start#L99 it monitors the eth0 network interface and if the IP address isn't what is specified in the config file then it assigns said IP address. This could be broken out into a different script

@afdrus No I haven't.

Found the offset its gpiochip1100 so for gpio 12 echo 1112 > /sys/class/gpio/export will enable gpio 12