Added RPU, lost DMX

My brand new RPU came in this morning, I was able to get it setup, update software on all consoles and sync up with my EOS. I ran up a couple of channels and things seemed to operate just fine. I then walked back stage and looked up at my rig and noticed that all of the dmx were flashing (no dmx). I checked on our Fleenor isolated splitter and the signal indicator was not lit. I was working with all of my movers, scrollers and leds in the morning...everything seemed well. Oddly enough my two sensor racks are still functioning correctly. I plugged in the RPU and I lose DMX. I have created a quick schematic showing how my system is setup. Again, before the RPU...GREAT. After RPU...No DMX.. Here is a link to the file: http://www.patrickimmel.com/LNL.jpg Thanks for any assistance. Pat
Parents
  • Is your RPU running as Master? It's a possibility that you have different network protocols or defaults on your RPU to your Eos. If you go into the shell on your Eos and check what's selected there and then copy those settings into your RPU that might help.

    Cheers

    Dan

  • Thanks Hydro and Daniel! I'll take a look at these!
  • Pat,

    You may also want to take a look at the screen on the front of your gateway. Are the arrows static or flashing. If they are flashing the gateway is not seeing any sACN patched to the universes assigned to the gateway outputs, and will subsequently shut down those ports until something is patched. Assuming you do have something patched on the console and the arrows are flashing you could have a draft/ratified sACN issue. Your gateway may be running an old version of code which will not receive ratified sACN - there is a setting in the Eos shell to enable draft sACN, maybe this is checked on your Eos, but not on your RPU.

    I suggest checking the version of code in your gateway and updating it. The latest released gateway code is 5.1. To get this and send it to your gateway you will need the latest version of GCE installed, which can be found here - http://www.etcconnect.com/docs/docs_downloads/console/ETC_GCE_Net3Svc_v3.0.0.9.0.15.zip

    Versions of gateway code from 3.0 and above support draft and ratified sACN, so it doesn't matter how your consoles are set.

     

    Graham

Reply
  • Pat,

    You may also want to take a look at the screen on the front of your gateway. Are the arrows static or flashing. If they are flashing the gateway is not seeing any sACN patched to the universes assigned to the gateway outputs, and will subsequently shut down those ports until something is patched. Assuming you do have something patched on the console and the arrows are flashing you could have a draft/ratified sACN issue. Your gateway may be running an old version of code which will not receive ratified sACN - there is a setting in the Eos shell to enable draft sACN, maybe this is checked on your Eos, but not on your RPU.

    I suggest checking the version of code in your gateway and updating it. The latest released gateway code is 5.1. To get this and send it to your gateway you will need the latest version of GCE installed, which can be found here - http://www.etcconnect.com/docs/docs_downloads/console/ETC_GCE_Net3Svc_v3.0.0.9.0.15.zip

    Versions of gateway code from 3.0 and above support draft and ratified sACN, so it doesn't matter how your consoles are set.

     

    Graham

Children
No Data
Related