5/16/2016 4:59 PM | |
Joined: 1/21/2013 Last visit: 11/20/2024 Posts: 4620 Rating:
|
Hello dolby, Why not use this example just change the type of CPU: DP link between CPU 315-2DP (slave) and S7-400 (master) with ... or this: What master/slave communication options are available on ... 19449428 |
Last edited by: Ste39 at: 5/16/2016 5:00:24 PMLast edited by: Ste39 at: 5/16/2016 5:04:26 PMAdd ID CPU-CPU |
|
This contribution was helpful to
1 thankful Users |
5/20/2016 2:24 AM | |
Joined: 9/27/2006 Last visit: 3/23/2025 Posts: 12344 Rating:
|
Hello dolby; S7 connections are not linked to a protocol, you are right. But when using a S7 Connection for S7 communication blocks (PUT/GET, BSend/BRecv...) you are using a client/server exchange. So first of all, both partners must be masters (this cannot be done with a master-slave exchange) and a client must be a CP (CP 342-5 for a S7-300) Integrated Profibus ports on the CPU do not support client functionalities. See the following FAQ, copied in the attachment: https://support.industry.siemens.com/cs/ww/en/view/24352751 You can find more explanations from other members on the following discussion: Master--to--Master Communication on Profibus https://support.industry.siemens.com/tf/ww/en/posts/84804/ So, in resumé: to establish S7 connections you will need 2 Profibus masters; to setup S7 Commiunication blocks on that connection, you must have at least one CP 342-5 in the PLC that will initiate the exchange. Hope this helps, Daniel Chartier |
Last edited by: dchartier at: 5/20/2016 2:26:20 AMLast edited by: dchartier at: 5/20/2016 2:09:14 PM |
|
This contribution was helpful to
3 thankful Users |
5/20/2016 8:43 AM | |
Posts: 106 Rating:
|
Thanks Daniel, your answer helps alot ;) |
Follow us on