BNI PNT-507-005-Z040

BNI PNT-527-005-Z040
IP67 Module
User's Guide
Table of Contents

1 General 4
1.1. Structure of the guide 4
1.2. Typographical Conventions 4
Enumerations 4
Actions 4
Syntax 4
Cross-references 4
1.3. Symbols 4
1.4. Abbreviations 4
1.5. Differing views 4
2 Safety 5
2.1. Intended use 5
2.2. Installation and Startup 5
2.3. General Safety Notes 5
2.4. Resistance to Aggressive Substances 5
Dangerous Voltage 5
3 First Steps 6
3.1. Module overview 6
3.2. Mechanical Connection 7
3.3. Electrical Connection 7
Supply voltage 7
Grounding 7
PROFINET interface 7
Port 8
4 Tecnical data 9
4.1. Dimensions 9
4.2. Mechanical Data 9
4.3. Operating conditions 9
4.4. Electrical Data 9
4.5. PROFINET 10
4.6. Function indicators 10
Module Status 10
Port 11
5 Integration 12
5.1. Configuration 12
GSDML file 12
Integration of the module 12
Configuration of the header module 13
Hardware configuration 14
IO-Link configuration 15
IO-Link functions 15
Cycle Settings 15
Data selection 15
Validation 15
Device name, Profinet address 16
Establishing device relationship 17
Assigning device name 17
Concluding the configuration 18
5.2. Functions in module properties 19
Module settings 19
Port functions 19
Safe state 19

www.balluff.com 1
 5.3. Bit mapping and function 20
Inputs pin 4 20
Inputs pin 2 20
Outputs pin 4 20
Outputs pin 2 20
IO–Link modules 20
Actuator shutdown pin 4 / pin 2 20
Actuator warning pin 4 / pin 2 20
Restart pin 4 / pin 2 20
Switching IO-Link diagnostics on / off 21
IO-Link communication 21
Peripheral error, socket 21
Sensor supply 21
Short-circuit 21
Station diagnostics 21
IO-Link PD valid 21
Parameter server 22
6 Monitoring & diagnostics 23
6.1. General 23
6.2. SNMP MIBs 23
7 Web Server 25
7.1. General 25
7.2. Navigation / Info 26
7.3. Login/Logout 27
7.4. "Home" dialog 28
7.5. "Ports" dialog 30
7.6. "Configuration" dialog 31
7.7. "Diagnostics" dialog 32
8 Diagnostics 33
8.1. Diagnostics messages 33
8.2. Block Header 34
Block Type 34
Block Length 34
Block Version 34
Alarm Type 34
API 34
Slot 34
Subslot 34
Module ID 35
Submodule ID 35
8.3. AlarmSpecifier 36
Sequence Number 36
Channel Diagnostic 36
Manufacturer-Specific Diagnosis 36
Submodules 36
Diagnostic State 36
ARDiagnosis State 36
User Structure ID 36
8.4. Channel Number 37
8.5. Channel Properties 38
Type 38
Accumulative 38
Maintenance 38
Specifier 38
Direction 38
8.6. Channel Error Type 39
9 Configuration of IO-Link devices 40
Options 40
Read 40
Write 40
10 Appendix 41

www.balluff.com 2
 10.1. Included in the Scope of Delivery 41
10.2. Order number 41
10.3. Ordering information 41
Notes 42

www.balluff.com 3
1 General

1.1. Structure of the This guide is arranged so that one chapter builds upon the other.
guide Chapter 1: General
Chapter 2: Basic safety instructions
………

1.2. Typographical The following typographical conventions are used in this manual.
Conventions

Enumerations Enumeration is shown in list form with indentation.

 Entry 1
 Entry 2

Actions Action instructions are indicated by a preceding triangle. The result of an action is indicated
by an arrow.
 Action instruction 1
 Result of action
 Action instruction 2
Actions can also be indicated as numbers in parentheses.
(1) Step 1
(2) Step 2
(3)

Syntax Numbers:
Decimal numbers are shown without additional information (e.g. 123),
Hexadecimal numbers are shown with the additional indicator hex (e.g., 00 hex) or the prefix
"0x" (e.g., 0x00).

Cross-references Cross-references indicate where additional information on the topic is located.

1.3. Symbols Note

This symbol indicates general notes.

Attention!
This symbol indicates a security notice which must be observed.

1.4. Abbreviations BNI Balluff Network Interface

I Standard input port
PNT ProfiNet™
EMC Electromagnetic Compatibility
FE Function ground
O Standard output port
US Sensor supply undervoltage
UA Actuator supply undervoltage

1.5. Differing views Product views and images in this manual may differ from the product described. They are
intended to serve only as illustrations.

www.balluff.com 4
Balluff Network Interface ProfiNet™

2 Safety

2.1. Intended use The BNI PNT-… is a decentral IO-Link input and output module for connecting to a
ProfiNet™ network.

2.2. Installation and Attention!

Startup Installation and startup are to be performed by trained technical personnel only.
Skilled specialists are people who are familiar with the work such as installation
and the operation of the product and have the necessary qualifications for these
tasks. Any damage resulting from unauthorized tampering or improper use shall
void warranty and liability claims against the manufacturer. The operator is
responsible for ensuring that the valid safety and accident prevention regulations
are observed in specific individual cases.

2.3. General Safety Commissioning and inspection

Notes Before commissioning, carefully read the User's Guide.
The system must not be used in applications in which the safety of persons depends on the
function of the device.
Intended use
Warranty and liability claims against the manufacturer shall be rendered void by damage
from:
 Unauthorized tampering
 Improper use
 Use, installation or handling contrary to the instructions provided in this User's
Guide.
Obligations of the owner/operator!
The device is a piece of equipment in accordance with EMC Class A. This device can
produce RF noise. The owner/operator must take appropriate precautionary measures
against this for its use. The device may be used only with a power supply approved for this.
Only approved cables may be connected.
Malfunctions
In the event of defects and device malfunctions that cannot be rectified, the device must be
taken out of operation and protected against unauthorized use.
Approved use is ensured only when the housing is
fully installed.

2.4. Resistance to Attention!

Aggressive The BNI modules always have good chemical and oil resistance. When used in
Substances aggressive media (such as chemicals, oils, lubricants and coolants, each in a high
concentration (i.e. too little water content)), the material must first be checked for
resistance in the particular application. No defect claims may be asserted in the
event of a failure or damage to the BNI modules caused by such aggressive
media.

Dangerous Attention!
Voltage Before working on the device, switch off its power supply.

Note
In the interest of continuous improvement of the product,
Balluff GmbH reserves the right to change the technical data of the product and
the content of these instructions at any time without notice.

www.balluff.com 5
3 First Steps

3.1. Module overview

1 12

2 11

10

5
4

Figure 1 – Overview of BNI PNT-50x-005-Z040

1 Mounting hole 8 Port 0

2 PROFINET ™ Port 1 9 Power IN
3 Status LEDs 10 Labels
4 Pin/Port-LED : Signal status 11 PROFINET ™ Port 2
5 Port 3 12 Ground connection
6 Port 2
7 Port 1

www.balluff.com 6
Balluff Network Interface ProfiNet™

3 First Steps

3.2. Mechanical The module is secured by means of two M6 screws and two washers.
Connection Insulation support is available separately.

3.3. Electrical
Connection

Supply voltage Pin Function Description

1 0V GND actuator supply
2 0V GND module / sensor supply
Class A

IN
3 FE Function ground
4 +24 V Module / sensor supply
5 +24 V Actuator supply
7/8”, male 1 N24 Separate supply voltage (-)
2 0V GND module / sensor supply
Class B

3 FE Function ground
4 +24 V Module / sensor supply
5 P24 Separate supply voltage (+)

Note
Where possible, use separate power supplies for sensor/bus and actuator.
Total current < 9 A The total current of all modules must not exceed 9 A even in
the case of series connection of the actuator supply.

Grounding

Note
The functional ground connection between housing and machine must have a
low impedance and be as short as possible.

PROFINET M12, D-coded, female

interface Pin Function
1 Tx+ Transmit Data +
2 Rx+ Receive Data +
3 Tx- Transmit Data -
4 Rx- Receive Data -

Note
Unused I/O ports must be provided with cover caps to comply with degree of
protection IP67.

www.balluff.com 7
3 First Steps

Port Function
Pin
Class A Class B
1 +24V 1.6 A +24V 1.6A
2 Input/output 2A P24
3 0V 0V
M12 Input / Output 2A/
A-coded 4 IO-Link input/output 2A
IO-Link
female
5 n. c. N24

Note
The IO-Link interface is powered from the sensor supply.

Note
For the digital sensor inputs, refer to guideline on inputs EN 61131-2,
Type 3.

Port
0-3
BNI PNT-507-005-Z040 IO-Link Class A
BNI PNT-527-005-Z040 IO-Link Class B

www.balluff.com 8
Balluff Network Interface ProfiNet™

4 Technical data

4.1. Dimensions

4.2. Mechanical Data Housing material Zinc diecasting, matte nickel-plated

Enclosure rating per IEC 60529 IP 67 (only in plugged-in and screwed-down state)
Supply voltage 7/8" female, 5-pin
Input ports / output ports M12, A-coded (4x female)
Dimensions (W x H x D in mm) 37 x 224 x 32.6
Type of mounting Screw mounting with 2 mounting holes
Ground strap installation M4
Weight Approx. 350 g

4.3. Operating Operating temperature Ta -5°C ... 70°C

conditions Storage temperature -25°C ... 70°C
EMC EMC – Directive 2004/108/EEC
- EN 61000-4-2/3/4/5/6 - EN 61000-6-2
- EN 55011 - EN 61000-6-4
EN 60068-2-6, EN 60068-2-27
Vibration/shock
EN 60068-2-29, EN 60068-2-64

4.4. Electrical Data Supply voltage 18...30.2 V DC, in accordance with EN 61131-2
Ripple < 1%
Input voltage at 24 V 130 mA

www.balluff.com 9
4 Technical data

4.5. PROFINET PROFINET port 1 x 10Base/100Base Tx

Cable types in accordance
Shielded, twisted pair min. STP CAT 5/ STP CAT 5e
with IEEE 802.3
Data transmission rate 10/100 Mbps
Max. cable length 100 m
Flow control Half-duplex/full-duplex (IEEE 802.33x pause)

