BANNER S22 Indicator Process Data Function Instructions

S22 Indicator Process Data Function
March 19th, 2026

This document covers the installation and use of a function for Siemen’s TIA Portal software package. This function handles cyclic IO-Link Process Data Out to a Banner S22 Indicator light via an IO-Link Master from a Siemens PLC. The function covers parsing and display of the S22 Indicator sensor Process Data Out.

Components
Banner S22 Library v16.zal16

There are two methods for the process data. The first is used when creating a connection to Banner’s IO-Link masters. The second set of instructions are for systems using other manufacturer’s IO-Link masters.

Installation Instructions

1. Open a project.
2. Go to the Open Global Library option in the Libraries tab in TIA Portal v16 or greater.
3. Switch the “Files of type” to Compressed libraries. Go to the location of the compressed library.
4. Press the Open button and the library will be uncompressed and opened.
5. The library is now accessible in the Libraries tab in v16 or greater.

Setup of S22 Indicator with a Banner DXMR

1. Go to Device and Networks to configure the DXMR. Add the DXMR if it has yet to be added to the system.
2. Add Banner IO-Link Master Info to Slot 1. This sets the DXMR for IO-Link mode.
3. Open the IO-Link Generic Devices and select the proper module. The 8/8 byte is required for K30 Pro Touch. Make note of the I address for the Slot 2 which represents Port 1. Slot 2 starts are 1 for outputs. The other number needed is I3. The data for the port start at that point (I3). The previous two bytes Port Control.
4. Drag the necessary tag from
   Banner_Specialized_Data_Types. The tag used in this example is “Banner_8out”.
5. Drag the necessary files from the S22 Indicator Folder.
   a. Banner_S22_4State, Banner_S22_Advanced,
   Banner_S22_Multi, Banner_S22_PDO, and
   Banner_S22_PDOraw to the PLC Data Types area.
   b. Move Banner_S22_PD to the Program Blocks area.
6. Go to PLC Tags. Create two tags. In this example, Tag table_1 was created, then the tag “S22PT IOLM1 01 PDO” was created using a Data Type of “Banner_8out”. This naming convention calls out the type of device in question as well as the specific IO-Link Master and port number where the sensor is connected. A different IO-Link Master might be named IOLM2 or IOLM3, for instance, and other specific sensors may be connected to different port numbers. The “Q” address found in step 2 (%Q1) is tied to this new tag. The tag that represents the raw data is “S22PT IOLM1 01 oRaw” and uses the “Q” address found in step 2 (%Q3).
7. Go to Program blocks. Add a new Data block if necessary. In this example the new data block is named “db”.
8. In the new data block, create a new tag to represent the parsed Process Data Output for our S22 Indicator. The tag name again calls out the type of sensor, the IO-Link Master, and the port number. Use the data type “Banner_S22_PDO” for the new tag.
9. Add the “Banner_S22_PD” function to an OB ladder. Link the “PDO” to the raw process data variable from step 6. The tag name again calls out the type of device, IO-Link Master, and the port number. Use the variable called “S22PT IOLM1 01 oRaw” in this example. The “S22” needs to be linked to the variable created in step 8. It was called “S22 IOLM1 01 PD” for this example.
   The last variable, “Operational Mode”, allow the function to correctly interpret the Process Data Out. In the case of the S22 Indicator, there are four user-selected modes for the Process Data Out. This function needs to know what choice has been made in the S22 Indicator for this Operational Mode variable.
   There are two ways to achieve this goal. We can simply type in the correct number for Operational Mode (see Fig. 1), or we can link this S22 Process Data Function to the S22 Parameter Data Function Block (see Fig. 2). See Appendix A for more information about K30 Pro Touch Process Data Out.NOTE: if you type in the incorrect number (i.e. it does not match the tower light’s current Operational Mode configuration) you will get incorrectly displayed Process Data Out information.
   Operational Mode: the options here are “0” (Multi Color Mode), “1” (Four State Mode), and “2” (Advanced Mode); where the entire tower light behaves as a level indicator). The default is “2”.
