WO2021061122A1

WO2021061122A1 - Developer roller authentication

Info

Publication number: WO2021061122A1
Application number: PCT/US2019/052986
Authority: WO
Inventors: Roman KATZ; Niv Shemtov; Arie Livshin; Gilles Chriqui
Original assignee: Hewlett-Packard Development Company, L.P.
Priority date: 2019-09-25
Filing date: 2019-09-25
Publication date: 2021-04-01

Abstract

In one example of the disclosure, a print fluid developer assembly includes a housing with a receiving element for receiving installation of a developer roller. The developer roller is for providing print fluid to a photoconductive member at a printer. The print fluid developer assembly includes a NFC reader to enable wireless and contactless reading of authentication data stored at a NFC data storage component included within the installed developer roller.

Description

DEVELOPER ROLLER AUTHENTICATION BACKGROUND

[0001] A printer may apply print agents to a paper or another print substrate. One example of a printer is a liquid electro-photographic (“LEP”) printer, which may be used to print using an electrostatic printing fluid. Such electrostatic printing fluid includes electrostatically charged or chargeable particles (for example, resin or toner particles which may be colorant particles) dispersed or suspended in a carrier fluid).

DRAWINGS

[0002] F!G. 1 is a block diagram depicting an example of a system for developer roller authentication at a LEP printer.

[0003] FIG. 2 is a block diagram depicting another example of a system for developer roller authentication at a LEP printer.

[0004] FIG. 3 is a block diagram depicting another example of a system for developer roller authentication at a LEP printer.

[0005] FIG. 4 is a block diagram depicting a memory resource and a processing resource to implement an example of a method for developer roller authentication. [0006] FIGS. 5A-5E are perspective views illustrating an example of a system for developer roller authentication at a LEP printer.

[0007] FIG. 6 is a simple schematic diagram that illustrates an example of a system for developer roller authentication at a LEP printer.

[0008] FIG. 7 is a schematic diagram showing a cross section of an example LEP printer implementing a system for developer roller authentication at a LEP printer. [0009] FIG. 8 is a flow diagram depicting implementation of an example of a method for developer roller authentication. DETAILED DESCRIPTION

[0010] in an example of LEP printing, a printer system may form an image on a print substrate by placing an electrostatic charge on a photoconductive element, and then utilizing a laser scanning unit to apply an electrostatic pattern of the desired image on the photoconductive element to selectively discharge the photoconductive element. The selective discharging forms a latent electrostatic image on the photoconductive element. The printer system includes a developer assembly to develop the latent image into a visible image by applying a thin layer of electrostatic print fluid (which may be generally referred to as “LEP print fluid”, or “electronic print fluid”, “LEP ink”, or “electronic ink” in some examples) to the patterned photoconductive element. Charged particles (sometimes referred to herein as “print fluid particles” or “colorant particles”) in the LEP print fluid adhere to the electrostatic pattern on the photoconductive element to form a print fluid image. In examples, the print fluid image, including colorant particles and carrier fluid, is transferred utilizing a combination of heat and pressure from the photoconductive element to a blanket attached to a rotatable blanket drum. The blanket is heated until carrier fluid evaporates and colorant particles melt, and a resulting molten film representative of the image is then applied to the surface of the print substrate via pressure and tackiness. In examples the blanket that is attached to the blanket drum is a consumable or replaceable blanket.

[0011] For printing with colored print fluids the printer system may include a separate print fluid developer assembly (referred to herein as a “developer assembly) for each of the various colored print fluids. There are typically two process methods for transferring a colored image from the photoreceptor to the substrate. One method is a multi-shot process method in which the process described in the preceding paragraph is repeated a distinct printing separation for each color, and each color is transferred sequentially in distinct passes from the blanket to the substrate until a full image is achieved. With multi-shot printing, for each separation a molten film (with one color) is applied to the surface of the print substrate. A second method is a one-shot process in which multiple color separations are acquired on the blanket via multiple applications (each with one color) from the photoconductive element to the blanket, and then the acquired color separations are transferred in one pass as a molten film from the blanket to the substrate.

[0012] The developer assemblies described in the preceding paragraph typically includes a housing with a set of electrodes to charge the electrostatic print fluid, and a consumable development roller to apply the charged print fluid to the blanket. In order to ensure proper operation of the developer unit it is important to be able to verify that the correct consumable developer roller is being installed. Existing developer roller installation verification methods, such as a user comparing a development roller serial number to a list, or a user utilizing a handheld optica! scanner to scan a bar code label at the developer roller or developer roller packaging, require user invention and manual effort. Accordingly, users in some situations may be inclined to install a developer roller at a developer assembly without taking the verification steps. If an incorrect developer roller is installed poor print quality and damage to the printer can be the result. To address these issues, various examples described in more detail below provide a new system and a method that enable automated authentication of developer roller installation at a print developer assembly.

[0013] In certain examples, a developer assembly system includes a receiving element for receiving installation of a developer roller. The received developer roller is for providing print fluid to a photoconductive member at a printer. The system includes a NFC reader to enable wireless and contactless reading of authentication data stored at a NFC data storage component included within the installed developer roller. In examples, the authentication data is indicative of prior usage of the developer roller at this developer assembly. In other examples, the authentication data is indicative of prior usage of the developer roller at another developer (at the same printer, or a different printer). In examples, the authentication data may be indicative of a count of service rotations of the developer roller. In an example, the NFC data storage component is affixed to an end of the developer roller to be installed at the housing. In example, the end of the developer roller includes a rotatable gear assembly with a circular plane surface, and wherein the NFC data storage component is in the shape of a disc and is affixed to the circular planed surface. In an example, the data read from the NFC storage component by the NFC reader is to be transmitted to a printer controller for authentication of the installed developer roller. In an example the NFC data storage component at the developer roller is to include a flash memory, and the NFC reader is a NFC reader/writer to enable wireless and contactless writing of data to the NFC data storage component, the data indicative of usage of the developer roller at the developer assembly and/or a count of service rotations of the developer roller at the developer assembly. In examples the developer assembly includes an electronic connector that is in wired electronic communication with each of the housing, the NFC reader, a printer controller, and a power supply. The electronic connector is for transmitting read authentication data to the printer controller for authentication of the installed developer roller.

[0014] In this manner the disclosed system and method enable automatic authentication of developer rollers installed at a printer assembly. Users of LEP printing systems will appreciate the elimination of the user task of manual verification of developer roller suitability for a developer assembly, and the avoidance of print quality issues and equipment damage that often result from improper development roller installations. Customer satisfaction with LEP printers utilizing the disclosed system and method will be increased, such that installations and utilization of such printers will thereby be enhanced.

[0015] F!G. 1 is a block diagram depicting an example of a system 100 for developer roller authentication at a LEP printer. Developer roller authentication system 100 includes a print fluid developer assembly 102 having a housing 104. In examples, the housing 104 of developer assembly 102 includes a receiving element 106 for receiving installation of the developer roller at the developer assembly.

[0016] As used herein, “print fluid developer assembly” or “developer assembly” refers generally to an apparatus that prepares a thin film of electrically charged ink and carrier fluid to a development roller surface. As used herein, “developer roller” refers generally to a roller of the developer assembly that directly engages with a photoconductor to apply, through a combination of electrical and mechanical forces, the charged print fluid to the photoconductor. In an example, the combination of electrical fields applied to the photoconductor and within the developer unit result in attracting an ink paste to image areas of the photoconductor, and repelling ink paste from non-image areas. The result is replication of the electrical latent image that was formed upon the photoconductor with an inked image. As used herein, an “ink” refers generally to any fluid that is to be applied to a substrate during a printing operation to form an image upon the substrate. In examples inks may be, or include, aqueous inks, solvent inks, UV-curab!e inks, dye sublimation inks, latex inks, liquid electro-photographic inks, liquid or solid toners, or powders. As used herein, the term “print fluid” refers generally to any material or substance with fluid properties that can be applied upon a substrate by a printer during a printing operation, including but not limited to inks, primers, and overprint materials (such as a varnish). In certain examples, the photoconductor may engage with an intermediate transfer member (hereinafter referred to as a “blanket”), which blanket in turn engages with a substrate to convey the developed (sometimes referred to as “inked”) image to the substrate to form a printed image. In other examples, the photoconductor may engage directly with a substrate to form a printed image. In certain examples, the photoconductor may be attached to a rotatably mounted drum and the blanket may be attached to another rotatably mounted drum, wherein the drums are arranged such that the photoconductor and the blanket each are to rotate and are to about one another during the rotations. As used herein a “receiving element” refers generally to any combination of hardware and programming that is to accept a consumable developer roller at a developer assembly. In examples, the receiving element may Include a set of alignment features or fiducials. In examples, the receiving element may include a locking mechanism for securely installing the developer roller.

[0017] Continuing at FIG. 1, developer assembly 102 includes a NFC reader 108 to enable wireless and contactless reading of authentication data stored at a NFC data storage component included within the installed developer roller. As used herein, “NFC reader” refers generally to a near field communication or other short-range wireless technology that enables communication between electronic devices. In examples the communication range of NFC may be between 1 and 10 centimeters, so as to provide accuracy and security by only allowing devices to communicate within close proximity of each other. In examples NFC reader 108 may include an antennae to enable wireless and contactless reading of data stored at the NFC data storage component.

