Quote:
Originally Posted by ayeckley
Probably a correct assessment. Will give it Deeper Thought.
|
Using LabVIEW, our initial application of the workaround seems to result in the "Rate" output scaling based upon the value of "DistancePerCount" (for a given angular velocity using an E4P and 2X decoding). This behavior is nonintuitive and isn't suggested by the Help File for the WPI_EncoderGet.vi even when reading between the lines. We know we didn't accidentally wire into the "Distance" output since the output value is constant rather than accumulating. We haven't had time to test the full range of conditions that this occurs under; that will have to wait for after ship date at this point. It's totally possible that the same thing happend before we applied the workaround; there's no obvious connection between the two in looking at how the workaround was accomplished. It's also totally possible that we accidentally varied some other condition without realizing it and noticed something that wasn't really there at all.
Has anybody else seen this? If this is known behavior then we won't invest any time trying to study it, but if nobody else has experienced it then we probably need to dig deeper after ship date. Thanks...