XMatrix technical documents: tell us how you will use it
When you need a software package, the full command interface, DMX512 notes, the API-SDK, a parameter description, or an example project, send the device and the project conditions. We prepare the documents for that device version and that control method, so the software, protocol, or parameter table is the matching one.
- Software packageMatched to the device version
- Interface notesCommand / DMX512
- API-SDKHeaders and examples
- Parameter notesCheck them on site
Which documents you need
| What you are about to do | Documents you can receive | Read this first |
|---|---|---|
| Install the software, connect the device, and finish commissioning | The XMatrix package, the network driver, the commissioning steps, and the version notes | XMatrix Online or XMatrix Offline |
| Your own program sends motion commands | The full command set, replies, error descriptions, and multi-axis address rules | XMatrix Command Interface |
| Connect a lighting console or a DMX512 system | The channel table, address rules, wiring, and project-mode notes | XMatrix DMX512 Interface |
| Call motion from your own desktop program | The API-SDK, headers, libraries, and a sample project | XMatrix API-SDK |
| Check homing, limits, speed, and protection parameters | The parameter notes for the current software version | Feature and hardware map |
Prepare this before you write
- MSP model, quantity, and the version shown on the software screen.
- Whether you will use Online, Offline, the Command Interface, DMX512, or the API-SDK.
- Axis count, motor type, travel, and how the move is triggered.
- If you already have a problem, attach the error text and a screenshot of that screen.
What you receive
- Documents matched to the device and the software version, so you are not guessing among older versions.
- The package, protocol, parameter notes, or example project for the control method you are using.
- A document version and an update date, so the project file can be checked later.
- Where a compatibility boundary exists, a clear statement of what can be used directly and what needs a project confirmation.
Before you use it
- Software, library files, firmware, and the notes must be versions that match each other.
- IP addresses, ports, and moves in an example only illustrate the flow. Site parameters are checked against the device and the mechanism.
- Back up the project and the current parameters before an update. Prove a production machine on a prototype first.
Request the documents: Open Contact and send the device model, axis count, control method, and what the machine does. If the conditions are not fully settled, describe the current plan. We will judge which set of documents is needed.