4.6. Function
indicators

Status LEDs

Port LEDs

Module Status LED Indicator Function

Green Supply voltage OK
U Red No actuator power supply
UA supply voltage
Red, flashing
low (< 18 V)
Off US error
No supply voltage
low (< 18 V)
SF Red Diagnostics message; system error
Red, flashing Service DCP signal activated via bus
Off No error
BF Red No connection or no configuration
Red, flashing No data exchange

LK Green Data transfer

www.balluff.com 10
Balluff Network Interface ProfiNet™

4 Technical data

Port Standard port

Status Function
Off Status of input or output pin is 0
Yellow Status of input or output pin is 1

IO-Link port
Status Function
Green IO-Link – connection active
Green, flashing No IO-Link – connection
Green, rapidly flashing Preoperate
Red, flashing Validation failed

Port configuration
Status Diagnostics
Input Output
input
Short-circuit
Red Input inactive Short circuit at output pin
Pin 1 and 3
Red, flashes briefly - - Short circuit Pin 1 and 3

www.balluff.com 11
5 Integration

5.1. Configuration When planning Profibus devices, a device is depicted as a modular system with a header
module and several data modules. The screenshots shown here
have been taken from the configuration software of the Siemens HW config.

GSDML file The device data required for project planning is saved in GSDML files (Generic Station
Description Markup Language). The GSDML files are available in two languages as an
Internet download (www.balluff.com). The data modules of an IO-Link block are depicted in
the project planning software according to the slot.
The GSDML file makes the possible data modules available (input or output of different
data ranges). For configuration of the IO-Link blocks, the corresponding data modules are
assigned to a slot.

Integration of the The device can be found by searching in the catalog and inserted in the Profinet section by
module drag & drop.

The BNIPNT507005Z040 / BNIPNT527005Z040 module with

submodules PN-IO, port 1-M12, port 2-M12 are used for
Profinet communication.
In X1 PN-IO, functions such as prioritized run-up or the domains for the ring topology can be
selected.
Slot 0 can be used for defining the port function (input, output, diagnostics input) or
diagnostics messages.
The remaining slots (2-5) preallocated in the default configuration are the placeholders for
the IO-Link modules or standard I/O modules. Slot 2 is for the first IO-Link port / standard
I/O port and Slot 5 for the last.
If IO-Link communication is planned for a given port, the standard I/O module must be
deleted and replaced with an IO-Link module, e.g., IOL_E_2byte.

www.balluff.com 12
Balluff Network Interface ProfiNet™

5 Integration

Configuration of Double-click on the header module to open its properties.

the header Click on the "Parameter" tab to open a menu selection for
module defining the port functions and diagnostic functions.

Note
IO-Link configuration:
If the connected IO-Link device makes outputs available, pin 2 must be configured
to output on the corresponding port.
Standard input and output:
For each port, the function (N.C., N.O., diagnostic input (pin 2)) can be arbitrarily
selected for each port at pin 2 and pin 4.

www.balluff.com 13
5 Integration

Hardware The IO-Link / standard I/O modules must now be configured appropriately for the
configuration configuration of the header module.
If necessary, these can be taken over into the configuration table from the hardware catalog
by means of drag & drop.
By default, all ports are set to Standard I/O.
If the port is to be configured as an IO-Link port, the module must be deleted and replaced
with an IO-Link module.

Slots 1..4 are reserved for the IO-Link ports / standard I/O ports.

Module addressing:
Double-click on the IO-Link modules and the remaining addressable modules to change the
addressing in the "Addresses" window

Configuring the IO-Link module:

A suitable IO-Link module that corresponds to the process data length of the IO-Link device
must be selected in the catalog and dragged to the appropriate slot by means of drag &
drop.
The process data length required by the device in each case can be obtained from the
manual of the IO-Link device.

Configuring a standard input / output:

If one of the possible port pins (pin 4) is to be configured with a standard function (input,
output),
the "Standard I/O" placeholder module must be used for the
corresponding slot.
To address the inputs and outputs, input pin 2 / 4 and output 2 /4
must be taken over from the catalog and used in the configuration according to the given
modules.

For the SIO function, integrate the "IO-Link input with SIO mode" module.

With the remaining modules, the various functions are mapped into the process data areas.

www.balluff.com 14
Balluff Network Interface ProfiNet™

5 Integration

IO-Link In the IO-Link properties of the module you can change the IO-Link parameters
configuration of the respective port.

IO-Link functions Explanation of the possible settings in the properties of the IO-Link port

Cycle Settings This parameter can be used to reduce the IO-Link communication speed by increasing the
IO-Link cycle time.
Use the scroll down menu to adjust the cycle time.

Data selection The start byte of the process data can be defined with the data section offset. For the max.
input data length, the actual process data length of the IO-Link device is entered. These
settings are only for the input data.
The visible data window for the input data can now be adjusted via an IO-Link module with
appropriate process data length.

Validation No validation: validation deactivated, every device will be accepted

Compatibility: manufacturer ID and device ID are compared to the module data.
The IO-Link communication is only started if there is a match. Manufacturer ID and device
ID are entered in decimal format.
Identity: manufacturer ID and device ID and serial number are compared to the module
data. The IO-Link communication is only started if there is a match.
Manufacturer ID and device ID are entered in decimal format, the serial number is entered
in ASCII code

www.balluff.com 15
5 Integration

Device name, Double-click on the module in the Profinet line to view the communication parameters of the
Profinet address module.

The device name and the Profinet address (IP) are configured here.

www.balluff.com 16
Balluff Network Interface ProfiNet™

5 Integration

Establishing "Device view"  right-click on module  "Assign device name".

device
relationship

Assigning device Select the desired name and use "Assign name" to assign the marked device that you
name found.
The device name must be the same as that previously configured under device properties
(see previous page)

Identification takes place via the MAC address (on the rear of the device)
or via the Blink Test.

www.balluff.com 17
5 Integration

Concluding the Download the configuration into HW config.

configuration
At this point, the bus error on the module should disappear.
There could still be an active system error, particularly if an IO-Link is used.

Possible causes:
- Line break (no IO-Link device connected)
- IO-Link device fault (e.g., external voltage supply not connected)
- Validation failed

If the module still reports a bus error,

there could be a problem in one of the following areas:

- Device relationship not established.

Scan the network and check whether the device is signaling under the correct
device name and correct IP address.
Adapt the Ethernet address or device name if necessary,
reassign the device name and download the configuration.

www.balluff.com 18
Balluff Network Interface ProfiNet™

5 Integration

5.2. Functions in Description of the functions in module properties

module properties

Module settings Global diagnostics:

This function can be used to permit / suppress all diagnostics messages of the module.
(optical diagnostics signals and diagnostics in configured diagnostics modules
are not affected)

Sensor supply undervoltage:

This function can be used to permit / suppress the diagnostics message Sensor supply
undervoltage. (optical diagnostics and diagnostics in configured diagnostics modules are
not affected)

Actuator supply undervoltage:

This function can be used to permit / suppress the diagnostics message Actuator supply
undervoltage. (optical diagnostics signals and diagnostics in configured diagnostics
modules are not affected)

Port functions The function for every individual port pin can be defined here:
Make contact = input as normally open contact
Break contact = input as normally closed contact
Output = output function
IO-Link Input with SIO mode = SIO Mode; an IO-Link device can be
configured and then placed in an SIO mode
in which the IO-Link port functions as a
simple switching input.
Pin function depends on configuration.

Safe state This function is a supplement to an output configuration of the respective port pin.
For each port pin, a safe status can be predefined which is to be assumed in the event of
a loss of bus communication.

www.balluff.com 19
5 Integration

5.3. Bit mapping and Bit mapping and function of the configurable modules
function

Inputs pin 4 Signal from configured inputs or outputs are depicted in the modules
Inputs pin 2 inputs pin 4 / inputs pin 2 and outputs pin 4, outputs pin 2.
Outputs pin 4
Outputs pin 2 The "inputs pin 2" module also depicts the diagnostic inputs of the diagnostic input
function. Depending on configuration..

IO–Link modules The IO-Link modules always have the same structure:

IOL_I/O_x/xBytes
Number of process data items used (should be equal to or greater than
the process data length of the IO-Link device)
I = Input data
O = Output data
I/O = Both input and output data

Actuator shutdown Depicts a short circuit between a set output to ground

pin 4 / pin 2 at the respective port pin.

Bit 3 Bit 2 Bit 1 Bit 0

Port 3

Port 2

Port 1

Port 0

Actuator warning Feedback if a voltage is being supplied at an output that is not set.
pin 4 / pin 2
Bit 3 Bit 2 Bit 1 Bit 0
Port 3

Port 2

Port 1

Port 0

Restart pin 4 / pin 2 If this function is configured, after an actuator short-circuit there is no
automatic restart, but rather the port must be activated by inserting the corresponding bit.

Bit 3 Bit 2 Bit 1 Bit 0

Port 3

Port 2

Port 1

Port 0

www.balluff.com 20
Balluff Network Interface ProfiNet™

5 Integration

Switching IO-Link If this function is configured,

diagnostics on / off the IO-Link diagnostics is deactivated for all ports and
can be reactivated for the desired ports.

Bit 3 Bit 2 Bit 1 Bit 0

Port 3

Port 2

Port 1

Port 0
IO-Link Bit status for each IO-Link port; feedback indicating whether communication is
communication established.

Bit 3 Bit 2 Bit 1 Bit 0

Port 3

Port 2

Port 1

Port 0

Peripheral error, Feedback indicating the port at which an error occurred.

socket
Bit 3 Bit 2 Bit 1 Bit 0
Port 3

Port 2

Port 1

Port 0

Sensor supply Feedback indicating the port at which there is a sensor supply short circuit.
Short-circuit
Bit 3 Bit 2 Bit 1 Bit 0
Port 3

Port 2

Port 1

Port 0

Station diagnostics Feedback indicating which fault occurred.

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Short-circuit

Short-circuit

US actuator
short circuit

US sensor
Actuator

Actuator
Warning

External
voltage
IO-Link

Sensor

no UA
error

IO-Link PD valid Bit 3 Bit 2 Bit 1 Bit 0

Port 3

Port 2

Port 1

Port 0

www.balluff.com 21
5 Integration

Parameter server Switched off:

Data management functions disabled, saved data are retained.

