SECOND TOOL ASSOCIATED WITH A TOOL CONTROLLER

TECHNICAL FIELD

The present disclosure relates to a method, a tool

controller, and a computer program to enable different functionality sets for at least a first and a second tool associated with a tool controller

BACKGROUND

[0001] Assembling of today are often complex. An assembling process may include assembling more or less complex objects where the components are assembled together. It is often high requirements on the manufacturing steps performed so that the manufacturing steps are performed correctly.

[0002] In assembling processes, different types of tools are used. It is often important that the tools are able to perform different types of functions. However some tools can only perform less advanced functions. While other tools can perform more advanced functions. There is therefore a need to control which types of functions that can be performed by different types of tools.

[0003] It is also important that the results from the

different types of tool are presented and stored in an appropriate way. [0004] There is therefore a need for an improved solution to enable flexible functionality sets for different types of tools. And thereby provide a solution that capture different types of functionality requirements for different tools.

SUMMARY

[0005] It is an object of the present disclosure to address at least some of the problems outlined above, e.g. to ensure flexible functionality sets for different tools. And thereby provide a solution that capture new functionality

requirements for different tools.

[0006] Another object of the present disclosure is to enable new functions of a tool controller without changing the actual software of the tool controller and thereby making unforeseen changes to the tool controller. This makes it possible to adapt to new requirements without software updates of the tool controller and its corresponding long lead times.

[0007] In accordance with a first aspect the disclosure relates to a method for enabling different functionality sets for at least a first and a second tool. The method comprising the steps of. Retrieving at least a first license type. The first license type specifies a first set of functions allowed to be performed by at least a first tool. Next the method comprising retrieving at least a second license type. The second license type specifies a second set of functions allowed to be performed by at least a second tool. Thereafter the method comprising enabling the first set of functions for at least the first tool. In the next step the method comprising enabling the second set of functions for at least the second tool.

[0008] In accordance with a second aspect the disclosure relates a tool controller operative to enable different functionality sets for at least a first and a second tool associated with the tool controller. Whereby the tool

controller being operative to. Retrieve at least a first license type. The first license type specifies a first set of functions allowed to be performed by at least the first tool. Retrieve at least a second license type. The second license type specifies a second set of functions allowed to be performed by at least the second tool. Enable the first set of functions for at least the first tool. And enable the second set of functions for at least the second tool.

BRIEF DESCRIPTION OF DRAWINGS

[0009] The solution will now be described in more detail by means of exemplary embodiments and with reference to the accompanying drawings, in which:

Fig. 1 is a block diagram of a tool controller 100

according to an exemplary embodiment of the present disclosure .

Fig. 2 is a block diagram of a tool controller 100

according to an exemplary embodiment of the present disclosure . Fig. 3 is a block diagram of a tool controller system 400 according to an exemplary embodiment of the present disclosure .

Fig. 4 illustrates a flowchart of a method according to an exemplary embodiment.

DETAILED DESCRIPTION

[00010] Briefly described, a solution is provided to enable different functionality sets for at least a first and a second tool associated with a tool controller.

[00011] Thus, an object of the present disclosure is to provide flexible functionality sets for different tools associated with a tool controller. And thereby provide a solution that capture new functionality requirements for different tools.

[00012] Another object is to provide flexibility in the way in which different tools functions. This is achieved by providing at least a first and a second license type which specifies a first and a second set of functions allowed to be performed by at least the first tool and the second too.

[00013] Fig. 1 illustrates a block diagram of a tool controller 100 according to an exemplary embodiment of the present disclosure. The tool controller 100 controls the functionality of at least one tool 200 associated with the tool controller 100. The tools 200 can either be connected to the tool controller 100 via a wire, or be wirelessly

connected to the tool controller 100. In case the tool 20 is an electric tightening tool 200 the tool controller 100 among others control the tightening that the electric tightening tool 200 should perform. For instance how hard the electric tightening tool should tighten a screw joint. Or to which angle the electric tightening tool should tighten the screw joint. According to one embodiment the tool controller 100 also controls which results that are presented from the tool controller .

[00014] According to one exemplary embodiment the tool controller 100 is operative to enable different functionality sets for at least a first and a second tool associated with the tool controller 100. The tool controller 100 is in this exemplary embodiment operative to retrieve at least a first licence type. The first licence type specifies a first set of functions allowed to be performed by at least the first tool 200. The tool controller 100 is also operative to retrieve at least a second licence type. The second licence type

specifies a second set of functions allowed to be performed by at least the second tool 200. The tool controller 100 is further operative to enable the first set of functions for at least the first tool 200. And enable the second set of functions for at least the second tool 200.

[00015] The tool controller 100 is thus operative to retrieve at least a first and a second license type. Which means that according to exemplary embodiments the tool controller 100 also retrieves more license types. The license types can be of other types as well. Where the other license types specifies other types of functionality sets that the first and second license types. Thus the tool controller 100 can enable many different sets of function sets for many different tools 200.

[00016] According to one exemplary embodiment these license types can be of the first and/or the second license type or any other license type. The license types can for instance be of third, fourth, fifth or sixth type of license. Where the different license types specifies different sets of

functions .

[00017] According to one exemplary embodiments the sets of functions of the different license types can be changed over time. In one exemplary embodiment first set of functions and the second sets of functions can be changed over time. This without changing the tool controller software. In one exemplary embodiment no operator needs to update the licenses types on the tool controller. Instead the license types are automatically updated through a license server.

[00018] If for instance there is a requirement that a certain type of tool and/or functions is used more often together with the tool controller. But this type of tool and/or function is not allowed according to the current license types on the tool controller. One type of license type can then be changed so that the type of tool and/or function are allowed together with the tool controller.

[00019] According to exemplary embodiment set of functions also means the types of tools that are allowed together with the tool controller.

[00020] According to one exemplary embodiment of the tool controller 100 the first and the second tools are electric tightening tools. In this exemplary embodiment the first and/or second set of functions may comprise types of

tightening strategies that the first and second tightening tools are allowed to perform.

[00021] In another exemplary embodiment the first and/or second set of functions comprising types of result data that the tool controller 100 can provide from the first and second tools. In the exemplary embodiment where of the first and the second tools are electric tightening tools the first and/or second set of functions may comprise types of result data that the tool controller 100 can provide from the first and second tightening tools.

[00022] In another exemplary embodiment of the tool

controller 100 the first tool 200 is associated with a first tool controller user interface part and the second tool 200 is associated with a second tool controller interface part.

In this exemplary embodiment the first and the second tool controller interface parts are separate parts of the tool controller interface. In this embodiment the first and the second tool controller interface parts respectively control the functionality of the first and second tools respectively.

[00023] In one exemplary embodiment the first licence type is associated with the first tool controller user interface part and the second licence is associated with the second tool controller user interface part.

[00024] In the embodiment where the tools are electric tightening tools the first control interface part can then for instance control types of tightening that the first electric tightening tools can perform. And the second tool controller interface control which types of tightening that the second electric tightening tool can perform. [00025] In a further exemplary of the tool controller 100 the first and/or second licence types specifies the type of tool 200 that can be used together with the first and/or second function sets.

[00026] According to one exemplary embodiment of the tool controller 100 the first and/or second license types are retrieved via a network connection of the tool controller 100.

[00027] The tool controller interface parts can be accessed via a network connection to the tool controller 100. Thus it is not necessary to physically interacts tool controller 200 in order to operate the tool controller 100.

[00028] According to one exemplary embodiment the tool controller 100 is implemented in the tool 200. In this exemplary embodiment the tool controller 100 is integrated in the tool 200. The tool controller 100 interface parts can be accessed via a network connection to the tool 200 in the embodiment where the tool controller 100 is integrated in the tool 100. Thus it is not necessary to physically interact with tool 200 in order to operate the tool controller 100.

The tool controller 200 can be accessed via a network connection to the tool 100. In the embodiment where the tool controller 100 is part of the tool 100 other tools 200 that do not have an integrated tool controller 100 can use the tool controller 200 integrated in the tool 100 via a network connection .

[00029] According to one exemplary embodiment functions in the functionality sets specified by the different license types can be of many different types. Figure 2 is block diagram of exemplary embodiments of the tool controller 100. The tool controller 100 further comprise a processor 160 arranged to control the tool controller 100. The tool controller 100 also comprises a memory 260

containing instructions executable by the processor 160.

In the embodiment where the tool controller 100 is integrated in the tool 100 the processor 160 and the memory are the saml for the tool controller 200 and the tool 100.

The processor 160 is a Central Processing Unit, CPU,

microcontroller, Digital Signal Processor, DSP, or any other suitable type of processor capable of executing computer program code. The memory 260 is a Random Access Memory, RAM, a Read Only Memory, ROM, or a persistent storage, e.g. a single or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.

According to one aspect, the disclosure further relates to the above mentioned computer program, comprising computer readable code which, when run on the tool controller 100 causes the tool controller 100 to perform any of the aspects of the disclosure described herein.

When the above-mentioned computer program code is run in the processor 160 of the tool controller 100 it causes the tool controller 100 to be operative to retrieve at least a first licence type. The first licence type specifies a first set of functions allowed to be performed by at least the first tool 200. And further retrieve at least a second licence type. The second licence type specifies a second set of functions allowed to be performed by the at least the second tool 200. Next enable the first set of functions for at least the first tool 200. And enable the second set of functions for at least the second tool 200.

According to one aspect of the disclosure the processor 160 comprises one or several of: a retrieving module 161 adapted to retrieve at least a first license type. The first license type specifies a first set of functions allowed to be performed by at least the first tool 200. the retrieving module 161 being further adapted to retrieve at least a second licence type. The second licence type specifies a second set of functions allowed to be performed by the at least the second tool 200. an enabling module 162 adapted to enable the first set of functions for at least the first tool 200. And enable the second set of functions for at least the second tool 200.

