Data exchange between input / output module and mobile device

Abstract

An input / output module (I / O module) is disclosed. The I / O module comprises an input and / or an output designed to be detachably connected to one or more electrical conductors, a bus interface designed to transmit first process data or to receive second process data, and a wireless interface designed to exchange third data with a mobile device, the wireless interface being further designed to be powered by the mobile device.

Description

Technical Field

[0001] The invention relates to data exchange between an input / output module (ie, an I / O module) and a mobile device. Background Art

[0002] I / O modules are usually connected to the network via wired interfaces (such as local bus interfaces and field bus interfaces) and can send or receive data via these wired interfaces. In addition, some I / O modules have the following interfaces: These interfaces allow the I / O module to be connected to a mobile device via a (temporary) cable connection, so that data can be read from or written to the I / O module independently of the network. For example, some I / O modules have an RS232 interface, a USB interface or an Ethernet interface, which enables the user to read data such as the serial number or product name of the I / O module from the I / O module, and also read diagnostic data or configuration data, or in the case of configuration data, write these configuration data to the I / O module when the user uses a correspondingly designed mobile device near (close to) the I / O module.

[0003] The requirement that a user must be in the vicinity (close proximity) of an I / O module in order to access the I / O module via a network-independent interface can be advantageous, for example, in order to (re)commission an I / O module while it is not (yet) reachable via the network, or in order to protect safety-critical data or settings from unauthorized access. For example, it can be provided that certain data or settings (particularly in error situations or during operation) can only be reached via a network-independent interface in order to exclude access via a possibly corrupted network. Summary of the invention

[0004] According to a first aspect of the present invention, an I / O module comprises an input terminal and / or an output terminal designed to be detachably connected to one or more electrical conductors, a bus interface designed to send first process data or receive second process data, and a wireless interface designed to exchange third data with a mobile device, wherein the wireless interface is also designed to be powered by the mobile device. The mobile device can be, for example, a portable electronic device equipped with a battery, the device having a processor and a wireless interface controlled by the processor.

[0005] Furthermore, the term "module" as used within the scope of the present description and claims is understood in particular to mean a device which is designed to be electrically connected to another device for expanding the capabilities of the other device, so that the two devices functionally form a unit. Furthermore, it can be provided that the two devices are designed to be not only electrically connected to each other but also mechanically connected, so that the two devices not only functionally but also mechanically form a unit.

[0006] Furthermore, the bus interface can be designed to send first process data to the field bus coupler or to receive second process data from the field bus coupler. In this regard, the term "I / O module" used within the scope of the present specification and claims is particularly understood to mean a device that is connected to the field bus coupler via a wired transmission path during operation, which is connected to the field bus coupler (via a wired transmission path) and, if necessary, to a higher-level control device (via a field bus coupler) when one or more field devices are in operation. If the I / O module can be directly connected to the field bus, that is, if the I / O module does not require a field bus coupler to communicate with the field bus, then the term "I / O module" used within the scope of the present specification and claims is particularly understood to mean a device that is connected to the higher-level control device (via a wired transmission path) when one or more field devices are in operation.

[0007] The I / O module can have a housing which is designed to connect the I / O module in series to another I / O module or to a fieldbus coupler. The term "housing" as used within the scope of the present description is understood in particular to mean a structure made of solid insulating material, in which conductive structures are embedded, wherein the housing is generally designed to substantially exclude accidental contact with live conductors. Furthermore, the term "series" as used within the scope of the present description is understood in particular to mean the establishment of a friction-locking or form-locking connection between the housings, via which a plurality of modules can be connected in series with one another. The housing can be equipped in such a way that a wired transmission path is established within the scope of the series connection (without further aids).

[0008] Furthermore, the term "fieldbus coupler" as used within the scope of the present description and claims is to be understood as a component of a modular fieldbus node, the task of which is to make data and / or services of I / O modules connected in series to the fieldbus coupler available via a fieldbus connected to the fieldbus coupler. The fieldbus coupler and the I / O modules can be designed to exchange data by means of electrical signals via a local bus implemented on the basis of a wired transmission path.

[0009] The term "local bus" as used within the scope of the present description is understood to mean, in particular, a bus via which (only) the I / O modules connected in series to a fieldbus coupler are (directly) connected to one another or to the fieldbus coupler. In this context, the term "bus interface" as used within the scope of the present description and claims is understood to mean, in particular, a bus interface which is designed to be connected to a local bus (or to generate a local bus) and to exchange (process) data with other I / O modules or fieldbus couplers. If the I / O module can be connected directly to the fieldbus, i.e. if the I / O module does not require a fieldbus coupler for communicating with the fieldbus, then the term "bus interface" as used within the scope of the present description and claims is understood to mean, in particular, a fieldbus interface.

[0010] The I / O module can have one or more inputs and / or outputs which are designed to read in status signals and / or output control signals (control voltages and / or control currents). The I / O module can be configured to derive process data from status signals or to derive control signals from process data. In particular, the I / O module can be designed to derive first process data sent to the fieldbus coupler from signals input via the inputs or to derive signals output at the outputs from second process data received by the fieldbus coupler.

[0011] The I / O module may also have a memory in which data from which the configuration of the I / O module can be derived can be stored. This configuration may, for example, reveal how a process image is generated (e.g. how process data representing a specific point in time or a specific time period are derived from signals read in at the input of the I / O module and how the process data are transmitted to the fieldbus coupler via the local bus) and / or how control signals are derived from process data transmitted from the fieldbus coupler via the local bus to the I / O module (these control signals are output, for example, at the output of the I / O module).

[0012] For example, the I / O module may include a processor and a memory, in which configuration data is stored, wherein the processor is designed to derive, when using the configuration data, first process data sent to the field bus coupler from a signal input via the input, or to derive, when using the configuration data, a signal output at the output from second process data received by the field bus coupler. The memory may be part of a "near field communication" (NFC) chip. By using the memory of the NFC chip to store the configuration data, other memories required for storing the configuration data (or storage areas provided for this purpose on a microprocessor chip containing the processor) may be omitted. The processor may also be designed to cause the first process data to be transmitted to the bus interface, or the bus interface may be designed to cause the second process data to be transmitted to the processor.

[0013] At the input and / or output, a field device can be connected, which provides a status signal or processes a control signal. Here, the concept of "field device" used within the scope of the current specification is particularly understood to be a sensor and / or actuator connected to the I / O module (signal technology) (for example, connected to the I / O module). In this regard, the concept of "input" or "output" used within the scope of the current specification and claims is particularly understood to be an electrical connection. It can be provided that the voltage and / or current on the input of the I / O module is generated by other devices and the voltage and / or current on the output of the I / O module is generated by the I / O module itself.

[0014] Furthermore, the term "detachable connection" as used within the scope of the present description and claims is understood in particular to mean an electrical connection that can be electrically isolated without loss, such as a connection established by means of a spring-based clamping connection. Furthermore, the term "conductor" as used within the scope of the present description and claims is understood in particular to mean a wire or stranded wire. Furthermore, the term "wireless interface" as used within the scope of the present description and claims is understood in particular to mean an interface that is designed to wirelessly transmit data and / or wirelessly receive data.

[0015] Furthermore, the term "mobile device" as used within the present description and claims is understood to mean a device which is designed and arranged to be carried by a user (in normal operation). Furthermore, the term "power supply" as used within the present description and claims is understood in particular to mean ensuring an electrical energy supply which (primarily) enables the operation of the wireless interface and thus the exchange of data.

[0016] The wireless interface can be designed to allow access by the I / O module to data generated during configuration or operation of the I / O module (and stored in the overwritable memory). In addition, the wireless interface can be designed to store data in a memory that can be read by other components of the I / O module (such as a processor) during operation of the I / O module.

[0017] The wireless interface can also be designed to support communication with the processor. Here, the processor can be designed to execute (specific) instructions received via the wireless interface. For example, the processor can be designed to store data received via the wireless interface in a memory provided for this purpose on the I / O module in response to instructions received via the wireless interface. The processor can also be designed to transmit data (via the wireless interface) to the mobile device in response to a connection (with a portable device) established via the wireless interface, or in response to instructions received via the wireless interface.

