Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
en:sw:01-mervis:08-sscp-bridge [2020/05/11 11:08] avsetula |
en:sw:01-mervis:08-sscp-bridge [2020/07/15 08:22] jan_kozak [Configuration] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== SSCP to SQL Bridge ====== | ====== SSCP to SQL Bridge ====== | ||
| - | This daemon-based service allows bi-directional data transfer between an Unipi PLC running Mervis and a SQL database through an SSCP protocol (the proprietary protocol used by Mervis runtime and Mervis IDE). The daemon can run anywhere - on the system with Mervis runtime running, on the same system as a database server or another remote machine. | + | This daemon-based service allows bi-directional data transfer between an Unipi PLC running Mervis and a SQL database through an SSCP protocol (the proprietary protocol used by Mervis). The daemon can run on any Linux machine (database server or another remote machine) or directly on the PLC. |
| {{ :en:sw:01-mervis:sscp-sql-bridge.png?direct |}} | {{ :en:sw:01-mervis:sscp-sql-bridge.png?direct |}} | ||
| Line 6: | Line 6: | ||
| * **Daemon runs on the PLC** | * **Daemon runs on the PLC** | ||
| * In this case, the daemon runs on the PLC right next to the Mervis RT and send the data to a remote database. Requires IP connection between the PLC and the database server. | * In this case, the daemon runs on the PLC right next to the Mervis RT and send the data to a remote database. Requires IP connection between the PLC and the database server. | ||
| - | * **Daemon runs a different machine/server** | + | * **Daemon runs on a different machine/server** |
| * This can be divided into two scenarios depending on the network connection. | * This can be divided into two scenarios depending on the network connection. | ||
| * **Daemon has IP access to the PLC** | * **Daemon has IP access to the PLC** | ||
| Line 45: | Line 45: | ||
| - One or more **.vlist** file(s) containing a list of all variables in the Mervis project(s). These files are generated automatically by the Mervis IDE and are located in the main Mervis project folder in your Windows PC. These files should be copied (eg. using SCP) from the PC to the PLC/server where this toll will run. Default path within the PLC/server is /opt/unipi/data/ and can be changed in the **mapping.yaml** file. This .vlist file should not be edited manually. | - One or more **.vlist** file(s) containing a list of all variables in the Mervis project(s). These files are generated automatically by the Mervis IDE and are located in the main Mervis project folder in your Windows PC. These files should be copied (eg. using SCP) from the PC to the PLC/server where this toll will run. Default path within the PLC/server is /opt/unipi/data/ and can be changed in the **mapping.yaml** file. This .vlist file should not be edited manually. | ||
| - | Care should be taken that the configuration files follow the valid YAML format. An online YAML validator (such as this one https://codebeautify.org/yaml-validator) can be used to ensure this. Do not add any extra fields that are not listed in the example. | + | Make sure the configuration files follow the valid YAML format. An online YAML validator (such as this one https://codebeautify.org/yaml-validator) can be used to ensure this. Do not add any extra fields that are not listed in the example. |
| The structure of the mapping.yaml file is described below. | The structure of the mapping.yaml file is described below. | ||