Delete:
Data management functions disabled, saved data is deleted.

Restore:
The parameter data are downloaded to the IO-Link device.
As soon as the saved parameter data in the parameter server of the port differ from the
connected IO-Link device a download is performed.
Only exception: the parameter server is empty. Then another upload is carried out.

Save/Restore:
The parameter data are up- and downloaded to the IO-Link device.
As soon as the saved parameter data in the parameter server of the port differ from the
connected IO-Link device and there are no upload requests from the
IO-Link device, an upload is performed.
As soon as a device requests and upload (upload flag set) or when no data are stored in
the master port (e.g. after deleting the data or before the first upload), the master starts an
upload of the parameter data from the device.

Note
After the upload of the parameter data, the vendor ID and device ID of the
connected IO-Link device are also still saved until the data records are deleted.
When the connected IO-Link device is started, a validation takes place. Thus, only
an IO-Link device of the same type can be used for the data management.

www.balluff.com 22
Balluff Network Interface ProfiNet™

6 Monitoring & diagnostics

6.1. General The fieldbus module provides several diagnostics interfaces which are described in the
following:

 Device diagnostics through the Web interface

 Network diagnostics via SNMP
 Fieldbus-specific diagnostics through the PLC

The Web interface and the fieldbus-specific diagnostics interface are each described in a
separate section.

Access to the Monitoring and Diagnostics interfaces of the device is via the IP-based
Management interface using the Ethernet network. The necessary setting of IP access can
be made not only using the procedure described in the "Integration" section, but also using
other dedicated configuration tools using the DCP protocol of PROFINET. The following
parameters must be set for this:

 IP Address (IP)
 Subnet mask (SN)
 Gateway address (GW)
 Device name

The configuration settings can be reset to the factory default settings via the Web interface.

Configuration settings are only possible if the module does not have an active connection to
a controller.

6.2. SNMP MIBs Monitoring and diagnostics of the network interfaces for the device can be performed using
the SNMPv1 protocol. This can be accessed simply from a so-called SNMP browser using
ordinary network management tools.

The following MIDs are supported:

 MIB-2 (RFC 1213)

 LLDP-MIB (IEEE 802.1AB)

The module-specific information for the MIB-2 are provided by the fieldbus module:

MIB-Variable Description
sysDescr A textual description of the entity. This value should include the full
name and version identification of the system's hardware type, software
operating-system, and networking software.
sysObjectID {1.3.6.1.4.1.44233.1.2.1}
For Balluff products with Product enterprise Number (PEN) = 44233, the
product list is defined in BALLUFF-PRODUCTS-MIB
sysUpTime The time (in hundredths of a second) since the network management
portion of the system was last re-initialized.
sysContact The textual identification of the contact person for this managed node,
together with information on how to contact this person. (“BALLUFF”)
sysName An administratively-assigned name for this managed node. By
convention, this is the node's fully-qualified domain name.
(“BNI PNT ….”)
sysLocation The physical location of this node (e.g. “73765 Neuhausen a.d.F,
Germany”)

www.balluff.com 23
6 Monitoring & diagnostics

The port-specific information for the MIB-2 contains diagnostics data about the network
connections as well as the IO-Link ports:

MIB-Variable Ethernet-Port IO-Link-Port

ifIndex A unique value, contiguously
starting from 1.
ifDescr A textual string containing ”IO-Link X" / “IO-IN X” / ”IO-OUT
information about the interface, X”
i.e. "Ethernet X”
ifType IANAifType = 6 IANAifType = 280 (sdci) when
(ethernetCsmaCd) when IO-Link-Port
Ethernet = 0 (other) when I/O-Port

ifMTU length of Ethernet MTU length of IO-Link process data

(typically max. 32 Byte) or 1,
when IO-port
ifSpeed actual Ethernet speed IO-Link speed (no device = 0
bit/s, Com1 Mode = 4800 bit/s,
Com2 Mode 38400 bit/s, Com3
Mode = 230400 bit/s)
ifPhysAddress MAC address assigned to this This object may contain an octet
port string of zero length, since IO-
Link is a serial P2P protocol
with no specific addressing.
ifAdminStatus Up(1), Down(2), depending Up(1), Down(2), depending if
IO-Link capability is configured.
ifOperStatus Up(1), Down(2), depending if an IO-Link device is connected and
operable.
ifLastChange The value of sysUpTime at the n/a
time the interface entered its
current operational state. If the
current state was entered prior
to the last re-initialization of the
local network management
subsystem, then this object
contains a zero value.
ifInOctets The total number of octets received on the interface, including
framing characters.
ifInErrors n/a Number of received frames that
were rejected as invalid by the
IO-Link-Master (Abort).
ifOutOctets The total number of octets transmitted out of the interface,
including framing characters.
ifOutErrors n/a Number of retries by the IO-
Link-Master, indicating
unsuccessful packet
transmissions.

www.balluff.com 24
Balluff Network Interface ProfiNet™

7 Web Server

7.1. General The BNI fieldbus module provides an integrated web server for retrieving detailed device
information and for configuring the device.

To use the web interface you must first ensure that the module has been correctly integrated
into your network. In addition the IP subnet of the BNI module must be accessible from the
PC on which the browser is running. Please use Internet Explorer 10 or newer as the browser;
older versions may result in display problems.

