Hi Pegaia, 

I have downloaded your sample program. I would like to know something. I am having trouble getting this thing done: I need to trigger an output a PLC (example: trigger q0.0 of PLC 1 using I0.0 of PLC 2) using TCP protocol. Please advise me on this how this can be done? Because at the moment i am able to it using the S7 connection but not using TCP connection. Can this be done the way i want i now?

Thank you in advance.

Denilson Pegaia

Hi,

Here there is a sample program to TCP data exchange between two S7-1200.

Tips on programming:

1 – You can use the blocks TSEND_C and TRCV_C

2 – Select the blocks on the ladder (with instance db). In the bottom window, there are the connections properties.

3 – Connection properties:
3a - You can select a partner CPU if both are in the same project. If it is not the case, select “unspecified”.
3b - One, and just one, of the two partners should be the active for establishment of the connection.
3c – Connection ID: it should any number. It will be used as reference on the blocks to related connections parameters and blocks actions. So, each connection in a PLC should be its own number.
3d – Port: If the TCP IP address is like an address number of the street. The Port is like the apartment number.

4 – Block parameters:
4a – REC is triggered by edge (0->1). Fill it, for example, with a clock memory.
4b – Cont: if you use this communication continuously, set it as true.

------------------------------------------------------------------------------------------
Split from S7-1200 TCP communication - Sample program.

Hello,

look, if you have see example, probably some of device send some data to other device. Data will be store to some receive buffer defined with some of structure (for most cases BYTE can be best). There is no problem if device what send data, set needed agreed value to that buffer on right place. Device which receive data can read that value from it's receive buffer and due this value make other work, also turn ON/OFF that output. Start investigate example, make tests and give us info.

Hello,

Simple way is i device communication.

But again its depends on Which PLC type, Which interface? How much data?Distance?

Go thru below link for which devices can the S7-1200 communicate via the integrated PROFINET interface and which protocols does the S7-1200 support?

https://support.industry.siemens.com/cs/ww/en/view/38051505

Configuration and application of PROFINET I-Device function

https://support.industry.siemens.com/cs/in/en/view/109478798

HI all, 

I have attach my file here, i had followed the example file, i am having problem (I am unable to achieve what i wanted: I need to enable Input (I0.0 of PLC 1) & trigger an output  (Q0.0 of PLC 2). At the moment i am able to trigger the Q0.0 but (its not the way i need it to work). Example when i make I0.0 true Q0.0 is true but when i make the I0.0 false, the Q0.0 remains true. Besides, not only Q0.0 is triggered (it also triggers some random outputs (example in my testing, there is one round where the outputs Q0.0, Q0.4 & Q0.6 was triggered (where my other PLC input (I0.0, I0.4, I0.6 & I1.0 was true) - but my program only contain I0.0 & Q0.0. Another round testing, only I0.0 was true but the Q0.0 - Q0.7 was all triggered on. But when i made the I0.0 to go false, all the Q remain triggered.

Please advise since I am still new to TCP connection.

Hello,

sry not looking to your program, but if your communication is ok then all must work. In principle, if you put your I0.0 to false, you must change in send buffer also this change-value. In case f.ex. you can send IB0 to needed BYTE in send buffer. It will contain relevant infos about inputs on your PLC with that address. In receive PLC you then read from rcv buffer this value and 'copy' value of BYTE to output byte address depended to your needs. This can look very simple (receive PLC side):

QB0:=DB10.DBB10;

Example point to receive buffer in DB10 to 11-th BYTE which will contain this value. Very simple, isn't it?

Update: also some kind of important info, this problem doesn't depends to TCP, you must prepare your statuses/refreshes outside of TCP, this is basic logic system, not communication.