This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Max length for serial TTL between Tinypilot Hat and Controller
I would be very gretaful if experience could be shared from users regarding the maximum cable length for the serial connection between a TinyPilot Hat (direct feed from RaspberryPI UART @3.3V) and a motor controller (isolated thanks to a CPC5001 optocoupler).

Best regards,

if you use a shielded cable it is generally hundreds of feet

Generally it will work for very long runs unless there is some interference.
Hi Sean,

Thanks for the information.

I was envisionning something like 6m ; it sounds from your answer that it should work fine.
I will pay attention to interferences and will make some tests prior to final implementation.

Thanks again,

The protocol over that line includes a crc - a redundancy check, so messages are dropped if they don't sum up. Is there some way to signal 'dropped packets', e.g. in arduino_servo.cpp? Otherwise faults due to line interference are hard to diagnose.
if it didnt do a crc i dont think you would notice.. I just really dont want wrong commands to ever get through.

Anyway, you can run the wires basically anywhere in the boat and not have a length issue.
Ok, but if ever, against all odds, the line would suffer from interference, there is no logging of it anywhere, although there could be some warning. It now feels a bit like ostricizing, without the need to stick your head into the ground ;-)
I tried when I had a 200ft ethernet cable and it worked perfectly with no errors...

Do you want to count and record crc errors somehow or start using packet serial numbers to detect if some dont reach or?? Is this a solution searching for a problem?

Forum Jump:

Users browsing this thread: 1 Guest(s)