The Axes section of the PositionReceiver Device editor is used to create PositionAxis objects which control the movement of individual screens or props along each axis.
Axes are discrete objects themselves, but can be automatically created by reading the axis data the automation system is sending to Disguise software.
To create a PositionAxis object:
-
Select the + button within the Axes section of the PositionReceiver Device editor, type the name of the new object into the text field and hit Enter.
-
Click the Create Axes button to automatically read the incoming axes from the Automation driver.
Or alternatively;
Configuration
Axis ‘Engage’ and ‘Disengage’ options. Allows the user to allow/disallow stage objects being updated in the visualiser. Can also be used during calibration to prevent automation data passing through to the stage objects.
The unique identifier for the axis normally being sent by the automation system. In r14.2 onwards you shouldn’t have to edit this field.
The Screen that the automation is affecting, ie Surface 1.
Which property of the stage object will be automated. E.g. offset.x, offset.y, offset.z, rotation.x, rotation.y, rotation.z.
Allows the user to switch on/ off the graphing/ monitoring of incoming packet data (position/ velocity) and filtered position data.
Range
Maximum/ Minimum Input: Set the Min and Max Input in Disguise software to the real world values coming into the software from the automation system. The set button for Maximum and Minimum Input fields can be used to mark the in and out positions (range) of the automated object. This will reference the current Input Value and therefore when pressed it will paste the current input value into the field. Therefore, making it easier to set these values. Disguise software works in metres and degrees so the user should set appropriate scaling if the received values are not in metres.
The Minimum and Maximum Output fields allow the user to scale the input range to a local range in the visualiser.
Wrap input allows the user to specify that the automated object has rotary motion and the data will wrap. For example, a revolve going from 0-359 and wrapping back to 0.
Filter
Default - Off
When switched on, filter parameters override the parent devices parameters.
Minimum change needed before updating output value. This helps when data has unwanted movement when intended to be static. 0 means no threshold (disabled).
Number of samples to filter. Use 0 to disable. More samples will introduce higher latency with more smoothing effect. Fewer samples will introduce less latency with less smoothing effect.
Number of time samples to filter. Use 0 to disable. More samples will introduce higher latency with more smoothing effect. Fewer samples will introduce less latency with less smoothing effect.
Smoothing factor %. Higher values will smooth the data more but will increase latency and therefore the need for prediction
Velocity
This is for prediction and determines the method for calculating the speed between samples within Disguise software in order to predict the position ahead of time. When in Calculate mode, Disguise will calculate the speed between the latest and previous packet. When From Packet is selected, the speed information should be received within the packet itself.
Please note: Note that the velocity units will be calculated/ received in the units in which the source is sending position and/ or velocity. E.g. If the source is sending position/ velocity in mm/s2 then the velocity is calculated in mm/s2 or when From Packet is selected, the velocity received would be in mm/s2. Therefore, any scaling (min/ max values for input/ output) is applied after the velocity prediction step. The scaling is used in order to scale input values into metres which is what Disguise uses. Disabled sets velocity to 0 and consequently turns prediction off.
Updates only when in Calculated or From Packet modes and displays the velocity that is being calculated/ received from the automation system for the axis.
Prediction
When switched on, prediction uses the bias property to predict tracked positions at a future time.
Compensate for time latency between received data and projector output. Use 0 to disable.
Adjust
Allows the user to offset the position of the object relative to the incoming position data.
Values
The values of the incoming data, from here one can determine the Min and Max Input of data.
The output including any prediction.
Scaled output velocity comparing the Input and Output levels.
The difference between the incoming position data and output position data. For good output should be twitching between -0 and 0 value.
The field displays the average frequency that automation data is being received for the axis. It’s important to monitor this field and ensure that the rate is at least 30 Hz or higher and consistently at the rate specified by the automation system. I.e. avoid large swings/ fluctuations in the input frequency.
