Fluid ejection controller interface, method and apparatus for controlling fluid ejection
By combining clock recovery logic and counter logic, random insertion bits in the fluid injection device are removed, compatibility problems in the prior art are solved, printing quality and injection control accuracy are improved, and it is suitable for a variety of printing density applications.
Patent Information
- Application Number
- CN201980090006.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-02-06
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2039-02-06
AI Technical Summary
The existing fluid injection device design fails to effectively remove the random insertion bits when processing control data packets of random length headers, resulting in compatibility problems and electromagnetic compatibility radiation frequency expansion during the injection period, affecting the printing quality.
The clock recovery logic is used to generate a free-running clock signal, and the position of the random insertion bit is identified through the counter logic, the output logic removes the random insertion bit, and the modified control data packet is output to the fluid injection device to ensure compatibility and accuracy of injection control.
The compatibility processing of random length headers is achieved, the random insertion bits are removed, and the compatibility of fluid injection devices and the accuracy of injection control is improved. It is suitable for high-density and low-density printing applications, providing flexible system design.
Smart Images

Figure CN113348467B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to fluid injection control. Background Art
[0002] Many printing devices include at least one fluid ejection device (e.g., a printhead) that is designed to receive a cartridge filled with a fluid (e.g., ink or toner in the case of an inkjet printing device, or a fine agent in the case of a three-dimensional printing device). The fluid ejection device further includes at least one nozzle through which the fluid is dispensed from the cartridge onto a substrate (e.g., paper). When printing a document, the print engine controller of the printing device may send commands to the fluid ejection device that control when each nozzle of the fluid ejection device "fires" or dispenses the fluid. Summary of the invention
[0003] In one aspect, the present disclosure provides a fluid injection controller interface, comprising: output logic for receiving control data packets, each control data packet comprising a set of primitive data bits and a set of random bits; and counter logic for causing the output logic to output a modified control data packet in which the set of random bits is removed to a fluid injection controller of a fluid injection device.
[0004] In one aspect, the present disclosure provides a method for controlling fluid injection, comprising: generating a free-running clock signal by clock recovery logic based on a received burst mode input clock signal; receiving control data packets by output logic, each control data packet including a set of primitive data bits and a set of random bits; and outputting, by the output logic, a modified control data packet from which the set of random bits are removed to a fluid injection controller of a fluid injection device.
[0005] In one aspect, the present disclosure provides a device for fluid injection, comprising: clock recovery logic for recovering a free-running clock signal from a received burst mode input clock signal; a first output logic component for receiving control data packets, each control data packet comprising a set of primitive data bits and a set of random bits; a second output logic component for receiving the free-running clock signal; and counter logic for causing the first output logic component to output a modified control data packet from which the set of random bits have been removed to a fluid injection controller of the fluid injection device, and for causing the second output logic component to output an output clock signal to the fluid injection controller. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] Figure 1 is a block diagram illustrating elements of a printing device according to one example.
[0007] Figure 2is a diagram illustrating a control data packet that may be used to communicate a command for causing a nozzle of a fluid ejection device to fire, according to one example.
[0008] Figure 3 is a block diagram illustrating a fluid ejection array controller interface according to one example.
[0009] Figure 4 is a diagram for use according to an example Figure 3 0048. The timing diagram of the timing of the signals of the fluid ejection array controller interface is shown in FIG.
[0010] Figure 5 is a block diagram illustrating an example of a fluid injection controller interface.
[0011] Figure 6 is a flow chart illustrating a method of processing a control data packet according to one example. DETAILED DESCRIPTION
[0012] In the following detailed description, reference is made to the accompanying drawings which form a part thereof, and in which specific examples in which the present disclosure may be practiced are illustrated by way of illustration. It will be understood that other examples may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description will not be understood in a restrictive sense, and the scope of the present disclosure is defined by the appended claims. It will be understood that, unless otherwise specifically noted, the features of the various examples described herein may be combined with each other in part or in whole.
[0013] When printing a document, a print engine controller of a printing device may send commands in control data packets to a fluid ejection device (e.g., a print head) via a data path, which commands control when each nozzle of the fluid ejection device "fires" or dispenses fluid (e.g., ink, toner in the case of an inkjet printing device, or fine agent in the case of a three-dimensional printing device). For high-density printing applications, the various nozzles may be grouped into multiple "primitives" so that one nozzle in each primitive fires at any given time based on data loaded from the print engine controller (e.g., one data bit per primitive). For lower-density printing applications, multiple primitives may be combined to form "virtual" primitives, where one nozzle in each virtual primitive fires at any given time (thus, some of the virtual primitives may not cause any nozzles to fire).
[0014] Some shift register fluid jet implementations may allow random data to be inserted into the header of a control data packet. A variable number of random data bits may be added to the header. The random data bits may have no functional impact on the real nozzle data and / or control word data, but may provide benefits, such as identifying data integrity issues and effectively randomizing or jittering the firing period to extend the frequency of electromagnetic compatibility radiation associated with the firing. However, some fluid jet device designs may not utilize receivers that are compatible with random length headers. These fluid jet device designs may not operate properly in systems that utilize random length headers. For example, some fluid jet device designs may utilize different control words or data path structures, and therefore remapping of bits within the data packet may be performed to provide compatibility. This remapping involves the ability to align to the random length header to determine the location of the real control word / data packet.
[0015] Some examples of the present disclosure are directed to a fluid jet array controller interface that determines the location of random data within a control data packet. Aligning to a random length header allows the random header to be removed and / or the data packet (including the control word) to be modified. Some examples of the present disclosure are directed to a fluid jet array controller interface that removes random insertion bits from the header of a control data packet before providing the control data packet to a fluid jet device. Some examples disclosed herein allow a system defined for compatibility with a shift register fluid jet implementation to be used with an alternative fluid jet device (e.g., by removing the random header) or a system defined for a specific control word bit ordering (e.g., address bit position) to be used with an alternative fluid jet device (e.g., by modifying the control word data and / or bit mapping to rearrange the control word bits). Some examples provide flexible system design for future undefined fluid jet architectures.
[0016] In one example, a fluid jet array controller interface includes clock recovery logic for receiving a burst mode input clock signal and generating a free running clock signal. The fluid jet array controller interface may include counter logic for identifying the position of a random insertion bit based on the free running clock signal. The fluid jet array controller interface includes output logic for removing the random insertion bit based on the identification performed by the counter logic, and outputting a modified data packet with the random insertion bit removed to the fluid jet device. The output logic also generates the output clock signal by masking the free running clock signal during a time corresponding to the position of the random insertion bit.
[0017] Although examples of the present disclosure may be discussed within the context of inkjet printing, the techniques disclosed herein may be further applied to control fluid ejection devices of three-dimensional printing devices and other devices that eject fluids (such as inks, toners, etc., or fine agents (e.g., binder materials, powders, etc.) used in additive manufacturing processes.
[0018] Figure 1 1 is a block diagram illustrating elements of a printing device 100 according to one example. The printing device 100 includes a print engine controller 102, a fluid ejection array controller interface 104, and a fluid ejection device 106. In one example, the fluid ejection device 106 can be one of a plurality of fluid ejection devices (e.g., a print head) arranged in a fluid ejection array (e.g., a print bar) of a printing device (e.g., an inkjet printing device or a three-dimensional printer). The fluid ejection device 106 includes a nozzle array 108, which further includes nozzle columns 110(1)-110(X) (hereinafter collectively referred to as "nozzle columns 110") arranged in rows along the fluid ejection device 106. Each nozzle column 110 includes a plurality of nozzles arranged to dispense a fluid onto a substrate, wherein the nozzles may be arranged into groups referred to as "primitives". The primitives may be further arranged into groups referred to as "virtual primitives". The number and arrangement of the nozzles may vary depending on the desired printing density. The fluid ejection device 106 also includes a fluid ejection array controller 112, which is connected to the nozzle array 108. In some examples, the fluid-jet array controller 112 may also be referred to as a fluid-jet controller, and the fluid-jet array controller interface 104 may also be referred to as a fluid-jet controller interface.
[0019] The fluid jet array controller interface 104 receives a control data packet 103 from the print engine controller 102 for controlling fluid ejection by the nozzles of the nozzle array 108. The interface 104 removes the random insertion bits from the received control data packet 103 to create a modified control data packet 105 from which the random insertion bits are removed, and outputs the modified control data packet 105 to the fluid jet array controller 112. The fluid jet array controller 112 generates ejection control data 113 for the nozzles of the nozzle array 108 (or more specifically, in some examples, for the virtual primitives of the nozzle array 108) based on the content of the modified control data packet 105. A data path interconnects the print engine controller 102, the fluid jet array controller interface 104, and the fluid jet array controller 112, and transmits the control data packet 103 and the modified control data packet 105. The data path may be a high-speed data path, such as a multi-lane serial bus.
[0020] In one example, the control data packets 103 are "fire pulse group" (or "FPG") packets that contain data about which nozzles of the fluid ejection device 106 should fire. For example, the control data packets 103 may identify the primitives or virtual primitives that contain the nozzles to fire, or the packets may contain data bits for each primitive. Figure 2An example of a firing pulse group is illustrated in further detail in FIG. 1 . The fluid jet array controller interface 104 can be configured to remove the random insertion bits from the received control data packet 103 to create a modified control data packet 105. Based on the information contained in the modified control data packet 105, the fluid jet array controller 112 writes unique primitive data (e.g., the worth of data for one nozzle) to each primitive of the fluid jet device 106. The unique primitive data is contained in the firing control data 113. This can involve inserting a null value into the control data packet 103 to indicate that a particular primitive should not cause any nozzle to fire.
[0021] The fluid jet array controller 112 may also generate a plurality of nozzle control bits based on the information contained in the modified control data packet 105. These nozzle control bits may include a combination of primitive data local to that primitive, address information, and a FIRE (fire) signal. The nozzle control bit commands the addressed nozzle to fire. In one example, the fluid jet array controller 112 generates one nozzle control bit for each primitive on the fluid jetting device 106. In one example, the fluid jet array controller 112 fills the nozzle control bit with a bit value (e.g., "0" or "1") indicating whether the nozzle identified by the corresponding address should fire. The fluid jet array controller 112 may also deliver address data to the primitives of the fluid jetting device 106. In one example, the address data identifies (e.g., by the corresponding address) which nozzles within the primitives of the fluid jetting device 106 should fire.
[0022] In one example, the fluid ejection array controller interface 104 is implemented as a device separate from the fluid ejection device 106 and positioned between the print engine controller 102 and the fluid ejection device 106. In another example, the fluid ejection array controller interface 104 is integrated into the fluid ejection device 106 and may be located on a common semiconductor die with the fluid ejection array controller 112.
[0023] Figure 2 2 is a diagram illustrating a control data packet 200 according to an example, which can be used to convey a command for causing a nozzle of a fluid ejection device to eject. The control data packet 200 is a control data packet 103 ( Figure 1 ). In one example, the control data packet 200 is a fire pulse group (or FPG) packet. In one example, the control data packet 200 includes random data 202, a header 204, a payload including a set of address bits 206 and / or a set of fire data bits 208, and a footer 210. Figure 2The examples illustrated in are abstract concepts and are not intended to limit the number of bits that may be included in package 200 or in any particular portion of package 200 .
[0024] The random data 202 includes a random number of random data bits added to the front end of the control data packet 200 in front of the header 204. In one example, the random data 202 is generated by a pseudo-random number generator (PRNG), such as by using a linear feedback shift register method. The length of the random data 202 (i.e., the number of random data bits included) and the value of the random data bits can both be determined by the PRNG. In one example, the random data 202 having a pseudo-random length includes 0, 2, 4, 6 or 8 bits of pseudo-random data.
[0025] In one example, the header 204 includes a header that is generated by the fluid ejection array controller 112 ( Figure 1 ) is used to detect the start of the control data packet 200. Therefore, the header 204 may include some predefined bit sequence that indicates the start of the control data packet. In one example, the header 204 additionally includes a set of primitive selection bits 212. The primitive selection bits 212 may be used, for example, to identify which primitive within the virtual primitive is being addressed (and therefore should be ejected). The primitive selection bits 212 may be included in different parts of the control data packet 200, such as the payload or footer 210.
[0026] In one example, the set of address bits 206 identifies, for each primitive, an address (also referred to as an "embedded address") corresponding to a nozzle to be fired (i.e., firing unique primitive data and ejecting fluid). In one example, the set of address bits 206 may be omitted from the control data packet 200; in this case, the address bits 206 may be generated by an address generator of the fluid ejection array controller 112.
[0027] In one example, the set of firing data bits 208 includes valid data (e.g., unique primitive data) for one nozzle of each primitive on the fluid ejection device 106. The data included in the set of firing data bits 208 determines whether the nozzle identified by the set of address bits within a particular primitive should fire. For example, the firing data bits 208 may include a non-null value (e.g., "1") to indicate that the nozzle of the primitive should fire. The data included in the set of firing data bits 208 may be different for each primitive.
[0028] In one example, the footer 210 includes bits used by the fluid ejection array controller 112 to detect the end of the control data packet 200. Thus, the footer 210 may include some predefined sequence of bits that indicates the end of the control data packet.
[0029] Once the control data packet 200 is loaded into the fluid ejection array controller 112, the information bits for data and addresses are then present at each primitive. At this point, the ejection signal is sent to all primitives (propagating from the first primitive to the last primitive). The ejection signal then generates nozzle control bits, which include a combination of primitive data, address information, and FIRE (ejection) signals local to that primitive. The nozzle control bits are then sent to the primitive groups on the fluid ejection device 106, and these primitive groups will cause the nozzles addressed by the nozzle control bits to eject. In order to cause all nozzles on the fluid ejection device 106 to eject in one ejection pulse group, a virtual primitive control packet 200 will therefore be loaded for each address value.
[0030] Figure 3 is a block diagram illustrating a fluid ejection array controller interface 300 according to one example. Figure 3 The interface 300 shown in FIG. Figure 1 1. The interface 300 includes a DCLK input 302, a DATA_x input 304, a clock signal generator 306, a clock recovery logic 308, a trainable gated counter 310, AND gates 312 and 314, and a DCLK out Output 316 and DATAx out Output 318. Clock signal generator 306 may be a phase locked loop or a digitally controlled oscillator. As described in further detail below, the data signal and clock signal received by interface 300 are immediately re-driven to the receiving fluid ejection device in real time with minimal latency, with random bits removed. Figure 4 To describe in further detail Figure 3 .
[0031] Figure 4 is a diagram for use according to an example Figure 3 0048. A timing diagram of the timing of the signals of the fluid ejection array controller interface 300 is shown in FIG. Figure 4 Five control packets 402(0)-402(4) (collectively referred to herein as control packets 402) are shown. In one example, control packets 402 are "fire pulse group" (or "FPG") packets or data bursts that contain data about which nozzles of a fluid ejection device should fire. Each of control packets 402 includes real packet data (e.g., real packet data 420(1), 420(2), and 420(3)) and random data (e.g., random data 418(2) and 418(3)).
[0032] Figure 4Also shown are signals 404, 406, 408, and 410. DATA_x signal 404 represents a control data packet 402 received by interface 300 via input 304 and provided in serial fashion to an input of AND gate 314. DCLK signal 406 represents an input clock signal received by interface 300 via input 302 and provided to clock recovery logic 308. DCLK free_running Signal 408 is a free running clock signal generated by clock recovery logic 308 based on DCLK signal 406 and the clock signal provided by clock signal generator 306. Clock recovery logic 308 converts DCLK free_running Signal 408 is output to trainable gated counter 310 and to the input of AND gate 312. DCLK out Signal 410 is the output clock signal from AND gate 312 to output 316. AND gate 314 converts DATA_ xout signal output to output 318, the DATA_ xout The signals represent real packet data (eg, real packet data 420(1), 420(2), and 420(3)). The real packet data output by AND gate 314 for each control data packet may also be referred to herein as a modified control data packet.
[0033] In one example, inputs 302 and 304 are connected to a print engine controller (e.g., print engine controller 102), and outputs 316 and 318 are connected to a fluid ejection array controller (e.g., fluid ejection array controller 112). In operation according to one example, clock recovery logic 308 receives a burst mode input DCLK signal 406 via input 302 and a clock signal provided by clock signal generator 306. Based on these received clock signals, clock recovery logic 308 recovers an internal free running clock signal (DCLK) from DCLK signal 406 using a clock recovery method. free_running Signal 408). In one example, DCLK free_running Signal 408 is a phase-locked and continuous clock signal. The clock recovery method can be a phase-locked loop method, an oversampling method, or another clock recovery method. Clock recovery logic 308 converts DCLK free_running Signal 408 is output to trainable gated counter 310 and to the input of AND gate 312 .
[0034] Trainable gated counter 310 includes counter logic for free_runningSignal 408 determines the position of random data (e.g., random data 418(2) and 418(3)) within control data packet 402. Real packet data (e.g., real packet data 420(1), 420(2), and 420(3)) have a fixed burst period. Since the idle period (T IDLE ) has a fixed period (i.e., a fixed number of DCLK free_running cycle), so the gated counter 310 can be used to control a fixed number of DCLK free_running The cycle (equal to the idle period) is counted and the output clock (DCLK out ) Remove / mask these DCLK free_running During the time period corresponding to the real packet data (eg, the real packet data 420(1), 420(2), and 420(3)), the gated counter 310 sets the DCLK_ with a logic high value via the communication link 311. enable The signal is output to the input of AND gate 312. This enables AND gate 312 to output DCLK out Signal 410, the DCLK out The signal corresponds to DCLK at the input of AND gate 312 free_running During the time period corresponding to the random data (eg, random data 418(2) and 418(3)), the gated counter 310 sets DCLK_ enable signal changes to a logic low value, which causes AND gate 312 to mask the received DCLK free_running Signal 408.
[0035] During the time period corresponding to the real packet data (eg, the real packet data 420(1), 420(2), and 420(3)), the gated counter 310 transmits DATA_420(1), which has a logic high value, to the communication link 313. x _ enable The signal is output to the input of AND gate 314. This enables AND gate 314 to output a DATA_x signal corresponding to DATA_x signal 404 at the input of AND gate 314. out The gated counter 310 receives the DATA_ signal and the real packet data is driven serially to the fluid ejection device (e.g., fluid ejection device 106) via output 318 by AND gate 314. During the time period corresponding to the random data (e.g., random data 418(2) and 418(3)), the gated counter 310 sends the DATA_ signal to the fluid ejection device (e.g., fluid ejection device 106). x _ enable The signal changes to a logic low value, which causes AND gate 314 to mask the received DATA_x signal 404, thereby blocking random data. Multiple DATA channels may also be masked in the manner described above.
[0036] The gated counter 310 uses a counter target value corresponding to the idle period. The counter target value may be fixed within the gated counter 310, or the gated counter 310 may be adaptive / trainable to determine the idle period and use the corresponding counter target value. Since the real packet data (e.g., the real packet data 420(1), 420(2), and 420(3)) has a fixed period (i.e., a fixed number of DCLK free_running cycle), so the gated counter 310 can determine the idle period based on the length of the real packet data and the position of the end point of the data burst.
[0037] One example of the present disclosure relates to a fluid injection controller interface. Figure 5 is a block diagram illustrating an example of a fluid ejection controller interface 500. The fluid ejection controller interface 500 may include clock recovery logic 506 for receiving a burst mode input clock signal 502 and generating a free running clock signal 508. The interface 500 includes output logic 512 for receiving control packets 504. Each control packet 504 includes a set of primitive data bits and a set of random bits. The interface 500 includes counter logic 510 for causing the output logic 512 to output a modified control packet 514 to a fluid ejection controller 518 of a fluid ejection device 516. In other examples, the interface 500 may include more or fewer elements, such as clock recovery logic 506 that is not included in the interface 500.
[0038] The counter logic 510 may identify the position of the random bits in the received control data packet based on the free-running clock signal. The set of random bits of each control data packet 504 may have a pseudo-random length. The value of the set of random bits of each control data packet 504 may have a pseudo-random value. The counter logic 510 may count clock cycles of the free-running clock signal 508 to identify the position of the random bits. The output logic 512 may include a logic component for receiving the free-running clock signal 508 and outputting the output clock signal to the fluid injection controller 518. The counter logic 510 may cause the logic component to mask the free-running clock signal 508 during a period corresponding to the set of random bits of each control data packet 504. The output logic 512 may include a logic component for receiving the control data packet 504 and outputting the modified control data packet 514, and the counter logic 510 may cause the logic component to mask the received control data packet 504 during a period corresponding to the set of random bits of each received control data packet 504. The fluid injection controller interface 500 may be implemented separately from the fluid injection device 516. The fluid ejection controller interface 500 can be integrated into the fluid ejection device 516. The fluid ejection controller interface 500 can be located on a common semiconductor die with the fluid ejection controller 518.
[0039] The output logic 512 may include modification logic for modifying the positions and / or values of bits in the received control packet 504 to facilitate creation of a modified control packet 514, and the modified control packet 514 may or may not include the set of random bits.
[0040] Another example of the present disclosure relates to a method of processing a control data packet. Figure 6 6 is a flow chart illustrating a method 600 of processing a control data packet according to an example. At 602, the method 600 includes: generating, by clock recovery logic, a free-running clock signal based on a received burst mode input clock signal. At 604, the method 600 includes: receiving, by output logic, control data packets, each control data packet including a set of primitive data bits and a set of random bits. At 606, the method 600 may include: identifying, by counter logic, a position of the random bits in the received control data packet based on the free-running clock signal. At 608, the method 600 includes: outputting, by the output logic, a modified control data packet to a fluid ejection controller of a fluid ejection device. In other examples, the method 600 may include more or fewer steps, such as the identification at 606 that is not included in the method 600.
[0041] The set of random bits of each control data packet in method 600 may have a pseudo-random length, and the value of the set of random bits of each control data packet may be a pseudo-random value. Method 600 may further include: receiving, by output logic, a free-running clock signal; and controlling, by counter logic, the output logic to generate an output clock signal by masking the free-running clock signal during a period corresponding to the set of random bits of each control data packet. Method 600 may further include: removing, by the output logic, random bits from a received control data packet based on the identified position of the random bits to create a modified control data packet.
[0042] Yet another example of the present disclosure is directed to a device that includes clock recovery logic for recovering a free-running clock signal from a received burst mode input clock signal. The device includes a first output logic component for receiving a control data packet. Each control data packet includes a set of primitive data bits and a set of random bits. The device includes a second output logic component for receiving the free-running clock signal. The device includes counter logic for causing the first output logic component to output a modified control data packet to a fluid injection controller of a fluid injection device, and causing the second output logic component to output an output clock signal to the fluid injection controller.
[0043] The counter logic may identify a position of the random bit in the received control data packet based on the free running clock signal. The counter logic may count clock cycles of the free running clock signal to identify the position of the random bit. The counter logic may cause the first output logic component to mask the received control data packet based on the identified position and cause the second output logic component to mask the free running clock signal based on the identified position.
[0044] Various aspects of the present disclosure may be implemented by machine-readable instructions and / or in a combination of machine-readable instructions and hardware, such as using an application specific integrated circuit (ASIC), a programmable logic array (PLA) (including a field programmable gate array (FPGA)), or a state machine deployed on a hardware device, a general-purpose computer, or any other hardware equivalent. For example, computer-readable instructions related to the method(s) discussed herein may be used to configure a hardware processor to perform the blocks, functions, and / or operations of the disclosed methods.
[0045] In addition, when a hardware processor executes instructions to perform an "operation", this may include the hardware processor directly performing the operation and / or facilitating, directing, or cooperating with another hardware device or component (e.g., a coprocessor, etc.) to perform the operation. A processor that executes machine-readable instructions related to the (multiple) methods described herein may be considered a programmed processor or a dedicated processor. Thus, the modules (including associated data structures) of the present disclosure for controlling the devices disclosed herein may be stored on a tangible or physical (broadly non-transitory) computer-readable storage device or medium, such as a volatile memory, a non-volatile memory, a ROM memory, a RAM memory, a magnetic or optical drive, device, or a floppy disk, etc. More specifically, a computer-readable storage device may include any physical device that provides the ability to store information (such as data and / or instructions to be accessed by a processor or computing device (such as a computer or application server)).
[0046] Although specific examples have been illustrated and described herein, various alternative and / or equivalent embodiments may be used to replace the specific examples shown and described without departing from the scope of the present disclosure. This application is intended to cover any modifications or variations of the specific examples discussed herein. Therefore, the present disclosure is intended to be limited only by the claims and their equivalents.
Claims
1. A fluid injection controller interface, comprising: output logic for receiving control data packets, each control data packet including a group of primitive data bits and a group of random bits; as well as The counter logic is used to cause the output logic to output the modified control data packet with the set of random bits removed to the fluid ejection controller of the fluid ejection device.
2. The fluid injection controller interface of claim 1, wherein: The counter logic identifies the location of the random bits in a received control data packet based on a free running clock signal.
3. The fluid injection controller interface according to any one of claims 1 to 2, further comprising: Clock recovery logic that receives a burst mode input clock signal and generates a free running clock signal.
4. The fluid injection controller interface according to any one of claims 1 to 2, wherein: The set of random bits in each control data packet has a pseudo-random length.
5. The fluid injection controller interface according to any one of claims 1 to 2, wherein: The value of the set of random bits in each control data packet is a pseudo-random value.
6. The fluid injection controller interface according to any one of claims 1 to 2, wherein: The counter logic counts clock cycles of a free running clock signal to identify the position of the random bit.
7. The fluid injection controller interface according to any one of claims 1 to 2, wherein: The output logic includes logic components for receiving a free running clock signal and outputting an output clock signal to the fluid ejection controller.
8. The fluid injection controller interface of claim 7, wherein: The counter logic causes the logic component to mask the free running clock signal during a period corresponding to the set of random bits in each control data packet.
9. The fluid injection controller interface according to any one of claims 1 to 2, wherein: The output logic includes logic components for receiving the control packets and outputting the modified control packets, and wherein the counter logic causes the logic components to mask the received control packets during a period corresponding to the set of random bits in each received control packet.
10. The fluid injection controller interface according to any one of claims 1 to 2, wherein: The fluid ejection controller interface is implemented separately from the fluid ejection device.
11. The fluid injection controller interface according to any one of claims 1 to 2, wherein: The fluid ejection controller interface is integrated into the fluid ejection device.
12. The fluid injection controller interface of claim 11, wherein: The fluid ejection controller interface is located on a common semiconductor die with the fluid ejection controller.
13. A method for controlling a fluid jet, comprising: generating, by clock recovery logic, a free-running clock signal based on the received burst-mode input clock signal; receiving control data packets by the output logic, each control data packet including a group of primitive data bits and a group of random bits; as well as The modified control data packet with the set of random bits removed is output by the output logic to a fluid ejection controller of the fluid ejection device.
14. The method according to claim 13, further comprising: The position of the random bit in the received control data packet is identified by counter logic based on the free running clock signal.
15. The method according to any one of claims 13 to 14, wherein: The set of random bits in each control data packet has a pseudo-random length, and wherein the value of the set of random bits in each control data packet is a pseudo-random value.
16. The method according to claim 14, further comprising: receiving, by the output logic, the free running clock signal; as well as The output logic is controlled by the counter logic to generate an output clock signal by masking the free running clock signal during a period corresponding to the set of random bits in each control data packet.
17. The method according to any one of claims 13 to 14, further comprising: The random bits are removed from the received control data packet by the output logic based on the identified position of the random bits, thereby creating the modified control data packet.
18. A device for fluid ejection, comprising: clock recovery logic for recovering a free running clock signal from a received burst mode input clock signal; A first output logic component, configured to receive control data packets, each control data packet comprising a group of primitive data bits and a group of random bits; a second output logic component for receiving the free-running clock signal; as well as The counter logic is used to cause the first output logic component to output the modified control data packet with the group of random bits removed to the fluid injection controller of the fluid injection device, and to cause the second output logic component to output the output clock signal to the fluid injection controller.
19. The apparatus according to claim 18, wherein: The counter logic identifies a location of the random bit in a received control data packet based on the free running clock signal.
20. The apparatus of claim 19, wherein: The counter logic counts clock cycles of the free-running clock signal to identify a position of the random bit, causes the first output logic component to mask a received control data packet based on the identified position, and causes the second output logic component to mask the free-running clock signal based on the identified position.
