Fluid Ejection Controller Interface for Random-Bit Packet Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Fluid ejection devices in printing systems face compatibility issues due to the insertion of random data bits in control data packets, leading to improper operation in systems that do not support random length headers, and require a flexible system design for compatibility with various fluid ejection architectures.
Innovation Solution
A fluid ejection array controller interface is introduced to identify and remove randomly inserted bits from control data packets, using clock recovery logic and counter logic to generate a free-running clock signal, allowing alignment and modification of data packets for compatibility with different fluid ejection devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If random data bits are inserted in control data packets to spread frequency of electromagnetic emissions, then electromagnetic compatibility is improved, but compatibility with fluid ejection devices that do not support random length headers deteriorates
Solution Approach 1:
The patent introduces an intermediary component (controller or interface) between the data source and fluid ejection devices that detects random data bits in control packets and removes them before forwarding to incompatible devices. This intermediary enables electromagnetic compatibility benefits to be retained while ensuring broad device compatibility.
Solution Approach 2:
The system dynamically changes the parameter of data packet structure by detecting the presence of random data bits and modifying the packet format accordingly - removing random bits when targeting devices that don't support them, while preserving them when targeting devices that do support them.
2Reliability
If random length headers are utilized in control data packets, then data integrity identification is improved, but operation of fluid ejection devices with incompatible control structures deteriorates
Solution Approach 1:
The system employs dynamic adaptation where the controller detects the presence and length of random headers in incoming packets, then dynamically adjusts its processing accordingly - removing them for incompatible devices while preserving them for compatible ones, enabling the system to operate reliably across different device types.
Solution Approach 2:
The controller acts as an intermediary that detects data integrity issues through random headers and selectively removes them based on the target device's capabilities, ensuring both data integrity and operational compatibility.
3Device complexity
If a fixed control word structure is used in fluid ejection devices, then device simplicity is improved, but flexibility to support random length headers deteriorates
Solution Approach 1:
The patent places the complexity of handling random length headers in an intermediary controller rather than in the fluid ejection device itself. The device maintains its simple fixed control word structure while the controller performs the complex detection and removal of random headers, preserving device simplicity while enabling versatility.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A fluid ejection controller interface includes output logic to receive control data packets, each control data packet including a set of primitive data bits and a set of random bits. The fluid ejection controller interface includes counter logic to cause the output logic to output modified control data packets to a fluid ejection controller of a fluid ejection device.