Tool Server Message Segmentation for Multi-Controller Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing work tools communication systems face inefficiencies in updating multiple tool controllers simultaneously and lack a straightforward method for pre-planning and implementing new operations or torque changes across a production line with multiple tool controllers.

Innovation Solution

A method and system where a tool server communicates with multiple tool controllers using messages with a destination address and requested actions, including a header and payload with data nodes, allowing for centralized control and data updates across multiple controllers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If an operator connects to one controller at a time to update data, then each controller receives accurate updates, but the process becomes very time consuming

Engineering Contradiction:
Improveupdate accuracyVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The message is segmented into a header part containing the requested action and a payload part containing details divided into multiple data nodes. This segmentation allows the system to process and distribute updates efficiently across multiple controllers simultaneously while maintaining data integrity for each controller.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The tool server acts as an intermediary that receives update requests and distributes them to multiple tool controllers simultaneously. The server manages the communication protocol, ensuring each controller receives the appropriate segmented messages with correct destination addresses, thereby updating all controllers in parallel rather than sequentially.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If a centralized communication system is implemented to update multiple controllers, then update efficiency improves, but the system complexity increases

Engineering Contradiction:
Improveupdate speedVSAvoidcommunication system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The message structure is designed with universal components (header and payload parts) that can accommodate multiple types of requested actions and data nodes. This universal structure allows the same communication protocol to handle various update scenarios across different controllers without requiring separate communication mechanisms, thus managing complexity while maintaining productivity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses parameter changes in the message structure, specifically dividing the payload into multiple data nodes with different types. This allows flexible configuration of update content while maintaining a consistent communication framework, enabling efficient multi-controller updates without proportionally increasing system complexity.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If detailed control messages are sent to each controller, then precise control is achieved, but the message complexity and data transmission overhead increase

Engineering Contradiction:
Improvecontrol precisionVSAvoidmessage structure complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The message is divided into a header part containing the requested action and a payload part containing details organized into multiple data nodes. Each data node has a specific type, allowing controllers to efficiently parse and process only the relevant information for their specific control needs, achieving precise control without overwhelming complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The payload part includes multiple data nodes that may contain more information than any single controller needs. Each controller selectively processes the data nodes relevant to its operation, allowing the system to send comprehensive control messages that can be partially utilized by each receiver, maintaining control precision while managing message complexity.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP3164984B1Methods and nodes for facilitating communication between a tool server and a plurality of tool controllers in a work tools communication system
Publication Date: 2018.05.16 ATLAS COPCO IND TECHNIQUE AB INTELLECTUAL PROPERTY DEPARTMENT
  • EP3164984B1 patent drawingFigure 1
  • EP3164984B1 patent drawingFigure 2
  • EP3164984B1 patent drawingFigure 3~4

AI summary

Disclosed is a method performed by a work tools communication system for facilitating communication between a tool server (10) and a plurality of tool controllers (16a, 16, 16) of the work tools communication system. The tool server (10) is connected to the plurality of tool controllers (16a, 16, 16), the tool controllers is further adapted for communication with work tools (18) connected to the tool controllers. The method comprises sending, from the tool server (10) to a first (16a) of the plurality of tool controllers, a message relating to control of one or more work tools (18a) connected to the first tool controller (16a), the message comprising a destination address of the first tool controller and a requested action to be performed by the first tool controller. The method further comprises receiving, by the first tool controller (16a), the message sent by the tool server (10), based on the destination address, analysing, by the first tool controller (16a), the message to detect the requested action, and controlling, by the first tool controller (16a), the one or more work tools (18a) connected to the first tool controller according to the detected requested action.