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 strange collapse

Created by: azsym at: 7/2/2014 6:45 PM (5 Replies)

Rating (0)

Thanks 3

6 Entries

7/2/2014 6:45 PM	Rate (0)
azsym Posts: 49 Rating: (0)	Hi network experts, I have profibus network. On it I have 40 devices - SEW servos, ET200s, some tach, BOSH proportional cards for servo valves, and 2 profibus encoders. The master is S300 CPU 318, and the speed of bus I 1.5 Mbits (have RS485 repeaters). The settings of profibus is on standard the cycling time is about 8 - 9 ms. The longest 12 ms ( sense by profibus tester) . In 10 minutes I have 4 - 5 illegal frames in network. The problem is 10 or more time a day the cycling time become 75 ms and the profibus collapse. On control PC (winCC 5) I have a lots of alarms related to drives, panels, and so on . When profibus time become 75 ms all type of alarms came in series by 20 - 30. So any ideas what the reason my profibus to die, all device are perfect grounded I can't get the reason for long cycling time, I try to increase the repeat index form 1 to 3 and typical time become form 10 to 26 ms but nothing - after some time the bus break, so I want to ask how to catch the defective slave or how to manage with this problem at all. Thanks !
azsym Posts: 49 Rating: (0)
Suggestion To thank Quote Answer

7/3/2014 4:09 PM	Rate (0)
eisenpferdreiter Posts: 1058 Rating: (93)	azsym Hi network experts, I have profibus network. On it I have 40 devices - SEW servos, ET200s, some tach, BOSH proportional cards for servo valves, and 2 profibus encoders. The master is S300 CPU 318, and the speed of bus I 1.5 Mbits (have RS485 repeaters). The settings of profibus is on standard the cycling time is about 8 - 9 ms. The longest 12 ms ( sense by profibus tester) . In 10 minutes I have 4 - 5 illegal frames in network. The problem is 10 or more time a day the cycling time become 75 ms and the profibus collapse. On control PC (winCC 5) I have a lots of alarms related to drives, panels, and so on . When profibus time become 75 ms all type of alarms came in series by 20 - 30. So any ideas what the reason my profibus to die, all device are perfect grounded I can't get the reason for long cycling time, I try to increase the repeat index form 1 to 3 and typical time become form 10 to 26 ms but nothing - after some time the bus break, so I want to ask how to catch the defective slave or how to manage with this problem at all. Thanks ! Hi azsym, have you checked if termination of bus is ok? Terminal resistors should be activated only with first and last member of Profibus. If termination resistors are activated somewhere in between too, it might lead to the problems you described.
eisenpferdreiter Posts: 1058 Rating: (93)
Suggestion To thank Quote Answer

7/3/2014 6:29 PM	Rate (0)
azsym Posts: 49 Rating: (0)	.Intrestnig if u miss that it will be very easy to detect the fault. Acctually is the first thing evrybody do in profibus is sometning like do u plug-in into the power sorce (for domestic staff) or do u have gas (for cars). Yes - only first-last slaves have ON on profibus connectors. Are u wrote what only to increase your post index ?
azsym Posts: 49 Rating: (0)	Last edited by: azsym at: 7/3/2014 6:31 PM
Suggestion To thank Quote Answer

7/4/2014 9:52 AM	Rate (0)
eisenpferdreiter Posts: 1058 Rating: (93)	azsym .Intrestnig if u miss that it will be very easy to detect the fault. Acctually is the first thing evrybody do in profibus is sometning like do u plug-in into the power sorce (for domestic staff) or do u have gas (for cars). Yes - only first-last slaves have ON on profibus connectors. Are u wrote what only to increase your post index ? I have done worldwide startups for machines for more than 30 years - you would not believe how often I found termination resistors activated within the bus or no termination at bus end. However, these kind of problems normally come from profibus connectors. Are there some connectors, that are thermally loaded? If shield has bad connection inside a connector and connector is thermally loaded, shield connection could be lost when connector gets warm. Also I have often experienced, that connectors are just plugged in, but not fixated. That could also cause these problems, especially if thermally loaded or if there are vibrations. Generally, to catch the problematic slave, you should look with which address the series of alarms starts and then wire any suspicious slaves to the end of the bus. Thus the follow-up errors of other slaves will be reduced, bus should run more stable, and you can isolate problematic slaves. In most cases these kind of problems arise with bad connectors or ground leakage (which you have already excluded).
eisenpferdreiter Posts: 1058 Rating: (93)
Suggestion To thank Quote Answer

7/4/2014 9:53 AM	Rate (0)
olloy Silver Member Joined: 8/27/2010 Last visit: 4/13/2024 Posts: 417 Rating: (37)	Hi! //What CPU diagnostics buffer says? //Where from did you get info about "have 4 - 5 illegal frames in network"? I suggest you to use Profibus diagnostics repeater. It can be cost-effective if you are working with such a big networks. The diagnostic repeater recognizes the following types of faults: • Break in the signal line A or B, • Short-circuit in the signal line A or B to shield, • Missing terminators, • Loose contacts, • Invalid cascading depth, • Two or more measuring circuits in a segment, • Too many nodes in a segment, • Node too far away from the diagnostic repeater, • Faulty messages. Hereyou can find a complete manual andhereis a commercial-llok-like leaflet with few another options. Good luck! BR, olloy

Suggestion To thank Quote Answer

7/9/2014 12:18 PM	Rate (0)
azsym Posts: 49 Rating: (0)	It was power fault for second in one RS485 repeater. It lose it 24V for second in resalt of bad eath of servo modor 11kw. Now works fine. Thanks for help.
azsym Posts: 49 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users S_Moderator olloy eisenpferdreiter

|

Share this page:

Share this page on...

Follow us on