Thread: Windows 10
View Single Post
  #19   Spotlight this post!  
Unread 05-05-2015, 11:59
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,112
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Windows 10

Quote:
Originally Posted by stinglikeabee View Post
Windows as an operating system isn't really a factor in connection issues on the field. Most connection issues are caused by robot electrical issues and improperly configured driver stations.
On the other hand, my experience is that Windows is the single biggest factor in problems switching from on-field networking to in-pit networking. There are probably things that the Driver Station can do to make it work better, but they would basically be workarounds for inconsistent and undesired Windows behavior.

Quote:
Originally Posted by lopsided98 View Post
On another note, though, it doesn't seem like it would be very hard for NI to make the driver station work on Linux, because (I'm pretty sure, I haven't had much experience with it) LabView can be compiled for Linux without many/any changes.
I think it's the specifics of the USB drivers that would make a Linux version of the Driver Station harder to implement than one might assume.