HMC Driver
このコンテンツはまだ日本語訳がありません。
The HMC Driver receives axis position data from systems using the Hudson Motion Control (HMC) protocol, originally developed for Hudson scenic and stage automation systems. The protocol (header HATx) can carry position, speed, motor-status, and cues-running information — Designer consumes only the position value for each axis.
In most cases, the default settings are suitable; adjustments are only required when your automation system or network uses non-standard ports, IP filters, or multicast addressing.
The HMC Driver is used when Disguise needs to receive axis position data from hardware that transmits using the HMC protocol. It enables real-time positional input from Hudson-style automation systems, which can be mapped to PositionAxis objects to drive content alignment or screen positioning.
This driver is particularly useful when:
- Integrating Hudson-controlled scenic automation hardware into a Disguise workflow.
- Receiving continuous axis position updates over UDP.
- Driving content alignment or screen positions from real-world stage motion.
- Monitoring or validating HMC data during setup or troubleshooting.
As HMC is lightweight and network-friendly, it is well suited for real-time automation where consistent, low-latency position updates are essential.
Driver Properties
Section titled “Driver Properties”
This driver listens on UDP port 9699 by default.
Port
The UDP port on which the driver receives data. Set this to match the port configured on the sending device or controller.
IP filter (optional)
Restricts incoming data to a specific source IP address. Useful when several sources are present on the network, or to isolate a single sender. Leave blank to accept data from any IP.
Multicast address (optional)
The multicast group address used by your system. Only required when the sender is configured for multicast — enter the exact multicast address used by the emitter. Leave empty for unicast or broadcast configurations.
Developer Documentation