View Single Post
  #3   Spotlight this post!  
Unread 30-05-2009, 22:43
daltore's Avatar
daltore daltore is offline
Electronics/programming/design
AKA: Aaron Osmer
FRC #3529 (ausTIN CANs)
Team Role: Mentor
 
Join Date: Dec 2007
Rookie Year: 2007
Location: San Antonio, TX
Posts: 272
daltore has a spectacular aura aboutdaltore has a spectacular aura aboutdaltore has a spectacular aura about
Send a message via AIM to daltore Send a message via MSN to daltore Send a message via Yahoo to daltore
Re: VEX programming without transmitter

The enable/disable state is governed by the VEX firmware. Unless you know how to rewrite the firmware, I think you need the transmitter. The timing of the operator controlled mode is syncs itself to the transmitter when it finds a signal, and this is the mode where motor udpates are run because the timing is regulated. Basically, what is called Autonomous() in EasyC is called user_routines_fast.c in the default code, and what is called OperatorControl() is called user_routines.c. The user_routines_fast.c code runs as fast as it is able to, while the user_routines.c code runs once every 18.5 ms. This 18.5 ms cycle is synced to the transmitter's update rate, also at 18.5 ms, when the transmitter is turned on. Because motor signals are also time critical, and update at 18.5 ms. all of the motors signals are handled in user_routines.c regardless of whether or not they're sent in autonomous or operator control. However, user_routines.c does rely on the transmitter, so motors will not run without that code being synced up.