Vehicle Graphic Code Conversion for Git-Based Debugging Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle development processes face challenges in managing and comparing differences between graphic codes due to the difficulty of using version management software like Git, which primarily handles text-based codes, leading to inconsistencies and repeated conversions between graphic and text codes, resulting in potential discrepancies.
Innovation Solution
A method is introduced to convert graphic codes into text codes by inserting configuration information as annotations, using serialization encoding, and upon conversion back, extracting this information to ensure one-to-one correspondence, utilizing base64 encoding and global unique IDs for precise restoration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If graphic codes are converted to text codes using existing version management software, then text-based code management is improved, but graphic code information is lost and one-to-one correspondence cannot be maintained
Solution Approach 1:
The patent embeds graphic code configuration information within text code files using annotation formats. The graphic code data is nested inside the text code structure, allowing both formats to coexist and maintain correspondence without losing information during conversion.
Solution Approach 2:
The patent introduces an intermediary conversion system that maintains bidirectional mapping between graphic codes and text codes. This intermediary mechanism ensures that graphic code information is preserved through annotations while enabling text-based version management.
2Productivity
If graphic codes are repeatedly converted to text codes and back, then text code execution capability is improved, but code discrepancies and inconsistencies increase
Solution Approach 1:
The patent performs preliminary encoding of graphic code configuration information into annotations during the initial conversion. This preliminary action preserves the original graphic code data structure, enabling accurate restoration and preventing discrepancies during subsequent conversion cycles.
Solution Approach 2:
The patent implements a feedback mechanism where the conversion system continuously verifies and maintains one-to-one correspondence between graphic codes and text codes. The annotation system provides feedback loops that ensure consistency is preserved across multiple conversion operations.
3Illumination intensity
If graphic codes are used directly in vehicle controllers, then graphical representation capability is improved, but logical operation capability is lost
Solution Approach 1:
The patent segments the code system into two distinct but corresponding parts: graphic codes for visual representation and text codes for logical operation. The annotation system creates a segmented structure where each graphic code element has a corresponding text code representation, enabling both capabilities to function independently yet consistently.
Data Source
AI summary
A vehicular development and debugging system includes: a computer device, a bus adapter or a burner, where the computer device includes a processor, a readable storage medium, a communication bus and a communication interface; the readable storage medium is configured to store programs of performing the conversion method of text codes and graphic codes, and the programs cause the processor to perform the operations corresponding to the conversion method of text codes and graphic codes to generate the text codes; the processor, the readable storage medium and the communication interface communicate with the bus adapter via the communication bus; the processor is configured to compile at least one fragment of execution codes in the text codes; and the bus adapter or the burner is configured to write the compiled execution codes into a debugging device.