Device-Specific Parametrisation; Behaviour Of The Inputs And Outputs In Fail State Mode - Festo CTEU-DN Description, Functions And Maintenance

Universal bus node
Table of Contents

Advertisement

4. Commissioning

4.3.3 Device-specific parametrisation

4.3.4 Behaviour of the inputs and outputs in fail state mode

Festo P.BE-CTEU-DN-OP+MAINT-EN en 1206NH
The CTEU-DN bus node has device-specific parameters, re-
ferred to as parameter objects, e.g. for setting the behaviour
of the connected I-port devices or for activating certain status
signals. These parameters can be set in the configuration
program ("network configurator"
The type and scope of the parameter objects available in
CTEU-DN depends on the connected I-port device.
Use the QuickConnect and Automatic Device Replacement
(ADR) DeviceNet functions or communication and program-
ming via Explicit Messaging, in order to set the required para-
meters (
Section 4.3.1 and Tab. 4/15).
In this case, the controller (PLC) automatically transmits the
programmed parameters to the bus node after switch-on. The
settings will then be retained even after a restart or device
replacement.
To use explicit messaging programming, you need the object
descriptions and addresses of the DeviceNet object model
Appendix A.4.
In case of a control or communication interference, the net-
work participants, i.e. the bus nodes and the I-port devices,
assume fail state mode.
Possible causes of fail state mode:
Interference in the control system (PLC/scanner)
Network/fieldbus interruption (e.g. communication inter-
ference, broken cable)
Interference to data telegrams.
"Parameters").
4-15

Advertisement

Table of Contents
loading

Table of Contents