Profinet integration

Configuration

When planning Profinet devices, a device is mapped as a modular system, which has a headslot and several data modules.

GSDML file

The device data required for project planning is stored in Generic Station Description Markup Language (GSDML) files. The data modules of a network module are displayed in the project planning software itemized by subslots.

The GSDML file provides the possible data modules (input or output of different data widths). To configure the network modules, the corresponding data modules are assigned to a subslot.

Integrating a module

The device can be found in the catalog via the search function and pulled into the Profinet string via drag & drop (see Integrating a module).

The BNI PNT… module with the PN-IO, Port 1-M12 and Port 2-M12 sub-modules are used for Profinet communication.

In X1 PN-IO, functions such as prioritized startup or the domains for the ring topology can be selected.

Slot 1 is reserved for IO-Link. The following submodules can be inserted in the eight submodules below:

• IO-Link

• Digital Input (DI)

• Digital Output (DO)

• Port deactivated

Only the IO-Link headslot is plugged in by default. The submodules are free.

Hardware configuration

The remaining submodules can, if necessary, be pulled into the configuration table from the hardware catalog using drag & drop and must be configured in accordance with the configuration of the headslot.

Addressing modules

After double-clicking on the submodules, the addressing can be changed in the Addresses window.

Configuring the network module

The ports 1…8 are reserved for the IO-Link Ports.

• In accordance with the process data length of the IO-Link device, select a matching network module in the catalog and drag it to the corresponding slot using drag & drop.

  The process data length required by the device can be found in the manual for the IO-Link device.

  

Port Qualifier (PQI)

Network modules are available with and without PQI. The PQI is 1 byte long and contains various information about the respective port status. This information can be found at the end of the input data of the submodule of a port for each bit.

IO-Link submodules without PQI save 1 byte. The information which the PQI contains can currently not be replaced with another submodule. Submodules which contain this information (e.g. PD Valid, Pin2/4, etc.), will be added in the future.

The flags have the following meaning:

PQ

Value	Description
0	Process data from device invalid
1	Process data from device valid

DevErr

Value	Description
0	No errors/warnings
1	Errors/warnings occurred.

DevCom

Value	Description
0	No device available
1	Device available

PortActive

Value	Description
0	Port deactivated.
1	Port activated.

Configuring digital input and digital output

In order to configure the port pins to input or output, the corresponding submodule Digital Input or Digital Output must be dragged to the port. Input/Output are always configured to Pin 4 of the port. Pin 2 must be manually configured in the module parameters of the port properties.

The inputs and outputs can be mapped either to the network module 1 (see Network module 1) or to the submodules Input-Pin 2/4 or Output-Pin 2/4 in slot 3.

To save the two bytes in the network module, there is a second network module without IO data. If this is used, the inputs and outputs can be mapped to the corresponding submodules in slot 3.

If the network module has been inserted with IO data, the submodules Input-Pin 2/4 and Output-Pin 2/4 can be inserted in slot 3 but the output module has no function. Only the configuration of the ports in slot 1 is valid. The inputs are also always displayed at slot 3.

Disable IO-Link diagnosis

If this function is configured, the IO-Link diagnosis remains activated for all ports and can be deactivated for the desired ports by setting the bit for the respective port.

IO-Link communication

Bit status for each IO-Link port, i.e. feedback on whether communication has been established.

IO-Link PD Valid

Bit status for each IO-Link Port, i.e. feedback whether the process data at the corresponding port are set to Valid.

Deactivating diagnostic messages

The Diagnostics Deactivated module allows various diagnostic messages sent by the module to be suppressed.

To deactivate the diagnostic messages:

• Plug the Diagnosis Disable module into the extended modules (see Configurations of the Diagnosis Disable module).

  

The table below shows the individual bits fields and their possible values.

Pending diagnostics can be deleted at runtime by toggling the bit.

Configuring device

After double-clicking on the module in the Profinet string, the communication parameters of the module are displayed.

Assign IP address

The IP address is configured under IP Protocol.

Establishing a device connection

• In theDevice overview, right-click on the module and select Assign device name.

  

  The identification takes place via the MAC address or via the Flash LED function. This function causes the SF-LED on the module to flash three times at a frequency of 1 Hz.

  

Assigning the device name

• Assign the desired device name and assign it to the selected, found device by clicking on Assign name.

  Note

  The device name must match the name that was previously configured (see chapter Configuring device ).

  

Completing the configuration

• Download the configuration into the module parameterization.
  ⇒ The bus error should be reset at the module.

If the module continues to report a bus error, this could be because the device relationship has not been established. The following remedies are possible:

• Via Target system > Ethernet > Ethernet subscriber > Browse, scan the network and check whether the device is reporting under the correct device name and IP address.