10. The final step is to configure the IO-Link output control. This is done by sending a 1 to Port Control and a 2 to Port Config. Both parameters are part of the tag created in step 6 “S22PT IOLM1 01 PDO”.
11. Process Data Setup is complete.
12. Compile and download the configuration to the PLC, then go online. Open the “db” data block and click Monitor all. The S22 Indicator can be controlled now.

Setup of S22 Indicator with other IO-Link Masters

1. The Banner S22 library will now be in the Global Library List. Expand the Master copies section.
2. Drag Banner_S22_PD to the Program Blocks area under your PLC.
3. Drag Banner_S22_4State, Banner_S22_Advanced, Banner_S22_Multi, Banner_S22_PDO, and Banner_S22_PDORaw to the PLC Data Types area under your PLC.
4. Go to Devices and networks to configure the system as necessary. Below is an example of what a configuration might look like. This example shows 5 different IO-Link Masters connected to the same PLC.
5. Click on the relevant device and configure the IO-Link Master as necessary. Refer to the documentation for the IO-Link Master. Recall that a S22 Indicator requires 6 bytes of space for the Process Data Out.
6. Record the “Q” addresses where this S22 Indicator Process Data is to be stored, as these addresses will be required in the next step. In this example, 8 bytes of Process Data Out for port 1 on the IO-Link Master will be stored starting at Q68.
7. Go to PLC Tags. Add a new tag table, then create a new tag to represent the raw Process Data Out to be sent from the IO-Link Master. In this example, Tag table_1 was created, then the tag “S22PT IOLM1 01 PDO” was created using a Data Type of “Banner_S22_PDORaw”. This naming convention calls out the type of sensor in question as well as the specific IO-Link Master and port number where the sensor is connected. A different IO-Link Master might be named IOLM2 or IOLM3, for instance, and other specific sensors may be connected to different port numbers. The “Q” address found in step 6 is tied to this new tag.
8. Go to Program blocks. Add a new Data block if necessary. In this example the new data block is named “Banner IO-Link Data”.
9. In the new data block, create a new tag to represent the parsed Process Data Out for our S22 Indicator. The tag name again calls out the type of sensor, the IO-Link Master, and the port number. Use the data type “Banner_S22_PDO” for the new tag.
10. Add the “Banner_S22_PD” function to an OB ladder. Link the “PDO” to the raw Process Data Out variable from step 7. Link “S22 PD” to the parsed Process Data variable from step 9.
    The last variable, “Operational Mode”, allows the function to correctly interpret the Process Data Out. In the case of the S22 Indicator, there are five user-selected modes for the Process Data Out. This function needs to know what choice has been made in the S22 Indicator for this Operational Mode variable.
    There are two ways to achieve this goal. We can simply type in the correct number for Operational Mode (see Fig. 1), or we can link this S22 Indicator Process Data Function to the S22 Parameter Data Function Block (see Fig. 2). See Appendix A for more information about S22 Indicator Process Data Out.NOTE: if you type in the incorrect number (i.e., it does not match the S22’s current Operational Mode configuration) you will get incorrectly displayed Process Data Out information.
11. Process Data setup is complete.
12. Compile and download the configuration to the PLC, then go online. Open the “Banner IO- Link Data” data block and click Monitor all.
13. Process Data is broken up into three different types. Operational Modes controls which of three types is used to parse the raw byte data.

Appendix A

S22 Indicator Process Data
The S22 Indicator has 8 bytes of Process Data Out. There are three modes for displaying this data, as shown below. This Process Data is mapped to a specific group of PROFINET addresses. This function intelligently parses this Process Data into its component pieces.

The first is mode 0, “Multicolor”.

The next mode, “1”, is “Four State Full Logic”.

Mode 2 is “Advanced”.