Visual Debugging of Robotic Process Logic via Flowchart Paths

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing debugging techniques for robotic processes are unsuitable for high-level debugging, as they require users to set breakpoints and manipulate software directly, making it difficult to visualize and understand the logical flow and implementation details of robotic processes.

Innovation Solution

A graphical user interface is provided to visually debug robotic processes by rendering a flowchart that represents the logical flow, using robot operation data to distinguish different logical paths and allowing users to manipulate and test these paths for debugging purposes, enabling efficient identification of implementation characteristics and error analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional debugging techniques (breakpoints, variable manipulation) are used on robotic process software, then detailed software-level debugging is possible, but it becomes difficult to visualize and understand the logical flow at a high level

Engineering Contradiction:
Improvedebugging detailVSAvoidvisual understanding
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The patent transforms the debugging interface from a traditional code-level view to a visual flowchart representation, adding a graphical dimension to the debugging process. This allows users to see the logical flow of robotic processes in a visual format while maintaining access to detailed software debugging capabilities when needed.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The patent introduces a visual flowchart as an intermediary layer between the user and the underlying software code. This flowchart serves as a mediator that simplifies the complex software logic into understandable visual blocks, making it easier to grasp the overall logical flow while still allowing drill-down to detailed software debugging when necessary.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If users manually analyze robot operation log files to understand process implementation, then detailed operation data is accessible, but it requires significant time and effort to identify patterns and errors

Engineering Contradiction:
Improveoperation data accessibilityVSAvoidanalysis time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system automatically analyzes robot operation log files and generates visual flowcharts with embedded statistics and error information without requiring manual intervention. The system serves itself by automatically processing the data, identifying patterns, and presenting them in an easily consumable visual format, eliminating the need for users to manually analyze logs.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the manual mechanical process of analyzing log files with an automated computational system that processes operation data and generates visual representations. This substitution transforms the time-consuming manual analysis into an automated process that quickly produces insightful visualizations.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Measurement precision

If comprehensive robot operation data is collected and analyzed, then accurate identification of logical path characteristics is achieved, but the complexity of processing and visualizing this data increases

Engineering Contradiction:
Improvepath analysis accuracyVSAvoiddata processing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent extracts only the most relevant information from comprehensive robot operation data and presents it in the visual flowchart. Instead of displaying all raw data, the system selectively extracts key metrics such as error frequencies, path traversal counts, and critical operation statistics, simplifying the visualization while maintaining analytical accuracy.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies different visual properties to different parts of the flowchart based on the local characteristics of each logical path. Error-prone paths are highlighted with specific visual indicators, frequently traversed paths are marked differently, and critical decision points are emphasized. This local differentiation allows comprehensive data to be presented in a simplified, easily interpretable format.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9910761B1Visually debugging robotic processes
Publication Date: 2018.03.06 X DEVELOPMENT LLC
  • US9910761B1 patent drawing
  • US9910761B1 patent drawing
  • US9910761B1 patent drawing

AI summary

Methods, apparatus, systems, and computer-readable media are provided for visually debugging robotic processes. In various implementations, a graphical user interface may be rendered that includes a flowchart representing a robotic process. A plurality of different logical paths through the robotic process may be represented by a plurality of different visible paths through the flowchart. In various implementations, robot operation data indicative of one or more implementations of the robotic process may be determined. Based on the robot operation data, a first logical path through the robotic process that satisfies a criterion may be identified. In various implementations, a first visual path through the flowchart may be selected that corresponds to the identified first logical path. In various implementations, the first visible path through the flowchart may be visually distinguished from a second visible path through the flowchart.