You are not registered yet. Please click here to register!


 
 
plc storereviewsdownloads
This board is for PLC Related Q&A ONLY. Please DON'T use it for advertising, etc.
 
Try our online PLC Simulator- FREE.  Click here now to try it.

---------->>>>>Get FREE PLC Programming Tips

New Here? Please read this important info!!!


Go Back   PLCS.net - Interactive Q & A > PLCS.net - Interactive Q & A > LIVE PLC Questions And Answers

PLC training tools sale

Reply
 
Thread Tools Display Modes
Old October 18th, 2016, 02:00 PM   #1
harryggianakis
Member
United States

harryggianakis is offline
 
Join Date: Oct 2016
Location: Philadelphia, Pa
Posts: 20
Major Fault Type 1, Code 62

A PLC controller at one of our sites had a major fault, and the failure code was Type 1, Code 62. When we cleared the fault, the controller was OK. However, we are not sure what caused this fault. Based on the error code, I'm assuming that they're using a secure digital (SD) card. I've looked through the Rockwell Knowledge Base, and found certain references that could cause this fault, such as;

- Systems wth PowerFlex drives that support ADC (automatic device configuration), which will cause the secondary controller to experience a Major Non-recoverable Fault (i.e. and which cannot be trapped by a Program Fault Handling routine)
- Redundant controllers with firmware that does not support motion applications. When the CIP Motion axes drives come online, the controllers will then shut down
- Outdated firmware
- Improperly done on-line edits

From what I've also read, Type 1, Code 61 and Type 1, Code 62 Major Faults are the only ones that leave 'fault logs' on the SD drive (I believe as .BIN files). So, is my best course of action to send those log files to Rockwell for analysis, or is there a way to easily access & review those .BIN files myself? Again, thanks in advance for any help that you can provide.
  Reply With Quote
Old October 18th, 2016, 02:10 PM   #2
nhatsen
Member
Venezuela

nhatsen is offline
 
Join Date: Oct 2010
Location: Argentina
Posts: 679
Quote:
Originally Posted by harryggianakis View Post
my best course of action to send those log files to Rockwell for analysis
That's the best course.
__________________
"If you can't solve a problem, then there is an easier problem you can solve: find it." (George Pólya)
  Reply With Quote
Old October 18th, 2016, 02:22 PM   #3
harryggianakis
Member
United States

harryggianakis is offline
 
Join Date: Oct 2016
Location: Philadelphia, Pa
Posts: 20
Major Fault Type 1, Code 62

nhatsen..., Thanks for the input

FYI: Would still be interested in hearing the opinion of others on this issue
  Reply With Quote
Old October 18th, 2016, 03:47 PM   #4
Gil47
Member
New Zealand

Gil47 is offline
 
Gil47's Avatar
 
Join Date: Apr 2007
Location: South Island, NewZealand
Posts: 1,319
I found this in a Google search

http://www.plctalk.net/qanda/archive...p/t-75454.html
  Reply With Quote
Old October 18th, 2016, 06:06 PM   #5
harryggianakis
Member
United States

harryggianakis is offline
 
Join Date: Oct 2016
Location: Philadelphia, Pa
Posts: 20
Major Fault Type 1, Code 62

Gil47..., Thanks for the link. It looks like the general guidance (as posted by daba back on May 30th) is to review the .BIN files on the SD card to see what the problem could be.

I hope anyone else whose encountered this fault code (i.e. Type 1, Code 62) with their Rockwell system can post the actual problem that was causing it
  Reply With Quote
Old October 18th, 2016, 06:29 PM   #6
Ken Roach
Lifetime Supporting Member + Moderator
United States

Ken Roach is online now
 
Ken Roach's Avatar
 
Join Date: Apr 2002
Location: Seattle, WA
Posts: 15,119
Those general fault codes cover a number of faults that can only be inferred or investigated by looking at the logs.

It's like saying "I have a headache"; could be a hangover, could be a brain tumor. Further investigation is necessary, and that's what the fault logs are for.

Over the history of the ControlLogix, sometimes known issues have been discovered in the field because of patterns and evidence that come from fault logs. That sort of thing wasn't found, or findable, in the development labs.

Is this from the same plant shutdown event that you posted about the DeviceNet system malfunction ?
  Reply With Quote
Old October 18th, 2016, 07:45 PM   #7
harryggianakis
Member
United States

harryggianakis is offline
 
Join Date: Oct 2016
Location: Philadelphia, Pa
Posts: 20
Major Fault Type 1, Code 62

Ken..., Thanks for your perspective. It makes a lot of sense

Actually, I think this problem is decoupled from the DeviceNet configuration parameters issue
  Reply With Quote
Reply
Jump to Live PLC Question and Answer Forum

Bookmarks


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Topics
Thread Thread Starter Forum Replies Last Post
VBA code Guru's dbh6 LIVE PLC Questions And Answers 6 April 2nd, 2013 03:17 PM
Orphaned PLC code twu026 LIVE PLC Questions And Answers 26 October 21st, 2008 10:28 AM
Automatin Direct Changes Download ArikBY LIVE PLC Questions And Answers 53 May 12th, 2004 01:05 AM
SIMATIC_WF-726C module problem with IFM Encoders-RM6104 type murarisetty_apparao LIVE PLC Questions And Answers 0 July 7th, 2003 05:36 AM


All times are GMT -5. The time now is 01:53 PM.


.