Doc PS Rev Rb Parameters (1)
All standard modules willreceive all the data they require via parameters direct addressing of system areas from within the standard modules
willnot be permitted.
(2) Application modules are project specific and are used to structure and coordinate the control system software, such modules
shallnot generally use parameters and direct addressing of system areas from within
the application modules shallbe permitted.
(3) The use of parameters
willbe standardised, a common approach to the handling of parameters
willbe
established, such that all module parameters have a consistent and familiar mechanism for passing data.
(4) Where a standard module uses a system block that requires an instance data block (an example would be the system PID control block, this requires its own iDB), the instance data block address
willbe a parameter to the standard module, this will be passed internally by the standard module to the system block as a pointer or other indirect reference (i.e. the standard modules will not have any hardcoded instance data block references.
4.8.5 Global data (1)
Various global signals willbe required by the software modules that form the library this will include but not be limited to
• Global logic signals (true, false)
• Various timing pulses and square wave signals
• Cyclically dependent signals (first cycle c)
(2) The Controller CPUs are equipped with an internal function to generate accurate square waves ranging from 0.5 Hz to 10 Hz, this is referred to as the clock memory. The clock memory
maybe used as part of the global data generation.
62-71 Doc PS Rev Rb
Nomenclature (1) A comprehensive naming mechanism will be established to give a common approach to the naming of the following
• Module names
• Module parameters
• Local (temporary) data
•
Constants • IO symbols
• Tagging conventions
• Variable names within different types of UDT
• Variable
names within data blocks (2) The Style Guide (§ 4.6.5),
willcontain details of all naming conventions.
Share with your friends: