Robot Control Device Self-Service Configuration File Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for configuring communication between programmable logic controllers and robot control devices are cumbersome, requiring users to manually search for and obtain configuration files, which can lead to increased effort, cost, and maintenance challenges due to the complexity of factory automation communication protocols and the need for frequent updates.

Innovation Solution

A communication system that includes a robot control device and a communication setting device loaded with a configuration file, which defines communication parameters and allows for easy generation and output of the configuration file based on the internal state of the robot control device, eliminating the need for users to manually search for and obtain configuration files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If configuration files are obtained from websites or external sources, then users can access communication setup data, but users must manually search and follow links which increases effort and time

Engineering Contradiction:
Improveaccess to configuration fileVSAvoidtime to find and obtain configuration file
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The robot control device automatically generates and stores configuration files for itself, enabling self-service. Users can directly obtain configuration files from the device without manual searching or external website access, eliminating the time loss associated with manual information retrieval.

Inventive Principle:
Principle #25Self-service

2Reliability

If configuration files are posted on websites for long periods, then users can consistently access them, but website modification flexibility is reduced and management costs increase

Engineering Contradiction:
Improveconsistent access to configuration fileVSAvoidwebsite management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of relying on external websites to host configuration files, the robot control device generates and stores its own configuration files. This eliminates the need for website maintenance and modification constraints while ensuring reliable access to configuration data directly from the device.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The traditional approach has external sources providing configuration files to users. This invention inverts the approach by having the robot control device itself generate and provide configuration files, reversing the information flow direction and eliminating website management dependencies.

Inventive Principle:
Principle #13The other way round (Inversion)

3Adaptability or versatility

If multiple communication protocols are supported, then the system is more versatile, but the number of configuration files and versions increases

Engineering Contradiction:
Improvecommunication protocol compatibilityVSAvoidnumber of configuration files
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The robot control device automatically generates configuration files specific to its own communication settings and protocol configurations. This self-generated approach ensures that only the necessary configuration files for actually supported protocols are created and stored, avoiding accumulation of unnecessary files while maintaining protocol versatility.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10345782B2Robot control device and communication system having communication function for communicating with programmable logic controller
Publication Date: 2019.07.09 FANUC LTD
  • US10345782B2 patent drawing
  • US10345782B2 patent drawing
  • US10345782B2 patent drawing

AI summary

A communication system according to an embodiment of the present invention includes a robot control device, a programmable logic controller for establishing communication with the robot control device, and a communication setting device that is loaded with a configuration file to define communication parameters used in the communication. The communication setting device sets the communication parameters to the programmable logic controller. The robot control device includes a file output unit for outputting the configuration file depending on an internal state of the robot control device.