IIoT controller
AE3100
5
2 Safety instructions
•
The unit described is a subcomponent for integration into a system.
– The system architect is responsible for the safety of the system.
– The system architect undertakes to perform a risk assessment and to create documentation in
accordance with legal and normative requirements to be provided to the operator and user of
the system. This documentation must contain all necessary information and safety instructions
for the operator, the user and, if applicable, for any service personnel authorised by the
architect of the system.
•
Read this document before setting up the product and keep it during the entire service life.
•
The product must be suitable for the corresponding applications and environmental conditions
without any restrictions.
•
Only use the product for its intended purpose (
Ò
Intended use).
•
If the operating instructions or the technical data are not adhered to, personal injury and/or damage
to property may occur.
•
The manufacturer assumes no liability or warranty for any consequences caused by tampering with
the product or incorrect use by the operator.
•
Installation, electrical connection, set-up, operation and maintenance of the product must be
carried out by qualified personnel authorised by the machine operator.
•
Protect units and cables against damage.
•
Replace damaged units, otherwise the technical data and safety will be impaired.
•
Observe applicable documents.
2.1 Safety symbol on the device
Safety symbol on the device:
u
Adhere to the operating instructions for the safe operation of the unit.
2.2 Cyber security
The device has the following security functions:
Design
•
Hardened Yocto-Linux distribution
Integrity
•
Convenient update of the complete system (recovery system)
•
Backup & restoring the system configuration
Authentication
•
User management via CODESYS Development System
•
Individual rights management for both the programming system and the runtime system via
CODESYS Development System
•
Authentication to external cloud
Confidentiality
•
Browser-based access to web visualisation via TLS-secured connection
•
Cloud communication only via TLS-secured connection
•
Identification of data sources in the cloud according to a readable name scheme
