EIO344 - Bluetooth Adapter IFM - Free user manual and instructions

USER MANUAL EIO344 IFM

Operating instructions

Bluetooth® Mesh IO-Link adapter

EIO344

Firmware: 1.15

Contents

1 Preliminary note 4

1.1 Legal and copyright information 4
1.2 Symbols used 4
1.3 Warnings.... 4

2 Safety instructions.... 5

2.1 Cybersecurity 5
2.2 Safety symbol on the device 6

3 Intended use.... 7

3.1 Foreseeable misuse 7
3.2 Example application 7

4 Function 8

4.1 Visual indication 8
4.2 IO-Link interfaces 8

4.2.1 IO-Link 8

4.3 Bluetooth LE 9
4.4 Bluetooth mesh....9
4.5 ifm IoT-Core 9

5 Installation.... 10
6 Electrical connection.... 11

6.1 Overview.... 11
6.2 General notes on wiring 11
6.3 Process connection.... 11
6.4 Power supply / control signals.... 12

7 Operating and display elements 13

7.1 Overview.... 13
7.2 Status LED 13

8 Set-up.... 14
9 Parameter setting 15

9.1 Notes on parameter setting.... 15

9.1.1 Installing ifm moneo|blue.... 15
9.1.2 Installing ifm moneo|configure.... 15
9.1.3 Bluetooth password.... 16
9.1.4 Integrating the device into a Bluetooth Mesh network 16
9.1.5 Device validation and data storage 17

9.2 Parameter setting: Bluetooth LE interface.... 18

9.2.1 Available parameters and commands 18

9.2.1.1 Identification information 18
9.2.1.2 Bluetooth Mesh network 19
9.2.1.3 Switching output 19
9.2.1.4 Device validation and data storage 19
9.2.1.5 Adapter 20

9.3 Parameter setting: IO-Link interface 21

9.3.1 Available parameters and commands 21

9.3.1.1 Identification 21
9.3.1.2 Parameter.... 22
9.3.1.3 Diagnostics 22
9.3.1.4 Process data.... 23

9.4 Parameter setting: ifm IoT-Core 24

9.4.1 Available parameters and commands 24

9.4.1.1 Identification information 24
9.4.1.2 Adapter 25
9.4.1.3 Bluetooth LE 26
9.4.1.4 Bluetooth Mesh network 27
9.4.1.5 Switching output 28
9.4.1.6 IO-Link master 29
9.4.1.7 IO-Link device 32

10 Troubleshooting 33
11 Maintenance, repair and disposal 34
11.1 Firmware update.... 34

1 Preliminary note

You will find instructions, technical data, approvals and further information using the QR code on the unit / packaging or at documentation.ifm.com.

1.1 Legal and copyright information

© All rights reserved by ifm electronic gmbh. No part of these instructions may be reproduced and used without the consent of ifm electronic gmbh.

• Bluetooth® is a registered trademark of Bluetooth SIG Inc.
• Apple ^® , the Apple logo, iPhone and iPod Touch are trademarks of Apple Inc., registered in the U. S. and other countries. The App Store is a service mark of Apple Inc.
• iOS® operating system is a registered trademark of Apple Inc.
• Google® is a registered trademark of Google LLC.
• Android® operating system is a registered trademark of Google LLC.
  • Android, Google Play and the Google Play logo are trademarks of Google Inc.

1.2 Symbols used

√ Requirement

Instructions

Reaction, result

[...] Designation of keys, buttons or indications

→ Cross-reference

Important note

Non-compliance may result in malfunction or interference.

Information

Supplementary note

1.3 Warnings

Warnings indicate the possibility of personal injury and damage to property. This enables safe product handling. Warnings are graded as follows:

WARNING

Warning of serious personal injury

▷ If the warning is not observed, fatal and serious injuries are possible.

CAUTION

Warning of minor to moderate personal injury

▷ If the warning is not observed, minor to moderate injuries are possible.

ATTENTION

Warning of damage to property

▷ If the warning is not observed, damage to property is possible.

2 Safety instructions

- The unit described is a subcomponent for integration into a system.

• The system architect is responsible for the safety of the system.

• The system architect undertakes to perform a risk assessment and to create documentation in accordance with legal and normative requirements to be provided to the operator and user of the system. This documentation must contain all necessary information and safety instructions for the operator, the user and, if applicable, for any service personnel authorised by the architect of the system.

• Read this document before setting up the product and keep it during the entire service life.

• The product must be suitable for the corresponding applications and environmental conditions without any restrictions.
• Only use the product for its intended purpose (→ Intended use).
• If the operating instructions or the technical data are not adhered to, personal injury and/or damage to property may occur.
• The manufacturer assumes no liability or warranty for any consequences caused by tampering with the product or incorrect use by the operator.
  • Installation, electrical connection, set-up, programming, configuration, operation and maintenance of the product must be carried out by personnel qualified and authorised for the respective activity.
• Protect units and cables against damage.
• Replace damaged units, otherwise the technical data and safety will be impaired.
• Observe applicable documents.

2.1 Cybersecurity

Installation

The device is suitable for operation in a secure environment according to IEC 62443-1-1.

▶ Carry out a risk assessment of the system according to IEC 62443-1-1.
The device was designed for operation behind a firewall.
▶ Take measures to ensure physical security.
The device has no built-in protection against unauthorised access.
▶ Only operate the device in trustworthy networks.

Examples of trustworthy networks (according to IEC 62443-3-1, part 5):

