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.
Aggregator version 1.4+
Configuration | Data | Description | Required |
|---|---|---|---|
|
| The machine's interface type. | ✓ |
|
| The individual machine's interface url. | ✓ |
|
| The MES instance(s) of your organization. | ✓ |
|
| 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
]
}
OR
{
"type":"EOS",
"url":"opc.tcp://SI3456:4843",
"authentication_file_path":
{
"username":"username",
"password":"password",
"certificate":"./my_cert.der",
"application_uri":"urn:example.com",
"private_key":"./my_priv.der",
},
"mes_id":[
1
]
}
Creating a secret:
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. Starting from version 1.4, you can also inline the contents of your secret file in the in the authentication_file_path field.
{
// 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",
}
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.
{
// 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",
}
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:
{
"type": "EOS",
"url": "opc.tcp://SI3456:4843",
"mes_id": [
1
]
}