Quote:
Originally Posted by Jared341
I think you guys are jumping the gun big time. Assuming they put the USB hub, E stop, and I/O breakout into a single, well-designed enclosure, what's the big deal?
|
I agree, we can't shoot the messenger. Let's work with the classmate to improve it's functionality so we can achieve the robustness of the 2004 IFI driver station. Let's start with supporting all the basic functionality including in previous years systems (I/O, E-stop, USB Hub). Then let's try to optimize boot load time to less than 1 minute.
Is there anyway to put the classmate in standby mode so the time to start is less than 5 seconds ?
Quote:
Originally Posted by Jared341
3) The clamshell has audio playback, a microphone, and an optional camera. There is opportunity for innovation here. Imagine a game where in "autonomous" mode you could talk to or gesture to your interface without touching buttons.
|
I'm not too worried about microphones or cameras, but audio playback would be useful.
Quote:
Originally Posted by Jared341
4) The clamshell is much more capable a computer than even the cRIO. If they let you write code for it, you can suddenly offload some complicated (computer vision) tasks.
|
Off-loading processing to a remote driver station seems inefficient for a real-time OS on a robot.
Quote:
Originally Posted by Jared341
5) Every team now has access to a sort of dashboard app without having to pony up their own laptop. This helps not only the teams, but also potentially FTAs and staff to troubleshoot problems from the driver stations.
|
Having basic terminal access would be nice so we can monitor the system processes. I would trade all dashboard visuals for reliability and speed.