Fluid Ejection Controller Interface Random Header Removal
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Some fluid ejection device designs are not compatible with control data packets that contain random length headers, leading to operational issues, as they may not be able to properly align or process the random data bits, affecting data integrity and electromagnetic compatibility.
Innovation Solution
A fluid ejection array controller interface is introduced to identify and remove randomly inserted bits from control data packets, allowing for alignment and modification of the data packets to ensure compatibility with different fluid ejection devices, using an independent internal clock for buffering and modifying the clock timing and data burst length.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If control data packets contain random length headers with random data bits, then electromagnetic compatibility is improved and data integrity is enhanced, but compatibility with fluid ejection devices is worsened and device operational reliability deteriorates
Solution Approach 1:
The interface extracts and removes the random length header containing random data bits from the incoming control data packet. This separation allows the random data to be discarded while the structured payload is processed, resolving the contradiction by eliminating the harmful randomness for devices that cannot handle it.
Solution Approach 2:
The fluid ejection array controller interface acts as an intermediary between the controller and the fluid ejection device. It translates packets with random headers into a format the device can process, mediating between the electromagnetic compatibility benefits of random data and the device's inability to handle such data.
2Reliability
If random data bits are inserted in control data packets, then data integrity is improved through identification of integrity issues, but device compatibility is worsened and processing capability deteriorates
Solution Approach 1:
The interface extracts the random data bits from the control data packet header, separating them from the structured payload. This allows the system to maintain data integrity checking capabilities while removing the incompatible random data portion before it reaches the fluid ejection device.
Solution Approach 2:
The interface changes the parameter of data packet structure by removing the random length header and presenting a standardized format to the device. This parameter transformation maintains the integrity benefits of random data transmission while adapting to device compatibility requirements.
3Object-affected harmful factors
If shift register fluid ejection implementations are used with random length headers, then electromagnetic compatibility is improved, but compatibility with alternative fluid ejection devices is worsened
Solution Approach 1:
The fluid ejection array controller interface provides universal functionality by handling multiple packet formats. It can process packets with random length headers from shift register implementations while also being compatible with alternative fluid ejection devices that require standardized formats, making the system multi-functional and broadly compatible.
Solution Approach 2:
The interface serves as a universal intermediary that translates between different packet formats. It receives packets with random headers suitable for electromagnetic compatibility and converts them to standardized formats suitable for various alternative fluid ejection devices, enabling universal compatibility across different implementations.
Data Source
AI summary
A fluid ejection controller interface includes input logic to receive control data packets and a first clock signal, each control data packet including a set of primitive data bits and a set of random bits, wherein the input logic identifies the random bits in the received control data packets to facilitate the creation of modified control data packets. The fluid ejection controller interface includes a clock signal generator to generate a second clock signal that is different than the first clock signal, and output logic to receive the modified control data packets, and output the modified control data packets to a fluid ejection controller of a fluid ejection device based on the second clock signal.