Go to Post Kit wheel? Someone probably has them. N-tooth IFI sprocket? You might get lucky. Part Made By A Local Company When You're Competing 800 Miles Away? Bring three. - Billfred [more]
Home
Go Back   Chief Delphi > Technical > Programming
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
 
Thread Tools Rate Thread Display Modes
  #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
  #2   Spotlight this post!  
Unread 13-05-2006, 23:23
Cuog's Avatar
Cuog Cuog is offline
Registered Linux User: 390661
AKA: Alex
FRC #0422
Team Role: Mentor
 
Join Date: Nov 2005
Rookie Year: 2004
Location: Richmond, Virginia
Posts: 852
Cuog has a reputation beyond reputeCuog has a reputation beyond reputeCuog has a reputation beyond reputeCuog has a reputation beyond reputeCuog has a reputation beyond reputeCuog has a reputation beyond reputeCuog has a reputation beyond reputeCuog has a reputation beyond reputeCuog has a reputation beyond reputeCuog has a reputation beyond reputeCuog has a reputation beyond repute
Send a message via AIM to Cuog
Re: Mapping VEX I/O to FRC code

What are you using for both, EasyC for vex, for FRC or MPLab all the way, with these different options the coding and structure are different so we will need to know what your using b4 we can really help.
__________________
KK4KQO
http://voltair.us
Too many projects, too little time.
  #3   Spotlight this post!  
Unread 14-05-2006, 06:45
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
Re: Mapping VEX I/O to FRC code

Quote:
Originally Posted by Cuog
What are you using for both, EasyC for vex, for FRC or MPLab all the way, with these different options the coding and structure are different so we will need to know what your using b4 we can really help.
Thanks. It is MPLab all the way. I want to play with our FRC code on a VEX, try various sensors on the VEX before we move it to the big FRC bot.
__________________
Doug Leppard
  #4   Spotlight this post!  
Unread 14-05-2006, 02:32
DonRotolo's Avatar
DonRotolo DonRotolo is offline
Back to humble
FRC #0832
Team Role: Mentor
 
Join Date: Jan 2005
Rookie Year: 2005
Location: Atlanta GA
Posts: 6,979
DonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond repute
Re: Mapping VEX I/O to FRC code

Quote:
Originally Posted by Doug Leppard
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
You need to look at what those mean, exactly, and translate that to Vex.

p1_x is OI port 1, the "X" direction. This would possibly translate to Channel 1 on the Vex controller. But, of course, you can define it as Channel 3 (which is "X" on the left joystick instead of the right), or anything else you like.

p1_y might be channel 2

The three "wheel" values are the switches on the little thumbstick on the standard KOP joystick. It is also an analog input (like X and Y) and has no equivalent on the Vex controller. Maybe a good use for Channels 3 and 4 or, with some limits, channels 5 and 6.

As a hint, you'd use the "RX Input" block.

Look at this schematic to help in understanding what the joystick does, and then you can think about how to replicate that functionality on the Vex controller.

Note that the FRC OI is a LOT more versatile than the Vex transmitter.

Don
__________________

I am N2IRZ - What's your callsign?
Closed Thread


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
PIC18F8520 port mapping to VEX microcontroller module. Yuriy Programming 2 28-04-2006 13:11
Using Vex Brain as FRC Coprocessor Tom Bottiglieri General Forum 25 18-04-2006 22:36
FRC/VEX Challenge Rick TYler General Forum 32 05-04-2006 21:54
VEX 2005 = Mini FRC 2004 Joe Johnson FIRST Tech Challenge 12 08-04-2005 17:22


All times are GMT -5. The time now is 23:05.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi