Connecting industrial tool to controller

Abstract

The present application relates to a method of a network device (40) connecting a set of industrial tools (10a-n) to a plurality of controllers (30a-n), and a network device performing the method. In one aspect, a method of connecting a set of industrial tools (10a-n) to a network device (40) of a plurality of controllers (30a-n). The method comprises assigning (S101) a single virtual IP address to be shared between the industrial tools (10a-n) in the group, assigning (S102) a single virtual IP address to be shared between the plurality of controllers (30a-n), routing (S103) data between the industrial tools (10a-n) and the controllers (30a-n) through the assigned single virtual IP address.

Description

Technical Field

[0001] The present application relates to a method for connecting an industrial tool group to a network device of multiple controllers, and a network device for executing the method. Background Art

[0002] Modern industrial tools often communicate wirelessly with a remote controller for controlling the tool, for example to send operating settings to be applied by the tool or instructions to be displayed to an operator via a display of the tool. In another example, the tool (e.g., a tightening tool) can transmit measured torque values ​​to a controller for further evaluation.

[0003] In a practical implementation, for example in an industrial setting in the form of a factory, a large set of tools may be connected to a large number of controllers. Thus, hundreds of tools may be connected to hundreds of controllers.

[0004] Such a practical implementation requires the allocation of a large number of network resources. In particular, each tool and each controller must be assigned an Internet Protocol (IP), via which the respective tool and controller can be addressed. Summary of the invention

[0005] An object is to solve or at least alleviate this problem in the art and therefore to provide an improved method of connecting a group of industrial tools to a network arrangement of a plurality of controllers.

[0006] In a first aspect, the object is achieved by a method of a network device connecting a group of industrial tools to a plurality of controllers (i.e., a method performed by the network device), the method comprising allocating a single virtual IP address to be shared among the industrial tools in the group, allocating a single virtual IP address to be shared among the plurality of controllers, and routing data between the industrial tools and the controllers through the allocated single virtual IP address.

[0007] In a second aspect, the object is achieved by a network device configured to connect a group of industrial tools to multiple controllers, the network device comprising a processing unit and a memory, the memory containing instructions executable by the processing unit, wherein the network device is capable of operating to assign a single virtual IP address to be shared among industrial tools in the group, assign a single virtual IP address to be shared among multiple controllers, and route data between the industrial tools and the controllers through the assigned single virtual IP address.

[0008] Advantageously, rather than assigning dozens or hundreds of static IP addresses to tools and controllers, one specific IP address per tool and one specific IP address per controller, a single virtual IP address is assigned to connect a specific tool to a specific controller, which saves network resources in the form of IP addresses.

[0009] In an embodiment, the method includes assigning a unique identifier to each industrial tool in the group, the unique identifier being used to address a single industrial tool in the group via an assigned single virtual IP address.

[0010] In an embodiment, the method includes assigning a unique identifier to each controller, the identifier being used to address a single controller of the plurality of controllers via an assigned single virtual IP address.

[0011] In an embodiment, the identifier is included in a data packet for transmission to a selected single industrial tool or a selected single controller via an assigned single virtual IP address.

[0012] In an embodiment, the method includes performing packet inspection to extract an identifier, determining based on the extracted identifier a single industrial tool (or controller) to which the packet is routed via an assigned single virtual IP address.

[0013] In an embodiment, the identifier is a serial number of a single industrial tool or controller.

[0014] In an embodiment, the method includes storing operational data for each industrial tool.

[0015] In an embodiment, the industrial tool is a tightening tool.

[0016] In a third aspect, there is provided a computer program comprising computer executable instructions, which, when executed on a processing unit included in a network device, cause the network device to perform the steps described in the method according to the first aspect.

[0017] In a fourth aspect, there is provided a computer program product comprising a computer readable medium having embodied thereon the computer program according to the third aspect.

[0018] Generally, unless otherwise explicitly defined herein, all terms used in the claims should be interpreted according to their ordinary meaning in the technical field. Unless otherwise explicitly stated, all references to "a / an / element, device, component, means, step, etc." should be openly interpreted as referring to at least one instance of an element, device, component, means, step, etc. Unless explicitly stated otherwise, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Various aspects and embodiments will now be described by way of example with reference to the accompanying drawings, in which:

