Regardless of which service you are using, the relay mapping is identical.

The concept is this: instead of each audio service having a set of relays with which it is associated, each audio port on the Unity 4000 receiver has a set of relays with which it is associated.

The difference is an important one. Since there are more than 30 audio services available on the Unity 4000 and only 4 audio ports, there is obviously no reasonable way to divide 14 relays among 30 services.

As such, we developed a method whereby whatever service you have selected on a specific audio port on your Unity receiver will have control of the associated relays.

Example: When SR1 is selected on audio port 3, the relays EXPPORT2-1 through EXPPORT2-3 will be controlled by (associated with) whatever audio is present on SR1.
When you retune your receiver's audio port 3 to SR4, now the relays EXPPORT2-1 through EXPPORT2-3 will be controlled by (associated with) whatever audio is present on SR4.

This way, when you retune your receiver's ports around to different channels, you will not need to disable and enable different sets of trigger inputs on your automation system. The triggers you receive for a certain port will always be those that correspond with the audio selected on that port at that time.

Relay Mapping for Full-Form Music Affiliates

Relay Mapping for Affiliates not taking programming from a Full-Form Music service