View Single Post
  #6   Spotlight this post!  
Unread 05-09-2011, 10:35
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Custom Controller Info

Seeing as how the cRIO can decode a jpeg with 80,000 pixels in a 20ms control period, it can certainly do a few derivatives. But directly to the issue. Try just plotting the axis value and determine if it is a line, a curve, or other. Also, do you have any documentation on the controller? It isn't uncommon for a supplier to have developer level documents on their site that describe the SW interface or the configurations available.

The initialize value on analysis blocks should receive one True, and then Falses. It is often wired with either a (first run) block or the i==0 expression based on a loop in the program. Depending on the joystick graph, you can probably just use discrete math -- subtract the previous value to get the delta, and then normalize the delta between -1 and 1. I'd assume that the joystick simply adds a scaled value to an accumulated value. Note that this will glitch when/if the DS packet to the robot is dropped.

If you want to post some VIs and screenshots showing how the controller behaves, someone may have other ideas.

Greg McKaskle
Reply With Quote