WO2016001210A1 - Methods and systems for facilitating communication in a work tools network environment - Google Patents
Methods and systems for facilitating communication in a work tools network environment Download PDFInfo
- Publication number
- WO2016001210A1 WO2016001210A1 PCT/EP2015/064815 EP2015064815W WO2016001210A1 WO 2016001210 A1 WO2016001210 A1 WO 2016001210A1 EP 2015064815 W EP2015064815 W EP 2015064815W WO 2016001210 A1 WO2016001210 A1 WO 2016001210A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- communication node
- server
- communication
- controller
- tool
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1073—Registration or de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/147—Signalling methods or messages providing extensions to protocols defined by standardisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/535—Tracking the activity of the user
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/30—Nc systems
- G05B2219/45—Nc applications
- G05B2219/45127—Portable, hand drill
Definitions
- the present solution relates to a system and method for controlling work tools in a work tool system.
- Work tools and systems with work tools including portable work tools such as power wrenches operated by an operator, are often used in production work.
- a common application is in assembly lines.
- Work tools in assembly lines may have a controller connected to them and the controller is adapted to control the work performed by the tool so that the tool works automatically. The controller sees to that the tool is operated correctly, e.g. performing a wrench operation with the correct torque etc.
- a system for a work tools communications network comprises a server comprising a memory and which is operatively coupled to a communication node, wherein the communication node comprises a processor and a memory device and is operatively coupled to a controller.
- the controller comprises a processor and a memory, and is adapted to control parameters of a work tool.
- the server is adapted to connect to and register with the communication node, the controller is adapted to connect to and register with the communication node, and the communication node is adapted to establish a communication session between the server and the controller.
- a method for communication in a work tool communications network comprising a server, a communication node, a plurality of tool controllers and a plurality of work tools connected to the tool controllers, wherein the server and the tool controllers are connected to the
- the method comprises registering the server with the communication node, registering the tool controller with the communication node, and establishing a communication session between the server and the tool controller.
- the communication node is configured to connect to the server, connect to the tool controller, register the server and the tool controller with the communication node, and establish a communication session between the server and the tool controller.
- a computer program product comprising a non-transitory computer readable medium storing computer instructions for managing communication in a communication node of a work communications network, the network comprising a server, a communication node comprising a memory device, and a processing device operatively coupled to the memory device, wherein the processing device is configured to execute computer-readable computer instructions.
- the network further comprises a plurality of tool controllers and a plurality of work tools connected to the tool controllers, wherein the server and the tool controllers are connected to the communication node.
- the computer instructions comprises instructions for connecting and registering the server to the
- a method for communication in a work tool communications network comprising a server , a communication node, a plurality of tool controllers and a plurality of work tools connected to the tool controllers, wherein the server and the tool controllers are connected to the communication node.
- the method comprises receiving, by the communication node, a request from the server to register with the communication node, registering the server with the communication node, receiving, by the communication node, a request from the tool controller to register with the communication node, registering the tool controller with the communication node and establishing, by the
- the communication node may facilitate
- the solution may also improve communication in a network with multiple servers and controllers, by directing all communication via the communication node instead of having different communication for each server and controller. Further, it may facilitate updating a tool network with new equipment, such as servers and controllers, since the communication node may enable communications between entities that otherwise may not have been compatible. This is also advantageous when updating and/or changing versions of servers and controllers, since the communication node enables entities with different versions to communicate with each other.
- FIG. 1 is a block diagram of a work tools communication system according to an embodiment.
- FIG. 2 is a flow chart of a method performed in a work tools communication system for facilitating communication between a tool server and a plurality of tool controllers via a communication node according to a first embodiment.
- FIG. 3 is a flow chart of a method performed in a work tools communication system for facilitating communication between a tool server and a plurality of tool controllers via a communication node according to a second embodiment.
- FIG. 4 is a flow chart of a method performed in a work tools communication system for facilitating communication between a tool server and a plurality of tool controllers via a communication node according to a third embodiment.
- FIG. 5 is a flow chart of a method performed by a communication node according to a fourth embodiment.
- Fig. 6 is a block diagram illustrating a server and a controller in more detail according to some embodiments.
- a system is provided to enable remote configuration, control and data collection of controllers for work tools.
- the work tools are configurable for different operations.
- a specific work tool may further be a part of a work station with material for production, arrangements for material handling, the work tool, different equipment for the tool, interaction devices for work tool operation such as indicator lamps, displays and so forth.
- Fig. 1 shows a tool communication system comprising a plurality of tool controllers 16 for control, supervision and/or collection of result data from one or more work tools 18, individual of the work tools in turn being connected to one of the tool controllers.
- Result data may be data that pertains to operations of work tools 18.
- the tool communication system further comprises a tools server 10 for configuration management, control of the tool controllers 16, storage of result data received from the tool controllers and/or storage of control data sent to the tool controllers.
- the tool communication system further comprises a communication node 14 for management and relay of communication, for example between a server 10 and a controller 16.
- the communication node 14 may comprise a storage 13 associated with it for storing information such as communication logs. Also, there may be clients 12 such as laptops connected to the tools server 10. There may be more than one tools server in a tool communication system, illustrated by the two tools servers in fig. 1 .
- a work tool 18 may be any kind of power driven tool that is used for performing mechanical operations, such as a wrench, a drill, a hammer.
- the work tool 18 may be a part of a work station with e.g. material for production,
- the work tool 18 may be set up for simple operations, or just manually controlled by an operator person. However, the work tool may also be set up for complex work operations by a configuration. Such complex work operations may include a number of similar and different operations, series of operations with one equipment, shifting to another equipment followed by another series of operations and may be shifting to a third equipment. How the work tool should perform operations and interact with an operator, may be based on control data received from the tools server. Each individual operation may need to be performed with high accuracy in terms of e.g. torque and rotation speed. Further, in order to maintain desirable quality control, results performed by the work tools may be measured by e.g. sensors, such results may be the number of rotations
- the tool communication system may be applied e.g. in a small
- the tool communication system may be distributed over several buildings or over remote locations.
- the manufacturing environment may also be a factory with a challenging environment of dirt, aggressive chemicals, electrical disturbances, sometimes challenging for communication equipment and computers. Sometimes the communication may be interrupted. Even if it is a challenging environment, configuration data and result data need to be conveyed between a tool server and a controller. Production stops or production disturbances need to be avoided, because they sometimes result in significant costs.
- Communication in the tool communication system may be performed based on Local Area Network, LAN, technologies such as Ethernet, e.g. according to IEEE 802.3 , Transfer Control Protocol/User Datagram Protocol/Internet Protocol,
- the tool communication system may be operational in a factory or a manufacturing plant, for examples for
- the tool communication system may be covering or connecting a number of facilities within a closed area such as a campus with a number of buildings.
- the tool communication system may be covering or connecting a number of factories or manufacturing plants remotely located from each other.
- a tool server such as the tool server 10, may be a server which clients 12 may connect to for creation and/or administration of work operations for work tools 18.
- the tool server 10 may be a general purpose server or a tool server specifically arranged for remote control of work tools. Administrators connecting to the tool server via clients 12, may for example create, specify and change how a particular work tool 18 or a group of work tools 18 should behave in a certain situation. Examples are series of operations, tool selections, values for each operation like a torque rate, number of rotations, rotational speed, position, how and when result data should be feed backed, etc.
- the server 10 may comprise a CPU 20 and a memory 22, as shown in Fig. 6a.
- a communication node such as the communication node 14, may be arranged for managing communication between different participating functional nodes or devices in the communications network.
- the communication node 14 may for example keep track of identities of tool controllers 16, tool servers 10, and/or work tools 18.
- the communication node 14 may keep track of any nodes or devices alternating between on-line and off-line.
- a tool controller 16 may for example not always be connected to a network for various reasons.
- the communication node 14 may further validate and/or authorize node or device communication in the
- the communication node 14 may comprise a CPU 24 and a memory 26, as shown in Fig. 6b.
- a tool controller 16 such as a first tool controller 16a, may be a tool controller for control of work tools.
- the tool controller may be a specific node for control of work tools or it may be for example a general purpose computer, which has been adapted for control of work tools.
- the tool controller may be connected to the tool communication system for communication by wire or wirelessly.
- the tool controller may receive control data and store the control data in a suitable database from e.g. the tool server 10.
- the tool controller may use the control data for control of a work tool or operation of a work tool. Sensors of the tool controller or the work tool may generate result data of work tool operations.
- the tool controller 16 may also be termed controller, controller node, controlling node, control unit, tool processor, tool regulator, or similar terms.
- the tool controller 16 may be co-located with or comprised in a work tool 18, a tool server 10, a communication node 14, or other suitable technical nodes operating in a tool communication system.
- a work tool 18, such as a first work tool 18a may be controlled by the first tool controller 16a.
- Controlling a work tool 18a may for example include providing control data to the work tool, operating the work tool by provision of electrical power, pneumatic or hydraulic power, sensor instructions, not limiting to other types of control or regulation.
- Controlling the work tool may for example also include detection of electrical energy consumption, sensing of pneumatic or hydraulic power, torque, torque rate, position, three dimensional position, or other types of sensor data.
- Examples of a work tool 18 may be a torque wrench, a hammer, a breaker, a rock drill, a nut runner, a screwdriver, or various combinations of those, not limiting to other similar types of work tools.
- a work tool 130 may be connected by wire or wirelessly to its tool controller.
- a client 12 may be a computer, e.g. a laptop or a stationary computer that is connected wirelessly or via wire line to the tools server.
- the client may be run by an administrator and used by the administrator to for example control the function of the work tools and/or the tool controllers, by for example supervising sensor data delivered by the tool controllers to the tool server and inputting tool control data that is delivered by the tool server to the concerned tool controller for subsequent delivery to the concerned work tools of that tool controller.
- control data that is delivered to a tool controller and stored at the tool controller may also be stored at a database 1 1 of the tool server 10.
- other data related to the control and/or operation of the work tools may be stored at the database of the tool server, such as sensor data.
- Clients 12 may connect to a desired server 10, which may then enable the client 12 to communicate with other applications, such as a controller 18.
- a desired server 10 may then enable the client 12 to communicate with other applications, such as a controller 18.
- communication node 14 is an entity that is responsible for routing, managing and storing communication, and is adapted to and responsible for authenticating and registering any clients that use an appropriate protocol.
- the communication node is further arranged to act as a message relay and client registry in a distributed tool system.
- a system may have one or multiple communication nodes 14.
- An entity is a device connected to the communication node and may for example be a server 10 or a controller 16.
- Entities connected to the communication node 14 may request a list of registered entities and may also subscribe to certain events in order to receive information when they happen, for instance when a new entity connects or when an old entity disconnects.
- the communication node 14 keeps track of sessions between the connected entities and de-allocates sessions when an entity stops responding.
- the communication node 14 also routes messages between entities and makes it possible to subscribe to and monitor messages sent in the system. In one
- messages are structured with a header part comprising the destination and message type, and a payload part comprising control data for controlling a work tool by 18 by a controller 16.
- the control data may contain both metadata and value data, the metadata pertaining to what is to be performed and the value data containing a value for what is to be performed, e.g. the amount of torque to be used during an operation.
- Register Used to register a new client. After a client 12 has connected to the communication node 14, it must be registered before it is allowed to do anything. A part of this registration process includes authenticating the connecting client to ensure that it is authorized to connect.
- Connect to client Used to connect the communication node 14 to a client 12. This function is used when connecting to a client 12 that is not configured to automatically register with the communication node 14, for instance a controller 16. Typically, information about an Internet Protocol and a port is included in the connect message.
- Disconnect client Disconnects a client from the communication node by using the corresponding unique ID for the client to be disconnected.
- Subscribe to client status Used to subscribe to changes in connection for a client.
- a filter may be used to subscribes to certain types of clients such as controllers 16.
- Unsubscribe to client status Cancels a previous subscription to a client or client type.
- Subscribe to messages Subscribes to messages sent in the system.
- a filter may be used to subscribe to certain types of messages or to messages to/from specific clients.
- Unsubscribe to messages Cancels a previous subscription to messages or message types.
- List clients Used to list all connected clients, a filter may be used to list only certain types of clients.
- the communication node 14 supports messages to read and update information in the communication node 14.
- the communication node 14 may also keep track of all communication. This may be done through logs of all messages sent and all clients that connect and/or disconnect. It also keeps track of sessions allocated by a client in another client. Messages relating to allocating a session may have a certain message class, such as SessionAllocation. For deallocating a session, a Sessiondeallocation message may be used.
- SessionAllocation For deallocating a session, a Sessiondeallocation message may be used.
- the communication node 14 may comprise a communication node manager.
- a communication node manager may for example be a software program installed on the communication node or it may be an external unit plugged in to the communication node.
- the communication node manager may be used to:
- Disconnect client • View and change configuration of a communication node
- a server such as the server 10, may be a server to which clients 12 may connect to for creation and/or administration of work operations for work tools 18.
- the tool server may be a general purpose server or a tool server 10 specific arranged for remote control of work tools. Administrators connecting to the tool server via clients 12, may for example create, specify and change how a particular work tool or a group of work tools 18 should behave in certain situation. Examples are series of operations, tool selections, values for each operation like a torque rate, number of rotations, rotational speed, position, how end when result data should be feed backed, etc.
- Servers 10 in the tool system are primarily used as connection points for clients and are intended to provide a user friendly interface for communicating with and configuring controllers 16. This interface may be accessible from the server itself or it may be accessible through a client 12 connected to the server 10. Servers 10 are generally the entity through which communication with a controller is initiated, either by the server 10 or by a client 12 connected to the server.
- the server 10 has software installed thereon for enabling the above mentioned features. This software may for example be applications intended for communication within a tool
- the server has no previous knowledge of the connecting controller and therefore retrieves all necessary information from the controller. This may be done via a communication node or straight from server to controller.
- the server 10 then optionally updates relevant clients accordingly.
- the server 10 has knowledge of the connecting controller 16 before it connects, for instance when a controller connects after being offline for a while.
- the first step for the server 10 is then to check for configuration changes in the controller 16. If no change has been made, the server still updates database information to reflect that even though the information is the same, it was received at a later point in time. Also, the server optionally updates relevant clients with the new information.
- the server receives an information notification from a controller that it has been updated.
- the server 10 retrieves the updated configuration, and optionally notifies relevant clients.
- Entity is added/removed: This occurs when an entity such as a controller connects or disconnects from the server. The server is then notified by the entity and updates its database information accordingly, and optionally notifies relevant clients.
- Update configuration in controller In this scenario a user requests configuration changes for a controller. The server then retrieves any necessary data from its database, and then updates the controller configuration. After this has been done, the server updates its database with the new configuration and optionally notifies relevant clients.
- Restore previous configuration This function may be requested by a client connected to a server.
- the server retrieves the older configuration from its database, then sends it to the client which then changes its configuration.
- the configuration is then saved and information regarding this is sent to the server, which updates its database.
- One of the tasks of a server 10 in the tool system described herein is to store data from communication.
- This data may for example be related to the work performed by a work tool 18, such as the amount of torque applied or the number of revolutions required to tighten a bolt. It may also store other information, for example settings and configurations for a controller 16. This enables for example historical comparisons as well as facilitates configuration of new controllers by using stored data related to similar controllers.
- Controllers 16 in the system have the main purpose of controlling work tools 18. Controllers may communicate with servers 10, either via a communication node 14 or directly. The direct communication may be both wireless and require physical connection. It is possible for a user to use a controller 16 to configure a tool 18, for example through a client 12, such as a personal computer, connected to a server 10. It is possible for a controller 16 to be integrated into a tool 18, and it is also possible for a controller 16 to be external from the tool 18.
- Examples of parameters that may be controlled via a controller include torque, angle and speed.
- a wrench work tool 18 could be controlled by a controller 16 to determine the angle of operation and the amount of torque applied. It could further be controlled to work according to a pre-determined pattern, for instance rotating three full revolutions and then stopping or tightening to a certain degree. It may also be controlled to make a revolution upon directions from a user, such as when a specific button on a computer acting as a client 14 connected through a server 10 to a controller 16 is pressed.
- these are merely examples of what may be configured and how, there are a vast number of other parameters relating to the tools 18 that may be configured through use of controllers 16.
- Fig. 2 shows communication involving a server 10, a communication node 14 and a controller 16 that are operatively coupled together.
- the communication is illustrated as being synchronous, but it may also be asynchronous, meaning that a process does not stop to wait for a specific response but instead continues normal processing when a message has been sent and a callback is called when a response is received.
- the server 10 first connects 100 to the communication node 14. Before being able to communicate with other entities connected to the communication node, the server 10 registers 1 10 with the communication node 14, and the communication node 14 may acknowledge that the server 10 is connected. The controller also connects 120 with the communication node 14, and after it has been connected it may also register 130 with the
- the communication node 14 in order to communicate with other entities also connected to the communication node.
- the controller 16 it is also possible for the controller 16 to register before the communication node 14, or for the controller 16 and the communication node 14 to register simultaneously.
- the step of registering 1 10 and connecting 120 can be done simultaneously in a single step.
- the communication node 14 may assign an identifier to each entity that is connected to and/or registered with it.
- the identifiers may for instance be numbers or names and they may be in various different formats, such as numeric, binary and alphanumeric.
- the identifiers are used for keeping track of the registered units, and in an exemplary embodiment the communication node 14 is the only entity within the communications network 1 1 that has knowledge of the virtual and/or physical location of other entities.
- the assigned identifiers are the only type of information that entities other than the communication node, such as the server 10 and the controller 16, need to know in order to effectively direct messages to the appropriate destinations.
- the communication node 14 may in some embodiments be further adapted to also assign a unit type to each entity that has registered with it. In some embodiments,
- the unit type only specifies whether the connected entity is a server or a controller, in other embodiments the unit types will be more specified. For example, there may be different types among controllers such as wrench controllers, drill controllers etc. It is also possible for the unit types to be even more specific and/or to be named differently, such as "PF6000" denoting one group of controllers.
- the server 10 After connecting to and registering with the server, it is possible for the server 10 to communicate with the controller 16 via the communication node 14.
- One exemplary scenario is shown in Fig.2 where the server 10 requests 140 to establish a communication session controller 16. This means, in exemplary implementation, communicating to the communication node 14 that the server 10 wishes to
- the communication node 14 may in some embodiments include the identifier of the source and/or the destination in the communication. For instance when the server 10 requests 140 to establish a communication session by logging in to the controller 16, the communication node will specify which server 10 initiated the communication, and also to which controller 16 the communication is being sent.
- the server 10 After a communication session has been established between the server 10 and the controller 16, it is possible to use the server 10 to control 150 parameters of a work tool 18. These parameters are in an exemplary embodiment related to the operation of the work tool 18 and may for instance be angle, torque and speed.
- the communication relating to control of parameters is routed by the communication node 14, since the server 10 and the controller 16, in an exemplary embodiment, does not have information about the others' location or virtual address.
- the communication node 14 is further adapted to store all communication sessions in a message log.
- the message log is typically a database for storing and keeping track of all communication sessions and all registered entities related to the communication node 14. In some embodiments, the message log only registers which entities that have been communicating with one another and not the content of the communication. In other embodiments, the message log is further adapted to store information relating to the sender of a communication, the destination for a communication, as well as the content of the communication.
- the communication node 14 may also provide a session identifier with communication in order for the server 10 and controller 16 to know what subsequent communication is related to.
- This session identifier may in some embodiments be a uniquely generated identifier, for instance a number or a name, and in some embodiments it may be a randomly generated and assigned number with a very low probability of generating two identical identifiers.
- the communication node 14 also provides a sequence identifier for keeping track of asynchronous communication.
- Fig. 3 shows how the communication node 14 may be further adapted to list all connected entities upon request. It an exemplary embodiment it is possible to request a list of connected entities, connected controllers, connected servers, and connected entities of a certain type, but in alternate embodiments there may be more variations available.
- the figure shows a server first connecting 200 and registering 210 with the communication node 14, whereafter the communication node 14 acknowledges 220 the registration.
- the step of acknowledging 220 the registration is optional and in some embodiments the communication node does not acknowledge registration, and in other embodiments the step of acknowledging 220 registration may be included in the registration step 210.
- the server 10 may request that the communication node lists all connected entities, all connected controllers, all connected controllers of a certain type, all servers or any similar combination.
- Fig. 3 shows how the server 10 requests that the communication node 14 lists all connected controllers in step 230.
- the communication node 14 then responds with a list of connected controllers, which may be 0 as indicated in step 240. If a controller 16 connects 250 and registers 260 with the communication node 14 after the list of controllers has been requested, the list is, in an exemplary embodiment, not automatically updated and communicated to the server 10.
- the communication node 14 will respond 290 with a new list of connected controllers, in the example show in Fig. 3 this would be one controller.
- Fig. 4 shows the server connecting to and registering 300 with the communication node 14, in one step. It may be possible to connect and register in separate steps, but it may also be done in a single step.
- the server 10 may choose to subscribe 310 to the status of a certain controller 16 or a certain controller type. Subscribing means to request to be notified of any update relating to the controller.
- the status of a controller is in exemplary embodiment related to whether it's connected or not, but it may in other embodiments be more detailed and contain information regarding, for example, how long ago the controller was connected, the entity with which the controller most recently communicated and so on.
- Fig. 4 shows the server requesting to subscribe 310 to the status of all controllers of the type "PF6000".
- the communication node 14 then responds by listing 320 currently connected controllers of the type specified by the server in the subscription request.
- the response from the communication node 14 would indicate that no controllers of the requested type are connected at that time.
- a controller 16 of a certain type connects and registers 330 with the communication node 14 after a server 10 has subscribed to the status of all controllers of that type, the server 10 will still be notified.
- Fig. 4 shows how a controller 16 connects and registers 300 with the communication node 14.
- the communication node 14 then notifies 340 to each server 10 that has subscribed to the status of the controller type that matches the recently connected controller 16, that a controller of the specified type has connected to the communication node 14.
- This scenario is repeated each time a new entity for which a previously registered entity has subscribed to status changes, connected with the communication node 14.
- the need for making repeated requests for the same information is reduced, and the system may also have better and more recently updated information.
- the communication node 14 not only keeps track of all the communication between controllers 16 and servers 10, it also keeps track of connected controllers and provides a service for subscription of controller state, such as described above.
- the server 10 may subscribe for changes in a controller status and keep the controller status in memory, so that it does not continuously have to request the communication node 14 to update the status. This makes it possible for any client 12 connected to a server 10 to ask for the state of a controller 16 without necessarily having to go through the communication node 14.
- Fig. 4 further shows how a sever 10 may communicate with a controller 16 via a communication node 14, and how a reply function may be used.
- a server 10 previously registered with the communication node 14 may subscribe 310 to the status of controllers 16 through a communication sent to the communication node 14. The communication node 14 then responds listing 320 connected controllers 16.
- the server 10 will be notified 340 that a new controller has been connected, as long as the server has not unsubscribed to controller status before the controller 16 connects and registers 320. By unsubscribing, a previous subscription may be canceled.
- a reply function is a part of how the communication between the server 10 and the controller 16 is performed.
- the server 10 may request 350 to establish a
- the controller 16 may then respond to the request 350 by using a reply function.
- the reply function allows an entity connected to the communication node 14 to reply to a communication without unnecessarily specifying to where the communication should be sent.
- the reply function automatically sends the communication to the entity from which communication was sent.
- Fig. 4 shows how the controller 16 replies 360 by providing a session ID to the server 10. The session ID is then included in all continued communication between the server 10 and the controller 16 until the communication session is ended.
- Fig. 4 shows the communications 350 and 360 as being between server 10 and controller 16 which is the case, although all
- Fig. 5 shows a method performed in a communication node 14 according to one embodiment.
- the communication node 14 receives S100 a request from a previously connected server 10 to register with the communication node 14, and subsequently registers S1 10 the server with the communication node 14.
- the communication node 14 then receives a request from a tool controller 18 to register with the communication node 14, and registers S130 the tool controller 18 with the communication node 14.
- the communication node 14 may establish S140 a communication session between the server 10 and the tool controller 18.
- Fig. 6 shows a more detailed block diagram of a server 10, as shown in Fig. 6a, and a more detailed block diagram of a controller 16, as shown in Fig. 6b.
- the server 10 may comprise a Computer Processing Unit 20 and a memory 22, used for example to store communication between entities.
- the controller 16 may similarly comprise a Computer Processing Unit 24 and a memory 26, the memory may be used to store for instance control data relating to operations performed by a work tool 18.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Medical Informatics (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP15736805.1A EP3164983B1 (en) | 2014-07-03 | 2015-06-30 | Methods and systems for facilitating communication in a work tools network environment |
JP2017519976A JP2017520872A (en) | 2014-07-03 | 2015-06-30 | Method and system for facilitating communication in a work tool network environment |
CN201580036435.4A CN106537877A (en) | 2014-07-03 | 2015-06-30 | Methods and systems for facilitating communication in work tools network environment |
US15/323,625 US20170149904A1 (en) | 2014-07-03 | 2015-06-30 | Methods and systems for facilitating communication in a work tools network environment |
KR1020177000205A KR20170051408A (en) | 2014-07-03 | 2015-06-30 | Methods and systems for facilitating communication in a work tools network environmen |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
SE1450838-6 | 2014-07-03 | ||
SE1450838 | 2014-07-03 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016001210A1 true WO2016001210A1 (en) | 2016-01-07 |
Family
ID=53546207
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2015/064815 WO2016001210A1 (en) | 2014-07-03 | 2015-06-30 | Methods and systems for facilitating communication in a work tools network environment |
Country Status (6)
Country | Link |
---|---|
US (1) | US20170149904A1 (en) |
EP (1) | EP3164983B1 (en) |
JP (1) | JP2017520872A (en) |
KR (1) | KR20170051408A (en) |
CN (1) | CN106537877A (en) |
WO (1) | WO2016001210A1 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3734382A1 (en) * | 2019-05-03 | 2020-11-04 | AB Sandvik Coromant | Method for establishing communication in a machine tool system and a communication apparatus therefor |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030182396A1 (en) * | 2002-03-22 | 2003-09-25 | Daniel Reich | Internet based distributed control system |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7127358B2 (en) * | 2004-03-30 | 2006-10-24 | Tokyo Electron Limited | Method and system for run-to-run control |
US7600024B2 (en) * | 2006-03-31 | 2009-10-06 | Microsoft Corporation | Restricting device access per session |
JP5065851B2 (en) * | 2007-10-19 | 2012-11-07 | 株式会社日立製作所 | Work management system |
JP2009259229A (en) * | 2008-03-17 | 2009-11-05 | Nec Personal Products Co Ltd | Remote controller, remote control program, remote control method, and remote control system |
CN201812182U (en) * | 2010-10-12 | 2011-04-27 | 东莞宝元数控科技有限公司 | Parameter control system of tool machine |
DE102011053799A1 (en) * | 2011-09-20 | 2013-03-21 | Dritte Patentportfolio Beteiligungsgesellschaft Mbh & Co.Kg | Method for controlling at least one control variable of a tool and the tool |
US20130070056A1 (en) * | 2011-09-20 | 2013-03-21 | Nexus Environmental, LLC | Method and apparatus to monitor and control workflow |
JP2014021538A (en) * | 2012-07-12 | 2014-02-03 | Hitachi Koki Co Ltd | Working situation management system for power tool |
-
2015
- 2015-06-30 KR KR1020177000205A patent/KR20170051408A/en not_active Application Discontinuation
- 2015-06-30 JP JP2017519976A patent/JP2017520872A/en active Pending
- 2015-06-30 WO PCT/EP2015/064815 patent/WO2016001210A1/en active Application Filing
- 2015-06-30 CN CN201580036435.4A patent/CN106537877A/en not_active Withdrawn
- 2015-06-30 EP EP15736805.1A patent/EP3164983B1/en active Active
- 2015-06-30 US US15/323,625 patent/US20170149904A1/en not_active Abandoned
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030182396A1 (en) * | 2002-03-22 | 2003-09-25 | Daniel Reich | Internet based distributed control system |
Also Published As
Publication number | Publication date |
---|---|
CN106537877A (en) | 2017-03-22 |
EP3164983B1 (en) | 2018-05-16 |
KR20170051408A (en) | 2017-05-11 |
JP2017520872A (en) | 2017-07-27 |
EP3164983A1 (en) | 2017-05-10 |
US20170149904A1 (en) | 2017-05-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20170153631A1 (en) | Method, nodes and computer program of a tool communications network | |
JP6870568B2 (en) | Communication system, control device, setting device, setting method and program | |
CN110320793B (en) | Method for constructing redundant communication connections and fail-safe control unit | |
EP2530542B1 (en) | Systems and methods for alert device removal | |
EP3100404A1 (en) | Apparatus and method for securing a distributed control system (dcs) | |
JP2017041747A (en) | Information processing device, information processing device control program, control method, and information processing system | |
JP2018528703A (en) | Method for setting modular control device of industrial automation system and modular control device | |
EP3164983B1 (en) | Methods and systems for facilitating communication in a work tools network environment | |
US20170153620A1 (en) | Methods and nodes for facilitating communication between a tool server and a plurality of tool controllers in a work tools communication system | |
JP5754199B2 (en) | Management system, management device, and control program | |
EP3554761A1 (en) | Method, monitoring node and computer program of monitoring energy flow in a tightening tool | |
JP2004306200A (en) | Robot control system | |
JP2015141644A (en) | Data collection apparatus | |
JP6483592B2 (en) | Controller and control system | |
JP6878697B2 (en) | Data processing equipment, data processing methods and programs | |
Tang et al. | Development of upper computer software based on OPC UA technology | |
JP2017076888A (en) | Relay device and relay communication system | |
JP6570901B2 (en) | Device information management system, control method and program for device information management system | |
JP7039843B2 (en) | Communication path control device, communication system, communication path control method, and program | |
JP2011120056A (en) | Communication system | |
JP6202903B2 (en) | Building monitoring system and monitoring control device | |
KR102350208B1 (en) | Redundant heating, ventilation, and air conditioning control systems | |
JP2000003344A (en) | Computer monitoring device, computer monitoring system using the same, and monitoring method | |
JP2001228915A (en) | Equipment control system | |
WO2013136526A1 (en) | Distributed application-integrating network system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15736805 Country of ref document: EP Kind code of ref document: A1 |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
REEP | Request for entry into the european phase |
Ref document number: 2015736805 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2015736805 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2017519976 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15323625 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 20177000205 Country of ref document: KR Kind code of ref document: A |