That's ok that you didn't understand. My intentions were to help others who don't understand how something like this works. I either provided too much info or not enough.?
You are correct in saying it is nothing like cross points. I said?
If you have used Cross Point Routing before in your code, the EISC works in a similar way, the only difference is, the "equipment" module (EISC) is on one program, and the "control" module is on another program. Like Cross Point Routing where you have IDs for Equipment and Control, the IPIDs must match between programs.
What I meant by this is, in the same way that Cross Points require 2 modules, one being the equipment side, and the other being the control side, they need to connect to each other in the appropriate way so that input or output from one module goes -o or comes-from the other module. The difference here between Cross Points and EISC is that instead of using Equipment ID and Control ID, you use IPIDs and IP Addresses. In Cross Points, you would use the Control Crosspoint Connect symbol to connect the Control Crosspoint symbol to the desired Equipment Crosspoint symbol. In comparison, the EISCs use IPIDs and IP Addresses, where the IPIDs must match, and the IP Addresses in their configuration window point to each other.?
The layout, was to show the difference between using EISCs between different processors, in comparison to how you would use them between programs within a single processor. I might have made it more obvious, but the section that says "Ethernet Devices per CP4N" shows 5 CP4N Processors. I then was typing on the assumption that people would surmise there is only one program running per cp4n, and in each program there are EISCs at specific IPIDs. In the next part, right before "Ethernet Devices per Program", I said
As a note to those looking to see how it works between programs on the same processor, the only difference is the IP address you configure the EISC like I describe in Ethernet Devices per CP4N, just replace CP4N with Program:
This was to A) show how external and internal EISC uses would differ, and B) in case someone looking up info on EISCs could have a bit of help if they landed on my post.?
I hope I was able to provide clarity to what you didn't understand from what I previously described in my original post.?
--
Sr. AV Systems Developer
Crestron Programmer
Looking to create a smarter, connected tomorrow, today.
nicofreda
BruteForceIsUnderRated