IO-Link master and procedures for controlling an IO-Link system

Abstract

IO-Link master (20) having at least one IO-Link port (21) configured to be connected to an IO-Link port transceiver (11) of an interface (10) having an IO-Link port transceiver (11), at least one wireless transceiver (12, 12a, 12b) and a signal processing device (13) configured to provide a network between the IO-Link port transceiver (11) and the at least one wireless transceiver (12, 12a, 12b), characterized in that the IO-Link master (20) has a signal processing device (23) configured to provide a network between the interface (10) and IO-Link devices (40) connected to further IO-Link ports (22) of the IO-Link master (20).

Description

[0001] The present invention relates to an IO-Link master. Furthermore, the present invention relates to methods for controlling an IO-Link system. State of the art

[0002] In mechanical and plant engineering as well as in automation technology, numerous standardized fieldbus systems have proven their worth as an alternative to parallel individual wiring. In these systems, a number of so-called fieldbus modules are connected to a central control unit via the fieldbus. End devices are then connected to these fieldbus modules.

[0003] Recently, so-called "IO-Link" connections have been used to connect end devices to fieldbus modules. Such an IO-Link, as well as a method and a control unit for operating such an IO-Link, are described in DE 10 2012 009 494 A1. As described therein, the fieldbus modules assume the role of an IO-Link master. End devices (hereinafter referred to as "IO-Link devices") can include, for example, sensors, actuators, display devices, operator panels, and even small drives on machines.

[0004] A standard for an intelligent sensor / actuator interface called "IO-Link" is to be standardized as an international open standard in IEC 61131-9. IO-Link devices will then be described using description files called IODD (IO-Link Device Description). The IODD as a description language is also to be standardized as an open standard in ISO 15745. The existing "IO-Link Wireless System Extensions" specification already describes an IO-Link wireless master with a fieldbus interface.

[0005] An IO-Link provides a serial point-to-point connection for signal transmission between sensors and actuators and the machine's I / O level. Essentially, an IO-Link transmits data between a designated IO-Link master and a connected IO-Link device (acting as a slave). Both fieldbus modules and PLC interface modules can serve as IO-Link masters. The connection of multiple IO-Link masters via a fieldbus is described in DE 10 2012 009 494 A1.

[0006] Common fieldbuses include PROFIBUS-DP, Interbus, DeviceNet, CC-Link, CC-Link IE Field, CC-Link IE Field Basic, Modbus TCP, Sercos III, and CANopen. More recently, Ethernet-based fieldbus standards such as PROFINET, EtherNet / IP, EtherCAT, Mechatrolink, Varan, and Ethernet POWERLINK have also been used. Fieldbuses are particularly advantageous for bridging large distances between individual devices, ranging from several hundred meters to over 10 kilometers. However, a significant drawback is that these high-performance bus systems are not practically economically viable at the sensor / actuator level.

[0007] German patent application DE 10 2016 217 706 A1 describes an intermediate unit that can be used as a coupler between an IO-Link master and an IO-Link device. The intermediate unit comprises a virtual IO-Link device that is connected to the IO-Link master via an IO-Link communication interface and a secondary master that is connected to the IO-Link device via an IO-Link communication interface. Communication between the virtual IO-Link device and the secondary master can be established via Bluetooth.

[0008] IO-Link devices can be configured individually on-site using screwdrivers on a power potentiometer or by pressing a button. Alternatively, they can also be configured and monitored via the fieldbus. Access to the fieldbus is typically via the PLC (programmable logic controller).

[0009] It is an object of the present invention to provide a way to parameterize and monitor IO-Link devices in a simpler manner. Disclosure of the invention

[0010] This problem is solved in one aspect of the invention by an IO-Link master that has multiple IO-Link ports. One of the IO-Link ports is configured to be connected to an IO-Link port transceiver of an interface. This IO-Link port can therefore function as a service port, allowing a service technician direct access to the IO-Link master. The interface or gateway has an IO-Link port transceiver configured to establish a connection between the interface and the IO-Link master via an IO-Link port. In different embodiments of the interface, the IO-Link port transceiver can be configured, for example, to be plugged directly into an IO-Link port or to be connected to it via a cable. Furthermore, the interface has at least one wireless transceiver.This can be configured to communicate wirelessly using one or more different radio protocols, such as Bluetooth. A signal processing device is configured to provide a network between the IO-Link port transceiver and the at least one wireless transceiver, thus enabling data exchange between them.

[0011] The interface allows an existing IO-Link master to be retrofitted with an additional communication capability, thus enabling the configuration and monitoring of IO-Link devices. Since the wireless transceiver is not an integral part of the IO-Link master, radio certification is not required.

[0012] It is preferred that the interface retain a switching element configured to establish a communication link between a communication partner and the wireless transceiver. To ensure that only authorized communication partners can establish a communication link, it may be provided, for example, that when the switching element is activated, an establishment signal is first sent to the IO-Link master. The master then displays a code on a screen to ensure that only persons with physical access can connect to it. The communication partner must then send this code to the interface. Only when a comparison in the signal processing device confirms that the correct code has been returned by the communication partner is the communication link established.

[0013] Furthermore, it is preferred that the interface includes a switching element configured to block the establishment of communication links between a communication partner and the wireless transceiver. Once a communication link has been established with one communication partner, actuating this switching element prevents the establishment of further communication links with other communication partners. This prevents external access to the IO-Link master.

[0014] Furthermore, it is preferred that the interface includes a switching element configured to block communication between the wireless transceivers via at least one configurable communication protocol. For example, this can be used to block only communication via the Bluetooth protocol. This embodiment of the interface is particularly useful when it includes multiple wireless transceivers, each configured for different communication protocols. The switching element can then selectively disable one of the wireless transceivers.

[0015] If the interface is intended to enable communication via several different wireless communication protocols, it is generally possible to use multiple separate wireless transceivers or a single wireless transceiver that can switch between different communication protocols, either automatically or manually (e.g., by actuating an additional switch). In particular, one of the communication protocols used can be the IO-Link wireless protocol. In this case, the interface is an IO-Link wireless master or an IO-Link wireless device. This device can, in particular, have multiple tracks (transceiver radios), one of which is specifically configured to switch between the IO-Link wireless protocol and a faster protocol, such as Bluetooth.

[0016] An antenna of the wireless receiver can be implemented in particular as an external antenna or within a housing of the interface as a chip or as a PCB antenna on a printed circuit board (PCB = Printed Circuit Board).

[0017] The signal processing device is, in particular, a microcontroller that can provide the network, for example, in the form of an ad-hoc communication protocol.

[0018] The communication partner can be, in particular, a mobile device such as a smartphone or tablet PC, or a cloud.

[0019] The connection between the IO-Link port and the IO-Link transceiver is established by the IO-Link master's integrated signal processing unit. This unit is configured to provide a network between the interface and IO-Link devices connected to other IO-Link ports on the IO-Link master. This allows for the configuration of these IO-Link devices and the retrieval of data they provide, such as conditional monitoring data.

[0020] In another aspect of the invention, the problem is solved by a method for controlling an IO-Link system. In this method, a communication partner communicates with at least one IO-Link device via the interface. Therefore, in this method, it is not necessary to address the IO-Link device locally or to contact it via the PLC.

[0021] In one embodiment of the method, the IO-Link device is connected to the same IO-Link master as the interface. Communication between the IO-Link device and the interface therefore takes place exclusively via the IO-Link master.

[0022] In another embodiment of the method, the IO-Link device is connected to an IO-Link master, which is connected to the IO-Link master to which the interface is connected via a fieldbus. In this embodiment, communication takes place via both IO-Link masters and the fieldbus. This makes it possible to address even more distant IO-Link devices using the interface.

[0023] In yet another embodiment of the method, the IO-Link device is connected to an IO-Link master, which is connected to the IO-Link master to which the interface is connected via a wireless network. Additional connection elements can also be provided. For example, the IO-Link device can be connected to a first IO-Link master, which is connected via a fieldbus to a second IO-Link master. This second master can be connected via the wireless network to a third IO-Link master, which in turn is connected via a fieldbus to a fourth IO-Link master, to which the interface is connected.

[0024] In this process, the communication partner can, in particular, read data from the IO-Link device. For example, if the IO-Link device is a sensor and the communication partner is a mobile device, a service technician can use this process to visualize sensor data on the mobile device.

[0025] Furthermore, the communication partner can use this method to configure the IO-Link device. If the communication partner is a mobile device, this offers a user-friendly way to configure IO-Link devices without having to physically manipulate them with a screwdriver or configure them via the PLC.

[0026] If an IO-Link master has a web interface, an API (application programming interface), or a GUI (graphical user interface), then it is preferred in this procedure that the communication partner communicates with the IO-Link master's interface. This can be the IO-Link master to which the interface is connected, or an IO-Link master connected to the IO-Link master to which the interface is connected via a fieldbus and / or a wireless network. This provides the communication partner with web access via the interface.

[0027] It is still preferred that communication between the interface and the IO-Link master does not take place using an IO-Link protocol. Instead, it is preferred that the IO-Link master detects when communication with the interface is to take place via the IO-Link service port and switches to a faster communication protocol for this purpose.

[0028] Furthermore, it is preferred that a transceiver of the interface for communication with the communication partner is switched from an IO-Link wireless protocol to another protocol, in particular a Bluetooth protocol. Brief description of the drawings

