DISOCONT Tersus ↔ Siemens PLC (PROFINET)

Tap a step to expand/collapse the details. Use this as a quick checklist on site.

Step 1 Prepare DISOCONT Tersus

▾

Parameters (Menu P18)

P18.01 = PROFINET IO
P18.24 = PARA_ID_6_15 (or project-specific PARA_ID)
P18.02 = timeout (e.g. 10 s)
P18.03 = event cyclic comm (e.g. A)
P18.04 = event acyclic comm (e.g. W1)
P18.05 = check in keyboard mode = YES
P18.25 = event IP address conflict = W2

Network

Set IP address to match PLC network (e.g. 192.168.31.54/55).
Check PROFINET cable and link LEDs.
Use fieldbus recorder to confirm telegrams in/out.
Save parameter backup and fieldbus logs.

Goal: DISOCONT is configured and talking on the network.

Step 2 Prepare TIA hardware

▾

GSDML & Device

Install DISOCONT GSDML in TIA (Options → Manage GSD).
Add DISOCONT as a PROFINET IO device in “Devices & networks”.
Connect PLC PROFINET port to DISOCONT in network view.

IP & Name

Open DISOCONT device properties → PROFINET interface.
Set IP address to match DISOCONT IP.
Set a PROFINET device name (e.g. DISO_G400).

Goal: PLC project knows the DISOCONT device with correct IP and name.

Step 3 Get PROFINET “green”

▾

Online

Compile and download hardware configuration to PLC.
Scan for PROFINET devices and assign device name to DISOCONT.
Go online and check DISOCONT status in TIA diagnostics.

Troubleshooting

If device is red: check IP, device name, GSDML, module layout.
Check for diagnostics in “Online & diagnostics”.

Goal: DISOCONT appears as OK/green in TIA (no PROFINET errors).

Step 4 Map & test IO data

▾

IO configuration

Insert IO modules/telegram layout according to Qlar manual.
Note input/output address ranges (I/Q) assigned by TIA.
Create PLC tags mapped to these addresses.

Testing

Use a watch table to monitor inputs from DISOCONT.
Change something on DISOCONT and confirm PLC values change.
Write outputs (control words) from PLC and verify DISOCONT reaction.

Goal: PLC and DISOCONT exchange meaningful process data (setpoint, status, etc.).