ETC Ion DMX input query

eos-family consoles don't handle dmx-in afaik. the gateway itself merges the data and sends it to the rest of the network (and its ports) but the console never sees that data...

As Ueli commented, the Eos family desks do not support a DMX input function, so any DMX going into the 4 port Gateway is not going to the desk to be acted upon.

That said, it sounds like all you need is the ability to use the house desk as the functioning console until such time as a show console is up and running.  As well, you can as needed have both the house Ion as well as the visiting console operational at the same time.  

So question one becomes - is this a networked system ? and is the Ion connected via a Cat5 cable ?.  If so you can connect the gateway to the network at either another Cat5 connection point, or into a switch near the Ion, then simply plug the visiting console DMX into port 4 as you have it set up, if and when the visiting desk is up and functional.  Both desks will be sending DMX to the system in a highest takes precedence mode, so maybe power down the Ion prior to show.  

If the system is not a network, you can re-configure the gateway for 2 DMX universe 1 inputs (assuming you are only controlling one universe), then have both desks input to the gateway at the same time.  Note though that the typical configuration for Net3 gateways when using as a DMX merger (which is essentially what it's doing) is that a lower numbered port has priority over a higher number port.  Thus any DMX at a value of zero inputting to port one would over-ride the inputs to higher numbered ports.  You might want to check this in the gateway manual as you might be able to change this configuration.  Or just swap DMX from the Ion to the visiting at half hour or so.  

FWIW, I often keep my Ion up and running with a visiting console in use.  I have a networked system so it's an HTP setup.  I sometimes have the channel to address patch for the event in the Ion to make it easier on the LD, but if not given that info. I will do a one to one patch so as to have the channel and address the same.  This eliminates the slight lag the console exhibits when calling up addresses not patched to channels.  

Eamon,

From my touring experience I always find it easier to have a hard DMX line. I find that 99% of venues I go thru have the setup that is listed above. Trying to patch in via NET3 Ethernet can pose lots of problems. I use universes 1-12, and they are all dedicated to something. I keep universe 4 open to output to local DMX. If your ethernet assignment is not the ETC 'standard' things might not work or you might find unwanted results. 

ErikP said:

. Trying to patch in via NET3 Ethernet can pose lots of problems. 

If it's a Net3 (or Net2 for that matter) system you might not see a hard DMX line to house dimmers, if you need that for FOH, Box control, etc...  You'd be sending DMX to the house universe thru Net2/3 as the racks are probably on the network.

This is how you would hookup at my house, but we'd run your snake with however many universes you have, to your system backstage.  We would not route you into our lighting network except to have your U4 control our U1 house conventionals as needed.

Hi all

Thanks for the replies.

Sorry for the lateness of my response but that little ol work thing has been getting in my way...

Here is some background to the venue. I have approx 126 ways of hard DMX dimming. The install is comprised of rjuliat tivoli & a strand wallrack. All units are ran via DMX to a buffer and then to the console. The network gateway only comes into action via the console. There is no other dimmers or options to control lighting elements via any network protocol.

I was lucky to avail of a grant and figured the 4 port gateway would allow me greater flexibility with a new ion rather than having 2 touch screens.
My gateway consist of 3 physical DMX outports and 1 DMX input port.

The gateway does its job very well in allowing me to expand my DMX ports and universe ability as IMO the console does not offer enough DMX outs etc. That is a side issue and one that could take all day...

I do get a wide variety of shows in with various models of lighting desks and not all carry a riggers ( 6way manual up to hog, various strand & etc products). I accept I can swop DMX inputs but that can prove tiresome, awkward and not always practical.

I only ever wish to extend control over dimmers. This desire is down to helping a fit up run smoother and minimise trouble shooting silliness etc without interfering with a show.

I will give the 2 port configuration a go. It seems to make sense but can I ask why you would have to set the port up as such? Is it just one of those things or is it a deeper control issue?

Many thanks for the helpful replies.

Eamon

The intent of DMX input for Net3 gateways and legacy Net2 nodes was to get a port(s) where you could allow any console to input DMX into a system whose dimmers and other devices were on a networked system, CEM+ and CEM3 dimmer racks as example, or into a network large enough to have multiple locations where you need to be able to route universes, as well as pulling off DMX from a gateway/node at assorted locations for devices.  It was never intended that DMX input to the network be acted upon by the consoles.  

Probably the easiest setup for you would be to add a small and simple Cat5 Ethernet switch, connect the Ion and the Net3 gateway to the switch, essentially creating a mini Net 3 environment, then any visiting console into a DMX input port on the gateway, then send DMX out of the gateway to your house dimmers.

This would allow the Ion to act upon the dimming system alongside a visiting console in an HTP manner - I/E., whatever address value is highest from either console.  No priorities to deal with, the Net3 system deals with HTP.  Remember as well to enable Net3 in the Ion shell.  

See attached.

A

Hi Steve

Many thanks for the diagram and the hints.

I currently have a wifi router in place with the wifi part devoted to the arfr remote. The gateway is plugged in directly to the router. From what I am gathering the net 3 gateway is separate to the desk and it does the controlling of the input/outputs to the dimmers etc.

I will try the set up as described and report back when in work again.

Thanks for the tips et al.

eamon

You can in all likelyhood, plug the gateway into the WiFi router and skip my suggestion of a separate switch.  I believe the WiFi unit will do that.  I think that if the router has a pass through port, you should use that so that the router does not manage the gateway.  Possibly ETC might have better advice.

The gateway will talk to the Ion if the Ion has the Net3 switch enabled in setting.