Quote:
Originally Posted by techhelpbb
Let's frame that:
Simple as in all in one piece with no room for wiring error or simple as in connect these wires here...here...and there?
In the current system the connect time is determined more by the D-Link robot AP and field than the cRIO. Point being: where is the line between the control system and accessories that FIRST provides?
To elaborate if someone makes a system that can boot, connect, and be ready to run in < 15 seconds. Then a user comes along with say a laptop and that takes 1.25 minutes to boot added to it is that an issue for the control system developer, FIRST or the user?
What about the amount of time to upload software into the control system?
Just curious.
|
I can't speak for Andy, but to me, the benchmark of "a simple, robust system that connects quickly and dependably" remains the 2008 control system (with the 2005-2006 breaker panel). The cRIO era has had some pluses, but you can't beat opening the package, wiring the robot, turning it on at the breaker and being able to drive three seconds later. (You'll notice I didn't say anything about imaging, setting IP addresses, or even downloading some user code.)
I'm not married to the IFI system, but it is my point of reference on things related to (re-)connection speed and simplicity.