workaround to upgrade Element 1 address count

Something I want to add: we have an Element 1 console that is able to run Augment3d, so I think this is the newer model, because I've read that the old Element model can't run v3.0.

But I don't know for how long our Element 1 console will be able to keep up with software updates. So I would appreciate some info on this as well: even if my idea works, it was designed "for the long run", so will it keep up? We have many moving lights in our space, as well as LED pars and LED bars. Not just a bunch of conventionals.

In other words, should I try to convince others that the Element 2 may be the better alternative, and that the 60 faders requirement just isn't going to work out within our budget.

Hi Lucas, unfortunately, Element consoles can only connect to ETCNomad in Element mode allowimg only 1024 Addresses. 

You best bet is to try either an IonXE20 + Faderwing 40, 

or an ETCNomad Unlocked (6144 Addresses) + Eos Programming Wing + Faderwing 40 + Faderwing 20. 

Thanks and Good Luck!

There actually might be a solution: ETCNomad can go to 6144 addresses with an unlocked dongle. This number is the same for Nomad in Eos and in Element mode. 

This should allow you to get more addresses while still using the faders if your Element: Nomad in Element mode with a 6144 dongle as primary, your Element 1 as client.

But in the long run you might want to look into a console with encoders. Controlling your many moving lights and LEDs without physical encoders can quickly get cumbersome. The two sets of hardware Corey suggested would be your next step up from your current system.

I'm sorry, but I am confused now.

You are saying it's possible to run an unlocked ETCnomad as primary and then connect an Element console as a client, while keeping the expanded address range that the unlocked ETCnomad provides?

Wasn't this my proposal which Corey said wasn't possible?

When I was searching around about address range limits, I came across the fact that the address range is the lowest of primary and backup (which makes total sense), but it didn't say anything about the client consoles connected (and how they influence the address range limit).

Yes, that's what I'm saying. Clients don't influence the system count. They do need a dongle to participate in the session, but the size of their license doesn't matter. Which means the only thing that determines the output license of the system I'm proposing is the ETCNomad dongle.

To connect the Element to the Nomad you will need to make sure that your Nomad is running in Element mode.

Hi Lucas, 

you had asked about an unlocked Nomad could connect to an Element as secondary, which I took as in Backup Mode. When connecting as backup then both Nomad and Element would be set to max 1024 addresses, and if the Nomad failed/crashes/Windows Update and Restarts, the Element as Backup woukd take over control of show seamlessly. 

If the Element connects as Cilient, yes, the Nomad could output 6144 Addresses, but if Nomad disappears, the Element won’t take over at all. You could then only stop Eos Software, restart Software as Primary on Element and only be able to control the first 1024 addresses. 

Thanks for clarifying, Corey. I now reget using the term 'secondary', because it can indeed be interpreted as either 'backup' or 'client'. I meant 'client', but I now totally understand why you said it wasn't possible.

We have never had the Element fail on us during a show (I don't think it has ever failed). When migrating our DMX output from Element to ETCnomad, do you think there is a bigger chance that an error occurs? Because a laptop is now handling the output, instead of a lighting console specifically designated for this?