Versions Compared

Old Version 12

changes.mady.by.user Dennis Hezel

Saved on

compared with

New Version 13

changes.mady.by.user Simone Dal Poz

Saved on

Key

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

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.

Creating a secret file:

Info

For OPC/UA authentication (since 1.3) 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.4+

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.

✗

authentication_file_path

./secret.json

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

✓

...

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

Secret file example:

...

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
[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.
✗
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
languagejson
{
   // Client Id
   "usernametype":"usernameEOS",
   // Client Secret
   "passwordurl":"password",
   
   // Optionally override secrets:
   // Relative or absolute path to a PEM or DER file, or its content inlineopc.tcp://SI3456:4843",
   "certificateauthentication_file_path":"./my_certsecret.der",
   // Subject Alternative Name, URI=json",
   "applicationmes_uriid":"urn:example.com",[
   // Relative or absolute path to1
a PEM or DER file, or its content inline
   "private_key":"./my_priv.der",
}
Obtaining access credentials:
...
 ]
}
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
  ]
}
...