@jeremyrbrown5 What type of RC are you using?

@jeremyrbrown5 Can you attach a px4 log?

@brandon Agreed, the code has a fixed port but should use the source port. We will fix that and also add configurable ports for the gcs IP addresses in the configuration file.

Hi @snowt33nshi
note there are multiple lengths we offer:
https://www.modalai.com/collections/cables-1/products/mcbl-00084?variant=48956821602608

Hi @Jetson-Nano
Here is our info for Doodle Labs support:
https://docs.modalai.com/cable-datasheets/#mcbl-00085
Sorry it's buried in a cable page, but it makes the case clear (we think) how to support Doodle

regarding probing USB signals, unless you had a USB decoder on the scope, I do not think that will prove anything useful. You may be better off running usbview:
Windows:
USBTreeView by Uwe Sieber — uwe-sieber.de/usbtreeview_e.html
It shows enumeration hierarchy, configuration descriptors, endpoints, VID/PID, power requirements, etc.
Linux equivalent:
Use usbview — it’s essentially the same utility (GTK front-end to lsusb).

Hope that helps!

@Jetson-Nano Another thing you can do is attach an oscilloscope to the rx and tx lines of the UART. You may be able to sport obvious signal quality issues with that.

@Jetson-Nano It's best to try to determine what exactly is the cause first. If you determine that it is interference from a cable then the solution may be as simple as rerouting the cable. But you haven't determined for sure that EMI is even causing the issue. A good approach when designing a new vehicle is to first gather all of the electronic components and hook them together on a bench top as spread out from each other as possible and make sure that everything all works before trying to mount them inside the drone.

@emarcphera Huh, interesting. Okay, thanks for posting the update!

@ndwe -z in the voxl-logger command, not the voxl-replay command. But looks like voxl-replay sees the data and there is a raw data file for it to parse. Are you still having an issue?

@emarcphera I cannot reproduce the issue with v1.14.0-2.0.94 nor one of our most recent builds v1.14.0-2.0.105.