Control/Dimming Ion DMX with Strand SN110

DayOne

Member
The theater I work in just got an ETC Ion console after seven years with a Strand 520i. First off, does anyone know about ETC Net3? Is it in any way compatible with Shownet? Is ACN compatible with Shownet?

Anyways, I bypassed the network problem by using the 5-pin DMX outputs on the back of the Ion, however the SN110 input nodes we have will not read the DMX output from the Ion. Does anyone have any suggestions? The nodes used to work when we used to run an Expression 2X through the DMX input nodes.
 
Have you made sure the Ion is set to output DMX?
 
Ion by default has it's DMX ports enabled, but you can check - it's in the the shell - Network, the DMX boxes should have check marks in them.

AFAIK, Strand nodes do not listen to either ETC Net2 or 3.

You might give ETC tech a call to see about changing DMX speeds out of the Ion, or changing the Strand nodes, I'd bet they know how to do that as well.
 
Thanks, I'll try setting the speed to slow. Does this have any bearing on overall performance? Such as, strobe effects with LED units, etc? I know the ports are enabled. Hopefully this will work, I'll keep you posted.
 
Thanks, I'll try setting the speed to slow. Does this have any bearing on overall performance? Such as, strobe effects with LED units, etc? I know the ports are enabled. Hopefully this will work, I'll keep you posted.

No

It has to do with receiver/transmitter timing and how much time each device spends/devotes and understands of the packet being sent. The 44 times per second data rate doesn't change, thus no impact how the device responds.
 
Well, that didn't work. The Ion ports are working because I was able to control a seachanger directly plugged into the board... I'm going to do some more trouble-shooting tomorrow and work from there. Any ideas are welcome though.
 
I have a great idea: I'll buy the SN110 nodes from you, and then you will have enough money for about 1/3 of one new ETC Net3 Gateway. :evil:
 
Well, that didn't work. The Ion ports are working because I was able to control a seachanger directly plugged into the board... I'm going to do some more trouble-shooting tomorrow and work from there. Any ideas are welcome though.

Do you mean that you tried slowing down the speed and the node was unable to translate the DMX signal to ShowNet, or do you mean that you were able to connect a Seachanger at normal speed and because it worked, you did not try connecting it to the node?

I'm just looking for a clarified statement on what exactly you have and have not tried. A connected Seachanger won't care if the Ion is broadcasting DMX at whatever speed it feels like. A Strand ShowNet node on the other hand is somewhat touchy.

A local facility had a 520i and ShowNet system. A touring Ion came through the facility and when connected, it's default setting was to broadcast DMX as fast as possible, which blew the SN node out of the water and caused lighting all over the building to strobe like a dance party where everyone is hocked up on Ecstasy. Several panicked phone calls to Strand went nowhere but a few exchanges via phone with ETC's tech support and the problem was resolved -- all that needed to be done is the Ion had to slow down its DMX speed. For the most part, the system was fine then but every so often it would hiccup and all of the lighting would flicker off and on in the blink of an eye.

A couple years ago that facility replaced their dying 520i with a Congo Jr. I do not know for certain that the occasional flicker persisted, but I do know that they didn't take too long after that to rip their 7-or-so-year-old Strand Premier system out and replaced everything in the building with ETC Paradigm and presumably replaced nodes as well (though I am not certain about the nodes). They were able to keep the system standing as long as they did partially because one of their lighting guys was a software engineer making six figures who did theatre for fun -- in his spare time he'd make his own modifications to system files in the nodes and in their 520i.
 
So what is the actual change in the slow/fast toggle on the console.

I am assuming the fast is 44Hz but that is an assumption. Does anyone know the actual changes that take place from that fast/slow toggle.

I am curious to know because we had a situation with a Martin Ether2DMX8 output rack having the ability to dial the refresh rate from a range of 10Hz up to 44Hz. Our Sn110 nodes do not like the fast flavor and we didn't have time to experiment with the rate change testing.

Even when using a simple DMXter when it is toggled to Fast it will not drive the SN110 node but once switched to "Slow" it work fine.

Does anyone know the technical difference between "Slow" vs "Fast" dmx options?

Do you mean that you tried slowing down the speed and the node was unable to translate the DMX signal to ShowNet, or do you mean that you were able to connect a Seachanger at normal speed and because it worked, you did not try connecting it to the node?

I'm just looking for a clarified statement on what exactly you have and have not tried. A connected Seachanger won't care if the Ion is broadcasting DMX at whatever speed it feels like. A Strand ShowNet node on the other hand is somewhat touchy.

A local facility had a 520i and ShowNet system. A touring Ion came through the facility and when connected, it's default setting was to broadcast DMX as fast as possible, which blew the SN node out of the water and caused lighting all over the building to strobe like a dance party where everyone is hocked up on Ecstasy. Several panicked phone calls to Strand went nowhere but a few exchanges via phone with ETC's tech support and the problem was resolved -- all that needed to be done is the Ion had to slow down its DMX speed. For the most part, the system was fine then but every so often it would hiccup and all of the lighting would flicker off and on in the blink of an eye.

A couple years ago that facility replaced their dying 520i with a Congo Jr. I do not know for certain that the occasional flicker persisted, but I do know that they didn't take too long after that to rip their 7-or-so-year-old Strand Premier system out and replaced everything in the building with ETC Paradigm and presumably replaced nodes as well (though I am not certain about the nodes). They were able to keep the system standing as long as they did partially because one of their lighting guys was a software engineer making six figures who did theatre for fun -- in his spare time he'd make his own modifications to system files in the nodes and in their 520i.
 
Thanks for posting the link, mstaylor. Unfortunately it's not completely up-to-date with the latest timings for Ion/Element and Congo series consoles. I'll have to fix that. Note that the Net3 GWs and SmartFades have slow speed settings with much longer timings, expecially for the Slow setting. This is specifically in there to deal with Strand 110 nodes.

The 110 nodes need an 8mS [8000uS] interpacket idle time in order to see valid DMX. This, for those of you that know DMX timings, is a LOOONNNGGGG time. [A 44Hz update rate is 23mS].

Depending on the receiving product, various timing changes may be required to control the item. Some DMX products need to see some extra time between dimmer bytes [interbyte timing], some need extra time after the start code and some need extra time after the last dimmer byte sent [interpacket timing].

We've put these times in to allow users to have options controlling various receivers. According to the DMX spec, receivers are supposed to latch on to all of the possible allowable timings but that just isn't the case out there. So, we fixed it.

Does that explain it ok?

David
 

Users who are viewing this thread

Back