Machine Tool Postprocessor Architecture for Reuse and Customization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

CAM postprocessor developers face difficulties in reusing existing functionality from postprocessors developed by others, as creating new postprocessors from scratch is challenging and lacks efficient adaptation and modification capabilities.

Innovation Solution

A library-based model with multiple levels (library, controller, machine, OEM, and customer levels) is introduced, allowing protection against reading and modification while enabling overriding of lower levels, along with a dynamic user interface and flag capability for easier adaptation and customization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If postprocessors are created from scratch, then complete functionality is achieved, but development time and complexity increase significantly

Engineering Contradiction:

Improvepostprocessor functionalityVSAvoiddevelopment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The postprocessor is divided into multiple hierarchical levels (library level, controller level, machine level, OEM level, and customer level), each handling specific functionality. This segmentation allows developers to reuse existing code from lower levels while customizing only the necessary higher levels, significantly reducing development time while maintaining complete functionality.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Standard postprocessor functionality is pre-configured at lower hierarchical levels during system setup. This preliminary action enables developers to leverage pre-built, tested code rather than creating everything from scratch, reducing development time while ensuring reliable baseline functionality.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If postprocessors are created from scratch, then complete customization is achieved, but ease of manufacture decreases

Engineering Contradiction:

Improvecustomization capabilityVSAvoidease of creation

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The hierarchical level structure enables customization at specific levels without affecting other parts of the system. Developers can modify the customer level or OEM level for customization while leaving the stable library and controller levels unchanged, making the postprocessor easier to manufacture and maintain while preserving adaptability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system merges standardized functionality from lower levels with customized requirements at higher levels into a single integrated postprocessor. This combination approach maintains ease of manufacture through reuse of proven code while achieving complete customization through level-specific modifications.

Inventive Principle:

Principle #5Merging (Combining)

3Loss of time

If existing postprocessor code is reused, then development time decreases, but adaptability to new requirements worsens

Engineering Contradiction:

Improvedevelopment timeVSAvoidadaptability

Core Design Contradiction:

Loss of timeVSAdaptability or versatility

Solution Approach 1:

By organizing code into hierarchical levels, the system enables selective reuse of existing postprocessor code from lower levels while maintaining the ability to adapt higher levels to new requirements. This structure resolves the contradiction by allowing both time-efficient reuse and flexible adaptation simultaneously.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The hierarchical level structure provides dynamic adaptability, allowing the postprocessor to be configured differently at each level based on specific requirements. Existing code can be reused at stable lower levels while higher levels dynamically adapt to new requirements, maintaining both development efficiency and flexibility.

Inventive Principle:

Principle #15Dynamics

4Stability of the object's composition

If protection against reading and modification is implemented, then code stability is improved, but ease of operation worsens

Engineering Contradiction:

Improvecode stabilityVSAvoidease of customization

Core Design Contradiction:

Stability of the object's compositionVSEase of operation

Solution Approach 1:

The hierarchical level structure with access level properties segments the postprocessor into protected and customizable portions. Lower levels can be protected for stability while higher levels remain accessible for customization, resolving the contradiction between code stability and ease of operation.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Different access level properties are applied to different levels of the hierarchical structure. Critical lower levels have restricted access for stability, while higher customer and OEM levels have more permissive access for ease of customization, achieving both stability and operational ease through localized quality control.

Inventive Principle:

Principle #3Local quality

Data Source

PatentEP3207431B1Machine tool post configurator systems and methods

Publication Date: 2022.08.17 SIEMENS INDUSTRY SOFTWARE INC

Figure 1
Figure 2
Figure 3

AI summary

Methods for post processor development and corresponding systems and computerreadable mediums. A method includes generating (705) a machine tool post processor (200) having a plurality of levels including a library level (202), a controller level (204), and at least one other level (206, 208, 210, 212, 214). The method includes interacting (710) with a user in a dynamic user interface (400) corresponding to the machine tool post processor (200). The method includes storing (715) the machine tool post processor (200).