The USB Dropouts seem to be a disconnect and the device refuses to reconnect until physically disconnecting and reconnecting.
We're using the first 4 pins for USB 2.0 on the 3.0 connector as specified in the 3.0 specification https://en.wikipedia.org/wiki/USB_3.0#Pinouts
We've left all the other pins disconnected. I still need to run more tests to determine if it's actually this port or if it's the devic
Latest posts made by benjamin linne
-
RE: 5G modem USB hub dropout on 3.0 but not 2.0
-
5G modem USB hub dropout on 3.0 but not 2.0
Hi,
I'm experiencing USB dropouts on the 5G breakout board on the 3.0 port but not the 2.0 port when attempting to run 2.0 devices on the 3.0 port.
Looking at the block diagram, it appears the 2.0 port comes off the same hub. How is that wired since I'm thinking maybe I need to group the remaining grounds or pull the unused signal lines high or low.Thanks,
Ben -
RB5 3rd part ESC support
Hey, are there any plans to support 3rd party ESCs with the RB5? Specifically blheli ESCs with DShot support. I'm looking for ESCs that are capable in the 100A range and heard there was some progress being made in . I like the reduced wiring with the modalAI ESC since it uses a single UART, so if there are other compatible ESCs with a higher amperage rating, I'd be interesting in learning about them.
-
RE: RB5 WiFi antennas
Thanks! I think there was some confusion about which connector to plug into, but that clarifies it. Also, any reason why the RB5 ships with a different antenna type than the VOXL?
-
RB5 WiFi antennas
Hi, I'm interested in acquiring more WiFi antennas for the RB5, but the original WiFi antennas for the VOXL don't appear to fit, and there's none listed on ModalAI store. Also, are the included WiFi antennas for the RB5 tuned for both 2.4 and 5Ghz? I found 5Ghz in station mode to work very well on the VOXL with significantly faster throughput than connecting to a 2.4Ghz only wifi AP.
-
RE: micrortps setup via voxl_io
Hey @ryan_meagher , I've managed to get micrortps working without the internal uart. I'm using an ftdi adapter from a uart on the voxl to a usb port on-top of the microhard adapter. This is working well, except the voxl is locking up when we are running several nodes. I suspect it to be a problem with DDS requiring more bandwidth and potentially a race condition occurring. I'm interested in trying your voxl_io version if that is working, and I can provide some help to get the ftdi to usb version working if needed.
-
RE: voxl communications completely locking up
@Eric-Katzfey I was referring to the documentation for the specific registers that would need to be modified to enable and configure it since I'm familiar with embedded systems that allow that functionality. Another possibility is to add the /dev/watchdog kernel module, however that would require an update to the operating system. If this is possible, it would greatly improve the robustness since we are encountering many cpu lockups that require human intervention to perform hard reboots. For remote applications this is potentially a critical feature
-
RE: voxl communications completely locking up
@Eric-Katzfey I'm looking for documentation on the hardware watchdog timers onboard the voxl's snapdragon microcontroller
-
RE: voxl communications completely locking up
@Eric-Katzfey Could you point me to how I can setup watchdog timers on the voxl?
-
RE: voxl communications completely locking up
@Eric-Katzfey We're having trouble identifying the errors in dmesg. Is there a watchdog timer that could automatically restart the voxl? This will help debugging uas in a remote location without needing a hard reset.