US9269029B2 - Data communication in a printing device - Google Patents

Data communication in a printing device Download PDF

Info

Publication number
US9269029B2
US9269029B2 US14/413,933 US201214413933A US9269029B2 US 9269029 B2 US9269029 B2 US 9269029B2 US 201214413933 A US201214413933 A US 201214413933A US 9269029 B2 US9269029 B2 US 9269029B2
Authority
US
United States
Prior art keywords
data
packet
based control
data streams
print
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
US14/413,933
Other languages
English (en)
Other versions
US20150206037A1 (en
Inventor
Jordi Sempere Agullo
Narcis Simon Rabaseda
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hewlett Packard Development Co LP
Original Assignee
Hewlett Packard Development Co LP
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hewlett Packard Development Co LP filed Critical Hewlett Packard Development Co LP
Publication of US20150206037A1 publication Critical patent/US20150206037A1/en
Assigned to HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P. reassignment HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HEWLETT-PACKARD ESPANOLA SL
Application granted granted Critical
Publication of US9269029B2 publication Critical patent/US9269029B2/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K15/00—Arrangements for producing a permanent visual presentation of the output data, e.g. computer output printers
    • G06K15/02—Arrangements for producing a permanent visual presentation of the output data, e.g. computer output printers using printers
    • G06K15/18—Conditioning data for presenting it to the physical printing elements
    • G06K15/1801—Input data handling means
    • G06K15/1803—Receiving particular commands
    • G06K15/1806—Receiving job control commands
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K15/00—Arrangements for producing a permanent visual presentation of the output data, e.g. computer output printers
    • G06K15/02—Arrangements for producing a permanent visual presentation of the output data, e.g. computer output printers using printers
    • G06K15/10—Arrangements for producing a permanent visual presentation of the output data, e.g. computer output printers using printers by matrix printers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K15/00—Arrangements for producing a permanent visual presentation of the output data, e.g. computer output printers
    • G06K15/02—Arrangements for producing a permanent visual presentation of the output data, e.g. computer output printers using printers
    • G06K15/10—Arrangements for producing a permanent visual presentation of the output data, e.g. computer output printers using printers by matrix printers
    • G06K15/102—Arrangements for producing a permanent visual presentation of the output data, e.g. computer output printers using printers by matrix printers using ink jet print heads
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K15/00—Arrangements for producing a permanent visual presentation of the output data, e.g. computer output printers
    • G06K15/40—Details not directly involved in printing, e.g. machine management, management of the arrangement as a whole or of its constitutive parts
    • G06K15/4045—Managing the interface to the data source, e.g. choosing an interface for data reception

Definitions

  • a printbar may comprise one or more printheads with a plurality of nozzles to eject liquid ink onto a print medium. Ink is ejected from each nozzle using a transducer.
  • the transducer comprises a nozzle resister; in other ink-jet printers the transducer may comprise a piezoelectric element. Continuous ink-jet printing is also possible, wherein ejected ink is directed onto a print medium using an electro-magnetic field.
  • the ejection of ink by a transducer is controlled by a voltage signal, sometimes referred to as a firing signal.
  • a voltage signal sometimes referred to as a firing signal.
  • one or more printbars of a printing device are mounted above a media transport that transports a print medium along a path under said printbars. In these cases, ink is ejected across a gap formed below the one or more printbars and is deposited on to the print medium carried by the media transport.
  • a print controller or print engine needs to generate firing signals for a plurality of printheads located in one or more printbars based on an image to be printed. Due to the location of the one or more printbars above the media transport, the print controller or print engine is often located in a central printer structure or in a coupled computing device. The print controller or print engine thus sends nozzle firing signals to individual printheads over a plurality of printhead data lines that extend between the central printer structure (or coupled computing device) and the printbar.
  • the nozzle firing data is unidirectional and time-dependent; the transducers need to be accurately controlled in time in order to print a suitable image on a print medium.
  • a printhead monitoring and control bus may also be supplied. Since the printing data flow is unidirectional and it is not possible to guarantee when the printing data will be generated, the printhead control data needs to travel on its own control bus.
  • FIG. 1 is a schematic diagram of at least a portion of a printing device according to an example
  • FIG. 2 is a schematic diagram of at least a portion of a printing device according to another example
  • FIG. 3 is schematic diagram of a number of communication layers for printer communications according to an example
  • FIG. 4A is a schematic diagram of components of a packet-based interface transaction layer according to an example
  • FIG. 4B is a schematic diagram of components of a physical layer according to an example
  • FIG. 5 is a flow diagram showing a method of communicating data in a printing device according to an example.
  • FIG. 6 is a flow diagram showing another method of communicating data in a printing device according to an example.
  • FIG. 1 shows a portion of a printing device 100 according to an example.
  • the printing device comprises a control system 105 .
  • the control system 105 receives image data 115 for use in a printing operation.
  • the image data 115 may be received from a computing device (not shown) coupled to, or forming part of, the control system 105 .
  • the image data 115 may comprise data associated with an image to be printed on a print medium by the printing device.
  • the image data 115 may comprise halftone data.
  • the control system 105 also sends and receives packet-based control data 120 .
  • the control data 120 is referred to as ‘packet-based’ because it is sent and received in packets, i.e. discrete blocks of data of a predefined size.
  • the packets used to communicate the control data 120 may comprise a data or payload portion comprising a fixed-number of bits or bytes of control data encapsulated in a control wrapper.
  • the control wrapper may comprise a predefined number of header and/or footer bits or bytes.
  • the control wrapper may comprise, amongst others: data to route packets (e.g. may specify a source and/or destination hardware address); data for error correction and/or detection; data defining one or more control protocols; data indicating a time-to-live value; data indicating related packets etc. While the packet-based control data 120 may need to be received within a particular time window (for example as defined by a time-to-live value) it does not require a deterministic latency, i.e. packets of control data 120 can accommodate variations in travel times between a source and a destination.
  • the control system 105 comprises a first interface component 110 arranged to receive the image data 115 and to communicate (i.e. to send and/or receive) packet-based control data 120 .
  • the first interface component 110 is communicatively coupled to a coupling medium 125 .
  • the coupling medium couples the control system 105 to a remote printbar 135 , i.e. a printbar that is a set distance from the control system 105 .
  • the set distance is greater than a distance that would allow the control system 105 and the printbar 135 to be connected by conductive traces (e.g. on the order of meters).
  • the printbar 135 comprises a second interface component 140 that is communicatively coupled to the coupling medium 125 .
  • the control system 105 is separate from the printbar 135 , for example it may be mounted or installed in a different section of a structure of the printing device.
  • the second interface component 140 receives data from the coupling medium 125 and distributes print and control data to a plurality of printhead controllers 145 .
  • printhead controllers 145 In FIG. 1 there are N printhead controllers ( 145 A, 145 B, 145 C . . . 145 N), wherein each printhead controller is communicatively coupled to the second interface component 140 via one or more signal lines 150 .
  • Each printhead controller 145 controls one or more printheads. In certain example, the printheads are mounted on the printbar together with the printhead controller 145 .
  • the first interface component 110 combines print data derived from image data 115 and packet-based control data 120 in one or more data streams 130 that have a deterministic latency.
  • Deterministic latency in this case, is achieved by combining the different channels, i.e. one or more channels associated with print data and one or more channels used to send and/or receive packet-based control data. The channels may be combined by multiplexing them in time.
  • the data streams 130 are then communicated over the coupling medium 125 .
  • the second interface component 140 receives the one or more data streams 130 and extracts the print data and packet-based control data, which is then relayed to at least one of the plurality of printhead controllers 145 over signal lines 150 .
  • the second interface component 140 is also arranged to receive control data from at least one of the plurality of printhead controllers 145 over signal lines 150 and transmit said control data as one or more data streams 130 over the coupling medium 125 .
  • These one or more data streams 130 are then received by the first interface component 110 , which extracts the control data for onward communication, for example to a print controller or print engine, as packet-based control data 120 .
  • ink-jet printheads need to be remotely controlled and monitored at regular intervals.
  • this has been accomplished by using low-speed input/output (I/O) interfaces that are independent of the real time printing data lines.
  • low-speed may be interpreted as approximately on an order of ⁇ 10 0 or ⁇ 10 1 mega-bits-per-second (Mbps) and below.
  • I/O interfaces traverse long distances across a structure ( ⁇ 10 0 or ⁇ 10 1 meters) of the printing device.
  • the number of control lines also increases, leading to complex wiring schemes. These, in turn, reduce the reliability and make the assembly and maintenance of the printer more complex.
  • a wiring problem between a print controller or engine, for example housed in a central electronics structure, and one or more printbars of a printing device, such as a page-wide-array printer, is addressed by encoding print and packet-based control data as one or more data streams, which then allows the use of a single coupling medium per printbar.
  • FIG. 2 shows at least a portion of a printing device 200 according to another example. Similar reference numerals are used for features that are related to those shown in FIG. 1 .
  • the printing device 200 comprises a control system 205 and a printbar 235 communicatively coupled via coupling medium 225 .
  • the control system 205 receives halftone data 215 and packet-based control data 220 .
  • the control system 205 also sends packet-based control data 220 , for example over a network or to a computing device.
  • the control system 205 comprises a first interface component 210 .
  • the first interface component 210 may comprise a field-programmable gate array (FPGA).
  • FPGA field-programmable gate array
  • the first interface component 210 comprises a first link-layer component 212 and a first transceiver 214 for encoding and transmitting one or more data streams 236 to the printbar via the coupling medium 225 .
  • the first link-layer component 212 and the first transceiver 214 are also arranged and constructed to receive and decode one or more data streams 238 from the printbar via the coupling medium 225 .
  • Print-data generator 218 comprises logic configured to generate print data with a deterministic latency.
  • deterministic latency it is meant that there is a fixed upperbound on a range of time delays (i.e. latencies) for data signals that can be tolerated by control circuitry. In some cases there may be a fixed latency value that is expected. There may also be a minimum latency value. If data signals are received that have a time delay outside of a predetermined range then the control circuitry may not function or produce an erroneous output. In the example of FIG.
  • the print-data generator 218 receives the halftone data 215 , which may be image data, and converts it into a plurality of print data signals 222 for the printhead controllers.
  • the print-data generator 218 may generate a print data signal for each die on a printer pen, wherein the printer pen forms part of a print head module. If there is a one-to-one mapping between printer pens and printhead controllers, a plurality of printhead controllers m and a plurality of dies n (i.e. silicon dies comprising transducers for ejecting ink), then m*n print data signals may be generated.
  • Other implementations may have different formats for the print data signals depending on the particular printing equipment that is used.
  • the plurality of print data signals 222 are received by the first link-layer component 212 .
  • the first link-layer component 212 of the first interface component 210 is arranged to encode the plurality of print data signals 222 as one or more data streams 236 , i.e. perform link-layer processing, before the one or more data streams are transmitted to the printbar 235 by the first transceiver 214 .
  • the first link-layer component 212 is arranged to continuously transmit data to the print bar with a deterministic latency, which may be the same deterministic latency enforced by the print-data generator 218 .
  • the first interface component 210 also comprises a first packet-based control component 216 .
  • the first packet-based control component 216 sends and/or receives packet-based control data 220 .
  • the first packet-based control component 216 receives packet based control data 220 , for example from a computing device (not shown) and appropriately forwards control packets 224 to the first link-layer component 212 .
  • Appropriately forwarding control packets may comprise performing a first set of packet-processing operations.
  • the first packet-based control component 216 may be a packet-based-interface (PBI) host.
  • PBI packet-based-interface
  • the first packet-based control component 216 is arranged to use the first link-layer component 212 to embed control packets 224 in the one or more data streams 236 carrying the print data (i.e. the data carried by the plurality of print data signals 222 ) with a deterministic latency.
  • the first packet-based control component 216 is also arranged and constructed to receive status and control data 226 extracted from one or more data streams 238 received from the coupling medium 225 by the first transceiver 214 and processed by the first link-layer component 212 .
  • the status and control data may comprise one or more responses received from one or more packet-based control components operating on the printbar 235 , and these responses may be used to determine whether one or more packets need to be re-transmitted, for example by the first packet-based control component 216 . This then provides a high tolerance to transmission errors.
  • a second interface component 240 comprises a second transceiver 244 and a second link-layer component 242 .
  • the second transceiver 240 receives the one or more data streams 236 transmitted by the first transceiver 214 of the first interface component 240 .
  • the second transceiver 240 is arranged to pass received data to the second link-layer component 242 .
  • the second link-layer component 242 extracts the plurality of print data signals 252 and forwards them on to respective printhead controllers.
  • the second link-layer component 242 also extracts packet-based control data 254 from the one or more data streams 236 and forwards this to a second packet-based control component 246 .
  • print data signals 252 for a particular printhead controller are first sent to a serializer 255 .
  • the print data signals may comprise a binary stream.
  • the second interface component 240 comprises a plurality of serializers, one for each printhead module or controller 245 (i.e. serializer 255 A for printhead controller 245 A, serializer 255 B for printhead controller 245 B, etc. until serializer 255 N for printhead controller 245 N).
  • serializer 255 also receives packet-based control data 256 from the second packet-based control component 246 .
  • the print data signals 252 and the packet-based control data 256 are multiplexed by the serializers.
  • FIG. 1 the example of FIG.
  • the second packet-based control component 246 may comprise a repeater with N outputs arranged to identify a control packet for an nth printhead controller and to send the control packet on an nth signal line to an nth serializer.
  • each serializer 255 may comprise a 7b/8b interface to encode 7 bits of received binary data (print data streams for 6 dies and a data stream for the control data) as 8 bits, i.e. 7b/8b encoding, which can then be serialized by the serializer 255 and transmitted to each printhead controller 255 over data and control signal lines 270 .
  • a latency of print data signals is kept deterministic during the transcoding process (i.e. during the 7b/8b encoding).
  • the second interface component 240 which in certain cases is mounted on the printbar 235 , is thus capable of receiving a stream of print and control data and then distributing the received information to individual print heads through much shorter and cheaper cables.
  • the second interface component 240 may also comprise a FPGA device.
  • the second interface component 240 of FIG. 2 also comprises a third packet-based control component 248 .
  • the third packet-based control component 248 is communicatively coupled to the second packet-based control component 246 and receives control data 256 .
  • the third packet-based control component 248 may comprise a PBI device.
  • the third packet-based control component 248 has a number of functions. Firstly, it is arranged to receive commands from the first packet-based control component 216 addressed to itself. Secondly, it is communicatively coupled to each of the printhead controllers 245 via status signal lines 260 . Status signal lines 260 form part of signal lines 250 with data and control signal lines 270 .
  • the third packet-based control component 248 is arranged to gather status data for transmission to the control system 205 , and in turn the first packet-based control component 216 .
  • the third packet-based control component 248 may also gather status and control data from other control circuitry mounted on the printbar 235 , for example, the second interface component 240 itself.
  • the third packet-based control component 248 may generate one or more interrupts to trigger an action within one or more processors forming part of the control system 205 .
  • the third packet-based control component 248 generates status and control data 262 that is sent to the second link-layer component 242 .
  • the second link-layer component 242 is arranged to encode the status and control data 262 as one or more data streams 238 for transmission to the control system 205 by the second transceiver 244 .
  • the third packet-based control component 248 and the second packet-based control component 246 may be combined in a single device.
  • FIG. 3 is a schematic diagram showing a communications stack or layer model according to an implementation example.
  • PBI layers are implemented in one or more of the packet-based control components 216 , 246 and 248 .
  • Printhead Data Generation and Printing Data layers are implemented in print-data generator 218 . They generate the print data that needs to be transmitted.
  • Stream Link Layer 370 and Physical Layer 380 are implemented in one or more of transceivers 214 , 244 and serializers 255 . Each layer in the stack or model may represent a different level of encoding and/or data encapsulation.
  • a PBI transaction layer 310 that forms part of a PBI protocol used for monitoring and control one or more printheads and, in certain case, one or more electronics subsystems, such as other FPGAs, sitting on a printbar.
  • the monitoring and control functions are implemented by computer program code that is retrieved from memory and processed by one or more processors of a computing device, such as a computing device coupled to the control system 105 or 205 .
  • the PBI transaction layer 310 may be a level in which monitoring and control transactions, commands and/or requests are implemented; for example, each packet of control data may belong to a particular transaction such as a status request address to a printhead controller.
  • printhead data generation protocol 340 may correspond to procedures used by the print-data generator 218 , for example commands used by a FPGA implementing the first interface component 110 or 210 .
  • the mechanical control protocol 330 may correspond to procedures used by control circuitry (not shown in FIGS. 1 and 2 ) for controlling other components of the printing device, for example commands used by a FPGA implementing the first interface component 110 or 210 to control position encoders for controlling a media transport.
  • PBI link layer and streaming sub-layer 320 comprise protocols that define how data from the PBI transaction layer 310 is to be processed before sending to a streaming link layer 370 . For example, they may define how data from the PBI transaction layer 310 is to be encapsulated to implement addressing, error detection and/or retransmission functions.
  • the first, second and third packet-based control components 216 , 246 and 248 may implement processing in this layer.
  • the PBI link layer and streaming sub-layer 320 may also comprise protocols defining how packet-based control data is to be prepared for transmission as one or more data streams; for example, may define protocols for preparing data from the PBI transaction layer 310 for embedding in a data stream at the streaming link layer 370 .
  • the first and second link-layer components 212 and 242 may also perform processing for the PBI Link Layer and Streaming Sub-Layer 320 .
  • a protocol defining other real time data 350 may define how mechanical control 330 commands or transactions are communicated to control devices such as encoders and how data such as encoder pulses and column sync pulse are to be structured.
  • the protocol defining other real time data 350 sets out a specification for communicating real-time, time-dependent signals from FGPA devices.
  • Printing data 360 defines how data generated according to printhead data generation protocols 340 is to be structured and/or communicated. For example, printing data 360 may be communicated in real-time according to simplex protocols that maintain a deterministic latency.
  • a streaming link layer protocol 370 This may be implemented by the first and second transceivers 214 and 244 and, in certain cases, the first and second link-layer components 212 and 242 .
  • the streaming link layer protocol 370 may specify how link setup, error detection procedures and/or reporting are to be performed.
  • the streaming link layer protocol 370 sets the format for the one or more data streams 236 and/or 238 that are to be communicated over the coupling medium.
  • the streaming link layer protocol 370 may be based on existing standards such as the low voltage differential signaling (LVDS) standard.
  • LVDS low voltage differential signaling
  • Physical Layer protocol 380 which encompasses three sub-protocols: PCS (Physical Coding Sublayer), PMA (Physical Medium Attachment sublayer) and PMD (Physical Medium Dependent sublayer).
  • PCS Physical Coding Sublayer
  • PMA Physical Medium Attachment sublayer
  • PMD Physical Medium Dependent sublayer
  • FIG. 4A shows an implementation of the PBI transaction layer 310 .
  • the specifications for the PBI transaction layer 310 are split into two groups: a first group of specifications associated with a PBI Host 410 , which may be the first packet-based control component 216 , and a second group of specifications associated with a PBI Device 440 , which may be the third packet-based control component 248 .
  • the first group of specifications associated with a PBI Host 410 may comprise specifications for a user register interface (I/F) 420 and a memory interface such as a Dynamic Random Access Memory (DRAM) bus interface (I/F) 430 .
  • I/F user register interface
  • DRAM Dynamic Random Access Memory
  • the second group of specifications associated with a PBI Device 410 may then comprise specifications for an FPGA Control and Status Register Bus (I/F) 450 and a serial protocol interface 460 such as SPI (Serial Peripheral Interface), UART (Universal Asynchronous Receiver/Transmitter) or others to communicate with external devices.
  • I/F FPGA Control and Status Register Bus
  • serial protocol interface 460 such as SPI (Serial Peripheral Interface), UART (Universal Asynchronous Receiver/Transmitter) or others to communicate with external devices.
  • FIG. 4B shows component parts of the Physical Layer protocol 380 .
  • the PCS layer 470 defines the specifications for one or more of transmit phase compensation and transcoding, such as 8b/10b encoding for transmitting over the coupling medium.
  • the PMA layer 480 defines the specifications for one or more of serialization and deserialization and byte alignment.
  • the PCS layer 470 and PMA layer 480 may define how the plurality of serializers 255 process and communicate data.
  • the PMD layer 490 defines the logical and electrical specifications for using the physical coupling medium, for example single or double data rate signals, or LVDS or PCML (Pseudo Current Mode Logic) transceivers.
  • the coupling medium 225 comprises a cable that complies with the DisplayPort standard defined by the Video Electronics Standards Association (VESA).
  • VESA Video Electronics Standards Association
  • the cable is adapted for use as the coupling medium 225 described in the examples, the digital data and/or electrical format of the signals being communicated need not comply with the standard uses for video data according to VESA.
  • up to 10 Gbps may be transported to the printbar by the coupling medium using four 2.5 Gbps differential uplink data channels.
  • a downlink data channel may also be configured to transmit a data stream at 2.5 Gbps from the printbar to the control system.
  • the coupling medium may comprise, amongst others, a copper cable or one or more optical links.
  • the coupling medium that is used may be selected depending on one or more of the performance, dimensions and cost constraints of the printing device.
  • Optical links have an advantage of offering higher data rates.
  • QSFP Quad Small Form-factor Pluggable
  • a signal conditioner may be used for copper cabling.
  • Coupling media that enable data rates of Gbps and above are referred to herein as high-speed media.
  • the data streams transmitted over the coupling media are effectively a form of serialized data that is deserialized at the printbar (in addition to the serialization of serializes 255 ).
  • the coupling medium may be simplex, half-duplex or duplex.
  • FIG. 5 shows two portions 500 and 550 of a method for communicating data in a printing device.
  • Portion 500 comprises a number of blocks for sending data from a control system to a plurality of printhead modules. The blocks within portion 500 are performed within the control system, which may be control system 105 or 205 .
  • print data and packet-based control data is received.
  • the print data may comprise image 115
  • halftone data 215 and block 510 may comprise an additional sub-block of converting said data 115 and 215 into a plurality of print data signals 222 .
  • print data and packet-based control data is encodes as one or more data streams with a deterministic latency.
  • the encoded data streams are transmitted. This may be performed by a dedicated transmitter or a transceiver such as the first transceiver 214 .
  • block 540 represents the communication of the one or more data streams over a coupling medium.
  • the method then continues to portion 550 which represented blocks for receiving data from a control system for distribution to one or more printhead modules. Portion 550 may be performed at one or more printbars in a printing system.
  • the encoded data streams are received, for example by a dedicated receiver or a transceiver such as the second transceiver 244 .
  • the received data streams are decoded. This may be performed by one or more of the second link layer component 242 , the second packet-based control component 246 and the third packet-based control component 248 depending on the implementation. Decoding the received data streams comprises extracting packet-based control data and print data.
  • the print data and packet-based control data are distributed (e.g. sent) to appropriate control circuitry associated with the printhead modules.
  • the packet-based control data may be sent to a repeater for distribution to one or more printhead modules in an appropriate form. This may involve serializing print data and control data for distribution to one or more printhead modules.
  • the printhead modules may comprise printhead controllers for controlling one or more printheads according to the print data and control data.
  • FIG. 6 shows two portions 600 and 650 of a method for communicating data in a printing device.
  • Portion 600 comprises a number of blocks for sending data to a control system from a plurality of printhead modules.
  • the blocks within portion 600 may be performed within a printbar such as printbars 135 or 235 , or within any other suitable mounting for one or more printhead modules such as a carriage.
  • an indication of a status of one or more printhead modules is received.
  • a status may relate to, amongst others, printhead communication errors, temperature & voltage information, etc. This may comprise receiving control data from one or more printhead controllers over signal lines such status signal lines 260 .
  • the indication of a status is encoded as one or more data streams.
  • the third packet-based control component 248 may receive status data from one or more printhead controllers and forward this status data in an appropriate form to the second link-layer component 242 for encoding.
  • the encoded data streams are transmitted. This may be performed by a dedicated transmitter or a transceiver such as the second transceiver 242 .
  • block 640 represents the communication of the one or more data streams over a coupling medium.
  • the method then continues to portion 650 which represented blocks for receiving data at a control system from one or more printhead modules.
  • Portion 650 may be performed at control system 105 or 205 .
  • the encoded data streams are received, for example by a dedicated receiver or a transceiver such as the first transceiver 214 .
  • the received data streams are decoded. This may be performed by one or more of the first link layer component 212 and the first packet-based control component 216 , for example the first link layer component 212 may extract packet-based control data 226 that is forwarded to the packet-based control component 216 for analysis and processing at block 680 .

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Mathematical Physics (AREA)
  • Accessory Devices And Overall Control Thereof (AREA)
US14/413,933 2012-07-12 2012-07-12 Data communication in a printing device Expired - Fee Related US9269029B2 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2012/063745 WO2014008944A1 (en) 2012-07-12 2012-07-12 Data communication in a printing device

Publications (2)

Publication Number Publication Date
US20150206037A1 US20150206037A1 (en) 2015-07-23
US9269029B2 true US9269029B2 (en) 2016-02-23

Family

ID=46639988

Family Applications (1)

Application Number Title Priority Date Filing Date
US14/413,933 Expired - Fee Related US9269029B2 (en) 2012-07-12 2012-07-12 Data communication in a printing device

Country Status (4)

Country Link
US (1) US9269029B2 (zh)
EP (1) EP2873029B1 (zh)
CN (1) CN104704512B (zh)
WO (1) WO2014008944A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10853004B2 (en) 2017-04-20 2020-12-01 Hewlett-Packard Development Company, L.P. Calibrating communication lines
US11260653B2 (en) 2017-01-20 2022-03-01 Hewlett-Packard Development Company, L.P. Configuring communication interfaces of fluid ejection devices

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014008944A1 (en) 2012-07-12 2014-01-16 Hewlett-Packard Development Company L.P. Data communication in a printing device
WO2016068898A1 (en) 2014-10-29 2016-05-06 Hewlett-Packard Development Company, L.P. Printhead data error detection and response
WO2021216065A1 (en) * 2020-04-22 2021-10-28 Hewlett-Packard Development Company, L.P. Fluidic die data transmission modes

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6585339B2 (en) 2001-01-05 2003-07-01 Hewlett Packard Co Module manager for wide-array inkjet printhead assembly
WO2004088577A1 (en) 2003-04-01 2004-10-14 Willett International Limited Print head control device and method
US6866367B2 (en) 2002-12-20 2005-03-15 Eastman Kodak Company Ink jet printing system using a fiber optic data link
US7887156B2 (en) 2005-04-25 2011-02-15 Ulvac, Inc. Integral printhead assembly
US20110122184A1 (en) 2009-11-24 2011-05-26 Ricoh Company, Ltd. Image forming apparatus, image formation method, and computer-readable medium
US7978372B2 (en) 2000-06-30 2011-07-12 Silverbrook Research Pty Ltd Printhead driven by multiple print engine controllers
WO2011098345A2 (en) 2010-02-11 2011-08-18 Markem-Imaje Industrial inkjet printer with digital communications
US20120050785A1 (en) * 2010-08-24 2012-03-01 Paul Rudolph Printing system control using multiple metadata packets
WO2014008944A1 (en) 2012-07-12 2014-01-16 Hewlett-Packard Development Company L.P. Data communication in a printing device

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7978372B2 (en) 2000-06-30 2011-07-12 Silverbrook Research Pty Ltd Printhead driven by multiple print engine controllers
US6585339B2 (en) 2001-01-05 2003-07-01 Hewlett Packard Co Module manager for wide-array inkjet printhead assembly
US6866367B2 (en) 2002-12-20 2005-03-15 Eastman Kodak Company Ink jet printing system using a fiber optic data link
WO2004088577A1 (en) 2003-04-01 2004-10-14 Willett International Limited Print head control device and method
US7887156B2 (en) 2005-04-25 2011-02-15 Ulvac, Inc. Integral printhead assembly
US20110122184A1 (en) 2009-11-24 2011-05-26 Ricoh Company, Ltd. Image forming apparatus, image formation method, and computer-readable medium
WO2011098345A2 (en) 2010-02-11 2011-08-18 Markem-Imaje Industrial inkjet printer with digital communications
US20120050785A1 (en) * 2010-08-24 2012-03-01 Paul Rudolph Printing system control using multiple metadata packets
WO2014008944A1 (en) 2012-07-12 2014-01-16 Hewlett-Packard Development Company L.P. Data communication in a printing device

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
International Search Report and Written Opinion for PCT/EP2012/063745 dated Apr. 18, 2013, 12 pp.
Iwazawa, N. et al., "Printhead carriage transport high speed control system with robust compensator", Proceedings of the IECON '93, Nov. 15-19, 1993, pp. 2126-2131.

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11260653B2 (en) 2017-01-20 2022-03-01 Hewlett-Packard Development Company, L.P. Configuring communication interfaces of fluid ejection devices
US10853004B2 (en) 2017-04-20 2020-12-01 Hewlett-Packard Development Company, L.P. Calibrating communication lines

Also Published As

Publication number Publication date
EP2873029B1 (en) 2019-08-28
CN104704512A (zh) 2015-06-10
EP2873029A1 (en) 2015-05-20
WO2014008944A1 (en) 2014-01-16
CN104704512B (zh) 2017-06-13
US20150206037A1 (en) 2015-07-23

Similar Documents

Publication Publication Date Title
US9269029B2 (en) Data communication in a printing device
JP5340343B2 (ja) プリント装置用通信プロトコル
CN113875210B (zh) 串行链接装置之间的选定转发
KR101187389B1 (ko) 프린트 헤드들의 특성들에 대한 이미지 데이터 패킷들의 조절
US20100272102A1 (en) System and method for packet messaging and synchronization
US11269316B2 (en) Intelligent controller and sensor network bus, system and method including smart compliant actuator module
US8649398B2 (en) Packet network interface apparatus and method
WO1998021044A1 (en) System and method for synchronizing clock sources driving piezoelectric crystals of ink jet printheads
WO2009067886A1 (fr) Procédé et dispositif pour émettre et recevoir un surdébit oam d'une couche physique ethernet
US10965728B2 (en) Method and system for aggregating and converting sensor data streams
US11171804B2 (en) Common bus data flow for serially chained devices
CN102804653A (zh) 可变比特率设备
CN118614043A (zh) 通过以太网的传感器数据的直接封装
US20140098742A1 (en) Up-Converter for Ethernet Physical Layer
CN110166341B (zh) 一种服务器、服务器集群及通信方法
CN111152580A (zh) 一种多喷头扫描式喷墨打印机检测信号传输方法
KR20130003614A (ko) 다중 레인 기반 이더넷 장치 및 이더넷 장치의 레인 운용방법
Narapureddy et al. Design and implementation of fiber channel based high speed serial transmitter for data protocol on FPGA
JP3871177B2 (ja) データ通信装置およびデータ通信方法
CN113853835B (zh) 串行链接的装置之间的选定模式信号转发
Popov et al. USB 3.0 Based Heterogeneous Data High-Speed Transfer Subsystem
Popov et al. Method for high-speed fiber optic data transfer channel development using Spartan-6 transceivers
CN118870650A (zh) 串行链接的装置之间的选定模式信号转发
JP2008260239A (ja) 画像形成装置
JPH06216907A (ja) 記録装置

Legal Events

Date Code Title Description
AS Assignment

Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P., TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD ESPANOLA SL;REEL/FRAME:036505/0578

Effective date: 20150907

ZAAA Notice of allowance and fees due

Free format text: ORIGINAL CODE: NOA

ZAAB Notice of allowance mailed

Free format text: ORIGINAL CODE: MN/=.

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20240223