© Phoenix Contact 09/1996

Type:

Revision:

Order No.:

This guide is valid for :

INTERBUSG4 Diagnostics Guide

IBS SYS DIAG DSC UM E

A / C01

27 47 29 3

IBS ABB DSC/SL/I-T Firmware ≥ 4.0

IBS PLC5 DSC/I-T Firmware ≥ 4.0

IBS S5 DSC/I-T Firmware ≥ 4.0

IBS BA DSC/I-T Firmware ≥ 4.0

5277A

Figure 1: M

enu (Mode)

Menu (Mode)

5241A000LEVLLEN

MODE

CFG DIAG STAT OPT

ID

MPM DEBG QFLG WFLG

ERRHIST

SCANTIME FW-V

NORM MONI

SNGL

ACTV CFGBRDGSWTC

OPTITIME HW-V RSET LCD TEST

REC PF CRC PF TEN CRC TEN

ADBG

SAVE CFG

SER-No.

5277A

Possible indications in Line 1:

BOOT, RDY, ACTV,RUN Page 8

CTRL Page 44

LOOK FOR FAIL Page 9

RBUS Page 46

LBUS Page 48

OUT1 Page 52

OUT2 Page 60

BUS Page 52

DEV Page 64

PF Page 68

USER Page 72

EVNT Page 70

E1 - E9 Page 15

Figure 2: Possible indications on the LCD

INTERBUS

5241A030

5277A

Bus Structure and Device Counting Method

Figure 3: Example of a bus configuration

5241A031

1.0

2.0

3.0

4.0 4.1 4.2

5.0

6.07.0

8.0

9.0

10.0

7.1 7.2 7.3 6.1 6.2 6.3

Level 3Level 2Level 1Level 0

15277A

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.

The descriptions refer to the firmware version 4.x. Information on the firmware version is indicated in the text by the short-form "FW4.0".

When using this guide, please observe the following notes:

The front cover page shows an overview of the menu structure of the controller board.

The attention symbol refers to erroneous handling, which could lead to damage to the hardware or soft-ware or to personal injury. This symbol is always loca-ted to the left of the tagged text.

The hand symbol gives you tips and advice on the ef-ficient use of hardware and on software optimization. In addition, text marked in this way informs you of sy-stem-related conditions that must absolutely be ob-served to achieve error-free operation. The hand is also found in front of clarifications of terms.

The text symbol refers to detailed sources on informa-tion (manuals, data sheets, literature, etc.) on the sub-ject matter, product, etc. This text also provides helpful information for the orientation, reading order etc. in the manual.

i 5277A

Table of Contents

General Information 1

Keypad 2

Diagnostics Display 3

Structure of the Display 4

System Startup 8

BOOT 8

READY 8

ACTIVE 8

RUN 8

Error Messages 9

Controller Error 9

Error Localization 9

Remote Bus Error 10

Local Bus Error 11

OUT1 12

OUT2 13

General Bus Error 14

Bus Errors E1 - E9 15

Device Error 16

Peripheral Fault 17

User Error 18

EVENT Message 19

Extended Diagnostics 20

Selecting a Menu Item 20

Menu Structure 20

CFG Menu Item 21

ID - Identification Code of the Selected Device 21

LEN - Process Data Length of the Device 21

LEVL - Bus Level of the Selected Device 21

SWTC - List of Switched Off Devices 21

BRDG - List of Bridged Devices 21

ACTV CFG - Active Configuration 22

SAVE CFG - Saving the Configuration 22

DIAG Menu Item 23

MPM 23

ii5277A

DEBG - Debug 23

ADBG - Auto Debug 24

QFLG - Quality Flag 24

WFLG - Warning Flag 24

SNGL - Single (Single Error) 24

MPM Menu Item 24

Submenus of MPM Diagnostics 26

User Error 26

Peripheral Fault 26

Bus Error 26

Controller Error 27

DEBG Menu Item (Debug) 27

ADBG Menu Item (Auto Debug) 29

Help for Startup 29

QFLG Menu Item (Quality Flag) 30

WFLG Menu Item (Warning Flag) 31

SNGL Menu Item (Single Error) 31

STAT Menu 31

REC Menu Item 33

PF Menu Item (Peripheral Fault) 33

CRC Menu Item 33

PF TEN Menu Item 33

CRC TEN Menu Item 34

ERRHIST Menu Item 35

OPT Menu 36

SCAN TIME Menu Item 37

OPTI TIME Menu Item 37

FW-V Menu Item 37

HW-V Menu Item 37

SER-No. Menu Item 38

RSET Menu Item (RESET) 38

LCD TEST Menu Item 38

MONI Menu (Monitor) 38

Siemens S5 39

Flowchart for Error Recovery 43

Controller Error (CTRL) 44

iii 5277A

Remote Bus Error (RB) 46

Local Bus Error (LB) 48

Bus Error (BUS) 52

OUT1 56

OUT2 60

Device Error (DEV) 64

Peripheral Fault (PF) 68

EVENT 70

User Error (USER) 72

Fuse Types for INTERBUS Devices 90

Replacing INTERBUS Components 93

Repairing Defective INTERBUS Components 98

Technical Support 98

We Are Interested in Your Opinion! 99

Service Sheet for the Repair of DefectiveINTERBUS Components 100

iv5277A

2 5277A

Keypad

Figure 4: Keypad

The keypad allows menu-driven operation of the LCD via the arrow keys.

5241A003

INTERBUS

Diagnostics display

Keypad

Up Arrow

Down Arrow

Right Arrow, selection frommenu items or addresses

Left Arrow, selection frommenu items or addresses

ENTER, confirm selection

ESCAPE, leave menu item, change to the next higher level

35277A

Diagnostics Display

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.

- a green or red background color according to the operat-ing state of the bus.

5241A004

INTERBUS

Diagnostics display

Keypad

4 5277A

Structure of the Display

Figure 6: Display segments and lines

Line 1

Main line:Four alphanumeric positions for variable displays.

FAILIs 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: Remote bus error- LBUS: Local bus error- BUS: General bus error

5241A005

5

6

1

2

3

4

1

55277A

- OUT1: Error at the outgoing interface- OUT2: Error at the branching interface- DEV: Error on a device- USER: User error- PF: Peripheral fault

MODEIf the MODE menu item is active, further menu items can be selected from this point.

- CFG Configuration- DIAG Diagnostics- STAT Statistics- OPT Other display modes

MONIIndicates that the "monitor" mode is activated, e.g.S5 = host monitor for the S5 controller board.

HEXThe displayed value in the main line is a hex number. If the HEX segment is not activated, the value is represented as decimal number.

Line 2

Main line:Four and a half alphanumeric positions for variable displays.

PARAThe displayed value is the parameter of a message.

CODEThe displayed value represents a code.

SEG.POSThe displayed value is a device number (bus segment and lo-cation). You will find an example of the counting method on the inside cover page of this guide.

HEXThe displayed value in the second main line is a hex number. If the HEX segment is not activated, the value is represented as a decimal number.

2

6 5277A

Line 3

Main line Four alphanumeric positions for variable displays.

VALUEThe displayed number represents a value.

CODE(see line 2)

HIGHThe displayed number is the higher-order word of a 32-bitvalue.

LOWThe displayed number is the lower-order word of a 32-bitvalue.

%The displayed number is a percentage.

HEXThe displayed value in the third main line is a hex number. If the hex segment is not activated, the value is represented as a decimal number.

Status line

The bottom frame of the display is the status line which com-prises the following four elements:

RUNIf the controller board is in the READY or BOOT state, the el-ement is switched off. In the ACTIVE state, it is flashing, in the RUN state, it is permanently on.

FAILGoes on in the case of controller, user or bus errors.

BSA(Bus Segment Aborted) Goes on when a bus segment is dis-connected and disappears when all segments are connected again.

PF(Peripheral Fault) Goes on when an INTERBUS device indi-cates a fault in the peripherals.

4

3

75277A

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 inhibitSYSFAIL (VME bus) System failureNETFAIL (Ethernet) Network failureSTOP (Allen-Bradley) Control system in

programming modeLAB (Bosch) Stop state

16 Status segments

16 square status segments on the left side of the display pro-vide the basis for the binary representation of input and output words. Also, they are used for some other menu items.

6

5

8 5277A

System StartupDuring system startup, diagnostics is carried out as standard function. The system runs through the following phases:

BOOTThe system is currently in the boot phase and loads pre-stored data from the parameterization memory.

READYThe 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.

ACTIVEIndicates that a bus configuration has been loaded to the con-troller board and that this configuration is currently active. No data is transmitted over the bus yet. However, the bus is checked cyclically by identification cycles causing the BA-LEDs to flash on the INTERBUS devices. If an error occurs during the check, a corresponding indication is displayed. The RUN element is flashing.

RUNThe bus is running and refreshes the process image cyclical-ly. In the status line, i.e. in the lower frame, the RUN element is also active. The chasing chain displayed in the second line is further indi-cation that data cycles are running.

In all phases, the background color is green.

Figure 7: System startup

5241A006

95277A

Error MessagesController ErrorDie 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. However, to achieve this, the name must first be assigned to the bus seg-ment and location by means of software.

Error LocalizationIf an error occurs in the bus system (shown gray in the figure), a diagnostics routine is automatically started on the controller board. This diagnostics routine attempts to put the bus in op-eration one segment after the other in order to locate the er-ror.

While the error localization is being carried out, the display in-dicates the message LOOK FOR FAIL which is shown over the three main lines (see Figure 8).The background color changes to red.

Figure 8: Error localization message

5241A008

Segment 1

Segment 2

Segment 3

INTERBUS

10 5277A

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.

Remote Bus Error

If a remote bus error has been detected, data transmission on the bus is stopped. The outputs are reset in the LOOK FOR FAIL state.

Display reading:

- Line 1 - Error type (RBUS)- Line 2 - Error segment and location- Line 3 - Error code. In the status line, the FAIL element is

active, the RUN element is flashing.- The background color changes to red.

Figure 9: Remote bus error message

5241A009

Segment 1

Segment 2

Segment 3

INTERBUS

115277A

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).

- Line 2 - Segment and location of the faulty device, in the case of OUT2, the bus terminal module.

- Line 3 - Error code- In the status line, the FAIL element is active, the RUN el-

ement is flashing.- The background color changes to red.

Figure 10: Local bus error message

INTERBUS

Segment 1

Segment 2

Segment 3

5241A010

12 5277A

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.

Figure 11: Error at the outgoing bus interface

Segment 1

Segment 2

Segment 3

INTERBUS

5241A029

135277A

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.

Figure 12: Error at the branching bus interface

Segment 1

Segment 2

Segment 3

INTERBUS

5241A028

14 5277A

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.- In the status line, the FAIL element is active, the RUN el-

ement is flashing. - The background color changes to red.- Line 3 - Error code

Figure 13: General bus error message

INTERBUS

Segment 1

Segment 2

Segment 3

5241A011

155277A

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.

The bus errors are represented by the error codes E1 - E9. The codes E3 and E5 are reserved and not actively used.

In the case of bus errors of this kind, the bus stops and the outputs are reset in the LOOK FOR FAIL state. The following display can be read:

- Line 1 - Error type (BUS)- Line 2 - Relevant error type, e.g. E1- The background color changes to red.

Figure 14: Message of bus errors (E1 - E9)

E1

E2

E4

E6

No error was found when theconfiguration was acquired andcompared after the error occurred.- Power supply/shielding/grounding

The maximum permissible configu-ration was exceeded.

The configuration could not beacquired (- power supply -).

No error was found when the con-figuration was acquired and com- pared, but no data cycle is possible. - Power supply/shielding/grounding

E7

INTERBUS

The configuration could not beacquired during startup.

E8 The configuration could not be acquired during startup of diagnosticcycles. The additional diagnostic phase wasinterrrupted due to errors.

5241A012Change of configuration duringactive diagnostics.

E9

16 5277A

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.

Figure 15: Device error

INTERBUS

5241A025

Segment 1

Segment 2

Segment 3

175277A

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. This is based on the fact that data transmission is not affected. The message continues to be displayed even after the error has been eliminated and must be acknowl-edged separately via the application program.

The background color is green.

Figure 16: Peripheral fault message

The message "peripheral fault" corresponds to the message "module error" of Generation 3.

INTERBUS

5241A007

Segment 1

Segment 2

Segment 3

18 5277A

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. Further examples of user errors are for example the switching on and off of groups which have not previously been defined. This is a negative confirmation to a request sent before.

Display reading:

- Line 1 - Error type USER - Line 2 - An error code is represented as hex number.- Line 3 - An additional error information is shown as hex

number.- The background color is green.

Figure 17: Display of a user error

5241A013

Segment 1

Segment 2

Segment 3

INTERBUS

195277A

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.

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-

curred.- The background light is green.

5277A014

INTERBUS

20 5277A

Extended DiagnosticsSelecting a Menu ItemA 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. When reaching the end of a level, just press one key (Left Arrow or Right Arrow, de-pending on the direction) and you automatically return to the first or last menu item.

- After selecting a menu item, press the ENTER key to change to a lower level. The currently selected menu item is displayed in the first line. If another level is available un-der the menu item shown in line 2, this is indicated via flashing.

- Pressing the ESCAPE key always takes you back to the previous level.

- In the same way, it is possible to jump from one device number to another and vice versa within menu levels con-taining device lists.

Menu StructureThe uppermost level comprises the following menu items: Normal Display, MODE and MONI.

To reach the MODE menu item, press the Right Arrow key. Afterwards acknowledge immediately via the ENTER key that the display automatically resets after a few seconds, if no in-put is made.

Now, you have changed to the next level which provides ac-cess to the following submenus: CFG, DIAG, STAT and OPT:CFG Configuration DIAG DiagnosticsSTAT Statistics OPT Options

Figure 19: Main level of the menu

MODE

CFG

NORM MONI

5241A014 OPTDIAG STAT

215277A

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.

CFG Menu Item

The CFG menu item comprises the following subitems:

ID - Identification Code of the Selected Device

ID is displayed in line 1, the device number is flashing in line 2, and the ID code of the device is shown in line 3 (decimal representation).

LEN - Process Data Length of the Device

LEN is displayed in line 1, the device number is flashing in line 2, and the process data length of the device in bit is shown in line 3 (decimal representation).

LEVL - Bus Level of the Selected Device

LEVL is displayed in line 1, the device number is flashing in line 2, and the device level is shown in line 3 (decimal repre-sentation).

SWTC - List of Switched Off Devices

Here, a list of disconnected devices is displayed. According to the physical bus configuration, the device which was first dis-connected is assigned to the number 1 of the list. The list numbers can be selected via the Left Arrow/Right Arrow keys. The respective device number is displayed. Starting at list number 1, the number of switched off devices can be dis-played by pressing the Up Arrow key. The second line dis-plays CNT (Count), line 3 the number of switched off devices.NO CFG is displayed as long as there is no configuration. NO DEV appears if none of the devices is switched off.

BRDG - List of Bridged Devices

Display and operation correspond to the SWTC menu item.

22 5277A

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.

Figure 20: CFG menu item with submenus

SAVE CFG - Saving the Configuration- SAVE CFG serves to store the set address offset.- This menu item is available in the test mode only.- The bus must be in the RUN state, otherwise, the mes-

sage NOT NOW appears.

CFG

MODE

5241A015

ID code forIB ST 24 DI 16/4

ID code forIB ST 24 AO 4/SF

ID code forIBS ST 24 BK-T

ID

LEN LEVL

SWTC

BRDG

ACTV CFG

SAVE CFG

235277A

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. Now, the Left Arrow and Right Arrow keys allow to set an ad-dress offset. When pressing the ENTER key, a new boot se-quence is generated to which the newly set address offset is linked. If an error occurs, there will be a change to the NOR-MAL mode and a corresponding error message will be dis-played. If no error occurs, the third line indicates WAIT during the storage process and afterwards RDY (Ready).

You can select this menu as often as you like. The data stored previously is overwritten with every new selection.

DIAG Menu Item

The DIAG menu item provides diagnostic information on the current state of the bus. To simplify troubleshooting, the bus can be started up step-by-step, i.e. one device after the other.

