View Single Post
  #7   Spotlight this post!  
Unread 13-03-2006, 00:02
P1h3r1e3d13's Avatar
P1h3r1e3d13 P1h3r1e3d13 is offline
Unregistered User
FRC #0295
Team Role: Alumni
 
Join Date: Jan 2006
Rookie Year: 2006
Location: San Diego/Granite Bay
Posts: 46
P1h3r1e3d13 is an unknown quantity at this point
Re: Pointers in EasyC

Well, sort of. I want to show how far left or right or up or down the camera is pointing (relative to the bot) using multiple OI LEDs per axis. (Something along the lines of an LED for "too far left," an LED for "locked on," and an LED for "too far right.") That way we can manually turn the bot to point at the goal by centering the pan, and tell if our shooter's in range by the tilt angle.

I thought I knew how to do it using the capture command's pan and tilt outputs, but when I tried, it didn't seem to work, and I don't know enough about the camera and EasyC's camera commands to tell why.

Do the servos have to be plugged into the camera board to get those values? Does servo tracking have to be enabled? Why are the camera's outputs pointers? And if the camera can get servo outputs from the controller (as opposed to the camera board), how can I?

That last I originally wanted to know in order to emulate what the default code does with the LEDs. Then I learned that the default code's LEDs just show the OI inputs, so it's mainly just a curiosity now.

Is that enough info, or way too much?


Edit: No longer just a curiosity, as I found out the "hard" c camera code reads PWM output values, and I will probably need to to make our EasyC camera code work. How does "hard" c do it?

Last edited by P1h3r1e3d13 : 13-03-2006 at 23:02. Reason: New info