abb错误代码.pdf

《abb错误代码.pdf》由会员分享，可在线阅读，更多相关《abb错误代码.pdf（24页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、TroubleshootingTroubleshootingIntroductionIntroductionSection 5Section 5This section contains Harmony bridge controller (BRC) trou-bleshooting information. Included is information on moduleerror codes, troubleshooting flowcharts, diagnostic routines,and the module status summary.Error codes provide

2、specific module fault information andappropriate corrective action. Troubleshooting flowcharts pro-vide a quick look at hardware associated problems that mayoccur during module installation and startup. Diagnostic testshelp determine if there is a problem with module componentsor circuitry. They are

3、 useful for testing the module when thesystem is down or there is some other means of controlling theprocess. For example, use the backup module (if redundantmodules are installed) to control the process while testing theprimary module. The module status summary is a 16-bytemodule status record that

4、 provides summary flags for errorconditions, module type, and firmware revision level.Error CodesError CodesBRC module error codes are listed in Table 5-1. The moduledisplays error codes on group A LEDs. Table 5-2 lists statusLED states and other conditions that are indicated byLEDs.Table 5-1. Error

5、 CodesTable 5-1. Error CodesCodeCode1 101020305LEDLED8 8 7 7 6 6 5 5 4 4 3 3 2 2 1 10 0 0 0 0 0 0 10 0 0 0 0 0 1 00 0 0 0 0 0 1 10 0 0 0 0 1 0 1ConditionConditionNVRAM checksum errorAnalog input calibrationI/O module status badConfiguration error(undefined block)Corrective ActionCorrective ActionIni

6、tialize NVRAM. If error recurs call ABBfield service.Check I/O module error.Check module status and I/O modules.Check module status undefined block(modules referenced).WBPEEUI230017B15 - 1Error CodesTable 5-1. Error CodesTable 5-1. Error Codes(continued)CodeCode1 106080A0B0C0DLEDLED8 8 7 7 6 6 5 5 4

7、 4 3 3 2 2 1 10 0 0 0 0 1 1 00 0 0 0 1 0 0 00 0 0 0 1 0 1 00 0 0 0 1 0 1 10 0 0 0 1 1 0 00 0 0 0 1 1 0 1ConditionConditionCorrective ActionCorrective ActionConfiguration error (data typeCheck module status (data type) modules.mismatch)Tripblock activatedSoftware programming errorNVRAM initializedNVR

8、AM opened for writeIntermodule link errorCheck module status.Internal error. If error recurs, call ABB fieldservice.Confirm that NVRAM is initialized; noaction is required.Initialize NVRAM. If error recurs, call ABBfield service.Check the cable connection between pri-mary and secondary BRC modules a

9、t thePBA board.Put position 8 of SW2 in the opposite posi-tion of the primary module SW2 position 8.Check configuration. Correct any faultyvalues. Execute the configuration.0E0F0 0 0 0 1 1 1 00 0 0 0 1 1 1 1Redundancy IDs the samePrimary failed, backup can-not take over, configurationnot current100

10、0 0 1 0 0 0 0111213140 0 0 1 0 0 0 10 0 0 1 0 0 1 00 0 0 1 0 0 1 10 0 0 1 0 1 0 0Check configuration. Correct any faultyPrimary failed, backup can-not take over, data not checkvalues. Execute the configuration.pointedError during write tononvolatile memorySet addresses the same.Backup and primary mo

11、duleaddresses are differentROM checksum errorContact ABB field service.Reformat BRC module.BRC set forINFI-NET/Superloop but in aPlant Loop environmentDuplicate Controlwayaddress detectedHnet failureSet address to unique value in PCU.Check Hnet cabling and connections toPBA board, terminations, and

12、HarmonyI/O blocks. Replace the BRC module ifHnet cabling and connections check out.Repeat configuration download.Check file directory, replace bad file.171D0 0 0 1 0 1 1 10 0 0 1 1 1 0 120210 0 1 0 0 0 0 00 0 1 0 0 0 0 1C program format errorFile system error5 - 2WBPEEUI230017B1Error CodesTable 5-1.

13、 Error CodesTable 5-1. Error Codes(continued)CodeCode1 122232425LEDLED8 8 7 7 6 6 5 5 4 4 3 3 2 2 1 10 0 1 0 0 0 1 00 0 1 0 0 0 1 10 0 1 0 0 1 0 00 0 1 0 0 1 0 1ConditionConditionInvoke C errorUser write violationC program stack overflowConfigureable Logic Interface Check firmware revision level. Ve