DIAG comprises the following submenus:

MPM

If an error occurs, detailed information can be displayed with the MPM diagnostics. The first line indicates MPM, the sec-ond line the corresponding error type, e.g. USER or PF. NO ERR is displayed in line 2 and 3 if no error has occurred.

DEBG - Debug

This mode serves to start up the bus, device after device.

24 5277A

ADBG - Auto Debug

QFLG - Quality Flag

WFLG - Warning Flag

SNGL - Single (Single Error)

Figure 21: DIAG menu item with submenus

MPM Menu Item

In the case of an error, the MPM menu item provides further information.

Figure 22: MPM Diagnostics

DEBGMPM

MODE

CFG

NORM MONI

SNGL WFLGQFLG

DIAG

5241A016

ADBG

PARA BIT Device

5241A017

CFG

MODE

DIAG

MPM

25

5277A

Figure 23: S

ubmenu (M

PM

Diagnostics)

Submenus (MPM Diagnostics)

5241A018

MODE

CFG DIAG STAT OPT

PARA BIT MSG CNT

MPM DEBG ADBG

RELT INFO

NORM MONI

PCSRERR

PARA BIT "TN" "TN"

PARA BIT "TN"

PARA BIT ADDRVECT

USER error

Peripheral fault

Bus error

Controller error

QFLG WFLG SNGL

26 5277A

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. In this case, the MPM display disappears and the error type is displayed.

User Error- Line 1 - USER- Line 2 - (flashing) see overview on Page 25 - PARA - Diagnostic parameter register- Line 3 - Value in HEX format- BIT - Diagnostic status register- Line 3 - Value in HEX format, binary representation via

status segments at the same time- MSG - Message code of the negative confirmation- Line 3 - Code in HEX format, code segment switched on- CNT - ParaCounter (parameter counter)- Line 3 - Parameter counter in HEX format- RELT - Result (error code)- Line 3 - Code in HEX format, code segment switched on- INFO - Additional Info (additional error information)- Line 3 - Error information in HEX format

Peripheral Fault- Line 1 - PF- Line 2 - (flashing) see overview on Page 25 - PARA - Diagnostic parameter register- Line 3 - Value in HEX format- BIT - Diagnostic status register- Line 3 - Value in HEX format, binary representation via

status segments at the same time- TN - logical device number of the faulty device

Bus Error- Line 1 - RBUS, LBUS, BUS, OUT1, OUT2 or DEV- Line 2 - (flashing) see overview on Page 25 - PARA - Diagnostic parameter register- Line 3 - Value in HEX format- BIT - Diagnostic status register

275277A

- 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- Line 2 - (flashing) see overview on Page 25

PARA - Diagnostic status register- Line 3 - Value in HEX format- BIT - Diagnostic bit register- Line 3 - Value in HEX format, binary representation via

status segments at the same time- ERR - Error code- Line 3 - Value in HEX format- SR - Status register of the processor in the case of an er-

ror- Line 3 - Value in HEX format- PC - (Program Count) Program counter of the processor.

displaying the address of the controller error. - Line 3 - Value in HEX format- VECT - Vector number of the controller error which has

occurred- Line 3 - Value in HEX format- ADDR - Address which was accessed when the error oc-

curred. LOW and HI values are displayed alternately - (32-bit value).- Line 3 - Value in HEX format

DEBG Menu Item (Debug)

To simplify troubleshooting, The DEBG menu item allows to start up the bus one device after the other. For this, the con-troller board must be in the READY state. Every other state causes the message NOT NOW to be displayed in the sec-ond and third line indicating that the DEBUG function cannot be carried out in the currently selected state.

28 5277A

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. The bus is started up to the se-lected device. Local busses can only be started up complete-ly. If the startup has not been carried out successfully, an error code in HEX format is displayed in the third line, the physical number of the device on which the error occurred is shown in the second line. The second line displays a "0" if the error has been located on the controller board. In the second line, the CODE element is switched on. After a successful startup, the third line displays the ID code of the selected device in deci-mal format. In the third line, the CODE segment is switched on.

When reaching a bus terminal module or the last device of a local bus, ID and data cycles can be started by pressing the ENTER key. In this case, the double arrow element disap-pears. The double arrow is switched on if a device is selected within the local bus. This means that cycles cannot be started at the moment. If cycles have been started, ID and DATA al-ternate in the first line.The third line 3 displays alternately the number of faulty ID and data cycles. The cycles can be stopped by selecting an-other device (Left Arrow/Right Arrow).

When errors occur during the execution of cycles or the step-by-step startup, which also lead to bus errors during normal operation, the background color of the display changes from green to red. If this takes place during the startup, the second line displays the physical number of the device in which the error occurred and the third line shows the error code. Here, it is also possi-ble to start cycles via the ENTER key. If the error has occurred when running cycles, the ID cycles will continue to run. If no error has been detected up to now, the second line flashes the number of the device up to which it was possible to start up the system. The third line displays the contents of the IPMS error register. If an error has been detected but not located, the second line flashes the word

295277A

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.

There is one fundamental difference between this menu and other. The background color is independent of basic diagnos-tics, it depends on this menu only. As soon as a bus error occurs when starting up the bus device after device or running cycles, the background color changes from green to red. If the error has been eliminated, the back-ground color changes back to green. This menu can only be executed in the READY state. Thus, there are no conflicts with basic diagnostics.

ADBG Menu ITEM (Auto Debug)

Help for Startup

This menu item has the same function as DEBG except for the fact that functions are carried out automatically.

After selecting this menu item, the aim is to start up the bus. When carrying out the step-by-step startup without errors, data and ID cycles start after a waiting time of 1 second.

The diagnostic LEDs of the device allow to determine to what extent the bus is started up. If all BA-LEDs are active, the bus runs without errors.

As soon as a bus error occurs, it is attempted to restart the bus after a waiting time of 1 second. This is repeated as long as the step-by-step startup is carried out successfully.

Also, a new startup is attempted when the error counter is greater than 10. The display reading corresponds to that of the DEBG menu item.

30 5277A

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.Bit is set: ONBit is not set: OFF

5241A019

MODE

DIAG

DEBUG

Position

ID

Stopping cycles

Starting cycles

Position

ID

CODECODE

MPM QFLG

315277A

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.

Display reading:

- Line 1 - WFLG (warning flag)- Line 3 - State of the warning bit in the diagnostic status

register.Bit is set: ONBit is not set: OFF

SNGL Menu Item (Single Error)

Display reading:

- Line 1 - SNGL- Line 2 - Display of the errors which have occurred up to

now with regard to the current configuration frame as dec-imal number. Even if more than 9999 errors occur, 9999 will continue to flash.

- Line 3 - Contents of the IPMS error register

STAT Menu

The STAT menu provides statistic information on the bus state, e.g. device-oriented or total error counter. STAT comprises the following submenus:

ERRHIST Error protocol of the last ten errors

REC Reconfiguration error counter

PF Peripheral fault counter.

CRC CRC error counter.

PF TEN The chronological sequence of the last ten de-vices with peripheral faults (the last device on which a fault has occurred is assigned to number 1 of the list).

CRC TEN The ten devices with the most transmission er-rors (the device with the greatest number of errors is assigned to number 1 of the list).

32 5277A

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).The device number is indicated in the second line, the error counter in the third line. If you press the Up Arrow key, the bus structure will run up to the first device. When reaching the first device, the second line flashes CNC after repeated pressing of the Up Arrow key. The third line displays the total error counter of the entire bus. The Up Arrow key allows you to re-turn to the error counter of the selected device.

5241A020

MODE

STAT

SEC.POS

SEG.POS

SEC.POS

Number of errors

ERRHISTREC PF CRC TEN PF TENCRC

335277A

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- Line 2 - Device number- Line 3 - Error counter

In the menu items REC, PF and CRC, the devices represent-ed in the second line can be selected via the arrow keys. Right Arrow means the next device, Down Arrow the next bus segment, Up Arrow one segment back and Left Arrow one de-vice back.

PF TEN Menu Item

Display reading:

- Line 1 - PF- Line 2 - TEN- Line 3 - Shows a chronological list of the last ten devices

in which peripheral faults occurred.

The second and third line display NO CFG if no current con-figuration frame is available.

34 5277A

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. The corresponding

CODE element is displayed.

CRC TEN Menu Item

This menu allows the transmission quality of the bus to be evaluated rapidly.

Display reading:

- Line 1 - CRC- Line 2 - TEN- Line 3 - List number (1 - 10). The list numbers are acces-

sible via the Right Arrow or Left Arrow keys. The device characterized by the greatest number of transmission er-rors is assigned to number 1. If you keep pressing the EN-TER key at the selected entry number, the following display can be read:

Line 1 - Error counter is flashing. - Line 2 - Device number- Line 3 - Error code in HEX format. The corresponding

CODE element is displayed.

355277A

ERRHIST Menu Item

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. If you keep pressing the ENTER key at the selected input number, the third line displays the diagnostic parameter register as hex code. The status segments located on the left side of the display indicate the diagnostic status register. The uppermost sta-tus segment corresponds to the least significant bit, the lowest status segment to the most significant bit.

If no list entry exists, the third line flashes a "0".

5241A021

MODE

STAT

ERRHIST

PF

StatusDiagnos.

Parameter

36 5277A

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 - Optimum update time of the bus

FW-V - Firmware version

HW-V - Hardware version

SER-No.- Serial number

RSET.- Reset

LCD TEST

Figure 27: OPT menu (options)

375277A

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.

OPTI TIME Menu Item

Display reading:

- Line 1 - OPTI- Line 2 - TIME- Line 3 - Indicates the optimum update time for bus oper-

ation in milliseconds.

FW-V Menu Item

Display of the firmware version.

Display reading:

- Line 1 - FW-V- Line 2 - (empty)- Line 3 - Displays the firmware version, e.g. 4.0.

HW-V Menu Item

Display of the hardware version.

Display reading:

- Line 1 - HW-V- Line 2 - (empty)- Line 3 - Displays the hardware version.

38 5277A

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 board is reset (controller board is booting).

LCD TEST Menu Item

LCD TEST serves to check all display segments.

Display reading:

- Line 1 - LCD- Line 2 - TEST

When confirming with ENTER, all segments of the display are switched on.

MONI Menu (Monitor)

The MONI menu contains a process image monitor. This monitor is adapted to the addressing syntax of the con-trol and computer system and is therefore host-specific. Thus, the display reading varies depending on the controller board used (S5, ABB, VMEbus, etc.).

Activate RESET only in the STOP state of the application program as all outputs are set to zero.

395277A

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 - 0x10FFP-area for OUT data - Address area 0x0000 - 0x00FFQ-area for IN data - Address area 0x1100 - 0x11FFQ-area for OUT data - Address area 0x0100 - 0x01FF

In addition, there are four other address areas:X-area for IN data - Address area 0x1200 - 0x12FFX-area for OUT data - Address area 0x0200 - 0x02FFY-area for IN data - Address area 0x1300 - 0x13FFY-area for OUT data - Address area 0x0300 - 0x03FF

405277A

Figure 28: M

enu (Monitor)

Menu (Monitor )MODE MONI

P IN

S5

NORM

5241A001

P OUT Q IN Q OUT X IN X OUT Y IN Y OUT

415277A

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.- if you keep pressing key and the display reaches an ad-

dress divisible by ten, the display scrolls in steps of ten.

After selecting the area, the most recent address is flashing. The Left Arrow and Right Arrow keys allow to select the ad-dresses, the valid area ranges from 0 to 254.

The third line displays the contents of the address as hex number. The corresponding VALUE element is switched on.On the left side of the display, the value is represented in bi-nary form (see Figure 29).

Figure 29: Example of the display of process data

5241A024

INTERBUS

42 5277A

435277A

Flowchart for Error Recovery

Figure 30: Flowchart for error recovery

The diagnostic behavior of the controller board can be divided as follows:

1. Recognition of operating and faulty states;automatic diagnostics

2. Display of diagnostic data via the:- Front panel (error group and parameter via LCD)

3. Extended diagnostic functions via the driver software sup-plied or the RS232/V24 interface with the IBS CMD SWT G4 software tool.

Error occurs

5277A005

Error is indicated: - LC Display - Software function

LCD displays: Error group, segment/position, code

RB, LB, BUS, OUT1, OUT2, PF, DEVCTRL

Segment/Position and error code are displayedFirmware or hardware error

Checking the faulty bus segment

Message: RBError in remote bus cabling, supply of bus terminal modules(BK), ...

Message: LBError in localbus cablingI/O module

Message: BUSError location isnot clearly de-fined, an area is limited.

Message: OUT1Seg./Pos. of theinterface as ofwhich the erroroccurs.

Messge: OUT2Seg./Pos. of BK module as of which theerror occurs.

Message: DEVNo transmission error. Error is detec-ted in the device it-self and indicated inthe display of thecontroller board.

Maintain system

Delete error display: Via application program

Bus is in stop state. All outputs are reset!

Message: PFPeripheral fault

Attention:Bus continues to run

44 5277A

Controller Error (CTRL)

Figure 31: Controller error

5277A001

INTERBUS

= Error location

1.0

2.0

3.0

4.0 4.1 4.2

5.0

6.0

7.0

8.0

7.1 7.2 7.3

6.1 6.2 6.3

455277A 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.

1019to 101E

MPM manager errorError on the controller board when the MPM was accessed.

Please contact Phoenix Contact.

1020to 1025

Flash EEPROM error - Error on the controller board when theparameterization memory was accessed.

Please contact Phoenix Contact.

1030to 1036

Power-on-self-test error - Hardware error on the controller board during the self-test.

Please contact Phoenix Contact.

1051to 1055

RS232 error - Error on the controller board when the parameteriza-tion interface (RS232) was accessed.

Please contact Phoenix Contact.

1101 Host adaption error - Error on the controller board in the host-specific part of the firmware.

Please contact Phoenix Contact.

46 5277A

Remote Bus Error (RB)

Figure 32: Remote bus error

= Error location

1.02.0

3.0

4.0 4.1 4.2

5.0

6.0

7.0

8.0

7.1 7.2 7.3

6.1 6.2 6.3

5277A002

INTERBUS

475277A Display Description Remedy

0C10to 0C13

An INTERBUS device is missing. Compare the bus topology with the current con-figuration. If they match, check the segment for:

Shielding of bus cables or connectors, ground-ing/equipotential bonding, defective connectors or soldered joints, voltage dips on the communi-cation voltage supply of the remote bus device.

0C14to 0C17

Multiple error in the segment of the specified device due to trans-mission errors.

0C18to 0C1B

Multiple timeout in the segment of the specified INTERBUS device due to transmission errors.

0C1Cto 0C1F

Transmission error (CRC error) in the forward data path at the in-coming bus interface (IN) of the specified device.

0C20to 0C23

Interruption in the forward data path at the incoming bus interface (IN) of the specified device.

0C24to 0C27

Transmission error (CRC error) in the return data path at the incom-ing bus interface (IN) of the specified device.

0C28to 0C2B

Interruption in the return data path at the incoming bus interface (IN) of the specified INTERBUS device.

48 5277A

Local Bus Error (LB)

Figure 33: Local bus error

= Error location

1.02.0

3.0

4.0 4.1 4.2

5.0

6.0

7.0

8.0

7.1 7.2 7.3

6.1 6.2 6.3

5277A003

INTERBUS

3.0

4.0

4.1

4.2

5.0

6.0 6.1 6.2 6.3

4.3

Example: INTERBUS Loop

495277A Display Description Remedy

0D10to 0D13

An INTERBUS device is missing. Compare the bus topology with the current con-figuration. If they match, check the segment for:

Shielding of bus cables or connectors, ground-ing/equipotential bonding, defective connectors or soldered joints, voltage dips on the logic volt-age supply of the local bus device.

0D14to 0D17

Multiple error in the segment of the specified device due to trans-mission errors.

0D18to 0D1B

Multiple timeout in the segment of the specified device due to trans-mission errors.

0D1Cto 0D1F

Transmission error (CRC error) in the forward data path at the in-coming bus interface (IN) of the specified device.

