Nodes

A Nomad will not output NET2.

You are correct that our Net2 nodes where made by PathWay. We do not and will not support sACN/NET3 on these devices.

You are welcome to contact Pathway directly.

The CEM+ utilities a completely different hardware and was made completely in house.

Marcus

marcusbirkin said:

You are correct that out Net2 nodes where made by PathWay. We do not and will not support sACN/NET3 on these devices.

You are welcome to contact Pathway directly.

In my case, my 2 port nodes (I have 4)  say "ETC" on the front.  Not "Pathway".

I believe they are were not manufactured by ETC, who instead opted to have Pathway versions adapted for ETC use.

So why would you NOT support an ETC product that can otherwise be used on an sACN network ?.

Steve Bailey

Lighting Director

Brooklyn Center for the Performing Arts at Brooklyn College

The ETC NET2 gateway was manafactured and sold for use with NET2. It does this.

The ETC NET3 gateway was manafactured and sold for use with NET3. It does this.

As an added bonus, and for free, the NET3 Gateway (old revision) can be turned into NET2 mode.

Hi Steve,

To clarify a bit, Marcus is correct that the ETCNet2 nodes are designed for use only with Net2 systems. Pathway was the OEM for the hardware and the software was an ETC version jointly developed.

When we developed the Net3 versions, we chose to have a mode that allowed the gateways to operate in Net2 mode to help ease that transition and provide a more up-to-date product that could be switched from the legacy Net2 protocol to Net3 (sACN) when the time came. A few years ago, a change in physical parts drove the need for a "Net3 Only" version of the Net3 gateways because the new component didn't support the legacy Net2 protocol.  These versions do not allow themselves to be flipped into Net2.

So with that history lesson, we come to today. Since we do not actively manufacture or develop software for the original Net2 2-Port gateways, we do not have a mode that would allow it to send/receive sACN data. Because the hardware is similar enough to Pathway's version of the same type, users have reported that they have been able to load Pathway's code that supports sACN. Because you would be loading code that was not manufactured nor tested by ETC, ETC cannot support the product in that state. If asked, we will advise you to restore the ETC code as the first step of troubleshooting an issue.

It basically comes down to if it has ETC's logo and ETC's code, we can support it.
If it has ETC's logo and someone else's (Pathway or whomever else's) code, we cannot support it.
If it has someone else's logo, we cannot support it, though we might have advice from other field stories. :)

Thanks Kirk, much clearer.

SB