NOTE: The following 1-port gateway issue was resolved in Eos Family software version 1.9.1 and higher. If you are experiencing this issue, please update to the latest version of software, if able, and check to see if the problem persists.

There have been reports of issues with 1-Port Net3 Gateways running firmware version 4.0.0 (distributed with NCE 4.3.0) running in Net2 mode with Eos/Ion consoles running software versions 1.8.1, 1.8.2, and 1.9.0. After using the console for a period of time without changing any levels within the gateway's configured output range, the gateway stops outputting and its DMX light begins to blink. The gateway holds the look for 3 to 5 seconds and then fades out -- causing any devices fed by the gateway to fade out as well. As soon as the gateway receives a changed level instruction, it comes back online and begins to respond again, returning lights to their previous levels until this process repeats.

To trigger the issue, the following conditions must be true:

The Eos/Ion/Element console must have faders and must be outputting ETCNet2.

A fader affecting a universe the 1-port gateway is not outputting must be moved.

The workaround is to put the 1-Port Gateway into sACN mode and ensure the console is outputting both ETCNet2 (EDMX) and Net3 (sACN) in the patch and in the console settings. To put the gateway into sACN mode, you can use Network Configuration Editor (NCE) version 4.3.0 as follows (or use GCE or Net3 Concert to switch the gateway to ACN mode):

Open NCE.

Go to Network → Connect.

Go to Network → Get Unbound Nodes.

Go to View Node Details.

Scroll left in NCE about 75% of the way across until you see the PROTOCOL column, which will show "EDMX" selected. Click on "EDMX" and select "sACN" from the drop-down menu.

Go to Network → Send Config to Nodes.

This should eliminate the issue. ETC has identified the problem and a solution was implemented in Eos Family console software version 1.9.1.