Command: *motion:

Command: *motion:
Adjusts the unit's motor control (freeze, for example). Note that the unit's actual ability to move could differ from this. For example, a unit's motor control may be turned on (set to 1), but it may still be frozen because of motor interference, or because its power is off.

Usable in: Programs, Commands

Parameters

 * 1=Motor systems active; unit able to move (default)
 * 0=Motor systems disabled; unit frozen


 * setting
 * Default parameter. The value to which the control is to be set. The following values must be recognized; additional options may also be available.
 * Object values are permitted - for example, a Core that allowed different parts of the body to be activated by separate controls could allow.


 * fallback
 * The value to be used in the event that the specified setting is not recognized. For example, a Core might be designed that has a "Slow Motion" mode, denoted "SM". A device designed to talk to that Core could allow for the possibility of talking to a Core that does not have that mode by sending, thereby ensuring that such a Core will still recognize this as a motors-on setting. Default value is 1; only 0 and 1 are legal.

Expected Action by Core
When a setting other than 1 is selected, the unit's ability to move should be partially or entirely restricted. Setting to 1 should restore full movement capabilities, unless other factors prevent this.

Response(s) Expected
None, but an updated message is likely. (It may not happen, though - if the unit was already unable to move when 0 was sent, no message needs to be sent.

Examples
0 {"setting":"1"}

Typical usage
This message would be sent by an Access Panel or Remote Control to freeze or unfreeze the unit. It should NOT be sent by something like an interference generator or a physical restraint, as these do not actually change the setting of the unit's controls. Instead, such devices should use.

Implementation Details: ACS
Minimum Level:

Other constraints: