Industrial controller having a housing and a computing unit

Abstract

The aim of the invention is to be able to more easily access an industrial controller (100) having a housing (99) in which a first printed circuit board (LP1) having a computing unit (1) is arranged, the industrial controller further having an operating system (2) and an application program (AW). To achieve this aim, a second printed circuit board (LP2) is arranged below a front face (Vo) of the housing (99); the second printed circuit board (LP2) has a conductor loop (LS) in the form of an NFC antenna. The operating system (2) can output data to the outside via an NFC component (D5).

Description

[0001] Description

[0002] Industrial control with one housing and one processing unit

[0003] The invention relates to an industrial control system with a housing in which a first circuit board with a computing unit is arranged, further comprising an operating system and a user program which is executed in the computing unit to control an industrial process, wherein the computing unit has a data memory, and the operating system is designed to process the user program cyclically.

[0004] For the purposes of the invention, an industrial controller is preferably understood to mean a programmable logic controller (PLC), which is an automation device used to control or regulate a machine or system in an industrial environment. In a cycle-oriented PLC, this cycle is controlled by an operating system permanently stored by the manufacturer. Depending on its program modules, the control program can contain branches and conditional calls, which result in different execution times.

[0005] EP 2 477 085 B1 already describes such an industrial controller. The disadvantage of existing industrial controllers is that a PC must be connected to the controller, even if one simply wants to collect information or make a simple change to the PLC. Currently, a specialist must connect to the PLC programming software or web browser via the PC to interact with the PLC.

[0006] US 2015 / 0097669 A1 discloses an industrial controller with NFC functionality and shows the basic idea of ​​NFC communication in industrial environments.

[0007] US 2014 / 0266025 A1 covers NFC communication in electronic devices and provides general information on NFC technology.

[0008] EP 3 151 098 A1 deals with the security of NFC communication, but not with industrial controllers. It is an object of the present invention to provide an industrial controller that can be securely accessed with a read / write device via NFC.

[0009] The object is achieved by providing an NFC component, wherein a second circuit board is arranged beneath a front side of the housing. The second circuit board has a conductor loop configured as an NFC antenna with a first endpoint and a second endpoint. The NFC component has a first antenna input, a second antenna input, a data interface, and a signaling output. The NFC component is configured to output a signal via the signaling output when a communication request is detected via the NFC antenna. The first endpoint is connected to the first antenna input, and the second endpoint is connected to the second antenna input. Furthermore, the computing unit has a signaling input and a counter interface. The signaling input is connected to the signaling output, and the counter interface is connected to the data interface.The operating system is configured to detect a signal at the signaling input. It is further configured to query a configuration file stored in the data memory and, depending on the query result, to permit data communication on the counterpart interface. The operating system is further configured to read a serial number of the industrial controller during data communication and to transfer it to an NFC read / write device. The operating system is further configured to temporarily store an identification serial number supplied by the NFC read / write device and assigned to the write request in the data memory during data communication with a write request, read the industrial controller's own serial number, compare the serial numbers, and, if the serial numbers are identical, execute the write request.

[0010] With an NFC component and the appropriate antenna integrated into the industrial control system, the technician can easily retrieve information from the industrial control system. This works with the power off and on. For example, if a technician brings a smartphone with a suitable app close (approximately 1-2 cm) to the front of the industrial control system, the industrial control system communicates with the phone.

[0011] A further embodiment of the industrial control system provides that the operating system is further configured to read a data entry from the configuration file in which read / write rights are stored, the operating system is further configured to check the read / write rights and, in the event that only read rights exist, to not allow any write requests to the data memory and / or the configuration file and / or a process image and / or a variable management of the user program via the counterpart interface.

[0012] Once the initial read operation is complete, a subsequent write operation is possible, but not required; this is at the discretion of the technician. However, the initial read should preferably be performed to obtain the serial number, ensuring that writing is secure.

[0013] The serial number is unique to each industrial controller manufactured and is used in subsequent NFC write operations to ensure that the NFC reader / writer attempting to perform the write operation is also connected to the industrial controller, which is displayed on the NFC reader / writer screen of the mobile application. Therefore, there is a two-step process for writing data using NFC. A read operation must be performed to identify the CPU, and then a second user-initiated NFC write operation can be performed. The serial number is used in the NFC write operation to verify the industrial controller.

[0014] A further design of the industrial control system provides that the operating system is designed to compile diagnostic data and make it available for query at the counterpart interface.

[0015] For example, a specialist can view cycle time, memory utilization, alarms, and diagnostic buffer information on their smartphone. If the NFC read / write device is a smartphone, a corresponding app is installed on the smartphone. This app then has a main screen with buttons. For these buttons to be active, at least one industrial controller must have been successfully scanned and assigned as a selected device. Pressing the Diagnostics button on the main screen displays the "Diagnostics" screen. The following can be performed on the Diagnostics screen.

[0016] Display diagnostics on the industrial controller and its associated modules. • Display information about the device configuration compared to the actual hardware on the industrial controller.

[0017] • Display information about the properties of a memory card

[0018] • Display cycle times

[0019] • Show used vs. free memory

[0020] • Display the diagnostic buffer.

[0021] A further design of the industrial control system provides that the operating system is designed to compile configuration data from other modules connected to the industrial control system via a backplane bus and to make it available for query at the counterpart interface.

[0022] In this way, a hardware configuration of the assemblies, modules, input / output assemblies, communication assemblies, etc. could be displayed on the smartphone.

[0023] A further embodiment of the industrial control system provides that the operating system is designed to search the configuration file for a watch list of variables, to fill the variables of the watch list with the current values ​​of the process image, and to make them available for query at the counterpart interface.

[0024] A further embodiment of the industrial control system provides that the operating system is designed to search the configuration file for a control list of variables, to fill the variables of the control list with the current values ​​of the process image, and to make them available for query at the counterpart interface, and is further designed to receive the control list with changed values ​​at the counterpart interface and to write them into the current process image.

[0025] When the "Watch / Force Tables" button or the "Watch / Force Tables" button on the main screen is pressed on the app, the "Watch / Force Tables" screen is displayed. Watch and force tables are optionally configured in advance in an engineering system for the industrial control system. If neither of the two tables is configured in the engineering system and downloaded to the industrial control system, the mobile NFC application must indicate that no tables are available.

[0026] A further embodiment of the industrial control system provides that the operating system is configured to configure the NFC component when the industrial control system is switched on for the first time. For this purpose, the operating system is configured to delete an EEPROM memory of the NFC component, create a CC file, and format the EEPROM memory in accordance with NDEF starting from the end of the CC file.

[0027] Accordingly, the operating system, i.e. the firmware of the industrial control system, must perform the following steps:

[0028] 1) Erase the entire EEPROM memory.

[0029] 2) Generate a CC file with the following data: E2 40 00 01 00 00 03 FF.

[0030] 3) Format the remaining memory after the CC file so that it is NDEF compliant.

[0031] This can be achieved by placing a properly formatted NDEF message as a default on the EEPROM.

[0032] The CC file is 8 bytes and should be saved as follows:

[0033] “E2 43 00 01 00 00 3F FE”.

[0034] To ensure the most trouble-free communication between the smartphone and the industrial controller, the antenna design is crucial. Excellent results were achieved with an antenna with a length of approximately 53.5 mm, a width of approximately 35.7 mm, and six windings. Additionally, the windings are spaced approximately 0.23 mm apart, have a width of approximately 0.23 mm, and a winding thickness of 35 μm.

[0035] The antenna is a circuit trace with a specific trace width, a specific trace spacing, and a specific number of turns to tune the conductor loop to the carrier frequency of 13.576 MHz. The antenna therefore has an inductance of 4.43 pH at 13.56 MHz, and the thickness of the circuit board is approximately 1 mm.

[0036] 1 ,6 mm and £ r is equal to 4.6.

[0037] The industrial controller or antenna is further improved if an ESD suppression component is arranged between the first and second endpoints. In the industrial controller, the processing unit is advantageously designed as an application-specific integrated circuit with processors, interfaces, memory, memory management, a runtime environment for the operating system, and Profinet interfaces.

[0038] Other benefits include: a. Mobile phone access to PLC identification data. b. Mobile phone access to diagnostic data. c. Mobile phone access to read PLC data variables that control the manufacturing process. d. Access to data variables that control the manufacturing process. e. Mobile phone access to change the CPU operating mode from RUN to STOP or STOP to RUN. f. Using the mobile phone, the customer can now simply browse the PLC data with a snap of the finger to scroll through one large set of data. A significant improvement in usability over all front panel displays in existing PLCs. g. Mobile phone access and historical recording and storage of PLC data for 100 NFC-scanned PLCs. This data can then be retrieved later in the office and analyzed if necessary. h. Mobile phone access to write the IP suite to troubleshoot computer connection problems over Ethernet. i.Mobile phone access can be configured: blocked, read-only, read / write, or read / write but with a password.

