-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Co-authored-by: Goetz Goerisch <[email protected]> Signed-off-by: Goetz Goerisch <[email protected]>
- Loading branch information
1 parent
9d5248d
commit 8391639
Showing
5 changed files
with
104 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,102 @@ | ||
| # umati showcase information model for Laser Systems | ||
|
|
||
| In the following the umati showcase describes the additional information on top of the [OPC 40501-1 UA for LaserSystems](https://reference.opcfoundation.org/LaserSystems/v100/docs/) companion specification. | ||
|
|
||
| ## NodeSets | ||
|
|
||
| [Normative NodeSet hosted by the OPC Foundation](https://github.com/OPCFoundation/UA-Nodeset/tree/latest/LaserSystems) | ||
|
|
||
| ## General information valid for the umati showcase demonstration | ||
|
|
||
| | **DISCLAIMER** | For all applications the OPC UA server is to be configured without predefined NodeIds for the instances. Clients need to utilize the Services [Browse](https://reference.opcfoundation.org/Core/docs/Part4/5.8.2/) and [TranslateBrowsePathsToNodeIds](https://reference.opcfoundation.org/Core/docs/Part4/5.8.4/) to access nodes of interest. | | ||
|
|
||
| ### Identification data | ||
|
|
||
| The identification for Laser Systems are inherited from the Machinery companion specification. | ||
| To fill the demo dashboard machine page with the most content the variables marked with a **strong mandatory** should be provided if you like to look the machine identification nicely. | ||
|
|
||
| #### [**MachineIdentificationType Definition**](https://reference.opcfoundation.org/Machinery/docs/8.6/) | ||
|
|
||
| | **Attribute** | **Value** | | | | | | ||
| | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | --------------------------- | --------------- | ------------------ | --------- | | ||
| | BrowseName | MachineIdentificationType | | | | | | ||
| | IsAbstract | False | | | | | | ||
| | Description | Contains information about the identification and nameplate of a machine | | | | | | ||
| | | | | | | | | ||
| | **References** | **NodeClass** | **BrowseName** | **DataType** | **TypeDefinition** | **Other** | | ||
| | Subtype of the 2:FunctionalGroupType defined in OPC 10000-100, i.e. inheriting the InstanceDeclarations of that Node. | | | | | | | ||
| | 0:HasProperty | Variable | 0:DefaultInstanceBrowseName | 0:QualifiedName | 0:PropertyType | | | ||
| | 0:HasInterface | ObjectType | IMachineVendorNameplateType | | | | | ||
| | 0:HasInterface | ObjectType | IMachineTagNameplateType | | | | | ||
| | Applied from IMachineVendorNameplateType | | | | | | | ||
| | 0:HasProperty | Variable | 2:ProductInstanceUri | 0:String | 0:PropertyType | M, RO | | ||
| | 0:HasProperty | Variable | 2:Manufacturer | 0:LocalizedText | 0:PropertyType | M, RO | | ||
| | 0:HasProperty | Variable | 2:ManufacturerUri | 0:String | 0:PropertyType | O, RO | | ||
| | 0:HasProperty | Variable | **2:Model** | 0:LocalizedText | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | **2:ProductCode** | 0:String | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | 2:HardwareRevision | 0:String | 0:PropertyType | O, RO | | ||
| | 0:HasProperty | Variable | **2:SoftwareRevision** | 0:String | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | 2:DeviceClass | 0:String | 0:PropertyType | O, RO | | ||
| | 0:HasProperty | Variable | 2:SerialNumber | 0:String | 0:PropertyType | M, RO | | ||
| | 0:HasProperty | Variable | **YearOfConstruction** | UInt16 | 0:PropertyType | **M**, RO | | ||
| | 0:HasProperty | Variable | MonthOfConstruction | Byte | 0:PropertyType | O, RO | | ||
| | 0:HasProperty | Variable | InitialOperationDate | DateTime | 0:PropertyType | O, RO | | ||
| | Applied from IMachineTagNameplateType | | | | | | | ||
| | 0:HasProperty | Variable | 2:AssetId | 0:String | 0:PropertyType | O, RW | | ||
| | 0:HasProperty | Variable | 2:ComponentName | 0:LocalizedText | 0:PropertyType | O, RW | | ||
| | 0:HasProperty | Variable | **Location** | 0:String | 0:PropertyType | **M**, RW | | ||
|
|
||
| #### Special requirements for correct location of the machine icon on the dashboard | ||
|
|
||
| The instance _Location_ property is evaluated according to the special requirements detailed [here](../Dashboard.md#location-of-fair-machine-and-software-icons-on-the-dashboard) to place a map icon for the machine. | ||
|
|
||
| ### Adaption of the provided information models for your purpose | ||
|
|
||
| - The provided NodeSet contains the address space with the ObjectTypes, VariableTypes and DataTypes of the Laser Systems companion specification and **must not** be changed. | ||
| - Change the URI of the instance namespace (optional, but recommended) | ||
|
|
||
| `http://www.<MANUFACTURERDOMAIN>/example` | ||
|
|
||
| - The rules for creating a URI can be found online. Please follow [this link](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier). | ||
| In the case of a URL as a URI, it is not necessary that the site actually exists, it only identifies the machine uniquely. | ||
| In order to simplify debugging it is recommended to choose a URI which allows an identification of the machine also for third persons, e.g. by including the company name. | ||
|
|
||
| - The machine will get a unique identifier like `clientId%3Dvdw%7Csmplsrv1%3Bnsu%3Dhttp%3A_2F_2Fwww.wenzel-group.com_2FWenzel_20LH_2087_2F%3Bi%3D66382` - `<clientId><mqttusername><NamespaceUri><EntryNodeId>` in the MQTT tree and in the Dashboard URL. | ||
|
|
||
| ## Value mapping between OPC UA companion specification and umati.app machine instance page | ||
|
|
||
| ### Laser System - Overview | ||
|
|
||
|  | ||
|
|
||
| ### Active Program Statusbar | ||
|
|
||
| For the status overview in the dashboard, the _StateNumber_ of the _4:Monitoring_.LasterSystemStatus.LaserSystemState*StateMachineType.CurrentState.Number* is stored and plotted over time. The status bar **does NOT relate to the stacklight** status! | ||
|
|
||
| Each status is assigned to a color, the color scheme is here (subject to change): | ||
|
|
||
| | State | Number | Color | | ||
| | ----------------------------- | ------ | --------------- | | ||
| | Off | 0 | ⚪ Grey | | ||
| | EnergySaving | 1 | ⚪ Grey | | ||
| | Idle | 2 | ⚪ Grey | | ||
| | SetUp | 3 | ⚪ Grey | | ||
| | LaserReady | 4 | ⚪ Grey | | ||
| | Maintenance | 5 | ⚪ Grey | | ||
| | Error | 6 | ⚪ Grey | | ||
| | LaserOn | 7 | 🟢 Green | | ||
| | Any other (unspecified) state | | ⚫ Black | | ||
|
|
||
| A gap is left for periods of time in which no data was recorded (e.g. machine offline). An exemplary timeline is shown above. | ||
|
|
||
| ### Laser Systems - Identification | ||
|
|
||
|  | ||
|
|
||
| ### Laser Systems- Production | ||
|
|
||
|  | ||
|
|
||
| ### Laser Systems - Monitoring | ||
|
|
||
|  |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.