Profibus communications between multiple S7-300 processors

agarb

Member
Join Date
May 2006
Location
USA
Posts
309
I am not great with Siemens and Profibus so looking for some advice.

I have a project where I need to communicate approximately 20 status words (bi-directional) with a customer’s PLC on the line.

Can I do this directly with the 315-2 PN/DP processor or do I need to add 6ES7158-0AD01-0XA0 DP/DP coupler?
 
Is the customers cpu already set up as a profibus master?
Is your cpu a profibus master too?
If the answer is yes to both- I would use the dp/dp coupler
 
Thanks for the response.

I am not using the profibus connector on my CPU for anything else so it can be slave. In that case, is there any advantage to using the dp/dp coupler?
 
I am not great with Siemens and Profibus so looking for some advice.

I have a project where I need to communicate approximately 20 status words (bi-directional) with a customer’s PLC on the line.

Can I do this directly with the 315-2 PN/DP processor or do I need to add 6ES7158-0AD01-0XA0 DP/DP coupler?

Short version: you probably can do it directly (depending on the setup), but the DP/DP coupler is a great solution. I see the PN equivalent used all the time.

Long version:
It depends how the network is structured and how often you need to communicate the data.

Are all the PLCs on the same DP network? If so, you can communicate directly. If they are all different DP networks, then you either need a CP card or a coupler.

There are also two different mechanisms for communicating. You can use cyclic comms, which are good for sending smallish amounts of data (less than 256 bytes, so this is probably a good choice for you) very often (IO scan update rate). Minimal code effort here, it just uses the standard IO table, and is my preference. You can also use acyclic comms when you want to send larger chunks of data (up to tens of thousands of bytes) only occasionally. This is done via send/recv blocks.

For cyclic comms, if you aren't using the DP port for anything else and you are on the same DP network, you can set it to be an I-Slave and have it directly be a slave of the other controller. Otherwise you can use a DP-DP coupler (or a CP card). One note with those: they have two sides, and you MUST use one side in one project, and the other side in the other project. If both controllers have the left side in the HW config, it won't work.

For acyclic comms, there are a number of blocks available, dependng on what you want to do. You'll need to create a connection (in Net Pro, if using Simatic Manager), and then assign the blocks to that connection. Put/Get are the simplest, but they don't give acknowledgement. B_send/B_recv are the blocks I most often see used.

edit: JRW solved the problem with a couple sentences in the time I wrote an essay. I think there is an important lesson here.
 
Last edited:

Similar Topics

I am in the initial stages of setting up a profibus network using siemens 315 2DP plcs. I have followed this guide to setup the network. So far I...
Replies
2
Views
1,808
Hi, I was noticing that Profibus connectors have 2 ports on them that can house 2 separate cables. Can I use 2 cables with Profibus signals...
Replies
4
Views
140
Hello, I am in possession of a WAGO PFC 200 750-8216 which I was successfully able to set up as a Modbus RTU Master to a slave device using...
Replies
0
Views
48
I am trying to implement a profibus network and am a newbie in the automation and communication industry. what are the components required for the...
Replies
1
Views
82
Hi, I am using TIA Portal V18. I have imported a (v5.7) SIMATIC manager project via device proxy. I have created a HMI project (TP700) in TIA...
Replies
2
Views
281
Back
Top Bottom