Phoenix Contact 27 41 40 6, User Manual

Page: 27 / 80

onlinecomponents.com
Advanced Diagnostics for AS-i Masters
6170
B
21
6 Advanced Diagnostics for AS-i Masters
The advanced AS-i diagnostics serve to locate occasionally occurring errors and
to judge the quality of data transmission on AS-i without additional diagnostics
tools.
The "AS-i Control Tools" (software for the comfortable commissioning of the AS-
Interface and the programming of AS-i Control) support the operation of the ad-
vanced diagnostics (LCS, error counters and LOS).
6.1 List of Corrupted AS-i Slaves ( LCS )
To locate occasionally occurring short-time configuration errors the AS-i masters
with advanced diagnostics manage beside the list of projected slaves (
LPS ), the
list of detected slaves ( LDS ) and the list of activated slaves ( LAS ) a forth list, the
list of corrupted slaves ( LCS ) . This list contains entries of all AS-i slaves which
were responsible for at least one configuration error since powering up the AS-i
master or reading the list. Short-time AS-i power failures are represented in the
LCS at the position of AS-i slave with address 0.
6.2 Protocol Analysis: Counters of Corrupted Data Telegrams
The AS-i master with advanced diagnostics has a counter of telegram repetitions
for each AS-i slave, which is increased everytime there is a corrupted data tele-
gram. This makes possible to judge the quality of the AS-i network, even if only a
few corrupted telegrams occured and the AS-i slave did not cause any configura-
tion errors.
With every read access the LCS will be deleted.
The last short-time configuration error can also be displayed on the
AS-i Master:
Pressing the “SET” button of the AS-i master shows the AS-i slave
which was responsible for the last short-time configuration error. If
there was a short-time AS-i power failure the display shows “39”
after pressing the “SET” button.
This function is only available if device is in the normal operation
mode of the protected mode (display empty) or in the off-line-phase.
The counter values can be read via the host interface and will be
deleted with every read access. The counter value is limited to 254.
255 means counter overflow.