Table of Contents
Advertisement
Configuration Error/Config Error
An configuration error is indicated, when target and actual configuration of the con-
nected slaves do not match. The following cases may result in configuration errors:
Missing slave:A slave entered in the ⇒ LPS is not available
Erroneous type of slave:The ⇒ slave profile of the connected slave does not com-
ply with the configured one.
Unknown slave:A connected slave is not entered in the ⇒ LPS.
LAS - List of Activated Slaves
The master exchanges IO data with the slaves entered in the LAS. In the proteced
mode only those detected slaves (⇒ LDS) are activated which are expected by the
master and are entered in the ⇒ LPS. In the configuration mode all slaves entered
in the ⇒ LDS are activated.
LDS - List of Detected Slaves
All slaves from which the master was able to read the ⇒ slave profile are entered
in the LDS.
LPF - List of Peripheral Faults
There is a list of peripheral faults only for masters fulfilling the new specification
2.1. This list includes an entry for each slave that signals a ⇒ peripheral fault.
LPS - List of Projected Slaves
The list of projected slaves includes all slaves expected by the master. All entries
of the ⇒ LDS are taken over to the LPS by storing the actual configuration (except
for a not addressed slave with the address 0).
Offline phase
In the offline phase all input and output data is reset. This phase is entered at start-
up of the master, after a ⇒ AS-i power fail, and at the transition of the ⇒ configu-
ration mode to the ⇒ protected mode.
Furthermore the master can actively be put into the offline phase with the offline
flag.
During the offline phase, masters with a display show code "40".
Subject to reasonable modifications due to technical advances.
Pepperl+Fuchs Group · Tel.: Germany (6 21) 7 76-0 · USA (3 30) 4 25 35 55 · Singapore 7 79 90 91 · Internet http://www.pepperl-fuchs.com
AS-i/PROFIBUS-Gateway
Glossary: AS-i Terms
Copyright Pepperl+Fuchs, Printed in Germany
173
Advertisement
Table of Contents
