BANNER CTL50 Pro Process Data Function Instruction Manual

BANNER-LOGO

BANNER CTL50 Pro Process Data Function

BANNER-CTL50-Pro-Process-Data-Function-PRODUCT

Overview

This manual explains how to install and use the CTL50 Pro Process Data Function in TIA Portal to handle cyclic IO-Link Process Data Out for a Banner CTL50 Pro light via a Siemens IO-Link master, including parsing and display of the CTL50 Pro process data.

Specifications

Banner library Banner CTL50 Library v16.zal16
Supported TIA Portal version v16 or greater (Global Library)
IO-Link Process Data size (CTL50) 32/32 bytes required for CTL50 (32 bytes of space for process data)
Port/Q address guidance (example) Slot 2 represents Port 1; Slot 2 starts at %Q1 for outputs; port data starts at %Q3; previous two bytes are Port Control
Process data modes (CTL50 Pro) 7 different process data modes; default mode is Segment Override (2)
Segment control capability Segment Array supports control of up to 20 segments
Parameter tag example data type Banner_CTL50_PDO
Example segment array mapping SegmentArray[1..20] of USInt: 0=Off, 1=On, 2=Flash, 3=Animation

Quick Setup / Use

  1. Open a project in TIA Portal v16 or greater.
  2. In the Libraries tab, open Open Global Library, set Files of type to Compressed libraries, open the compressed library, and ensure it appears in the Libraries list.
  3. Configure the CTL50 device: in Device and Networks, add the DXMR/IO-Link master device if needed, then add the Banner IO-Link Master Info to Slot 1 (IO-Link mode).
  4. Select the CTL50 module in IO-Link Generic Devices (32/32 byte is required). Note the Q address for Slot 2 (Port 1), where output process data starts at %Q3 in the provided example.
  5. Add tags/data types: drag the needed tags from Banner_Specialized_Data_Types (example tag: Banner_32out for full raw process data + port status) and move the PLC data types and required PLC data type files into TIA Portal.
  6. Create two PLC tags: one for the full raw process data structure (example uses Banner_32out), and one raw output tag that uses the %Q address for the port data (example: outRaw using %Q3).
  7. Add a data block (e.g., db) and create a parsed process data tag using data type Banner_CTL50_PDO (or Banner_CTL50Pro_PDO for the “Select with other IO-Link Masters” flow).
  8. Add the appropriate function block to an OB ladder, and link its PDO input to the raw process data tag; link its parsed CTL50 PD / CTL50 Pro PD output to the parsed tag.
  9. For CTL50 with the Banner DXMR example: configure IO-Link output control by sending 1 to Port Control and 2 to Port Config (both are part of the PDO tag created in the parsed setup).
  10. Compile, download, go online, and monitor the created data block to control the CTL50 select.

Process Data Function

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

