Diagnostics and troubleshooting
Leuze electronic
AMS 348
i
92
TNT
35/7-2
4
V
10
Diagnostics and troubleshooting
For the PROFINET, there are two different options for diagnosis.
Event-related diagnostics
PROFINET transmits events within an automation process as alarms that must be
acknowledged by the application process.
The following events are possible:
• Process alarms: Events that originate from the process and are reported to the control.
• Diagnostic alarms: Events that indicate the malfunctioning of an IO device.
• Maintenance alarms: Transmission of information to avoid the failure of a device
through preventative maintenance work.
• Manufacturer-specific diagnostics
To identify the alarms uniquely, they are always reported via a slot/subslot. The user can
prioritize diagnostic and process alarms differently.
State-related diagnostics
In addition, all alarms are entered into the diagnostics buffer. If required, this buffer can be
read by a primary instance via acyclic read services.
A further option to report malfunctioning or status changes in a field device to a plant control
is to enter low-priority diagnostic or status messages into the diagnostic buffer only instead
of actively reporting them to the primary control.
This option can also be used for preventative maintenance or for low-priority warnings, for
example.
The AMS 348
i
uses both the event-related diagnostics for high-prioritized events/errors as
well as the state-related diagnostics for preventative maintenance and the signaling of low-
prioritized events or warnings.
The following alarms and diagnostics messages are supported:
Table 10.1:
AMS 348
i
alarm and diagnostics messages
Diagnostics
Description
AMS 348
i
category
API/
Slot/
Subslot
Type
Coming/
going
Remark
Parameter error
Error in the configuration
of a module.
Error
0/n
1)
/0
1)
n = module number
Diagnostics
alarm
2)
2)
Only diagnostics or process alarms actually trigger the transmission of an alarm. All other
types (preventative maintenance and status messages) only lead to an entry into the
diagnostics buffer and are thus part of the state-based diagnostics.
Coming only
Configuration error
Error in the configuration
of a module.
Error
0/n/0
Diagnostics
alarm
Coming only