[0029] Exemplary embodiments of the invention are shown in the drawings and are explained in more detail in the following description. Fig. Figure 1 schematically shows an interface of an IO-Link master according to an embodiment of the invention. Fig. Figure 2 shows schematically how, in an embodiment of the invention, an IO-Link device communicates with a communication partner via an IO-Link master and an interface. Fig. Figure 3 schematically shows the communication in an IO-Link system using an interface according to an embodiment of the invention. Fig. Figure 4 schematically shows the communication in IO-Link systems via interfaces according to an embodiment of the invention. Exemplary embodiments of the invention

[0030] An interface 10 for an IO-Link master according to an embodiment of the invention is in Fig. Figure 1 shows the interface. It features an IO-Link port transceiver 11, which is implemented as an IO-Link wired transceiver. This is connected to an IO-Link wired connector 111 in the form of a plug for an IO-Link port. Furthermore, the interface 10 features a wireless transceiver 12, which is implemented as a Bluetooth transceiver and has an antenna 121. A signal processing device 13 in the form of a microcontroller is connected to the IO-Link port transceiver 11 and to the wireless transceiver 12 and provides a network between these two. It is also connected to three switching elements 14, 15, 16 in the form of pushbuttons. The first switching element 14 is a pairing pushbutton, the actuation of which allows a pairing signal to be sent to an IO-Link master via the IO-Link port transceiver 11.The second switching element 15 is configured to block the establishment of further communication connections via the wireless transceiver in addition to existing communication connections. The third switching element 16 is configured to block connections via the wireless transceiver 12 using the Bluetooth protocol. A storage element 17 in the form of a memory card is also provided. The signal processing device 13 is configured to read the communication between IO-Link ports of an IO-Link master, to which the interface 10 is connected, via the IO-Link port transceiver 11. All communication is stored by the signal processing device 13 on the storage element 17. This element can be removed from the interface 10 to transfer the stored data, for example, to a computer where it can then be evaluated.

[0031] As in Fig. As shown in Figure 2, interface 10 can be plugged directly into an IO-Link port 21 of an IO-Link master using the IO-Link wired connector 111. It can be attached to the IO-Link port 21, for example, using a screw (not shown). This IO-Link port 21 is referred to below as the IO-Link service port. Further IO-Link ports 22 of the IO-Link master are connected to the IO-Link service port 21 via a signal processing device 23 within the IO-Link master 20, enabling interface 10 to exchange data with a 10-Link device 40 connected to an IO-Link port 22. This data can then be forwarded to a communication partner 30, such as a smartphone. The IO-Link master 20 also features a fieldbus communication interface 24, an electrical supply 25, a display 26 and a web interface.The web interface enables web communication via the fieldbus communication interface 24 or, according to the invention, via interface 10. When a pairing signal is sent to the signal processing device 23 via the IO-Link service port 21, a code stored therein is displayed on the display 26. The user of the communication partner 30 must then read this code and enter it into the communication partner 30. The communication partner 30 then sends it back via interface 10 to the IO-Link master and its signal processing device 25. Only when the signal processing device 25 recognizes that the correct code has been entered is interface 10 granted access to the other IO-Link ports 22 and the IO-Link devices 40 connected to them. Access to other IO-Link masters connected to this IO-Link master 20 via the fieldbus communication interface 24 is also granted at this time. Access to the web interface is also enabled.

[0032] As in Fig. As shown in Figure 3, interface 10 does not need to be plugged directly into IO-Link service port 21. Instead, IO-Link wired connector 111 can also be connected to IO-Link service port 21 via cable 211. This allows the interface to be positioned at a greater distance from an IO-Link master 20a, which facilitates easier access via communication partner 30. If additional IO-Link masters 20b, 20c, and a PLC 60 are connected to the first IO-Link master 20a via a fieldbus 50, communication partner 30 can also access them. In particular, this also enables the reading of data from an IO-Link device 40 connected to a more distant IO-Link master 20c. Parameterizing this IO-Link device 40 is also possible without direct physical access to it.

[0033] Fig.Figure 4 shows an embodiment in which, in a first IO-Link system, an interface 10a is connected to a first 10-Link master 20a. This master is connected via a first fieldbus 50a to a second IO-Link master 20b and a first PLC 60a. A second IO-Link system has a second interface 10b, which is connected to a third IO-Link master 20c. A fourth IO-Link master 20d and a second PLC 60b are connected to the third IO-Link master 20c via a second fieldbus 50b. A 10-Link device 40 is connected to the fourth IO-Link master 20d. The IO-Link masters 20a to 20d of the two IO-Link systems are interconnected via a wireless mesh network.If the user of a smartphone acting as communication partner 30 is only within range of the first interface 10a but not within range of the second interface 10b, he can still access the remote IO-Link device 40 via the first interface 10a, the wireless network and the fieldbuses 50a, 50b.

Images