3 terminology used, Terminology used, 1about this documentation – Lenze E94AYAE SM301 User Manual
Page 7

Lenze · SM301 safety module · Parameter setting & configuration · DMS 2.3 EN · 11/2013 · TD05
7
1
About this documentation
1.3
Terminology used
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1.3
Terminology used
Term
Meaning
Engineering tools
Software solutions for easy engineering in all project stages
»EASY Navigator« – provides a good guide to the user
• All convenient Lenze engineering tools at a glance
• Tools can be selected quickly
• The clear structure simplifies the engineering process from the start
»Engineer« – multi-device engineering
• For all products in our L-force portfolio
• Practical user interface
• Graphic interfaces make it easy to navigate
• Can be applied in every phase of a project (project planning,
commissioning, production)
• Parameter setting and configuration
Code
"Container" for one or several parameters used for controller parameter setting or
monitoring.
Subcode
If a code contains several parameters, they are stored in "subcodes".
In the documentation, the slash "/" is used as a separator between the code and the subcode
(e.g. "C00118/3").
Function block
A function block (FB) can be compared with an integrated circuit that contains a specific
control logic and delivers one or several values when being executed.
• An instance (reproduction, copy) of the function block is always inserted in the circuit.
• It is also possible to insert several instances of a function block in a circuit.
• Each instance has an unequivocal identifier (the instance name) and a processing
number which defines the position at which the function block is calculated during the
task cycle.
System block
System blocks provide interfaces to basic functions and hardware of the controller in the
function block editor of the »Engineer« (e.g. to the digital inputs).
• System blocks cannot be instanced in contrast to function blocks.