Thread: Using WPILib
View Single Post
  #2   Spotlight this post!  
Unread 19-01-2008, 17:15
dcbrown dcbrown is offline
Registered User
AKA: Bud
no team
Team Role: Mentor
 
Join Date: Jan 2005
Rookie Year: 2005
Location: Hollis,NH
Posts: 236
dcbrown has much to be proud ofdcbrown has much to be proud ofdcbrown has much to be proud ofdcbrown has much to be proud ofdcbrown has much to be proud ofdcbrown has much to be proud ofdcbrown has much to be proud ofdcbrown has much to be proud ofdcbrown has much to be proud ofdcbrown has much to be proud of
Re: Using WPILib

The Getdata in WPILIB is done at interrupt level as part of the system clock. This prevents the master processor from shutting you down and allows the user code to loop essentially forever without having to periodically check for new rx data packets.

As part of the same system clock interrupt service routine, when autonomous period ends, then the code forces a warm reboot and this automatically kicks the code out of autonomous code and restarts the code back through main. So the autonomous routine should be able to loop forever and appear never to return on its own via a coded return path.

At least that is how I remember it when I last looked at it.