Navigator Driver

このコンテンツはまだ日本語訳がありません。

The Navigator Driver receives axis data from FTSI Navigator motion control systems.

Navigator sends real-time positional and velocity information over UDP, which Disguise converts into automation axes. The driver requires the incoming data to follow a specific packet structure to ensure correct parsing and axis updates.

Uses

Use the Navigator Driver when integrating FTSI Navigator motion control systems with Disguise. The driver converts real-time positional and velocity data into automation axes, allowing physical movement to drive virtual objects, scenic elements, or synchronised media playback.

This driver is especially useful when:

Receiving live axis data from FTSI Navigator-controlled winches, hoists, or tracked systems.
Synchronising virtual objects or content with physical stage machinery.
Visualising Navigator motion data inside Designer for rehearsal or alignment.
Driving complex automation behaviours based on continuous motor position and velocity.
Testing or validating Navigator output formatting during setup or troubleshooting.
Handling multi-axis systems where several motion channels are streamed in a single packet.

As Navigator supports high-frequency updates, this driver is well suited for accurate, real-time motion tracking in media-driven or interactive production environments.

Driver Properties

Navigator Driver

This driver listens on UDP port 8000 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.

FTSI Navigator UDP Packet Format

Designer requires the Navigator system to send data in a specific format. Each axis should send data in the following format.

ID:POS,VELOCITY;

ID = Axis ID

POS = Axis position as a floating point number

VELOCITY = Axis velocity as a floating point number

Example (single axis)

1:-24.034,1.323;

Example (multiple axes in a single message)

Navigator messages may contain multiple axis entries in sequence:

ID:POS,VELOCITY;ID:POS,VELOCITY;ID:POS,VELOCITY;.....

1:-24.034,1.323;2:5.346,12.098;3:9.064,2.511;

Developer Documentation