0D20to 0D23

Interruption in the forward data path at the incoming bus interface (IN) of the specified device.

0D24to 0D27

Transmission error (CRC error) in the return data path at the incom-ing bus interface (IN) of the specified device.For Loop devices: Transmission path from the last Loop device to the bus terminal module (BK).

0D28to 0D2B

Interruption in the return data path at the incoming bus interface (IN) of the specified INTERBUS device.For Loop devices: Transmission path from the last Loop device to the bus terminal module (BK).

505277A

0D2Cto 0D2F

Permanent error in the forward data path of the specified Loop de-vice or error in the preceding Loop device.

Compare the bus topology with the current con-figuration. If they match, check the segment for:

Bus cables, connectors or devices.0D30to 0D33

Permanent error in the return data path from the last Loop device to the bus terminal module (BK) or in the specified device.

Display Description Remedy

515277A

52 5277A

Bus Error (BUS)

Figure 34: Bus error

INTERBUS

5277A012

1.02.0

3.0

4.0

5.0

4.1 4.2 4.31.0

2.0

3.0

7.0

8.0

7.1 7.2 7.3

Case 1 Case 2

Case 1

Case 2

INTERBUS

535277A Display Description Remedy

0BF0and0BF6

Data transmission was temporarily interrupted. The error can be found in:- the preceding bus segment of a local bus.- 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.

Cause: a) Voltage reset of a device in the specified area. b) The bridge (RBST or LBST) in the connector for the out-going bus is defective in the specified area.

0BF1 Data transmission is interrupted at a bus terminal module (BK). Cause: a) The connector for the branching remote bus branch has not been plugged in. b) Defective bridge (LBST) in the connector for the branching remote bus branch.

0BF2 Data transmission is interrupted at a bus terminal module (BK). Cause: a) The connector for the outgoing remote bus branch has not been plugged in. b) Defective bridge (RBST) in the connector for the outgoing remote bus .

0BF3 Data transmission is interrupted at a bus terminal module (BK), a local bus device or within an INTERBUS compact station. Local bus:- Cause: a) The connector for the outgoing local bus has not been plugged in. b) The bridge (RBST or LBST) in the

connector for the outgoing local bus is defective.ST compact station:

- Cause: a) The ST cable has not been plugged in. b) The RBST connection led via the next module of the IB ST compact station is interrupted.

545277A

0BF4 Transmission error (CRC error) in the forward data path at the in-coming bus interface (IN) of the specified device.

Compare the bus topology with the current con-figuration. If they match, check the segment for:

Shielding of bus cables or connectors, ground-ing/equipotential bonding, defective connectors or soldered joints, voltage dips on the communi-cation voltage supply of the remote bus device.

0BF5 Transmission error (CRC error) in the return data path at the incom-ing bus interface (IN) of the specified device.

E1 No configuration error, but short interruption during the transmis-sion of ID cycles due to installation errors or a defective device (ID register).

Check the system for: Shielding of bus cables or connectors, grounding/equipotential bonding, voltage dips on the logic voltage supply of remote bus devices.

E2 Further operation of the bus is not possible due to configuration changes. The maximum number of INTERBUS words or devices was exceeded.

E3 Reserved.

E4 The bus configuration could not be read in. The power supply of the electronics of one or serveral devices is interrupted.

Check the system for voltage dips in the power supply of remote bus devices.

E5 Reserved.

Display Description Remedy

555277A

E6 No interruption when reading in or activating the configuration. However, data cycles are not possible. Short interruption during the transmission of ID cycles due to installation errors or a defective de-vice (ID register).

Check the system for: Shielding of bus cables or connectors, grounding/equipotential bonding, voltage dips on the logic voltage supply of the re-mote bus device. Replace the device which has defective data registers.

E7 The configuration could not be activated by the controller board. The communication voltage supply of one or several devices is in-terrupted.

Check the system for voltage dips taking place during the supply of remote bus devices.

E8 During the quick startup, the additional diagnostic phase was interrupted after a fatal error.

E9 During the iterative diagnostics, the additional diagnostic phase was interrupted after a fatal error.

EA Fatal error. The Control_Device_Function_Request service cannot be executed.

Display Description Remedy

56 5277A

OUT1

Figure 35: Error at the outgoing bus interface

= Error location

3.0

4.0 4.1 4.2

5.0

6.0

7.0

8.0

9.0

10.0

7.1 7.2 7.3

6.1 6.2 6.3

5277A010

2.0

1.0

INTERBUS

575277A

Display Description Remedy

0C80to 0C830D80to 0D83

Multiple error at the outgoing bus interface (OUT1) of the specified INTERBUS device due to a defect taking place at the bus cable connected, a defective following device or a defective device of any subsequent local bus.

Check the shielding of bus cables or connectors, grounding/equipotential bonding, defective con-nectors or soldered joints, voltage dips on the logic voltage supply of the remote bus devices.

0C84to 0C870D84to 0D87

Multiple timeout at the outgoing bus interface due to a defect taking place at the bus cable connected, a defective fol-lowing device or a defective device of any subsequent local bus.

0C88to 0C8B0D88to 0D8B

Unexpected devices were found at the outgoing bus interface (OUT1) of the specified device, e.g. devices connected without an entry in the active configuration or INTERBUS cables connected without any further devices.

0C8Cto 0C8F0D8Cto 0D8F

Only ID cycles but no data cycles can be run. The data register of the outgoing remote bus interface (OUT1) of the specified device is interrupted or the number of data registers of the device that is connected to the outgoing remote bus interface (OUT1) of the specified device is not identical with the length code.

585277A

0C90to 0C93

The specified device could not activate the following bus segment, as the device carried out a voltage reset or is defective.

a) Check the device.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).c) Check the power supply unit of the bus termi-nal module (BK) for overload (data sheet).

0C94to 0C97

A device with the ID code of a local bus device was found at the outgoing remote bus interface of the specified device.

0C98to 0C9B0D98to 0D9B

The device connected to the outgoing remote bus interface (OUT1) of the specified device has an invalid ID code.

0D9Cto 0D9F

The local bus connected directly to the controller board consists of more devices than were entered in the active con-figuration.

Display Description Remedy

595277A

60 5277A

OUT2

Figure 36: Error at the branching bus interface

= Error location

1.0

2.0

3.0

4.0 4.1 4.2

5.0

6.0

7.0

8.0

9.0

10.0

7.1 7.2 7.3

6.1 6.2 6.3

5277A009

INTERBUS

615277A Display Description Remedy

0CC0 to 0CC30DC0 to 0DC3

Multiple error at the branching bus interface (OUT2) of the specified device. An INTERBUS cable is connected without any further de-vices, defective device in the local bus connected or failure of the communication voltage VL.

Check the local bus.

0CC4 to 0CC70DC4 to 0DC7

Multiple timeout at the branching bus interface (OUT2) of the spec-ified INTERBUS device due to a defective device, defective local bus cable or failure of the logic voltage VL.

0CC8 to 0CCB0DC8 to 0DCB

Other unexpected devices were found at the branching bus interface (OUT2) of the specified device. Device connect-ed without an entry in the active configuration or INTERBUS cable without connected devices.

0CCC to 0CCF0DCC to 0DCF

Only ID cycles but no data cycles can be run. Replace the device or adapt the length code in the configuration frame.

625277A

0CD0to 0CD30DD0to 0DD3

After the branching bus interface (OUT2) of the specified device was opened (due to a firmware or hardware error) further devices in addition to a bus terminal module (BK) were included in the data ring.

Please contact Phoenix Contact.

0CD4to 0CD70DD4to 0DD7

Error in the 8-wire local bus connected to the specified device due to a defective device in the local bus, defective local bus cable or failure of the logic voltage VL.

Check the local bus.

0CD8 to 0CDB0DD8 to 0DDB

The local bus connected to the specified bus terminal module (BK) consists of more local bus devices than were en-tered in the active configuration.

0CDC to 0CDF 0DDC to 0DDF

The device connected to the branching bus interface (OUT2) of the specified device has an invalid ID code.

Display Description Remedy

635277A

64 5277A

Device Error (DEV)

Figure 37: Device error

= Error location

