Keyboard Shortcuts
Likes
Search
Lessons Learned - Crestron EISC
#simplwindows
#useful
#EISC
|
*I edited?this to reflect some of the conversations in response?to this post... 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.?
|
|
I don't understand anything you just described. EISC is very easy to use and besides signal layout is nothing like crosspoints.
One example of where you lost me is your processor/program layout. The first one you show using the actual IP address of the connecting processor, the next you show using the loopback address. |
|
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. |
|
I also have issues following your guide here or to understand what exactly you want to show.
The only difference between EISC between program slots and between processors is the IP address the modules pont to. Between programs it's 127.0.0.2 in both programs and between processors it's the IP of the other processor. |
¿ªÔÆÌåÓýI agree, the comparison with crosspoints made it more confusing than clarifying IMHO. I also find EISC much easier to understand and use as you only need to get the direction of the signals right (or left ?) and the addressing (internal <> cross controller). ? Cheers, Thorsten ? Von: [email protected] <[email protected]> Im Auftrag von dblpnt ? I also have issues following your guide here or to understand what exactly you want to show. |
|
Thanks for the clarification, Duck.
I see what you meant now. I had thought you were showing what you would do on the processor verses in the program. Also, as others have pointed out, you use 127.0.0.2 for the loopback on hardware processors. One last item that confused me, why do you have help.crestron.com after each IPID? |
|
The links to help.crestron.com are links that describe what I am doing with the F6 command. Just in case the text version that precedes it is unclear with the brackets and all.?
That is all, just references to the interface I am configuring based on what step I was on in my description.? Also, to confirm, I knew about the 127.0.0.2. I must have fat fingered it and not caught it. I'm new to this type of forum, I would edit the original if I could. Sucks really, my intention was to help those who didn't know what EISCs are or how to use them in special ways that are clear to one group but not to another. My mistake could lead them down the wrong path... and just create more confusion. Hopefully they see this response and those from others who point that out. -- Sr. AV Systems Developer Crestron Programmer Looking to create a smarter, connected tomorrow, today. |