Overview
General
The OPC UA Server is a part of the PLC and establishes a connection to the OPC UA Client (Fiware).
Purpose
- Transmit a trigger for program version request
- Transmit a trigger for program to the robot
- Transmit a trigger for program to the database
- Receive program version information
- Receive update status
- (Receive program editing status)
Example
The operator triggers from the PLC a request for a certain program (with part/mould ID).
The OPC UA Server transmits this "version request" to OPC UA Client --> Fiware.
From Fiware --> OPC UA Client comes the answer with:
Requested program exists or not and if the related version was ever downloaded to the robot.
The operator now can choose following options to do next:
- Robot update --> the robot gets the program version from the database
- Database update --> the database gets the program version from the robot
- Nothing
When the operator chooses a robot/database update a trigger is transmited to the Robot Program Handler Client.
The RPH then performs the update and gives a feedback to the PLC (Fiware --> OPC UA Client).
The feedback then is shown on the HMI (update successfull or not).
Overview
General
The OPC UA Server is a part of the PLC and establishes a connection to the OPC UA Client (Fiware).
Purpose
Example
The operator triggers from the PLC a request for a certain program (with part/mould ID).
The OPC UA Server transmits this "version request" to OPC UA Client --> Fiware.
From Fiware --> OPC UA Client comes the answer with:
Requested program exists or not and if the related version was ever downloaded to the robot.
The operator now can choose following options to do next:
When the operator chooses a robot/database update a trigger is transmited to the Robot Program Handler Client.
The RPH then performs the update and gives a feedback to the PLC (Fiware --> OPC UA Client).
The feedback then is shown on the HMI (update successfull or not).