[0018] Moving to FIG. 2, in an example developer assembly 102 includes a BUS connector 202 or other electronic connector that is in a wired electronic communication with each of housing 104, NFC reader 108, a controller for the printer that includes developer assembly 102, and a power supply. As used herein, “BUS connector” refers generally to an electronic connector to a network topology or circuit arrangement in which a set of electronic components or devices are attached to a line directly and ail signals pass through each of the devices. Each component or device has a unique identity and can recognize those signals intended for it. !n certain examples BUS connector 202 may connect to a One-Wire circuit arrangement that connects NFC reader 108 and other components such as a temperature sensor, a humidity sensor, a data storage device, or a circuit board to the printer controller and power supply. As used herein, a “controller” refers generally to a combination of hardware and programming that is to control part, or all, of the components and print process at a printer. In examples of this disclosure, the controller may control system 100 for developer roller authentication at a printer, including controlling, e.g. via BUS connector 202, NFC reader 108.

[0019] In certain examples, the NFC data storage component that is to be detected by NFC reader 108 is a NFC data storage component affixed to an end of the developer roller being installed at the printer. In a particular example, the end of the installed developer roller includes a rotatable gear assembly with a circular plane surface, and the NFC data storage component at the developer roller is a component in the shape of a disc or plate in this particular example the developer roller’s disc or plate-shaped NFC data storage component is affixed to the circular planed surface of the rotatable gear assembly, so as to be situated at a distance between 1 and 10 centimeters to NFC reader 108.

[0020] Continuing at FIG 2, in an example the authentication data read by the NFC reader 108 from the NFC data storage component is data indicative of a serial number or an authentication code for the installed developer roller. As used herein, “authentication code” refers generally to something, e.g., any text, number, character string, image, graphic, or other element, that identifies an object, e.g. a developer roller. The printer controller may access a look up table or database in electronic connection with the controller to compare the read serial number or authentication code with a list of expected or authorized codes for developer rollers, and determine authentication of the development roller for use with developer assembly 102 if there is match in serial numbers or authentication codes.

[0021] In examples, the authentication data, indicative of prior usage of the developer roller, read by NFC read 108 from the NFC data storage component at the developer roller may include a count of service rotations of the developer roller developer assembly 102. In another example, the read authentication data may include a count of service rotations of the developer roller at a developer assembly other than developer assembly 102. !n yet another example, the read authentication data may include a count of service rotations of the developer roller at a developer assemblies installed at a subject printer.

[0022] In an example, a recognition by the printer controller that the developer roller was previously utilized at developer assembly 102 may be determined as an acceptable prior use, such that the developer roller can be reinstalled at developer assembly 102. In a different example, recognition by the printer controiler that the developer roller was utilized at developer assembly 102 could be determined as an unacceptable prior use, e.g. a reuse of developer roller that would be detrimental to print quality or operation of the printer that includes developer assembly 102, such that the developer roller can be reinstalled at developer assembly 102 [0023] In an example, a recognition by the printer controller that the developer roller was utilized at a developer assembly other than developer assembly 102 might be determined as an acceptable prior use (e.g. a prior use of the developer roller in a developer assembly other than developer assembly 102 at the same printer), such that the developer roller is deemed authorized and can be installed at developer assembly 102.

[0024] In another example, a recognition by the printer controller that the developer roller was utilized at a developer assembly other than developer assembly 102 might be determined as an unacceptable prior use (e.g. a use at a developer assembly other than developer assembly 102 at a printer other than the subject printer where developer assembly 102 is Installed), such that the developer roller cannot be installed at developer assembly 102. In this example, the developer roller may be deemed unauthorized as the prior use situation suggests the developer roller is likely an aftermarket reworking of a previously authorized consumable).

[0025] Continuing at FIG. 2, in a particular example, the NFC data storage component that is affixed to an end of the developer roller being installed at the developer assembly includes a flash memory. In an example, NFC reader 108 is a NFC reader/writer, and is to enable wireless and contactless writing of data to the NFC data storage component. As used herein, a “NFC reader/writer” refers generally to a NFC reader that is capable of not only reading data from, but also sending data to, a NFC data storage component for writing or storage at the NFC data storage component. In an example, a reader/writer NFC reader 108 may include an antennae to enable wireless and contactless reading of data stored at the MFC data storage component and writing of data to the NFC data storage component.

[0026] In an example, NFC reader 108 is a reader/writer NFC, and is to enable wireless and contactless writing of data to the NFC data storage component at the end of the developer roller installed at the developer assembly 102. In an example, the data written to the NFC data storage component at the installed developer roller may be data indicative of an installation or usage of the developer roller at developer assembly 102. In another example, the data written to the NFC data storage component at the Installed developer roller may be data indicative of a count of service rotations of the developer roller at developer assembly 102. As used herein, a “service rotation” generally refers to a rotation of a developer roller installed at a developer assembly during a printing operation. In an example, the service rotation of the developer roller may be a service rotation to accomplish transfer print fluid from housing 104, via the developer roller, to a photoconductor at the printer.

[0027] FIG. 3 is a block diagram depicting another example of a system for developer roller authentication at a LEP printer. In FIG. 3 various components are identified as engines 302, 304, and 306. in describing engines 302-306 focus is on each engine’s designated function. However, the term engine, as used herein, refers generally to hardware and/or programming to perform a designated function. As is illustrated with respect to FIG. 4, the hardware of each engine, for example, may include one or both of a processor and a memory, while the programming may be code stored on that memory and executable by the processor to perform the designated function.

[0028] In the example of FIG.3, system for development roller authentication 100 includes developer assembly 102, a developer roller receipt engine 302, a data read engine 304, and a developer roller authentication engine 306. !n performing their respective functions, engines 302-306 may access a data repository, e.g., a memory accessible to fluid developer assembly 102 that can be used to store and retrieve data.

[0029] In an example, developer roller receipt engine 302 represents generally a combination of hardware and programming to receive a developer roller at a receiving element 106 of a developer assembly 102. The received developer roller includes a NFC data storage component.; [0030] Data read engine 304 represents generally a combination of hardware and programming to utilize a NFC reader 108 that is positioned in or included within developer assembly 102 to cause a wireless and contactless reading of authentication data stored at the developer roller’s NFC data storage component. In examples, the authentication data may include a serial number, an authentication code, or another identifier for the developer roller.

[0031] Development roller authentication engine 306 represents generally a combination of hardware and programming to transmit the read authentication data to a printer controller for authentication of the installed developer roller.

[0032] In an example, the developer roller’s NFC data storage component includes a flash memory, and the read authentication data includes a number of installations of the developer roller at a printer, a number of service rotations of the developer roller at a printer !n particular examples, the NFC reader 108 that data read engine 304 utilizes to cause a wireless and contactless reading of authentication data stored at the developer roller’s NFC data storage component is a NFC reader/writer, and the NFC reader/writer is to wirelessly and without physical contact with the NFC data storage component write authentication data to the NFC data storage component. In particular examples, the NFC reader/writer is to write to the NFC data storage component authentication data that provides details of or otherwise indicates usage of the developer roller at developer assembly 102. In an example, the details may be a count of service rotations of the subject developer roller at developer assembly 102. In certain examples, the count of service rotations may be, or may be derived from, a count of pages printed with the subject developer roller. In other examples, the count of service rotations may be, or may be derived from, a count of actual rotations of the subject developer roller made utilizing an encoder at developer assembly 102.

[0033] In the foregoing discussion of FIG. 3, engines 302-306 were described as combinations of hardware and programming. Engines 302-306 may be implemented in a number of fashions. Looking at FIG. 4 the programming may be processor executable instructions stored on a tangible memory resource 430 and the hardware may include a processing resource 440 for executing those instructions. Thus, memory resource 430 can be said to store program instructions that when executed by processing resource 440 implement system 100 of FIG. 3. [0034] Memory resource 430 represents generally any number of memory components capable of storing instructions that can be executed by processing resource 440. Memory resource 430 is non-transitory in the sense that it does not encompass a transitory signal but instead is made up of a memory component or memory components to store the relevant instructions. Memory resource 430 may be implemented in a single device or distributed across devices. Likewise, processing resource 440 represents any number of processors capable of executing instructions stored by memory resource 430. Processing resource 440 may be integrated in a single device or distributed across devices. Further, memory resource 430 may be fully or partially integrated in the same device as processing resource 440, or it may be separate but accessible to that device and processing resource 440.

[0035] In one example, the program instructions can be part of an installation package that when installed can be executed by processing resource 440 to implement system 100. In this case, memory resource 430 may be a portable medium such as a CD, DVD, or flash drive or a memory maintained by a server from which the installation package can be downloaded and installed. In another example, the program instructions may be part of an application or applications already installed. Here, memory resource 430 can include integrated memory such as a hard drive, solid state drive, or the like.

[0036] In FIG. 4, the executable program instructions stored in memory resource 430 are depicted as developer roller receipt module 402, data read module 404, and development roller authentication module 406. Developer roller receipt module 402 represents program instructions that when executed by processing resource 440 may perform any of the functionalities described above in relation to developer roller receipt engine 302 of FIG. 3. Data read module 404 represents program instructions that when executed by processing resource 440 may perform any of the functionalities described above in relation to data read engine 304 of FIG. 3. Development roller authentication module 406 represents program instructions that when executed by processing resource 440 may perform any of the functionalities described above in relation to development roller authentication engine 306 of FIG.

3.

