[DFTF] Operator Interface...

[Chris Hibner]

Originally Posted by DonRotolo

There are a bunch of digital outputs available. No analog outputs. These sink enough current to drive small LEDs, and can certainly drive a transistor or other switch to manage larger loads.

I see no rules prohibiting either of those items from being used with the Operator Interface. And that would surely win the "cool as beans" award in my book.

We've done a lot with LEDs with the old IFI system (2008 and prior). We haven't done anything since then, but we're planning to this year. We haven't implemented it yet, but I can let everyone know how it goes.

I actually think we'll be making a lot of use of the Cypress board this year.

[eStop Robotics]

Originally Posted by Gary Bonner

We used the eStop CCI last year. Very easy to wire and program, but no O, only I.

Glad to hear that you found the CCI easy to use...that was our primary goal in designing the product.

With the extensive dashboard capabilities of the current Operator Interface what O would you like to see in an interface like the CCI?

[Jared Russell]

The eStop CCI is a very well designed product in my experience.

One thing you should know about, Dr. Joe, is the evolution of the dashboard software over the past few seasons. Not only is there a good default LabView dashboard, but for C++ or Java users there is also the SmartDashboard, which is highly configurable and supports things like bidirectional data exchanges (so you can pick your autonomous mode right in the GUI) and integration with JavaCV/OpenCV (in case you prefer doing any image processing remotely).

In addition, there have been a few team-created open source dashboards released, with the most popular probably being ZomB.

Links:
SmartDashboard (http://firstforge.wpi.edu/sf/projects/smartdashboard)
ZomB Dashboard (http://firstforge.wpi.edu/sf/projects/zombdashboard)

[Dad1279]

We Used the eStop CCI last year, it was simple to use.

We have also dissected a std joystick, and made a custom control panel by wiring the (arcade)switches to the corresponding connections on the joystick.

[Cecil]

Originally Posted by apalrd

I'd stay away from the Cypress (FIRSTtouch) board if possible.

We used it in 2010 with nothing but problems

We have used the Cypress for the past 2 years, and have had no problems with it. Instead of the breadboard that came in the KOP, we also order one of these every year, so we can just pull off the Cypress and reuse it the next year while leaving the button box intact, just in case we need to use it again.

I guess I am a bit biased, however, as i have never tried the new CCI. I do, however, give props to the enclosure that eStop made. It makes it so much easier to wire up the Cypress.