[0039] A professional can now easily use their mobile phone with a corresponding app and simply "tap" the front of the PLC. When the professional brings their mobile phone close (~1-2 cm) to the front of the PLC, the PLC communicates with the phone.

[0040] Data transfers (scans) are performed when the application is "ready to scan" by holding the phone within 10 cm of the NFC tag on the front of the CPU. For security, a double tap is performed: the first tap reads the serial number, and a second tap compares the serial number. At this point, write commands can also be scheduled.

[0041] Now there is also a way to detect an industrial control system in the warehouse through the packaging material.

[0042] The drawing shows an embodiment of the invention, showing

[0043] FIG 1 an industrial control system in a perspective and cutaway view,

[0044] FIG 2 the circuit boards from the industrial control system,

[0045] FIG 3 is a schematic block diagram of the function of the first circuit board in connection with the second circuit board,

[0046] FIG 4 shows an example of an antenna being connected to an NFC component and

[0047] FIG 5 shows the layout of an EEPROM memory of the NFC component.

[0048] FIG. 1 shows an industrial controller 100 with a housing 99. A first circuit board LP1 with a computing unit 1 is arranged in the housing 99. A second circuit board LP2 is arranged below a front side Vo of the housing 99. The second circuit board LP2 has a conductor loop LS configured as an N FC antenna with a first end point P1 and a second end point P2 (see FIG. 3).

[0049] The computing unit 1 (see FIG. 3) has an operating system 2 and a user program AW in a data memory 3. The computing unit 1 is designed, specifically in the context of programmable logic controllers, to execute or process the user program AW cyclically. To enable a specialist to easily access diagnostic data, variables, control lists, or watch lists of the industrial controller 100, the industrial controller 100 is configured such that an NFC component D5 is present on the second circuit board LP2. For this purpose, the second circuit board LP2 is arranged below the front side Vo of the housing 99. The second circuit board LP2 has a conductor loop LS configured as an NFC antenna with a first end point P1 and a second end point P2.

[0050] FIG. 2 shows the arrangement of the first circuit boards LP1 and LP2 within the housing 99. The first circuit board LP1 houses the computing unit 1, while the second circuit board LP2 houses the NFC component D5 and the conductor loop LS configured as an NFC antenna. To enable the first circuit board LP1 to communicate with the second circuit board LP2, a third circuit board LP3 with corresponding signal lines is arranged between the first circuit board LP1 and the second circuit board LP2 via connectors.

[0051] FIG 3 schematically shows the structure of the industrial controller 100 with an NFC receiver on the second circuit board LP2. The NFC component D5 is arranged on the second circuit board LP2. This component has a first antenna input AC0, a second antenna input AC1, a data interface SDA, and a signaling output GPO. The NFC component D5 is designed to output a signal via the signaling output GPO when a communication request is detected via the NFC antenna. The computing unit 1 has a signaling input GPI and a counter interface GSDA. The signaling input GPI is connected to the signaling output GPO of the second circuit board LP2. The counter interface GSDA of the computing unit 1 is connected to the data interface SDA of the NFC component D5.The operating system 2 is configured to recognize a signal at the signaling input GPI as an interrupt, and is thus further configured to query a configuration file HWC stored in the data memory 3. This query determines whether the industrial controller 100 with the processing unit 1 is configured to allow data communication on the counterpart interface GSDA. For this purpose, the operating system 2 is configured to provide a query result 4.

[0052] The operating system 2 is further configured to read a data entry from the configuration file HWC in which read / write rights 5, 5a are stored. The operating system 2 is further configured to check the read / write rights 5 and, if only read rights 5a are present, to disallow any write requests to the data memory s and / or to the configuration file HWC and / or to a process image 6 and / or to a variable management 7 of the user program AW via the counterpart interface GSDA.

[0053] Furthermore, the operating system 2 is designed to read a serial number SN of the industrial controller 100 during data communication and to transfer it to an NFC read / write device 8.

[0054] Furthermore, the operating system 2 is designed to temporarily store an identification serial number ISN supplied by the N FC read / write device 8 and assigned to the write request 9 in the data memory 3 via a data communication with a write request 9.

[0055] In order to ensure that when a write request 9 is issued by an N FC read / write device 8 to the industrial controller 100, this selected industrial controller 100 is also meant, the operating system 2 is further configured to temporarily store an identification serial number ISN supplied by the N FC read / write device 8 in the case of a write request 9 to the data memory 3 and to compare it with its own serial number SN.