1.0

2.0

3.0

4.0 4.1 4.2

5.0

6.0

7.0

8.0

9.0

10.0

7.1 7.2 7.3

6.1 6.2 6.3

5277A007

INTERBUS

655277A

Display Description Remedy0C40 to 0C430D40to 0D43

The length code of the specified device is not identical with the entry in the configuration frame.

0C44to 0C470D44to 0D47

The ID code of the specified device is not identicaI with the entry in the configuration frame.

0C48to 0C4B0D48to 0D4B

a) Data registers of the specified device were interrupted. b) The number of data registers of the specified device is not identical with the length code entered in the configuration frame.

0C4Cto 0C4F0D4Cto 0D4F

The specified device has an invalid ID code. Please contact Phoenix Contact.

0D50to 0D53

The specified device has the ID code of a remote bus device, but is located in a local bus.

665277A

0C54to 0C570D54to 0D57

The slave chip of the specified INTERBUS device is a SUPI1 which is operated in the µP mode. This mode is not supported by the firm-ware.

Please contact Phoenix Contact.

0C58to 0C5B0D58to 0D5B

The data transmission was aborted at the outgoing remote bus interface (OUT1) of the specified device.

0C5Cto 0C5F0D5Cto 0D5F

The data transmission was aborted at the branching bus interface (OUT2) of the specified device.

0C60to 0C630D60to 0D63

Transmission error at OUT1. The SUPI3 detected a CRC or MAU (Medium Attachment Unit) error.

Replace the INTERBUS device and contact Phoenix Contact.

Display Description Remedy

675277A

0C64to 0C670D64to 0D67

Transmission error at OUT2. The SUPI3 detected a CRC or MAU (Medium Attachment Unit) error.

0C68to 0C6B0D68to 0D6B

The SUPI3 of the specified device detected an I/O timeout.

0C6Cto 0C6F0D6Cto 0D6F

The specified device carried out a reset due to a defect or an insuf-ficient power supply.

Check the device. Check the power supply whether it conforms to the nominal value and the permissible AC voltage portion is exceeded (data sheet). Check the power supply unit of the bus terminal module (BK) for overload (data sheet).

0C70to 0C730D70to 0D73

The data transmission was aborted, as the INTERBUS device is defective or the SUPI initialization failed.

a) Replace the INTERBUS device.b) Delay the call of the Activate_Configuration_Request (0711hex) service until the microproces-sor has initialized the SUPI.

0D74to 0D77

The data transmission was aborted. An invalid mode is set on the Loop chip of an Loop device.

Please contact Phoenix Contact.

Display Description Remedy

68 5277A

Peripheral Fault (PF)

Figure 38: Peripheral fault

= Error location

1.0

2.0

3.0

4.0 4.1 4.2

5.0

6.0

7.0

8.0

9.0

10.0

7.1 7.2 7.3

6.1 6.2 6.3

5277A006

INTERBUS

695277A

The PF message indicates an error in the peripherals of anINTERBUS 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. The message remains on the display even after the error has been eliminated and must be acknowl-edged separately via the application program.

70 5277A

EVENT

Figure 39: EVENT message

5277A008

INTERBUS

INTERBUS

INTERBUS

715277A

Display Description Remedy0B8D 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

data width which is smaller than the data consistency defined for this area.

Only access data areas with a data width that is equal to the full data consistency defined for this area.

0BD2 The bus warning time has elapsed. No data cycle could be trans-mitted within the set bus warning time.

Check the system or increase the bus warning time with the Set_Value_Request service.

72 5277A

User Error (USER)

Figure 40: User error

5277A004

= Error location

1.0

2.0

3.0

4.0 4.1 4.2

5.0

6.0

7.0

8.0

7.1 7.2 7.3

6.1 6.2 6.3

INTERBUS

735277A

Display Description Remedy0903 Not enough free memory space on the controller board. Carry out a warm start with the Reset_

Controllerboard_Request (0956hex) service.

0904 Inconsistent parameters were entered. Check the parameters entered last for inconsis-tencies.

0905 Invalid parameters were entered. Check the parameters of the service called last.

0906 Access to this object is not supported. Check the last access.0907 Attempt to access an object that does not exist.

0908 The service called conflicts with another services called before. Wait for the completion of the service called be-fore, then try again.

0909 The confirmation which follows a service exceeds the maximum permissible mailbox size.

Please contact Phoenix Contact.

090A The Parameter_Count parameter does not correspond to the number of subsequent words.090B The controller board could not enable the specified service (wrong

password).Use the right password or a service which is not disabled.

0910 The service is disabled and cannot be called. Enable the service before calling, or use a ser-vice which is not disabled.

0911 The controller board cannot enable the specified service (as it has already been enabled).

Call the service.

745277A

0912 The controller board cannot process the called service. The service is protected. It can only be enabled with a password.

Enable the service before calling it, or use a ser-vice which is not protected.

0913 The controller board cannot process the called service, as it is not supported.

Use a service supported for this controller board.

0918 An unknown service code was called. The service code is not sup-ported for this controller board.

0919 The service exceeds the maximum permissible mailbox size. The service is longer than 1024 bytes.

Use only services which are no longer than 1024 bytes including all parameters. Call the service more than once to transmit the data set in multi-ple steps.

091A An unknown value was entered for the Action_Index parameter.

091B A value already used elsewhere was entered for the Action_Index parameter.

0920 A value already used elsewhere was entered for the Signal_Index parameter.

0925 An undefined value was entered for the Event_Index parameter.

0926 A value already used elsewhere was entered for the Event_Index parameter.

0928 The controller board cannot process the called service, as this ser-vice can only be used exclusively.

Change the assignment of the right with the Change_Exclusive_Rights_Request (0956hex) or use a non-exclusive service.

Display Description Remedy

755277A

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 (0750hex) service due to wrong parameters used when

calling.

0931 The controller board could not process the service called last. A non-defined value was used for the Variable_ID pa-rameter.

0932 The specified MPM device could not enable the exclusive rights.

0933 The request of the exlusive rights was rejected as a different MPM accessor still has these rights.

Use the Change_Exclusive_Rights_Request (014Fhex) service to enable the exclusive rights only when no other MPM accessor already has these rights.

0934 The request of exclusive rights was rejected. 0935 The permissible value range was exceeded when specifiying a

communication reference (CR).Assign only CRs within the range of: 2≤CR≤63. .

0938 A value which is reserved for the firmware was used for the Variable_ID parameter.

0939 A value which is not enabled was used for the Variable_ID parameter.

Display Description Remedy

765277A

093A The controller board could not process the Set_Value_Request (0750hex) service as a wrong value was entered for the Variable_Count parameter.

Check the call of this service.

093B The controller board could not process the service called last as the variable length encoded in the Variable_ID paramter is not identical with the length of the specified variable.

Check the call of the service called last.

093C The Signal_Handle object was defined incorrectly.

093D An invalid bit number was entered. 093E The maximum permissible number of Write parameters was exceeded.

093F Write parameter addresses were entered for a resident action.

0940 The controller board could not process the boot sequence without errors due to an error in the service call.

Check the call of the service given in the Add_Error_Info parameter.

0941 The controller board could not process the Clear_RAM_Card_Request(0159hex) service without errors, as a wrong address field was specified via the parameters Resi_Length and Diag_Length.

0942 The controller board could not process the Clear_RAM_Card_Request (0159hex) service, as a wrong value was entered for the Area_Flag parameter.

Check the call of this service.

Display Description Remedy

775277A

0943 The controller board could not process the Clear_RAM_Card_Request (0159hex) service, as a wrong value was entered for the Action_Flag parameter.

Check the call of this service.

0944 The controller board could not process the Clear_RAM_Card_Request (0159hex) service, as a non-defined service flag was spec-ified.

Check the call of this service.

0945 The controller board could not process the Clear_RAM_Card_Request (0159hex) service. The access to the parameterization memory was rejected, as the memory was not or not properly in-serted.

Check whether the parameterization memory was properly inserted.

0946 The access to the parameterization memory was rejected, as the parameterization memory is write-protected.

Disable the write protection and try again.

0947 Incorrect definition of an action object. Check the definitions of the action objects.

