Thread: Mapping VEX I/O to FRC code
View Single Post
  #1   Spotlight this post!  
Unread 13-05-2006, 19:33
Doug Leppard's Avatar
Doug Leppard Doug Leppard is offline
Registered User
FRC #1902 (Exploding Bacon)
Team Role: Engineer
  
Join Date: Apr 2003
Rookie Year: 2003
Location: Orlando
Posts: 435
Doug Leppard has a reputation beyond reputeDoug Leppard has a reputation beyond reputeDoug Leppard has a reputation beyond reputeDoug Leppard has a reputation beyond reputeDoug Leppard has a reputation beyond reputeDoug Leppard has a reputation beyond reputeDoug Leppard has a reputation beyond reputeDoug Leppard has a reputation beyond reputeDoug Leppard has a reputation beyond reputeDoug Leppard has a reputation beyond reputeDoug Leppard has a reputation beyond repute
Send a message via AIM to Doug Leppard
Mapping VEX I/O to FRC code
I want to practice and adjust our FRC code using the VEX. Do you know of a document that explains the mapping of IO that is used in FRC and correlates FRC IOs to the VEX IOs?

When I complied the FRC code in the VEX the following variables were not defined:
'p1_x' has not been defined
'p1_y' has not been defined
'p3_wheel' has not been defined
'p1_wheel' has not been defined
'p1_wheel' has not been defined

Also on the VEX it says interrupts, how is that mapped to the FRC code. There is a lot I don't understand between the two.
__________________
Doug Leppard