The retrieving module 161, enabling module 162 are

implemented in hardware or in software or in a combination thereof. The modules 161, 162 are according to one aspect implemented as a computer program stored in the memory 260 which run on the processor 160. The tool controller 100 is further configured to implement all the aspects of the disclosure as described herein.

Referring to figure 3, another aspect of the present

disclosure relates to a tool controller system 400. The tool controller system 400 comprising according to one exemplary embodiment a License Portal 350 and a Local License Server 300. The Local License Server 300 is connected to the License Portal 350. According to one exemplary embodiment the tool controller 100 retrieves at least the first license type and the second license type from the Local License Server 300. According to one exemplary embodiment the tool controller 100 regularly verifies the at least first and the second license types towards the Local License Server 300. In one exemplary embodiment the at least first and second license types are expired in case the tool controller 100 does not connect to the Local License Server 300 and verifies the first license type and the second license types. Verification of the first and second license types towards the Local License Server 300 can for instance be required once a month, or any other appropriate time interval.

According to another exemplary embodiment no Local License Server 300 is available. Then in one exemplary embodiment a hardware dongle 150 can be connected to the tool controller 100. The hardware dongle 150 comprises at least the first license type and the second license type. According to one exemplary embodiment the hard ware dongle 150 is a USB dongle 150 having a secured area inside the USB dongle 150 together with a hardware based identifier and a flash drive volume.

According to one exemplary embodiment the hard ware dongle 150 has an area inside the secured that will be used to store at least the first license type and the second license type. This are is denoted dongle trusted storage. A controller trusted storage also exists in the tool controller 100 that holds at least the first license type and the second license type for the tool controller 100. The at least first license type and the second license type are then moved between the dongle trusted storage and the controller trusted storage.

According to one exemplary embodiment the tool controller 100 trusted storage is placed in a removable tool controller module 170 which among others stores the configuration of the tool controller 100. In this embodiment it is possible to move the at least first license type and the second license type and the configuration to another tool controller 100 by moving the tool controller module 170 to another tool

controller 100.

According to one exemplary embodiment the hard ware dongle 150 can be used to load new license types from the Local License Server 300. When the hard ware dongle 150 then is inserted in the tool controller 100 at least the first license type and the second license type will be moved to the tool controller 100 trusted storage.

According to one exemplary embodiment the process of

retrieving the at least first license type and the second license type through the hard ware dongle 150 is the

following. The at least first license type and the second license type are setup and reserved in the Local License Server 300. Then downloaded into the hard ware dongle 150.

The hard ware dongle 150 is inserted in the tool controller 100. The tool controller 100 is informed about the hard ware dongle 150. Then the tool controller 100 retrieves the at least first license type and the second license. And further enables the first set of functions for at least the first tool 200 and enables the second set of functions for at least the second tool 200. According to one exemplary embodiment the at least first license type and the second license type can each

respectively be assigned to a tool control interface part (not shown) of the tool controller 100. According to

exemplary embodiments only retrieved licenses types that not already have been enabled for a tool 200 can be enabled for another tool 200. According to one exemplary embodiment each license type is associated with license type features. In exemplary embodiment the features are dependent of the license type, i.e. some features are only allowed in

combination with certain license types

Fig. 4 illustrates a flowchart of a method for enabling different functionality sets for at least a first and a second tool 200. The method comprising the steps of

retrieving S100 at least a first license type, the first license type specifies a first set of functions allowed to be performed by at least a first tool 200. In a next step S110, the method comprising retrieving at least a second license type. The second license type specifies a second set of functions allowed to be performed by at least a second tool 200. Further in the next step S120, the method comprising the step of enabling S120 the first set of functions for at least the first tool 200. In yet another step S130, the method comprising enabling S130 the second set of functions for at least the second tool 200.

In one exemplary embodiment of the method the first and second tools 200 are electric tightening tools. According to another exemplary embodiment of the method, the first and/or the second set of functions comprising types of tightening strategies that the first and second tools 200 are allowed to perform. According to one exemplary embodiment of the present disclosure the first and/or second set of functions

comprising types of result data that the tool controller 100 can provide from the first and second tools 200.

In yet another exemplary embodiment of the present disclosure the first tool 200 is associated with a first tool controller interface parts and the second tool 200 is associated with a second tool controller interface parts.

According to another exemplary embodiment of the present disclosure the first license is associated with the first tool controller user interface part and the second license is associated with the second tool controller interface part.

Aspects of the disclosure are described with reference to the drawings, e.g., block diagrams and/or flowcharts. It is understood that several entities in the drawings, e.g., blocks of the block diagrams, and also combinations of entities in the drawings, can be implemented by computer program instructions, which instructions can be stored in a computer-readable memory.