Partioning

As follow up:

I see that the Ion/Eos partitions Channels, not addresses, so.... question sorta' answered in part.

I also see that a Sensor CEM+ can assign dimmers to a Room, so...

How does the rack/dimmers "know" to only listen to a address call coming from a space, when the connection is Net3 ?.  An how do I do what I want to avoid and accomplish as stated in the first post ?

Thanks

SB

If you have 2 different venues with 2 different consoles, I would not recommend trying to use partition control to limit the output.  Eos/Ion have a built in output limition function found under the network tab in the shell.  This will stay with the desk and does is not effected by the show file. Simply remove all addresses by selecting the {remove} button below.  Next select the address you wish to have the console control and select {Add New Range} 

Just to add a note...

You will probably want to assign 2 different address ranges for any movers, or Multi-attribute fixtures you might be using.

`Steve

The dimmer racks themselves can also be partitioned to only respond to certain addresses - whether they be sACN, EDMX, DMX whatever...

The ML and multi-attribute device issue adds another element.

I'm assuming that any such devices probably want to be on different universes - such as Univ 2 for the Theater Reh. room and Univ 3 for the Music Reh. room, so that the 2 consoles address patching and disabling in shell doesn't allow talking to a universe in another space (same as dimmers)

This means that the Ion that sends on Univ 3 HAS to be a 1536, as unless I port it thru a Net3 Gateway and put it in another EDMX range, the 1024 ain't talking to nuthin on Univ 3.

Hmmm....

More ammo for not going the shared dimmer rack idea.

SB

Jeff Mabray said:

The dimmer racks themselves can also be partitioned to only respond to certain addresses - whether they be sACN, EDMX, DMX whatever..

Jeff

Do you know where in the CEM+ manual you saw that ?. 'cause I went thru the manual yesterday and only saw the ability to partition/assign dimmers to rooms, activated as presets internal to the CEM and I presume, then driven by a button box preset type activator that ETC can provide as a system not needing Unison or a Console.

I didn't see any method to to allow the rack to only have certain dimmers respond to call up from a DMX source in a particular room.  The CEM doesn't know where the source is, just that there's data for certain dimmers/relays to activate.

Thanks

SB

Jeff Mabray said:

The dimmer racks themselves can also be partitioned to only respond to certain addresses - whether they be sACN, EDMX, DMX whatever..

Jeff

Do you know where in the CEM+ manual you saw that ?. 'cause I went thru the manual yesterday and only saw the ability to partition/assign dimmers to rooms, activated as presets internal to the CEM and I presume, then driven by a button box preset type activator that ETC can provide as a system not needing Unison or a Console.

I didn't see any method to to allow the rack to only have certain dimmers respond to call up from a DMX source in a particular room.  The CEM doesn't know where the source is, just that there's data for certain dimmers/relays to activate.

Thanks

SB

It would depend on how the system is laid out, but you can assign each dimmer to a specific sACN address if you want.  So for instance, you could assign several dimmers in a rack to respond to sACN universe 1 and others to respond to sACN universe 2.  to make this as easy as possible, the inputs in each space would probably need to be DMX plates tied to a gateway or a single port gateway.  This way you set the sACN input address and it is already patched to those dimmers.  The other option is to use a direct net input to the system from the console and then use the sACN addressing option in the shell discussed above.

If spending a little less on dimmer racks and sharing them between spaces gets you more other toys to play with, it may be an idea well worth considering.