Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Communication between 2 S7-300 CPU's via DP/DP coupler

Created by: Dawson at: 9/17/2013 12:36 PM (17 Replies)

Rating (0)

Thanks 7

Result pages:: |; 1 | 2; |

18 Entries

Entries per page: 10 | all

9/18/2013 10:12 AM	Rate (0)
Dawson Advanced Member Joined: 9/17/2013 Last visit: 4/29/2025 Posts: 39 Rating: (0)	I thought this problem was resolved, however I am still having issues. When powering either PLC down the SF LED comes on. If the PLC is powered back up the SF LED remains on. The only way I can get around this is to power up bothe PLC's at the same time. Is this normal behaviour?

Suggestion To thank Quote Answer

9/22/2013 11:56 AM	Rate (0)
Dawson Advanced Member Joined: 9/17/2013 Last visit: 4/29/2025 Posts: 39 Rating: (0)	I am still struggeling with this, I have had it working but I guess I was lucky in powering up both PLC's at the same time, now itis near impossible to get both PLC's into the run mode, do I have to add in some code to re check errors or something like that?

Suggestion To thank Quote Answer

9/22/2013 1:14 PM	Rate (0)
dchartier Grandmaster-Expert Joined: 9/27/2006 Last visit: 12/24/2025 Posts: 12472 Rating: (2722)	Hello Dawson; Please show us a completesave of your diagnostic buffer (not your interpretation of the contents, just a "Save as text" upload to the forum (as a zip file if needed)). And you shouldcheck if the diagnostic messages are the same on both CPUs... Also try using the diagnostic features of the DP/DP coupler (LEDs and signal bit from the DIA dipswitch) to help you understand the source of the problem: What are the special features of input/output addressing with the DP/DP coupler? Behavior of the DP/DP coupler when a master system fails Hope this helps, Daniel Chartier
	Last edited by: dchartier at: 9/22/2013 1:23 PM Last edited by: dchartier at: 9/22/2013 1:14 PM
Suggestion To thank Quote Answer

9/22/2013 2:43 PM	Rate (0)
Dawson Advanced Member Joined: 9/17/2013 Last visit: 4/29/2025 Posts: 39 Rating: (0)	Hi Daniel, Thanks for all the help, I really appreciate it, I will attach both diagnostic files to this post as a zip but as far as I can see they run into the same problems at some point or another, I do not know how to do diagnostic checks on the actual dp/dp coupler whenever I try to do it from the same menu as the CPU diagnostics I get an error message saying that the saved version is not the same as the configured version and I cannot see any buffer. The only thing I was now wondering is do I have to use siemens bus coupler plugs? I am currently using a WAGO connector like this: http://uk.rs-online.com/web/p/plc-accessories/7191910/ as I did not have any siemens ones in stock Attachment Diagnostics.zip (296 Downloads)

Suggestion To thank Quote Answer

9/22/2013 3:52 PM	Rate (0)
dchartier Grandmaster-Expert Joined: 9/27/2006 Last visit: 12/24/2025 Posts: 12472 Rating: (2722)	Hello Dawson; It seems that the coupler you have installed in the configuration and the physical coupler in the network do not match, for some reason. How did you select the DP/DP coupler, from the Profibus catalog (in HWConfig) or through installation of a gsd file? Please describe your procedure. In any case, start by looking at the diagnostic messages you have provided. There is a recurring text in many of the messages: "Requested OB: Diagnostic interrupt OB (OB82) OB not found, or disabled, or cannot be started in the in the current operating mode" This OB82 is a diagnostic interrupt OB, meaning some fault has been detected in the CPU's actual configuration; thesame text applies to OB86, a remote rack diagnostics OB. Since they are not found in the CPU (you have to add them to the program) that is the extent of information you canobtain from these diagnostic OBs at this time Creating them (right-click on the Blocks folder, create new block, type OB, select the appropriate number) and downloading them to the CPU will allow them to collect more precise data on the faults occurring ion the network. No need to program them, their program interface is sufficient to collect data from the CPU's system messages. Just load them to the CPU and run the program; the SF LED should turn on when the faults appear, but the CPU will remain active, and the diagnostic buffer will contain more information on the fault. Come back to us with more details. Edit: one of the possible issues when you receive a message of inconsistency between saved and existing slaves is addressing. It is possible that the 2 slaves on the coupler have a set address (by dipswitches) that is different than the one configured in HWConfig? see the attached file, from the DP/DP coupler manual. Hope this helps, Daniel Chartier Attachment DP_DP coupler addressing.jpg (390 Downloads)
	Last edited by: dchartier at: 9/22/2013 10:00 PM
Suggestion To thank Quote Answer

9/23/2013 7:36 PM	Rate (0)
Dawson Advanced Member Joined: 9/17/2013 Last visit: 4/29/2025 Posts: 39 Rating: (0)	I had tried to add the DP coupler 2 ways, the first way: right click > insert object > additional field device > gateway > dp/dp coupler release 2 and the second way: right click > insert object > network components > dp/dp coupler release 2 neither way seemed to make a difference I have now added OB82 and OB86 and this has fixed the problem I can now communicate between the PLC's if I switch 1 off then I get an SF led on the other PLC but it does not stop the PLC and when the other PLC is powered back up the SF led goes away Thanks for all the help

Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users dchartier O_Moderator tinhnguyen

11/12/2015 9:25 AM	Rate (0)
Min_Moderator Posts: 4758 Rating: (122)	New question published by tinhnguyen is split to a separate thread with the subject Connect s7300 with na 9122 (profibus) of crevis. Best regards Min_Moderator
Min_Moderator Posts: 4758 Rating: (122)
Suggestion To thank Quote Answer

11/12/2015 9:26 AM	Rate (0)
Min_Moderator Posts: 4758 Rating: (122)	New question published by tinhnguyen is split to a separate thread with the subject Comunication of two 315 2dp with profibus dp. Best regards Min_Moderator
Min_Moderator Posts: 4758 Rating: (122)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on