Phoenix Contact IBS ABB DSC-T Diagnostics Manual
Phoenix Contact IBS ABB DSC-T Diagnostics Manual

Phoenix Contact IBS ABB DSC-T Diagnostics Manual

Ibs sys diag dsc um e interbus g4
Table of Contents

Advertisement

Type:
Revision:
Order No.:
This guide is valid for :
IBS ABB DSC/SL/I-T Firmware ≥ 4.0
IBS PLC5 DSC/I-T
IBS S5 DSC/I-T
IBS BA DSC/I-T
© Phoenix Contact 09/1996
IBS SYS DIAG DSC UM E
A / C01
27 47 29 3
Firmware ≥ 4.0
Firmware ≥ 4.0
Firmware ≥ 4.0
INTERBUS
G4 Diagnostics Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the IBS ABB DSC-T and is the answer not in the manual?

Questions and answers

Summary of Contents for Phoenix Contact IBS ABB DSC-T

  • Page 1 Order No.: 27 47 29 3 This guide is valid for : IBS ABB DSC/SL/I-T Firmware ≥ 4.0 Firmware ≥ 4.0 IBS PLC5 DSC/I-T Firmware ≥ 4.0 IBS S5 DSC/I-T Firmware ≥ 4.0 IBS BA DSC/I-T © Phoenix Contact 09/1996...
  • Page 2 Menu (Mode) NORM MODE MONI DIAG STAT SCANTIME OPTITIME FW-V HW-V SER-No. RSET LCD TEST ERRHIST PF TEN CRC TEN DEBG ADBG QFLG WFLG SNGL LEVL SWTC BRDG ACTV CFG SAVE CFG 5241A000...
  • Page 3 Possible indications in Line 1: BOOT, RDY, ACTV, Page 8 NTER CTRL Page 44 LOOK FOR FAIL Page 9 RBUS Page 46 LBUS Page 48 OUT1 Page 52 OUT2 Page 60 Page 52 Page 64 Page 68 USER Page 72 EVNT Page 70 5241A030...
  • Page 4 Bus Structure and Device Counting Method Level 0 Level 1 Level 2 Level 3 7.1 7.2 7.3 6.1 6.2 6.3 4.0 4.1 4.2 10.0 5241A031 Figure 3: Example of a bus configuration 5277A...
  • Page 5 General Information Depending on their design, controller boards of Generation 4 have a keypad with 6 keys and an LCD for status and diag- nostics displays. The display is carried out via LEDs or sys- tem messages (by means of driver blocks). This guide describes the operation of the diagnostic display, the signal representation of LEDs, and system messages in- dicated via driver blocks.
  • Page 6: Table Of Contents

    Table of Contents General Information Keypad Diagnostics Display Structure of the Display System Startup BOOT READY ACTIVE Error Messages Controller Error Error Localization Remote Bus Error Local Bus Error OUT1 OUT2 General Bus Error Bus Errors E1 - E9 Device Error Peripheral Fault User Error EVENT Message...
  • Page 7 DEBG - Debug ADBG - Auto Debug QFLG - Quality Flag WFLG - Warning Flag SNGL - Single (Single Error) MPM Menu Item Submenus of MPM Diagnostics User Error Peripheral Fault Bus Error Controller Error DEBG Menu Item (Debug) ADBG Menu Item (Auto Debug) Help for Startup QFLG Menu Item (Quality Flag) WFLG Menu Item (Warning Flag)
  • Page 8 Remote Bus Error (RB) Local Bus Error (LB) Bus Error (BUS) OUT1 OUT2 Device Error (DEV) Peripheral Fault (PF) EVENT User Error (USER) Fuse Types for INTERBUS Devices Replacing INTERBUS Components Repairing Defective INTERBUS Components Technical Support We Are Interested in Your Opinion! Service Sheet for the Repair of Defective INTERBUS Components 5277A...
  • Page 9: General Information

    5277A...
  • Page 10: Keypad

    Keypad INTERBUS Diagnostics display Keypad Up Arrow Down Arrow Right Arrow, selection from menu items or addresses Left Arrow, selection from menu items or addresses ENTER, confirm selection ESCAPE, leave menu item, change to the next higher level 5241A003 Figure 4: Keypad The keypad allows menu-driven operation of the LCD via the arrow keys.
  • Page 11: Diagnostics Display

    Diagnostics Display INTERBUS Diagnostics display Keypad 5241A004 Figure 5: Diagnostics display The diagnostics display consists of: three main lines representing operating states, addresses and data. Here, for example, the messages are partly shown in clear text. 16 status segments on the left side of the display repre- senting input and output data in binary form.
  • Page 12: Structure Of The Display

    Structure of the Display 5241A005 Figure 6: Display segments and lines Line 1 Main line: Four alphanumeric positions for variable displays. FAIL Is always active if an error has occurred. In the first main line, the type of error is indicated during standard operation. CTRL: Controller error RBUS:...
  • Page 13 OUT1: Error at the outgoing interface OUT2: Error at the branching interface DEV: Error on a device USER: User error Peripheral fault MODE If the MODE menu item is active, further menu items can be selected from this point. Configuration DIAG Diagnostics STAT...
  • Page 14 Line 3 Main line Four alphanumeric positions for variable displays. VALUE The displayed number represents a value. CODE (see line 2) HIGH The displayed number is the higher-order word of a 32-bit value. The displayed number is the lower-order word of a 32-bit value.
  • Page 15 Three arrows pointing down If the higher-level control system is in the STOP state, an ar- row appears in the bottom line of the display pointing to the lettering on the front panel. This lettering is host-specific and indicates the state of the host system, e.g.: BASP (Siemens) Output inhibit SYSFAIL...
  • Page 16: System Startup

    System Startup During system startup, diagnostics is carried out as standard function. The system runs through the following phases: BOOT The system is currently in the boot phase and loads pre- stored data from the parameterization memory. READY The boot phase has been completed, the system is ready-to- run, all self-checking routines have been carried out and no error has been detected.
  • Page 17: Error Messages

    Error Messages Controller Error Die CTRL message indicates an error on the controller board. The display color changes to red. Controller errors have highest priority. The first line displays CTRL, the second an error code as hex value. When locating errors of first and second priority, the station name can be indicated via the ENTER key.
  • Page 18: Remote Bus Error

    On completion of the diagnostic routine, the error is indicated on the display. There are different displays: RBUS for remote bus errors (see Figure 9), LBUS for local bus errors (see Figure 10), BUS for general bus errors (see Figure 13), OUT1 for errors at the out- going interface, OUT2 for errors at the branching interface or DEV for errors on devices.
  • Page 19: Local Bus Error

    Local Bus Error If a local bus error is detected, data transmission on the bus is stopped. The outputs are reset in the LOOK FOR FAIL state. Display reading: Line 1 - Error type (LBUS). If the exact location within the segment cannot be located, the outgoing interface of the bus terminal module (BK module) belonging to that seg- ment is indicated (OUT2).
  • Page 20: Out1

    OUT1 Display reading: Line 1 - Error type (OUT1) Line 2 - Segment and location of the interface as of which the error occurs. Line 3 - Error code The background color changes to red. INTERBUS Segment 1 Segment 2 Segment 3 5241A029 Figure 11: Error at the outgoing bus interface...
  • Page 21: Out2

    OUT2 Display reading: Line 1 - Error type (OUT2) Line 2 - Segment and location of the bus terminal module as of which the error occurs. Line 3 - Error code The background color changes to red. INTERBUS Segment 1 Segment 2 Segment 3 5241A028...
  • Page 22: General Bus Error

    General Bus Error If the diagnostic routine cannot clearly define the error loca- tion, but is able to limit it to one area, data transmission on the bus is stopped. The outputs are reset in the LOOK FOR FAIL state. Display reading: Line 1 - Error type (BUS) Line 2 - Segment and location of the error area.
  • Page 23: Bus Errors E1 - E9

    Bus Errors E1 - E9 Generally, the display indicates the segment and location of the error in the case of a remote bus error. However, this does not include bus errors which begin with an E. For these errors, it was not possible to clearly define the er- ror location or area.
  • Page 24: Device Error

    Device Error This message, for example, is displayed if a wrong ID code has been selected. The error is directly assigned to a device. Transmission errors do not exist. Display reading: Line 1 - DEV (Device) Line 2 - Device number Line 3 - Error code The background color changes to red.
  • Page 25: Peripheral Fault

    Peripheral Fault The PF message indicates an error in the peripherals of an INTERBUS device. The first main line displays the error type (PF), the second line shows which device is affected. In the case of peripheral faults, the background light does not change to red.
  • Page 26: User Error

    User Error The user error signals an error in the area of the controller board. An example of this type of error is an overlapping of addresses in the input or output area of the PLC, causing more than one INTERBUS device to try and access the same address.
  • Page 27: Event Message

    EVENT Message The EVENT message has lowest priority. It indicates that an error has occurred which does not cause the system to be switched off and does not affect bus operation. INTERBUS 5277A014 Figure 18: EVENT message Display reading: FAIL does not appear above the first line. Line 1 - EVNT (Event) Line 2 - Error code Line 3 - Additional information depending on the error oc-...
  • Page 28: Extended Diagnostics

    Extended Diagnostics Selecting a Menu Item A menu system on the controller board allows to select differ- ent menu items. An overview is given on the inside cover page which can be unfold. The Left Arrow and Right Arrow keys allow to jump on the corresponding menu level.
  • Page 29: Cfg Menu Item

    The currently selected menu item is always displayed in the first line. If another level is available under this menu item, one of the respective menu items will flash in the second line. If no further submenus are available, the second line displays information specific to the currently selected menu item.
  • Page 30: Actv Cfg - Active Configuration

    ACTV CFG - Active Configuration NO CFG is displayed if no current configuration frame exists. Otherwise, the number of the current configuration frame will be displayed. MODE LEVL SWTC SAVE CFG BRDG ACTV CFG 5241A015 Figure 20: CFG menu item with submenus SAVE CFG - Saving the Configuration SAVE CFG serves to store the set address offset.
  • Page 31: Diag Menu Item

    After selecting this menu, the third line displays the number of bus devices in decimal representation. By pressing ENTER again, ADDR appears in the first line, a flashing "0" in the sec- ond line 2. The number of bus devices is shown in the third line.
  • Page 32: Adbg - Auto Debug

    ADBG - Auto Debug QFLG - Quality Flag WFLG - Warning Flag SNGL - Single (Single Error) NORM MODE MONI DIAG SNGL QFLG DEBG ADBG WFLG 5241A016 Figure 21: DIAG menu item with submenus MPM Menu Item In the case of an error, the MPM menu item provides further information.
  • Page 33 Submenus (MPM Diagnostics) NORM MONI MODE DIAG STAT DEBG ADBG QFLG WFLG SNGL PARA RELT INFO USER error Peripheral fault PARA "TN" "TN" PARA "TN" Bus error PARA VECT ADDR Controller error 5241A018...
  • Page 34: Submenus Of Mpm Diagnostics

    Submenu Items of MPM Diagnostics MPM is displayed in line 1, the corresponding error in line 2. If no error has occurred, NO ERR is displayed in lines 2 and 3. In the case of an error, the menu items of the additional diag- nostics can be moved through via the Left Arrow/Right Arrow keys.
  • Page 35: Controller Error

    Line 3 - Value in HEX format, binary representation via status segments at the same time. TN - Device number; if the error has not been located, the second line will be deleted. In the case of several errors, they are displayed one after the other. Line 3 - Error code in HEX format Controller Error Line 1 - CTRL...
  • Page 36 In the READY state, the second line flashes the physical bus location of the device (starting with 1). The Left Arrow/Right Arrow keys allow to change to the devices. If you keep the ar- row key pressed, the display starts to scroll in steps of one. After reaching a physical device number divisible by 10, the display scrolls in steps of ten.
  • Page 37: Adbg Menu Item (Auto Debug)

    length with which ID cycles are currently run. Line 3 displays the contents of the IPMS error register. If the state of the controller board changes during the time in which the DEBG menu item is active, cycles are stopped and NOT NOW is indicated, if required.
  • Page 38: Qflg Menu Item (Quality Flag)

    MODE DIAG DEBUG QFLG Stopping cycles Position CODE CODE Starting cycles Position 5241A019 Figure 24: DEBUG function QFLG Menu Item (Quality Flag) QFLG is displayed when exceeding a determined ratio of cy- cles with/without errors. Display reading: Line 1 - QFLG (Quality Flag) Line 3 - State of the quality bit in the diagnostic status reg- ister.
  • Page 39: Wflg Menu Item (Warning Flag)

    WFLG Menu Item (Warning Flag) This flag is activated if, within a set time, no error-free cycles could be transmitted. In this case, it is advisable to carry out more detailed bus diagnostics as the message gives a hint of a bundle error.
  • Page 40 MODE STAT CRC TEN PF TEN ERRHIST Number of errors SEC.POS SEG.POS SEC.POS 5241A020 Figure 25: STAT menu Every device has its own counters for reconfiguration, periph- eral and CRC errors. These menu items allow the error num- ber of every device to be displayed. The first line displays the selected menu item (REC, PF or CRC).
  • Page 41: Rec Menu Item

    REC Menu Item Display reading: Line 1 - REC Line 2 - Device number Line 3 - Error counter PF Menu Item (Peripheral Fault) Display reading: Line 1 - PF Line 2 - Device number Line 3 - Error counter CRC Menu Item Display reading: Line 1 - CRC...
  • Page 42: Crc Ten Menu Item

    The last device which has indicated an error is assigned to number 1 of the list. If there are more messages than ten, the oldest message will be removed. Press the arrow keys to se- lect a message and the ENTER key to obtain information on the peripheral fault: Line 2 - Device number Line 3 - Error code in HEX format.
  • Page 43: Errhist Menu Item

    ERRHIST Menu Item MODE STAT ERRHIST Status Diagnos. Parameter 5241A021 Figure 26: ERRHIST (error history protocol) Display reading: Line 1 - ERR Line 2 - HIST Line 3 - List number (1 - 10). The list numbers are acces- sible via the Left Arrow or Right Arrow keys. The most re- cent error is assigned to number 1.
  • Page 44: Opt Menu

    OPT Menu The OPT menu item (options) provides information which re- fers to all areas of the firmware but cannot be assigned to the diagnostics and configuration menus, e.g. reading the firm- ware version. The OPT menu comprises the following items: SCAN TIME - Update time in milliseconds [ms] OPTI TIME -...
  • Page 45: Scan Time Menu Item

    SCAN TIME Menu Item The interval between two data cycles (cycle time) is dis- played. The cycle time can either be set by yourself or determined au- tomatically by the controller board. The display is updated every five seconds. Display reading: Line 1 - SCAN Line 2 - TIME Line 3 - Indicates the update time in milliseconds.
  • Page 46: Ser-No. Menu Item

    SER-No. Menu Item Display reading: Line 1 - SER- Line 2 - No. Line 3 - (empty) When pressing the ENTER key, the serial number (12 posi- tions) is displayed over all three lines. RSET Menu Item (RESET) Display reading: Line 1 - RSET (Reset) When pressing the key combination Left Arrow, Down Arrow and ESCAPE for approximately three seconds, the controller...
  • Page 47: Siemens S5

    The following diagram illustrates the process image monitor ® of the IBS S5 DSC controller board for Siemens SIMATIC S5 PLCs. Siemens S5 Siemens S5 PLCs have four defined address areas: P-area for IN data - Address area 0x1000 - 0x10FF P-area for OUT data - Address area 0x0000 - 0x00FF Q-area for IN data - Address area 0x1100 - 0x11FF Q-area for OUT data - Address area 0x0100 - 0x01FF...
  • Page 48 Menu (Monitor) NORM MODE MONI P IN P OUT Q IN Q OUT X IN X OUT Y IN Y OUT 5241A001...
  • Page 49 To cause the display of data, select the desired address area, e.g. P IN or P OUT, and confirm with ENTER. The second line flashes the address. If you press the arrow key longer than 0.8 seconds, the dis- play starts to scroll: first, every 0.5 seconds in steps of two.
  • Page 50 5277A...
  • Page 51: Flowchart For Error Recovery

    Flowchart for Error Recovery Error occurs Error is indicated: - LC Display - Software function LCD displays: Error group, segment/position, code CTRL RB, LB, BUS, OUT1, OUT2, PF, DEV Firmware or hardware error Segment/Position and error code are displayed Checking the faulty bus segment Message: PF Message: RB Message: LB...
  • Page 52: Controller Error (Ctrl)

    Controller Error (CTRL) INTERBUS = Error location 7.1 7.2 7.3 6.1 6.2 6.3 4.0 4.1 4.2 5277A001 Figure 31: Controller error "" 5277A...
  • Page 53 Display Description Remedy 0Fxx System error on the controller board (hardware or firmware). Please contact Phoenix Contact. 1010 Firmware error on the controller board. Please contact Phoenix Contact. 1011 Hardware error on the controller board. Please contact Phoenix Contact. 1019 MPM manager error Please contact Phoenix Contact.
  • Page 54: Remote Bus Error (Rb)

    Remote Bus Error (RB) INTERBUS = Error location 7.1 7.2 7.3 6.1 6.2 6.3 4.0 4.1 4.2 5277A002 Figure 32: Remote bus error "$ 5277A...
  • Page 55 Display Description Remedy 0C10 An INTERBUS device is missing. Compare the bus topology with the current con- to 0C13 figuration. If they match, check the segment for: 0C14 Multiple error in the segment of the specified device due to trans- Shielding of bus cables or connectors, ground- to 0C17 mission errors.
  • Page 56: Local Bus Error (Lb)

    Local Bus Error (LB) INTERBUS = Error location 7.1 7.2 7.3 4.0 4.1 4.2 6.1 6.2 6.3 Example: INTERBUS Loop 6.0 6.1 6.2 6.3 5277A003 Figure 33: Local bus error "& 5277A...
  • Page 57 Display Description Remedy 0D10 An INTERBUS device is missing. Compare the bus topology with the current con- to 0D13 figuration. If they match, check the segment for: 0D14 Multiple error in the segment of the specified device due to trans- Shielding of bus cables or connectors, ground- to 0D17 mission errors.
  • Page 58 Display Description Remedy 0D2C Permanent error in the forward data path of the specified Loop de- Compare the bus topology with the current con- vice or error in the preceding Loop device. to 0D2F figuration. If they match, check the segment for: 0D30 Permanent error in the return data path from the last Loop device Bus cables, connectors or devices.
  • Page 59 5277A...
  • Page 60: Bus Error (Bus)

    Bus Error (BUS) Case 1 Case 2 INTERBUS INTERBUS 4.1 4.2 4.3 Case 1 7.1 7.2 7.3 Case 2 5277A012 Figure 34: Bus error 5277A...
  • Page 61 Display Description Remedy 0BF0 Data transmission was temporarily interrupted. The error can be found in: the preceding bus segment of a local bus. 0BF6 the preceding bus segment of a ST compact station. the bus segments of a preceding remote bus branch. the bus segment of the indicated INTERBUS device.
  • Page 62 Display Description Remedy 0BF4 Transmission error (CRC error) in the forward data path at the in- Compare the bus topology with the current con- coming bus interface (IN) of the specified device. figuration. If they match, check the segment for: 0BF5 Transmission error (CRC error) in the return data path at the incom- Shielding of bus cables or connectors, ground-...
  • Page 63 Display Description Remedy No interruption when reading in or activating the configuration. Check the system for: Shielding of bus cables or However, data cycles are not possible. Short interruption during the connectors, grounding/equipotential bonding, transmission of ID cycles due to installation errors or a defective de- voltage dips on the logic voltage supply of the re- vice (ID register).
  • Page 64: Out1

    OUT1 INTERBUS = Error location 7.1 7.2 7.3 6.1 6.2 6.3 4.0 4.1 4.2 10.0 5277A010 Figure 35: Error at the outgoing bus interface 5277A...
  • Page 65 Display Description Remedy 0C80 Multiple error at the outgoing bus interface (OUT1) of the specified Check the shielding of bus cables or connectors, INTERBUS device due to a defect taking place at the bus cable to 0C83 grounding/equipotential bonding, defective con- connected, a defective following device or a defective device of 0D80 nectors or soldered joints, voltage dips on the...
  • Page 66 Display Description Remedy 0C90 The specified device could not activate the following bus segment, a) Check the device. to 0C93 as the device carried out a voltage reset or is defective. b) Check the power supply of the device whether it conforms to the nominal value and whether the permissible AC voltage portion is exceeded (data sheet).
  • Page 67 5277A...
  • Page 68: Out2

    OUT2 INTERBUS = Error location 7.1 7.2 7.3 6.1 6.2 6.3 4.0 4.1 4.2 10.0 5277A009 Figure 36: Error at the branching bus interface 5277A...
  • Page 69 Display Description Remedy 0CC0 to Multiple error at the branching bus interface (OUT2) of the specified Check the local bus. 0CC3 device. An INTERBUS cable is connected without any further de- 0DC0 to vices, defective device in the local bus connected or failure of the 0DC3 communication voltage V 0CC4 to...
  • Page 70 Description Remedy 0CD0 After the branching bus interface (OUT2) of the specified device Please contact Phoenix Contact. to 0CD3 was opened (due to a firmware or hardware error) further devices 0DD0 in addition to a bus terminal module (BK) were included in the data to 0DD3 ring.
  • Page 71 5277A...
  • Page 72: Device Error (Dev)

    Device Error (DEV) INTERBUS = Error location 7.1 7.2 7.3 6.1 6.2 6.3 4.0 4.1 4.2 10.0 5277A007 Figure 37: Device error $" 5277A...
  • Page 73 0D48 frame. to 0D4B 0C4C The specified device has an invalid ID code. Please contact Phoenix Contact. to 0C4F 0D4C to 0D4F 0D50 The specified device has the ID code of a remote bus device, but is located in a local bus.
  • Page 74 Display Description Remedy 0C54 The slave chip of the specified INTERBUS device is a SUPI1 which Please contact Phoenix Contact. to 0C57 is operated in the µP mode. This mode is not supported by the firm- 0D54 ware. to 0D57 0C58 The data transmission was aborted at the outgoing remote bus interface (OUT1) of the specified device.
  • Page 75 0D70 Request (0711 ) service until the microproces- to 0D73 sor has initialized the SUPI. 0D74 The data transmission was aborted. An invalid mode is set on the Please contact Phoenix Contact. to 0D77 Loop chip of an Loop device.
  • Page 76: Peripheral Fault (Pf)

    Peripheral Fault (PF) INTERBUS = Error location 7.1 7.2 7.3 6.1 6.2 6.3 4.0 4.1 4.2 10.0 5277A006 Figure 38: Peripheral fault $& 5277A...
  • Page 77 The PF message indicates an error in the peripherals of an INTERBUS device. The first main line displays the error type (PF), the second main line the segment and position of the relevant device. In the case of peripheral faults, the background color of the display does not change to red, as data transmission on the bus is not affected.
  • Page 78: Event

    EVENT INTERBUS INTERBUS INTERBUS 5277A008 Figure 39: EVENT message 5277A...
  • Page 79 Display Description Remedy 0B8D A synchronous interrupt was illegally initiated. Initiate synchronous interrupts in the synchro- nous modes only. 0B8F Overflow of the IPMS input FIFO. A data area was accessed with a Only access data areas with a data width that is data width which is smaller than the data consistency defined for equal to the full data consistency defined for this this area.
  • Page 80: User Error (User)

    User Error (USER) INTERBUS = Error location 7.1 7.2 7.3 4.0 4.1 4.2 6.1 6.2 6.3 5277A004 Figure 40: User error 5277A...
  • Page 81 Wait for the completion of the service called be- fore, then try again. 0909 The confirmation which follows a service exceeds the maximum Please contact Phoenix Contact. permissible mailbox size. 090A The Parameter_Count parameter does not correspond to the number of subsequent words.
  • Page 82 Display Description Remedy 0912 The controller board cannot process the called service. The service Enable the service before calling it, or use a ser- is protected. It can only be enabled with a password. vice which is not protected. 0913 The controller board cannot process the called service, as it is not Use a service supported for this controller board.
  • Page 83 Display Description Remedy 092B An MPM accessor used a communication reference which had not been assigned to this accessor. 092E Not enough free memory space available on the controller board to initialize the Standard Signal Interface (SSGI). 0930 The controller board cannot process the Set_Value_Request (0750 ) service due to wrong parameters used when calling.
  • Page 84 Display Description Remedy Check the call of this service. 093A The controller board could not process the Set_Value_Request (0750 ) service as a wrong value was entered for the Variable_Count parameter. 093B The controller board could not process the service called last as the Check the call of the service called last.
  • Page 85 Display Description Remedy 0943 The controller board could not process the Clear_RAM_Card_ Check the call of this service. Request (0159 ) service, as a wrong value was entered for the Action_Flag parameter. 0944 The controller board could not process the Clear_RAM_Card_ Check the call of this service.
  • Page 86 Display Description Remedy 0951 The controller board cannot print the information, as the buffer of Wait a moment, then try again. the RS232 parameterization interface is full. 0952 A non-defined value was used for the Variable_ID parameter. Check the definitions of the event objects. 0953 The controller board could not process the service called last, as an Check the call of this service.
  • Page 87 Display Description Remedy 0A06 The controller board could not carry out the access. 0A07 The controller board could not carry out the access. The object does not exist. 0A08 The service called conflicts with another service. Wait for the processing of the service called first, then try again.
  • Page 88 Display Description Remedy 0A17 An unknown ID code was assigned. Check the parameters of the configuration frame. 0A18 An invalid bit was activated in the Used_Attributes parameter. Check the Used_Attributes parameter. The Nos. 0, 1, 3 and 4 are permitted. 0A19 When accessing the configuration frame, the end of the frame was Check the last access to the configuration...
  • Page 89 Display Description Remedy 0A21 Logical device number was assigned more than once. Check the logical INTERBUS device number in the configuration frame. 0A22 Inconsistent logical INTERBUS device numbers were assigned. Check the INTERBUS device numbers in the configuration frame. 0A23 Inconsistent device levels were specified.
  • Page 90 Display Description Remedy 0A2E The permissible number of internal indirect entries into address Reduce the number of devices occupying only lists was exceeded. one byte or one nibble of address space. 0A2F The controller board could not process the Initiate_Load_Con- Enter the correct number of devices.
  • Page 91 Display Description Remedy 0A40 Incorrect entry in the process data reference list. 0A41 Incorrect entry in the process data reference list. No OUT-PD was specified as target. 0A42 Incorrect entry in the process data reference list. No IN-PD was specified as source. 0A43 Incorrect entry in the process data reference list.
  • Page 92 Display Description Remedy 0A4A The controller board could not read out the process data reference Read out the process data reference list with the list. Read_PDRL_Request_0327 service. 0A4B Error when assigning a process data item. The bit string process Note that a bit string process data item does not data item exceeds the byte boundaries.
  • Page 93 Display Description Remedy 0A56 The configuration data transmitted to the controller board with the Check the lists of the transmitted configuration Compare_Configuration_Request (0317 ) service does not data and the specified configuration frame. match the configuration frame specified by the Frame_Reference parameter.
  • Page 94 The controller board did not accept the specified data consistency. Check the data assignments of the data consis- tencies. 0AFC Hardware error on the controller board. Please contact Phoenix Contact. 0AFD The contents of the address decoder EEPROM have changed. Carry out a power-up/reset of the PLC.
  • Page 95 Device_Function parameter. (0714 ) service. 0B84 The controller board cannot process the Control_Device_ Please contact Phoenix Contact. Function_Request (0714 ) service, as an error occurred in the list of physical device locations. 0B85 The configuration cannot be created.
  • Page 96 Display Description Remedy 0B88 The controller board cannot process the Control_Device_ Please contact Phoenix Contact. Function_Request (0714 ) service, as a firmware error occurred on the controller board. 0B8A The controller board changed to the stop state after a new or mod-...
  • Page 97 Display Description Remedy 0BD1 A data cycle exceeded the specified PD cycle time. The controller Check the system or increase the value set for board indicates this only, if it has been activated before with the the PD cycle time with the Set_Value_Request Set_Value_Request 0750 service.
  • Page 98: Fuse Types For Interbus Devices

    Phoenix Contact. The following table lists the fuses which are used in the modules. Fuses which are sol- dered in and can only be replaced at Phoenix Contact are list- ed as well. For some modules (printed in bold), the installed medium-blow fuses are to be replaced by the ones listed below after they have blown.
  • Page 99 Table 1: Overview of fuse types Order No. Designation Module Device Fuse Type Order No. SI. TR5 0,2AT 2753452 IBS TR5 0,2 AT 2721028 IB ST 24 BAI 8/I SI. TR5 0,4AT 2753478 IBS TR5 0,4 AT SI. TR5 0,2AT 2753452 IBS TR5 0,2 AT 2721015...
  • Page 100 Table 1: Overview of fuse types Order No. Designation Module Device Fuse Type Order No. 2767370 IBS TR5 0,5AT 2754668 IBS SP DIO SI. TR5 0,5AT 2787839 IBS PT 100A/2 SI. TR5 0,5AT 2767370 IBS TR5 0,5AT 2787842 IBS PT 100A/4 SI.
  • Page 101: Replacing Interbus Components

    Replacing INTERBUS Components Replacing the INTERBUS Controller Board When replacing the controller board, proceed as follows: 1. Note the system-related safety information. 2. Switch off the operating voltage of the host system (PLC, VME bus computer, PC). The bus system stops! 3.
  • Page 102 Replacing an INTERBUS Device When replacing a device, proceed as follows: 1. Put the system into a safe state. 2. Switch off the power supply of the corresponding bus seg- ment. 3. Unplug the bus cable from the device (does not apply to IB ST modules).
  • Page 103 Replacing INTERBUS IP20 devices Do not remove the cover from the devices! 1. Unplug the bus connector from the device. 2. Unplug the I/O connectors and PE connecting cable. 3. Unhook the device from the DIN rail. 4. Installation is done in reverse order. Replacing INTERBUS IP65 Devices The location of the mounting screws is described in the data sheet of the relevant device.
  • Page 104 LED green Voltage for the module logics Voltage within the valid range off: No voltage. Eliminate the cause, replace the fuse, if required (below the housing or in the case of IBS ST, fuses are pluggable from the outside). For the fuse type, refer to the data sheet or "Fuse Types for IBS De vices"...
  • Page 105 Diagnostics in Controller Boards Without LC Display If controller boards are not provided with an LC display, diag- nostics is carried out via LEDs. The following table shows the different LED states and the corresponding LC display reading: Table 2: Comparison of LED states and the LC display Name LED State LC Display...
  • Page 106: Repairing Defective Interbus Components

    Information on a Defective Device If you need to send in a defective INTERBUS component for repair to Phoenix Contact, copy the service sheet overleaf to a DIN A4 format and fill it out. Your complete information facilitates the service and allows us a quick processing.
  • Page 107: We Are Interested In Your Opinion

    No matter how small your contribution, we will deal with any hint or comment. Please send your comments, suggestions, etc. to the follow- ing address: Phoenix Contact GmbH & Co. Produktmarketing INTERBUS/ME-DOKU Flachsmarktstr. 8-28 32825 Blomberg Germany Alternatively, you may use the following FAX number: FAX No.: +49 - 52 35 - 34 12 00...
  • Page 108: Service Sheet For The Repair Of Defective Interbus Components

    Service Sheet for the Repair of Defective INTERBUS Components Contact name for Phoenix Contact Mr./Mrs./Ms. Company Department Address Postal code/ City/Country Phone General information on the system concerned Control system and CPU used What other boards are plugged? Type and serial number of the...
  • Page 109 Error description Since when does the error occur? How often does it occur? How does the error manifest itself? 5277A...
  • Page 110 5277A...
  • Page 111 Symbols µP mode Action_Flag Action_Index ACTV CFG ADBG Add_Error_Info ADDR Address_Direction BRDG Bus error Change_Exclusive_Rights_Request Clear_Ram_Card_Request CODE Compact_Load_PDRL_Request Compact_Read_PDRL_Request Compare_Configuration_Request Control_Active_Configuration_Request Control_Device_Function_Request Controller error CRC error CRC TEN CTRL DEBG Deactivate_Configuration_Request Device error Device_Level DIAG Diag_Length Diagnostic functions on INTERBUS devices Diagnostics in controller boards without LC display Entry_Count ERRHIST...
  • Page 112 Event Event_Index FAIL Flash EEPROM error Flowchart for error recovery Frame_Reference Fuse types FW-V Help for Startup HIGH Host adaption error HW-V I/O timeout Keypad LBUS LCD TEST LEVL Load_PDRL_Request Local bus error MAU error MODE MONI MPM manager error OPTI TIME OUT1 5, 52...
  • Page 113 PARA Parameter_Count PCP device PDD_Index PDDL PDRL_Index PDRL_Request_0327hex Peripheral fault PF TEN Power-on-selftest error Put_PDD_List_Request Put_Process_Data_ Description_List_Request QFLG RBUS Remote bus error Repair Replacement Reset_Controllerboard_Request RSET RS232 error SAVE CFG SCAN TIME SEG.POS. SER-No. Set_Value_Request Signal_Index SNGL STAT SWTC USER 5, 72 User error 18, 72...
  • Page 114 WAIT WFLG 5277A...
  • Page 115 Quick Diagnostics CTRL OUT1 From Page 44 From Page 46 From Page 48 From Page 52 From Page 56 OUT2 EVNT USER From Page 60 From Page 64 From Page 68 From Page 70 From Page 72 Figure 44: Quick diagnostics This table provides an overview of error messages which might occur when operating or starting up the system.
  • Page 116 Flowchart for Error Recovery Error occurs Error is indicated: - LC Display - Software function LCD displays: Error group, segment/position, code CTRL RB, LB, BUS, OUT1, OUT2, PF, DEV Firmware or hardware error Segment/Position and error code are displayed Checking the faulty bus segment Message: PF Message: RB Message: LB...
  • Page 117 Notes: 5277A...
  • Page 118 Phoenix Contact GmbH & Co. Postfach 13 41 32819 Blomberg Germany Telefon +49 - 52 35 - 3-00 Telefax +49 - 52 35 - 3-4 12 00 5277A...

Table of Contents