View Single Post
  #9   Spotlight this post!  
Unread 20-02-2010, 20:14
pSYeNCe's Avatar
pSYeNCe pSYeNCe is offline
Programaster
AKA: James
FRC #2010 (Lightning Bots)
Team Role: Alumni
 
Join Date: Feb 2010
Rookie Year: 2007
Location: Ohio
Posts: 58
pSYeNCe is a splendid one to beholdpSYeNCe is a splendid one to beholdpSYeNCe is a splendid one to beholdpSYeNCe is a splendid one to beholdpSYeNCe is a splendid one to beholdpSYeNCe is a splendid one to beholdpSYeNCe is a splendid one to behold
Re: SOFTWARE PROBLEM!!!! PLEASE HELP!!!

Quote:
Absolutely. You can read the millisecond clock simply by dropping the Tick Count block. It is used for timing the Vision code and elsewhere in the framework. You can read it at the beginning and end of Teleop, or you can read it each entry, etc. You can also make use of the Match Info.Elapsed Seconds which has millisecond resolution. It comes from the same clock, and you can use it at the beginning of Teleop to identify a missed packet. I've made notes about how each of the choices listed would impact the robot if they were the chosen method.
That's from the link you recommended, and I just don't understand what he means on how to identify the missed packet.
As a side note, we're going to reload the original code (after all the batteries recharge, which somehow all became dead at the same time ).

Edit: We're also going to try disabling Vision to see if that's causing the problem.

Last edited by pSYeNCe : 20-02-2010 at 21:30. Reason: Additional troubleshooting