开云体育

*I edited?this to reflect some of the conversations in response?to this post...

Crestron EISC (Ethernet Intersystem Communication) can be a confusing thing to some. I know it was to me, but if it is not confusing to you, then this post isn't for you. Keep in mind, this post contains info that I wish I knew when I was trying to accomplish EISC in my environment for an upcoming?project. Once I figured some stuff out, with much help from Crestron True Blue, It all became clear. So, it is my good intention to pass some of this info along to others.

I?scoured?the internet trying to find useful information on how to configure this for one of my installs. So, since I now have the info, I would share it so others who may be looking can get the info they need.?

The information I am sharing is based on the design of a particular install.

Project Framework:
There are a total of 8 rooms, all of which should work independently of one another, and per customer request, the rooms should be operating programmatically on their own processor (In the event there is something wrong with a processor, or with code, only affected rooms will be down, and not all of them). The routing is done using the Crestron NVX devices, totaling about 1000 inputs and outputs combined. Each room will have access to all inputs and outputs defined.?

Environment:
Processor - 9x CP4N
EISC - "3 Series TCP/IP Ethernet Intersystem Communications" (When adding items to Ethernet Devices, it is the very first item in the list)
Network Switch - CISCO C9300 (Using multiple VLANS)

VLANs:

• VLAN 100?
• DHCP Server Enabled
  • (Used to simulate the corporate LAN side of my system)?
• CP4N 01 - LAN
• VLAN 10
  • NVX DEVICES
  • CP4N 01 - SUBNET LAN
  • CP4N 02 - LAN
  • CP4N 03 - LAN
  • CP4N 04 - LAN
  • CP4N 05 - LAN
  • CP4N 06 - LAN
  • CP4N 07 - LAN
  • CP4N 08 - LAN
  • CP4N 09 - LAN
• VLAN 11
  • CP4N 02 - SUBNET LAN
• VLAN 12
  • CP4N 03 - SUBNET LAN
• VLAN 13
  • CP4N 04 - SUBNET LAN
• VLAN 14
  • CP4N 05 - SUBNET LAN
• VLAN 15
  • CP4N 06 - SUBNET LAN
• VLAN 16
  • CP4N 07 - SUBNET LAN
• VLAN 17
  • CP4N 08 - SUBNET LAN
• VLAN 18
  • CP4N 09 - SUBNET LAN

CP4N Ethernet Settings:?
Ethernet LAN Settings -?
Ethernet Subnet LAN Settings -?

• CP4N 01
  • LAN = DHCP (IP will be provided by the DHCP Server on VLAN 100)
  • SUBNET LAN = MANUAL - 172.10.0.0/16
  • Make reserved lease
    • [CP4N 02 MAC] 172.10.0.11
    • [CP4N 03 MAC] 172.10.0.12
    • [CP4N 04 MAC] 172.10.0.13
    • [CP4N 05 MAC] 172.10.0.14
    • [CP4N 06 MAC] 172.10.0.15
    • [CP4N 07 MAC] 172.10.0.16
    • [CP4N 08 MAC] 172.10.0.17
    • [CP4N 09 MAC] 172.10.0.18
• CP4N 02
  • LAN = DHCP (IP will be provided by DHCP Server on CP4N Subnet LAN)
  • SUBNET LAN = MANUAL - 172.11.0.0/16
• CP4N 03
  • LAN = DHCP?(IP will be provided by DHCP Server on CP4N Subnet LAN)
  • SUBNET LAN = MANUAL - 172.12.0.0/16
• CP4N 04
  • LAN = DHCP?(IP will be provided by DHCP Server on CP4N Subnet LAN)
  • SUBNET LAN = MANUAL - 172.13.0.0/16
• CP4N 05
  • LAN = DHCP?(IP will be provided by DHCP Server on CP4N Subnet LAN)
  • SUBNET LAN = MANUAL - 172.14.0.0/16
• CP4N 06
  • LAN = DHCP?(IP will be provided by DHCP Server on CP4N Subnet LAN)
  • SUBNET LAN = MANUAL - 172.15.0.0/16
• CP4N 07
  • LAN = DHCP?(IP will be provided by DHCP Server on CP4N Subnet LAN)
  • SUBNET LAN = MANUAL - 172.16.0.0/16
• CP4N 08
  • LAN = DHCP?(IP will be provided by DHCP Server on CP4N Subnet LAN)
  • SUBNET LAN = MANUAL - 172.17.0.0/16
• CP4N 09
  • LAN = DHCP?(IP will be provided by DHCP Server on CP4N Subnet LAN)
  • SUBNET LAN = MANUAL - 172.18.0.0/16

