In a process, where the data transfer is an essential component of the workflow, hardware failures might slow down or even endanger the process. Therefor in this repository we explain how to setup a redundant infrastructure of Industrial Edge with IIH and Opcener Execution Core. This example should serve as a blueprint, if a similar redundant infrastructure is needed.
This tutorial describes the steps, that are necessary to create a redundant communication from the PLC over Industrial Edge to Opecenter. Following graphic illustrates the final structure.
- Industrial Edge Management License for two devices
- Purchased apps: Common Configurator, IIH Semantics, IIH Essentials, Registry Service, Databus, Databus Gateway, and SIMATIC S7+ Connector
- Opcenter Execution Discrete License
- TIA Portal License
- PLCSIM Advanced License
- TIA-Portal
- Industrial Edge Management (IEM)
- Industrial Edge Device (IED)
- Opcenter Execution Discrete
By meticulously following these steps, you'll establish a robust and synchronized environment for your industrial automation operations.
The guide is provided here.
The guide is provided here.
- Execute Save Sequence
- Request Next
- Request Order Info
- Execute Work Order Operation
- Execute Work Instruction Data Collection
- Execute Quality Inspection
- Track Item Location Single
Both IEDs are setup redundant, therefor both IEDs are collecting data simultanously. The Opcenter installation is subscribed to both OPC UA Servers running on the IEDs. If one IED has a failure, Opcenter automatically detects the failure and switches to the redundant alternative. In turn, when one instance of Opcenter crashes, the Secondary instances of Opcenter are taking over.
You can find further documentation and help in the following links
- Industrial Edge Hub
- Industrial Edge Forum
- Industrial Edge Documentation
- Industrial Edge landing page
- Industrial Edge GitHub page
Thank you for your interest in contributing. Anybody is free to report bugs, unclear documentation, and other problems regarding this repository in the Issues section. Additionally everybody is free to propose any changes to this repository using Pull Requests.
If you haven't previously signed the Siemens Contributor License Agreement (CLA), the system will automatically prompt you to do so when you submit your Pull Request. This can be conveniently done through the CLA Assistant's online platform. Once the CLA is signed, your Pull Request will automatically be cleared and made ready for merging if all other test stages succeed.
Please read the Legal information.