View Single Post
  #34   Spotlight this post!  
Unread 14-04-2014, 00:10
pathew100 pathew100 is offline
Registered User
AKA: Pat Murphy
FRC #0862 (Lightning Robtics)
Team Role: Mentor
 
Join Date: Feb 2005
Location: Canton, MI
Posts: 169
pathew100 has much to be proud ofpathew100 has much to be proud ofpathew100 has much to be proud ofpathew100 has much to be proud ofpathew100 has much to be proud ofpathew100 has much to be proud ofpathew100 has much to be proud ofpathew100 has much to be proud ofpathew100 has much to be proud ofpathew100 has much to be proud of
Send a message via AIM to pathew100
Re: FIRST please fix....

I was the scorekeeper at MSC and was an FTA for 3 FiM districts this year. I don't have the answers but I can clear up/confirm some things.

As some have mentioned, yes, you have to finish the match and commit the scores before the match logs are saved. That's why we had to complete the second match. FIRST HQ wanted the logs from both matches.

As Adam stated, we were going to stop the third match if we saw the same behavior.

Right in the field monitor logs it clearly showed that FMS transitioned the robots from Auto to Teleop back to Auto. It affected all 6 robots on the field. As mentioned in this thread, the actual outcome of that incorrect transition is different for each team based on their code implementation.

This is one of the purest definitions of a 'field fault' and is a replay no matter what teams are on the field, what match it is, or whether or not the match is played for 10 seconds or the full 2:30.

The 'signature' of the fault is known and when it occurs the data confirming it can be found in the field logs and the driver's station logs. I can't speak to whether or not FIRST can fix this before Championship but I'm sure they will try.