View Single Post
  #27   Spotlight this post!  
Unread 14-10-2016, 12:31
frcguy's Avatar
frcguy frcguy is offline
Unregistered Unuser
AKA: Nicholas Dal Porto
FRC #5940 (B.R.E.A.D.)
Team Role: Tactician
 
Join Date: Dec 2015
Rookie Year: 2012
Location: Burlingame, California
Posts: 855
frcguy has a reputation beyond reputefrcguy has a reputation beyond reputefrcguy has a reputation beyond reputefrcguy has a reputation beyond reputefrcguy has a reputation beyond reputefrcguy has a reputation beyond reputefrcguy has a reputation beyond reputefrcguy has a reputation beyond reputefrcguy has a reputation beyond reputefrcguy has a reputation beyond reputefrcguy has a reputation beyond repute
Re: [FRC Blog] Control System Update

Quote:
Originally Posted by Chris is me View Post
The big problem is that the USB spec limits the length of most USB cables to shorter lengths than Ethernet. Ethernet is designed to be used over longer distances than USB. In practice you're probably fine either way, but Ethernet is what we "should" be using IMO
Yep, I agree that Ethernet is the ideal tethering method. For us however, tethering was limited to just testing things in either our pit or in queue, and we didn't need the longer distance that Ethernet can handle. If we needed to test on the practice field or some other long distance tether we had a long Ethernet cable ready.

Quote:
Originally Posted by bobbysq View Post
Also, I don't believe you get full access to the robot's LAN when using USB. This is important if you used vision tracking with an external processor like us this year.
This is correct as well, although we didn't have issues with that this season (low goal robot ).
__________________


2016: Team 5940 (Silicon Valley Regional Rookie All-Star and Quarterfinalist, Curie Quarterfinalist)

Volunteer: 2016 (Chezy Champs Field Reset, Capital City Classic FTA, MadTown ThrowDown FTA)

Last edited by frcguy : 14-10-2016 at 12:36.
Reply With Quote