Home› AMX Technical Discussion

Unable to bind device to system

TheAVSupportGuyTheAVSupportGuy Posts: 19
in AMX Technical Discussion

Hi everyone!

Hopefully a simple issue to fix, but i have an AMX-REL8 (relay box) that is unbound within Netlinx Studios.
Whenever i try and bind it to the active system, it flickers like its trying and just remains unbound.

I have tried a reset and a full factory reset on the relay box itself with no luck.

We did replace the AMX controller as it faulted which i am guessing has caused this issue - but i just figured pointing it/binding it to the currently active system would bind it.

Any ideas? :)

Comments

  • Marc ScheibeinMarc Scheibein Posts: 965

    Right-click and "Show Device Properties" to see the IP address. Is it in the correct IP range?

    Manual:
    https://www.amx.com/en/site_elements/instruction-manual-icslan-device-control-boxes

    You may do a factory reset, see pdf page 18.

    Worst case telnet to the EXB-REL8 box, following the instructions in Appendix A in the manual.

    With SET DEVICE, you set the device number for the box
    With SET CONNECTION you set the connection data to assign the box to the master (I recommend TCP as connection type).

  • TheAVSupportGuyTheAVSupportGuy Posts: 19

    Thanks Marc.

    The current physical connections are as follows:

    Relay box ethernet cable to POE injector (POE data and power out) then POE Injector Data IN to ICSL LAN port on NX 3200.

    The REL8 box is detected as an unbound device in the device tree however always has a 169.254.2.2 address.
    I have tried setting this to DHCP and Static against the same range as the controller but it wont seem to connect/be picked up with an appropriate address.

    (using TELNET set device and set connection. I also tried the set IP command as well)

    I have tried a full factory reset a few times, each time it just reverts back to 169.254.2.2.

    Hmm i think i am so close!

  • Marc ScheibeinMarc Scheibein Posts: 965

    The ICSLAN Port on regular NX controllers by default has the IP Range 198.18.x.x Subnet 255.255.0.0, where 198.18.0.1 always is the NX Master itself. Furthermore, by default the ICSLAN is running a DHCP server, assigning DHCP devices in range up to 198.18.63.254, and static IP is up from 198.18.64.1 (with reserved ranges 198.18.130.x and 198.18.134.x)

    The ICSLAN dhcp can be disabled, maybe that's why the EXB is falling back into the 169.254 range.

    Let's check, get by terminal/telnet to the NX

    These are the default settings for ICSLAN.
    On regular NX controllers, the IP range can be changed, but must be in anotehr subnet than the public IP network. (ob DGX and DVX the range can't be changed)

  • TheAVSupportGuyTheAVSupportGuy Posts: 19

    Your a genius! Thanks Marc! that was it! The ICSLan port was statically set!

Sign In or Register to comment.