01-30-2007 11:07 AM
01-30-2007 12:17 PM - edited 01-30-2007 12:17 PM
Message Edited by AnalogKid2DigitalMan on 01-30-2007 11:17 AM
01-31-2007 02:07 AM
02-13-2007 05:23 AM
As far as I remember (*) , the FP-QUAD will measure the velocity by counts during a fixed time slot. The maximum time is (was?) 26.??ms.
Your resolver has 1024 pulses (I assume 2 pulse streams with 90° shift) , the QUAD will count pulse edges, so you get 4096 counts per revolution. Together with the integration time (26.??ms), you get a resolution of 38.15 counts/s (See manual of the FP-QUAD) or an error of +/- 0.559 RPM
Of course you can read the 32bit counter of the QUAD in a user defined time periode and calculate the velocity.
If you have real slow movements, you can measure the time between each pulse. The accuracy will depend on the quality of your resolver and the resolution of your timer, however I think this couldn't be done with the FP-QUAD.
* My last task with FP-QUAD was 4 years ago, maybe new firmware and driver give you more choices now
02-13-2007 07:05 PM
02-14-2007 08:46 AM
To measure velocity you measure counts per time. (OK, that was nothing new 😉 )
If you have to use a FP-QUAD read the 32bit? pulse counter on a regular base (100ms) and calculate the counts per time 'by wire' different integration times can be realized like this. Care must be taken if you over or under run the counter (don't use the zero pulse, if you can avoid it) but one pulse per 10ms and 2^31 pulses before that happens gives you a lot of monitoring time... BUT it will arrive :-0
However I would use a timer module and measure the time between pulses (if direction doesn't care, or is determed by a QUAD, hey, you can use your sensor output on two module inputs).