For open a connection with the web server, enter the IP address of the module in the address
line of the browser. The homepage then appears with the essential device information.

www.balluff.com 25
7 Web Server

7.2. Navigation / Info The navigation bar appears in the upper area of the window, which allows you to switch
between the various dialogs of the web interface. Simply click on the corresponding icon and
for example when selecting "?“ the following Help dialog appears:

Directly below the selected navigation icon a short text appears which shows the current
dialog selection. The Web interface version is stored in the footer of the Help dialog. The
"BALLUFF" logo at upper right links to the international Balluff homepage.

www.balluff.com 26
Balluff Network Interface ProfiNet™

7 Web Server

7.3. Login/Logout To be able to make configuration setting on the fieldbus module through the web interface,
you must first be logged in, since otherwise dialogs and functions are not accessible, as
indicated by grayed out buttons inside the dialogs.

The default password is "BNIPNT“.

After successfully logging in the dialogs are shown as follows:

Note
For security reasons the fieldbus module shows only one login at a time with
configuration access. Reading (without logging in) is however possible from
multiple PCs at the same time on the fieldbus module.

www.balluff.com 27
7 Web Server

7.4. "Home" dialog In this dialog you are given the essential information about the fieldbus itself and its network
activity. You are also shown whether the configuration block was enabled by the controller
(PLC).

Information is also shown about the current process data and the status of the module via the
corresponding LEDs.

After selecting "Led Legend" a Help dialog appears which explains the meaning of the LED
indicators.

If an IO-Link device is connected to one of the configured IO-Link terminals, some of the
device data will be displayed in addition to the module data in the form of a link. After
selecting one of these links the corresponding device dialog is opened.

www.balluff.com 28
Balluff Network Interface ProfiNet™

7 Web Server

Note
You can monitor only the process data and the current status of the module. It is not
possible to configure a module or set the output data.
In this case, you have to use the control unit together with the corresponding
operating software.

www.balluff.com 29
7 Web Server

7.5. "Ports" dialog This dialog shows information and process data for the IO-Link device which is connected to
the selected and configured IO-Link port.
To select the desired IO-Link device, select the correct port on the right side of the module
illustration.

In addition, it is possible to read and configure the parameters of the IO-Link device via the
"Parameter Data" option. The parameter index and subindex of the IO-Link device are
described in the corresponding separate user's guide.

Under "Events" you can see whether a diagnostic event from the IO-Link device exists.

Under "Parameter server content" you can view the content of the parameter server if
parameter data is stored on the parameter server.

www.balluff.com 30
Balluff Network Interface ProfiNet™

7 Web Server

7.6. "Configuration" The configuration page permits configuration of the module. You can change the displayed
dialog module information texts and module parameters.
The "Set Ports" action is not permanently stored in the device and is lost after the next reboot.

The parameter set “Module Configuration” on the left side is used by pressing "Save
Configuration" and permanently stored in the device.

The "Reboot" button restarts the device like after power has been turned off and on again.

Pressing "Factory Reset" deletes the configuration stored in the device, all uploaded IODD
files as well as saved log files and then performs a reboot, so that the device is again in the
default factory configuration.

www.balluff.com 31
7 Web Server

7.7. "Diagnostics" This dialog is used for displaying the internal module diagnostics capabilities and shows
dialog events as they have occurred over time. A tool for detailed troubleshooting in equipment is
provided.

Events are classified using the "Severity“ column as follows:

1) Internal error: The fieldbus module has detected a fault in itself (hardware or
software) which should not occur during normal operation. If this happens, the
module must be serviced or replaced. These errors are classified as "Emergency“,
"Alert“ or "Critical“.

2) External error: The fieldbus module has detected what may be a non-permissible
event which is affecting the module from the outside. The system may require
troubleshooting. This error is classified as "Error“ or "Warning“.

3) Event: The fieldbus module has detected an important normal operating event and
reports it. These may include also configuration actions over the web interface and
other configuration interfaces which are also recorded. These messages are
classified as "Notice“.

Pressing "Set Module Time“ sends the current browser time to the fieldbus module.

Pressing "Update Log" updates the display.

www.balluff.com 32
Balluff Network Interface ProfiNet™

8 Diagnostics

8.1. Diagnostics The diagnostics messages that are generated by the module in the event of an error are
messages usually read out by the PLC and processed. It is also possible to read out the diagnosis from
the module by means of function modules and evaluate it.

The diagnostics message is 34 bytes long and divided into 3 blocks:

Block Header, Alarm Specifier, Channel Properties

Byte Value Meaning Block

0 00
Block Type
1 02
2 00
Block Length
3 1E
4 01 Block Version High
5 00 Block Version Low
6 00
Alarmtype
7 01
8 00
9 00
API
10 00
11 00
12 00 BlockHeader
Slotnumber
13 01
14 00
Subslotnumber
15 01
16 00
17 00
Module Ident
18 00
19 17
20 00
21 00
Submodule Ident
22 00
23 01
24 XX
AlarmSpecifier
25 36
26 80
User Structure Ident AlarmSpecifier
27 00
28 XX
Channelnumber
29 XX
30 08
ChannelProperties
31 00
ChannelProperties
32 00
ChannelErrorType
33 1A

