Text signals are analog signals of the STRING or STRING[x] type. STRING[x] is a text (string) with a maximum length of x characters.

Text signals can be transmitted to ibaPDA through various interfaces. Depending on the type of interface, the text signals are configured in the normal modules or in separate text modules.

A text signal can contain the entire source text or parts of it. The information of a text can be split into several sections in the I/O Manager, whereby each section shows a text signal and can be processed as individual pieces of information.

A text containing a lot of different information may be split up into any number of text signals.

With some interfaces, a text can be split directly in the interface module. With other interfaces, another module Text splitter must be added to split a text. The newly created sections are configured in the same module as new text signals of the data type STRING or a numerical data type.

Text signals are used wherever numerical signals are used.

The start/stop index of the characters (for fixed text length) or different delimiters (for changeable text lengths) serve as criteria for splitting the text. In many cases, the JSON format can also be used.

Text signals that only contain numbers can be interpreted as a numerical value with or without decimal marks and can be used for calculations.

A text (signal) can contain up to 10,000 characters.

Every text signal can be enabled or disabled individually.

The different types of texts are classified by their source or the interface which is used for transmission.

Some of the interfaces depend on a corresponding release in the dongle.

Table Sources and interfaces for text signals

Text source

Note

TCP/IP text

UDP Text

The source text is transmitted as a TCP/IP telegram or UDP datagram to ibaPDA via the computer network. You can configure this in the I/O Manager under the node Text interface. In the TCP text or UDP text module, Analog tab, the source text with the STRING data type and the text signals derived from the source text with the STRING data type or a different data type are configured. For numerical data types, the conversion is carried out automatically.

A TCP text or UDP text module must be configured for each source text or telegram.

Serial text

The source text is transmitted via a serial interface to ibaPDA (COM1...COM4). You can set the configuration in the I/O Manager under the node Text interface. In the Serial text module Analog tab, the source text with the STRING data type and the text signals derived from the source text with the STRING data type or a different data type are configured. For numerical data types, the conversion is carried out automatically.

Depending on the source text or telegram, a module of the type Serial text must be configured.

File text

The source text is contained in a text file (.txt, .csv, .json) that is provided on a dedicated drive in a defined path (local or network) by an external system. You configure this in the I/O Manager under the node Text interface. In the File text module, Analog tab, the source text with the STRING data type and the text signals derived from the source text with the STRING data type or a different data type are configured. For numerical data types, the conversion is carried out automatically.

Depending on the source text or file, a module of the type File text must be configured.

Text creator

The source text is created on the ibaPDA server in the Text creator module, Text creation tab. It can be a typed in fixed text, the value of a signal or the text of another text signal. It can also be a combination of all three forms. Furthermore, XML and JSON data structures can be used for text creation. You can set the configuration in the I/O Manager under the node Virtual. In the Analog tab of the same module, you will then configure the derived text signals with the data type STRING or a different data type. For numerical data types, the conversion is carried out automatically.

Depending on the source text, a module of the type Text creator must be configured.

ibaQPanel text input

The text can be entered manually via a text input control of ibaQPanel. You can set the configuration in the I/O Manager under the node Virtual.

A module of the type ibaQPanel text input can receive several text signals. In the process, every text signal corresponds to exactly one text input control in the ibaQPanel view. Optionally, these text signals can be broken down into sections with a Text splitter module and, if necessary, converted into other data types.

Text shift register

Management of existing text signals in the form of a shift register. It provides the last 1 to 64 values of other text signals. The current value of a text signal is applied to the shift register with a trigger signal (rising edge). You can set the configuration in the I/O manager under the node Virtual.

The required text signals must have been created beforehand with the different modules.

OPC / OPC UA

The source text is transmitted to ibaPDA via the PC network (Ethernet TCP/IP) by an OPC or OPC UA server. You can set the configuration in the I/O Manager under the node OPC or OPC UA. In the OPC client or OPC UA client module, Analog tab, the source text is configured with the data type STRING. To divide the text from the OPC tag onto individual text signals, a Text splitter module must be configured per source text under the Virtual node.

B&R-Xplorer

The source text is transferred via the B&R-Xplorer interface (Ethernet TCP/IP) to ibaPDA. The processing of symbols of the data type STRING or WSTRING is supported. The configuration can be done in the I/O Manager in a B&R-Xplorer module. The source text is formed in the Analog tab from the symbols with a string data type.

To divide the source text into individual text signals, a module Text splitter must be configured under the Virtual node.

Codesys-Xplorer

The source text is transferred via the Codesys-Xplorer interface (Ethernet TCP/IP) to ibaPDA. The processing of symbols of the data type STRING or WSTRING is supported. This can be configured in the I/O manager in a Codesys V2 or V3 module. The source text is formed in the Analog tab from the symbols with a string data type.

To divide the source text into individual text signals, a module Text splitter must be configured under the Virtual node.

Logix-Xplorer

The source text is transferred via the Logix-Xplorer interface (Ethernet TCP/IP) to ibaPDA. The processing of symbols of the data type STRING is supported. This can be configured in the I/O manager in a Logix-Xplorer module. The source text is formed in the Analog tab from the symbols with a string data type.

To divide the source text into individual text signals, a module Text splitter must be configured under the Virtual node.

S7-Xplorer

