Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

You need at least aggregator version 1.1.1 to use this configuration.

Configuration Overview

The following configuration options of the common machine configuration model applies 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 EOS Connect interface: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

Descripton

Description

Mandatory

Required

type

EOS

The

machines

machine's interface type.

x

url

opc.tcp://

192.168.2.47

SI3456:4843

The individual machine's interface

URL

url.

x

custom_name

my_eos_machine

The custom machine name

will be displayed in MES together with the machine interface URL.

to be displayed in the Agile MES. Will be read from the machine if unset.

mes_id

[1]

The MES instance(s) of your organization.

authentication_file_path

./secret.json or

JSON object

Secrets for OPC/UA authentication (see below). For files, the path can be absolute or relative to the Aggregator.

EOS Connect machine example:

Code Block
languagejson
{
  "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:

Code Block
languagejson
{
  // 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

type

EOS

The machine's interface type.

url

opc.tcp://SI3456:4843

The individual machine's interface url.

mes_id

[

10, 33

1]

The MES instance(s) of your organization.

x

umati_server_port

4840+

To specify umati

Umati server port used for

data transfer between aggregator and the machine driver.optional

internal data transfer. Set if the default port is conflicting with another port on your server.

authentication_file_path

./secret.json

A secrets file for OPC/UA authentication (see below). Path can be absolute or relative to the Aggregator.

EOS Connect machine example:

Code Block
breakoutModelanguagewidejson
{

    "type": "EOS",
 
   "url": "opc.tcp://192.168.2.47",
     "custom_name": "my_eos_machine",
     "mes_id": [
        10,
        33
   SI3456:4843",
   "authentication_file_path":"./secret.json",
   "mes_id":[
      1
   ]
}

Creating a secret.json file:

Info

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.

Code Block
languagejson
{
   // 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

type

EOS

The machine's interface type.

url

opc.tcp://SI3456:4843

The individual machine's interface url.

mes_id

[1]

The MES instance(s) of your organization.

umati_server_port

4840+

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:

Code Block
languagejson
{
  "type": "EOS",
  "url": "opc.tcp://SI3456:4843",
  "mes_id": [
    1
  ]
}