[0018] The processor may be designed, for example, to transmit the fourth data to the wireless interface. The fourth data may be, for example, debugging data or diagnostic data. The debugging data or diagnostic data may be transmitted to the mobile device via the wireless interface and processed, displayed or visualized on the mobile device.

[0019] The wireless interface can be designed to transmit the fifth data to the processor. For example, the mobile device can transmit the fifth data to the wireless interface, and the wireless interface enables the fifth data to be accessed by the processor or forwards the fifth data to the processor. The fifth data can include instructions and / or parameters. These data can relate to the configuration of the I / O module and the desired state of the I / O module.

[0020] For example, the processor may be designed to derive configuration data from fifth data transmitted to the processor by the wireless interface and store the configuration data in the memory. The processor may also be designed to check the configuration data and discard the configuration data when the check finds an error in the configuration that is usually caused by the configuration data.

[0021] The processor can also be designed to derive third process data from fifth data transmitted to the processor via the wireless interface and send the third process data to the field bus coupler, or to derive a signal output at the output end from the third process data. Thus, the operation of the I / O module or a specific operating state (for example for testing purposes) can be controlled or preset via the wireless interface.

[0022] The processor can also be designed to derive the operating mode of the I / O module from the fifth data and switch to the derived operating mode. Therefore, the operating mode of the I / O module can be preset via the wireless interface (for example, for testing purposes). The I / O module can also provide acoustic or optical feedback about the selected operating mode. For example, the I / O module can be equipped with one or more optical signal transmitters (such as light emitting diodes), which display (for example, by light of different colors) which operating mode the I / O module is in.

[0023] Likewise, the I / O module can be designed to indicate optically or acoustically that a (successful) connection has been established between the mobile device and the wireless interface.

[0024] According to a second aspect of the invention, the I / O module comprises an input and / or an output designed for detachable connection to one or more electrical conductors, a bus interface designed for sending or receiving process data, and a first wireless interface designed for exchanging data with a mobile device (preferably a transponder), wherein the first wireless interface is also designed to supply power to a second wireless interface of the mobile device. The bus interface can be designed to send process data to a field bus coupler or to receive process data from a field bus coupler.

[0025] The I / O module may also include a processor and a memory, wherein the configuration data is stored in the memory. The processor may be designed to derive, when using the configuration data, first process data sent to the field bus coupler from a signal input through the input end, or to derive a signal output at the output end from second process data received by the field bus coupler when using the configuration data. The processor may also be designed to cause the first process data to be transmitted to the bus interface, or the bus interface may be designed to cause the second process data to be transmitted to the processor. The processor may also be designed to transmit the fourth data to the wireless interface, and the wireless interface may be designed to transmit the fifth data to the processor. The fourth data may be, for example, debugging data or diagnostic data.

[0026] In addition, the processor can be designed to derive configuration data from the fifth data transmitted to the processor by the wireless interface and store the configuration data in the memory, or to derive third process data from the fifth data transmitted to the processor by the wireless interface and send the third process data to the field bus coupler, or to derive a signal output at the output end from the above-mentioned third process data, or to derive the operating mode of the I / O module from the fifth data and switch to the exported operating mode.

[0027] Furthermore, it is to be understood that in principle all features of a step performed using an I / O module may be features of the corresponding method and vice versa. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The invention is explained in detail below using an exemplary embodiment, with reference to the accompanying drawings, in which:

[0029] Figure 1 A schematic diagram showing a fieldbus system;

[0030] Figure 2 Show Figure 1 A schematic diagram of a fieldbus node of a fieldbus system shown in;

[0031] Figure 3 Explanation of the configuration using a computer connected to the fieldbus node Figure 2 The field bus node shown in;

[0032] Figure 4 A schematic diagram showing an I / O module equipped with a wireless interface designed to be powered by a mobile device;

[0033] Figure 5 A schematic diagram of another I / O module is shown, the I / O module being equipped with a wireless interface designed to supply power to a wireless interface of a mobile device;

