Robot Software Update Scheduling via Non-Operating Time Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing automatic updating systems for robots in factories require a large number of steps and are prone to defects when updating software, as each robot must be updated individually, and moving robots for updates is inefficient.
Innovation Solution
An automatic updating system that includes an off-line management server, an in-line management server, a production management server, and a data analysis server to centrally manage and schedule software updates for robots, using non-operating times calculated from production plans to minimize disruptions and prevent defects by evaluating and installing update-software on off-line robots before updating in-line robots.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software is updated individually for each robot, then update reliability is improved (defects can be isolated), but the number of updating steps increases significantly
Solution Approach 1:
The patent segments the robot fleet into two groups: in-line robots (operational) and off-line robots (non-operational). Software updates are first tested on off-line robots, then deployed to in-line robots. This segmentation allows parallel processing of updates across multiple robots while maintaining isolation of defects, thus reducing total updating steps without compromising reliability.
Solution Approach 2:
The patent implements preliminary action by installing and evaluating update software on off-line robots before deploying it to in-line robots. This preliminary testing phase allows defect detection and isolation before operational robots are affected, maintaining update reliability while enabling batch updates that reduce the number of steps required.
2Reliability
If robots are moved to update performing places for software updates, then update reliability is improved (controlled environment), but the number of updating steps increases due to movement requirements
Solution Approach 1:
Instead of moving robots to a centralized update facility, the patent inverts the approach by bringing the update capability to the robots' current locations. Off-line robots receive updates at their operational positions, eliminating the need for physical movement while maintaining controlled update conditions through the structured evaluation process.
3Device complexity
If update software is collectively transmitted to all robots, then the number of updating steps is reduced, but the risk of widespread malfunction increases when defects are present
Solution Approach 1:
The patent segments the robot population into in-line and off-line groups, allowing collective update transmission to both groups while implementing staged deployment. Updates are first installed on off-line robots for evaluation, then conditionally deployed to in-line robots. This segmentation enables batch processing that reduces updating steps while maintaining reliability through controlled rollout and defect isolation.
Solution Approach 2:
The patent introduces an intermediary evaluation process where off-line robots serve as test beds before updates reach in-line robots. This intermediary phase acts as a buffer that allows defect detection without widespread impact, enabling collective update transmission while protecting operational robots from potential malfunctions.
4Productivity
If software updates are performed during operating time, then productivity is maintained (robots remain operational), but update reliability decreases and production may be disrupted
Solution Approach 1:
The patent implements periodic action by scheduling software updates during non-operating periods when off-line robots are already unavailable. This periodic update cycle aligns with natural production pauses, allowing updates to be performed without disrupting ongoing production while maintaining robot availability during operating hours. The structured periodic evaluation and deployment process ensures reliability without sacrificing productivity.
Data Source
AI summary
An automatic updating system includes an off-line management server, an in-line management server, a production management server configured to calculate a non-operating time in each time period, and a data analysis server. The off-line management server installs update-software transmitted from a manufacturer server in a corresponding off-line robot based on the transmitted update-software, evaluates the installed update-software, and determines whether or not it is possible to update the in-line robot by the update-software based on the evaluation. The data analysis server schedules the timing of the update of the software so that the update by the update-software, which has been determined to be updatable, is carried out within the non-operating time of the in-line robot. The in-line management server updates the software of the in-line robot at the timing scheduled by the data analysis server.