|
ControllerState Enumeration
Description
The ControllerState enumeration represents the operational state of the motion controller.
If Controller.State is not OK, then the controller is not in a fully functional state and some methods and properties will fail if accessed.
Version History
Introduced in MPX 2.0.
Enumeration Values
| |
| ControllerState |
Meaning |
| OK |
The controller is operating normally. |
| FirmwareInvalid |
The controller firmware is invalid. Call Controller.LoadFirmwareFromFile to load new firmware. |
| FirmwareMismatch |
The controller firmware is not compatible with the current MPX. Call Controller.LoadFirmwareFromFile to load new firmware. |
| FirmwareMissing |
The controller firmware is missing. Call Controller.LoadFirmwareFromFile to load new firmware. |
| SynqNetTopologyMismatch |
The SynqNet topology does not match the expected topology (stored in dynamic memory). During the first network initialization the controller stores node identification information (manufacturer, product, and unique values) into its dynamic memory. To correct this problem, either change the network topology to the original configuration or clear the controller’s memory by calling Controller.Reset. |
| SynqNetTopologyMismatchFlash |
The SynqNet topology does not match the expected topology (stored in flash memory). During the first network initialization the controller stores node identification information (manufacturer, product, and unique values) into its dynamic memory. Later, when SynqNet.TopologySave is called, the topology information is stored into flash memory. To correct this problem, either change the network topology to the original configuration or clear the controller’s memory by calling SynqNet.TopologyClear and then calling Controller.Reset. |
| SynqNetErrorState |
The SynqNet network is in an error state. This indicates that a problem occurred during the SynqNet initialization sequence. To correct the problem, try calling Controller.Reset. |
| SynqNetCableLengthMismatch |
SynqNet initialization has failed because a cable length is detected that lies outside minimum and maximum values set by an MPI application. This problem may occur with cables of the correct length that are about to fail. To correct the problem, either replace the cables with good cables of the proper length, or clear the cable length values by clearing the SynqNet topology via SynqNet.TopologyClear, then by calling Controller.Reset and then optionally SynqNet.TopologySave if it desired for the topology to still be saved. |
|
See Also
Controller Object
State
FirmwareLoadFromFile
Reset
SynqNet Object
Initialize
Shutdown
TopologyClear
TopologySave
|
