View Single Post
  #1   Spotlight this post!  
Unread 31-05-2002, 16:51
DanL DanL is offline
Crusty Mentor
FRC #0097
Team Role: Mentor
 
Join Date: Jan 2002
Rookie Year: 2001
Location: Somerville, MA
Posts: 682
DanL is just really niceDanL is just really niceDanL is just really niceDanL is just really niceDanL is just really nice
Send a message via AIM to DanL
Makin' a home-brewn dashboard program, and I need theory help!

Okay, so Ian and I have decided to make our home-brewn Dashboard program (after all, wheres the fun in using someone elses?). Anyways, before we do any programming, we want to make sure we have the theory correct.

Basically, this document describes whats in a Dashboard packet. Now, if I understand it correctly, ANALOG1-7 are the analog inputs on the RC, SWITCH_A, _B are the digi inputs on the RC, and PORT 1/2/3/4 Y-Axis are the raw joystick feedback from the OI?

Now, before we go further, my first question is the x/y axises in the dashboard packet, are these the inputs from the oi, or the appropriate variables in the default code?

Anyways, moving on... So basically, our main question is where do these variables come from? Do they come from the OI master processor, or do they come from the information processed by the PBASIC processor?

Basically, the reason why we want to know is we want to be able to check the processed variables, kinda as if we were debugging them. Now, the diagram on page 5 of the user manual was kinda ambiguous. It appears that it outputs the 'dashboard bits' (analog1-7, switches_a, _b ?) after the processing. Does this mean that we can have the code manipulate the input variables and then use these to view it from the dashboard port? Meaning, say that we wanted to view a PROCESSED pwm output. Could we set an unused Analog input from the RC to the PWM value and thus, be able to view the final PWM output on a dashboard program?

Any clarifications would be helpful
__________________
Dan L
Team 97 Mentor
Software Engineer, Vecna Technologies