5/12/2016 2:50 PM | |
Joined: 4/21/2014 Last visit: 10/23/2024 Posts: 28 Rating:
|
I also used Open communication wizzard. It configures the connection type to 16#11 also and I have the same result. Thanks to your last link, I decided to check the protocol limits. It seems that communication between two PLC's can expand the original protocol limits, but due to the fact that I am communicating to an IT application I am a little bit more limited... I found the following information that might explain my problem
Thanks for the help |
5/12/2016 2:52 PM | |
Joined: 7/22/2008 Last visit: 4/14/2022 Posts: 1884 Rating:
|
RIP |
Last edited by: 1test at: 6/8/2016 9:12:42 AM~(‾▿‾)~ |
|
5/13/2016 8:48 AM | |
Joined: 10/7/2005 Last visit: 3/27/2025 Posts: 3043 Rating:
|
"Open" in this context simply means it is not a proprietary form of communication (which S7 communication for example would be as Layer 7 contains the Siemens specific part of the protocol). As far as Siemens is concerned, "Open IE communication" supports the following:
Any of the three above can be done via the CPU's on-board PN port and usage of "T Blocks" (e.g. TSEND, TCON etc. and this is where the name "Open" appears most often as the Wizard for the connection configuration also contains it). Open IE communication can though equally well be done in the good old fashioned way via CP, NetPro configured connection and usage of for example AG_SEND/AG_RCV blocks. In fact, even S5 could already do "Open TCP" communication via a CP1430 well over 20 years ago, except no-one thought about using the word "Open" for it back then. Hope this helps and have a look too a THIS and THIS link for more on this. |
Cheers |
|
This contribution was helpful to
4 thankful Users |
Follow us on