[0034] Figure 6A schematic diagram of another I / O module is shown, the I / O module being equipped with a wireless interface designed to be powered by a mobile device;

[0035] Figure 7 A schematic diagram showing an I / O module equipped with a wireless interface designed to supply power to a wireless interface of a mobile device; and

[0036] Figure 8 The sequence of steps for exchanging data between a mobile device and an I / O module using a wireless interface which is powered by a communication partner is shown.

[0037] In this case, identical or functionally similar elements are denoted by the same reference symbols in the figures. DETAILED DESCRIPTION

[0038] Figure 1 The block diagram of a fieldbus system 1000 is shown. The fieldbus system 1000 includes fieldbus nodes 100, 200, 300 and 400, which are connected to each other via a fieldbus 500. The fieldbus node 400 is configured as a superordinate control unit and can be used not only to monitor but also to regulate devices (not shown) controlled by the fieldbus system 1000. When the superordinate control unit 400 monitors the devices, the superordinate control unit 400 can receive status data from one or more of the fieldbus nodes 100, 200 and 300 cyclically or acyclically, the status data describing the status of the devices and generate a fault signal or an alarm signal when the status of the devices deviates (substantially) from an expected / permitted state or a state range. When the superordinate control unit 400 (not only monitors but also) regulates the device, it can cyclically or acyclically receive status data from one or more of the fieldbus nodes 100, 200 and 300 and determine control data to be transmitted to one or more of the fieldbus nodes 100, 200 and 300 taking into account the status data.

[0039] Figure 2The modular fieldbus node 100 is shown, comprising a fieldbus coupler 110 and two I / O modules 120 and 130 connected in series to the fieldbus coupler 110, to which sensors 140 and actuators 150 are connected. During operation, the I / O module 130 reads in sensor signals via an input 134 and generates status data from the sensor signals, which are transmitted to the fieldbus coupler 110 via a bus interface 132 of the I / O module 130, a local bus 160 and a bus interface 112 (of the fieldbus coupler 110). In addition to the fieldbus interface 114, the fieldbus coupler 110 has a processor and a memory, in which information about the configuration of the fieldbus coupler 110 is stored.

[0040] The information about the configuration of the fieldbus coupler 110 can indicate, for example, which or how many I / O modules are connected in series to the fieldbus coupler 110 and how the fieldbus coupler 110 is to process received status data. The fieldbus coupler 110 can be configured, for example, to process these status data locally and / or (if necessary in a modified form) to forward them to the superordinate control unit 400 via the fieldbus interface 114 and the fieldbus 500. The superordinate control unit 400 (or the fieldbus coupler 110 in the case of local processing) can generate control data taking into account these status data.

[0041] The control data generated by the superordinate control unit 400 can be transmitted to the fieldbus coupler 110 via the fieldbus 500. The control data transmitted to the fieldbus coupler 110 (or generated by the fieldbus coupler 110 in the case of purely local processing) are (if necessary in a modified form) forwarded / transmitted to the I / O module 120. The I / O module 120 receives the control data and outputs a control signal corresponding to the control data at an output 124, to which the actuator 150 is connected. In this case, the data communication between the components of the fieldbus system 1000, the mapping of sensor signals to status data and the mapping of control data to control signals can be adapted to different usage scenarios by configuring the fieldbus node 100.

[0042] to this end, Figure 3A fieldbus node 100 and a computer 600 (e.g., a desktop, laptop, tablet, etc.) connected to the fieldbus node 100 are shown, which is designed to configure the I / O modules 120 and 130 of the fieldbus node 100. Here, the computer 600 can not only be used only or mainly for configuration, but also (in addition to configuration) can also undertake other tasks. The computer 600 can especially be part of the superordinate control unit 400 and can also undertake monitoring tasks and / or control tasks in addition to configuration. For example, the computer 600 can monitor the device and be designed to switch from one operating mode to another operating mode when certain conditions exist (and in the process of switching, it is possible to change or update the configuration).

