SP command happens at end of <duration> not at beginning

corba22 / eggbotcode

Automatically exported from code.google.com/p/eggbotcode

0 stars 0 forks source link

SP command happens at end of <duration> not at beginning #66

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

The docs give the impression that the servo move should happen at the beginning 
of the <duration> (or delay) period. Currently they do not. Currently, the 
delay executes, and then the servo moves.

Original issue reported on code.google.com by brian.schmalz on 21 Sep 2013 at 3:17

GoogleCodeExporter commented 8 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

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

This issue was closed by revision r267.

Original comment by brian.schmalz on 21 Sep 2013 at 7:11