View Single Post
  #2   Spotlight this post!  
Unread 19-01-2009, 13:29
jerry w's Avatar
jerry w jerry w is offline
Free Agent Mentor
no team (Team Krunch)
Team Role: Engineer
 
Join Date: Nov 2003
Rookie Year: 2002
Location: dunedin fl
Posts: 113
jerry w has much to be proud ofjerry w has much to be proud ofjerry w has much to be proud ofjerry w has much to be proud ofjerry w has much to be proud ofjerry w has much to be proud ofjerry w has much to be proud ofjerry w has much to be proud ofjerry w has much to be proud of
Re: Issue with Color Tracking Example (C/C++) and with Counters, Encoders, and Ultras

Quote:
Originally Posted by BradAMiller View Post
There is also a problem that was discovered in the FPGA that causes reading the period or rate on an encoder or counter to be incorrect. It also causes unreliable readings from ultrasonic sensors using the Ultrasonic class. We are currently working on a fix for the problem and it will be in the next update. If you are using these features of the library, continue planning on using them but be aware that your results might not be correct until the next update.

Counters and encoders are correctly reporting counts (just not time related values). So using an encoder to measure distance is not a problem.

Since the encoder/counter/ultrasonic problem is in the hardware, it applies to LabVIEW programs as well as C/C++ programs.
i can confirm that this problem exists in labview. we spent several hours Sunday trying to understand why the rate occasionally reads zero, when the encoders were spinning at a constant speed.

we did use the distance value from the encoders to create our own speed values. simply remember the time and the distance value using feedback nodes from one reading till the next.


jerry
__________________
Happiest when people tell the truth... However, I am blessed with many friends.