
What’s New in X-Series Controllers
1
What’s New in X-Series Controllers
What’s New in X-Series Controllers
Two discrete Network Interfaces (NICs)
The NX-2200, NX-3200 and NX-4200 controllers have two 10/100BaseT Ethernet connections. The first, designated as
LAN, is intended for connection to the Data Network for external network communications such as database access or
scheduling. The second, the ICSLAN is intended for communication with AV devices.
These two Ethernet interfaces occupy separate logical address spaces and are implemented as discrete and independent
NICs to the microprocessor. There is no IP routing functionality, so there is no ability to port-forward between interfaces.
The only built-in communication between these two Ethernet interfaces is via AMX’s ICS protocol, which is
accomplished at the application layer. This allows for connection to and configuration of AMX devices on the ICSLAN
using Netlinx Studio or RPM Loader from the enterprise network. This is the same mechanism that allows
communication with AxLink devices from an Ethernet connection.
In addition, a NetLinx or Java application can open independent sockets on these two Ethernet interface and use these
sockets to pass data between networks.
No other data is able to pass between the interfaces.
Using the ICSLAN network
The default IP address for the ICSLAN network is 198.18.0.1 with a subnet mask of 255.255.0.0.
It is important that the ICSLAN and LAN subnets do not overlap. If the LAN port is configured such that it’s address
space overlaps with the ICSLAN network, the ICSLAN network will be DISABLED.
DHCP Server
The ICSLAN port has a built-in DHCP server. This DHCP server is enabled by default and will serve IP addresses to any
connected devices set to DHCP mode.
The DHCP server can be disabled from telnet with the command:
SET ICSLAN
The DHCP address range is fixed. The server will provide addresses in the range x.x.0.2 through x.x.63.255.
Devices using static IP addresses on the ICSLAN network should be set within the reserved static IP address range of
x.x.64.1 to x.x.255.255.
Opening LAN and ICSLAN sockets from code
When opening sockets from NetLinx or Java code there is no mechanism to indicate which network to use. The
controller will open the socket on whichever network has an IP subnet that matches the address provided in the
command to open the socket. There is no indication which network was used, only whether the socket was created
successfully.
Automatic binding of AMX devices on ICSLAN
When an ICSLAN device, such as an EXB-COM2, is set to NDP connection mode (the factory default), it will
automatically be bound to the master when connected to it’s ICSLAN port if it’s IP address is valid for the ICSLAN
subnet.
If the controller is set to serve DHCP addresses on ICSLAN and the ICSLAN device is set to DHCP addressing mode, a
valid IP address is assured. Since these are the factory default settings for these devices, automatic binding is the
expected behavior for all new equipment.
Even after being automatically bound to a master in this manner, if the ICSLAN device is disconnected and moved to the
ICSLAN port of a different controller, it’s old binding will be forgotten and it will bind to the new controller to which it’s
been connected.
Once bound, the device ID still must be set to match the device definition in code. Once bound, the device can also be
configured for a different connection mode if desired.
Kommentare zu diesen Handbüchern