[0037] FIGS. 5A-5E are perspective views illustrating an example of a system for developer roller authentication at a LEP printer. In the example of FIGS. 5A-5E, a developer roller authentication system 100 includes a print fluid developer assembly 102 having a housing 104. In examples, the housing 104 of developer assembly 102 includes a receiving element 106 for receiving installation of a developer roller 502 at developer assembly 102. In this example receiving element includes a seating element 106a for positioning and holding the developer roller and locking mechanisms 106b for securing developer roller 502 in seating element 106a.

[0038] Developer assembly 102 includes a NFC reader 108 to enable wireless and contactless reading of authentication data stored at a NFC data storage component 504 included an installed developer roller 502. In examples the communication range between NFC reader 108 at developer assembly 102 and NFC data storage component at developer roller 502 may be between 1 and 10 centimeters so as to provide accuracy and security by only allowing devices to communicate within close proximity of each other.

[0039] Continuing at FIGS. 5A-5E, in this example developer assembly 102 includes a BUS connector 202 that is in a wired electronic communication with each of housing 104, NFC reader 108, a controller for the printer that includes developer assembly 102, and a power supply in an example, BUS connector 202 connects to a BUS circuit arrangement In which a set of electronic components or devices, including NFC reader 108, are attached to a line directly and ail signals pass through each of the devices. In an example, each component or device, including NFC reader 108, has a unique identity and can recognize those signals intended for it. In certain examples BUS connector 202 may be a connection to a One-Wire circuit arrangement that connects NFC reader 108 and other components to a printer controller and a power supply at the printer where developer assembly 102 is installed. In an example, such other components may include NFC readers at developer assemblies other than developer assembly 102 at the printer. In another example, these such other components may be components other than NFC readers, e.g.. a temperature sensor, humidity sensor, data storage device, and/or circuit board.

[0040] The controller (not depicted in FIGS 5A-5E,) for the printer that includes developer assembly 102 may control system 100 for developer roller authentication and other systems, including print operation systems, at the printer. In an example, the power supply (not depicted at FIGS. 5A-5E) may provide low level power (e.g., between 3 volts and 6 volts) to the NFC reader 108 at developer assembly 102 to enable reading of data from NFC data storage components of a developer roller installed at developer assembly 102, and from other NFC readers installed at other developer assemblies installed at the printer where developer assembly 102 in installed.

[0041] In the example of FIGS. 5A-5E, NFC data storage component 504 that is to be detected by NFC reader 108 is a NFC data storage component affixed to an end 506 of the developer roller 502. In this example developer roller 502 is to be installed at receiving element 106 of developer assembly 102. In a particular example, the end 506 of the installed developer roller includes a rotatable gear assembly 508 with a circular plane surface 510. The NFC data storage component 504 at developer roller 502 is a component in the shape of a disc or plate. In the example of FIGS. 5A-5E, the developer roller’s disc or plate-shaped NFC data storage component 504 is affixed to the circular planed surface 510 of the rotatable gear assembly, so as to be situated at a distance between 1 and 10 centimeters to the NFC reader 108 at developer assembly 102 when installed.

[0042] Continuing at FIGS. 5A-5E, authentication data read by NFC reader 108 from the NFC data storage component at the end 506 of the installed developer roller 502 is transmitted, via BUS connector 202, along a BUS to the printer controller for authentication of the installed developer roller. In an example, the authentication data read by the NFC reader 108 from the NFC data storage component is data indicative of a serial number or an authentication code for the installed developer roller 502. The printer controller may access a look up table or database in electronic connection with the controller to compare the read serial number or authentication code with a list of expected or authorized codes for developer rollers. The printer controller may in turn determine authentication of the development roller for use with developer assembly 102 if there is match in serial numbers or authentication codes.

[0043] In examples, the authentication data, indicative of prior usage of developer roller 502, read by NFC reader 108 from the NFC data storage component 504 at developer roller 502 may include a count of service rotations of developer roller 502 at this developer assembly 102. In another example, the read authentication data may include a count of service rotations of the developer roller at developer assembly 102. In another example, the read authentication data may include a count of service rotations of developer roller 502 at a developer assembly other than depicted developer assembly 102. In yet another example, the read authentication data may include a count of service rotations of developer roller 502 at another developer assembly installed at the same printer as to which developer assembly 102 installed.

[0044] Continuing at FIGS. 5A-5E, in a particular example, the NFC data storage component 504 that is affixed to end 508 of the developer roller 502 includes a flash memory. In this example, NFC reader 108 is a NFC reader/writer, and is to enable wireless and contactless writing of data to NFC data storage component 504. In an example, the data written to the NFC data storage component 504 may be data indicative of an installation or usage of the developer roller 502 at developer assembly 102. In another example, the data written to the NFC data storage component at the installed developer roller may be data indicative of a count of service rotations of the developer roller 502 at developer assembly 102. In an example, the counted service rotations of developer roller 502 may be service rotations to accomplish transfer print fluid from housing 104 at developer assembly 102, via the developer roller 502, to a photoconductor at the printer to produce a printed image upon a substrate.

[0045] F!G. 6 is a simple schematic diagram that illustrates an example of a system 100 for developer roller authentication at a LEP printer. In this example, system 100 includes device D1 temperature sensor 604, device D2 humidity sensor 606, device D3 data storage device 608, device D4 circuit board 610, and device D5 developer assembly 102. System 100 includes a BUS 602 that enables an inline wired electronic communication with each of devices D1-D5, a printer controller 614, and a power supply 616. In an example, each of devices D1-D5 has a unique identity and can recognize those signals intended for it. In an example, printer controller 614 may control ail or part of operations of devices D1-D5, including a system 100 for developer roller authentication at D5 developer assembly 102. In an example, printer controller 614 may control part, or all, of other components and operations at printer 600, including, but not limited to, operations of power supply 616, a photoconductor 618, a media transport system, and calibration systems.

[0046] Looking at developer assembly D5 102 at FIG. 6, in an example a NFC data storage component 504 that is to be detected by NFC reader 108 is a NFC data storage component affixed to an end of a developer roller 502 being installed at the printer. In this example, an end of the installed developer roller 502 includes a rotatable gear assembly with a circular plane surface 510, and the NFC data storage component 504 at the developer roller is in the shape of a disc. In this example the disc-shaped NFC data storage component 504 is affixed to the circular planed surface 510 of the rotatable gear assembly 508 of developer roller 502, so as to be situated at a distance between 1 and 10 centimeters to NFC reader 108. In an example, the data read by NFC reader 108 from the NFC data storage component 504 at end of the installed developer roller 502 is transmitted, via BUS 202, to the printer controller 814 for authentication of the installed developer roller 502.

[0047] FIG. 7 is a schematic diagram showing a cross section of an example LEP printer 700 implementing a system for developer roller authentication at a LEP printer, according to an example of the principles described herein. Along with the elements previously described herein in connection with a system for developer roller authentication 100, the LEP printer 700 may include a photoconductor 618, a charging element 704, an imaging unit 706, a blanket 708, an impression cylinder 710, a discharging element 712, and a cleaning station 714.

[0048] According to the example of FIG. 7, a pattern of electrostatic charge is formed on a photoconductor 618 by rotating a clean, bare segment of the photoconductor 618 under a charging element 704. The photoconductor 618 in this example is cylindrical in shape, e.g. is constructed in the form of a drum, and rotates in a direction of arrow 720. In other examples, a photoconductor may planar or part of a belt-driven system

[0049] Charging element 704 may include a charging device, such as corona wire, a charge roller, scorotron, or any other charging device. A uniform static charge is deposited on the photoconductor 618 by the charging element 704. As the photoconductor 618 continues to rotate, it passes an imaging unit 706 where one or more laser beams dissipate localized charge in selected portions of the photoconductor 618 to leave an invisible electrostatic charge pattern (“latent image”) that corresponds to the image to be printed. In some examples, the charging element 704 applies a negative charge to the surface of the photoconductor 618. In other implementations, the charge is a positive charge. The imaging unit 706 then selectively discharges portions of the photoconductor 618, resulting in local neutralized regions on the photoconductor 618.

[0050] Continuing with the example of FIG. 7, the developer assemblies 102a-1G2e are disposed adjacent to the photoconductor 618 and may correspond to various print fluid colors such as cyan, magenta, yellow, black, and the like. There may be one developer assembly for each print fluid color. In other examples, e.g., black and white printing, a single developer assembly may be included in LEP printer 700. During printing, the appropriate developer assembly is engaged with the photoconductor 618 The engaged developer assembly presents a uniform film of print fluid to the photoconductor 618. The print fluid contains electrically charged pigment particles which are attracted to the opposing charges on the image areas of the photoconductor 618. As a result, the photoconductor 618 has a developed image on its surface, i.e. a pattern of liquid toner corresponding with the electrostatic charge pattern (aiso sometimes referred to as a “separation”).

[0051] The print fluid may be a liquid toner, comprising ink particles and a carrier liquid. The carrier liquid may be an imaging oil. The ink particles may be electrically charged such that they move when subjected to an electric field. Typically, the ink particles are charged such that they are repelled from the similarly charged portions of photoconductor 618, and are attracted to the discharged portions of the photoconductor 618.

[0052] The print fluid is transferred from the photoconductor 618 to an intermediate transfer member blanket 708. The blanket may be in the form of a rotatable drum, belt or other transfer system. In a particular example, the photoconductor 618 and blanket 708 are drums that rotate relative to one another, such that the color separations are transferred during the relative rotation. In the example of FIG. 7, the blanket 708 rotates in the direction of arrow 722. The transfer of a developed image from the photoconductor 618 to the blanket 708 may be known as the “first transfer, which takes place at a point of engagement between the photoconductor 618 and the blanket 708.

[0053] Once the layer of liquid toner has been transferred to the blanket 708, it is next transferred to a print substrate 716. This transfer from the blanket 708 to the print substrate may be deemed the “second transfer”, which takes place at a point of engage between the blanket 708 and the print substrate 716. The impression cylinder 710 can both mechanically compress the print substrate 716 in to contact with the blanket 708 and also help feed the print substrate 716. In examples, the print substrate 716 may be a conductive or a non-conductive print substrate, In the example of FIG. 7 the substrate is a web substrate advancing in a substrate direction 760. In other examples, the substrate may be in sheet form including, but not limited to, paper, cardboard, sheets of metal, metal-coated paper, or metal-coated cardboard.

[0054] In examples after the first transfer of print fluid from the photoconductor 618 to the blanket 708, the portion of the photoconductor that made the transfer continues in the photoconductor rotation direction 720 to encounter a discharging element 712 and a photoconductor cleaning station 714. The discharging element and the photoconductor cleaning station are for preparing the photoconductor for a next printing separation, e.g. the next separation to print a different coior utilizing print fluid delivered to the photoconductor 618 by a different developer assembly.

[0055] In an example, each of a plurality of developer assemblies 102a-1G2e includes a housing 104 with a developer roller receiving element 106, a NFC reader 108, and a BUS connector 202 in a wired electronic communication with each of housing 104, NFC reader 108, a controller 614, and a power supply 616 for the printer 700. Controller 614 is to control all or part of the print process described above with respect to FIG. 7. In this example, controller 614 includes developer receipt engine 302, data read engine 304, and development roller authentication engine 306, for implementation and control of the system 100 and method of development roller authentication described herein. In a particular example, controller 614 is to implement and control development roller authentication upon the installation of a development roller at any of developer assemblies 102a-1Q2e.

[0056] During a developer roller installation and authentication event at one of the developer assemblies 102a-1G2e, power supply 616 is to provide power (e.g., power between 3 volts and 6 volts) to the NFC reader 108 at the applicable developer assembly. The power is to enable reading of data from NFC data storage components of a developer roller installed at the applicable developer assembly. In an example where the NFC readers 108 are read/write readers and the installed developer rollers include a flash memory device, power supply 616 may provide power to the NFC readers at times when a developer roller is not being installed, e.g. providing power to a NFC reader to cause a writing to a NFC data storage component of a development roller of data indicative of a usage of a developer roller at a developer assembly of printer 700 and/or a count of service rotations of a developer roller at a developer assembly of printer 700.

[0057] FIG. 8 is a flow diagram of implementation of a method for development roller authentication at a LEP printer in discussing FIG. 8, reference may be made to the components depicted in FIGS. 1-7. Such reference is made to provide contextual examples and not to limit the way the method depicted by FIG. 8 may be implemented. A developer roller that includes a NFC data storage component is received at a receiving element of the developer assembly (block 802). Referring back to FIGS. 3, 4 and 7, development roller receipt engine 302 (FIGS. 3 and 7) or development roller receipt module 402 (FIG. 4), when executed by processing resource 440, may be responsible for implementing block 802.

[0058] A NFC reader included within the developer assembly is utilized to undertake a wireless and contactless reading of authentication data stored at the NFC data storage component (block 804) Referring back to FIGS 3, 4 and 7, data receipt engine 304 (FIGS. 3 and 7) or data read module 404 (FIG. 4), when executed by processing resource 440, may be responsible for implementing block 804.

[0059] The read authentication data is transmitted to a printer controller for authentication of the installed developer roller (block 806}. Referring back to FIGS.

3, 4 and 7, development roller authentication engine 306 (FIGS. 3 and 7) or development roller authentication module 406 (FIG. 4), when executed by processing resource 440, may be responsible for implementing block 806.

[0060] FIGS. 1-8 aid in depicting the architecture, functionality, and operation of various examples. In particular, FIGS. 1-7 depict various physical and logical components. Various components are defined at least in part as programs or programming. Each such component, portion thereof, or various combinations thereof may represent in whole or in part a module, segment, or portion of code that comprises executable instructions to implement any specified logical function(s).

Each component or various combinations thereof may represent a circuit or a number of interconnected circuits to implement the specified logical function(s). Examples can be realized in a memory resource for use by or in connection with a processing resource. A “processing resource” is an instruction execution system such as a computer/processor based system or an ASIC (Application Specific Integrated Circuit) or other system that can fetch or obtain instructions and data from computer-readable media and execute the instructions contained therein. A “memory resource” is a non-transiiory storage media that can contain, store, or maintain programs and data for use by or in connection with the instruction execution system. The term “non-transiiory” is used only to clarify that the term media, as used herein, does not encompass a signal. Thus, the memory resource can comprise a physical media such as, for example, electronic, magnetic, optical, electromagnetic, or semiconductor media. More specific examples of suitable computer-readable media include, but are not limited to, hard drives, solid state drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash drives, and portable compact discs.

[0081] Although the flow diagram of FIG. 8 shows specific orders of execution, the order of execution may differ from that which is depicted. For example, the order of execution of two or more blocks or arrows may be scrambled relative to the order shown. Also, two or more blocks shown in succession may be executed concurrently or with partial concurrence. Such variations are within the scope of the present disclosure.

[0082] It is appreciated that the previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein AH of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the blocks or stages of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features, blocks and/or stages are mutually exclusive. The terms “first”, “second", “third” and so on in the claims merely distinguish different elements and, unless otherwise stated, are not to be specifically associated with a particular order or particular numbering of elements in the disclosure.

Claims

What is claimed is:

1. A print fluid developer assembly (“developer assembly”), comprising: a housing including a receiving element for receiving installation of a developer roller, the developer roller for providing print fluid to a photoconductive member at a printer; and a MFC reader to enable wireless and contactless reading of authentication data stored at a NFC data storage component included within the installed developer roller.

2. The developer assembly of claim 1 , wherein the authentication data is indicative of at least one from the set of a serial number, and an authentication code for a developer roller.

3. The developer assembly of claim 1 , wherein the developer assembly is a first developer assembly, and wherein the authentication data is indicative of at least one from the set of usage of the developer roller at the first developer assembly, and usage of the developer roller at a developer assembly other than the first developer assembly.

4. The developer assembly of claim 3, wherein the authentication data indicative of usage of the developer roller includes at least one from the set of a count of service rotations of the developer roller at the first developer assembly, a count of service rotations of the developer roller at a developer assembly other than the first developer assembly, and a count of service rotations of the developer roller at a developer assembly installed at the printer.

5. The developer assembly of claim 1 , wherein the NFC data storage component is affixed to an end of the developer roller, and wherein the NFC reader is positioned such that the NFC reader is between 1 and 10 centimeters from the NFC data storage component.

6. The developer assembly of claim 1 , wherein the end of the installed developer roller Includes a rotatable gear assembly with a circular plane surface, and wherein the NFC data storage component is in the shape of a disc and is affixed to the circular planed surface.

7. The developer assembly of claim 1 , wherein the read data is to be transmitted to a printer controller for authentication of the installed developer roller.

8. The developer assembly of claim 1 , wherein the NFC data storage component is to include a flash memory, wherein the NFC reader is a NFC reader/writer, and wherein the NFC reader/writer is to enable wireless and contactless writing of data to the NFC data storage component.

9. The developer assembly of claim 8, wherein the NFC reader/writer and a NFC data storage component are to enable wireless and contactless writing to the NFC data storage component of data indicative of at least one from the set of usage of the developer roller at the developer assembly, and a count of service rotations of the developer roller at the developer assembly.

10. The developer assembly of claim 1 , further comprising an electrical connector that is in a wired electronic communication with each of the housing, the NFC reader, a printer controller, and a power supply.

11.A method for validating developer roller installation at a print developer assembly, comprising: receiving a developer roller at a receiving element of the developer assembly, wherein the developer roller includes a NFC data storage component; utilizing a NFC reader included within the developer assembly to undertake a wireless and contactless reading of authentication data stored at the NFC data storage component; transmiting the read authentication data to a printer controller for authentication of the installed developer roller.

12. The method of claim 11 , wherein the authentication data includes at least one of a serial number and an authentication code for the developer roller.

13. The method of claim 11 , wherein the NFC data storage component is to include a flash memory; and wherein the authentication data includes at least one from the set of a number of installations of the developer roller at a printer and a number of service rotations of the developer roller at a printer.

14. The method of claim 13, wherein the NFC reader is a NFC reader/writer, and wherein the NFC reader/writer is to enable wireless and contactless writing of authentication data to the NFC data storage component, the authentication data indicative of usage of the developer roller at the developer assembly.

15. A printer, comprising: a photo imaging plate; a print fluid developer assembly to apply print fluid to the photo imaging plate the print fluid developer assembly including a housing with a receiving element for receiving installation of a developer roller, the developer roller for providing print fluid to a photoconductive member at a printer, and a NFC reader to enable wireless and contactless reading of authentication data stored at a NFC data storage component included within the installed developer roller, the authentication data including at least one from the set of a serial number for the installed developer roller, an authentication code for the installed developer roller, a number of installations of the installed developer roller, and a number of service rotations of the installed developer roller; a printer controller; and a BUS connector in wired electronic communication with the NFC reader and the printer controller, the BUS connector to enable transmission of the read authentication data to the printer controiler for authentication of the installed developer roller.