• If necessary, change the IP address or the device name.

• Assign the device name to the device again and download the configuration.

IO-Link Configuration

Port configuration settings

In the network module properties, the IO-Link parameters of the respective port can be changed.

The following settings can be made:

Enable port diagnostics

Activates or deactivates the diagnostic messages of the port (static muting).

Configure process alarms

Maps single-shot events (notifications) to process alarms.

Activate input fraction

Checks the PD size of the device against the PD size of the plugged module.

Note

Only affects PD inputs. PD output size is always checked.

Enable Pull/Plug

Blocks the call of module OB82 (diagnosis alarm) or enables it.

Port mode

Defines the mode of the port.

The following settings are possible:

• Deactivated: Switches the port off.

• Auto Config: Activates IO-Link and the data exchange between master and device.

• Set Port Config: Enables some settings to be changed manually, e.g.Cycle Time.

Note

Set Port Config must be activated to enable validation and back-up (data storage).

Validation and backup

Validation and backup are used to identify specific or individual device types with which a data exchange should take place.

The following settings are possible:

• No Device Check: Validation is deactivated and every device is accepted.

• Compatibility Device V1.0: Only devices according to IOL specification 1.0 are accepted. No data storage, only validation active.

• Compatibility Device V1.1: Only devices according to IOL specification 1.1 are accepted. No data storage, only validation active.

• Compatibility Device V1.1 Backup and recovery: Only devices according to IOL specification 1.1 are accepted. Data storage with upload and download, with validation.

• Compatibility Device V1.1 Recovery: Only devices according to IOL specification 1.1 are accepted. Data storage only with download (Master to Device), with validation.

Port Class / Pin2 behavior

Defines the behavior of pins.

The following settings are possible:

• Class A / NC: Pin 2: Deactivated

• Class A / DI: Pin 2: Digital input

• Class A / DO: Pin 2: Digital output

• Class A / Power = actuator supply/continuous voltage on pin 2

• Class B / NC: Pin 2: Deactivated

• Class B / DI: Pin 2: Digital input

• Class B / DO: Pin 2: Digital output

• Class B / Power: actuator supply/continuous voltage on pin 2

Note

The Pin 4 behavior is specified by the plugged submodule.

Note

Class B only available for devices with Class B property.

Cycle Time

Makes it possible to influence the IO-Link communication speed.

The cycle time can be adjusted using the scroll-down menu.

Port class

The plugged submodule for Pin 4 / Pin 2 behavior is always the configuration for Pin 4.
In addition, NC (Not connected), DI, DO or Power can be selected for pin 2.

Settings for Pin 4 / Pin 2 behavior

The following settings are possible:

• Class A / NC: Defines Pin 4 as digital input / disables Pin 2.

• Class A / DI: Defines Pin 4 and Pin 2 as digital input.

• Class A / DO: Defines Pin 4 as digital input and Pin 2 as digital output.

• Class A / Power: Continuous voltage on pin 2.

Note

Configuration using pin 4 digital input as an example.

Function module

To be able to write or read out the ISDU data of connected IO-Link devices during operation, the common programming interfaces of the control manufacturers provide corresponding function modules or libraries.

REQ

Use Request to start the action in order to write or read data.

ID

The ID is permanently declared by the master via the hardware configuration.
This can be found under System constants in the hardware identification.

• Select the hardware ID of the module IO-Link_I_O_Ports_1~BALLUFF_….

CAP Value

This is assigned by the manufacturer. For Balluff products, it is the value 0xB400.

Read/Write

The command is defined here. To read data, it must be a 0; to write data, it must be a 1.

Port

Here you select the port to which the device has been connected. The master counts as 0 and the ports are counted from 1…8.

Index

This is the index of the IO-Link subscriber being read out or written. This can be found in the user’s guide for the IO-Link device.

SubIndex

The sub-index is defined by the data to be processed. This can also be found in the operating instructions for the connected IO-Link device.

LEN

This is the length of the data. This can also be found in the parameter data in the user’s guide for the IO-Link device.

RECORD_IOL_DATA

A data module is used for communication. The structure must be established in Array of Bytes. The data to be changed is written into this array.

DONE_VALID

Confirms the successful request to read or write data.

BUSY

Shows the working state of the module.

ERROR

If an error occurs in the function, it is reported here.

STATUS

Error status of the function

IOL_STATUS

Describes the current status or an error.

RD_LEN

Shows how many bytes were read by the module.

The IOL_Call function module composes a telegram that is transferred to the master via acyclic services. The following settings are required for this:

The telegram set-up is described in the table below.

Read

To be able to read out data, the master must be sent a read task for the corresponding slot/index/subindex.

