-
Obtain the OPC UA Client Binaries: There are two options for obtaining the binaries:
-
Download the stable version from Releases
- Select
latest
release. - Download artefact for your operating system.
- use
windows-2022
for most versions of Win 10 and Win 11,(only older versions needwindows-2019
(see #477 for details)
- use
- If older than 4 weeks use alternative option.
- Select
-
Download the development version from the latest CI run
- Select newest workflow run.
- Download artifact for your operating system.
-
-
Unzip Folder
- Linux: Install
.deb
package withsudo dpkg -i dashboardopcuaclient_*_*.deb
- Linux: Install
-
Create configuration for Client on Windows:
- Within folder
bin
create a file calledconfiguration.json
- Within folder
-
Create configuration for Client on Linux:
- Create a file
configuration.json
in your home directory
- Create a file
-
Adapt configuration
- Open
configuration.json
(use any text editor) and insert content from here- configuration.json.example
- Change OPC UA and MQTT endpoint information according to Configuration
- Open
-
Start on Windows
DashboardOpcUaClient.exe
. -
Start on Linux
DashboardOpcUaClient configuration.json
from your home directory-
The start-up phase can last for up to 10 minutes, depending of the size of the server. When the client is connected to the MQTT broker a
1
is transmitted to the MQTT Broker on the topicumati/v2/<CompanyName>/<ClientName>/clientOnline
. The output of the console should look like this: -
After the start up a JSON containing all machine values is published on the MQTT Broker at topic
umati/v2/<CompanyName>/<ClientName>/<SpecificationType>/<EscapedMachineNodeId>
(e.g.umati/v2/ISW/ClientSampleServer/MachineToolType/nsu=http:_2F_2Fexample.com_2FBasicMachineTool_2F;i=66382
)
-
To monitor and restart the client automatically, please use the provided restart.ps1.
You need to modifiy the path to the DashboardOpcUaClient.exe
to use it.
# Add own path to the executable
$ProcessPath = "C:\work\umati\UmatiDashboardOpcUaClient-Release-windows-2022-amd64\bin"
For the Debug version also the DLLs of Debugging are nessasry: