Data connection

The Data Connection is required to inform the JUMO Cloud Software Edge Gateway (for e.g. the JUMO variTRON device) which protocol it should use to pick up the Signals / data from a specific location.

There are different ways of retrieving values or signals in the JUMO variTRON Cloud Edge Gateway. These data connections do not require extra licensing:

Additional data connections can be used with JUMO smartWARE SCADA. See data sheet.

How to Link variTRON Data to the Cloud?

1. By selecting the "Data Connection" button, you can edit a data connection that was created earlier. A new data connection is created via the Plus button.

   

2. Assign the name of the data connection in the Basic Configuration. The Description field is optional. The "Group" field shows the Client in which this data connection was created. The path is generated automatically by the system.

   

3. In the "Data Source" field, select the relevant data source that was created.

   

4. The selected data source is entered in the field.

5. Save via the disk icon in the upper right corner. When using a new data connection, default values are automatically entered.

6. Select type (only the data connections listed above are relevant in the JUMO Cloud).

   

Advanced Settings

OpcUa

An OPC UA data connection is required if I want to transport the values of the JUMO variTRON device to the cloud (e.g. values from analog inputs). For this purpose, "Codesys" and "OPC UA" must be activated in the JUMO variTRON.

Enter in the field "URL": opc.tcp://localhost:4840 to reach the internal OPC UA Server of the variTRON (Codesys OPC UA Server).

opc.tcp://localhost:4840

Other OPC UA servers can also be addressed. For this purpose their URL is required.

The following part is described here, but is usually set correctly as default:

1. Select security rule:

   1. Basic128Rsa15: Retrieves an algorithm suite that uses RSA15 as the key wrap algorithm and 128-bit Basic as the message encryption algorithm.

   2. Basic256: A 256-bit encryption means the length of the key (= 256 bit).

   3. Basic256Sha256: Retrieves an algorithm collection that uses SHA256 for the signature digest and 256-bit Basic as the message encryption algorithm.

2. Select security mode:

   1. None: No security mode selected.

   2. Sign: Easier login without complex encryption.

   3. SignAndEncrypt: Secure login with encryption.

3. Select security authentication:

   1. Anonymous: Without authentication process.

   2. Credentials: Username and password for authentication.

   3. Certificate and private key for authentication.

4. Specify publishing interval (time in seconds until data is published and ready to be sent).

5. Specify sampling interval (time in seconds until data is sampled).

6. Specify queue size (maximum place in the queue at login).

7. Specify timeout (maximum time to wait for a signal).

8. Select coding:

   1. ASCII

   2. UTF7

   3. UTF8

   4. Unicode

   5. UTF32

Modbus

A Modbus TCP data connection is required if you want to send data to the Cloud from other devices (e.g. LOGOSCREEN or Aquis touch) via the JUMO variTRON. The JUMO variTRON merely serves as a gateway to retrieve data from peripheral devices.

1. The IP address of the required device is entered in the "Host" field.

2. The "Port" is usually correctly preset.

S7

A S7 TCP (PROFINET) data connection is required if you want to send data to the Cloud from SIEMENS devices (e.g. Siemens logo) via the JUMO variTRON. The JUMO variTRON merely serves as a gateway to retrieve data from peripheral devices.

The data connection to a S7 is always made with the IP address of the PLC and the PG connection on port 102.

Rack and Slot are to be entered with the S7-1200/1500 firmly on Rack 0 and Slot 1. With the old S7-300/400 the setting is to be taken from the system manager, with the S7-300 it is generally rack 0, slot 2.

Host: Here the address of the variTRON is entered, on which the cloud runs

Port: the released port is entered here. Default is 102

Rack: see above

Slot: see above

Timeout: Individual time in seconds in which to wait for response

LocalTSAP: Here the LocalTSAP will be one.

Die TSAP Settings are normally irrelevant, so leave empty, these only become relevant in more complex setups.

TSAP: Transport Service Access Point.
Comes from the time when there was only communication via the backplane bus by means of CP. The PLC had to transfer the data via I/O addresses. For this it was important in the CPU to know the rack (row) and slot number where the CP (communication processor) is plugged.

References

All references to this Data Connection are displayed in the References.

AuditLog

The AuditLog is a change log that transparently shows how the object was changed. For some objects, it also shows which target values were set by a specific person. Power users can use the button on the right-hand side to get a detailed view of exactly what has been changed in the configuration.

The AuditLog can be used to quickly trace what happened to the object last. It corresponds to an extract from the Control Operation Archive.