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

PROFIBUS 5613 A2 will not reset DP/DP Coupler properly after fault cleared

Created by: VanAwful at: 2/22/2008 11:10 PM (7 Replies)

Rating (0)

Thanks 0

8 Entries

2/22/2008 11:10 PM	Rate (0)
VanAwful Posts: 4 Rating: (0)	I have a computer with a 5613 A2 PROFIBUS card that is connected to DP/DP coupler. The other side of the coupler is connected to a third party PLC. When ever the customer puts the PLC into program mode the coupler goes into fault on both sides. When the PLC is put back into run mode that side of the coupler resets and runs, but the PC side does not. I have to disconnect the cable and reconnect or sometimes reboot the computer in order to get the coupler to operate again. I do not have this problem with any of my other PROFIBUS nodes. I can cause other nodes to fault and when cleared they go back online without a problem. Anyone run into this and/or know why the 5613 A2 master card does not reset the coupler and put it back online? Also, any idea why a fault on side 'B' causes a fault on side 'A'?
VanAwful Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

2/25/2008 5:35 PM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Hello, I have no clue... but I wonder, what type of Program do you run on the PC the CP is in? Is ita Program based upon OPC? If it is a Program based upon the DP-Base interface there might be the problem. Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

2/25/2008 7:15 PM	Rate (0)
VanAwful Posts: 4 Rating: (0)	Hello, We are running QNX on thePC with our own driver for the CP. Our program is home grown, so not based on OPC. What problems can occur ifit is a DP-Baseinterface. This is the data I see on the PC side of the coupler when the PLC on the other side goes into program mode (PLC is an Allen-Bradley with ProSoft PROFIBUS master): 09 0C 00 02 80 70 05 00 00 00 16 0A 05 00FF 80 70 05 00 00 00 16 0A 0C 00 02 80 70 05 00 00 00 16 0A 0C00 02 80 70 05 00 00 00 16 08 0C 00 02 80 70 05 00 00 00 16 0A 05 00FF 80 70 05 00 00 00 16 This data repeats and there is no change after the PLC goes back into run. The coupler on the PLC side goes back into operation, but PC sides requires us to reboot the computer or restart the application (forcing a restart of the CP) in order to get the coupler on the PC side to start working again. Is there a state bit that we may be missing? The coupler is the only PROFIBUS node we have this problem with. All other PB nodes reset and go back into operation without issues like this. Note: If I unplug the other side of the coupler and then plug it back in there is no problem. It is just when the PLC goes into program mode and back to run. Jim
VanAwful Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

2/25/2008 7:58 PM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Dear Jim, well, this changes the view a bit. But I guess I can help with the Information you see on the Screen, this is the Slave Diagnostics of the DP / DP Coupler. See the manual: DP/DP CouplerChapter 6.3.2 I am a bit astonished, because the DP V0 Diagnostics show that the remote side, the PLC by AB, does not deliver a valid value. There is no Input or Output Information at all. The Slave shows external Diagnostics information... so there might be some more. How does the System behave if you just power cycle the Coupler instead of the DP Master? If the Information the DP Master shows is correct I think the Problem is more likely in the Coupler. But maybe the information shown is only the information you receive on the PC as the DP Master from AB failed. Do you have any chance to use the Amprolizer to monitor the Bus? Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

2/26/2008 4:03 PM	Rate (0)
VanAwful Posts: 4 Rating: (0)	I am planning an internal test today to do a raw data capture on the AB side to see how the AB PB Master card is handling the coupler. I do not have Amprolizer, but am using a PBprotocol analyzer. The data I posted earlier is from the PC side of the coupler. What confuses me is why the coupler goes into fault on both nodes when just one node is actually faulted. Is this inherent to the coupler? My understanding is that the coupler should act as two independant nodes with one shared memory area for data transfer. Therefore, if a bus fault occurs on one, it should not indicate a bus fault on the other side. Possible configuration issue? I did find that we were using the GSD from the older0AD00 coupler. We changed it to the newer 0AD01 GSD. We now see all of the V1 diagnostics.
VanAwful Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

2/26/2008 4:23 PM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Hello, I think it is useful to have the information about the failing of one Master on both sides of the Coupler, because that way the Master that runs also sees that remote side is not responding anymore... so the System can react on the new situation. DP on PROFIBUS is luckily not likeUDP as it is used with Industrial Ethernet. Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

2/26/2008 11:38 PM	Rate (0)
VanAwful Posts: 4 Rating: (0)	I believe I have found the problem. On the PC side we are using the older GSD for the 0AD00 couplerwhich is V0. On the PLC side they are using the release 2 GSD for the0AD01 couplerwhich is V1. If they change the PLC side to the V0 GSD then the problem goes away and the profibus becomes very stable. If they leave it with the V1 GSD and I use the V1 GSD on the PC then neither side works. When looking at the data on either sideusing the V1 GSD I get this diagnostic data: 0E 05 00 FF 80 70 43 00 00 08 82 00 00 00 00 00 00 09 81 00 00 00 2A 2A 14 00 This shows a config fault of some kind. Our short term fix is to use the older GSD on both sides as it seems to work. Mean while I willlook deeper into the configuration we use with the older GSD and compare it to the configuration being used with the new GSD. It now looks like we have over looked something in the parameters of the new V1 GSD.
VanAwful Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

2/27/2008 9:48 AM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Hello, I am not sure how your configuration looks like but the Coupler says that you should have 42 Byte Input and 42 Bytes Output... but it does not look like he requires it. Therefore the device reports a Config fault. Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on