Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:sw:01-mervis:mervis-scada-project-hidden [2022/05/06 12:39] avsetula [4 Uploading the Mervis SCADA project definition] |
en:sw:01-mervis:mervis-scada-project-hidden [2024/04/03 07:46] (current) avsetula |
||
---|---|---|---|
Line 106: | Line 106: | ||
===== 2 PLC configuration ===== | ===== 2 PLC configuration ===== | ||
- | The second step is to configure the PLC to make it accessible for Mervis SCADA. Create a new project in the Mervis IDE, or open an existing one. The project must be opened in [[creating-new-project-hidden#switching_from_simple_mode_to_full_mode|Full mode]]. | + | The second step is to configure the PLC to make it accessible for Mervis SCADA. Create a new solution in the Mervis IDE, or open an existing one. The solution must be switched to [[creating-new-project-hidden#switching_from_simple_mode_to_full_mode|Full mode]]. |
Any PLC we want to connect to the SCADA project must be connected to the Mervis Proxy service. You can configure Mervis Proxy using the Proxy Parameters section located in the PLC properties. All the needed parameters are available in your [[https://www.unipi.technology/getmervis|Customer portal]]. Use a unique Proxy ID for each PLC. A more detailed description is available in the [[connecting-to-unipi-via-mervis-proxy-hidden|Connecting to Unipi via Mervis Proxy]] tutorial. | Any PLC we want to connect to the SCADA project must be connected to the Mervis Proxy service. You can configure Mervis Proxy using the Proxy Parameters section located in the PLC properties. All the needed parameters are available in your [[https://www.unipi.technology/getmervis|Customer portal]]. Use a unique Proxy ID for each PLC. A more detailed description is available in the [[connecting-to-unipi-via-mervis-proxy-hidden|Connecting to Unipi via Mervis Proxy]] tutorial. | ||
- | To display historic data in the SCADA control panel and the mobile app, the PLC must send data to the Mervis DB service. Each PLC within single SCADA project can have specific Mervis DB credentials, but identical credentials for all PLCs can also be used. Again, Mervis DB login info can be found in the [[https://www.unipi.technology/getmervis|Customer portal]]. A more detailed explanation is available in the [[storing-data-to-mervis-db-hidden|Storing data to the Mervis DB]] tutorial. | + | To display historic data (graphs) in the SCADA web interface or mobile application, it is necessary that the PLC stores data in Mervis DB. Together with the SCADA project, one set of Mervis DB credentials is also generated for all PLCs connected to this SCADA project. Setup and storing to DB is explained in detail in the [[storing-data-to-mervis-db-hidden|Storing data to the Mervis DB]] tutorial. |
Upon finishing the Mervis Proxy and Mervis DB configuration, don’t forget to [[updating-a-runtime-configuration-hidden|upload the configuration into the PLC]]. | Upon finishing the Mervis Proxy and Mervis DB configuration, don’t forget to [[updating-a-runtime-configuration-hidden|upload the configuration into the PLC]]. | ||
Line 323: | Line 322: | ||
<WRAP center round info 90%> | <WRAP center round info 90%> | ||
- | In case of editing dbtable, graphic HMI or any other adjustments in the SCADA terminal without any changes in the PLC itself, you do not need to deploy the solution into the PLC - a compilation only will do. By compiling the solution, a new definition for Mervis SCADA will be generated without affecting the PLC. | + | In case of editing dptable, graphic HMI or any other adjustments in the SCADA terminal without any changes in the PLC itself, you do not need to deploy the solution into the PLC - a compilation only will do. By compiling the solution, a new definition for Mervis SCADA will be generated without affecting the PLC. |
</WRAP> | </WRAP> | ||