14、rify that itFunction Code incompatiblesupports the revision the CLIF was com-piled for.with firmwareUser defined function (UDF)Check configuration. Fix block configura-tion. Fix block reference.block number referenceinvalidUDF function block cannotread programMissing UDF declarationWrong UDF typeMis

15、sing UDF auxiliaryCheck configuration. Fix UDF block file.Corrective ActionCorrective ActionCheck C program and invoke C blocks,correct and rerun.Check C program, correct and rerun.280 0 1 0 1 0 0 0292A2B2C2D2E2F3031323334350 0 1 0 1 0 0 10 0 1 0 1 0 1 000 1 0 1 0 1 10 0 1 0 1 1 0 00 0 1 0 1 1 0 10

16、0 1 0 1 1 1 00 0 1 0 1 1 1 10 0 1 1 0 0 0 00 0 1 1 0 0 0 10 0 1 1 0 0 1 00 0 1 1 0 0 1 10 0 1 1 0 1 0 00 0 1 1 0 1 0 1Not enough memory for UDFRevise configuration.Add function code 190 to configuration.Put correct UDF type in configuration.Put function code 198 in blockconfiguration.Check firmware

17、revision level. Verify that itsupports UDF.Check Basic program, correct and rerun.UDF compiler and firmwareincompatibleBasic program errorPrimary active during failoverReplace primary and/or backup to deter-attemptmine faulty module.Memory or CPU faultAddress or bus errorIllegal instructionInternal

18、error - trace/privi-lege violationInternal error -spurious/unassigned excep-tionInternal error - divide by 0 orcheck instructionInternal error - undefined trap Restart BRC module. If error recurs,replace BRC module.Board level hardware errorContact ABB field service.Reset BRC module. If error recurs

19、,replace BRC module.Replace BRC module. If error recurs, callABB field service.Reset BRC module. If error recurs,replace BRC module.3637380 0 1 1 0 1 1 00 0 1 1 0 1 1 10 0 1 1 1 0 0 0WBPEEUI230017B15 - 3Error CodesTable 5-1. Error CodesTable 5-1. Error Codes(continued)CodeCode1 13F4080C0XX2LEDLED8 8

20、 7 7 6 6 5 5 4 4 3 3 2 2 1 10 0 1 1 1 1 1 10 1 0 0 0 0 0 01 0 0 0 0 0 0 01 1 0 0 0 0 0 0ConditionConditionNormal stopBackup - cold takeover readyBackup - hot takeover readyPrimary - operatingUnknownContact ABB field service.None.Corrective ActionCorrective ActionNOTES:NOTES:1. Code numbers are hexad

21、ecimal digits.2. This symbol represents any LED combination not specifically addressed in this table.Table 5-2. Status LED and Other ConditionsTable 5-2. Status LED and Other ConditionsLEDLEDStatusConditionConditionOffCheck power.Check module seating.Check jumper J4. Remove if installed.If power and

22、 seating are okay, remove the moduleand replace with identically configured module.RedGreenGroup A6/7/8OffPress reset button. If LED remains red, remove themodule and replace with identically configured module.None - normal.Check power.Check module seating.If power and seating are okay, remove the m

23、oduleand replace with identically configured module.RedGroup A7/8OffNone - indicates primary module is in simulationmode.Check power.Check module seating.If power and seating are okay, remove the moduleand replace with identically configured module.RedNone - indicates primary module.Corrective Actio

24、nCorrective Action5 - 4WBPEEUI230017B1FlowchartsTable 5-2. Status LED and Other ConditionsTable 5-2. Status LED and Other Conditions(continued)LEDLEDGroup A8ConditionConditionOffCheck power.Check module seating.If power and seating are okay, remove the moduleand replace with identically configured m

25、odule.RedNone - indicates backup module in redundantconfiguration.Corrective ActionCorrective ActionFlowchartsFlowchartsThe flowcharts in Figures 5-1 and 5-2 provide a quick look athardware related problems that may occur during moduleinstallation and startup. Use the flowcharts to troubleshootprobl

