Interfacing Two-Wire Partyline to Your Matrix

Two-wire partyline is a simple and cost-effective way of providing communications to a number of users who can share one or two channels. As the name implies, this kind of system ties everyone together with a single cable. The cable goes into a beltpack, which also has a jack for a headset. Each beltpack has a cable to the next beltpack in the chain.

In a single-channel system, everyone speaks and listens to everyone. In a two-channel system, it is possible to create two separate groups. Two-wire partyline actually uses three wires. The wire carries audio, supply voltage, and ground. In a two-channel system, the wire carrying the supply voltage also has a signal superimposed. This signal scheme is usually referred to as ground-referenced. Systems with so-called differential signaling require additional wires but we will not get into that here.

Stand-Alone vs Matrixed Operation

A two-wire partyline system can be used with nothing except a power supply and multiple beltpacks. This is the stand-alone mode of operation. In many cases, it is convenient to connect a partyline to a matrix. That mode of operation provides additional possibilities but in most cases it requires an interface between the two-wire system and the matrix.

Use Cases

Use Case A: Stand-Alone

This is the simplest case, as discussed above. It requires nothing except beltpacks and a power supply. Theexample uses a PS-20 which is specific to the ground-referenced scheme from RTS.

Use Case B: Integration with ODIN

^{Figure 2. Front view of ODIN}

Use Case B: Integration with ODIN

A robust digital matrix in a compact 1RU space, built in OMNEO technology, eedundant power supplies, and energy-efficient design, uses less than 50W of power.

^{Figure 2. Front view of ODIN}

Use Cases C & D: Integration with ADAM / ADAM-M

^{Figure 3. Back of the SSA-324 | Figure 4. Back of DSI-2008}

Use Cases C & D: Integration with ADAM / ADAM-M

ADAM and ADAM-M are modular systems with cards that provide different capabilities. The AIO-16A card is used for connecting analog keypanels. Because the audio uses four electrical wires (plus two for keypanel data), this format is sometimes called four-wire. Two-wire and four-wire cannot be inter-connected without an adapter. RTS has two, the SSA-324 (an analog device) and the DSI-2008 (which has digital signal processing). Figure 3 and Figure 4 show the back of these two converters. The user manuals for these two products explain how the electrical connections must be made.

^{Figure 3. Back of the SSA-324 | Figure 4. Back of DSI-2008}

Use Case E: Integration via OMNEO

^{Figure 5. Back of the StudioTech M45DR}

Use Case E: Integration via OMNEO

It is possible to go directly from a two-wire partyline to high-quality audio over IP. Dante is supported by the OMNEO Matrix Interface (OMI), a card that goes into both ADAM and ADAM-M. Converters are available from several third-party suppliers. This example uses the M45DR from Studio Technologies. Figure 5 shows the back of that device.

The M45DR communicates via the RJ45 connector on the rear. In most cases, it would be connected to an Ethernet switch, which in turn is connected to the OMI-card. Dante eliminates the problem of creating unique analog cables, to connect from one device to another, as would be required in use cases C and D.

^{Figure 5. Back of the StudioTech M45DR}

Two-wire partyline systems can be used in a stand-alone or matrixed configuration. The use cases are summarized in the table below.

Configuration	Matrix	Matrix Card	Converter
Configuration Stand-alone	Matrix N/A	Matrix Card N/A	Converter N/A
Configuration Matrixed	Matrix ODIN	Matrix Card N/A	Converter N/A
Configuration Matrixed	Matrix ADAM / ADAM-M	Matrix Card AIO-16A	Converter SSA-324 or DSI-2008
Configuration Matrixed	Matrix ADAM / ADAM-M	Matrix Card OMI	Converter M45DR

Interfacing Two-Wire Partyline to Your Matrix

Stand-Alone vs Matrixed Operation

Use Cases

Use Case A: Stand-Alone

Use Case A: Stand-Alone

Use Case B: Integration with ODIN

Use Case B: Integration with ODIN

Use Cases C & D: Integration with ADAM / ADAM-M

Use Cases C & D: Integration with ADAM / ADAM-M

Use Case E: Integration via OMNEO

Use Case E: Integration via OMNEO

Search