This guide will help you set up Merge with a Current Device (any LumiNode device), but the same ideas apply to any node that is capable of merging RTTrPL and sACN or Art-Net.
For a guide for Luminex DMX devices, please refer to:
[Merge Setup Guide - Legacy Devices](https://scribehow.com/shared/Merge_Setup_Guide__Legacy_Devices__JR8neRVqSkqmsxniT56YAQ)
Blacktrax servers output RTTrPL, which stands for "Real-Time Tracking Protocol - Lighting". This is a lighting protocol, similar to sACN and Art-Net, that provides movement data to the light so it can track in real-time.
The Node merges RTTrPL with sACN or Art-Net so both the lighting console and Blacktrax can send data to the lighting fixtures.
Merge is a setting that determines whether the lighting fixtures receive Blacktrax data from the node. This setting is controlled by the lighting console.
1
Connect the Blacktrax server's RTTrP/L port to the RTTrPL network/VLAN on the switch. Connect the lighting node to the same lighting network/VLAN.
The RTTrP/L port is set up to be compatible with the node's IP address if it has a 10.x.x.x address or 2.x.x.x address. If not, change the node's IP address and subnet mask to be compatible with RTTrP/L.
Do not change the IP address of any pre-configured NICs on the servers.
If a new IP address needs to be added to a NIC, go to Network Connections > right-click the NIC for its Properties > IPv4 > Advanced > Add a new IP address.
2
Type the node's IP address into Microsoft Edge.
This is the home page of the node.
3
LumiNodes use Process Engines to send data from the source to the fixture.
Select the process engine that needs to be configured.
4
Change the Mode to X-Fade.
This will provide an option for a second input source.
5
Change the first protocol to either Art-Net or sACN. This depends on what protocol the lighting console is outputting.
To change the protocol, uncheck the checkbox.
6
Select a new protocol: sACN or Art-Net
7
Specify the sACN/Art-Net Universe for this output.
The Source IP does not need to be set, and can be left at 0.0.0.0. The node will respond to any data from the selected protocol that it receives.
If there are competing sources of data (ex. multiple lighting consoles) the Source IP can be specified to prevent conflicting data.
Once completed, click on the second input.
Note: sACN starts at Universe 1, while Art-Net and RTTrPL start at Universe 0
Example Merging setup for outputting Universe 10:
If using sACN, set: sACN Universe 10, RTTrPL Universe 9
If using Art-Net, set: Art-Net Universe 9, RTTrPL Universe 9
8
Select RTTrPL.
9
Specify the RTTrPL Universe for this output.
There's no need to set an RTTrPL Source IP since there will not be any conflicting data (unless there are multiple BT systems). If the Source IP is specified to the Main server, then the data from the Backup server would not be recognized.
The Merge Channel is a channel/fader on the lighting console that controls the merge level between RTTrPL and sACN/Art-Net.
If this Merge channel is at 0, then Source 1 (sACN/Art-Net from console) is in full control of the lights. If Merge is at 100% (or 255), then Source 2 (RTTrPL) is in control of the lights.
10
In the center, specify the Merge channel.
Tip! There is an option to fade between 0% to 100% Merge. This produces a smooth transition from the position set in the lighting console to the tracked target.
11
To edit the X-fade control source, click the gear.
Pick the correct protocol being used to control Merge, then the Merge Channel's Universe, then the Source IP (this can be left open).
12
Once completed, click "Update"
13
Select the preferred output for this node.
If sending data directly to the fixtures, select DMX.
If sending data to another node, then select either Art-Net or sACN.