The source text is transferred via the S7-Xplorer interface (Ethernet TCP/IP) to ibaPDA. The SIMATIC S7-300, S7-400, S7-1200, S7-1500 and WinAC controllers are supported.

The configuration can be done in the I/O Manager in a S7-Xplorer module. One or more source texts are formed in the Analog tab from S7 operands or symbols with the string data type.

To divide the source text into individual text signals, a module Text splitter must be configured under the Virtual node.

TwinCAT-Xplorer

The source text is transferred via the TwinCAT-Xplorer interface (Ethernet TCP/IP) to ibaPDA. The processing of symbols of the data type STRING or WSTRING is supported. The configuration can be done in the I/O Manager in a TwinCAT-PLC or BC/BX controller The source text is formed in the Analog tab from the symbols with a string data type.

To divide the source text into individual text signals, a module Text splitter must be configured under the Virtual node.

ibaVision

The source text is sent from ibaPDA output modules, which are configured in ibaVision, to ibaPDA. The text signals are configured in the I/O Manager under the node ibaCapture in so-called ibaVision text input modules. To divide the text into individual text signals, a module Text splitter must be configured under the Virtual node.

EtherNet/IP

The source text is transmitted to ibaPDA as a TCP/IP telegram via the EtherNet/IP connection.

The configuration can be done in the I/O Manager in an EtherNet/IP module. The source text is formed in the Analog tab from the symbols with the STRING data type.

To divide the text into individual text signals, a module Text splitter must be configured under the Virtual node.

Generic-TCP

The source text is transmitted to ibaPDA as a TCP/IP telegram via the Generic-TCP interface.

You can configure this in the I/O Manager in a Generic TCP module. The source text is formed in the Analog tab from the symbols with the STRING[32] data type.

To divide the text into individual text signals, a module Text splitter must be configured under the Virtual node.

Generic-UDP

The source text is transmitted to ibaPDA as a UDP datagram via the Generic-UDP interface.

This can be configured in the I/O Manager in a Generic unicast UDP, Generic multicast UDP, HiPAC Request or TwinCAT Request module. The source text is formed in the Analog tab from the symbols with the STRING[32] data type.

To divide the text into individual text signals, a module Text splitter must be configured under the Virtual node.

Modbus TCP Server

The source text is transmitted to ibaPDA as a TCP/IP telegram via the Modbus TCP server interface.

This can be configured in the I/O Manager in a Modbus Generic module. The source text is formed in the Analog tab from the symbols with the STRING[32] data type.

To divide the text into individual text signals, a module Text splitter must be configured under the Virtual node.

Reflective memory

The source text is transmitted via a Reflective Memory (RM) connection to ibaPDA. A special RM interface card is required for the ibaPDA computer.

Perform the configuration in the I/O Manager under the node Reflective Memory in a Reflective Memory Text module. The source text and the text signals with the data type STRING derived from the source text or a different data type are configured in the Analog tab of the module. For numerical data types, the conversion is carried out automatically.

ScramNet+

The source text is transferred to ibaPDA via a ScramNet+ connection. Therefore, a special interface card SC150 (manufacturer: Curtiss Wright) must be installed in the ibaPDA computer.

Perform the configuration in the I/O Manager under the node ScramNet+ in a ScramNet Text module. The source text and the text signals with the data type STRING derived from the source text or a different data type are configured in the Analog tab of the module. For numerical data types, the conversion is carried out automatically.

Sisteam TCP

The source text is transmitted to ibaPDA as a TCP/IP telegram via the Sisteam-TCP interface.

You can configure this in the I/O Manager in a Sisteam TCP Generic module. The source text is formed in the Analog tab from the symbols with the STRING[32] data type.

To divide the text into individual text signals, a module Text splitter must be configured under the Virtual node.

SIMADYN D

The source text is transmitted to ibaPDA via a connection with the SIMADYN-D system (CS12/13/14). This requires a special ibaFOB-SD/-SDexp interface card for the ibaPDA computer.

Perform the configuration in the I/O Manager under the node ibaFOB-SD/-SDexp in a Simadyn-D text module. The source text and the text signals with the data type STRING derived from the source text or a different data type are configured in the Analog tab of the module. For numerical data types, the conversion is carried out automatically.

SIMATIC TDC

The source text is transmitted to ibaPDA via a connection with the SIMATIC TDC system (CP52M0 in GDM). This requires a special ibaFOB-TDC/-TDCexp interface card for the ibaPDA computer.

Perform the configuration in the I/O Manager under the node ibaFOB-TDC/-TDCexp in a TDC text module. The source text and the text signals with the data type STRING derived from the source text or a different data type are configured in the Analog tab of the module.

TDC TCP/UDP

The source text is transmitted to ibaPDA as a TCP/IP telegram or UDP datagram via the TDC-TCP/UDP interface.

This can be configured in the I/O Manager in a TDC TCP/UDP Generic module. The source text is formed in the Analog tab from the symbols with the STRING[32] data type.

To divide the text into individual text signals, a module Text splitter must be configured under the Virtual node.

VIP TCP/UDP

The source text is transmitted to ibaPDA as a TCP/IP telegram or UDP datagram via the VIP-TCP/UDP interface.

This can be configured in the I/O Manager in a VIP TCP/UDP Generic module. The source text is formed in the Analog tab from the symbols with the STRING[32] data type.

To divide the text into individual text signals, a module Text splitter must be configured under the Virtual node.