In the previous release 1.2.0.1, if you called the move function while something was blocking the frames' movement, the carriage controller would throw an error message AND abort the program you are running ... then in 1.2.1.0 the move function fixed that issue ... and now you're telling us that you "thought of a better way to do it." so I wanted to remind you not to make the move command work like in 1.2.0.1 ..
My message was very clear, IMHO.
I don't think the terms are intuitive because people will get mistaken. the DRIVE() will "MOVE" with the frames like the carriage engine does while the MOVE() will push the frames while staying put like the carriage DRIVE does ...
I dunno ..