Thread: Week 2 Analysis
View Single Post
  #34   Spotlight this post!  
Unread 11-03-2014, 04:44
Travis Hoffman's Avatar Unsung FIRST Hero
Travis Hoffman Travis Hoffman is offline
O-H
FRC #0048 (Delphi E.L.I.T.E.)
Team Role: Engineer
 
Join Date: Sep 2001
Rookie Year: 2001
Location: Warren, Ohio USA
Posts: 4,047
Travis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond repute
Re: Week 2 Analysis

Quote:
Originally Posted by Rynocorn View Post
I did not think this was the way it was done... I am pretty sure the refs just plug in the pocessions for each robots in whichever zone and the FMS calculates the points based on the highest number of assist points. Also truss points aren't assessed when the goal is scored but when it goes over the truss. I would also assume that he ref would click the score button and then go back to entering the foul after. Just my knowledge of the system as I think I know it
Sounds like, as countless referees and casual observers have been saying all along ever since they learned how this system was intended to work, we should SPLIT THE SCOREKEEPING AND FOUL KEEPING into separate volunteer processes. Separate everything that isn't required to be tracked as part of the cycle - referees handle that - mainly fouls - these can be entered whenever. Scorekeeper refs focus solely on assists and scores. Truss/Catch can be handled by either - pick your poison - I'd choose scorekeeper refs in order to remain consistent.

So if I'm not mistaken from what I've read, the foul entry screen is on a separate menu page from the scoring menu on the AB PanelView touchscreens? Well bite the bullet, call up Allen-Bradley and buy some more of those suckers, and create separate HMI's for dedicated foul panels. I'm guessing the system can handle additional HMI's (Ethernet based IO??). Map the new HMI foul screen objects (is the HMI panel an RS View app?) to the same master controller IO that currently drives foul calculations. Hide or delete the foul screens from the original touchscreens. Or do the opposite if the foul tracking features need to physically remain where they are - separate the scoring menu into a separate HMI and application.

Provided you speed up the processing of final cycle information with more eyeballs and parallel HMI input, the pedestal and any remaining light up delays introduced by the laggy system can still be ignored. Decouple the pedestal lights from the system and drive them with human operated switches run by dedicated pedestal refs at each end of the field. They can track and signal for any HP early removals.

If these troubles continue...if you CAN'T fix this, because you embedded this inefficient blar too deep in the system to excise, then admit you screwed up, and issue a partial event fee refund to every FRC team for being forced into a flawed competition experience that diverged greatly from the product you originally marketed to teams.
__________________

Travis Hoffman, Enginerd, FRC Team 48 Delphi E.L.I.T.E.
Encouraging Learning in Technology and Engineering - www.delphielite.com
NEOFRA - Northeast Ohio FIRST Robotics Alliance - www.neofra.com
NEOFRA / Delphi E.L.I.T.E. FLL Regional Partner

Last edited by Travis Hoffman : 11-03-2014 at 05:57.
Reply With Quote