API of the unified implementation of the DAQ-templates

24.02.2019 16:17 Age: 5 yrs Category:

---

API of the unified implementation of the DAQ-templates has been implemented, applied and substantially tested.

Currently, this API is applied on the primary modules of the subsystem "Data acquisition", that is LogicLev, ModBus, Siemens, and as an optional feature for the controller object of the JavaLikeCalc module. From modules of other subsystems to the templates support, the protocol modules UserProtocol, ModBus and the graphical interface module WebUser have been adapted. Moreover, the use of templates in the modules UserProtocol and WebUser conceptually improved their functions and expanded the ability to create complex templates.

Implementation of the DAQ-templates, which themselves are described at the level of the "Data Acquisition" subsystem, before the appearance of this API were implemented independently in each module they used, and only in modules of the "Data Acquisition" subsystem: LogicLev, ModBus, Siemens. This made it impossible or complicated to unify the rules for linking to external sources and to exclude links to OpenSCADA data sources in modules with specific links, such as ModBus and Siemens.

Accordingly, the main purpose of implementing this API was unification, which allows you to quickly allocate the data acquisition modules by logical level function — creation of logical level parameters, and also use such templates in other subsystems, especially the subsystem "Transport protocols". An important feature is the ability to install links to OpenSCADA data sources even in implementations with specific links. Assistive functions have become:

• context help in the links format, which depends on the module;
• adding support for determining the choice of values for the parameter attribute.

Currently, this API is applied on the primary modules of the subsystem "Data acquisition", that is LogicLev, ModBus, Siemens, and as an optional feature for the controller object of the JavaLikeCalc module. From modules of other subsystems to the templates support, the protocol modules UserProtocol, ModBus and the graphical interface module WebUser have been adapted. Moreover, the use of templates in the modules UserProtocol and WebUser conceptually improved their functions and expanded the ability to create complex templates, examples and sample of which have become new templates:

• "Notifier (ntf)" — combines the template of the data source of the logical level and output protocols "SMS", "SMTP".
• "DCON" — combines the output protocol and the input protocols of individual prototype modules of this protocol (10AI, 8AO, 32DI, 32DO), which, with the ability to identify several protocols in the transport, allows you to install them in an arbitrary number and on the same bus (on different addresses), as well as with modules of other protocols such as ModBus.

No less potential, thanks to the use of DAQ-templates, has now got the graphical interface module WebUser, which should only be uncovered.

---