F4 (Mo-Sys)

Mo-Sys are camera tracking and robotic tracking systems, this IO connection is an input and output for the tracking data.

*This is only available for Virtual Production, and Full license.

!Map/Node Outputs can be used not only to send the F4 protocol to different render engines / media server.
This output stream from SP can also be used to drive the physical remote heads, robotic rail and robotic jib systems from Mo-Sys.

There are two different IO-Connections for the F4 protocol from Mo-Sys.

• UDP – F4 (Mo-Sys)
• Serial – F4 Serial (Mo-Sys)
  

Multiple type of maps are available:

• Star Tracker
• Axis Position
• Axis Rotation
  

These IO also provides Sender and Receiver board nodes.

*Check the Calibration/Allignment Tool here.

*Monitor the timing of the incoming data packages here.

MoSys Setup

Sender

!By changing one of the parameters, please click on the refresh icon:

Receiver

!By changing one of the parameters, please click on the refresh icon:

MoSys Setup (Serial)

Sender

!By changing one of the parameters, please click on the refresh icon:

Receiver

!By changing one of the parameters, please click on the refresh icon:

Maps In

Start Tracker Input

A Map Input, typical used on a Camera object.

*Multiple options can be enabled or disabled if needed.

*ID “-1” is working for all used ID´s. (“listen” to all)
Defining a ID like “3” means, that this input only works/parse the data if the sending ID is equal.

Axis Position Input

The F4 protocol is supporting additional linear axis for special needs like rails, crane positions etc.
A single axis can be linked to an object coordinate parameter.

The following axis types are supported:

• X Coordinate (Which is equal to the raw StarTracker X location parameter)
• Y Coordinate (Which is equal to the raw StarTracker Z location parameter)
• Z Coordinate (Which is equal to the raw StarTracker Y location parameter)
• Dolly Crane Position
• X String Encoder
• Y String Encoder
• Head Y Position
• Head Z Position
  

*ID “-1” is working for all used ID´s. (“listen” to all)
Defining a ID like “3” means, that this input only works/parse the data if the sending ID is equal.

Axis Rotation Input

The F4 protocol is supporting additional angle/rotation axis for special needs like turntables, crane pan etc.
A single axis can be linked to an object coordinate parameter.

The following axis types are supported:

• Head Pan (Which is equal to the raw StarTracker Pan parameter)
• Head Tilt (Which is equal to the raw StarTracker Tilt parameter)
• Crane Pan (Turn)
• Crane Tilt (Jib)
• Turntable Rotation
• Head Roll (Which is equal to the raw StarTracker Roll parameter)
  

*ID “-1” is working for all used ID´s. (“listen” to all)
Defining a ID like “3” means, that this input only works/parse the data if the sending ID is equal.

Map Out

To send from a camera object the Mo-Sys F4 protocol.

!Please note, that per IO-Connection / port just one map output can be used.
If for the same IO connection already have a node output/sender, please create an other IO Connection with a different port.

Nodes

Two maps are available.
One for receiving all parameters, one for sending.

!Please note, that per IO-Connection / port just one note output can be used.
If for the same IO connection already have a map output, please create an other IO Connection with a different port.