[0020] Figure 1 An industrial tool is shown in which tool embodiments may be implemented;

[0021] Figure 2 A communication scenario of the prior art is shown;

[0022] Figure 3 shows a network device according to an embodiment;

[0023] Figure 4 A flow chart showing a method according to an embodiment;

[0024] Figure 5 shows a network device for routing data from a controller to a tool according to an embodiment;

[0025] Figure 6 shows a flow chart of a method according to another embodiment;

[0026] Figure 7 shows a flow chart of a method according to a further embodiment;

[0027] Figure 8 A network device according to an embodiment is shown. DETAILED DESCRIPTION

[0028] Various aspects of the application will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the invention are shown.

[0029] However, these aspects can be implemented in many different forms and should not be interpreted as limiting; on the contrary, these embodiments are provided by way of example, so that this application will be thorough and complete, and the scope of all aspects of the invention will be fully conveyed to those skilled in the art. Throughout the specification, the same numerals represent the same elements.

[0030] Figure 1 An industrial tool in which tool embodiments may be implemented is shown in the form of a tightening tool 10 configured to apply torque to a fastener, such as a bolt 20 .

[0031] The tightening tool 10 may be cordless or cord-powered and has a body 11 and a tool head 12. The tool head 12 has an output shaft 13 having a socket (not shown) configured to be rotatably driven by a motor disposed in the body 11 to apply torque to the bolt 20.

[0032] The tightening tool 10 may be provided with a display 14 , by which information relating to the operation of the tool 10 may be presented to an operator of the tool 10 , and an interface 15 , by which the operator may input data into the tool 10 .

[0033] The tightening tool 10 may further be provided with communication functionality in the form of a radio transmitter / receiver 16 for wirelessly transmitting operating data (e.g. applied torque) to a remote controller (e.g. a cloud server 30). Alternatively, communication between the tool 10 and the controller 30 may be via a wired connection.

[0034] Thus, tool 10 may, for example, communicate measured torque values ​​to controller 30 for further evaluation, and controller 30 may, for example, send operating settings to be applied by tool 10 or instructions to be displayed to an operator via display 14 .

[0035] Now refer to Figure 2 In actual implementation, for example in an industrial location in the form of a factory, a large group of tools 10a, 10b, ..., 10n may be connected to a large number of controllers 30a, 30b, ..., 30n. Thus, hundreds of tools may be connected to hundreds of controllers.

[0036] Such a practical implementation requires the allocation of a large number of network resources. In particular, each tool and each controller must be assigned an Internet Protocol (IP), via which the respective tool and controller can be addressed.

[0037] To solve this problem, a network device 40 is provided, which is configured to connect the tools 10a-n to the controllers 30a-n, such as Figure 3 Thus, the network device 40 acts as an intermediary device for connecting the tools 10a-n to the controllers 30a-n.

[0038] Further references Figure 4 , Figure 4 A flow chart illustrating a method of connecting an industrial tool group 10a-10n to a network device 40 of a plurality of controllers 30a-30n.

[0039] Thus, at step S101 , the network device 40 assigns to the tool group 10a - b a single virtual IP address (SVIP) to be shared between the tools 10a - 10b.

[0040] Further, in step S102, the network device 40 allocates a single virtual IP address to the controllers 30a-n, also for sharing among the controllers.

[0041] Thereafter, at step S103 , any data transmitted between the industrial tools 10 a - c and the controllers 30 a - c (in either direction) is routed through the single virtual IP address assigned by the network device 40 .

[0042] Advantageously, rather than assigning dozens or hundreds of static IP addresses to tools 10a-n and controllers 30a-n, one specific IP address for each tool and one specific IP address for each controller, a single virtual IP address is assigned to connect a specific tool to a specific controller, which saves network resources in the form of IP addresses.