• Internal company networks (Local Area Networks - LANs)

– Networks managed and secured by the IT department

• Industrial control systems (Industrial Control Systems - ICS)

– Networks for the control and monitoring of industrial processes
– ICS are isolated from other networks

- Point-to-point connection between the device and its direct communication partner

Bluetooth LE interface

The Bluetooth LE interface uses the JustWorks pairing method to establish cryptographically secured communication between the device and ifm moneo|blue.

▶ Only establish a connection between the device and ifm moneo|blue in a secure environment.

The device's Bluetooth LE interface is password-protected. When logging on to the device for the first time, the user must change the factory-set password.

▶ Only change the password in a secure environment.
▶ Choose a strong password in accordance with company policy.

Bluetooth Mesh interface

The Bluetooth Mesh communication between the network participants is cryptographically secured after successful provisioning of the devices in the Bluetooth Mesh network.

▶ Only provision the devices in a secure environment for the Bluetooth mesh network.

Operation

▶ Observe the security functions described in the product documentation and the recommendations for their use.

Maintenance

• ▶ Back up system configuration and system data in accordance with your company’s change management processes.
  ▶ Regularly check whether software updates are available for the device.
  Ensure the integrity and authenticity of the software update by taking the following organisational measures:
  ▶ Download the new firmware file to a secure laptop/PC.
  ▶ Calculate the SHA-256 hash value for the downloaded firmware file, www.ifm.com/cnt/product-security.
  ▶ Check whether the calculated hash value matches the SHA-256 hash value provided on the ifm website.
  ▶ Install the firmware file on the device via a secure connection, e.g. a point-to-point connection.

Decommissioning

▶ Ensure that no sensitive information can fall into unauthorised hands.
▶ Always reset the system settings to the factory settings before decommissioning the device.

2.2 Safety symbol on the device

Safety symbol on the device:

▶ Adhere to the operating instructions for the safe operation of the device.

3 Intended use

The device can be used:

• As a participant in a Bluetooth Mesh network of a Bluetooth Mesh IoT base station
• As a gateway between a connected IO-Link device and the Bluetooth Mesh IoT base station
- To configure the connected IO-Link device
- For monitoring the connected IO-Link device (process data, status and diagnostic information)
• As a repeater without a connected IO-Link device in a Bluetooth Mesh network
- indoors
- Only use the device within the limits of the technical data: → Technical data.

Permitted use:

Notes relevant for approval: Package insert of the device and documentation.ifm.com

3.1 Foreseeable misuse

The device is not suitable for environments with special requirements for mechanical stability (e.g. shock/vibration).

The device is not suitable for use in critical applications. The data is not transmitted in real time.

3.2 Example application

1: IO-Link device
2: EIO344
3: Programmable Logic Controller (PLC)
4: Power supply
5: Bluetooth mesh IoT base station EIO404
6: Mobile device with ifm moneo|blue

4 Function

4.1 Visual indication

The device has a status LED for displaying status information, warnings and error states.

4.2 IO-Link interfaces

The device has 2 IO-Link interfaces.

Power supply / control signals (plug)

• Voltage supply
• Switching output OUT1
• Output OUT2 for analogue and digital signals (looped through from pin 2 of the process connection)
• IO-Link communication for parameter setting, control and monitoring of the device by an IO-Link master

Process connection (socket)

• Communication with an IO-Link device
- The device offers the "Device validation and data storage" function. The function offers the option of validating the IO-Link device connected to the device (manufacturer, identical design). In addition, data records of the connected IO-Link device can be backed up and restored to an identical IO-Link device if required.

4.2.1 IO-Link

IO-Link is a communication system for connecting intelligent sensors and actuators to automation systems. IO-Link is standardised in the IEC 61131-9 standard.

General information on IO-Link at io-link.ifm

Input Output Device Description (IODD) with all parameters, process data and detailed descriptions of the device at documentation.ifm.com

IO-Link offers the following advantages:

• Interference-free transmission of all data and process values
• Parameter setting in the running process or presetting outside the application
- Parameters for identifying the connected devices in the system
• Additional parameters and diagnostic functions
• Automatic backup and restore of parameter sets in case of device replacement (data storage)
- Logging of parameter sets, process values and events
• Device description file (IODD - Input Output Device Description) for easy project planning
• Standardised electrical connection
- Remote maintenance

4.3 Bluetooth LE

The device supports communication via Bluetooth Low Energy (LE). The following functions can be performed via Bluetooth LE:

• Parameter setting of the adapter
• Parameter setting of the IO-Link interface of the device
• Parameter setting of the connected IO-Link device

4.4 Bluetooth mesh

The device supports the Bluetooth Mesh protocol.

Together with an EIO404 Bluetooth Mesh IoT base station and additional EIO344 Bluetooth Mesh IO-Link adapters, the device can be operated in a Bluetooth Mesh network.

The device offers the following functions in a Bluetooth Mesh network:

• Parameter setting of the adapter
• Parameter setting of the connected IO-Link device
• Monitoring of process data (interval: 1 s ... 24 h)

Detailed information on the Bluetooth Mesh IoT base station EIO404: documentation.ifm.com

4.5 ifm IoT-Core

The device has the ifm IoT-Core. The ifm IoT-Core represents the functionality of the device. The functionality consists of a set of data, services and events. The elements of the ifm IoT-Core are arranged in a JSON object in a hierarchical tree structure. The ifm IoT-Core makes these elements available to the outside world via standard interfaces (e.g. HTTP). This allows the user and other devices to access data (parameters, process data), events and functions (services) of the device.

The functions of the ifm IoT-Core of the device are only available via the Bluetooth Mesh IoT base station EIO404.

5 Installation

For installation, the following optional accessories are available. documentation.ifm.com

6 Electrical connection

The unit must be connected by a qualified electrician.

Observe the national and international regulations for the installation of electrical equipment.

Voltage supply according to SELV, PELV.

▶ Disconnect power.

6.1 Overview

1: Process connection
2: Power supply / controller

6.2 General notes on wiring

The threaded connections in the device correspond to the M12 standard. To ensure compliance with the specified protection rating, only cables that comply with this standard may be used. In the case of self-assembled cables, the system manufacturer is responsible for the protection rating.

▶ Use connectors with gold-plated contacts.
▶ During installation, place the connectors vertically so that the coupling nut will not damage the thread.
▶ Before connecting the connector, check that there is an undamaged O-ring in the socket.
▶ Observe the coding of the connectors during installation.
▶ Provide all outgoing cables with suitable strain relief after a maximum of 200 mm.

For the cULus area of application:

▶ Only use UL-certified cables of category CYJV 2/7/8 with suitable technical data to connect the device.

6.3 Process connection

The device is connected to an IO-Link device via the process connection.

• Maximum cable length 20 m

The device must not be externally supplied via the M12 port. Pins 1, 2 and 3 are connected through.

Wiring:

1: L+ supply
2: OUT2 linked through
3: L- supply
4: IO-Link
5: n.c.

▶ Connect the connector with the device.
▶ For connection, use an M12 connector (minimum protection rating: IP67 / IP69K).
▶ Tighten the coupling nut.

• min. tightening torque: 0.6 Nm (tightening by hand)
  • max. tightening torque: 1.5 Nm (using a torque wrench).

When used as a Bluetooth repeater:

▶ Close the unused connection with a protective cap ( → Accessories).

6.4 Power supply / control signals

The device is connected to the power supply and, if necessary, to a control device (PLC, IO-Link master) via the port.

• Max. cable length for digital signals: 200 m
- Max. cable length for analogue signals: no recommendation, depending on receiver.

CAUTION

The port has no overcurrent protection.

▷ Risk of fire
▶ Protect circuits.

Wiring:

1: L+ supply
2: OUT2 linked through
3: L- supply
4: OUT1 switching output or IO-Link

▶ Connect the port to the supply voltage / controller.
▶ For connection, use an M12 connector (minimum protection rating: IP67 / IP69K).
▶ Tighten the coupling nut.

- min. tightening torque: 0.6 Nm (tightening by hand)

• max. tightening torque: 1.5 Nm (using a torque wrench).

7 Operating and display elements

7.1 Overview

1: LED: Status

7.2 Status LED

LED	Description	Colour	State	Type	Description
Status		-	Off	Error	Voltage too low
	Operation indication	Green	On	Normal operation	Device functions reliably
			Flashing (double flashing)	Warning	Optical identification
			Flashes (200 ms on, 800 ms off)	Note	Firmware updateNOTE! Wait until the connection is established.
	Interference display	Red	On	Device replacement	Hardware failure1
			Flashes (1 Hz)	Error	Temperature of the circuit board outside the tolerance range
			Flashes (1 Hz)	Note	Short circuit at the switching output
			Flashes (1 Hz)	Note	Invalid IO-Link process data1
			Flashes (1 Hz)	Note	Incorrect data storage
			Flashes (1 Hz)	Note	Invalid output configuration1
			Flashes (1 Hz)	Warning	No Bluetooth Mesh connection
	Bluetooth status	Blue	On	Note	Bluetooth active
			Flashes (double flash, once)	Note	Mesh provisioning successful (following device ID message)

Output response: The switching output OUT1 assumes the specified value in the event of an error ( → parameter FOU1)

8 Set-up

For initial set-up:

▶ Attach the sticker supplied in the packaging to the device.
▶ Connect the device properly.

▷ The device starts.
▷ The status LED shows the status of the device.

▶ Access the device with the selected parameter setting option.

▶ Change the factory-set password for the Bluetooth interface, Bluetooth password (→ ☐ 16).

▷ The security mode of the Ethernet interface is enabled.

▷ The device can be configured.

9 Parameter setting

▷ The device can be configured via the following interfaces:

- Bluetooth LE interface:

- ifm moneo|blue

- IO-Link interface

- ifm moneo|configure

- Ethernet interface (ifm IoT-Core):

- ifm IoT Core Visualizer

- ifm IoT Core REST API

The parameter setting can be carried out with or without a sensor or actuator connected.

9.1 Notes on parameter setting

9.1.1 Installing ifm moneo|blue

ifm electronic provides the ifm moneo|blue app for accessing the device via the Bluetooth interface. The app is available in the Apple App Store and the Google Play Store.

moneo|blue

To install ifm moneo|blue:

▶ Scan the QR code using your mobile device.
▷ The app page in the App Store or Google PlayStore opens.
▶ Install ifm moneo|blue.
▷ ifm mono|blue is installed on the mobile device.

9.1.2 Installing ifm moneo|configure

Information on ifm moneo|configure: ifm.com/cnt/moneo

▶ Download ifm moneo|configure.
▶ Start the laptop/PC.
▶ Log in with administrator rights.
▶ Install and licence ifm moneo|configure (→ installation instructions ifm moneo).
▷ ifm moneo|configure is installed.

9.1.3 Bluetooth password

Access to the device via Bluetooth LE is password-protected. The password protection cannot be deactivated.

The factory-set Bluetooth password consists of the last 6 digits of the device's serial number (e.g. 100000138488).

The serial number is printed on the packaging and on the device.

Fig. 1: Indication of the serial number: on the device (left) and on the packaging (right)

When accessing the device via ifm moneo|blue for the first time, the user is prompted to change the factory-set password.

▶ Choose a strong password in accordance with company policy.

The user-specific password can be reset to the factory-set password using the command Back-to-Box. The user name "Administrator" associated with the password cannot be changed.

The Bluetooth password has no influence on access to the device via the IO-Link and the IoT-Core interface.

9.1.4 Integrating the device into a Bluetooth Mesh network

To integrate the Bluetooth Mesh IO-Link adapter as a participant in a Bluetooth Mesh network, the device must be provisioned for the network via a Bluetooth Mesh IoT base station.

Options for provisioning a Bluetooth Mesh IO-Link adapter: → Operating instructions EIO404

General procedure for provisioning a Bluetooth Mesh IO-Link adapter (example ifm moneo|blue):

Requirements:

√ ifm moneo|blue is installed on the mobile device, Installing ifm moneo|blue (→ 15).
√ Bluetooth Mesh IoT base station EIO404 is started and ready for operation.
▶ Position the Bluetooth Mesh IO-Link adapter EIO344 near the base station (distance: max. 15 m).

Fig. 2: Step 1 Establishing a connection to the Bluetooth Mesh IoT base station EIO404

▶ Use the parameter setting software to establish a connection to the Bluetooth Mesh IoT base station.
▷ The parameter setting software has access to the Bluetooth Mesh IoT base station.

Fig. 3: Step 2: Search for available Bluetooth Mesh IO-Link adapters EIO344

Fig. 4: Step 3: Provision the Bluetooth Mesh IO-Link adapter

▶ Use the parameter setting software to search the Bluetooth Mesh IoT base station's environment for available Bluetooth Mesh IO-Link adapters.

▷ All available adapters that have not yet been provisioned are displayed.

▶ Provision the adapter.
▷ The Bluetooth Mesh IoT base station integrates the adapter into the Bluetooth Mesh network.
▷ The parameter setting software has access to the adapter and the connected IO-Link device.

After provisioning, the Bluetooth Mesh IoT base station automatically establishes a connection to the Bluetooth Mesh IO-Link adapter. The connection is established directly or via additional Bluetooth Mesh IO-Link adapters EIO344.

Cyclical process data is sent to the Bluetooth Mesh IoT base station at defined time intervals. The process data can be read out there and used for system monitoring.

9.1.5 Device validation and data storage

The user can choose how the IO-Link ports are to behave with regard to the device validation and the storage / recovery of parameter data of the connected IO-Link device.

The following options are available:

Option	Validation of the IO-Link device	Backing up the parameter data	Restoring the parameter data
[No check and clear]	No	No	No
[Type compatible V1.0 device]	Yes, check for compatibility with IO-Link standard V1.0.	No	No
[Type compatible V1.1 device]	Yes, check for compatibility with IO-Link standard V1.1.	No	No
[Type compatible V1.1 device with Backup + Restore]	Yes, check for compatibility with IO-Link standard V1.1 and identity of design (vendor ID and device ID).	Yes, automatic storage of the parameter data; changes to the current parameter data are saved.	Yes, recovery of the parameter data when connecting an identical IO-Link device with factory settings.
[Type compatible V1.1 device with Restore]	Yes, check for compatibility with IO-Link standard V1.1 and identity of design (vendor ID and device ID).	No, there is no automatic backup; changes of the current parameter data will not be stored.	Yes, recovery of the parameter data when connecting an identical IO-Link device with factory settings.

9.2 Parameter setting: Bluetooth LE interface

The device can be accessed via the Bluetooth LE interface either directly or indirectly via an EIO404 Bluetooth Mesh IoT base station.

The ifm moneo|blue app is required for parameter setting via the Bluetooth LE interface, Installing ifm moneo|blue ( → ☐ 15).

Fig. 5: Direct connection to the device

Fig. 6: Indirect connection to the device via EIO404

To access the device via the Bluetooth LE interface:

Requirements:

√ ifm moneo|blue is installed on the mobile device, .
√ Bluetooth is activated on the mobile device.
√ The device is close to the mobile device (distance: max. 15 m).
▶ Connect the Bluetooth Mesh IO-Link adapter to the supply voltage.
▶ Start ifm monoe|blue.

For direct access to the device:

▶ Search for the Bluetooth Mesh IO-Link adapter in moneo|blue and pair it with the mobile device.
▷ ifm moneo|blue has access to the device.

For indirect access to the device via a Bluetooth Mesh IoT Base Station:

▶ Search for the Bluetooth Mesh IoT Base Station in moneo|blue and pair it with the mobile device.
▷ ifm moneo|blue has access to the Bluetooth Mesh IoT Base Station.
▶ Search for the Bluetooth Mesh IO-Link adapters and provision the device found.
▷ ifm moneo|blue has access to the device.

9.2.1 Available parameters and commands

9.2.1.1 Identification information

Name	Description	Value range	Access
[Product name]	Product name	EIO344	ro 1
[Vendor]	Vendor	ifm electronic gmbh	ro 1
[Serial number]	Serial number	E.g. 100000138488	ro 1
[Hardware Revision]	Hardware version	E.g. AA	ro 1
[Firmware Version]	Firmware version	E.g. V1.36	ro 1
[Adapter name]	Device-specific name for display in Bluetooth Mesh networks Factory setting: Serial number of the device, e.g. ifm SN: 100000138488 )	E.g. mesh_adapter01	rw1

1 Read only

9.2.1.2 Bluetooth Mesh network

Name	Description	Value range	Access
[Mesh send interval]	Interval at which process data is sent from the adapter to the Bluetooth mesh IoT base station (value in ms)	1000 ms86400000 ms	rw1
[Link Quality]	Connection quality of the adapter in the mesh network (value in %)	0%100%	ro2

¹ Read and write
² Read only

9.2.1.3 Switching output

Name	Description	Value range	Access
[Output config]	Configuration of the switching output	Auto: The values for the parameters [FOU1] and [switching bit] are set automatically Manual: The user sets the parameters [FOU1] and [switching bit] manually Off: Switching output deactivated	rw1
[Switching bit]	Position of the value of the switching signal in the IO-Link data	0...255	rw1
[FOU1]	Behaviour of the switching output OUT1 in case of a fault	OFF: OffON: On	rw1

1 Read and write

9.2.1.4 Device validation and data storage

Name	Description	Value range	Access
[Validation / Datastorage]	Behaviour of the port when connecting an IO-Link device in the as-delivered stateNOTE! Observe the notes on validation and data storage: Device validation and data storage (→ 17)	No check and clear Type compatible V1.0 device Type compatible V1.1 device Type compatible V1.1 device with Backup + Restore Type compatible V1.1 device with Restore	rw 1
[Vendor ID]	IO-Link ID of the manufacturer that is to be validated	0...655535	rw 1
[Device ID]	IO-Link ID of the device to be validated	0...16777215	rw 1

1 Read and write

9.2.1.5 Adapter

Name	Description	Value range	Access
[Device Status]	Display of the current device and diagnostic state	Device OKBluetooth LE connectedNo valid IO-Link process data availableNo IO-Link process data available Master port no device connected Mesh not provisioned Mesh connection lost Switching output wrong setup Master wrong data storage setup Mesh bad signal Mesh sending problems Mesh too much traffic Master port short circuit Switching output short circuit Under temperature Over temperature UndervoltageHardware Error	ro 1
[Operating hours]	Operating hours since delivery (value in h)	e.g. 10 h	ro 1
[Internal Temperature]	CPU temperature of the device (value in °C)	e.g. 35°C	ro 1

1 Read only

Commands:

Name	Description
[Back to box reset]	All settings are reset to the factory settings and communication is blocked until the next time the device is switched off and on. (Back-to-Box)
[Application reset]	All settings are reset to the factory settings, except for the following parameters:• Application-Specific Tag• Function Tag• Location Tag• Bluetooth password• Bluetooth Mesh network

9.3 Parameter setting: IO-Link interface

The device has the profile of an IO-Link device. ifm provides a device description file (IODD - IO Device Description).

Parameter setting is carried out using suitable software, e.g. ifm moneo|configure. For parameter setting via the IO-Link interface, the device must be connected to an IO-Link master.

Fig. 7: Application example: Parameter setting with a PC

To configure the device via the IO-Link interface:

Requirements:

√ ifm moneo|configure is installed and licensed from the PC/laptop, Installing ifm moneo|configure (→ 15).
▶ Connect the device with an IO-Link master.
▶ Connect the IO-Link master to the laptop/PC.
▶ Start ifm moneo|configure and update the device catalogue.
▶ Establish a connection to the IO-Link master in ifm moneo|configure.

▷ ifm moneo|configure recognises the IO-Link master and the connected device.

▶ Call up the editor view of the device.

▷ The device can be configured.

9.3.1 Available parameters and commands

A detailed description of all parameters, process data, system commands and the available events is provided in the IO-Link interface description of the device: documentation.ifm.com

As an IO-Link device, the device offers the following data.

9.3.1.1 Identification

Name	Description	Value range	Access
[Vendor Name]	Vendor	ifm electronic gmbh (default)	ro 1
[Vendor Text]	Vendor	www.ifm.com (default)	ro 1
[Product Name]	Product name	EIO344	ro 1
[Product ID]	Product code	EIO344	ro 1
[Product Text]	Product designation	Bluetooth Mesh IO-Link Adapter	ro 1
[Serial Number]	Serial number	e.g. 000194610104	ro 1
[Hardware Revision]	Hardware version	E.g. AA	ro 1
[Firmware Revision]	Firmware version	E.g. V1.36	ro 1
[Application-Specific Tag]		*** (Default)	rw 2
[Function Tag]		*** (Default)	rw 2
[Location Tag]		*** (Default)	rw 2

¹ Read only
² Read and write

System commands:

Name	Description
[Flash On]	Switch on status LED (ID 222)
[Flash Off]	Switch off status LED (ID 223)

9.3.1.2 Parameter

System commands:

Name	Description
[Application reset]	All settings are reset to factory settings, except for the application-specific indicator, system indicator, location indicator, Bluetooth password, Bluetooth Mesh network (ID 129)
[Back-to-Box]	All settings are reset to factory settings and communication is blocked until the next switch-off and switch-on (ID 131)
[Reset Bluetooth Password]	Reset the Bluetooth password to the factory setting (last 6 digits of the serial number) (ID 208)
[IO-Link 1.1 system test command 240, event 8DFE appears]	System test event 8DFE appearing (ID 240)
[IO-Link 1.1 system test command 241, event 8DFE disappears]	System test event 8DFE disappearing (ID 241)
[IO-Link 1.1 system test command 242, event 8DFF appears]	System test event 8DFF coming (ID 242)
[IO-Link 1.1 system test command 243, event 8DFF disappears]	System test event 8DFF disappearing (ID 243)

9.3.1.3 Diagnostics

Name	Description	Value range	Access
[Device Status]	status of the device	0: Device is OK1: Maintenance required2: Out of specification3: Functional check4: Failure	ro 1

¹ Read only

Name	Description	Value range	Access
[Operating hours]	Operating hours since delivery (value in h)	e.g. 10 h	ro 1
[Temperature]	Current internal temperature (value in °C)	-40: -40 (°C)...85: 85 °C	ro 1
[Parameter configuration faults]	Display of parameter setting errors (structure: → IO-Link interface description)	For each parameter:0: No error1: Error	ro 1

¹ Read only
Detailed device status:

Name	Description	Value range	Access
[Event history]	List of the 20 most recently active events	Per list field0: noEvent (default)20480: Event 0x5000 – hardware error in the device25376: Event 0x6320 – parameter error16928: Event 0x4220 – permitted device temperature exceeded16912: Event 0x4210 – permissible device temperature not reached36059: Event 0x8CDB – flashing sequence active, device status = 1 (maintenance required)36350: Event 0x8DFE – test event 1, device status = 1 (maintenance required)36351: Event 0x8DFF – test event 2, device status = 1 (maintenance required)	ro 1
[Event counter]	Structure with separate counters for all events (structure: → IO-Link interface description)	Per counter:0...2147482880	ro 1
[Active Events]	Structure for displaying active events (structure: → IO-Link interface description)	Per event:0: no event1: event active	ro 1

1 Read only

System commands:

Name	Description
[Reset Event counter]	Reset event counter (ID 174)
[Reset event history]	Reset event history (ID 173)

9.3.1.4 Process data

Name	Description	Value range	Access
[Device Status]	status of the device	0: Device is OK1: Maintenance required2: Out of specification3: Functional check4: Failure	ro 1

¹ Read only

9.4 Parameter setting: ifm IoT-Core

The ifm IoT-Core of the device is accessed exclusively via the ifm IoT-Core of a Bluetooth Mesh IoT Base Station EIO404.

Access options:

• IoT-Core Visualizer
• IoT-Core REST API

To access the IoT-Core structure of the device:

Requirements:

√ The device is integrated into a Bluetooth Mesh network, Integrating the device into a Bluetooth Mesh network ( → ☐ 16).
▶ Connect a PC/laptop to the Bluetooth Mesh IoT base station via the Ethernet interface.
▶ Use the chosen option to access the ifm IoT-Core of the Bluetooth Mesh IoT base station.
▷ The IoT-Core structure of the device is mapped in the substructure meshnetwork/provisioning/mesh_adapter[x].

9.4.1 Available parameters and commands

9.4.1.1 Identification information

Substructure: deviceinfo

Available data points:

Name	Description	Value range	Access
../serialnumber	Serial number	E.g. 000194610104	ro 1
../swrevision	Firmware version	E.g. V1.36	ro 1
../bootloaderrevision	Bootloader version	E.g. V0.06	ro 1
../productinstanceuri	Name of the root node in the IoT Core tree	E.g. B4-E3-F9-C7-54-43	ro 1
../eepromversion	EEPROM version	E.g. V0.02	ro 1
../btmacaddress	Bluetooth MAC address	E.g. B4-E3-F9-C7-54-43	ro 1
../hwrevision	Hardware version	E.g. AA	ro 1
../producttext	Product designation	Bluetooth Mesh IO-Link Adapter	ro 1
../vendor	Vendor	ifm electronic gmbh	ro 1
../productname	Product name	EIO344	ro 1
../productcode	Product code	EIO344	ro 1
../devicename	User-specific device name	E.g. mesh_adapter01	rw 2

¹ Read only

² Read and write

9.4.1.2 Adapter

Substructure: Adapter

The following parameters / commands can be read / written with a suitable configuration tool (e.g. moneo|blue) or via the IoT core

Access to the IoT core of the adapter is only possible via the EIO404 Bluetooth mesh IoT base station. The adapter must be registered with the base station (provisioned).

Available data points:

Name	Description	Value range	Access
../operatinghours	Operating hours counter since delivery		ro 1
../operatingstate	Display of the current device and diagnostic state	0: Device OK1: Bluetooth LE connected2: No valid IO-Link process data available3: No IO-Link process data available4: Master port no device connected5: Mesh not provisioned6: Mesh connection lost7: Switching output wrong setup8: Master wrong data storage setup9: Mesh bad signal10: Mesh sending problems11: Mesh too much traffic12: Master port short circuit13: Switching output short circuit14: Under temperature15: Over temperature16: Undervoltage17: Hardware Error	ro 1
../temperature/cpu	CPU temperature of the device (in °C)	E.g. 32	ro 1
.../temperature/cpu/unit	Unit of the temperature value	°C	ro 1

1 Read only

Applicable services:

Name	Description
../application_reset/factoryreset	Resets settings (except: application specific identifier, system identifier, location identifier, Bluetooth password, Bluetooth mesh network).
../back_to_box/factoryreset	All settings are set to the factory settings and communication is blocked until the next time the device is switched off and on.
../signal	Trigger flashing of the LED on the device
../reboot	Restart the device.

