Chapter 8 Error Displays
Contents
1. ERROR MESSAGES 8 11 Table 8 6 DAP Mode Error Displays with Suggested Actions Cont Error Display P964 ENTRY ERROR COMMAND INVALID xxxxx NOT VALID P964 ENTRY ERROR DELAY TIME xx NOT VALID P964 ENTRY ERROR MEMORY ADDRESS xxxxxx NOT VALID P964 ENTRY ERROR REFERENCE NUMBER xxxxx NOT VALID P964 WARNING 01 SYSTEM ERROR 984 RCVD INVALID COMMAND P964 WARNING 02 SYSTEM ERROR 984 RCVD INVALID REFERENCE TYPE P964 WARNING 03 SYSTEM ERROR 984 RCVD INVALID COMM PORT NUMBER P964 WARNING 04 SYSTEM ERROR 984 RCVD INVALID MESSAGE PACKET P964 WARNING 05 COMM TIMEOUT ERROR CONNECT FAILED RETRY Cause Reference number is outside configured range in controller Delay time entered not decimal value in correct range Memory address not decimal value in correct range Reference number not in controller Invalid command sent to controller Invalid reference type sent to controller Invalid MODBUS or ASCII port number sent to controller Message with invalid format sent to controller No communication within required time Suggested Action Re enter reference number within controller configuration or reconfigure controller Re enter delay time Must be decimal value from 1 to 20 Re enter memory address Must be decimal value from 300000 to 365535 Check that reference number is valid type Oxxxx 1Xxxx 3XXXX 4XXXx and is configured in controller 1 Press CLEAR2. 984 START ERR 13 INVALID TRAFFIC COP TYPE 984 START ERR 14 984 FAILED CPU DIAGNOSTIC TEST 984 START ERR 15 ERROR IN 984 REAL TIME CLOCK 984 START ERR 16 984 WATCHDOG TIMER EXPIRED 984 SYMPTOM 05 PROM CHECKSUM PROBABLE CAUSE EXEC PROM PACK 984 SYMPTOM 10 MEMORY ERROR PROBABLE CAUSE MEMORY BOARD 984 SYMPTOM 20 MEMORY ERROR PROBABLE CAUSE MEMORY BOARD 984 SYMPTOM 30 MICROCODE ERROR PROBABLE CAUSE CPU BOARD Invalid traffic cop type detected in controller 984 controller failed diagnostic test Error detected in 984 real time clock 984 watch dog timer not reset within specified time Controller will not run due to PROM checksum error Controller will not run due to page 0 memory error Controller will not run due to page F memory error Controller will not run due to illegal microcode error 1 Press CLEAR and retry 2 Check controller program for interference with traffic cop area 3 Replace memory board 4 If retries fail contact Modicon 1 Press CLEAR and retry 2 Replace CPU board 3 If retries fail contact Modicon 1 Press CLEAR and retry 2 Replace CPU board 3 If retries fail contact Modicon 1 Press CLEAR and retry 2 Check program for too many DX blocks 3 If retries fail contact Modicon 1 Press CLEAR and retry 2 Replace controller exec PROM pack 3 If retries fail call Modicon 1 Press CLEAR and retry 2 Replace memory board
3. Denied access to password table Suggested Action Memory protect must be unlocked to perform desired action Stop controller Then perform action None required Retry controller start Verify that controller is properly configured Log in Retry command Verify that controller is properly configured Verify that controller is properly configured and can be started Verify that controller is properly configured and can be started continued Table 8 2 884 M84 User Error Displays with Suggested Actions Cont Error Display Cause Suggested Action TE E E This feature is not Call Modicon USER ERROR 21 supported at this time UNSUPPORTED FEATURE erionit T naman n Watchdog timer Verify the controller is properly USER ERROR 22 expired configured and can be started WATCHDOG TIMER EXPIRED wick earns fl keene eee eee eet Corrupted user logic Verify that controller is properly USER ERROR 23 configured and can be started UNKNOWN OPCODE Other errors should not occur The general display for these errors contains the error number with no error text similar to Figure 8 1 ERROR MESSAGES 8 7 884 M84 System Errors System errors in the 884 and M84 may give rise to error messages These are shown in Table 8 3 Table 8 3 884 M84 System Error Displays with Suggested Actions Error Display Cause Suggested Action THE Tiwcscdeui dunlentvestaes
4. Suggested Action Change address to fall in assigned range Change to an even value No action needed Controller is reset Check for invalid element type or reference continued Table 8 5 484 Error Messages Causes and Actions Cont Error Display Cause Suggested Action BBG oreo o pisces uv vace i piastcta ues Controller s memory Set memory protect to OFF ERROR cscspittnsecrs 11 protect is ON MEMORY PROTECT ON ior na a AGA ii e ai Controller running Stop controller ERROR poussait 12 SYSTEM NOT STOPPED nsina DAP Mode Error Messages Table 8 6 lists DAP mode error message displays causes and suggested actions Table 8 6 DAP Mode Error Displays with Suggested Actions Error Display P964 ENTRY ERROR CANNOT FORCE COIL WITH 984 IN RUN MODE P964 ENTRY ERROR CANNOT FORCE ENABLED COIL P964 ENTRY ERROR COMMAND INVALID WITH CONTROLLER IN RUN MODE P964 ENTRY ERROR COMMAND INVALID WITH MEMORY PROTECT KEY ON Cause Coils can only be forced when controller is stopped Coils can only be forced when disabled Command can only be performed when controller is stopped Command can only be performed when memory protect is off Suggested Action Go to CMD menu stop controller and retry Display coil press DISABLE and retry Go to CMD menu stop controller and retry Turn 984 controller memory protect key to off position Retry continued
5. 2 00008 INVALID COMMAND WBA ices coves av aae teen Seis Address is invalid TOF T Memory protect is on ERROR O3 eeeeeee MEMORY PROTECT TT renee eee ee er crore te Invalid reference or range VD E senacve Invalid parameter a cence rr terre et Controller is running ERROR OQ 00 000 CONTROLLER IS RUNNING esseere TErau t Not logged in ERROR 10 iccecencied once NOT LOGGED IN Te a E AS Coil is not disabled Suggested Action Verify controller is properly configured Use a valid address Turn memory protect off Use valid reference or range Use valid parameter Stop controller Log in Disable coil continued ERROR MESSAGES 8 9 Table 8 4 584 984 Error Displays with Suggested Actions Cont Error Display COIL DISABLE NOT ALLOWED ceeee Table 8 5 484 Error Messages Causes and Actions Error Display 8 10 ERROR MESSAGES Cause illegal configuration Coil disable not allowed 984 only 484 Error Messages Suggested Action Reconfigure controller Login and turn memory protect off Verify controller is properly configured In addition to unexpected errors the error messages shown in Table 8 5 may appear when connected to a 484 controller Cause Address is beyond allowed range Lower member of addressing word pair has odd value Does not correspond with valid message types Invalid data
6. 3 If retries fail call Modicon 1 Press CLEAR and retry 2 Replace memory board 3 If retries fail contact Modicon 1 Press CLEAR and retry 2 Replace CPU board 3 If retries fail contact Modicon continued ERROR MESSAGES 8 15 Table 8 6 DAP Mode Error Displays with Suggested Actions Cont Error Display 984 SYMPTOM 40 MINICODE ERROR PROBABLE CAUSE CPU BOARD 984 SYMPTOM 50 BAD PORT PARAM PROBABLE CAUSE MEMORY BOARD 984 SYMPTOM 60 MEM PARITY ERROR PROBABLE CAUSE MEMORY BOARD 984 SYMPTOM 70 DIM AWARENESS PROBABLE CAUSE MEMORY BOARD 984 SYMPTOM 100 P964 RCVD UNKNWN DEAD ERROR CODE CONTACT MODICON 984 WARNING 100 P964 RCVD UNKNWN RAP ERROR CODE CONTACT MODICON Cause Controller will not run due to illegal minicode error 984 will not run due to invalid port parameter Controller will not run due to parity error in memory Controller will not run unless configured P964 received an unknown error code from the 984 P964 received an unknown error code from the 984 Suggested Action 1 Press CLEAR and retry 2 Replace CPU board 3 If retries fail contact Modicon 1 Press CLEAR and retry 2 Replace memory board 3 If retries fail contact Modicon 1 Press CLEAR and retry 2 Replace memory board 3 If retries fail contact Modicon 1 Configure 984 using P190 and AS T984 204 2 Retry communications 1 Retry operation 2 If retries
7. see are shown Table 8 1 describes the MODBUS Functional Errors that may occur their causes and suggested actions Table 8 1 MODBUS Functional Error Displays with Suggested Actions Error Display Cause TAD E E AE Function requested is MODBUS ERROR 1 not allowed ILLEGAL FUNCTION Tl e E E Address is not allowed Te E EE Data or end address is MODBUS ERROR 3 not allowed ILLEGAL DATA OR END ADDRESG Plies AS E EEE Controller error 8 4 ERROR MESSAGES Suggested Action Verify that controller is properly configured and can be started Verify that controller is properly configured and can be started Verify that controller js properly configured and can be started Verify that controller is properly configured and can be started 884 M84 Error Messages Figure 8 3 Link Error Display Table 8 2 884 M84 User Error Displays with Suggested Actions Error Display USER ERROR 01 OTHER USER LOGGED IN eee USER ERROR O4 CONTROLLER IS RUNNING eee 884 M84 Link Errors These link errors such as Message Ack should be handled by the P965 internally In those situations in which the P965 cannot overcome the link error the Link Error Display Figure 8 3 appears nn is the link error number NOTE For link errors 12 13 and 14 the third line of the display shows RESETTING LINK and the P965 automatically issue
8. to erase the error message from the 984 START ERR 01 NO EOL DETECTED OR BAD NUMBER OF SEGMENTS 984 START ERR 02 STATE RAM TEST FAILED 984 START ERR 03 START OF NETWORK NODE DID NOT START SEGMENT 984 START ERR 04 MULTI RATE SOLVE TABLE IS INVALID No end of logic node found or illegal number of logic segments Test of random access memory in controller failed No start of network node at beginning of logic segment Invalid multi rate solve table in 984 controller screen No retry is performed when the CLEAR key is pressed 1 Press CLEAR and retry 2 Reload user data tape 3 If retries fail contact Modicon 1 Press CLEAR and retry 2 Replace 984 IOP board 3 If retries fail contact Modicon 1 Press CLEAR and retry 2 Reload user data tape 3 If retries fail contact Modicon 1 Press CLEAR and retry 2 Reload user data tape 3 If retries fail contact Modicon continued ERROR MESSAGES 8 13 Table 8 6 DAP Mode Error Displays with Suggested Actions Cont Error Display Cause Suggested Action 984 START ERR 05 ILLEGAL PERIPHERAL INTERVENTION 984 START ERR 06 984 HAS NOT YET BEEN CONFIGURED 984 START ERR 07 984 MEMORY PARITY ERROR 984 START ERR 08 984 PERIPHERAL PORT STOP 984 START ERR 09 ILLEGAL 984 CONFIGURATION 984 START ERR 10 COIL IS DISABLED WITH 984 IN RUN MODE 984 START ERR 11 CHECKSUM ERROR IN 984 LOGIC 984 START ERR 12
9. Chapter 8 Error Displays e Error Displays e Types of Errors e MODBUS Functional Error Messages e 884 M84 Error Messages e 584 984 Error Messages e 484 Error Messages e DAP Mode Error Messages e 584 984 Stopcode Error Messages ERROR MESSAGES 8 1 Error Displays This chapter presents P965 error displays in alphanumeric order for easy reference Descriptions and suggested actions are also given Several types of error displays appear in the P965 Some are due to errors in P965 operation and some are due to controller faults Upon receiving an error indication control is returned to the menu level appropriate for modifying the parameters used to invoke the command The parameters can be changed and a retry executed Generally this results in returning up one menu level from the current operation invalid operator entries generally result in an error display On some invalid operator entries the invalid key or keys have no effect but no error screen is displayed Upon clearing the error display a screen appears requesting operator input When an error display appears locate the display in this section If retries or other suggested actions fail contact your local Modicon representative or the Modicon Field Support Center in North Andover Massachusetts You can contact the Modicon Field Support Center by telephone The numbers are given in the front of this guide Types of Errors 8 2 ERROR MESSAGES Error
10. INVALID NODE IN 984 LOGIC Illegal peripheral intervention 984 controller must be configured before communicating with P964 Parity error detected in 984 controller memory Peripheral port error detected in controller Errors detected in configuration of controller Detected disabling of coil with 984 running Checksum error detected in 984 controller logic Invalid node type detected in 984 controller logic 1 Press CLEAR and retry 2 Reload user data tape 3 If retries fail contact Modicon 1 Load user data tape OR 2 Configure controller with P190 and AS T984 004 1 Press CLEAR and retry 2 Reload user data tape 3 If retries fail contact Modicon 1 Press CLEAR and retry 2 Reload user data tape 3 If retries fail contact Modicon 1 Reload user data tape OR 2 Reconfigure 984 using P190 and AS T984 004 3 Replace memory board 4 If retries fail contact Modicon 1 Press CLEAR and retry 2 Reload user data tape 3 If retries fail contact Modicon 1 Press CLEAR and retry 2 Reload user data tape 3 Replace memory board 4 If retries fail contact Modicon 1 Press CLEAR and retry 2 Reload user data tape 3 Check for tape and controller compatibility 4 If retries fail contact Modicon 8 14 ERROR MESSAGES continued Table 8 6 DAP Mode Error Displays with Suggested Actions Cont Error Display Cause Suggested Action
11. Messages are organized in groups One group pertains to DAP mode These are listed in Table 8 6 Another group pertains to general MODBUS errors Other groups of error messages are organized by controller type 484 884 M84 and 584 984 In the error displays shown below TTT is the controller type Unexpected Errors UNEXPECTED ERROR is a category of error that should not occur For example a legitimate 984 error may result from an operation modifying user logic Since the P965 does not modify user logic this error should never occur If this error or other errors not supported by the P965 is returned to the P965 from the controller the Unexpected Error Display appears The general format of this display is shown in Figure 8 1 Figure 8 1 Tb E ee kl USER ERROR nn UNEXPECTED ERROR Unexpected Error Display nn specifies the error number If an unexpected error occurs perform the following steps Retry the operation If this is not successful e Power the unit off and on and retry again e In any case inform Modicon of the error If the P965 receives what it believes to be an error message from a controller but cannot classify the message as to USER SYSTEM MODBUS or LINK error the Unknown Error Display Figure 8 2 appears Figure 8 2 ERROR DETECTED Unknown Error Display Ce ed ERROR MESSAGES 8 3 MODBUS Functional Error Messages In this section the MODBUS functional error displays that you may
12. and retry 2 If retries fail contact Modicon 1 Press CLEAR and retry 2 If retries fail contact Modicon 1 Press CLEAR and retry 2 If retries fail contact Modicon 1 Press CLEAR and retry 2 If retries fail contact Modicon 1 Press RETRY F2 Screen blanks for 0 5 sec then retries 2 If retries fail contact Modicon 8 12 ERROR MESSAGES continued Table 8 6 DAP Mode Error Displays with Suggested Actions Cont Error Display Cause Suggested Action P964 WARNING 06 COMM DATA ERROR REQUEST FAILED RETRY P964 WARNING 07 COMM TIMEOUT ERROR REQUEST ABORTED RETRY CNCL Invalid communication data sent to controller No communication within required time Request not acted on 1 Press RETRY F2 Screen blanks for 0 5 sec then retries 2 If retries fail contact Modicon 1 Press RETRY F2 Screen blanks for 0 5 sec then retries 2 Press CNCL F4 to return to previous display 3 If retries fail contact Modicon NOTE Press the CLEAR key to erase the error message from the P964 WARNING 08 COMM DATA ERROR REQUEST ABORTED RETRY CNCL Invalid communication data sent to controller Request not acted on screen No retry is performed when the CLEAR key is pressed 1 Press RETRY F2 Screen blanks for 0 5 sec then retries 2 Press CNCL F4 to return to previous display 3 If retries fail contact Modicon gt NOTE Press the CLEAR key
13. edsesice Command not allowed SYSTEM ERROR 69 UNSUPPORTED COMMAND c000 VD EE AE T Level of access not Obtain higher level of access SYSTEM ERROR 70 sufficient password INSUFFICIENT PRIVILEGE AUR 1d Beep peer T EA Invalid reference Use a valid reference E a E RRA Discrete not disabled Disable discrete SYSTEM ERROR 74 DISCRETE NOT DISABLED 0 L eE eepettateiiws Read only table Verify controller is properly SYSTEM ERROR 92 cannot be written to configured TABLE IS READ US T Invalid table offset Use valid table or offset length SYSTEM ERROR 93 length INVALID TABLE OFFSET LENGTH WT Tes el et vay tan cowwe bance st Invalid table Use valid table SYSTEM ERROR 94 INVALID TABLE TUT e AT Invalid table data Verify controller is properly SYSTEM ERROR 95 configured INVALID TABLE E A ET Invalid memory Use valid memory address SYSTEM ERROR 97 address INVALID MEMORY ADDRESG 00008 8 8 ERROR MESSAGES 584 984 Error Messages The following error messages may occur with either the 584 or the 984 programmable controller Table 8 4 shows the error messages the causes and gives suggested actions Table 8 4 584 984 Error Displays with Suggested Actions Error Display Cause Tohan eea Command not allowed ERROR O1
14. fail contact Modicon 1 Retry operation 2 If retries fail contact Modicon 584 984 Stopcode Error Messages Whenever a START command fails to cause a 584 or 984 controller to begin running the Unable to Start Display Figure 8 4 appears Figure 8 4 WNABLE TO START Unable to Start Display PO tie eutwe 4 8 16 ERROR MESSAGES Figure 8 5 584 984 Stopcode Error Display Table 8 7 Stopped Controller Error Displays with Suggested Action Press the CLEAR key to display the stopcode value as shown in the 584 984 Stopcode Error Display Figure 8 5 UNABLE TO START xxxx the hexadecimal value of the stopcode CLEAR returns the P965 to the display which originated the START request Table 8 7 lists the four digit hexadecimal codes and the meaning for each code FFFF Controller unhealthy 8000 Controller stopped 4000 Bad 1 O traffic cop 2000 Controller in dim awareness 1000 Bad port intervention 0800 Bad segment scheduler 0400 SON did not start segment 0200 Bad power down checksum 0100 Bad number of DOIL EOL 0080 Watchdog expired 0040 Real time clock failed 0020 Bad coil used table 0010 Remote I O option failed 0008 Illegal node type used 0004 User logic cksum error 0002 Discretes disabled error 0001 Bad configuration Suggested Action Using a P190 or an IBM PC verify that controller has a valid configuration and can be started Reference appropriate controller user manual
15. for corrective action The four digit number in the Stop Code Error Display Figure 8 5 indicates either a single error or the hexadecimal no carry sum of two or more of the errors listed in Table 8 7 For example Controller stopped 8000 Bad coil used table 0020 Illegal node type used 0008 User logic cksum error 0004 StOPCOdE erfor 802C ERROR MESSAGES 8 17
16. s a reset command to the 884 or Micro84 884 M84 User Errors These error messages Table 8 2 may occur in M84 and 884 controllers Other errors should not occur Cause Suggested Action Another user is logged Controller must be logged out In Invalid password Use valid password Stop controller Then perform action The attempted action e g trying to clear memory cannot be performed because the controller is running continued ERROR MESSAGES 8 5 Table 8 2 884 M84 User Error Displays with Suggested Actions Cont Error Display USER ERROR O6 MEMORY PROTECT USER ERROR O6 CONTROLLER IS ALREADY RUNNING USER ERROR 0O7 CONTROLLER IS NOT RUNNING USER ERROR O8 CONTROLLER START FAILED ripear ara USER ERROR O9 NOT LOGGED IN USER ERROR 10 CANNOT PERFORM COMMAND eee USER ERROR 18 CORRUPT DATABASE COMMAND FAILED USER ERROR 19 CAN T ACCESS PASSWORD TABLE 8 6 ERROR MESSAGES Cause The desired action can not be performed because the memory protect is on The attempted action e g trying to start controller cannot be performed because the controller is running Stop controller attempted while controller is not running Controller did not start User not logged in Unacceptable command Command failed due to corrupt database
Download Pdf Manuals
Related Search