Need Help? Call us!

[Amanda Morrison]

Team 1020 would like to offer a little help to teams during build season.

Our team has quite a few experienced programmers helping us out. We'd like to help YOU out, too. If you have a question about this year's programming, get a hold of us at the contact below.

If you can't get an answer on the forums, maybe we can help you out! We look forward to hearing from you!

Team 1020
PM: Amanda Morrison or deltacoder1020
email: ammorrison@bsu.edu

[miketwalker]

Team 21 is glad to offer help as well. So, you can send a message my way if you'd like to as well.

AIM SN: miketwalker86
E-mail: miketwalker@cfl.rr.com

[deltacoder1020]

Amanda didn't mention it, but my email is dav@thedevelopersalliance.com, if you prefer to use that instead of PM.

[Astronouth7303]

Heck, I'll try to give suggestions (or just info) if you post a new thread. I try to get one at least once a day and read everything new. I'm sort of new to C (I've done C-like languages). I don't think I'm doing badly, actually .

[tml240]

any of you guys got the receiver working? btw we only got one

[Ken Leung]

Originally Posted by Amanda Morrison

Team 1020 would like to offer a little help to teams during build season.

Our team has quite a few experienced programmers helping us out. We'd like to help YOU out, too. If you have a question about this year's programming, get a hold of us at the contact below.

If you can't get an answer on the forums, maybe we can help you out! We look forward to hearing from you!

Team 1020
PM: Amanda Morrison or deltacoder1020
email: ammorrison@bsu.edu

Wouldn't it be nice, if we can setup a directory of all the teams who are willing to offer help? Then anyone who need help can go to that directory, look up the state they are in, and look at the category they want to seek help about. This would be different from FIRST's team list, because only teams willing to offer help will sign up for this directory. Sort of like the BuzzU website for college students, but for teams to seek help.

Sure beat every team just post a message saying they are offering help. It is too disorganized and too hard to find the right team.

[Jessica Boucher]

::sniff:: I smell an award idea

Word to the wise for whomever does do this - don't let it die. This is a great opportunity for a newer team to find differentiation in the FIRST community, and I would love to see a forum/database like that last for years to come.

-Jessica B

[Ryan M.]

I might talk to the kid on our team who's designing our web site. You may see a post one day about that idea being done...

Of course, he might yell at me and tell me that he has enough to do.

Maybe I'm missing something here, but FIRST already has a "Willing to Mentor" list of teams.

Go to the team locator, click a state, and click "What teams are willing to mentor from this state?" - No need to reinvent the wheel

[deltacoder1020]

then again, adding catagories of help might be nice - i.e. some teams are willing to help with programming, et cetera

[Ian311]

does anybody know what the code variables are for a GC-1000FR joystick???
we have 2 of them hooked up to ports 3 & 4??


Thanks in advanced!!!

[Mark McLeod]

Do you mean like:
p3_x, p3_y, p3_wheel, p3_sw_trig, p3_sw_top
and
p4_x, p4_y, p4_wheel, p4_sw_trig, p4_sw_top

?

[Ian311]

we need the code for the new joysticks.

[Greg Ross]

Originally Posted by Ian311

we need the code for the new joysticks.

Sorry, Ian, but your clarification didn't clarify.

What, exactly, do you need? Do you need some C code with which to read the joysticks? Do you need to know what values are returned when you read the joysticks? What values are returned when you read the funny little "POV hat" thumb cursor thingie? (That's been covered in another thread.)

Give us a clue, and we'll try to help.

[Mark McLeod]

Originally Posted by Ian311

we need the code for the new joysticks.

As in user_routines.c, Default_Routine()

change:

 /*---------- 1 Joystick Drive ----------------------------------------------
  *--------------------------------------------------------------------------
  *  This code mixes the Y and X axis on Port 1 to allow one joystick drive. 
  *  Joystick forward  = Robot forward
  *  Joystick backward = Robot backward
  *  Joystick right    = Robot rotates right
  *  Joystick left     = Robot rotates left
  *  Connect the right drive motors to PWM13 and/or PWM14 on the RC.
  *  Connect the left  drive motors to PWM15 and/or PWM16 on the RC.
  */  
  pwm13 = pwm14 = Limit_Mix(2000 + p1_y + p1_x - 127);
  pwm15 = pwm16 = Limit_Mix(2000 + p1_y - p1_x + 127);

to

 /*---------- 2 Joystick Drive ----------------------------------------------
  pwm13 = pwm14 = p3_y;
  pwm15 = pwm16 = 254 - p4_y; // or p4_y if your motors are rigged to both run forward

?