[0056] If the serial numbers are identical, the write job can be carried out.

[0057] The serial number SN is unique for each manufactured industrial controller 100 and is used in subsequent NFC write operations 9 to ensure that the NFC read / write device 8 attempting to perform the write operation is also connected to the industrial controller 100 displayed on the NFC read / write device screen of the mobile application. Accordingly, there is a two-step process for writing data using NFC. A read operation must be performed to identify the industrial controller 100, and then a second user-initiated NFC write operation can be performed. The serial number SN is used in the NFC write operation to verify the industrial controller.

[0058] The operating system 2 is also designed to compile diagnostic data DD and make it available for querying at the counterpart interface GSDA. The operating system 2 is also designed to compile configuration data CD from other modules connected to the automation controller 100 via a backplane bus and make it available for querying at the counterpart interface GSDA. The operating system 2 can also search the configuration file HWC for a watch list BL of variables V1, ..., 10. The variables V1, ..., V10 of the watch list BL are then filled with current values ​​from the process image 6 and made available for querying at the counterpart interface GSDA.

[0059] In order to also be able to control variables V1,...,V10 in the user program AW, operating system 2 is configured to search the HWC configuration file for a control list SL of variables V1,...,V10. Variables V1,...,V10 of the control list SL are also filled with current values ​​from process image 6 and made available for query at the counterpart interface GSDA. In order to actually control variables V1,...,V10, operating system 2 is further configured to receive the control list SL with modified values ​​at the counterpart interface GSDA and write it to process image 6.

[0060] FIG 4 shows a circuit diagram showing how the conductor loop LS is connected to the NFC component D5. The actual conductor loop LS, i.e. the NFC antenna, is connected to a first antenna input AC0 and a second antenna input AC1. An ESD suppressor component V1 is arranged between the first endpoint P1 and the second endpoint P2. This serves to eliminate electrostatic charges that may affect the conductor loop LS. The ESD suppressor component V1 is connected to a supply voltage of 3.3 volts via a VCC connection via a resistor R7. A GND connection of the ESD suppressor component V1 is connected to ground M. The signal path from the conductor loop LS to the actual antenna inputs AC0.AC1 extends via the third circuit board LP3 mentioned in FIG 2. To absorb interference, capacitors C2, C4, C5, and C1 are installed. The NFC component D5 is also connected to a 3.3 volt supply voltage.It is supplied with a clock input CLK and is also connected to ground M. The NFC component D5 has the data interface SDA and the signaling output GPO as outputs.

[0061] FIG 5 shows how an EEPROM memory EE of the NFC component D5 is configured by the operating system 2 when switched on for the first time. In the previously empty EEPROM memory EE shown on the left, a CC file cc is created in the right figure, a first memory area 10, a second memory area 11 and a third memory area 12. The EEPROM memory EE is formatted in the EF comfort starting from the end of the CC file cc. The CC file cc is structured as follows. It comprises eight bytes: Byte 0 to Byte 7. Byte 0 contains a magic number for an address mode used later. Byte 0 contains a version and access number. Byte 2 is set to 00h. Byte 3 contains additional feature information. Byte 4 and Byte 5 are reserved for future features. RFU reserved before Future. Byte 6 and byte 7 describe the length of the NDEF area of ​​the EEPROM.

[0062] The magic number represents the 2-byte address mode. The major version is 1 and the minor version is 0. When the access control RF-NDEF is read-only.

[0063] Byte 3 is determined based on the features available on the NFC component itself, where 00h stands for fully feature.

[0064] RFU is reserved for future use, ie 00h.

[0065] MLEN must be set to represent 8176 bytes of the NDEF area. 8 bytes are reserved for the CC file cc and 8 bytes for the industrial controller 100, which means it is outside the NDEF area.

[0066] Byte 1 is read-only, which tells NFC applications not to write an NDEF message, but does not appear to control the writing itself.

[0067] For example, "WriteSingleBlock" and "WriteMultipleBlock" must also be blocked, but operate with this byte set as read-only.

[0068] The firmware or operating system must configure the NFC component D5 to block all RF write operations to the EEPROM.

[0069] The first memory area 10 is formatted for the NDEF NFC Data Exchange Format, creating TLV blocks. TLV stands for Type, Length, and Value. The second memory area 11 is still free, and the third memory area 12 is currently unused.

Claims