[0043] like Figure 4 As shown in , the I / O module 130 can have a circuit 10, which reads in a sensor signal of a sensor 140. The sensor signal can be read in, for example, in the following way: the circuit 10 determines (with a certain sampling frequency) a voltage applied to an input 134 or a current flowing through the input 134. The circuit 10 can also include a processor 12, which is designed to execute a program (such as an instruction sequence) stored in a memory 14 of the I / O module 130, which determines how process data is generated from the sensor signal and how the process data is further processed (for example, whether, when or with what frequency the process data is transmitted to the field bus coupler 110) under the use of configuration data.

[0044] The I / O module 130 further comprises a wireless interface 20 (which can be implemented, for example, by means of an NFC / RFID chip), which is designed to exchange data with a mobile device 700 (e.g., a laptop, a tablet, a mobile phone, etc.), wherein the wireless interface 20 is powered by the mobile device 700. It can be provided that the wireless interface 20 forwards received data to the processor 12 or receives sent data from the processor 12. Alternatively or additionally, it can be provided that the wireless interface 20 is equipped with a memory 22, which the processor 12 can directly or indirectly access.

[0045] Here, it can also be provided that the I / O module 120 acoustically or optically displays the successful establishment of the connection between the wireless interface 20 and the mobile device 700. For example, the I / O module 130 can have a light-emitting diode, which temporarily or continuously (i.e., while the connection exists) illuminates when the connection between the wireless interface 20 and the mobile device 700 is successfully established.

[0046] In the context of the connection, the mobile device 700 can, for example, transmit configuration data to the wireless interface 20, which forwards the configuration data to the processor 12 or stores it in a memory 22 accessible to the processor 12. If the wireless interface 20 stores the configuration data in a memory 22 accessible to the processor 12, it can be provided that the processor does not store the configuration data in another memory (only) assigned to the processor 12, but rather leaves the configuration data in the memory 22 and accesses the memory 22 when necessary. The processor 12 can also be designed to perform a credibility or security check before using the configuration data in order to exclude the use of erroneous or unsafe configuration data. In addition, it can be provided that the mobile device 700 can request configuration data from the processor 12 via the wireless interface 20 or read the configuration data from the memory 22, so as to enable, for example, a check of the configuration data on the mobile device 700.

