PLC table – Manage and edit signals

1. Two windows with different purposes

PLC table in the top bar opens the communication overview for searching, filtering and inspecting signals. Edit table opens the row-and-cell editor.

Symbols connect readable names such as Anlage_Sollwert to a device, address and data type. Displays, inputs and protocols use these assignments. The table is not a live display of all current measurements.

2. Search, filter and select

Search symbol

Search by name, address, data type or description, for example Anlage_Sollwert or 40007.

PLC / Device, Data type, Access

Restrict the displayed entries. Check search text and filters if a known signal is missing.

Sorting

Sets display order; the screenshot uses ascending address.

16 of 16 symbols

Shows visible entries versus the total. Filtering does not delete symbols.

Symbol information

Select an entry on the left to show its information on the right. None is selected in the screenshot.

Driver controls depend on selection and configuration. Communication drivers are hidden or unavailable in the demo, so its controls may differ from this image. See driver settings. Object guides already explain assigning signals through Select symbol.

3. Import and deletion in the overview

Import XML

Temporarily disabled from version 2.61.510 until tested and approved. The grey button is intentional; administrator rights do not override it.

Import CSV

Reads symbol definitions from CSV. Back up the project first and check resulting counts and assignments. This is a different workflow from Open CSV in the editor.

Edit table

Opens the editor described below.

Remove entry

Removes the selected symbol after confirmation.

Delete all

Clears the entire symbol list after confirmation, not merely the filtered view.

Before deleting, check which objects and protocols use the signal. Removing its definition can affect their assignments. Deleting a symbol is not a command to delete a PLC value.

4. Use the table editor

Each row defines a signal. Double-click to edit a cell. The bottom horizontal scrollbar reveals additional columns to the right.

New

Starts a new empty table after confirmation. Use + Row to add just one signal.

+ Row

Adds a row. Complete required fields and appropriate connection details.

Duplicate

Helps create similar signals. Check and change the symbol and address afterwards; duplicate entries can fail validation.

Delete selection

Removes selected entries. Check the selection first.

Search / Replace / Replace all

Finds or replaces table contents. Consider the scope of Replace all and check affected devices, names and addresses afterwards.

Displayed shortcuts include Ctrl+F/H for search/replace, Ctrl+A/C/X/V/Z/Y/S and Delete. Check the selection carefully when editing multiple cells.

5. Understand the columns

No.

Row number for navigation and validation messages.

PLC / Device

Configured device name, here Modbus_Testserver.

Symbol

Readable signal name, such as Anlage_Sollwert.

Address

The signal address for its assigned participant. Do not copy example addresses without checking.

Simulation value

A configured example/simulation value, not proof of a current reading from a real PLC.

Data type / Length

Determine data interpretation and length. They must match the signal and driver; changes are not merely formatting.

Unit / Description

Clarify meaning. A unit such as °C does not automatically scale raw readings.

IP address / Endpoint, Port, Unit-ID

Identify the communication target. The example uses 127.0.0.1, port 502 and Unit-ID 1. 127.0.0.1 refers to the local computer; these test-server values are not a template for an arbitrary real machine.

Additional columns to the right

Register type, function code, access, byte order, word order, driver and validation. These govern data interpretation and use and must match the device specification.

6. Read the Anlage_Sollwert example

Row six shows Modbus_Testserver → Anlage_Sollwert → 40007, simulation value 80, data type UINT16 and length 1. Its description is “Sollwert Anlage”; no unit is set.

This is the signal used in the Anlage_Sollwert protocol example. The 80 is a simulation value, not a confirmed current PLC setpoint.

To change a description, double-click its cell, edit, finish the entry and validate. After changing device, symbol or address, also check associated project objects.

7. Open CSV, save and close

Open CSV replaces the editor's current contents with the selected CSV. Back up needed data first. The opened source does not automatically become the save destination; check the destination hint.

Save writes CSV to the current destination or opens a chooser if none exists. Save as selects another CSV destination. These save the table, not the complete project.

Important: the editor works on the project's symbol list. Close is not Cancel and does not discard changes. On returning after edits, the project symbol CSV is updated and the project is marked changed. Then save the project to preserve its complete state.

8. Validate and resolve errors

Validate table checks required fields, connection details, duplicate symbol names per device, duplicate addresses for the same participant/register area and overlapping Modbus registers. Device, symbol, address and data type are required.

Messages identify the affected row. Correct it and validate again. Invalid entries can block saving and closing. “Table is valid” confirms the implemented table checks, not PLC connectivity or correct real-world signal assignments.

Before testing real communication, save a backup, check destination and access mode, and compare known values. Distinguish simulated from real measurements. Restrict Edit PLC table and project-saving rights to responsible roles; see permissions.

9. Bundled examples in the project folder

The project includes prepared CSV examples under Kommunikation/Beispiele/. They demonstrate signal definitions for the three communication types, so an exercise table does not have to be created entirely by hand.

01-Modbus-TCP/Kommunikation-Modbus-TCP.csv

Direct Modbus TCP examples including a Freigabe coil, Endschalter input and Temperatur_Ist register. The example connection points to the local Modbus_Testserver.

02-Siemens-S7-Moka7/Kommunikation-Siemens-S7.csv

S7 examples with names and addresses, such as Anlage_Bereit at M0.0 and Motor_Laeuft at M0.1.

03-OPC-UA/Kommunikation-OPC-UA.csv

OPC UA examples with Node IDs, including Machine1.Running at ns=2;s=Machine1.Running, speed and tank level. The example endpoint points to the local computer.

Beispiele/SCHEMA.txt describes the folder structure. Additional introductory information is available one level above in Kommunikation/LIESMICH-Kommunikation.txt.

First save the project under its name

Sequence: name and save the project once → import the example CSV → validate the table → save the project again. This establishes the project name and folder and associates the imported symbols with the correct project.

The project symbol table is stored as Kommunikation/<project name>_SYMBOLIK.csv. For “Mein_erstes_Projekt”, it is Mein_erstes_Projekt_SYMBOLIK.csv. Templates under Kommunikation/Beispiele/ retain their original filenames; they are not renamed after the project.

This means Save project in the top bar, not merely Save in the table editor. Save the project after importing too. A Modbus simulator launched by PamaGlawe uses the project symbol file rather than the original file in the examples folder.

Use an example

1. Use a separate practice project or back up your existing project first.
2. Choose PLC table → Import CSV and navigate to the project's Kommunikation → Beispiele folder.
3. Open the appropriate numbered subfolder and select its CSV. Do not indiscriminately import all three variants for the same exercise.
4. Inspect the imported symbols, use Edit table → Validate table and save the project.
5. Use Select symbol in a suitable object to assign one of these signals. For communication testing, the selected driver and test server must also match the template.

Alternatively, use Open CSV in the table editor. This replaces its current contents. Preserve the supplied examples as starting points and use Save as for your own modified file, then save the project.

Demo: Example files illustrate the table structure but do not unlock hidden communication drivers. Use the simulation features available in your demo. Importing CSV alone does not start a real PLC connection.

Templates are not plant configurations: Local test addresses, names, access modes and simulation values must match the exercise or actual machine. 127.0.0.1 refers to the local computer. Do not switch to real controllers or mix examples into production symbol definitions without checking.