Siemens Ecosystem.<\/strong><\/h1>\n <\/p>\n
Siemens<\/strong> is, indisputably, one of the most present automation hardware and software manufacturers<\/strong> at the European level. Practically all factories and facilities in Spain have, to a greater or lesser extent, some component of their installation from this brand. Its presence over the last 40 or 50 years and its extensive portfolio means that we can find everything from drives to PLCs, IT infrastructure or industrial management software anywhere. <\/p>\nAs a manufacturer with such a presence, it is obvious that many automation and systems integration projects require communicating some of its elements with the other systems of the installation. To do this, we must explain that all communication with the field elements will be resolved through the use of OPC Servers<\/strong>. OPC Router is not software designed for these communications as it is already very well resolved with solutions such as KEPServerEX<\/a>.<\/strong> <\/p>\nThus, in this specific post we will discuss how OPC Router allows connecting the main Siemens control and management tools with all the other systems of an installation.<\/p>\n
<\/p>\n
I <\/span>Integration with Old or S7 Range PLCs<\/strong><\/h4>\nExample architecture: KEPServerEX + OPC plugin + SQL plugin<\/strong><\/p>\nSiemens PLCs<\/strong> are the most common in our industries. Almost everyone has had to fight with S7-200, S7-300, S7-400 or S7-1200. But not only that, 20 or 25 years after the first PLC of the S7 range, we still find S5 PLCs working \u2013 the classic, if it works don’t touch it -. <\/p>\nTo communicate with all of them, we will need an OPC Server such as KEPSeverEX<\/strong> that is capable of acquiring information from them through its specific driver and serving that information in OPC DA or OPC UA.<\/p>\nTo give a practical example, once we have the PLC data in this protocol, with OPC Router we can use the OPC plugin<\/strong> and send that data to a historization system using the SQL plugin.<\/p>\n![\"Integration](\"https:\/\/becolve.com\/wp-content\/uploads\/2023\/04\/Integracion-con-PLCs-1024x578.png\")
<\/p>\n
<\/h4>\nI<\/span> Integration with LOGO!.<\/strong><\/h4>\nExample architecture: KEPServerEX + OPC plugin + MQTT plugin.<\/strong><\/p>\nLOGO! is a new range of low-cost controllers from Siemens<\/strong> very focused on being practical and simple. Without being so powerful, they are designed for simple automations or for home automation. <\/p>\nThese new controllers, report the information upstream through Modbus<\/strong>. That is why, to integrate that information with other systems, we will once again require an OPC Server with a Modbus driver to transform that data into OPC. <\/p>\nThus, the path is the same as in the previous case, the OPC plugin of OPC Router will communicate with the OPC Server<\/strong> to send the information wherever it is needed, to an IoT cloud platform via MQTT, for example.<\/p>\n <\/p>\n
I<\/span> Integration with S7-1500 PLCs.<\/strong><\/h4>\nExample architecture: OPC plugin + REST plugin.<\/strong><\/p>\nUnlike the previous equipment, the Siemens S7-1500 PLC is an OPC UA Server<\/strong>, so from OPC Router we can acquire information from it directly without the need for an intermediate OPC Server. From the point of view of robustness and scalability,<\/strong> it will always be more robust to use an OPC Server to centralize<\/strong> and optimize the traffic of communications between the process and the systems. OPC Servers always make architectures more secure. <\/p>\nHowever, from a technical point of view,<\/strong> for this range of PLCs we can communicate directly since they have the possibility of being OPC UA Servers themselves. With this data, we can send it, for example, to an energy management system<\/strong> that requires the data to be sent via REST API. <\/p>\n <\/p>\n
I<\/span> Integration with WINCC.<\/strong><\/h4>\n\n- Example architecture 1: OPC plugin + InfluxDB plugin.<\/strong><\/li>\n
- Example architecture 1: OPC Server plugin + Domino printer plugin.<\/strong><\/li>\n<\/ul>\n
Siemens<\/strong> is not only a hardware manufacturer, but also has software solutions for industrial monitoring and control<\/strong>. Among these solutions, WINCC Professional and WINCC OA stand out mainly. In addition, through its different modules and libraries it is possible to add additional functionalities to the classic SCADA ones. <\/p>\nCurrently, many of the projects in which there is WINCC it is necessary to communicate it with equipment<\/strong> and systems that are not from the Siemens family. For this, OPC Router is the tool that allows us to open WINCC to all other manufacturers. <\/p>\nIn this specific case, we have two architecture options<\/strong>.<\/p>\n\n- The first consists of enabling the option in WINCC that it is an OPC Server<\/strong>. Once enabled, through the OPC plugin we can send or request the information we want. For example, with this architecture we could save information from WINCC in an Influx database. <\/li>\n
- The second scenario is where we do not want or cannot enable WINCC as an OPC Server<\/strong>. In this case, what we should do is give that function to OPC Router through its OPC Server plugin. In this case, it will be WINCC through its connectivity drivers who will communicate with OPC Router to acquire the information. An example of use would be a scenario where WINCC has to communicate directly to a printer to transmit the codes that must be put on the labels. <\/li>\n<\/ol>\n
<\/p>\n
I<\/span> Integration with Mindsphere.<\/strong><\/h4>\nExample architecture: SQL plugin + MQTT plugin.<\/strong><\/p>\nMindsphere is the Siemens cloud Iot platform<\/strong>. This platform, based on the AWS cloud, seeks to analyze the data sent to it from an installation or factory to draw conclusions and valuable information for decision making. <\/p>\nThat is why, to extract useful resolutions<\/strong>, the most normal thing is that it should not only receive data from the installed Siemens devices, but also from all the other equipment and systems present in the installation.<\/p>\nThe protocol that allows sending data to Mindsphere is MQTT, as also happens in other cloud platforms<\/a><\/strong>. Thus, with OPC Router we can integrate all the information from the other elements in Mindsphere<\/strong> through its MQTT plugin. For example, we could send to Mindsphere all the new records that are made in an SQL database. <\/p>\n![\"Mindsphere](\"https:\/\/becolve.com\/wp-content\/uploads\/2023\/04\/Mindsphere-1024x590.png\")
<\/p>\n
As a manufacturer with such a presence, it is obvious that many automation and systems integration projects require communicating some of its elements with the other systems of the installation. To do this, we must explain that all communication with the field elements will be resolved through the use of OPC Servers<\/strong>. OPC Router is not software designed for these communications as it is already very well resolved with solutions such as KEPServerEX<\/a>.<\/strong> <\/p>\n Thus, in this specific post we will discuss how OPC Router allows connecting the main Siemens control and management tools with all the other systems of an installation.<\/p>\n <\/p>\n Example architecture: KEPServerEX + OPC plugin + SQL plugin<\/strong><\/p>\n Siemens PLCs<\/strong> are the most common in our industries. Almost everyone has had to fight with S7-200, S7-300, S7-400 or S7-1200. But not only that, 20 or 25 years after the first PLC of the S7 range, we still find S5 PLCs working \u2013 the classic, if it works don’t touch it -. <\/p>\n To communicate with all of them, we will need an OPC Server such as KEPSeverEX<\/strong> that is capable of acquiring information from them through its specific driver and serving that information in OPC DA or OPC UA.<\/p>\n To give a practical example, once we have the PLC data in this protocol, with OPC Router we can use the OPC plugin<\/strong> and send that data to a historization system using the SQL plugin.<\/p>\n Example architecture: KEPServerEX + OPC plugin + MQTT plugin.<\/strong><\/p>\n LOGO! is a new range of low-cost controllers from Siemens<\/strong> very focused on being practical and simple. Without being so powerful, they are designed for simple automations or for home automation. <\/p>\n These new controllers, report the information upstream through Modbus<\/strong>. That is why, to integrate that information with other systems, we will once again require an OPC Server with a Modbus driver to transform that data into OPC. <\/p>\n Thus, the path is the same as in the previous case, the OPC plugin of OPC Router will communicate with the OPC Server<\/strong> to send the information wherever it is needed, to an IoT cloud platform via MQTT, for example.<\/p>\n <\/p>\n Example architecture: OPC plugin + REST plugin.<\/strong><\/p>\n Unlike the previous equipment, the Siemens S7-1500 PLC is an OPC UA Server<\/strong>, so from OPC Router we can acquire information from it directly without the need for an intermediate OPC Server. From the point of view of robustness and scalability,<\/strong> it will always be more robust to use an OPC Server to centralize<\/strong> and optimize the traffic of communications between the process and the systems. OPC Servers always make architectures more secure. <\/p>\n However, from a technical point of view,<\/strong> for this range of PLCs we can communicate directly since they have the possibility of being OPC UA Servers themselves. With this data, we can send it, for example, to an energy management system<\/strong> that requires the data to be sent via REST API. <\/p>\n <\/p>\n Siemens<\/strong> is not only a hardware manufacturer, but also has software solutions for industrial monitoring and control<\/strong>. Among these solutions, WINCC Professional and WINCC OA stand out mainly. In addition, through its different modules and libraries it is possible to add additional functionalities to the classic SCADA ones. <\/p>\n Currently, many of the projects in which there is WINCC it is necessary to communicate it with equipment<\/strong> and systems that are not from the Siemens family. For this, OPC Router is the tool that allows us to open WINCC to all other manufacturers. <\/p>\n In this specific case, we have two architecture options<\/strong>.<\/p>\n <\/p>\n Example architecture: SQL plugin + MQTT plugin.<\/strong><\/p>\n Mindsphere is the Siemens cloud Iot platform<\/strong>. This platform, based on the AWS cloud, seeks to analyze the data sent to it from an installation or factory to draw conclusions and valuable information for decision making. <\/p>\n That is why, to extract useful resolutions<\/strong>, the most normal thing is that it should not only receive data from the installed Siemens devices, but also from all the other equipment and systems present in the installation.<\/p>\n The protocol that allows sending data to Mindsphere is MQTT, as also happens in other cloud platforms<\/a><\/strong>. Thus, with OPC Router we can integrate all the information from the other elements in Mindsphere<\/strong> through its MQTT plugin. For example, we could send to Mindsphere all the new records that are made in an SQL database. <\/p>\nI <\/span>Integration with Old or S7 Range PLCs<\/strong><\/h4>\n
<\/p>\n <\/h4>\n
I<\/span> Integration with LOGO!.<\/strong><\/h4>\n
I<\/span> Integration with S7-1500 PLCs.<\/strong><\/h4>\n
I<\/span> Integration with WINCC.<\/strong><\/h4>\n
\n
\n
I<\/span> Integration with Mindsphere.<\/strong><\/h4>\n
<\/p>\n