Components

  • Banner CTL50 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 is for systems using other manufacturers’ 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 later.BANNER-CTL50-Pro-Process-Data-Function-FIG-1
  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 CTL50 with a Banner DXMR

  1. Go to Device and Networks to configure the DXMR. Add the DXMR if it has not yet been 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 32/32 byte is required for CTL50. Make note of the Q address for Slot 2, which represents Port 1. Slot 2 starts at Q1 for outputs. The data for the port starts at that point (Q3). The previous two bytes are Port Control.BANNER-CTL50-Pro-Process-Data-Function-FIG-2
  4. Drag the necessary tag from Banner_Specialized_Data_Types. The tag used in this example is “Banner_32out”. This tag represents the full raw process data along with port status information.
  5. Drag the necessary files from the Process Data folder.
    • a. Move all the files in the PLC Data Types to the PLC Data Types area in TIA Portal.
    • b. Move Banner_CTL50_Adv_PD, Banner_CTL50_LED_PD, Banner_CTRL50_Over_PD, and Banner_CTL50_PD to the Program Blocks area.
  6. Go to PLC Tags. Create two tags. One tag is for the full data structure, while the second creates a tag to represent the raw Process Data from the IO-Link Master. In this example, Tag table_1 was created, and then the tag “CTL50 IOLM1 01 PDO” was created using a Data Type of “Banner_32out”. This naming convention calls out the type of device in question as well as the specific IO-Link Master and port number to which 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 3 (%Q1) is tied to this new tag. The second is “CTL50 IOLM1 01 outRaw” and uses the “Q” address found in step 2 (%Q3). This is the tag that will be used in the Function block.BANNER-CTL50-Pro-Process-Data-Function-FIG-3BANNER-CTL50-Pro-Process-Data-Function-FIG-4
  7. Go to Program blocks. Add a new Data block if necessary. In this example, the new data block is named “db”.BANNER-CTL50-Pro-Process-Data-Function-FIG-5
  8. In the new data block, we will create a new tag to represent the parsed Process Data In for our CTL50. The tag name again calls out the type of sensor, the IO-Link Master, and the port number. Use the data type “Banner_CTL50_PDO” for the new tag.BANNER-CTL50-Pro-Process-Data-Function-FIG-6
  9. Add the “Banner_CTL50_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. The variable was called “CTL50 IOLM1 01 outRaw” in this example. The “CTL50 PD” needs to be linked to the variable created in step 8. It was called “CTL50 IOLM1 01 PD” for this example.BANNER-CTL50-Pro-Process-Data-Function-FIG-7
  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, “CTL50 IOLM1 01 PDO”.BANNER-CTL50-Pro-Process-Data-Function-FIG-8
  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 CTL50 Select can be controlled now.
  1. The Banner CTL50 Library will now be in the Global Library List. Expand the Master copies section. The CTL50 folder contains elements for both Process Data and Parameter Data connections to a CTL50 device.
  2. Drag Banner_CTL50Pro_Adv_PD, Banner_CTL50_LED_PD, Banner_CTL50_Over_PD, and Banner_CTL50_PD to the Program Blocks area under your PLC.
  3. Drag all items in the PLC Data Types folder 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.BANNER-CTL50-Pro-Process-Data-Function-FIG-9
  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 CTL50 requires 32 bytes of space for the Process Data.
  6. Record the “Q” address where this CTL50 Process Data is to be stored, as the address will be required in the next step.BANNER-CTL50-Pro-Process-Data-Function-FIG-10
  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 to the IO-Link Master. In this example, Tag table_1 was created, and then the tag “CTL50 IOLM1 01 outRaw” was created using a Data Type of “Banner_CTL50_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.BANNER-CTL50-Pro-Process-Data-Function-FIG-11
  8. Go to Program blocks. Add a new Data block if necessary. In this example, the new data block is named “db”.
  9. In the new data block, create a new tag to represent the parsed Process Data In for our CTL50 Pro. The tag name again calls out the type of sensor, the IO-Link Master, and the port number. Use the data type “Banner_CTL50_PDO” for the new tag.BANNER-CTL50-Pro-Process-Data-Function-FIG-12
  10. Add the “Banner_CTL50Pro_PDO” function to an OB ladder. Link the “PDO” to the raw Process Data variable from step 7. Link “CTL50 Pro PD” to the parsed Process Data variable from step 9.BANNER-CTL50-Pro-Process-Data-Function-FIG-13
  11. Process Data setup is complete.

Using CTL50 Process Data

  • The CTL50 has 7 different Process Data Modes. The default mode is Segment Override (2). Set the unit to the correct mode for your application (Parameter Data controls this).
  • The Override mode allows for each segment to be controlled individually. The Segment Array allows for control of up to 20 segments. Parameter Data is used to configure these segments. Use Advanced mode for full control of the segments.BANNER-CTL50-Pro-Process-Data-Function-FIG-14

Troubleshooting

  • Library does not appear in TIA Portal: confirm you set Files of type to Compressed libraries in Open Global Library, then reopen the compressed library so it uncompresses and becomes available in the Libraries tab.
  • Process data not aligned / incorrect addressing: verify the Q address mapping you recorded for the CTL50 port (example: Slot 2 for Port 1 starts at %Q1, and port data starts at %Q3; the previous two bytes are Port Control).
  • Wrong module size selected: ensure the selected IO-Link Generic Device module uses the required 32/32 byte size for CTL50.
  • Function block not producing expected parsed outputs: confirm you linked the function block’s PDO to the correct raw process data variable/tag and linked the parsed output (CTL50 PD / CTL50 Pro PD) to the parsed data structure tag in your data block.

Documents / Resources

PDF thumbnailCTL50 Pro Process Data Function
Instruction Manual · CTL50, CTL50 Pro, CTL50 Library v16.zal16, process data, IO-Link

References

Ask a Question

Use this section to ask about setup, compatibility, troubleshooting, or anything missing from this manual.

Ask a Question

Ask about setup, compatibility, troubleshooting, or anything missing from this manual. Name and email are optional.