0948 Incorrect definition of a signal object. Check the definitions of the signal objects.

0949 Incorrect definition of an event object. Check the definitions of the event objects. 0950 The controller board cannot print the information, as the RS232 in-

terface is not in the print mode. Switch the RS232 interface into the print mode with Set_Value_Request (0750hex).

Display Description Remedy

785277A

0951 The controller board cannot print the information, as the buffer of the RS232 parameterization interface is full.

Wait a moment, then try again.

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

invalid parameter was specified.Check the call of this service.

0954 The controller board could not process the service called last, as a wrong value was specified for the Parameter_Count parameter.

Check the call of this service. The Parame-ter_Count parameter must correspond to the number of subsequent words.

0955 A message was not read out or sent, as the maximum permissible mailbox size was exceeded.

If the error code occurs after a request, the mes-sage can be read out in several steps.

0A02 The controller board could not process the service called last. A service was sent which was not permitted in the current state.

Set the controller board to the required state before calling the desired service.

0A03 Not enough free memory space on the controller board. Carry out a warm start of the controller board with the Reset_Controllerboard_Request (0956hex) service.

0A04 The controller board could not process the service called last. Check the call of this service.

0A05 The controller board could not process the service called last. In-valid parameter.

Check the call of this service.

Display Description Remedy

795277A

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.

0A10 The controller board could not process the Set_Value_Request (0750hex) service, as a wrong value was entered for the Variable_ID parameter.

0A11 The controller board could not process the Set_Value_Request (0750hex) service, as the permissible value range was exceeded when specifiying a parameter.

Check the parameters of this service.

0A12 The value range of the Device_Level parameter was exceeded. Check the Device_Level parameter. Values from 00hex to 0Fhex are permitted.

0A14 An invalid value was entered for the Error_Char_Flag parameter. Check the Error_Char_Flag parameter. Values from 0000hex to 0001hex are permitted.

0A15 An invalid value was entered for the Position parameter. Check the Position parameter. Values from 00hex to 3Fhex are permitted..

0A16 An invalid value was entered for the INTERBUS device number (segment/position).

Check the devices. For the segment, values from 01hex to FFhex are permitted, for the posi-tion, from 00hex to 3Fhex.

Display Description Remedy

805277A

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 exceeded.

Check the last access to the configuration frame.

0A1A The specified Frame_Reference does not exist or cannot be as-signed.

Check the Frame_Reference parameter.

0A1B The specified configuration frame could not be deleted, as it is cur-rently activated.

Deactivate the configuration frame with the Deactivate_Configuration_Request (0712hex) service before deleting.

0A1C The permissible number of specified or connected devices was exceeded.

0A1D The specified configuration frame could not be overwritten. A new Frame_Reference must be created.

Compare the existing configuration frame with the new data.

0A1E The next extension could not be assigned to the configuration frame.

Adapt the size of the new extension to the space provided.

0A1F The specified configuration frame could not be deactivated, as it is already inactive. 0A20 The physical first INTERBUS device in the data ring was not switched off, as the device cannot be switched off.

Display Description Remedy

815277A

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. Check the configuration frame.

0A25 The controller board did not accept the group definition. Different group numbers were assigned for devices of one bus segment.

Assign always the same group number to all devices of one bus segment.

0A26 The controller board did not accept the definition of an alternative group, as the assigned group number is invalid.

0A27 The controller board did not accept the definition of an alternative group, as the first device in the alternative group is not a bus terminal module (BK).

0A28 When attempting to activate alternative groups at the same time, the controller board could not activate the specified groups.

0A29 There was a conflict of mutual group dependencies when devices were switched on or off. 0A2A Conflict of devices due to inconsistent switching with the Control_Active_Configuration_Request (0713hex) service.

0A2C The specified INTERBUS device number does not exist.

0A2D Too many PCP devices are connected or more PCP devices are specified than permitted.

Reduce the number of connected or parameter-ized PCP devices (max. 63).

Display Description Remedy

825277A

0A2E The permissible number of internal indirect entries into address lists was exceeded.

Reduce the number of devices occupying only one byte or one nibble of address space.

0A2F The controller board could not process the Initiate_Load_Con-figuration_Request (0306hex) service, as a "0" was entered for the device number.

Enter the correct number of devices.

0A30 Incorrect entry in the process data description list (PDDL). Check the process data description list.

0A31 The controller board could not process the Put_PDD_List_Request (0321hex) service. The device number used does not exist.

0A32 The controller board could not process the Put_Process_Data_Description_List_Request (0321hex) service, as an invalid value was entered for the PDD_Index parameter.

Assign values in the range from 0000hex to 7FFFhex (with the exception of 6010hex and 6011hex) for this parameter.

0A33 Definition of process output data for a device, which has only input data or vice versa.

Define the data direction of the process data description with the Data_Direction parameter: 0Chex for IN-PDD, 0Dhex for OUT-PDD.

0A34 The internal address area of a device was exceeded when describing a process data item.

0A35 A data type and data length were specified that do not match when describing a process data item.

0A36 Error when defining a process data item. A bit string process data item exceeds the byte boundary.

Do not exceed the byte boundaries of the bit string process data item.

Display Description Remedy

835277A

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. The specified INTERBUS device number does not exist.

0A44 Incorrect entry in the process data reference list. A data consistency was entered for a process data item which does not match its length.

0A45 Incorrect entry in the process data reference list. A value which does not exist was entered for the PDD_Index parameter.

0A46 Addressing error. A wrong value was entered for the Compact_Load_PDRL_Request (0328hex) service or Load_PDRL_Request (0325hex) service for the Address_Direction parameter.

Enter 1000hex for an input address list, or 2000hex for an output address list.

0A47 Incorrect entry in the process data reference list. An incorrect or unknown value was specified for the PDRL_Index parameter.

0A48 Incorrect definition of a direct link in the PDRL. Check the definitions of direct links.

0A49 The controller board could not start up the bus configuration. A wrong device number was entered with the Entry_Count parame-ter for the Compact_Load_PDRL_Request (0328hex) service.

Compare the assignment of process data with the Compact_Read_PDRL_Request (0329hex) service.

Display Description Remedy

845277A

0A4A The controller board could not read out the process data reference list.

Read out the process data reference list with the Read_PDRL_Request_0327hex service.

0A4B Error when assigning a process data item. The bit string process data item exceeds the byte boundaries.

Note that a bit string process data item does not exceed the byte boundaries.

0A4C Error when assigning a process data item. An odd MPM address was assigned.

Assign only even MPM addresses to process data with a consistency of 16, 32 and 64 bits.

0A50 Error when assigning a process data item. The output address was assigned several times.

Assign only one process data item to an output address.

0A51 The controller board did not accept the Frame_Reference parame-ter.

The value "0" is not permitted for this parameter.

0A55 The configuration data transmitted to the controller board with the Compare_Configuration_Request (0317hex) service does not match the configuration frame specified by the Frame_Reference parameter. The device number (segment/position) specified by the Add_Error_Info parameter has been entered differently.

Check the lists of the transmitted configuration data and the specified configuration frame.

Display Description Remedy

855277A

0A56 The configuration data transmitted to the controller board with the Compare_Configuration_Request (0317hex) service does not match the configuration frame specified by the Frame_Reference parameter. The device code (length/ID code) specified by the Add_Error_Info parameter has been entered differently.

Check the lists of the transmitted configuration data and the specified configuration frame.

0A57 The configuration data transmitted to the controller board with the Compare_Configuration_Request (0317hex) service does not match the configuration frame specified by the Frame_Reference parameter. The device level specified by the Add_Error_Info parameter has been entered differently.

Check the lists of the transmitted configuration data and the specified configuration frame.

0A58 The configuration data transmitted to the controller board with the Compare_Configuration_Request (0317hex) service does not match the configuration frame specified by the Frame_Reference parameter. The group number specified by the Add_Error_Info parameter has been entered differently.

Check the lists of the transmitted configuration data and the specified configuration frame.

0A60 The controller board could not a assign a configuration frame. First create the configuration frame.

0A63 The diagnostic status register and the diagnostic parameter regis-ter are placed in the output address area.

Place these registers always in the input address area.

Display Description Remedy

865277A

0A64 Address conflict between a diagnostic register and a process input data item.

Place the diagnostic status register and the diagnostic parameter register in address area which are not assigned by process input data by using the Set_Value_Request (0710hex) service.

0A65 An odd MPM address was assigned to a 16-, 32- or 64-bit register (this is only allowed for 8-bit registers).

Assign only even addresses to 16-, 32- or 64-bit registers.

0A70 The controller board could not process the Get_Diag_Info_Request (032Bhex) service. The reserved attribute could not be enabled with the Diag_Info_Attr attribute.

0AFB 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.

0B00 to 0B03

Firmware error on the controller board. Please contact Phoenix Contact.

Display Description Remedy

875277A

0B80 The controller board cannot process the Set_Value_Request (0750hex) service, as an invalid value was entered for the Variable_ID parameter.

Use only the values specified in the description of the Set_Value_Request (0750hex) service.

0B81 The controller board cannot process the Set_Value_Request (0750hex) service, as the permissible value range was exceeded when entering a parameter.

0B83 The controller board cannot process the Control_Device_Function_Request (0714hex) service, as an invalid value was entered for the Device_Function parameter.

Use only the values specified in the description of the Control_Device_Function_Request (0714hex) service.

0B84 The controller board cannot process the Control_Device_Function_Request (0714hex) service, as an error occurred in the list of physical device locations.

Please contact Phoenix Contact.

0B85 The configuration cannot be created. Please contact Phoenix Contact.

0B86 The controller board cannot process the Control_Device_Function_Request (0714hex) service.

The INTERBUS device called does not have a command register.

0B87 The controller board cannot process the Control_Device_Function_Request (0714hex) service, as a number was entered for the Entry_Count parameter which is greater than the actual number.

Display Description Remedy

885277A

0B88 The controller board cannot process the Control_Device_Function_Request (0714hex) service, as a firmware error occurred on the controller board.

Please contact Phoenix Contact.

0B8A The controller board changed to the stop state after a new or mod-ified configuration was activated. The Alarm_Stop_Request (1303hex) service was sent too early.

Send the Alarm_Stop_Request (1303hex) ser-vice later.

0B8C The controller board could not activate the configuration frame. Reduce the number of decvices.

0BB1 The specified device indicates a peripheral fault. Check the devices. 0BB2 Reconfiguration request of the specified device. The reconfiguration button was pressed on the specified device.

0BB4 The microprocessor of the specified device carried out a reset.

0BB5 Impaired transmission quality in the forward data path of the incoming bus interface (IN) of the specified device. 0BB6 Impaired transmission quality in the return data path of the incoming bus interface (IN) of the specified device.

0BC2 Loop devices: The voltage is too low for initiators.

0BC3 Loop devices: The protocol chip is too hot. 0BC4 Loop devices: Internal power source is overloaded.

0BD0 The controller board could not start up the bus configuration. Connect the bus configuration.

Display Description Remedy

895277A

0BD1 A data cycle exceeded the specified PD cycle time. The controller board indicates this only, if it has been activated before with the Set_Value_Request 0750hex service.

Check the system or increase the value set for the PD cycle time with the Set_Value_Request service.

0BD2 The bus warning time has elapsed. No data cycle could be trans-mitted within the specified bus warning time.

Check the system or increase the bus warning time with the Set_Value_Request service.

0BD4 A single bus error occurred. The controller board indicates this only if this function has been activated before.

0BDE A synchronization error occurred in the "bus synchronous" mode. Check the system or increase the value set for the PD cycle time with the Set_Value_Request service.

0BDF A bus error occurred. The controller board has stopped the data transmission and is searching for the error location and cause.

Wait for the result of the troubleshooting.

Display Description Remedy

90 5277A

Fuse Types for INTERBUS Devices

All IBS devices with a 24V terminal are provided with TR5 fus-es. They protect the device on the bus side and, if devices with active inputs are used, on the input side. The TR5 fuses are available from 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.

Table 1: Overview of fuse types

Module Device Fuse Type Order No . DesignationOrder No.

IBS CT

2750497 IBS CT 24 DIO 24/16-LK SI. TR3 2AFSI. TR3 5AF

27226452721976

IBS TR3 2AFIBS TR3 5AF

2750507 IBS CT 24 DIO 24/16-T SI. TR3 2AFSI. TR3 5AF

27226452721976

IBS TR3 2AFIBS TR3 5AF

2722182 IBS CT 24 DIO 16/8-LK SI. TR3 2AFSI. TR3 5AF

27226452721976

IBS TR3 2AFIBS TR3 5AF

2722179 IBS CT 24 DIO 16/8-T SI. TR3 2AFSI. TR3 5AF

27226452721976

IBS TR3 2AFIBS TR3 5AF

IB ST2754309 IB ST 24 AI 4/SF SI. TR5 0,200AT 2753452 IBS TR5 0,2AT2754309 IB ST 24 AI 4/SF SI. TR5 0,400AT 2753478 IBS TR5 0,4AT2752534 IB ST 24 AI 4/SF-WT SI. TR5 0,400AT 2753478 IBS TR5 0,4AT2752521 IB ST 24 AO 4/BP SI. TR5 0,400AT 2753478 IBS TR5 0,4AT2754312 IB ST 24 AO 4/SF SI. TR5 0,400AT 2753478 IBS TR5 0,4AT2752440 IBS ST 24-BK- DIO-8/8/3-T-WT SI. TR5 1AT 2806600 IBS TR5 1AT2752440 IBS ST 24-BK- DIO-8/8/3-T-WT SI. TR5 5AT 2767383 IBS TR5 5AT2753232 IBS ST 24 BK LB-T SI. TR5 1AT 2806600 IBS TR5 1AT2752615 IBS ST 24 BK LB-T-WT SI. TR5 1AT 2806600 IBS TR5 1AT2754435 IBS ST 24 BK-LK SI. TR5 1AT 2806600 IBS TR5 1AT2753504 IBS ST 24 BK-RB-T SI. TR5 1AT 2806600 IBS TR5 1AT2752411 IBS ST 24 BK DIO 8/8/3-T SI. TR5 1AT 2806600 IBS TR5 1AT2751218 IBS ST 24 BK DIO 8/8/3-LK SI. TR5 1AT 2806600 IBS TR5 1AT2721662 IBS ST 24 BK RB-LK DIO

8/8/3-LKSI. TR5 1AT 2806600 IBS TR5 1AT

2754341 IBS ST 24 BK-T SI. TR5 1AT 2806600 IBS TR5 1AT2752437 IBS ST 24 BK-T-WT SI. TR5 1AT 2806600 IBS TR5 1AT2753012 IB ST 24 DI 32/2 SI. TR5 2AT 2752505 IBS TR5 2AT2752479 IB ST 24 DI 32/2-WT SI. TR5 2AT 2752505 IBS TR5 2AT2750808 IB ST 24 BDI 8/4 SI. TR5 0,4AT 2753478 IBS TR5 0,4 AT2750170 IB ST 24 BDI 16/4 SI. TR5 1AT 2806600 IBS TR5 1AT2721963 IB ST 24 BDI 32/4 SI. TR5 1AT 2806600 IBS TR5 1AT2753708 IB ST 24 DIO 8/8/3-2A SI. TR5 4 AT 2753465 IBS TR5 4AF2719166 IB ST 24 DIO 8/8/3-2A-WT SI. TR5 4AT 2750374 IBS TR5 4AT2753449 IB ST 24 DIO 8/8/3-2A-S SI. TR5 4AT 2753465 IBS TR5 4AF2751849 IB ST 24 DIO 8/8/R/3 SI. TR5 0,4AT 2753478 IBS TR5 0,4 AT2719629 IB ST 24 AI 4/I SI. TR5 0,4AT 2753478 IBS TR5 0,4 AT

2751564 IB ST 24 AI 4/BP SI. TR5 0,2AT 2753452 IBS TR5 0,2 ATSI. TR5 0,4 AT 2753478 IBS TR5 0,4 AT

2750565 IB ST 24 AI 4/SF4 SI. TR5 0,2AT 2753452 IBS TR5 0,2 AT