Closed AndyLindsay closed 6 years ago
It looks like the problem was actually that the Ping))) library needs 1 ms pauses.
The ping following application wasn't waiting long enough between ping))) calls, caused varying incorrect measurements in ping nav applications. This was not seen in abdrive (not 360) applications because delays in abdrive ensured that we wouldn't see the problem.
All delays re-removed from abdrive360 and servo360 speed calls.
Closed Here: https://github.com/parallaxinc/Simple-Libraries/tree/10b0a884526f01020b3d7c42dbe753ec2eaa11ab
...but always make sure to get the latest here: https://github.com/parallaxinc/Simple-Libraries/tree/Community
I've already hunted for this one a few times. For now, make the drive_speed call for a given servo remember the pulse count, and only update if the pulse count has changed.