CONGO as a guest in existing networks

Check IP addresses and ensure the Congo has a unique IP, then plug it into the network and turn on the appropriate DMX-over-Ethernet protocol(s).

- Congo and Eos support the same range of DMX-over-ethernet protocols.

- If they use the ETC default IP address ranges, the Congo default IP range will be fine even with the Eos console system left connected, though it's good practice to turn the Eos system off so you can't get unexpected levels from it.

In the case of other consoles, you will first need to check whether Congo supports the DMX-over-Ethernet protocol(s) in use. If Congo supports those protocols, then all is well.
If Congo doesn't support them, you'll need to use appropriate DMX-input devices and the ports on the back of the console to get the data onto the network.

In general, the important factor is the DMX-over-Ethernet protocol(s) being used, rather than which specific console is normally used in the host system.

Check IP addresses and ensure the Congo has a unique IP, then plug it into the network and turn on the appropriate DMX-over-Ethernet protocol(s).

- Congo and Eos support the same range of DMX-over-ethernet protocols.

- If they use the ETC default IP address ranges, the Congo default IP range will be fine even with the Eos console system left connected, though it's good practice to turn the Eos system off so you can't get unexpected levels from it.

In the case of other consoles, you will first need to check whether Congo supports the DMX-over-Ethernet protocol(s) in use. If Congo supports those protocols, then all is well.
If Congo doesn't support them, you'll need to use appropriate DMX-input devices and the ports on the back of the console to get the data onto the network.

In general, the important factor is the DMX-over-Ethernet protocol(s) being used, rather than which specific console is normally used in the host system.

Thanks for your answer, Richard. Seems just a little bit too simple ;-)

I am worried about merging DMX data.

The theatre wants to keep its in-house desk alive (not only for safety reasons, but they also have to run other parts of the show with their desk). How is a second DMX-over-Ethernet-source handled? HTP? – (which would mean there had to be a All-Movers-to-0-Values-Cue in both desks)

Thanks,

Mario

It depends on which DMX-over-Ethernet protocol(s) they are using, and the receiving equipment at the other end as each has quite different capabilities.

Most protocols and hardware support HTP-merge between sources, but the number of sources (and whether they can be prioritised) depends on the protocol and receivers.

For example, ArtNet is limited to a maximum of two sources - so you may not be able to have an online backup, while others (eg ETCNet2, most Streaming ACN receivers) allow for a large number of active sources per DMX address or per Universe.

Generally, consoles send either "0%" or "Nothing" (if supported*) to unpatched DMX addresses, so usually the best way to handle sharing a network Universe between multiple consoles is to unpatch the DMX addresses that should be handled by the 'other' console(s).

If certain fixtures need to be handed back and forth between the consoles, your notion of an "Set to Zero Output" cue/preset is the easiest way to handle it.

*ETCNet2 and the Net3/ACN version of Streaming ACN support the idea of sending "Nothing" to specific addresses, while (eg) ArtNet and Avab protocols don't.
The difference between the two is visible when consoles shut down or disconnect - "Nothing" will leave addresses where they were, while "0%" will obviously snap them to 0.

Thanks for that.

Now it's only gonna be a hard time convincing the local operators to allow a guest console sending data into their network.:-/