2/11/2011 10:36 PM | |
Joined: 10/7/2005 Last visit: 10/4/2024 Posts: 3024 Rating: (1054)
|
Hello bowler the DP/DP coupler manual is certainly a good place to start, on top of that, you'll find additional info in the FAQ's below (there's also a fair few DP/DP coupler related discussiosn to be found here on the forum just in case you have still questions afterwards): What are the special features of input/output addressing with the DP/DP coupler? Configuration of the I/O Data on DP/DP Coupler I hope this helps |
Cheers |
|
This contribution was helpful to1 thankful Users |
2/14/2011 2:54 AM | |
Joined: 10/7/2005 Last visit: 10/4/2024 Posts: 3024 Rating: (1054)
|
Hello again bowler not too sure ifI can really explain the DP/DP coupler any better than what's available in the previously suppliedmanual and links, but I'll try anyhow. The sole purpose of a DP/DP coupler is toallow(direct) data exchange between the two DP Masters. The DP/DP coupler does NOT create a physical link of the two individual Profibus Networks, each Network remains its ownsingle DP Master network (assuming you only have one PLC on each side). Each port ofthe DP/DP coupler is a simple DP Slave for its DP Master, the outputs of one side become the inputs of the other side and vice versa. Each DP Master can of course have additional DP Slaves on its own Network (its side of the DP/DP coupler) which are configured inthe HWconfig of each DP Master. Each DP Master can NOT "see"(nor control or read from) the DP Slaves on the "other" side of the DP/DP coupler. I hope the above remake sense and removes any remaining "doubt" and attached is a pic which will hopefully help in clarifying things further (collated from the previously supplied info). |
Cheers |
|
This contribution was helpful to1 thankful Users |
2/14/2011 10:02 AM | |
Joined: 10/7/2005 Last visit: 10/4/2024 Posts: 3024 Rating: (1054)
|
Hello bowler as said in my previous entry"Each DP Master can NOT "see"(nor control or read from) the DP Slaves on the "other" side of the DP/DP coupler". So while CPU2 can NOT directly control the Outputs of a DP Slave that belongs to CPU 1, it could do so indirectly as followed: CPU 2 writes to Outputs of the DP/DP coupler CPU 1 reads the corresponding inputs of the DP/DP coupler CPU 1 uses these inputstatuses to then drive outputs on the DQModule (322-1BH01) of its DP Slave I'm not saying that the above is a sensible thing to do, but it will work, myQuestion to you is though: What are you actually trying to achieve? |
Cheers |
|
2/14/2011 10:42 AM | |
Posts: 71 Rating: (0) |
Ok. It's most for training purposes =) I wanted to learn how it worked. Thanks for all help! |
This contribution was helpful to1 thankful Users |
Follow us on