====== Module operation ======
The reading/writing of values, incl. configuration, is done by the Modbus RTU protocol (RS-485 interface) according to the registers in [[..:downloads|Modbus table]]. The configuration (registers 1000-1100) allows to set e.g. the analogue input/output measurement mode or [[..:communication-and-addressing-of-module|SW communication parameters]].
The configuration and the current state of the outputs can be saved with **coil 1003** as the default configuration, which is restored at module startup.
===== Quick solutions =====
Because deploying the Modbus protocol is not always easy or comfortable, we have ensured that all Unipi Extension device definitions are included in the most widely used Unipi controller software solutions.
=== Creating your own app? ===
If Modbus RTU communication is not possible in the selected software or is not easily deployable, you can use one of the protocols provided by **Evok**, which is an API interface for accessing the inputs and outputs of Unipi products. Detailed information, including documentation on installing and using the API, is available at [[..:..:..:sw:02-apis:01-evok|this link]].
{{ :files:img_warning-line_b.png?nolink |}}
{{:en:hw:08_safety-instructions_pseudo-ISO-7010-info.png?nolink |(i)}}
**Please note**: \\
An alternative or complement to Evok can also be [[..:..:..:sw:02-apis:04-sysfs|sysfs access]].
=== Programmable Logic Controllers (PLC)? ===
Units with Mervis SW are the most ideal choice. The communication with the extension module is done via the Modbus RTU protocol only and the modules can be easily connected by [[..:..:..:sw:01-mervis:connecting-to-unipi-extension-hidden#working_with_expanding_unipi_modules_in_mervis|automatic bus search]]. Configuration is possible in the Mervis IDE by comfortably setting properties or module inputs/outputs and [[..:..:..:sw:01-mervis:unipi-configure-module-hidden|save/upload]] with a simple dialog.
\\
{{ :en:sw:mervis_color_without_padding.png?nolink&175 |}}
=== Flow-based programming? ===
Node-RED OS for Unipi units has Node-RED SW pre-installed, incl. [[https://flows.nodered.org/node/@unipitechnology/node-red-contrib-unipi-evok|prepared nodes]] communicating with the Evok API via Websocket. Adding an extension module is described in [[..:..:..:sw:02-apis:01-evok|Evok documentation]].
{{ :en:sw:03-3rd-party:node-red-icon-2.png?nolink&175 |}}