EOS Connect Machine Configuration
- Karl Patrick Möller
- Dennis Hezel
- Andres Repcik
- Simone Dal Poz
The following configuration options of the common machine configuration model apply to EOS Connect machines.
Obtaining access credentials:
Obtain username and password at https://si3456/gui/auth, replace si3456 with the actual ID of the machine. This page is secured with a login and you will need to use your EOScada credentials to access it. Only EOScada credentials that have the role of Supervisor can add new clients.
You must have purchased the EOSCONNECT Core license (40194). The purchased license will be activated on the machine after its first setup. To acquire additional licenses, or renew existing ones that are about to expire, contact your EOS field service technician.
Aggregator version 1.4+
Configuration | Data | Description | Required |
|---|---|---|---|
|
| The machine's interface type. | ✓ |
|
| The individual machine's interface url. | ✓ |
|
| The custom machine name to be displayed in the Agile MES. Will be read from the machine if unset. | ✗ |
|
| The MES instance(s) of your organization. | ✓ |
|
| Secrets for OPC/UA authentication (see below). For files, the path can be absolute or relative to the Aggregator. | ✓ |
EOS Connect machine example:
{
"type": "EOS",
"url": "opc.tcp://SI3456:4843",
"custom_name": "my_eos_machine",
"authentication_file_path": "./secret.json", // contents may also be inlined
"mes_id": [
1
]
}secret.json:
{
// Client Id
"username": "username",
// Client Secret
"password": "password",
// **Optionally** override secrets:
// Relative or absolute path to a PEM or DER file, or its content inline
//"certificate": "./my_cert.der",
// Subject Alternative Name, URI=
//"application_uri": "urn:example.com",
// Relative or absolute path to a PEM or DER file, or its content inline
//"private_key": "./my_priv.der",
}Troubleshooting
Sending data to the Agile MES fails with error:
certificate verify failed
Import the certificate of the Agile MES into the Local Machine’s certificate store:Open the Agile MES website in the browser.
Click on the Lock icon next to the address line
Export the certificate: Connection is secure → Certificate is valid → Details → Export selected certificate…
Double-click on the downloaded certificate (it should open using Crypto shell extensions)
Follow the steps in the pictures:
Aggregator version 1.3
Configuration | Data | Description | Required |
|---|---|---|---|
|
| The machine's interface type. | ✓ |
|
| The individual machine's interface url. | ✓ |
|
| The MES instance(s) of your organization. | ✓ |
|
| Umati server port used for internal data transfer. Set if the default port is conflicting with another port on your server. | ✗ |
|
| A secrets file for OPC/UA authentication (see below). Path can be absolute or relative to the Aggregator. | ✓ |
EOS Connect machine example:
{
"type":"EOS",
"url":"opc.tcp://SI3456:4843",
"authentication_file_path":"./secret.json",
"mes_id":[
1
]
}Creating a secret.json file:
For OPC/UA authentication you will have to create a file similar to the one below and adjust the authentication_file_path in your config.json.
Aggregator version 1.1 - 1.2
Configuration | Data | Description | Required |
|---|---|---|---|
|
| The machine's interface type. | ✓ |
|
| The individual machine's interface url. | ✓ |
|
| The MES instance(s) of your organization. | ✓ |
|
| Umati server port used for internal data transfer. Set if the default port is conflicting with another port on your server. | ✗ |
EOS Connect machine example: