interbus - Onlinecomponents.com
interbus - Onlinecomponents.com interbus - Onlinecomponents.com
0B83 Code Type Description and Remedy 0B83 USER The controller board cannot process the "Control_Device_Function" service (0714 hex ). You specified an invalid value for the Device_Function parameter. Remedy: Only use the values specified in the description of the "Control_Device_Function" service (0714 hex ). 0B84 USER The controller board cannot process the "Control_Device_Function" service (0714 hex ). An error was detected in the list of physical device positions. Remedy: Check the list of physical device positions. 0B85 USER The configuration cannot be created. An error was detected in the active configuration. Remedy: Check the list of the active configuration. 0B86 USER The controller board could not process the "Control_Device_Function" service (0714 hex ). The called device has no command register. 0B87 USER The controller board cannot process the "Control_Device_Function" service (0714 hex ). You specified a number for the Entry_Count parameter, which is greater than the actual number of devices. 0B88 USER The controller board cannot process the "Control_Device_Function" service (0714 hex ). A firmware error occurred on the controller board. Remedy: Replace the controller board. 0B8A USER After activating a new or modified configuration, the controller board changed to the stop state. You sent the "Alarm_Stop" service (1303 hex ) too early. Remedy: Send the "Alarm_Stop" service (1303 hex ) later. onlinecomponents.com 76 5277CC01
0B90 Code Type Description and Remedy 0B8C USER The controller board could not activate the configuration frame (“ page 116). You exceeded the maximum permissible number of I/O bits. Remedy: Reduce the number of devices. Depending on the type of controller board, you may use up to 8192 I/O points. To obtain the exact number, refer to the documentation for your controller board. 0B8D EVNT 0B8E EVNT 0B8F EVNT The control or computer system illegally initiated a synchronous interrupt. Remedy: Only initiate synchronous interrupts when the bus is running or in synchronous modes. You initiated a synchronous interrupt in the MPM (“ page 116), although the controller board was in asynchronous mode or the bus was not started. Remedy: Only initiate synchronous interrupts when the bus is running or in synchronous modes. This error may occur if the bus was installed incorrectly and the transmission quality is poor as a result. In addition, this message indicates a data inconsistency. Remedy: Check transmission paths or only access data areas with a data width that is equal to the full data consistency defined for this data area. The INTERBUS configuration enables you to specify the data consistency in addition to the address of a device. The data consistency ensures that the process data is coherently available. Word-oriented access is set by default. If other consistency area are needed, you can define areas of 8, 16, 32, and 64 bits by entering the consistency after the PLC address for the process data definition, e.g., P12:32 for doubleword access or P12:8 for byte-oriented access. onlinecomponents.com 0B90 USER The last INTERBUS cycle was aborted. A hardware fault has occurred on the controller board. Remedy: Replace the controller board. 5277CC01 77
- Page 27 and 28: MODE - DIAG 3.2 Unsuccessful Start
- Page 29 and 30: MODE - STAT STAT Menu (Statistics)
- Page 31 and 32: MODE - STAT CRC Menu Item (Transmis
- Page 33 and 34: MODE - OPT RSET Menu Item (Reset) O
- Page 35 and 36: Error Localization If a bus error o
- Page 37 and 38: Remote Bus Error (RBUS) , E= C I
- Page 39 and 40: When detecting a local bus error, d
- Page 41 and 42: transmission paths between these de
- Page 43 and 44: OUT 2 Interface Error , E= C I JE
- Page 45 and 46: Local Bus Error in an Inline Statio
- Page 47 and 48: Device Error (DEV) , E= C I JE? I
- Page 49 and 50: EVENT Message (EVNT) , E= C I JE?
- Page 51 and 52: Error Codes 0BE4 Code Type Descript
- Page 53 and 54: 0913 Code Type Description and Reme
- Page 55 and 56: 092A Code Type Description and Reme
- Page 57 and 58: 093B Code Type Description and Reme
- Page 59 and 60: 0953 Code Type Description and Reme
- Page 61 and 62: 09DB Code Type Description and Reme
- Page 63 and 64: 0A05 Code Type Description and Reme
- Page 65 and 66: 0A1B Code Type Description and Reme
- Page 67 and 68: 0A28 Code Type Description and Reme
- Page 69 and 70: 0A35 Code Type Description and Reme
- Page 71 and 72: 0A4A Code Type Description and Reme
- Page 73 and 74: 0A55 Code Type Description and Reme
- Page 75 and 76: 0A64 Code Type Description and Reme
- Page 77: 0B81 Code Type Description and Reme
- Page 81 and 82: 0BC2 Code Type Description and Reme
- Page 83 and 84: 0BE0 Code Type Description and Reme
- Page 85 and 86: 0C13 Code Type Description and Reme
- Page 87 and 88: 0C4F Code Type Description and Reme
- Page 89 and 90: 0C79 Code Type Description and Reme
- Page 91 and 92: 0C8F Code Type Description and Reme
- Page 93 and 94: 0CCF Code Type Description and Reme
- Page 95 and 96: 0D27 Code Type Description and Reme
- Page 97 and 98: 0D5F Code Type Description and Reme
- Page 99 and 100: 0D9B Code Type Description and Reme
- Page 101 and 102: 1011 Code Type Description and Reme
- Page 103 and 104: 1217 Code Type Description and Reme
- Page 105 and 106: 2010 Code Type Description and Reme
- Page 107 and 108: 202E Code Type Description and Reme
- Page 109 and 110: 8040 Code Type Description and Reme
- Page 111 and 112: 8400 Code Type Description and Reme
- Page 113 and 114: Table 3 Overview of fuse types (Con
- Page 115 and 116: Replacing the INTERBUS Controller B
- Page 117 and 118: E Red LED ON OFF Error message Erro
- Page 119 and 120: Services Offered by Phoenix Contact
- Page 121 and 122: Error Description When did the erro
- Page 123 and 124: Flowchart for Error Removal - HH H
- Page 125 and 126: Phoenix Contact GmbH & Co. KG Flach
0B83<br />
Code Type Description and Remedy<br />
0B83 USER The controller board cannot process the<br />
"Control_Device_Function" service (0714 hex ).<br />
You specified an invalid value for the<br />
Device_Function parameter.<br />
Remedy: Only use the values specified in the<br />
description of the "Control_Device_Function"<br />
service (0714 hex ).<br />
0B84 USER The controller board cannot process the<br />
"Control_Device_Function" service (0714 hex ). An<br />
error was detected in the list of physical device<br />
positions.<br />
Remedy: Check the list of physical device<br />
positions.<br />
0B85 USER The configuration cannot be created. An error<br />
was detected in the active configuration.<br />
Remedy: Check the list of the active<br />
configuration.<br />
0B86 USER The controller board could not process the<br />
"Control_Device_Function" service (0714 hex ).<br />
The called device has no <strong>com</strong>mand register.<br />
0B87 USER The controller board cannot process the<br />
"Control_Device_Function" service (0714 hex ).<br />
You specified a number for the Entry_Count<br />
parameter, which is greater than the actual<br />
number of devices.<br />
0B88 USER The controller board cannot process the<br />
"Control_Device_Function" service (0714 hex ). A<br />
firmware error occurred on the controller board.<br />
Remedy: Replace the controller board.<br />
0B8A USER After activating a new or modified configuration,<br />
the controller board changed to the stop state.<br />
You sent the "Alarm_Stop" service (1303 hex ) too<br />
early.<br />
Remedy: Send the "Alarm_Stop" service<br />
(1303 hex ) later.<br />
online<strong>com</strong>ponents.<strong>com</strong><br />
76 5277CC01
Change language