Integrated drive, or a PLC plus drives
The standard XMSP path does not add another motion controller. When a PLC is already installed, decide which system keeps the safety circuit and line interlocks, and which one runs the axes.
- Standard pathNo extra motion controller
- Standalone axesButton, UDP, or DMX512
- Existing PLCXMSP can run axes only
- BoundaryConfirmed per project
The standard path does not add another motion controller
The MSP unit combines motion control with the motor drive, while XMatrix handles the sequence. An existing PLC can continue to run the safety circuit, line interlocks, and other machine logic while XMSP runs the axes.
When the PLC should stay
| Site condition | XMSP can run | Stays in the existing system |
|---|---|---|
| Standalone axes triggered by a button, UDP, or DMX512 | Sequence and axis motion | A PLC is not required just to turn the motors |
| A PLC must keep the safety circuit | Axis motion | The safety circuit |
| A large IO map or line interlocks already live in a PLC | Axis motion | Those interlocks |
The existing PLC responsibilities define the system split. When safety and line interlocks remain in the PLC, XMSP can join the machine as a dedicated axis-motion system.
For a standalone machine, start from the trigger
- Buttons and inputs, UDP, and DMX512 are trigger entries, not three controllers.
- Whether a computer remains on site determines online or offline execution and is configured separately from the PLC safety and interlock roles.
- The electrical range of each axis still comes from the stepper, servo, or MSP1001 page.
System responsibilities
Application: motion sequencing and the motor drive should live in one system.
Configuration: whether a safety circuit, a large IO map, or line interlocks must stay in the existing PLC.
Related information
Related pages: MSP hardware, XMatrix software