Closed GoogleCodeExporter closed 9 years ago
This issue is now fixed in v2.2.1. The delay and the servo move start together.
Once the delay runs out, the next command is executed, no matter how long or
short the actually servo move is. This is what the docs imply.
Original comment by brian.schmalz
on 21 Sep 2013 at 3:17
This issue was closed by revision r267.
Original comment by brian.schmalz
on 21 Sep 2013 at 7:11
Original issue reported on code.google.com by
brian.schmalz
on 21 Sep 2013 at 3:17