In addition to the listed messages in the chapter Diagnostic messages, the message logger can display diagnostic messages of the runtime system in Logic Builder and Diagnostics.
These messages have a diagnostic code that deviates from the normal format:
A decimal greater than 1073741824 is displayed as diagnostic code.
The graphic shows the composition of the diagnostic code:
If the decimal diagnostic code of the message is converted into a hexadecimal, then the digit 4 displays in the first place that it is a runtime system message.
The following examples describe some possible runtime system messages:
Task cycle time monitoring:
Column message logger |
Value |
Description |
---|---|---|
Class |
4 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1073746179 |
Diagnostic code (HEX: 0x40001103) |
Ext. Diag |
16 |
External diagnostic: Indicates the time the task required (in ms). |
Message |
*EXCEPTION* Watchdog Application <Task name that caused the cycle time overrun> |
Exception occurred by the task cycle time monitoring: Example: *Exception* Watchdog Application TASK_S |
Application is not loaded:
Column message logger |
Value |
Description |
---|---|---|
Class |
3 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1073742337 |
Diagnostic code (HEX: 0x40000201) |
Ext. Diag |
1 |
External diagnostic |
Diagnostic text |
Application <Application name> not found to start |
The application could not be loaded. Example: Application Prepare not found to start |
Boot project is not loaded:
Column message logger |
Value |
Description |
---|---|---|
Class |
3 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1073742350 |
Diagnostic code (HEX: 0x4000020E) |
Ext. Diag |
16 |
External diagnostic |
Diagnostic text |
Boot project <Boot project name> corrupt |
The boot project could not be loaded. |
Exception FC_SysUserCallStack:
Column message logger |
Value |
Description |
---|---|---|
Class |
4 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1073746179 |
Diagnostic code (HEX: 0x40001103) |
Ext. Diag |
8192 |
External diagnostic: Number given |
Diagnostic text |
*EXCEPTION* <Exception type> Application |
Exception occurred by the function FC_SysUserCallStack. Example: *EXCEPTION* VendorException Application |
Fieldbus is not running:
Column message logger |
Value |
Description |
---|---|---|
Class |
3 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1079970304 |
Diagnostic code (HEX: 0x405F0A00) |
Ext. Diag |
-2146697191 |
External diagnostic |
Diagnostic text |
Could not get destination queue handle |
Diagnostic of the CAN driver: Fieldbus is not running |
Fieldbus configuration:
Column message logger |
Value |
Description |
---|---|---|
Class |
3 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1073746433 |
Diagnostic code (HEX: 0x 40001201 |
Ext. Diag |
1 |
External diagnostic |
Diagnostic text |
Update configuration failed from driver |
Message is related to fieldbus. Verify PLC configuration or replace the controller / optional card. Restart the controller. |
Fieldbus configuration:
Column message logger |
Value |
Description |
---|---|---|
Class |
3 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1074791425 |
Diagnostic code (HEX: 0x40100401) |
Ext. Diag |
1 |
External diagnostic |
Diagnostic text |
DriverMemoryPointer failed |
Message is related to fieldbus. Verify PLC configuration or replace the controller / optional card. Restart the controller. |
Column message logger |
Value |
Description |
---|---|---|
Class |
3 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1074791442 |
Diagnostic code (HEX: 0x40100412) |
Ext. Diag |
1 |
External diagnostic |
Diagnostic text |
TCP/IP service failed |
Message is related to fieldbus. Verify PLC configuration or replace the controller / optional card. Restart the controller. |
Fieldbus configuration:
Column message logger |
Value |
Description |
---|---|---|
Class |
3 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1074791448 |
Diagnostic code (HEX: 0x40100418) |
Ext. Diag |
1 |
External diagnostic |
Diagnostic text |
Firmwarename is not correct / Max. number of channels per board exceeded |
Message is related to fieldbus. Verify PLC configuration or replace the controller / optional card. Restart the controller. |
Loss of communication:
Column message logger |
Value |
Description |
---|---|---|
Class |
3 |
Diagnostic class 3 |
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1074791536 |
Diagnostic code (HEX: 0x40100470) |
Ext. Diag |
0 |
– |
Diagnostic text |
No cyclic telegrams |
The exchange of cyclical data was interrupted. |
Loss of fieldbus communication:
Column message logger |
Value |
Description |
---|---|---|
Class |
1 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1074791453 |
Diagnostic code (HEX: 0x4010041D) |
Ext. Diag |
1 |
(Internal diagnostic) |
Diagnostic text |
Hardware watchdog exceeded. Reset of application is necessary. |
– |
Loss of fieldbus communication:
Column message logger |
Value |
Description |
---|---|---|
Class |
1 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1074791491 |
Diagnostic code (HEX: 0x40100443) |
Ext. Diag |
1 |
(Internal diagnostic) |
Diagnostic text |
16#800C0019 |
Internal diagnostic code. Contact your Schneider Electric service representative. |
Loss of Ethernet communication:
Column message logger |
Value |
Description |
---|---|---|
Class |
1 |
|
Object |
LZS |
Runtime system |
Instance |
LZS |
Runtime system |
DiagCode |
1073754127 |
Diagnostic code (HEX: 0x4000300F) |
Ext. Diag |
1 |
(Internal diagnostic) |
Diagnostic text |
Failed to send data to <IP address> port. |
The Ethernet communication was interrupted. |