Board Thread:Questions and Answers/@comment-2.26.120.110-20121210204911/@comment-86.152.15.218-20121214174856

I don't have a definitive answer, but in trial and error, I found I needed at least a 10 TICK pause between setting and resetting a signal to a frame motor for it to step "reliably", particularly if moving a lot of steps. It may have been issues with not getting enough bluetricity to keep the motors charged enough to keep stepping and possibly related to the large number of blocks (almost 1000) I'm moving. To be on the safe side, I think I even increased the delay to 15 TICKS. But, your milage may vary. Best idea, build the delay factor in as a constant which is then used throughout your code, so you can then tweak it easily to be shorter and shorter until it fails, then take it back to one tick longer.