DISOCONT Tersus – PROFINET IO Guide

1 DISOCONT Tersus PROFINET configuration

▾

Protocol and communication parameters

P18.01 = PROFINET IO
P18.02 = timeout monitoring (e.g. 10 s)
P18.03 = event cyclic communication (e.g. A)
P18.04 = event acyclic communication (e.g. W1)
P18.05 = keyboard mode check = YES
P18.24 = Configuration = PARA_ID_6_15 (PPO type PARAID615)
P18.25 = event IP address conflict (e.g. W2)

Network settings

Assign a fixed IP address and subnet mask according to the controller network design.
Connect PROFINET cable to the designated port and verify link/activity LEDs.
Use the fieldbus recorder to verify that PROFINET telegrams are received and transmitted.
Create parameter and communication backups for documentation.

Objective: DISOCONT Tersus is configured as a PROFINET IO device and actively exchanges cyclical telegrams.

2 Controller configuration (example: TIA Portal)

▾

Device integration

Install the DISOCONT Tersus GSDML file in the engineering system.
Add DISOCONT Tersus as a PROFINET IO device in the project device network.
Connect the controller PROFINET interface to the DISOCONT PROFINET interface in the network view.

IP address and device name

Set the PROFINET interface IP address to match the IP configured in DISOCONT Tersus.
Assign a unique PROFINET device name for the DISOCONT device.
Download the hardware configuration to the controller and assign the device name online to the physical device.

Objective: the engineering system recognizes the DISOCONT Tersus as a PROFINET IO device with correct IP and device name and the device appears without PROFINET errors.

3 PROFINET status and diagnostics

▾

Online status

Go online with the controller and open the device diagnostics for the DISOCONT Tersus.
Verify that the PROFINET device status is OK (no red or diagnostic symbols).
Check for any PROFINET alarms or diagnostics (IP mismatch, device name mismatch, module mismatch).

Basic troubleshooting

Confirm that IP address and subnet match between controller configuration and DISOCONT parameters.
Confirm that the PROFINET device name configured in the controller has been assigned to the physical device.
Check that the configured modules/slots in the controller match the telegram format and configuration used in DISOCONT Tersus.

Objective: ensure stable PROFINET IO connection before testing process data.

4 PARAID615 – telegram structure (concept)

▾

General information

Configuration PARAID615 corresponds to a semi-variable PPO type with parameter range (PKW) and process data range (PZD). The structure is based on the PROFIdrive concept with:

PKW range (optional): parameter read/write (PKE, IND, PWE1, PWE2).
PZD range: cyclical process data for control words, status words, setpoints and measured values.

For PARAID615:

6 preset IDs (default values) are sent from the controller to DISOCONT Tersus.
15 read IDs are returned from DISOCONT Tersus to the controller.

Default values (controller → DISOCONT)

Default values are 4‑byte values (data double words, DDW) identified by command or default‑value IDs. Typical examples:

ID (hex)	Description	Comment
0x0140	Command 0405 – Clear events and release	Contains the clearance bit for connection monitoring.
0x0160	Command 0607 – General command	Can be used for additional command functions.
0x0180	Command 0809 – Keyboard mode	Used for keyboard mode control.
0x0100	Command 0001 – Select material data set	Selection of material data set (MDP set number).
0x0250	Serial setpoint	Main feedrate setpoint (FLOAT).
0x0252	Serial batch setpoint	Batch amount setpoint (FLOAT).

At least one default value ID must be non‑zero. If all default value IDs are zero, event SY08 (event cyclic communication) is triggered and default values are not processed.

5 Status and measured values (DISOCONT → controller)

▾

Mandatory IDs

For variable formats, the following IDs are always returned by DISOCONT Tersus regardless of the order list:

ID (hex)	Description	Direction
0x02F0	Status 0203 – overall status word	DISOCONT → controller
0x0750	Actual value – main measured value (e.g. feedrate)	DISOCONT → controller

Typical additional IDs

The order list can be configured to return further status and measured values. Commonly used IDs include:

ID (hex)	Description	Typical use
0x0310	Status 0405	Additional status information.
0x0330	Status 0607	Further status word for extended diagnostics.
0x0610	Status 5253 – highest priority event	Bit‑coded event class and group, including warning and alarm information.
0x0650	Status 5657 – activated material	Indicates the active material / material data set.
0x0752	Totalizer 1	Cumulative mass totalizer (FLOAT).
0x0754	Totalizer 2	Second totalizer value (FLOAT).
0x075E	Speed	Speed of the feeder (FLOAT).
0x0760	Fill weight	Fill weight value (FLOAT).
0x0762	BIN fill weight	Bin‑related fill weight (FLOAT).
0x0766	Setpoint (echo)	Setpoint as applied within DISOCONT Tersus (FLOAT).
0x0768	Batch actual value	Current batch mass (FLOAT).
0x076A	Batch residual amount	Remaining batch mass to reach setpoint (FLOAT).
0x0770	Deviation	Deviation between actual value and setpoint (FLOAT).

The exact selection and sequence of IDs is defined in the DISOCONT Tersus configuration (order list). The controller evaluates the returned data according to this agreed mapping.

6 IO mapping in the controller

▾

Process image

Insert the required PROFINET IO modules for DISOCONT Tersus according to the GSDML and configuration (PARAID615).
Note the assigned input and output address ranges in the process image (I/Q addresses).
Create symbolic tags in the controller project that map to these addresses (control words, status words, setpoints, measured values).

Testing

Monitor status and measured values in the controller using watch or monitoring functions.
Verify that changes on DISOCONT Tersus (e.g. simulated values) are reflected in the input data.
Verify that valid control commands and setpoints written from the controller are accepted and executed by DISOCONT Tersus.

The detailed PLC program structure is project‑specific. The information in this guide supports the mapping and interpretation of the DISOCONT Tersus process data.