9.4.1.3 Bluetooth LE

Substructure: bluetooth_le

Available data points:

Name	Description	Value range	Access
../bluetooth_name	Station name of the unit (string with max. 22 characters)	e.g. eio344_adapter01	rw1
../security/password	Set a password to authenticate with the Bluetooth LE interface (Base64-encoded string)Min. length: 6 Max. length: 32NOTE! The password has no influence on the mesh functionality.	e.g. YmxIX3 Bhc3N3b3Jk	wo2
../security/password_state	Current status of the Bluetooth password	0: Default Password – factory-set password (last 6 digits of the serial number)1: User specific password – user-specific password	ro3

1 Read and write
² write only
³ Read only

Applicable services:

Name	Description
../resetpassword	Reset password to factory settings

9.4.1.4 Bluetooth Mesh network

Substructure: bluetooth_mesh

Available data points:

Name	Description	Value range	Access
../base_station_name	Name of the Bluetooth Mesh IoT base station EIO404 to which the device is connected.1	e.g. mesh_base	ro2
../link_quality	Connection quality of the adapter in the mesh network (value in %)	0: 0%...100: 100%	ro2
../signal_strength	Signal strength to the next mesh adapter of the Bluetooth network (value in %)1	0: 0%...100: 100%	ro2
../provisioning_status	Status of the adapter	0: Bluetooth mesh not provisioned1: Bluetooth mesh provisioned2: Bluetooth mesh provisioning invalid credits3: Bluetooth mesh provisioning no space left4: Bluetooth mesh provisioning duplicate address5: Bluetooth mesh provisioning generic error	ro2
../unique_id	Unique UUID of the Bluetooth mesh IO-Link adapter. Required for logging in and logging out.	e.g. 3A-45-E4-7B-8A-FE-DD-40-90-13-5A-2C-5E-69-81-04	ro2
../send_interval	Interval at which process data is sent from the adapter to the Bluetooth mesh IoT base station (value in ms)	1000: 1000 ms...86400000: 86400000 ms	rw3

Parameter can only be accessed via the Bluetooth mesh IoT base station EIO404.
² Read only
³ Read and write

9.4.1.5 Switching output

Substructure: switching_output

Available data points:

Name	Description	Value range	Access
../config	Configuration of the parameters of the switching output	0: Auto - The values for fou1 and bit_position are set automatically; if automatic configuration fails, the adapter flashes red1: Manual - the user sets the values for fou1 and bit_position manually2: Off - device deactivated	rw1
../fou1	Behaviour of the switching output [OUT 1] in case of a fault	2: ON4: OFF	rw1
../bit_position	Position of the value of the switching output in the IO-Link stream	0...255	rw1

1 Read and write

9.4.1.6 IO-Link master

Substructure: iolinkmaster/pin[1]

Available data points:

Name	Description	Value range	Access
.../mode	Operating mode of pin 4 (US) of the port	0: Disabled - port deactivated1: DI - digital input2: DO - digital output3: IO-Link - IO-Link data	rw1
../mastercycletime_actual	Current cycle time of the data transfer between port and IO-Link device (value in μs)	0: best possible cycle time1: 1 μs...132800: 132800 μs	ro2
../comspeed	Current transfer rate between port and IO-Link device	0: COM1 - 4.8 kBaud1: COM2 - 38.4 kBaud2: COM3 - 230.4 kBaud	ro2
../mastercycletime_preset	Cycle time of the data transfer between port and IO-Link device (value in μs); only in IO-Link operating mode	0: Automatically set the best possible cycle time1: 1 μs...132800: 132800 μs	rw1
../validation_datastorage_mode	Behaviour of the port when connecting a new IO-Link device,Device validation and data storage(→ 17)	0: No check and clear1: Type compatible V1.0 device2: Type compatible V1.1 device3: Type compatible V1.1 device with Backup + Restore4: Type compatible V1.1 device with Restore	rw1
../validation_vendorid	IO-Link ID of the manufacturer that is to be validated	0...655535	rw1
../validation_deviceid	IO-Link ID of the device to be validated	0...16777215	rw1
../portevent	Port event Struktur: 0xYYZZ000xYY:Connection Status- Status of the connection0xZZ:- Device Status- Status of the IO-Link device- Error Code- Error code in case of an error	Connection Status:0x00: No IO-Link device connected0x40: Incorrect IO-Link device connected0x80: IO-Link device connected and in state PREOPERATE0xFF: IO-Link device connected and in state OPERATEDevice Status:0x00: Port deactivated0x01: Port activated, but no device connected0x02: Port activated and in operating mode “IO-Link”0x03: Port activated and in operating mode “DI”0x04: Port activated and in operating mode “DO”Error Code:0x02: CRC error received0x10: Incoming: IO-Link device disconnected; Outgoing: IO-Link device in state OPERATE0x1A: Incorrect IO-Link device detected (unspecified error)0x1B: Repetitions detected0x1E: Short circuit detected on pin 40x1F: Error in sensor supply0x20: Error in actuator supply0x21: Error in IO-Link master supply0x22: Port has been reset0x23: Fallback successful, IO-Link device in SIO mode0x24: IO-Link device reached state PREOPERATE0x28: Data storage completed, but invalid CRC0x29: IO-Link device does not match the stored parameter set0x2A: Parameter set of the IO-Link device too large for data storage0x2B: Error uploading parameter set to data storage0x2C: Error downloading parameter set from data storage0x2F: Error in data storage function because IO-Link device is locked0x32: Download of parameter set completed0x33: Upload of parameter set completed0x40: Length of process data (inputs) does not match settings0x41: Length of process data (outputs) does not match settings0x42: Incorrect revision of the IO-Link device0x43: Incorrect Vendor ID (V1.1 revision)0x44: Incorrect Device ID (V1.1 revision)0x45: Incorrect Vendor ID (V1.0 revision)0x46: Incorrect Device ID (V1.0 revision)0x47: Incorrect serial number0x48: Incorrect cycle time	ro 2

