The legalities of problems with motors

When issuing a move command from a script in the scripting engine, the following situations will cause an exception to be thrown:

• The global abort was been issued after this script was started.

• The motor is already moving.

• The move would exceed the motor's software limits.

• The motor has a child motor that is currently moving.

• The motor is locked.

The following errors will cause the scripting engine to issue a global abort.

• A sibling motor needs to be moved back to its last good position, but the move command threw an exception for one of the reasons listed above.

• The scripting engine receives a message indicating that a motor has completed its move abnormally,

After successfully issuing a move command, the script will continue until the wait_for_devices function is called. The wait_for_devices command will return and allow the script to continue only if the device completed its move normally. If the device has not completed normally, an exception will be thrown with the reason that it failed.