View Single Post
  #2   Spotlight this post!  
Unread 21-02-2009, 19:17
eugenebrooks eugenebrooks is offline
Team Role: Engineer
AKA: Dr. Brooks
no team (WRRF)
 
Join Date: Jan 2004
Rookie Year: 2001
Location: Livermore, CA
Posts: 601
eugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond repute
Re: AnalogModule->GetAverageValue() gives wrong results if polled too fast

Changing the battery jumper only changes what is wired to
an analog input (8 if I remember correctly) and should not
change whether spurious values occur.

I posted a message about spurious values picked up from
an analog input some time ago, which was clearly a race
condition in the system somewhere. Perhaps your timer
use is clearing the race condition somehow.

When we upgraded to the required updates for the cRIO,
the FPGA and WindRiver, our spurious values went away.
We were reading the analog input directly, not using the
averaging functions.
Are you running the software configuration required by
the team update 12?

Software/Firmware Revision
LabVIEW for FRC Update 3.0a and newer
cRIO FPGA Image FRC_2009_v11.Zip and newer
WPI Robotics Library 3.0.1718 and newer
Driver Station 2009-02-010a3 and newer

Again, our problems with stray analog input values went away
when we installed this software configuration (LabView version
is not relevant when using C++)

Sorry, I don't have time to read your post in detail,
I have to leave town on a trip...

Eugene
Reply With Quote