[DFTF] Operator Interface...

[Gary Bonner]

Originally Posted by Joe Johnson

What about the O part of IO?

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

[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.