View Single Post
  #8   Spotlight this post!  
Unread 03-04-2014, 16:46
NotInControl NotInControl is offline
Controls Engineer
AKA: Kevin
FRC #2168 (Aluminum Falcons)
Team Role: Engineer
 
Join Date: Oct 2011
Rookie Year: 2004
Location: Groton, CT
Posts: 261
NotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond repute
Re: Touch Screen with the Driver Station?

There are teams that have done this already, and have competed with a driverstation with a touchscreen.

Most notably last year one team had a touch interface with vision processing, where they would select the goal on the screen within the camera image to go after.

This year, we developed a custom dashboard writen in python and talking to our Java based Robot (one of items contributing to winning us the controls award at the district level).

The dashboard displays information as well as allows for the user to select different auto modes, hit a button to do other macros for the bot etc. It will run on a touchscreen laptop no problem, we just don't use one.

In addition to the controls on our dash, we have redundant controls assigned to buttons on our F310 joysticks. The operators love those and choose them over the dash (so they simply use the dash as a status display most of the time) because they never have to look down, and they can move around to see the action better.

A touchscreen dash is definetly something viable. However you need to weight the cool vs practical. What will allow you to beter control your robot behind the glass, and make your operators lives easier so they can focus on the game, that is what is most important. I would say try it out in the off-season, and if it is deemed beneficial, hit it hard next year.

EDIT: Even if you deem touchscreens will not benefit your drivers, touchscreen applications to support the performance of your FRC team are not out of the question. This year we had a student lead team develop a scouting app with a very sleek GUI(also a python front end) which runs on the windows surface tablets. These were used by our scouting team to enter data indivually on the touch based app, then synced to a single database for later viewing by the drive team during scouting. This application of touchscreens is where I would see the touchscreen FRC market take off the furthest.

Hope this helps,
Kevin
__________________
Controls Engineer, Team 2168 - The Aluminum Falcons
[2016 Season] - World Championship Controls Award, District Controls Award, 3rd BlueBanner
-World Championship- #45 seed in Quals, World Championship Innovation in Controls Award - Curie
-NE Championship- #26 seed in Quals, winner(195,125,2168)
[2015 Season] - NE Championship Controls Award, 2nd Blue Banner
-NE Championship- #26 seed in Quals, NE Championship Innovation in Controls Award
-MA District Event- #17 seed in Quals, Winner(2168,3718,3146)
[2014 Season] - NE Championship Controls Award & Semi-finalists, District Controls Award, Creativity Award, & Finalists
-NE Championship- #36 seed in Quals, SemiFinalist(228,2168,3525), NE Championship Innovation in Controls Award
-RI District Event- #7 seed in Quals, Finalist(1519,2168,5163), Innovation in Controls Award
-Groton District Event- #9 seed in Quals, QuarterFinalist(2168, 125, 5112), Creativity Award
[2013 Season] - WPI Regional Winner - 1st Blue Banner

Last edited by NotInControl : 03-04-2014 at 17:01.
Reply With Quote