www.balluff.com 33
8 Diagnostics

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

Block Type The first 2 bytes of the Block Header are described by the Block Type to define the data
type.

Possible values Meaning

0x0002 Alarm Notification Low

Block Length 2 bytes of data that define the length of the following diagnostics message.
(for the complete diagnostics message, the 2 bytes from the Block Type and the 2 bytes
from the Block Length must be added).

Block Version Low Byte fixed at 0x01, High Byte fixed at 0x00

Alarm Type 2 bytes; the information on the type of alarm is provided here

Possible values Meaning

0x0001 Diagnostics

API 4 bytes, default is 0.

Possible values Meaning

0x00000000 Default value

Slot 2 bytes of data that describe which slot of the module reports an error

BNI PNT-507-005-Z040
Possible values Meaning
0x0001 Slot 0 (Header module)
0x0002 Slot 1 - 4 (IO-Link Ports 0 - 3)
0x0003 Slot 1 - 4 (IO-Link Ports 0 - 3)
0x0004 Slot 1 - 4 (IO-Link Ports 0 - 3)
0x0005 Slot 1 - 4 (IO-Link Ports 0 - 3)
0x0006 Slot 5 - 20 (Standard IO-Modules)
0x0007 Slot 5 - 20 (Standard IO-Modules)
0x0008 Slot 5 - 20 (Standard IO-Modules)
0x0009 Slot 5 - 20 (Standard IO-Modules)
0x0010 Slot 5 - 20 (Standard IO-Modules)
0x0011 Slot 5 - 20 (Standard IO-Modules)
0x0012 Slot 5 - 20 (Standard IO-Modules)
0x0013 Slot 5 - 20 (Standard IO-Modules)
0x0014 Slot 5 - 20 (Standard IO-Modules)
0x0015 Slot 5 - 20 (Standard IO-Modules)

Subslot 2 bytes of data that describe which subslot of the slot reports an error

Possible values Meaning

0x0001 Subslot 1

www.balluff.com 34
Balluff Network Interface ProfiNet™

8 Diagnostics

Module ID 4 bytes of data that describe which module is inserted in the respective slot.
(The module ID is saved in the GSDML)

Possible values Meaning

0x00000017 BNI PNT-xxx-xxx-xxxx
0x00000025 IOL IN 1 OUT 0
0x00000026 IOL IN 2 OUT 0
0x0000003A IOL IN 4 OUT 0
0x0000003B IOL IN 6 OUT 0
0x00000027 IOL IN 8 OUT 0
0x00000035 IOL IN 10 OUT 0
0x00000037 IOL IN 16 OUT 0
0x0000003C IOL IN 24 OUT 0
0x00000028 IOL IN 32 OUT 0
0x00000029 IOL IN 0 OUT 1
0x0000002A IOL IN 0 OUT 2
0x0000003D IOL IN 0 OUT 4
0x0000003E IOL IN 0 OUT 6
0x0000002B IOL IN 0 OUT 8
0x00000036 IOL IN 0 OUT 10
0x00000038 IOL IN 0 OUT 16
0x0000003F IOL IN 0 OUT 24
0x0000002C IOL IN 0 OUT 32
0x0000002D IOL IN 1 OUT 1
0x0000002E IOL IN 2 OUT 2
0x00000040 IOL IN 2 OUT 4
0x00000041 IOL IN 4 OUT 2
0x00000042 IOL IN 4 OUT 4
0x0000002F IOL IN 2 OUT 8
0x00000043 IOL IN 4 OUT 8
0x00000030 IOL IN 8 OUT 2
0x00000044 IOL IN 8 OUT 4
0x00000045 IOL IN 8 OUT 8
0x00000031 IOL IN 4 OUT 32
0x00000032 IOL IN 32 OUT 4
0x00000039 IOL IN 16 OUT 16
0x00000046 IOL IN 24 OUT 24
0x00000033 IOL IN 32 OUT 32
0x00000059 Output pin 4
0x0000005A Output pin 2
0x0000005B Input pin 4
0x0000005C Input pin 2

Submodule ID 4 bytes of data that describe which submodule is used with the respective module.
(The submodule ID is saved in the GSDML)

Possible values Meaning

0x00000001 BNI PNT-xxx-xxx-xxxx

www.balluff.com 35
8 Diagnostics

8.3. AlarmSpecifier 2 bytes, subdivided as follows:

Sequence Number Bit 0-10, this counter is incremented with every new diagnostic message.

Channel Diagnostic Bit 11

Possible values Meaning

0x00 No diagnosis related to channel is pending
0x01 Diagnosis related to channel is pending

Manufacturer- Bit 12
Specific Diagnosis
Possible values Meaning
0x00 No diagnosis related to manufacturer is pending
0x01 Diagnosis related to channel is pending

Submodules Bit 13
Diagnostic State
Possible values Meaning
0x00 No further diagnosis of submodule present
At least one further diagnosis of the submodule
0x01
present

Bit 14 reserved

ARDiagnosis State Bit 15

Possible values Meaning

0x00 No further diagnosis of module is present
At least one further diagnosis of the module is
0x01
present

User Structure ID 2 bytes, describes the type of diagnosis