For this, the telegram must be adapted accordingly (slot, index) and entered at Task 0x03 for reading. The telegram can then be sent to the corresponding module via write command.

The module reads the data from the IO-Link device.

The data can be fetched by reading with the same telegram.

Write

To be able to write data, the network module must be sent a write task for the corresponding slot/index/subindex.

For this, the telegram must be adapted accordingly (slot, index) and entered at Task 0x02 for writing. The telegram can then be sent to the corresponding module via write command.

Ring topology

The network module also supports the ring topology with media redundancy, which is enabled via the Media Redundancy Protocol (MRP). For this, the module and the MRP master (Managed Switch, CPU, etc.) must be in the same topology instance.

With the ring topology, it is possible to establish a redundant system. I.e. in normal operation, one side of the ring line from the MRP master is deactivated. If the

line is damaged or capped at one place in the ring, the deactivated branch is activated again and there are two linear topologies.

Activating ring topology

• Set the media redundancy role to Client (the default setting is Non-subscriber).

  

  To ensure uninterrupted operation, the watchdog time should be greater than 200 milliseconds, as the MRP master requires some time to activate the second line. If the watchdog time is less than the switching time of the MRP master, this will cause a communication breakdown.

  The watchdog time is calculated from the “Update time” and the Accepted update cycles without IO data factor.

  

Device replacement without exchangeable medium

The modules also support simple device replacement in LLDP mode (Link Layer Discovery Protocol).

Activating device replacement without exchangeable medium

• In the CPU hardware configuration, activate the Support device replacement without exchangeable medium checkbox.

  

• Create the Profinet topology in the hardware configuration.

  Note

  The connections of the individual ports must match the hardware wiring. If the topology in the hardware configuration is not a match, errors can occur.

  

ISDU parameterization via GSDML

With ISDU parameterization via GSDML, the connected IO-Link devices can be configured via the parameters of the corresponding submodules when establishing a connection with Profinet.

The parameters are transferred when the BNI establishes the connection with the controller and are then forwarded directly to the corresponding IO-Link devices as ISDU write accesses. When an IO-Link device is unplugged and plugged in, the ISDU parameters configured in advance and transmitted by the controller are written again.

Carry out ISDU parameterization

1. Plug an IOL submodule into slot 1 of the desired port.

2. Insert the ISDU parameter configuration module into slot 3.

3. Select the corresponding submodule to define the maximum number of ISDU parameters that can be written to the corresponding port.

   

   The assignment position submodule = port number applies, e.g. slot 3/subslot 3 = Port 2 (see Assignment position submodule = port number).

   

4. Enter the ISDU parameters in the corresponding fields.

   Note

   Regardless of the submodule used, only the parameters that are entered are written to the IO-Link device (condition: length > 0). When the connection is established, all parameters are transferred to the BNI.

   Example

   ISDU 64 parameter is plugged in and 5 ISDU parameters are described.

   • All 64 parameters are transferred when the connection is established.

   • Only the 5 described ISDU parameters are transferred to the device.

Set ISDU parameterization

The following settings exist for the ISDU parameterization:

• Reset to factory defaults: Resets the ISDU parameters to factory settings. The ISDU parameters can then be reset.

• Start block parameterization: Starts the check of several parameters of a device. The parameters are checked for plausibility only at the end of the complete parameterization.

• End block parameterization: Ends the check of the parameters of a device. Setting the parameter is mandatory if Start block parameterization has been selected.

ISDU parameterization via GSDML and device catalog

With the ISDU parameterization via GSDML and device catalog, the connected IO-Link devices can be configured with the parameters taken from the IOOD of the device when establishing a connection with Profinet.

Carry out ISDU parameterization

• Plug the desired devices from the GSDML catalog into the corresponding subslots of the IO-Link ports (slot 1).

  

  ⇒ The device parameters appear in the module parameters of the corresponding port and can be selected.

  

The parameters are forwarded to the corresponding devices as ISDU write accesses and written to the device in the following cases:

• each time the IO-Link device is reconnected

• for a new connection with the PLC

Integrating Safety-Hub

Connecting the safe I/O module to the network module

When project planning for Profinet devices, a device is mapped as a modular system, which has a headslot and several data modules. The illustrations used here are taken as examples from the Totally Integrated Automation Portal (TIA Portal) project planning software and from the SIMTATIC Manager from Siemens AG and are for illustrative purposes only.

The necessary settings depend on the application and are the responsibility of the user. The BNI IOF-329-P02-Z038 must always be connected via a compatible Balluff network module.

Placing module on slot

The GSDML file provides the data modules available for the respective network module.