Programming the Ethernet Devices:
There was some controversy about me mentioning Cross Point Routing, so I need to clarify: EISC and Cross Points work in a similar way in that when one module is connected to another module (EISC or XPoint) what is changed on the input of one is communicated to the output of the other. For example, when digital join i1 goes high on module A, digital join o1 goes high on module B.

As well, there are variables that need to be configured to get the two modules to talk to each other. In Cross Points, you have to use the Equipment/Control Crosspoint Connect (ECCON) module to pair the Control Crosspoint module to the Equipment Crosspoint Module. However, when it comes to using EISC across processors, you have to set the IP of the EISC modules to point to the IP Address of the other processor and match IPIDs. If using EISC within the same processor and want to connect to an EISC in another program, you would use the loopback address (127.0.0.2), still making sure to use the same IPID.?

**NOTE: You can select the ethernet device and press F6 to open the Device Settings and select the IP Net Address tab.

EISC IP Address Settings when routing between processors:

• CP4N 01 (172.10.0.1)
• IPID 11: "IO Routing RM A" -?172.11.0.1
• IPID 12: "IO Routing RM B" - 172.12.0.1
• IPID 13: "IO Routing RM C" - 172.13.0.1
• IPID 14: "IO Routing RM D" - 172.14.0.1
• IPID 15: "IO Routing RM E" -?172.15.0.1
• IPID 16: "IO Routing RM F" -?172.16.0.1
• IPID 17: "IO Routing RM G" -?172.17.0.1
• IPID 18: "IO Routing RM H" -?172.18.0.1
• CP4N 02?(172.11.0.1)
• IPID 11: "IO Routing RM A" - 172.10.0.1
• CP4N 03?(172.12.0.1)
• IPID 12: "IO Routing RM B" -?172.10.0.1
• CP4N 04?(172.13.0.1)
• IPID 13: "IO Routing RM C" - 172.10.0.1
• CP4N 05?(172.14.0.1)
• IPID 14: "IO Routing RM D" - 172.10.0.1
• CP4N 06?(172.15.0.1)
  • IPID 15: "IO Routing RM E" -?172.10.0.1
• CP4N 07?(172.16.0.1)
  • IPID 16: "IO Routing RM F" -?172.10.0.1
• CP4N 08?(172.17.0.1)
  • IPID 17: "IO Routing RM G" -?172.10.0.1
• CP4N 09?(172.18.0.1)
  • IPID 18: "IO Routing RM H" -?172.10.0.1

EISC IP Address Settings when routing?between programs on the same processor:
When doing it this way, all the previous information regarding VLANs are not applicable. All that is important is that the IPIDs match, and the loopback address is used.?

• Program Slot 01
• IPID?11: "IO Routing RM A" -?127.0.0.2
• IPID?12: "IO Routing RM B" -?127.0.0.2
• IPID 13: "IO Routing RM C" -?127.0.0.2
• IPID 14: "IO Routing RM D" -?127.0.0.2
• IPID 15: "IO Routing RM E" -?127.0.0.2
• IPID 16: "IO Routing RM F" -?127.0.0.2
• IPID 17: "IO Routing RM G" -?127.0.0.2
• IPID 18: "IO Routing RM H" -?127.0.0.2
• Program Slot?02
• IPID 11: "IO Routing RM A" -?127.0.0.2
• Program Slot 03
• IPID 12: "IO Routing RM B" -?127.0.0.2
• Program Slot?04
• IPID 13: "IO Routing RM C" -?127.0.0.2
• Program Slot?05
• IPID 14: "IO Routing RM D" -?127.0.0.2
• Program Slot 06
  • IPID 15: "IO Routing RM E" -?127.0.0.2
• Program Slot?07
  • IPID 16: "IO Routing RM F" -?127.0.0.2
• Program Slot?08
  • IPID 17: "IO Routing RM G" -?127.0.0.2
• Program Slot?09
  • IPID 18: "IO Routing RM H" -?127.0.0.2

As a note, this is the process that I have learned with help from True Blue Support. Now that I know it, it seems really straight forward, and I wonder why I ever needed to find the answers to this at all. But for those who haven't had that realization yet, I thought by providing the answer to this question to the world wide web, I would help someone else. If for some reason someone else knows a better way, or would like to add more context that would help others in addition to what I have provided, I think we are all willing to listen. I always find it interesting to discover learn about what is an unknown-unknowns from those that know the known-unknowns.?


--
AV Systems Developer
Crestron Programmer
Looking to create a smarter, connected tomorrow, today.