26、ems that may have occurred because of improper hard-ware installation.DiagnosticsDiagnosticsThe BRC firmware contains diagnostic routines that can beinvoked during module power up. These routines verify theproper operation of the module components and circuitry. Put-ting the BRC module in the diagno

27、stic mode allows the moduleto perform a variety of diagnostic tests but suspends normaloperation. Therefore, use it during installation to check moduleintegrity, when the system is down, or transfer system controlto a backup BRC module to check a currently operating mod-ule. Refer to Diagnostic Test

28、 SelectionDiagnostic Test Selection in this section forinformation on how to use the diagnostic routines. Table5-5lists each test routine and gives a brief description.OverviewOverviewUse the BRC dipswitches to select the required diagnostic rou-tine. Diagnostic test results display on the BRC modul

29、e frontpanel LEDs. Both group and individual tests can be executed.The typical procedure is to select a diagnostic routine to exe-cute, set the module dipswitches accordingly, reset the mod-ule, and observe the results on the faceplate LEDs. If the halton error feature is disabled, the selected test

30、 runs repeatedlyuntil the module is reset and another test is selected. If halt onWBPEEUI230017B15 - 5DiagnosticsSTARTNOSTATUSLED OFF?YESNOSTATUS LEDRED?YESNOSTATUS LEDORANGE?YESNOSTATUS LEDGREEN?YESPOWER ON?YESNOTURN ONPOWERERROR CODEDISPLAYED?YESNOREMOVE MACHINEFAULT TIM ERJUMPER FROMBRC MODULEDON

31、EBRCMODULE SEATEDIN MMU?YESNOSEATBRCMODULE IN MMUBACKPLANEPERFORMCORRECTIVEACTION APPLICABLETO ERROR CODEDISPLAYEDREMOVE MACHINEFAULT TIM ERJUMPER FROM BRCMODULERESETBRC MODULECHECK +5 VDCOUTPUTS ONMMU BACKPLANE+5 VDCON MMUBACKPLANE?YESNOTROUBLESHOOTPOWER SYSTEM.REFER TO APPLICABLEINSTRUCTIONSYESREP

32、LACEBRC MODULEREPLACEBRC MODULET01270AFigure 5-1. Troubleshooting Flowchart (Serial Port)Figure 5-1. Troubleshooting Flowchart (Serial Port)error feature is enabled, the test stops and the LEDs displaythe failure.An additional module is required for I/O expander bus com-munication tests. To test I/O

33、 expander bus communications:1.Set the dipswitches on the IMDSO14 (DSO) module and theBRC module to the settings in Table 5-3.2.Insert the DSO module in the same module mounting unit(MMU) as the BRC module.5 - 6WBPEEUI230017B1STATUSLED RED?NODiagnosticsSTARTRS-232-CLINE ERRORSON BRC LEDs(CODE 15)?YE

34、SF1OPEN ONTU?YESREPLACE F1WITH 1.0 A250 V FUSENODONENO+24 VDCCONNECTED TOTU?YESNOREFER TO NTMP01INSTRUCTIONSTOCONNECT POWERMEASURE24 VDC ATTU?YESNOCHECK POWERCABLING TOTU/TM.CHECK POWERSYSTEM.RS-232-CCABLE WITH NOCROSSOVERS CONNECTTU (P5 OR P6) TOCOMPUTER?YESNOREPLACE CABLE WITHCABLE HAVING STRAIGHT

35、PIN TO PIN CONNECTIONBETWEEN DB-25CONNECTORSHANDSHAKEJUMPER SETTINGS MATCHAPPLICATION?NOSET JUMPERSFOR APPLICATIONYESTUCABLE INSTALLEDAND CONNECTED TOBRC P3?YESNOINSTALL TUCABLERS-232-CLINE ERRORSON BRC LEDs(CODE 15)?YESCONTACTABBTECHNICALSUPPORTNODONET01271CFigure 5-2. Troubleshooting Flowchart (St

36、atus LED)Figure 5-2. Troubleshooting Flowchart (Status LED)WBPEEUI230017B15 - 7DiagnosticsTable 5-3. DSO and BRC Setup for I/O Expander Bus TestTable 5-3. DSO and BRC Setup for I/O Expander Bus TestModuleModuleIMDSO14BRC-100Address DipswitchAddress DipswitchPolePole1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8S10

