Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Alarm 810004 with 25201, 26102

Created by: PISCEAN 2010 at: 6/9/2011 1:50 PM (12 Replies)

Rating (1)

Thanks 2

Result pages:: |; 1 | 2; |

13 Entries

Entries per page: 10 | all

6/9/2011 1:50 PM	Rate (0)
PISCEAN 2010 Diamond Expert Joined: 4/23/2010 Last visit: 11/23/2024 Posts: 8092 Rating: (880)	Hello Experts, On HBM with 840 Di, system trips on “810004- Stop/Abort event error analysis via step7 required” along with alarms 25201, 26102,380500 with all X,Y,Z,W,B axes drive fault & sign of life missing alarms. As NC gets reset/reboot, couldn’t go on line to check PLC. Why this problem occurs & how to troubleshoot it?

Suggestion To thank Quote Answer

6/9/2011 2:02 PM	Rate (0)
makaveli Posts: 259 Rating: (5)	Hi, Could you attach you plc project? With regards, makaveli
makaveli Posts: 259 Rating: (5)
Suggestion To thank Quote Answer

6/9/2011 3:54 PM	Rate (0)
pfuser Silver Member Joined: 9/18/2006 Last visit: 11/14/2024 Posts: 593 Rating: (64)	Hi. See the diagnostic buffer.

Suggestion To thank Quote Answer

6/9/2011 7:31 PM	Rate (0)
OvidiuNastac Silver Member Joined: 1/29/2008 Last visit: 7/26/2022 Posts: 419 Rating: (19)	Hi It seems that you have a problem with the profibus communication. Do you changed the standard profibus allocation? Good luck Nit

Suggestion To thank Quote Answer

6/10/2011 5:53 AM	Rate (0)
PISCEAN 2010 Diamond Expert Joined: 4/23/2010 Last visit: 11/23/2024 Posts: 8092 Rating: (880)	makaveli Hi, Could you attach you plc project? With regards, makaveli Hello Makveli, Please see the attached file. Attachment pegard_p.zip (393 Downloads)

Suggestion To thank Quote Answer

6/10/2011 5:55 AM	Rate (0)
PISCEAN 2010 Diamond Expert Joined: 4/23/2010 Last visit: 11/23/2024 Posts: 8092 Rating: (880)	pfuser Hi. See the diagnostic buffer. Where & how?

Suggestion To thank Quote Answer

6/10/2011 5:57 AM	Rate (0)
PISCEAN 2010 Diamond Expert Joined: 4/23/2010 Last visit: 11/23/2024 Posts: 8092 Rating: (880)	Nit Hi It seems that you have a problem with the profibus communication. Do you changed the standard profibus allocation? Good luck Nit Hi Nit, I suspect for the same & I checked the profibus termination also. Found OK. Also this problem arised all of sudden, while the machine was running. No any modifications, alterations are carried out. Machine is running from last almost 2 years.

Suggestion To thank Quote Answer

6/10/2011 6:17 AM	Rate (1)
pfuser Silver Member Joined: 9/18/2006 Last visit: 11/14/2024 Posts: 593 Rating: (64)	DEEPSTR2010 pfuser Hi. See the diagnostic buffer. Where & how? Hi. Simatic Manager Menu: PLC->Diagnostic/Setting->Module Information->Diagnostic buffer The diagnostic buffer displays the diagnostic messages in the order in which they occur. The first entry contains the newest event. The number of entries in the diagnostic buffer is dependent on the module and its current operating mode. Diagnostic events include the following: Faults on a module Errors in the process wiring System errors in the CPU Mode transitions on the CPU Errors in the user program User-defined diagnostic events (via the system function SFC52).

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users PISCEAN 2010

6/10/2011 6:18 AM	Rate (0)
OvidiuNastac Silver Member Joined: 1/29/2008 Last visit: 7/26/2022 Posts: 419 Rating: (19)	Hi If you have a series backup try to install it or you can check with the online STEP 7, click on CPU, right clik->PLC->Hardware diagnostic. Good luck Nit

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users PISCEAN 2010

6/10/2011 6:39 AM	Rate (0)
PISCEAN 2010 Diamond Expert Joined: 4/23/2010 Last visit: 11/23/2024 Posts: 8092 Rating: (880)	pfuser DEEPSTR2010 pfuser Hi. See the diagnostic buffer. Where & how? Hi. Simatic Manager Menu: PLC->Diagnostic/Setting->Module Information->Diagnostic buffer The diagnostic buffer displays the diagnostic messages in the order in which they occur. The first entry contains the newest event. The number of entries in the diagnostic buffer is dependent on the module and its current operating mode. Diagnostic events include the following: Faults on a module Errors in the process wiring System errors in the CPU Mode transitions on the CPU Errors in the user program User-defined diagnostic events (via the system function SFC52). Hi pfuser, Thank you for your reply. But when the system trips on this problem, NC starts rebooting & as such the communication fails. Again user has to exit & restart the machine. During this excercise as PLC also loses the comunication couldnot check the dignosis buffer. Is there any other way?

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on