• Select module IO-Link I/O ports (w/o IO data) with Safety Hub and ISDU and drag and drop to slot 1.

  

  

Assigning a secure I/O module to a slot

Before assigning to the desired slot, the two default entries Port deactivated and Empty submodule on the network module must be deleted. The BNI IOF-329-P02-Z038 security module can then be dragged and dropped under the tab Device view > Device overview to any IO-Link Port of the compatible Balluff network module as a new IO-Link data module.

The device data for the secure I/O module can be found in the Safety Hub submodule of the project planning software.

Configuring slot

1. Delete default setting for the Port deactivated and Empty submodule entries.

   

2. Drag and drop the secure I/O module for the secure data from the Safety Hub submodule to the upper free slot. Place the submodule for the standard IO data in the slot below.

   

   

Diagnosis

Diagnosis message

The diagnosis message that the module generates in the event of an error is usually read out from the PLC and processed. It is also possible for the diagnosis to be read out and evaluated from the module using function modules.

The diagnosis message is 40 bytes long and split into 3 blocks (Block Header, Alarm Header, Alarm Item) (see table below).

Block Header

The first part of the diagnosis is the so-called Block Header, which is 6 bytes long.

BlockType

The first 2 bytes of the Block Header are written by the block type, in order to define the data type.

BlockLength

2 bytes of data; Information about the length of the following diagnosis message (for the complete diagnosis message, the 2 bytes of the block type and the 2 bytes of the block length must be added together).

BlockVersion

Low Byte fixed at 0x00, High Byte fixed at 0x01.

Alarm Header

The second part of the diagnosis is known as the Alarm Header, which is 20 bytes long.

AlarmType

2 bytes of data; Information on the alarm type.

API

4 bytes of data; Application Process Identifier.

SlotNumber

2 bytes of data; defines which slot of the module is reporting an error.

SubslotNumber

2 bytes of data; defines which subslot of the slot reports an error.

ModuleIdentNumber

4 bytes of data; defines which module is plugged in to the respective slot (module identification is saved in the GSDML).

SubmoduleIdentNumber

4 bytes of data; defines which submodule is used in the respective module (submodule identification is stored in the GSDML).

Alarm Specifier

2 bytes of data; Alarm Specifier is divided as follows:

Sequence Number (Bit 0…10)

This counter is incremented with each new diagnostic message.

Channel Diagnosis (Bit 11)

Manufacturer Specific Diagnosis (Bit 12)

Submodule Diagnosis State (Bit 13)

Reserved (Bit 14)

AR Diagnosis State (Bit 15)

Alarm Item

The third part of the diagnostics is known as the Alarm Item, which is 14 bytes long.

User Structure Identifier

2 bytes of data; defines the type of diagnostics.

ChannelNumber

2 bytes of data; defines the channel number.

ChannelProperties

2 bytes of data; Channel Properties are divided as follows:

Type (Bit 0…7)

Accumulative (Bit 8)

Maintenance (Bit 9 and 10)

Specifier (Bit 11 and 12)

Direction (Bit 13…15)

ChannelErrorType

2 bytes of data; Information on the error type.

If User Structure Identifier has the value 0x8000, the module-related errors are displayed here:

ExtChannelErrorType

2 bytes of data; Information on the error type.

Profinet diagnostic module – Pin 4/2 Actor Ground Short Circuit Detection

If a short circuit is detected at a port on the pin, the corresponding bit is set to 1.

Profinet module – Short Circuit and Actor Warning Detection

If an error with the following modules occurs, the corresponding bit is set to true:

• Pin 1 Short Circuit Detection

• Pin 4/2 Actor Warning Detection

• Pin 4/2 Actor Ground Short Circuit Detection

• Pin 4 IO-Link Short Circuit Detection

Profinet diagnostic module – Pin 4 IO-Link Short Circuit Detection

If an IO-Link short circuit is detected at a port on pin 4, the corresponding bit is set to 1. The port must be configured to IO-Link.

Profinet module – IO-Link Device Event Pending

If there is a pending IO-Link device event at any connection, the corresponding bit is set to 1.

Profinet diagnostic module – Pin 4/2 Actor Warning Detection

If pin 2/4 of connection x (where x is a number between 1 and 8) is configured to:

• OUTPUT (Pin 2/4)

  • If the voltage is low and an external voltage is applied, the bit is set to true.

  • If high-controlled (UA is missing; therefore the output is physically low) and an external voltage is applied, the bit is set to true.

• POWER (Pin 2)

  • If UA is missing and external voltage is applied, the bit is set to true.

Profinet module – Port Event Pending

If an upcoming event is detected, the bit for the port is set to 1. If an outgoing event is sent for this event, the bit is reset to 0.