[0043] Figure 5 and Figure 6 A further embodiment is shown.Since the tools 10a-10n and controllers 30a-n share a single assigned virtual IP address, data to be transmitted from the controller to the tools (or vice versa) must be addressed in some way to the single tool to which the data is destined.

[0044] Therefore, at step S104, the network device 40 assigns a unique identifier to each industrial tool 10a-n in the group of industrial tools, the unique identifier being used to address the individual industrial tools in the group via the assigned single virtual IP address.

[0045] Similarly, to enable communication in the direction from tools 10a-n to controllers 30a-n, at step S105 the network device 40 assigns to each controller 30a-n a unique identifier which is used to address the individual controllers via the assigned individual virtual IP address.

[0046] For example, assuming that the first controller 30a wishes to send control data to the first tool 10a, the first controller will address the first tool using the unique identifier that has been assigned to the first tool 10a.

[0047] When the network device 40 receives data from the first controller 30a via the assigned single virtual IP address, the network device 40 will determine the tool specified by the data, namely the first tool 10a, based on the identifier declared by the first controller 30a, and therefore forward the data to the first tool 10a via the assigned single virtual first IP address.

[0048] In an example, the network device 40 will establish a mapping table where each unique identifier is mapped to a physical tool / controller.

[0049] An example of a tool-identifier mapping is shown below. As will be appreciated, a similar mapping is performed for the controller.

[0050] 10001àFirst tool 10a

[0051] 10002àthe second tool 10b, and so on.

[0052] In an embodiment, the identifier used is the serial number of the tool (and similarly the controller). In the above example, the serial number of the first tool 10a is "10001", while the serial number of the second tool 10b is "10002".

[0053] Assuming that the first controller 30a wants to establish a connection with a tool (e.g., the first tool 10a) (or vice versa), the first controller 30a transmits a data packet to the assigned single virtual IP address. The data packet may have the following representation:

[0054] 10001 Payload data

[0055] In other words, the transmitted data packet will include an identifier of the first tool 10a (in this example, the serial number of the tool), followed by any payload data to be transferred to the tool, such as an operating setting to be changed on the tool 10a (e.g., regarding the torque to be applied). In the case of transmission in the other direction, that is, from the first tool 10a to the first controller 30a, the payload data may include dynamic and static information describing the tool.

[0056] Reference Figure 7 , the network device 40 will therefore conclude through packet inspection at step S106 that the packet should be delivered to the first tool 10a via the assigned single virtual IP address, and not to any other tool in the tool group that is also assigned a single virtual IP address, at step S107. If transmission is made in the other direction, the data is delivered to a designated controller in the controller group. Therefore, the network device 40 will route the data to the correct tool or controller based on the extracted identifier and the mapping from tool identifier to controller identifier.

[0057] The network device 40 will establish a connection with the tool 10a and also with the controller 30a, forwarding the payload data from the tool 10a or controller 30a depending on the direction of transmission. Further communications back and forth between the tool and controller will be routed through the network device 40 using a single virtual IP address over the established connection.

[0058] For example, network device 40 may utilize a locally stored lookup table to determine to which individual tool (or controller) a data packet is to be delivered by associating the corresponding tool (or controller) with an identifier in the lookup table.

[0059] A further advantage of using a single virtual IP address is that if one or more tools or controllers are moved, no reconfiguration is required; the single virtual IP address and identifier can still be used.

[0060] Additionally, for example, if a controller is disconnected or a controller fails, tools served by that controller can be quickly redirected to another controller.

[0061] It is a further advantage that all tools may have the same network configuration regardless of which controller application the tool is assigned to.

[0062] In another embodiment, the network device 40 hosts a database that serves as an inventory of all connected tools, the database containing data and indicators for each individual tool.

