Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

SIMADYN D SYSTEM "C" fault

Created by: xiaokulong at: 2/26/2014 3:29 AM (5 Replies)

Rating (0)

Thanks 0

6 Entries

2/26/2014 3:29 AM	Rate (0)
xiaokulong Posts: 3 Rating: (0)	Hello expert, In China, there are a lot of SIMADYN D system operation for excitation system, now according to customer and SIEMENS engineers feedback, often occur “C” fault.The system configuration see following:This system include two channels, every channel include one SIMADYN rack, the rack use 24 slots, and configurate 2 pieces PM6 cards, 2 pieces CS7 cards and other cards. One CS7 cards configurate 3 pieces SS4 (One piece is in charge of connect to PC debugging tools, one is in charge of communication to other channel, last one is in charge of communication to OP monitor), other CS7 card configurate one SS52 card (this is in charge of connect to external monitor via Prifibus).“C” fault often occur at CPU2 card (PM6), sometime SS4 cards issue in this fault, sometime SS52 issue in this fault. A part of fault may reset via restart system power and clear dust at card, but some fault only reset via change new cards.Base on customer data collection, basic most fault occur in winter, if add environment temperature and often clear dust, the fault will reduce.But I didn’t find the reason of “ C” fault, I hope you may help me.
xiaokulong Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

2/26/2014 3:59 AM	Rate (0)
KSN Platinum Expert Joined: 8/25/2006 Last visit: 11/17/2024 Posts: 2211 Rating: (280)	Hello. You need to find the reason of 'C'-fault. If you use Step7/CFC/D7-SYS for programming Simadyn D, when the fault occurs, don't reset it. Connect your PG/PC via DUST1 to the local interface of CPU2 (X01), open one chart from CPU2-program and go to the menu 'CPU-Module information'. There will appear the window with 2 tabs ('Error fields' and 'Exception buffer'). Usually, on first tab ('Error fields') you will find the block(s) which is the cause of 'C'-fault. There will be the output(s) of FB with error numbers, e.g. 0x6014. Then you can find the description of fault in CFC-online help, goto CFC-menu 'Help-Contents', switch to Index tab and enter the fault number here.

Suggestion To thank Quote Answer

2/26/2014 6:39 AM	Rate (0)
xiaokulong Posts: 3 Rating: (0)	Thanks for your reply. This equipments use STRUC G/L for programming. Normally we use IBS tools debugging. I don't know whether may exchange from STRUC G toStep7. Could you have other ideas.
xiaokulong Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

2/26/2014 9:39 AM	Rate (0)
KSN Platinum Expert Joined: 8/25/2006 Last visit: 11/17/2024 Posts: 2211 Rating: (280)	Hello. When the next time communication error occurs ('C'), start HEX/Debug Monitor from IBS-menu. Enter ? or dh. There will be created file HEX.txt in the IBS directory, it contains log of HEX/Debug Monitor. In this file you should find the command to view theDiagnostics of the error panels, something like this string: Diagnostics of the error panels: jm 0x800..... Then enter this command: jm 0x800..... In the file HEX.txt you will get the contents of error panels, where you could find the FB(s) that is the cause of error and error code(s), e.g. 0x6014. Look for error-code description in the manual.

Suggestion To thank Quote Answer

2/27/2014 2:53 AM	Rate (0)
xiaokulong Posts: 3 Rating: (0)	Hello, When the 'C' Fault occur, we can’t communication with the CPU, the customer tried to use the IBS connect to CPU but failed. So we can’t get the error-code by this method.Do you have any other suggestion for this condition to get the error-code?Thanks a lot.
xiaokulong Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

2/27/2014 4:14 AM	Rate (0)
KSN Platinum Expert Joined: 8/25/2006 Last visit: 11/17/2024 Posts: 2211 Rating: (280)	Hello. You need to connect your PG/PC directly to the local CPU interface (X01 in PM6), because when communication error is active other interfaces may not work (CS7/SS4). Try the latest version ofIBS. Check COM-port settings. Try to do the following: 1. Start IBS, then menu 'Activities-IBS Program'. 2. Then menu 'Diagnostics-Start Debug Monitor', enter CPU number. 3. Then menu 'Service-Exit IBS Program'. 4. Then menu 'Activities-HEX/Debug Monitor'.

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on