12/5/2022 1:22 PM | |
Joined: 1/5/2012 Last visit: 4/1/2024 Posts: 22 Rating:
|
Duris, Thank you but what you sent also did not work. Again it seemed as if I hit some sort of firewall trying to come in to the other PLC. For the time being I abandoned trying to communicate between the 2 PLC's as my real goal is 1200 - Node Red. |
12/5/2022 1:26 PM | |
Joined: 1/5/2012 Last visit: 4/1/2024 Posts: 22 Rating:
|
Ok this time I tried it with TSEND_C and TRCV using the same connection. Again, Data received at Node Red but nothing received at the PLC.
Attachment0.7 TSEND_C and TRCV.zip (825 Downloads) |
12/5/2022 1:33 PM | |
Joined: 4/28/2015 Last visit: 2/24/2025 Posts: 10832 Rating:
|
Hello,
again pls, I can't help you in this case you've attached TIA project. To previous problem with TCP ports, although you can have Firewall traffic enabled, your settings in Connection are wrong, as I said. You connection is wrong and can't be established between 2 S7-1200. It is clear from your file tcon.zip and if I see it good (hope) you have also wrong IP settings, both Client and Server PLCs have set same remote IP so what connection you can have in this case? I expect from you that you can give us better description what device has what IP and ports because if that zip file sets 2 PLCs inter connection, is simply wrong. Give us pls better description. |
Last edited by: Duris_I at: 12/05/2022 13:35:23Last edited by: Duris_I at: 12/05/2022 13:39:54Last edited by: Duris_I at: 12/05/2022 13:44:50With best regards... |
|
12/5/2022 1:58 PM | |
Joined: 1/5/2012 Last visit: 4/1/2024 Posts: 22 Rating:
|
Ok here is another try using 2 ports. 2000 is outgoing port configured as active. 2001 is incoming port. TSEND_C is using connection 1 TRCV_C connection 2. The TRCV_C is setup as a passive connection. CONT := FALSE ADHOC := TRUE listening to port 2001 on connection 2. Again, sending data to node red works fine. I still have yet to receive anything. This is the overall problem. Sending has worked the whole time. Receiving fails. Attachment0.8 2 port TSEND_C and TRCV_C.zip (794 Downloads) |
12/5/2022 2:02 PM | |
Joined: 1/5/2012 Last visit: 4/1/2024 Posts: 22 Rating:
|
Thank you Duris and I understand your frustration. This is why Ive originally split it out. At this point I am concentrating solely on a 1200- node red and stopped plc - plc. The PLC is 192.168.30.20:2000 (TX - Node Red) 192.168.30.20:2001 (RX - Node red). Node red machine is 192.168.30.50:2001(TX - PLC) 192.168.30.50:2000 (RX - PLC) Again sending is not a problem, receiving is my only problem at this point. |
Last edited by: frazzled1 at: 12/05/2022 14:06:04 |
|
12/5/2022 2:09 PM | |
Joined: 4/28/2015 Last visit: 2/24/2025 Posts: 10832 Rating:
|
No worry with frustration, in case of not correct infos you provide, you're wasting time. Hope some one will open your prjs and help you. |
With best regards... |
|
This contribution was helpful to
1 thankful Users |
12/15/2022 6:28 PM | |
Joined: 1/5/2012 Last visit: 4/1/2024 Posts: 22 Rating:
|
Ok, to sum this all up I found something misleading in the online documentation. When I open it and search on "tcon" the whole list pops up of TCON references. This is where it gets confusing. Clicking the first in the list ((solid block) TCON: Establishing a communication connection....), it gives the "CONNECT" data type as SDT "TCON_Param". This was what I was trying to do to such frustration. If you go down to the (box with arrow) "TCON: Establish communication connection" and click on it, the parameter is different. In this entry it lists "CONNECT" as a variant and then lists SDT TCON_IP_v4 as the proper structure for the type of connection I was trying to make. Even stranger the TCON entry for just the S7-1200 also lists the structure as TCON_Param It is this second entry that is correct. Once I changed the SDT from TCON_Param to TCON_IP_v4 everything worked fine. If anyone knows why these two entries would be so different please let me know here. |
12/16/2022 6:18 AM | |
Joined: 4/28/2015 Last visit: 2/24/2025 Posts: 10832 Rating:
|
Hello, if I could only report, I have never problems use TCON default connection type and use it with SEND/RECV blocks, also with MB TCP functionality, it requires as def IP_v4 connection structure but worked also with TCON structure. Really isn't clear to me what problems you have. If some other diffrencies exists in other TIA versions, this isn't known to me. |
With best regards... |
|
Follow us on