Possible values Meaning

0x8000 Channel-related diagnosis

www.balluff.com 36
Balluff Network Interface ProfiNet™

8 Diagnostics

8.4. Channel Number Configuration as standard I/O

Error Type Channel Number

Undervoltage US 8000
Undervoltage UA 8000
No UA 8000
Sensor Short circuit Pin 1 - 3 0…..n
Actor Short circuit Pin 2 - 3 0…..n
Actor Short circuit Pin 4 - 3 0…..n
n = number of IOL ports

Configuration as IO-Link

Error Type Channel Number

Line break 0
Short circuit IOL Pin 4 - 3 0
Sensor short circuit Pin 1 - 3 0
IOL Device wrong configuration 0

Diagnostics for IO-Link devices

Error Type Channel Number

Short circuit 1
Undervoltage 1
Upper threshold exceeded 1
Lower threshold undershot 1

www.balluff.com 37
8 Diagnostics

8.5. Channel 2 bytes, subdivided as follows:

Properties

Type
Possible Meaning
values
Used if the channel number is 0x8000 or none of the types defined
0x00
below is relevant.
0x01 1 bit
0x02 2 bits
0x03 4 bits
0x04 8 bits
0x05 16 bits
0x06 32 bits
0x07 64 bits
0x08 – 0xFF Reserved
Bit 0-7

Accumulative Bit 8 not used, always 0.

Maintenance
Possible values
Meaning
Bit 9 Bit 10
0x00 0x00 Diagnostics
Bit 9-10

Specifier
Possible
Meaning
values
0x00 Not used
0x01 Diagnosis appeared
0x02 Diagnosis left
0x03 Diagnosis left, but another is still active
Bit 11-12

Direction
Possible
Meaning
values
0x00 Manufacturer-specific
0x01 Channel used as input
0x02 Channel used as output
0x03 Channel used as input and output
Bit 13-15

www.balluff.com 38
Balluff Network Interface ProfiNet™

8 Diagnostics

8.6. Channel Error

Type Error code in hex Description
0x0000 Unknown error
0x0001 Short-circuit
0x0002 Undervoltage
0x0003 Overvoltage
0x0004 Overload
0x0005 Temperature limit exceeded
0x0006 Cable break
0x0007 Upper threshold exceeded
0x0008 Lower threshold undershot
0x0009 Error
0x001A External error
0x001B Sensor has incorrect configuration (IO-Link device)
0x0101 Actuator warning
0x0105 Actuator supply undervoltage
0x0104 No actuator power supply

www.balluff.com 39
9 Configuration of IO-Link devices

Options IO-Link devices can be configured via the web server, function modules
and the IO-Link device tool.

When using the device tool and the web server, most of the
parameters that are required are taken over by the software.

The sample project with the IO_Call function module from Siemens AG can be downloaded
on the Balluff homepage.

The web server and the IO-Link device tool access the module directly,
the function module is used to compile a telegram which is sent via DPV1 functions to the
master.

Telegram structure

Area Size in bytes Value (dec) Definition

Call header 1 08h 08h for "CALL", fixed
1 0 IOL master
1…63 Port number
64…255 Reserved
2 65098 FI_Index, IO-Link header is following
IO-Link header 1 0…255 Task
2 = write
3 = read
2 0…32767 IO-Link index
65535 Port function
1 0…255 IO-Link subindex
Data range 232 Range of the data to be written or
read

Read To read out data, the master must be given a reading task for the corresponding
slot/index/subindex.

The telegram must be adapted accordingly for this purpose (slot, index),
and 0x03 for reading must be entered under "Task".
The telegram can then be sent by write instruction to the
corresponding module.

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

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

Write To write data, the master must be given a writing task for the corresponding
slot/index/subindex.

The telegram must be adapted accordingly for this purpose (slot, index),
and 0x02 for writing must be entered under "Task".
The telegram can then be sent by write instruction to the
corresponding module.

www.balluff.com 40
Balluff Network Interface ProfiNet™

10 Appendix

10.1. Included in the The BNI PNT comprises the following elements:
Scope of Delivery • IO-Link block
• 4x M12 dummy plugs
• Ground strap
• M4x6 screw
• 20 informational signs

10.2. Order number BNI PNT-5xx-005-Z040

Balluff Network Interface

ProfiNet

Functions
507 = IP 67 IO-Link master module, 4 IO-Link ports, Class A
527 = IP 67 IO-Link master module, 4 IO-Link ports, Class B

Variants
005 = 2-Port-Switch

Mechanical version
Z040 = Die-cast zinc
Data transmission: 2 x M12 internal thread
Power connection: 7/8" male thread / female thread
Sensor connections: 4 x M12 internal thread

10.3. Ordering Product order code Order code

information
BNI PNT-507-005-Z040 BNI0092
BNI PNT-527-005-Z040 BNI00A9

www.balluff.com 41
Notes

www.balluff.com 42
 Balluff Network Interface ProfiNet™

www.balluff.com

No. 931209 E Edition I16 Subject to modification.

Balluff GmbH
Schurwaldstrasse 9
73765 Neuhausen a.d.F.
Germany
Tel. +49 7158 173-0
Fax +49 7158 5010
www.balluff.com
[email protected]