Slaveing a RPU to the ION to add universe capacity

Hi Zatzuk,

The Eos family line of products when networked will always drop to the device on the network with the lowest attribute count. So if you have an Ion 3000 RPU and an Ion 1000, the RPU when connected to the Ion will drop its attribute count to 1000. The only way to upgrade  is to purchase an upgrade code. Its a very easy process. Give your console serial number to your ETC dealer. Make payment. Once your dealer process it with ETC, you'll receive an upgrade code which you just type into the console, and voila, more outputs. 

The first time I ran into this, I found that the console seems to count the address's used starting at channel 1. Once you hit the attribute limit, any channels above that cease to work.

So channel 1 takes 3 attributes. Channel 2 6 attributes. You are at 10..so on and so forth until the limit is reached. As Paul mentioned in another post, you can view your available address's by either pressing about, or you should see it in Patch. 

Good luck. 

Hi Zatzuk,

The Eos family line of products when networked will always drop to the device on the network with the lowest attribute count. So if you have an Ion 3000 RPU and an Ion 1000, the RPU when connected to the Ion will drop its attribute count to 1000. The only way to upgrade  is to purchase an upgrade code. Its a very easy process. Give your console serial number to your ETC dealer. Make payment. Once your dealer process it with ETC, you'll receive an upgrade code which you just type into the console, and voila, more outputs. 

The first time I ran into this, I found that the console seems to count the address's used starting at channel 1. Once you hit the attribute limit, any channels above that cease to work.

So channel 1 takes 3 attributes. Channel 2 6 attributes. You are at 10..so on and so forth until the limit is reached. As Paul mentioned in another post, you can view your available address's by either pressing about, or you should see it in Patch. 

Good luck. 

travisres said:

The Eos family line of products when networked will always drop to the device on the network with the lowest attribute count. So if you have an Ion 3000 RPU and an Ion 1000, the RPU when connected to the Ion will drop its attribute count to 1000. 

To clarify a quick point here -- address counts only matter between the console assigned as the Primary and the Backup.  There, the lowest address count will win.  Address counts on a console assigned as Client does not matter. 

Examples:

- If you have an Ion 3000 (actually 3072) RPU as Primary, and Ion 1000 (actually 1024) as Client, the overall address count of the system will be 3072.  The only issue here is that there is no backup that will take over.

- If you change the Ion 1000 to be the Backup and keep the Ion 3000 RPU as Primary, the address count of the system will be 1024. (The address count that both the Primary and Backup are both capable of outputting).

- If the Ion console was upgraded to 3072 and assigned to Backup, it of course would keep the address count of the system at 3072, and you would have full backup capability.

- Ignoring the RPU for a second - you can upgrade an Ion 1000 console in blocks of 512 addresses from 1024 all the way up to 3072 total outputs. This, as has been suggested above, will give you expanded output.  Note that to get additional DMX universes out of the console, you would need some sort of network protocol to DMX device (whether it is a Net3 DMX Gateway, Net2 DMX node, or an ArtNet device).

There's a wiki article about upgrading the console's outputs that can be found here: http://community.etcconnect.com/wikis/products/knowledgebase-upgrading-eos-ion-output-counts.aspx