Gateway update and RDM connection

We just got new Robert Juliat LED Profilers that don't have a display and can only be configured via Web Interface or RDM. So now we tried to do it via RDM to not have to give them fixed addresses, and it worked as long as we plugged in to the local DMX Outputs on our Gio @5. However as soon as it was over Network with a Response Mk2 Gateway inbetween it didn't work anymore. The ETC tech support said to update the software of the gateway and here's my Problem:

I got it as far as having the gateway recognized by UpdatorAtor and I got all the Softwares Installed, However in the Tag "Software version" it didn't change from "Finding" to the current software (I waited for about 10 minutes).

Does anyone know where the problem could be? Could the software update interfere with the compatibillity with the rest of my network and what else could be the problem with the RDM Network connection?

It's our first time working with stuff like this...

Parents
  • For the Gateway Update part, What version of UpdaterAtor are you using? The latest version is 6.3.0.9.0.8 and can be downloaded here: System Configuration Software.
    Using an older version of UpdaterAtor could cause the current software field to show "Finding" indefinitely.

    For the Gateway software/firmware, that will depend on the CPU variant of the Mk2 Gateway you have. if it is CPU1, the latest version is 2.1.0.6. If it is CPU2, the latest version is 3.1.0.13
    If your gateway(s) are already on this version, no need to try and update them.

    Just in case you need it, here are steps to updating Gateway Firmware using UpdaterAtor: Updating Response Gateway Firmware Using Updaterator (note that the video describes previous Net3 ACN/DMX Gateways, but the Mk2 Gateways update in the same fashion)

    One other setting on the Gateway to check is that RDM Background Discovery is enabled. This setting will show on the Gateway UI but can only be changed via Concert. When this setting is disabled, RDM Discovery (If RDM Is enabled) only happens when the Gateway is powered on/restarted. When this setting is enabled, RDM Discovery (If RDM is enabled) still happens when the Gateway is powered on/restarted, but it will also frequently poll for new devices. This polling frequency is dependent on a number of factors including the RDM Background Interval setting for that port in Concert as well as the number of Discovered RDM Devices on that port.

Reply
  • For the Gateway Update part, What version of UpdaterAtor are you using? The latest version is 6.3.0.9.0.8 and can be downloaded here: System Configuration Software.
    Using an older version of UpdaterAtor could cause the current software field to show "Finding" indefinitely.

    For the Gateway software/firmware, that will depend on the CPU variant of the Mk2 Gateway you have. if it is CPU1, the latest version is 2.1.0.6. If it is CPU2, the latest version is 3.1.0.13
    If your gateway(s) are already on this version, no need to try and update them.

    Just in case you need it, here are steps to updating Gateway Firmware using UpdaterAtor: Updating Response Gateway Firmware Using Updaterator (note that the video describes previous Net3 ACN/DMX Gateways, but the Mk2 Gateways update in the same fashion)

    One other setting on the Gateway to check is that RDM Background Discovery is enabled. This setting will show on the Gateway UI but can only be changed via Concert. When this setting is disabled, RDM Discovery (If RDM Is enabled) only happens when the Gateway is powered on/restarted. When this setting is enabled, RDM Discovery (If RDM is enabled) still happens when the Gateway is powered on/restarted, but it will also frequently poll for new devices. This polling frequency is dependent on a number of factors including the RDM Background Interval setting for that port in Concert as well as the number of Discovered RDM Devices on that port.

Children
No Data
Related