1 Read and write
² Read only

Applicable services:

Name	Description
../validation_useconnecteddevice	Validate the IO-Link device

9.4.1.7 IO-Link device

Substructure: iolinkmaster/pin[1]/iolinkdevice

Available data points:

Name	Description	Value range	Access
../pdin	Input data (pin 4)	“DI” operating mode:0x00: OFF0x01: ON“IO-Link” operating mode:Process value in hexadecimal representation	ro 1
../pdout	Output data (pin 4)	“DO” operating mode:0x00: OFF0x01: ON“IO-Link” operating mode Process value in hexadecimal representation	rw 2
../iolinkevent	IO-Link event	→ Note	ro 1\ 3

¹ Read only
² Read and write
³ Parameter only available if operating mode pin 4 (US) = IO-Link and IO-Link device is connected to the port

Applicable services:

Name	Description
../iolreadacyclic	Read parameters of an IO-Link device acyclically
../iolwriteacyclic	Write parameters of an IO-Link device acyclically

Note IO-Link events:

The device supports IO-Link events. IO-Link events are event and error messages. IO-Link events can be generated in the IO-Link master and in the connected IO-Link devices. IO-Link events generated in the IO-Link devices are forwarded to the IO-Link master and stored there.

An IO-Link event message has the following structure:

Byte 0...1	Byte 2	Byte 3	Byte 4	Byte 5	Byte 6
Event Code	Source	Validity	Type	Mode	Instance

Legend

Instance	IO-Link Event Qualifier: Trigger	1 byte	0x00: unknown0x01: PL (Physical Layer)0x02: DL (Data Layer)0x03: AL (Application Layer)0x04: APPL (Application)
Mode	IO-Link Event Qualifier: Event trigger	1 byte	0x40: One-time event or warning (single shot)0xC0: Error disappeared0x80: Error appeared
Type	IO-Link Event Qualifier: Event category	1 byte	0x10: Notification0x20: Warning0x30: Error
Validity	Validity of the process data	1 byte	0x00: Valid0x40: Invalid
Source	IO-Link Event Qualifier: Event source	1 byte	0x00: IO-Link device0xFF: IO-Link master
Event Code	IO-Link event code (bytes are swapped!)	2 bytes	→ IO-Link specification

10 Troubleshooting

Errors, warnings and status messages are indicated by the status LEDs: Operating and display elements ( → ☐ 13)

In the event of an error (status LED flashes red), the device status provides detailed diagnostic information.

Fault description	Cause of the fault	Corrective measures
The device is connected to the power supply, status LED is off	Supply voltage too low	▸ Check the voltage supply
The device is connected to the power supply, status LED lights up red	Hardware error, the device is defective	▸ Replace device
The status LED flashes red, device status: [Over temperature] or [Under temperature]	Temperature of the circuit board outside the tolerance range	▸ Check the ambient temperature
The status LED flashes red, device status: [Switching output short circuit]	Short circuit at the switching output	▸ Check wiring
The status LED flashes red, device status: [Switching output wrong setup]	Invalid output configuration	▸ Check the configuration of the switching output OUT1
The status LED flashes red, device status: [Master wrong data storage setup]	Incorrect data storage	▸ Check vendor ID and device ID of the connected IO-Link device

ifm moneo provides additional status and diagnostic information in online mode: → ifm moneo online help

11 Maintenance, repair and disposal

The unit is maintenance-free.

▶ Contact ifm in case of malfunction.
▶ Do not open the housing as the unit does not contain any components which can be maintained by the user. The unit must only be repaired by the manufacturer.
▶ Clean the device using a dry cloth.
▶ Dispose of the unit in accordance with the national environmental regulations.

11.1 Firmware update

The firmware of the device can be updated via ifm moneo|blue.

New firmware available on the product detail page of the device: documentation.ifm.com

For information on updating the firmware of several Bluetooth Mesh IO-Link adapters at the same time: → operating instructions EIO404

The firmware update must not be interrupted.

▶ Do not restart the device during the update process.
▶ Wait until the update is complete.

Requirements:

√ The firmware file of the Bluetooth Mesh IO-Link adapter is saved in the file system of the mobile device.
√ ifm moneo|blue has been launched.
▶ Establish a connection to the Bluetooth Mesh IO-Link adapter.
▶ Call up the editor view of the Bluetooth Mesh IO-Link adapter.
▶ In the header: Click on ↑.
▶ Click on [Browse].
▶ Select new firmware file.
▷ The menu page shows the selected firmware file.
▶ Click on [Import].
▷ A message appears that new firmware is available for the adapter.
▶ Click on [Update].
▷ New firmware is transferred to the Bluetooth Mesh IO-Link adapter.
▷ The firmware is updated.
▷ The adapter reboots.
▷ New firmware is installed on the Bluetooth Mesh IO-Link adapter.