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

ET200S 1SI Modbus Master SF Fault

Created by: Navnag at: 2/23/2012 7:10 PM (4 Replies)

Rating (1)

Thanks 0

5 Entries

2/23/2012 7:10 PM	Rate (0)
Navnag Platinum Expert Joined: 11/21/2007 Last visit: 3/16/2025 Posts: 2326 Rating: (309)	Hello We are using several 1SI Modbus Modules in ET200S slaves connected to a S7-400H system through Y-Link Modules. These are used to communicate with energy meters with Modbus RTU Protocol. Periodically the modules start showing SF Fault and stop communicating. The communication restarts only after either the Rack is switched Off and ON orthe Module is Plugged out and Plugged IN. As the Modules are in ET200S racks downward of Y-Link, we cannot read the Module error in Hardware Diagnostics. We routinely use these 1SI Modules for similar application ( in non H systems without Y-Link ) without any problem. We have also checked and rechecked the Grounding, shielding and bus termination etc and cannot find any problem. Any advise on solving the problem would be welcome. Thanks Navnag
	There is no such thing as the last bug in a program There are no stubborn bugs, There are only stubborn Debuggers.
Suggestion To thank Quote Answer

2/25/2012 11:44 PM	Rate (1)
Rated X Posts: 1547 Rating: (129)	Hi Navnag, have you already evaluated diagnostic information from your communication blocks? You can add some programm that will save the additional error inf according to http://support.automation.siemens.com/WW/view/de/9260793/0/enchapter 3.7.3 in case of error. Best is to record several errors including system time in a specific error DB. Or you read in your program in case of error the diagnostic data as given in instruction of Y-link http://support.automation.siemens.com/WW/view/de/1142696/0/enchapter 12.1.3 If this does not help you can monitor subnet of Y-link or your modbus communication with a data analyzer to understand reason of break.
Rated X Posts: 1547 Rating: (129)
Suggestion To thank Quote Answer

2/26/2012 9:22 AM	Rate (0)
Navnag Platinum Expert Joined: 11/21/2007 Last visit: 3/16/2025 Posts: 2326 Rating: (309)	Thanks Rated X Shall try these suggestions and post results. Cheers Navang
	There is no such thing as the last bug in a program There are no stubborn bugs, There are only stubborn Debuggers.
Suggestion To thank Quote Answer

2/27/2012 9:41 AM	Rate (0)
Navnag Platinum Expert Joined: 11/21/2007 Last visit: 3/16/2025 Posts: 2326 Rating: (309)	Hello We have observed the Status Word of 1SI Send/Receive Blocks for affected 1SI Modules. Even when the affected 1SI module is showing SF fault ( the Status is showing 0000h value ) Moreobservation : a) Even if we switch off the rack in which the 1SI is showing SF and switch ON again, the SF fault does not go away. The Fault resets only if we snap out the 1SI module and plug it in again. b) The Y-Link does not show any fault in its Diagnostics information, even when the 1SI Module(s) in the ET200S Rack connected to it are showing SF fault and are not communicating. Meanwhile I have setup the system to log the 1SI Send/Receive Status in WinCC Tag Logging so that we can observe the same over a period of time. Any more suggestiononunderstanding and solving this problem ? Thanks Navnag
	Last edited by: Navnag at: 2/27/2012 9:42 AM There is no such thing as the last bug in a program There are no stubborn bugs, There are only stubborn Debuggers.
Suggestion To thank Quote Answer

3/1/2012 4:58 AM	Rate (0)
Navnag Platinum Expert Joined: 11/21/2007 Last visit: 3/16/2025 Posts: 2326 Rating: (309)	Hello Any suggestions ? Navnag
	There is no such thing as the last bug in a program There are no stubborn bugs, There are only stubborn Debuggers.
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on