37、 0 0 0 1 1 1 1SW30 0 0 0 1 1 1 1NOTE:NOTE: 0 = closed or on, 1 = open or off.3.There must be continuity between the DSO and BRC mod-ules on the I/O expander bus (i.e., I/O expander bus dip-shunts inserted with straps intact between the DSO and BRCmodules). The modules do not need to be in adjacent s

38、lots.An additional NTMP01 termination unit (TU) is required forredundancy link and SAC link tests.Diagnostic Test SelectionDiagnostic Test SelectionPole one of dipswitch SW5 must be set to the open (off) positionto put the module into the diagnostic mode. The remainingpoles on dipswitch SW5 are used

39、 to select the module addressand communication bus mode. They should remain in theirnormal operating position. Use dipswitch SW2 to select diag-nostic tests. Table 5-4 defines the function of each pole ofdipswitches SW2 and SW5.Table 5-4. Diagnostic Dipswitch SettingsTable 5-4. Diagnostic Dipswitch

40、SettingsDipswitchDipswitchSW5PolePole1234 - 8SW2123 - 8SettingSetting10010 - 31(dec)000 - 2B(hex)FunctionFunctionDiagnostics mode. Test selected withSW2.Not used.Controlway mode.Module bus mode.Module address. Refer to Table 3-1.Special operations disabled.Not used.Test number (ID). Refer to Table 5

41、-5.NOTE:NOTE: 0 = closed or on, 1 = open or off.5 - 8WBPEEUI230017B1DiagnosticsOn dipswitch SW2, poles three through eight select the diag-nostic test. Pole eight is the least significant bit (binary weightone); pole three is the most significant bit (binary weight 32).Refer to Table 5-5 for test ID

42、 values. Pole one selects a specialoperations feature. When enabled, the BRC module will halttest execution whenever the selected test detects an error. Thenumber of the failing test is displayed on the group A LEDs(Fig. 5-3). The group B LEDs display the pass/fail count. Referto Table 5-5 for a des

43、cription of each diagnostic test.Table 5-5. Diagnostic TestsTable 5-5. Diagnostic TestsTest NameTest NameSwitches and LEDsTest-IDTest-ID00DescriptionDescriptionByte value of all dipswitches are exclusive ORed together. Resultsare displayed on LEDs. Status LED is off for even or on for oddtotal.Verif

44、ies CPU instruction set is operational.Calculates checksum of ROM and compares it to value stored inROM during programming.Performs walking one test. Clears, verifies, sets and verifies allRAM. Test includes byte, word and long word accesses.Verifies read and write function of NVRAM.Initializes DUAR

45、T timer for 1-msec interrupts and then waits for itto time-out.Verifies real-time clock is functioning.Sets a latch enabling a level seven interrupt to occur.Sends series of bytes to Controlway verifying timing and transferstatus.Issues software dispatcher request and waits for interrupt to occur.Te

46、sts (in local loopback mode) both serial channels of DUART cir-cuitry that supports the RS-232-C/RS-485 serial ports.Tests (in local loopback mode) both serial channels of DUART cir-cuitry that supports station link and debug port.Sets and resets all interrupt levels verifying proper operation.Test

47、Hnet interface in local loop back mode. Checks Hnet ASICoperation including both channel A and B, shared RAM, timers,time-sync, registers, etc.Reads CRC code from ID-ROM.Executes tests 01 through 0F.CPUROMRAMNVRAMTimerReal-time clockI/O expander busstallControlwayDispatcher IRQ2DUART 0DUART 1Immedia

48、te INTHnet(local loop back)ID ROMUnusedGroup test 10102030405060708090A0B0C0D0E0F10WBPEEUI230017B15 - 9DiagnosticsTable 5-5. Diagnostic TestsTable 5-5. Diagnostic Tests(continued)Test NameTest NameI/O expander bustest1UnusedSAC linkcontroller/stationTest-IDTest-ID11DescriptionDescriptionBRC module p

49、erforms status read and verifies the IMDSO14(address 15) responds over I/O expander bus. IMDSO14 LEDscount successful tests.Test station link (IISAC01) communication between a BRC moduleacting as a controller and another BRC module acting as a station.Checks the ability to perform direct memory acce

50、ssed data trans-fers across the RS-485 station link at 40-kilobaud rate. Requirestwo BRC modules (redundant) and the appropriate PBA andredundancy cabling. The master BRC module will provide pass/failindication; the station BRC module will display data received andtransmitted.Tests communications be