[0047] Furthermore, it can be provided that the mobile device 700 requests diagnostic data or process data (such as the temperature measured by the sensor 140) from the processor 12 via the wireless interface 20 or reads diagnostic data or process data from the memory 22. It can also be provided that the device 700 instructs the processor 12 via the wireless interface 20 to generate certain process data that are independent of the signals of the sensor 140, for example in order to test the functions of the I / O module 130, the fieldbus node 100 and / or the fieldbus system 1000. Thus, the wireless interface 20 can be used not only for testing / debugging at the end-use location, but also for testing / debugging (debugging) during development (in the manufacturer's factory). In addition, the device 700 can be used to determine whether an error exists without having to access other interfaces that may be difficult to access, which can be advantageous, for example, when handling complaints.

[0048] like Figure 5 As shown in , the I / O module 130 may also have a wireless interface 30, which is designed to supply power to a wireless interface of a mobile device 800 (which may be configured as a transponder, for example), so that the I / O module 130 can exchange data with the mobile device 800. Here, in addition to the data for configuring the I / O module 130 described above, the data exchange may also include other data, such as data that causes the I / O module 130 to switch from one operating mode to another operating mode.

[0049] For example, a user may carry a plurality of different mobile devices 800 (possibly with different tags or other identifications), wherein each mobile device 800 is equipped with a specific data set, which signals a specific operating mode or represents a specific configuration to the I / O module 130. If the range of the wireless interface is adjusted accordingly, the I / O module 130 can be switched between specific operating modes and / or configurations by holding the mobile device 800 against the I / O module 130.

[0050] Here, the operating mode and the configuration can also be dependent on each other, for example when the fieldbus node 100 is operated independently of the fieldbus network and therefore does not require the fieldbus interface 114 (and accordingly does not need to be taken into account in the configuration of the I / O module 130). Likewise, the I / O module 130 can be preconfigured for different operating modes, so that the I / O module 130 automatically selects the configuration data set assigned to the selected operating mode when the operating mode is switched and uses this configuration data set from then on. In addition, it can also be provided here that the I / O module 130 indicates the success or end of the data transmission connection in an acoustic or optical manner, in order to ensure, for example, when the I / O modules 120, 130 are arranged close to each other, that the correct I / O module 130 is or has been (successfully) addressed.

[0051] Furthermore, a new configuration can also be used when the I / O module 130 is replaced by an I / O module 130 of the same or similar structure. For example, the user can replace the I / O module 130 in the fieldbus node 100 with an I / O module 130 of the same structure and configure the I / O module 130 by placing the mobile device 800 in front. Furthermore, the mobile device 800 can also be used when the I / O module 130 is not configured via the wireless interface 30. For example, the I / O module 130 can be designed so that a (new or re) configuration is performed only after the I / O module 130 is notified by a signal from the mobile device 800 that the configuration is allowed to be performed. Furthermore, in combination with Figure 4 All the data mentioned can also be exchanged with the mobile device 800 via the wireless interface 30 .

[0052] like Figure 6 and Figure 7 As shown in FIG. 1 , the wireless interfaces 20 and 30 can also be used in an I / O module 120, which has an output terminal 124. Figure 6 and Figure 7In addition to the described use possibilities, it can also be provided that the actuator 150 connected to the output 124 of the I / O module 120 is (temporarily) controlled via the device 700 or the device 800. For example, the device 700 can transmit process data via the wireless interface 20 to the I / O module 120, the I / O module 120 derives a control signal from the process data, and the I / O module 120 then outputs the control signal at the output 124.

[0053] Figure 8 A flowchart showing a process of exchanging data between the mobile device 700 or 800 and the I / O modules 120 and 130 using the wireless interface 20 or 30 is shown. Here, the wireless interfaces 20 and 30 form a link between the processor 12 and the mobile devices 700 and 800 after establishing a connection, so that the data received by the mobile devices 700 and 800 can not only be stored but also processed by the processor 12, or the data processed by the processor 12 can be transmitted to the mobile device 700 or 800.

[0054] Reference numerals list

[0055] 10 Circuit

[0056] 12 Processor

[0057] 14 Memory

[0058] 20 Wireless Interface

[0059] 22 Memory

[0060] 30 Wireless Interface

[0061] 32 Memory

[0062] 100 fieldbus nodes

[0063] 110 Fieldbus Coupler

[0064] 112 Bus interface

[0065] 114 Fieldbus interface

[0066] 120 I / O modules

[0067] 122 Bus interface

[0068] 124 Output

[0069] 130 I / O modules

[0070] 132 Bus interface

[0071] 134 Input

[0072] 140 Sensors

[0073] 150 Actuator

[0074] 160 Local Bus

[0075] 200 fieldbus nodes

[0076] 300 fieldbus nodes

[0077] 400 Superior control unit

[0078] 500 Fieldbus

[0079] 600 Computer

[0080] 700 devices

[0081] 800 devices

[0082] 1000 Fieldbus Systems

[0083] 2000 steps

[0084] 2100 Steps

[0085] 2200 steps

Claims

1. Input / output module (120, 130), i.e., I / O module, comprising: An input terminal (134) and / or an output terminal (124) designed to be removably connected to one or more electrical conductors; A bus interface (122, 132) designed to send first process data or receive second process data; as well as The wireless interface (20) is designed to exchange third data with the mobile device (700, 800), wherein the wireless interface (20) is also designed to be powered by the mobile device (700, 800).

2. The I / O module (120, 130) according to claim 1, wherein: The bus interface (122, 132) is designed to send first process data to the field bus coupler (110) or to receive second process data from the field bus coupler (110).

3. The I / O module (120, 130) according to claim 2, wherein: The I / O modules (120, 130) are designed to derive first process data sent to the field bus coupler (110) from a signal input through an input terminal (134), or to derive a signal output at an output terminal (124) from second process data received by the field bus coupler (110).

4. The I / O module (120, 130) according to claim 3, further comprising: Processor (12); as well as A memory (14) in which configuration data are stored, wherein the processor (12) is designed to derive first process data sent to the field bus coupler (110) from a signal input via an input terminal (134) when using the configuration data, or to derive a signal output at an output terminal (124) from second process data received by the field bus coupler (110) when using the configuration data.

5. The I / O module (120, 130) according to claim 4, in, The processor (12) is further configured to cause the first process data to be transferred to the bus interface (122, 132), or the bus interface (122, 132) is configured to cause the second process data to be transferred to the processor (12); and The processor (12) is further designed to transmit fourth data to the wireless interface (20), and the wireless interface (20) is designed to transmit fifth data to the processor (12).

6. The I / O module (120, 130) according to claim 5, wherein: The fourth data is debugging data or diagnostic data.

7. The I / O module (120, 130) according to claim 5, wherein: The processor (12) is also designed to derive configuration data from fifth data transmitted to the processor (12) by the wireless interface (20) and to store the configuration data in the memory (14).

8. The I / O module (120, 130) according to claim 7, wherein: The processor (12) is also designed to check the configuration data and to discard the configuration data if the checking reveals errors in the configuration that would normally result from the configuration data.

9. The I / O module (120, 130) according to claim 5, wherein: The processor (12) is also designed to derive third process data from fifth data transmitted to the processor (12) by the wireless interface (20) and send the third process data to the field bus coupler (11), or to derive a signal output at the output end (124) from the third process data.

10. The I / O module (120, 130) according to claim 5, wherein: The processor (12) is further designed to derive the operating mode of the I / O module (120, 130) from the fifth data and switch to the derived operating mode.

11. Input / output module (120, 130), i.e., I / O module, comprising: An input terminal (134) and / or an output terminal (124) designed to be removably connected to one or more electrical conductors; A bus interface (122, 132) designed to send and receive process data; as well as The first wireless interface (20, 30) is designed to exchange data with a mobile device (700, 800), preferably a transponder, wherein the first wireless interface (30) is also designed to supply energy to a second wireless interface of the mobile device.

12. The I / O module (120, 130) according to claim 11, wherein: The bus interface (122, 132) is designed to send process data to a field bus coupler (110) or to receive process data from a field bus coupler (110).

13. The I / O module (120, 130) of claim 12, further comprising: Processor (12); as well as a memory (14) in which configuration data are stored, wherein the processor (12) is designed to derive first process data sent to the fieldbus coupler (110) from a signal input via an input terminal (134) when using the configuration data, or to derive a signal output at an output terminal (124) from second process data received by the fieldbus coupler (110) when using the configuration data; The processor (12) is further configured to cause the first process data to be transmitted to the bus interface (122, 132), or the bus interface (122, 132) is configured to cause the second process data to be transmitted to the processor (12); and The processor (12) is further designed to transmit fourth data to the wireless interface (30), and the wireless interface (30) is designed to transmit fifth data to the processor (12).

14. The I / O module (120, 130) according to claim 13, wherein: The fourth data is debugging data or diagnostic data.

15. The I / O module (120, 130) of claim 13, wherein: The processor (12) is also designed to: deriving configuration data from fifth data transmitted to the processor (12) by the wireless interface (30) and storing the configuration data in the memory (14); or deriving third process data from fifth data transmitted to the processor (12) by the wireless interface (30), and sending the third process data to the field bus coupler (110); or deriving a signal output at an output terminal (124) from the third process data; or The operating mode of the I / O module (120, 130) is derived from the fifth data and switched to the derived operating mode.

16. A method for exchanging data between an I / O module (120, 130) and a mobile device (700, 800), comprising: establishing (2000) a connection between an I / O module (120, 130) and a mobile device (700, 800) using a wireless interface (20, 30) powered by a communication partner (120, 130, 700, 800); transmitting (2100) data from the mobile device (700, 800) to the I / O module (120, 130) and processing the data by a processor of the I / O module; and / or Data processed by a processor (12) of an I / O module (120, 130) is transmitted (2200) from the I / O module (1200, 130) to a mobile device (700, 800).

Images