Patent claims 1. An industrial controller (100) comprising a housing (99) in which a first circuit board (LP1) with a computing unit (1) is arranged, further comprising an operating system (2) and a user program (AW) which is executed to control an industrial process in the computing unit (1), wherein the computing unit (1) has a data memory (3) and the operating system (2) is configured to cyclically process the user program (AW). Furthermore, an NFC component (D5) is provided, wherein a second circuit board (LP2) is arranged below a front side (Vo) of the housing (99). The second circuit board (LP2) has a conductor loop (LS) configured as an NFC antenna with a first end point (P1) and a second end point (P2). The NFC component (D5) has a first antenna input (AC1), a second antenna input (AC1), a data interface (SDA), and a signaling output (GPO). on,the NFC component (D5) is designed to output a signal via the signaling output (GPO) when a communication request is detected via the NFC antenna, the first endpoint (P1) is connected to the first antenna input (ACO) and the second endpoint (P2) is connected to the second antenna input (AC1), furthermore the computing unit (1) has a signaling input (GPI) and a counter interface (GSDA), the signaling input (GPI) is connected to the signaling output (GPO) and the counter interface (GSDA) is connected to the data interface (SDA), characterized in that the operating system (2) is designed, • to detect a signal at the signaling input (GPI), furthermore it is designed • to query a configuration file (HWC) stored in the data memory (3) and to allow data communication on the counterpart interface (GSDA) depending on the query result (4), the operating system (2) is further configured to read out a serial number (SN) of the industrial controller (100) during data communication and to transfer it to an NFC read / write device (8), wherein the operating system (2) is further configured to temporarily store an identification serial number (ISN) supplied by the NFC read / write device (8) and assigned to the write request (9) during data communication with a write request in the data memory (3), to read out the industrial controller's own serial number (SN) and to carry out a comparison of the serial numbers (ISN, SN) and in case the serial numbers (ISN, SN) are identical, to carry out the write request (9).

2. Industrial control (100) according to claim 1, wherein the operating system (2) is further configured to read out a data entry from the configuration file (HWC) in which read / write rights (5) are stored, the operating system (2) is further configured to check the read / write rights (5) and, in the event that only a read right (5a) is present, to permit no write requests to the data memory (3) and / or to the configuration file (HWC) and / or to a process image (6) and / or to a variable management (7) of the user program (AW) via the counterpart interface (GSDA).

3. Industrial control (100) according to one of claims 1 or 2, wherein the operating system (2) is designed to compile diagnostic data (DD) and to provide it for query at the counterpart interface (GSDA).

4. Industrial control (100) according to one of claims 1 to 3, wherein the operating system (2) is designed to compile configuration data (CD) from further modules connected to the industrial control (100) via a backplane bus and to make them available for querying at the counterpart interface (GSDA).

5. Industrial control (100) according to one of claims 1 to 4, wherein the operating system (2) is designed to search the configuration file (HWC) for a watch list (BL) of variables (V1,...,V10), to fill the variables (V1,...,V10) of the watch list (BL) with the current values ​​of the process image (6), and to make them available for querying at the counterpart interface (GSDA).

6. Industrial control (100) according to one of claims 1 to 5, wherein the operating system (2) is designed to search the configuration file (HWC) for a control list (SL) of variables, to fill the variables (V1,...,V10) of the control list (SL) with the current values ​​of the process image, and to make them available for query at the counterpart interface (GSDA), further designed to receive the control list (SL) with changed values ​​at the counterpart interface (GSDA) and to write them into the current process image (6).

7. Industrial control (100) according to one of claims 1 to 6, wherein the operating system (2) is designed to configure the NFC component (D5) when the industrial control (100) is switched on for the first time, for this purpose the operating system (2) is designed to delete an EEPROM memory of the NFC component (D5), to create a CC file (cc), to format the EEPROM memory in accordance with NDEF from the end of the CC file (cc).

8. Industrial control (100) according to one of claims 1 to 7, wherein the conductor loop (LS) on the second printed circuit board (LP2) has a length (I) of approximately 53.5 mm, a width (b) of approximately 35.7 mm and a number of turns of six, additionally the turns are spaced approximately 0.23 mm apart from one another and have a width of approximately 0.23 mm, a thickness of the turn is 35 pm.

9. Industrial control (100) according to one of claims 1 to 8, wherein an ESD suppression component (V1) is arranged between the first end point (P1) and the second end point (P2) in terms of circuitry.

10. Industrial control (100) according to one of claims 1 to 9, wherein the computing unit (1) is designed as an application-specific integrated circuit (ASIC) with processors, interfaces, memory, memory management, runtime environment for the operating system and Profinet interfaces.

Images