IO Lists in PLCCreator

PLCCreator

IO Lists in PLCCreator

Select Section ...
1. Introduction
2. Device IO List
3. Signal IO List
4. IO Lists and Architectures

1.
Introduction

IO lists are user-created files that play a fundamental role in PLC creation. These lists enable PLCCreator to automatically generate:

  • PLC hardware configuration
  • Signal-to-IO module assignment
  • PLC tags with addresses and/or aliases

PLCCreator supports two IO list formats:

Device IO List (more advanced) or Signal IO List (simpler structure)

Key Differences:

Device IO List

  • References Asset Library and Library Blocks
  • Error-Resistant – Automatically retrieves Block Signals
  • Part of our advanced Asset Oriented Programming - AOP support
  • More features and automation

Signal IO List

  • Uses Signal Type column
  • Simpler structure (fewer columns)
  • Easier to create manually
  • Faster processing

IO List Structure

As shown inFigure 1, all IO lists contain two main sections:

Header Section

Contains metadata needed for PLCCreator to process the data section:

  • IO list type identification
  • Column headers

Data Section

Contains the actual signal/device data:

  • Signal details (Signal IO List)
  • Device references (Device IO List)
Figure 1: IO List Basic Structure
Figure 1: IO List Basic Structure

2.
Device IO List

The PLCCreator Device IO List is a streamlined version of an Instrument Index, containing only PLC creation relevant columns.

An Instrument Index is a master document that catalogs all instruments in a system, providing key details like:

  • Tag/Identifier
  • Instrument Type
  • Location
  • Manufacturer/Model

* Format and naming may vary per company or project requirements.

Example: Instrument-Index-Example.xlsx

Figure 2: Instrument Index Example
Figure 2: Instrument Index Example

PLCCreator Device IO List Structure

In PLCCreator, the Device IO List for Single Rack Architecture simplifies this to 4 key columns:

  1. 1. Name
  2. 2. Description
  3. 3. Asset Library
  4. 4. Library Block

Must comply with column requirements for proper processing.

Mapping Instrument Index to PLCCreator

Table 1 shows how standard Instrument Index columns correlate with PLCCreator's Device IO List structure:

PLCCreator Device IO List Instrument Index Column
Name "Tag" or unique device identifier
Description "Description"
Asset Library Not in Instrument Index. PLCCreator-specific reference.
Library Block

"Instrument Type"

Table 1: Instrument Index ↔ PLCCreator Device IO List Column Mapping

Note:

  • "Asset Library" is not part of Instrument Index documents—it's PLCCreator-specific.
  • Thephysical IO signalsof the "Library Block" in itsBlock Signaltable, must match the "Instrument Type" IO signals.

Conversion Example

Figure 3 shows the Instrument Index from Figure 2 converted to a Device IO List for Single Rack Architecture :

DIOLSRA-from-Instrument-Index.xlsx
Figure 3: Device IO List - Converted Instrument Index from Figure 2 into Device IO List for Single Rack Architecture
Figure 3: Device IO List - Converted Instrument Index from Figure 2 into Device IO List for Single Rack Architecture

This example uses: Siemens Open Library with these blocks:

Learn More:

3.
Signal IO List

The PLCCreator Signal IO List is a streamlined version of an Instrument IO List or Machine IO List, containing only PLC creation relevant columns.

An Instrument IO List details all input/output signals for instruments, including:

  • Signal Tag/Identifier
  • Signal Type (Analog/Digital)
  • Range/Units
  • Connection Details

* Typically derived from the Instrument Index , but may be standalone. Formats vary by company/project.

Example: Instrument-IO-List-Example.xlsx

Figure 4: Instrument IO List Example
Figure 4: Instrument IO List Example

PLCCreator Signal IO List Structure

In PLCCreator, the Signal IO List for Single Rack Architecture simplifies this to 3 key columns:

  1. 1. Name
  2. 2. Description
  3. 3. Signal Type

Must comply with column requirements for proper processing.

Mapping Instrument IO List to PLCCreator

Table 2 shows how standard Instrument IO List columns correlate with PLCCreator's Signal IO List structure:

PLCCreator Signal IO List Instrument IO List Column
Name "Tag" or unique signal identifier
Description "Description"
Signal Type "Signal Type"
Table 2: Instrument IO List ↔ PLCCreator Signal IO List Column Mapping

Note:

•

Signal type information may be distributed across multiple columns in source documents (e.g., separate columns for signal category, range, and units).

•

For PLCCreator processing, signal types must match either:

‣
The official Signal Type/Hardware Compatibility Table
‣

Predefined values in the Signal IO List template dropdown

Conversion Example

Figure 5 shows the Instrument IO List from Figure 4 converted to a Signal IO List for Single Rack Architecture :

SIOLSRA-from-Instrument-IO-List.xlsx
Figure 5: Signal IO List - Converted Instrument IO List from "Figure 1" into "Signal IO List for Single Rack Architecture"
Figure 5: Signal IO List - Converted Instrument IO List from "Figure 1" into "Signal IO List for Single Rack Architecture"

Learn More:

4.
IO Lists and Architectures

PLCCreator enables you to build PLC systems using 3 distinct architectural models:

  1. Single Rack
  2. Single Fieldbus
  3. Multiple Fieldbuses

Each architecture model requires specific IO list columns to properly configure the PLC hardware.

  1. Single Rack Architecture

    This is the base architectural model and its IO lists, with their columns, were introduced earlier in the sectionsDevice IO ListandSignal IO List

    The purpose of these columns is to create theIO moduleswithin the PLC rack.
    Figure 6: IO List Columns for Single Rack Architecture
    Learn More:

  2. Single Fieldbus Architecture

    The IO lists for this model have Single Rack Architecture columns, plusRack Creation Columns:

    • "Hardware Platform"
    • "Group"
    Figure 7: IO List Columns for Single Fieldbus Architecture
    Learn More:

  3. Multiple Fieldbuses Architecture

    The IO lists for this model have the Single Fieldbus Architecture columns, plus theFieldbus Creation Columns:

    • "Fieldbus"
    • "Comm Protocol"
    Figure 8: IO List Columns for Multiple Fieldbuses Architecture
    Learn More:

On Figure 9 is shown an overview of the IO list columns for all PLC architectures:

Figure 9: Overview of IO List Columns for each PLC Architecture
Figure 9: Overview of IO List Columns for each PLC Architecture