[0063] The steps of the method to be described below performed by the network device 40 are actually performed by a processing unit 41, which is implemented in the form of one or more microprocessors and is configured to execute a computer program 42 downloaded to a storage medium 43 associated with the microprocessor (e.g., a random access memory (RAM), a flash memory, or a hard drive). The processing unit 41 is configured so that when a suitable computer program 42 including computer executable instructions is downloaded to the storage medium 43 and executed by the processing unit 41, the network device 40 performs a method according to the embodiment. The storage medium 43 can also be a computer program product including the computer program 42. Alternatively, the computer program 42 can be transferred to the storage medium 43 via a suitable computer program product (e.g., a digital versatile disc (DVD) or a memory stick). As a further alternative, the computer program 42 can be downloaded to the storage medium 43 via a network. The processing unit 41 can optionally be implemented in the form of a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a complex programmable logic device (CPLD), etc. The network device 40 further includes an interface through which the processing unit 41 receives and sends data wirelessly.

[0064] Various aspects of the application have mainly been described above with reference to a few embodiments and examples thereof. However, as readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the invention as defined by the appended patent claims.

[0065] Therefore, although various aspects and embodiments are disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for illustrative purposes and are not intended to be limiting, with the true scope and spirit being indicated by the appended claims.

Claims

1. A method for connecting an industrial tool group (10a-n) to a network device (40) of a plurality of controllers (30a-n), comprising: Allocating (S101) a single virtual IP address to be shared among industrial tools (10a-n) in the group; allocating (S102) a single virtual IP address to be shared among a plurality of controllers (30a-n); Data between the industrial tools (10a-n) and the controllers (30a-n) are routed through the assigned single virtual IP address (S103).

2. The method according to claim 1, further comprising: A unique identifier is assigned (S104) to each industrial tool (10a-n) in the group, the unique identifier being used to address the individual industrial tools (10a-n) in the group via the assigned single virtual IP address.

3. The method according to claims 1 and 2, further comprising: Each controller (30a-n) is assigned (S105) a unique identifier for addressing a single controller (30a-n) of the plurality of controllers via the assigned single virtual IP address.

4. The method according to claim 2 or 3, wherein the identifier is included in a data packet to be transmitted to a selected single industrial tool (10a) or a selected single controller (30a) via an assigned single virtual IP address.

5. The method according to claim 4, further comprising: performing (S106) packet inspection to extract the identifier; A single industrial tool (10a) or controller (30a) to which the data packet is routed via the assigned single virtual IP address is determined (S107) based on the extracted identifier.

6. The method according to any one of claims 2 to 5, the identifier being a serial number of a single industrial tool (10a-n) or controller (30a-n).

7. The method according to any one of the preceding claims, further comprising: Operational data for each industrial tool (10a-n) is stored.

8. A method according to any one of the preceding claims, wherein: The industrial tool (10a-n) is a tightening tool.

9. A computer program (42) comprising computer executable instructions which, when executed on a processing unit (41) included in a network device (40), cause the network device (40) to perform the steps according to any one of claims 1 to 8.

10. A computer program product comprising a computer readable medium (43) having embodied thereon a computer program (42) according to claim 9.

11. A network device (40) configured to connect an industrial tool group (10a-n) to a plurality of controllers (30a-n), the network device (40) comprising a processing unit (41) and a memory (43), the memory containing instructions (42) executable by the processing unit (41), wherein: The network device (40) is operable to: allocating a single virtual IP address to be shared among the industrial tools (10a-n) in the group; allocating a single virtual IP address to be shared among multiple controllers (30a-n); Data between industrial tools (10a-n) and controllers (30a-n) are routed through an assigned single virtual IP address.

12. The network device (40) according to claim 11, further operable to: Each industrial tool (10a-n) in the group is assigned a unique identifier, the unique identifier being used to address the individual industrial tools (10a-n) in the group via the assigned single virtual IP address.

13. The network device (40) according to claim 11 or 12, further operable to: Each controller (30a-n) is assigned a unique identifier that is used to address a single controller (30a-n) of the plurality of controllers via an assigned single virtual IP address.

14. The network device (40) according to claim 12 or 13, wherein the identifier is included in a data packet to be transmitted to a selected single industrial tool (10a) or a selected single controller (30a) via an assigned single virtual IP address.

15. The network device (40) according to claim 14, further operable to: Perform packet inspection to extract identifiers; A single industrial tool (10a) or controller (30a) to which the data packet is routed via the assigned single virtual IP address is determined based on the extracted identifier.

Images