Drive waveform proposal system

Abstract

This system provides outputting drive waveform setting data suitable for inkjet heads while minimizing the time and effort required. [Solution] The system according to the embodiment includes a communication unit that communicates with an external terminal via the cloud, and a response unit that creates response information in response to received information from the external terminal received by the communication unit and provides the response information to the external terminal via the communication unit. In response to received information of a register discrimination request that instructs the discrimination of inks to which the same register data, which is determined according to the ink contained in the set value data, can be applied, the response unit, assuming that multiple inkjet heads are of the same model and the operating conditions and ink ejection conditions are the same, discriminates among the multiple inks used by each inkjet head that have similar physical properties, and creates discrimination results as response information indicating that the multiple inks that were discriminated against are inks to which the same register data can be applied.

Description

Technical Field

[0001] Embodiments of the present invention relate to a drive waveform proposal system.

Background Art

[0002] A liquid ejection device having an inkjet head generally forms an image on a printing medium being conveyed by inputting a drive signal to a drive element such as a piezoelectric element of the inkjet head and ejecting a liquid such as ink from a nozzle.

[0003] In order to perform high-quality image formation, it is necessary to obtain a drive waveform suitable for the inkjet head in accordance with the usage conditions of the inkjet head, the physical property information of the ink, etc. so that the ejection characteristics of the ink from the nozzle become desired characteristics.

[0004] Conventionally, a drive waveform suitable for an inkjet head has been obtained by performing ejection observation such as measuring the flight state of ink droplets and print quality while varying the parameters of the drive waveform using the ink actually used.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] This method requires a lot of labor and time for ejection observation using the actual ink and inkjet head.

[0007] In liquid ejection systems that use multiple inks such as YMCK (cyan, magenta, yellow, and black), like color printers, this ejection observation must be performed for each individual inkjet head, which is time-consuming and laborious. Furthermore, in recent years, liquid ejection systems that use around 10 different color inks to improve color reproduction have emerged, and this problem becomes even more pronounced in such systems.

[0008] The problem that this invention aims to solve is to provide a drive waveform suggestion system that outputs setting value data for generating a drive waveform suitable for an inkjet head, while minimizing the time and effort required. [Means for solving the problem]

[0009] The drive waveform suggestion system according to this embodiment is a drive waveform suggestion system that outputs multiple set value data for generating multiple drive waveforms to drive multiple inkjet heads using different inks from each other, and includes a communication unit that communicates with an external terminal that controls a liquid ejection device having multiple inkjet heads via the cloud, and a response unit that creates response information in response to received information from the external terminal received by the communication unit and provides the response information to the external terminal via the communication unit. The set value data includes register data determined according to the ink. In response to received information of a register discrimination request that instructs the discrimination of inks to which the same register data can be applied, the response unit, assuming that the multiple inkjet heads are of the same model and the operating conditions and ink ejection conditions are the same, discriminates among the multiple inks used by the multiple inkjet heads that have similar physical properties, and creates a discrimination result as the response information that the multiple inks determined to have similar physical properties are inks to which the same register data can be applied. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a block diagram showing an example configuration of a liquid dispensing device that operates using setpoint data provided by the drive waveform proposal system according to the first embodiment. [Figure 2] Figure 2 is a block diagram showing a first configuration example of the head controller of the liquid dispensing device shown in Figure 1. [Figure 3] Figure 3 is a block diagram showing a first example configuration of the inkjet head of the liquid ejection device shown in Figure 1. [Figure 4] Figure 4 is a block diagram showing a second configuration example of the head controller of the liquid dispensing device shown in Figure 1. [Figure 5] Figure 5 is a block diagram showing a second example configuration of the inkjet head of the liquid ejection device shown in Figure 1. [Figure 6] Figure 6 is a block diagram showing the functional configuration of the drive waveform proposal system according to the first embodiment. [Figure 7] Figure 7 is a block diagram showing the functional configuration of the authentication server for the drive waveform proposal system shown in Figure 6. [Figure 8] Figure 8 is a block diagram showing the functional configuration of the application server and web API server of the drive waveform proposal system shown in Figure 6. [Figure 9] Figure 9 is a block diagram showing the functional configuration of the database server of the drive waveform proposal system shown in Figure 6. [Figure 10] Figure 10 is a block diagram showing the hardware configuration of the computer that constitutes the drive waveform proposal system shown in Figure 6. [Figure 11] Figure 11 shows the first part of a series of flowcharts illustrating the processing flow from accessing the drive waveform proposal system according to the first embodiment to obtaining the set value data. [Figure 12] Figure 12 shows the second part of a series of flowcharts illustrating the processing flow from accessing the drive waveform proposal system according to the first embodiment to obtaining the set value data. [Figure 13] Figure 13 shows the third part of a series of flowcharts illustrating the processing flow from accessing the drive waveform proposal system according to the first embodiment to obtaining the set value data. [Figure 14]FIG. 14 is a diagram showing an example of a home screen. [Figure 15] FIG. 15 is a diagram showing an example of a waveform proposal screen that accepts input processing of parameters applied to an inkjet head. [Figure 16] FIG. 16 is a diagram showing a first example of a register discrimination condition input screen. [Figure 17] FIG. 17 is a flowchart showing the flow of register discrimination processing corresponding to the register discrimination condition input screen shown in FIG. 16. [Figure 18] FIG. 18 is a diagram showing an example of a discrimination result screen corresponding to the register discrimination condition input screen shown in FIG. 16. [Figure 19] FIG. 19 is a diagram showing a second example of a register discrimination condition input screen. [Figure 20] FIG. 20 is a flowchart showing the flow of register discrimination processing corresponding to the register discrimination condition input screen shown in FIG. 19. [Figure 21] FIG. 21 is a diagram showing an example of a discrimination result screen corresponding to the register discrimination condition input screen shown in FIG. 19. [Figure 22] FIG. 22 is a diagram showing a second part of a series of flowcharts showing the flow of processing from access to the drive waveform proposal system according to the second embodiment to obtaining set value data. [Figure 23] FIG. 23 is a diagram showing a third part of a series of flowcharts showing the flow of processing from access to the drive waveform proposal system according to the second embodiment to obtaining set value data. [Figure 24] FIG. 24 is a diagram showing a fourth part of a series of flowcharts showing the flow of processing from access to the drive waveform proposal system according to the second embodiment to obtaining set value data. [Figure 25] FIG. 25 is a diagram showing a first example of a discrimination result screen in the drive waveform proposal system according to the second embodiment. [Figure 26] FIG. 26 is a diagram showing a second example of a discrimination result screen in the drive waveform proposal system according to the second embodiment. [Modes for carrying out the invention]

[0011] [First Embodiment] The drive waveform suggestion system according to the first embodiment will be described below with reference to the drawings. The drive waveform suggestion system receives parameters related to the inkjet head and ink from an external terminal via the cloud, estimates the drive waveform of the inkjet head based on the received parameters, calculates setting value data for generating the estimated drive waveform, and provides the calculated setting value data to the external terminal via the cloud.

[0012] Here, the setpoint data is digital data, and the drive waveform is a digital waveform pulse. In the following, the setpoint data for generating the drive waveform may be simplified and referred to as the drive waveform setpoint data, or simply as the setpoint data.

[0013] The setting value data specifically includes register data and drive voltage data. The drive voltage data is the voltage applied to the drive element of the inkjet head for driving the inkjet head. Hereafter, the drive voltage data will simply be referred to as the drive voltage. The register data is data conforming to the format of the driver IC mounted on the inkjet head. The register data may also be digital waveform data used to determine the drive waveform. Note that the drive voltage data is determined according to the combination of the inkjet head and ink, while the register data is determined according to the ink.

[0014] The external terminal supplies setting value data (register data, drive voltage) and print data to the liquid ejection device. The liquid ejection device generates drive pulses for the inkjet head from the setting value data and print data, generates an analog drive signal to drive the drive elements of the inkjet head from the generated drive pulses, and drives the inkjet head by supplying the generated drive signal to the drive elements.

[0015] Before describing the drive waveform suggestion system, the following section will first describe the liquid dispensing device that operates using the setpoint data provided by the drive waveform suggestion system.

[0016] (Liquid discharge device) Figure 1 is a block diagram showing an example configuration of a liquid ejection device 10 that operates using setpoint data provided by a drive waveform proposal system according to the first embodiment. The liquid ejection device 10 is, for example, an inkjet recording device. However, the liquid ejection device 10 is not limited to this and may be other devices such as a copier.

[0017] The liquid dispensing device 10 performs various processes, such as image formation, while transporting a printing medium, which is a recording medium.

[0018] The liquid dispensing device 10 comprises a control unit 11, a display 14, an operating unit 15, a communication interface 16, a transport motor 21, a motor drive circuit 22, a pump 23, a pump drive circuit 24, multiple inkjet heads 25, a head controller 26, a system bus 27, and a power supply circuit 28. Furthermore, the liquid dispensing device 10 includes a transport mechanism, a paper feed cassette, a paper output tray, etc., which are not shown. In the drawings, the interface is abbreviated as "IF".

[0019] The power supply circuit 28 converts AC power supplied from the commercial power source into DC power. The power supply circuit 28 supplies the DC power to each component in the liquid dispensing device 10.

[0020] The system bus 27 is a communication path between the control unit 11, the display 14, the operation unit 15, the communication interface 16, the motor drive circuit 22, the pump drive circuit 24, and the head controller 26. The control unit 11, the display 14, the operation unit 15, the communication interface 16, the motor drive circuit 22, the pump drive circuit 24, and the head controller 26 can send and receive information, data, addresses, control signals, commands, responses, etc., via the system bus 27.

[0021] The control unit 11 performs various controls on the liquid dispensing device 10. The control unit 11 includes a processor 12 and a memory 13. The processor 12 is an arithmetic element that performs calculations. For example, the processor 12 performs various processes based on the program stored in the memory 13 and the data used in the program. The memory 13 stores the program and the data used in the program in a rewritable manner.

[0022] The display 14 is, for example, a display device such as a liquid crystal display. The display 14 displays an image in response to video signals input from the processor 12, a graphics controller (not shown) for image processing, etc.

[0023] The operation unit 15 has an operating member that generates an operation signal based on user operation. The operating member is, for example, a touch sensor, a numeric keypad, a power key, a paper feed key, various function keys, a keyboard, etc. The touch sensor is, for example, a resistive touch sensor, a capacitive touch sensor, etc. The touch sensor acquires information indicating a specified position within a certain area. Alternatively, the touch sensor may be used as a touch panel that is arranged on the top surface of the display 14 and configured as an integral part of it. In this case, the touch sensor generates a signal indicating the touched position on the screen displayed on the display 14.

[0024] The communication interface 16 is an interface for communicating with external devices. For example, the communication interface 16 is used for communication with an external terminal 30 that transmits print data and setting value data to the liquid dispensing device 10. The communication interface 16 communicates with the external terminal 30 via a wired or wireless network, such as a LAN (Local Area Network). The external terminal 30 is a control server or PC (Personal Computer) that controls the liquid dispensing device 10.

[0025] The transport motor 21 rotates to operate transport components of a transport mechanism (not shown) for transporting the printing medium. The transport components include a transport belt for transporting the printing medium, multiple rollers (drive rollers and driven rollers) on which the transport belt is stretched, and guides. The transport motor 21 rotates the drive rollers to move the transport belt that holds the printing medium. The printing medium moves along a transport path defined by guides positioned near the transport belt.

[0026] The motor drive circuit 22 is a circuit that drives the transport motor 21. The motor drive circuit 22 drives the transport motor 21 according to the transport control signal input from the control unit 11. The motor drive circuit 22, the transport motor 21, and the transport mechanism transport the printing medium taken out from a paper feed cassette (not shown) to a paper output tray (not shown) via multiple inkjet heads 25. The paper feed cassette is a cassette that contains multiple printing media. The paper output tray is a tray that contains the printing media discharged from the liquid ejection device 10.

[0027] Pump 23 supplies ink from the ink tank through the ink supply path to the pressure chamber of the inkjet head 25. Pump 23 is located on the ink supply path, which consists of a tube (not shown) connecting the ink tank and the pressure chamber of the inkjet head 25. For simplicity, only one pump 23 is shown in the diagram, but a pump 23 (and ink tank) is provided for each inkjet head 25.

[0028] The pump drive circuit 24 drives the pump 23 according to the ink supply control signal input from the processor 12. The pump 23 supplies ink from the ink tank to the pressure chamber of the inkjet head 25.

[0029] The inkjet head 25 is an image forming unit that ejects ink onto a printing medium to form an image. Although not shown, the inkjet head 25 includes actuators, which are driving elements such as multiple piezoelectric elements that eject ink from nozzles, sensors for detecting ink temperature, and drive circuits for driving the actuators. Based on the drive power supply and control signals supplied from the head controller 26, the inkjet head 25 ejects ink onto a printing medium transported by a transport mechanism to form an image. Multiple inkjet heads 25 are provided, one for each ink color, for example, cyan, magenta, yellow, black, etc.

[0030] The liquid ejection device 10 receives print data and setting value data for each inkjet head 25 from an external terminal 30 via a communication interface 16 and stores them in memory 13. When setting up the inkjet head 25 (configuration), the processor 12 reads the print data and setting value data from memory 13 and transmits them to the head controller 26. When forming an image based on user print data (normal use), the processor 12 reads the user print data from memory 13 and transmits it to the head controller 26.

[0031] The head controller 26 is a circuit that controls multiple inkjet heads 25 based on print data and set value data. The head controller 26 supplies multiple drive voltages to the inkjet heads 25 based on the set value data. The head controller 26 also generates control signals based on the print data. The head controller 26 supplies drive voltages and control signals to the inkjet heads 25 to operate actuators within the inkjet heads 25, thereby ejecting ink from the nozzles of the inkjet heads 25 and forming an image on the printing medium.

[0032] (First example configuration of head controller and inkjet head) The following describes a first configuration example of the head controller 26 and inkjet head 25 of the liquid ejection device 10 with reference to Figures 2 and 3. Figure 2 is a block diagram showing the first configuration example of the head controller 26 of the liquid ejection device 10. Figure 3 is a block diagram showing the first configuration example of the inkjet head 25 of the liquid ejection device 10.

[0033] (Head controller) As shown in Figure 2, the head controller 26 includes a bus bridge 261, a set value data buffer 262, a print data buffer 263, a control signal generation unit 264, and a drive control unit 265. The drive control unit 265 includes a set value data transfer unit 266, a print data transfer unit 267, and a control signal transfer unit 268.

[0034] The setting value data stored in the memory 13 of the control unit 11 is input to the setting value data buffer 262 via the bus bridge 261 from the system bus 27 when the inkjet head 25 is configured. The setting value data buffer 262 stores the setting value data until the next configuration. Then, when the inkjet head 25 ejects liquid, the setting value data buffer 262 performs the necessary processing on the stored setting value data and outputs the processed setting value data to the setting value data transfer unit 266 of the drive control unit 265. The setting value data transfer unit 266 transfers the setting value data to the inkjet head 25.

[0035] Print data is input from the system bus 27 via the bus bridge 261 to the print data buffer 263. The print data buffer 263 temporarily stores the print data, performs the necessary processing as appropriate, and outputs it to the print data transfer unit 267 of the drive control unit 265. The print data transfer unit 267 transfers the print data to the inkjet head 25.

[0036] The control signal generation unit 264 generates a control signal for the inkjet head 25 and outputs it to the control signal transfer unit 268 of the drive control unit 265. The control signal includes a clock signal for timing the operation. The control signal generation unit 264 also generates a drive voltage to supply to the inkjet head 25 and outputs it to the control signal transfer unit 268 of the drive control unit 265. The control signal transfer unit 268 transfers the control signal and drive voltage to the inkjet head 25.

[0037] Figure 2 shows the configuration for one inkjet head 25. The head controller 26 includes a set value data buffer 262, a print data buffer 263, and a drive control unit 265 (set value data transfer unit 266, print data transfer unit 267, and control signal transfer unit 268) corresponding to each of the multiple inkjet heads 25. Conversely, the bus bridge 261 and control signal generation unit 264 of the head controller 26 can be shared by multiple inkjet heads 25.

[0038] (Inkjet head) As shown in Figure 3, the inkjet head 25 includes a driver IC 251 and an actuator group 256. The actuator group 256 has multiple actuators. Each actuator is a driving element that expands and contracts the pressure chamber containing the ink and ejects ink droplets from a nozzle communicating with the pressure chamber. For example, each actuator is a piezoelectric driving element made of PZT (lead zirconate titanate).

[0039] The driver IC 251 is a drive circuit for the inkjet head 25. More specifically, the driver IC 251 is a drive circuit that drives the actuator group 256. The driver IC 251 includes a drive signal generation circuit 252 and a data processing circuit 255. The drive signal generation circuit 252 includes a drive waveform generation circuit 253 and an analog switch circuit 254.

[0040] The drive signal generation circuit 252 receives set value data from the set value data transfer unit 266. The data processing circuit 255 receives print data from the print data transfer unit 267 and receives control signals and drive voltage from the control signal transfer unit 268. The data processing circuit 255 supplies the drive voltage to the drive signal generation circuit 252. The data processing circuit 255 also generates a control signal for the drive signal generation circuit 252 based on the print data and control signals, and outputs the control signal to the drive signal generation circuit 252. Under the control of the data processing circuit 255, the drive signal generation circuit 252 generates an analog drive signal from the set value data input from the set value data transfer unit 266 and outputs the drive signal to the actuator group 256.

[0041] More specifically, the analog switch circuit 254 has multiple switch elements, and the data processing circuit 255 supplies multiple levels of drive voltage to the multiple switch elements in the analog switch circuit 254. The drive waveform generation circuit 253 generates a digital drive waveform according to the set value data and printed data, and outputs the drive waveform to the analog switch circuit 254. The analog switch circuit 254 generates an analog drive signal by selectively turning on one of the multiple switch elements to which different drive voltages are supplied, according to the input digital drive waveform. The driver IC 251 outputs the drive signal to the actuator group 256.

[0042] Each actuator in the actuator group 256 operates according to a drive signal input from the driver IC 251, expanding and contracting the pressure chamber containing the ink and ejecting ink droplets from the nozzle.

[0043] (Second example of a head controller and inkjet head configuration) The following describes a second configuration example of the head controller 26 and inkjet head 25 of the liquid ejection device 10 with reference to Figures 4 and 5. Figure 4 is a block diagram showing the second configuration example of the head controller 26 of the liquid ejection device 10. Figure 5 is a block diagram showing the second configuration example of the inkjet head 25 of the liquid ejection device 10. In Figures 4 and 5, components with the same reference numerals as those shown in Figures 2 and 3 are the same components, and their detailed explanation will be omitted. The following explanation will focus on the differences.

[0044] (Head controller) As shown in Figure 4, the head controller 26 includes a bus bridge 261, a set value data buffer 2621, a print data buffer 263, a control signal generation unit 264, and a drive control unit 2651. The drive control unit 2651 includes a drive waveform generation circuit 269, a print data transfer unit 267, and a control signal transfer unit 268.

[0045] The setting value data stored in the memory 13 of the control unit 11 is input to the setting value data buffer 2621 via the bus bridge 261 from the system bus 27 when the inkjet head 25 is configured. In this second configuration example, the setting value data is digital waveform data for determining the drive waveform. The setting value data buffer 2621 stores the setting value data until the next configuration. Then, when liquid is ejected from the inkjet head 25, the setting value data buffer 262 performs the necessary processing on the stored setting value data and outputs the processed setting value data to the drive waveform generation circuit 269 of the drive control unit 2651. The drive waveform generation circuit 269 generates a digital drive waveform according to the setting value data and outputs the drive waveform to the inkjet head 25.

[0046] (Inkjet head) As shown in Figure 5, the inkjet head 25 includes a driver IC 2511 and an actuator group 256. The actuator group 256 has multiple actuators. Each actuator is a driving element that expands and contracts the pressure chamber containing the ink and ejects ink droplets from a nozzle communicating with the pressure chamber.

[0047] The driver IC 2511 is the drive circuit for the inkjet head 25. More specifically, the driver IC 2511 is the drive circuit that drives the actuator group 256. The driver IC 2511 includes an analog switch circuit 2521 and a data processing circuit 2551. The analog switch circuit 2521 receives a digital drive waveform from the drive waveform generation circuit 269. The data processing circuit 2551 receives print data from the print data transfer unit 267 and receives a control signal and drive voltage from the control signal transfer unit 268. The data processing circuit 2551 supplies the drive voltage to the analog switch circuit 2521. More specifically, the analog switch circuit 2521 has multiple switch elements, and the data processing circuit 2551 supplies multiple levels of drive voltage to the multiple switch elements within the analog switch circuit 2521. The data processing circuit 2551 also generates a control signal for the analog switch circuit 2521 based on the print data and control signal, and outputs the control signal to the analog switch circuit 2521. The analog switch circuit 2521, under the control of the data processing circuit 2551, generates an analog drive signal from the digital drive waveform input from the drive waveform generation circuit 269 and outputs the drive signal to the actuator group 256.

[0048] More specifically, the analog switch circuit 2521 generates an analog drive signal by selectively turning on one of several switch elements to which different drive voltages are supplied. The driver IC 2511 outputs the drive signal to the actuator group 256.

[0049] Each actuator in the actuator group 256 operates according to a drive signal input from the driver IC 2511, expanding and contracting the pressure chamber containing the ink and ejecting ink droplets from the nozzle.

[0050] (Selection of setpoint data using conventional methods) The selection of setting value data using conventional methods is performed as follows.

[0051] First, the inkjet head 25 is driven by the basic drive waveform, causing ink to be ejected and an image to be formed on the printing medium.

[0052] Next, the ink ejection is evaluated. The ink ejection is evaluated based on the size, speed, and shape of the ejected ink droplets, and on the image formed on the printing medium, for example, based on resolution, color reproduction, sharpness, and dot positional accuracy.

[0053] Next, the evaluation results are checked. For example, the evaluation results are checked by quantifying each of the above parameters and comparing those values ​​to thresholds. For example, if the values ​​of each parameter are deemed to be better than the respective thresholds, the evaluation result is considered OK; otherwise, the evaluation result is considered NG.

[0054] If the evaluation result is NG, the drive waveform is re-selected, the inkjet head 25 is driven with the re-selected drive waveform, ink is ejected, an image is formed, and the ink ejection is evaluated. This series of operations is repeated until the evaluation result is OK.

[0055] If the evaluation result is OK, the drive waveform at that time is recognized as the target drive waveform, and the setting value data that generates that drive waveform is selected as the target setting value data.

[0056] (Functional configuration of the drive waveform proposal system) Next, the functional configuration of the drive waveform suggestion system according to the first embodiment will be described. Figure 6 is a block diagram showing the functional configuration of the drive waveform suggestion system 50 according to the first embodiment. The drive waveform suggestion system 50 is composed of servers and the like on the cloud. In other words, the drive waveform suggestion system 50 can also be called a drive waveform suggestion server.

[0057] The drive waveform proposal system 50 includes a web server 51, an authentication server 52, a firewall 53, an application server 54, a web API (Application Programming Interface) server 55, a database server 56, and a database 57. In the diagrams, the application server is abbreviated as "AP server" and the database as "DB". Similarly, in the following explanation, the application server may also be abbreviated as "AP server" and the database as "DB".

[0058] The web server 51 serves as the initial entry point for access from the external terminal 30 to the drive waveform proposal system 50 and provides a user interface to the external terminal 30. The web server 51 has communication functions and user interface provision functions. The web server 51 also has a user interface database as a dedicated database in the database 57. In the following description, the user interface may be abbreviated as "UI". The web server 51 provides a user interface to the external terminal 30 and, through this user interface, cooperates with each server (authentication server 52, application server 54, web API server 55, database server 56) and the database 57 to receive requests from the external terminal 30 and return responses to those requests to the external terminal 30.

[0059] In one example, the external terminal 30 is a PC 31 that controls the liquid dispensing device 10. PC 31 is either a user PC or an administrator PC. In this case, the user or administrator operating PC 31 sends a request to a web server 51 via, for example, HTTPS (Hypertext Transfer Protocol Secure) communication through the user interface screen (UI screen) of a web application (e.g., a web browser) displayed on PC 31, and receives a response from the web server 51. The UI screen of the web application is created using, for example, HTML (HyperText Markup Language), CSS (Cascading Style Sheets), JavaScript (registered trademark), etc.

[0060] In another example, the external terminal 30 is a control server 32 that controls the liquid dispensing device 10. In this case, the control server 32 sends requests to the web server 51 via an API exposed as a web API and receives responses from the web server 51.

[0061] Database 57 stores various types of data. Database server 56 manages database 57. Database server 56 stores appropriate data in database 57 and reads appropriate data from database 57 in response to requests from authentication server 52, application server 54, and web API server 55, and provides them to authentication server 52, application server 54, and web API server 55.

[0062] Figure 7 shows a block diagram illustrating the functional configuration of the authentication server 52. The authentication server 52 has a login function. The authentication server 52 also has dedicated databases in database 57, including a customer database, a user database, a whitelist, and a serial number database. In the diagram, the serial number is abbreviated as "S / N". The serial number may also be abbreviated as "S / N" in the following explanation.

[0063] The authentication server 52 receives login information for external terminals 30 from the web server 51 and, through the cooperation of its login function and a whitelist that holds information on authorized external terminals 30, allows login for authorized external terminals 30. Furthermore, for new external terminals 30, the authentication server 52 uses its login function to prompt for necessary information, identifies the access source domain, registers the necessary information and the access source domain in the whitelist, and then allows login. The authentication server 52 outputs the authentication result to the firewall 53.

[0064] The authentication server 52 grants administrators permission to perform operations with administrator privileges, such as registering users in the user database and accessing each database. After login, the authentication server 52 verifies the inkjet head serial number entered against the customer database and the serial number database.

[0065] Firewall 53 protects the application server 54 and the web API server 55 from unauthorized access, etc. Based on the authentication results received from the authentication server 52, Firewall 53 allows authorized external terminals 30 to access the application server 54 and the web API server 55.

[0066] The application server 54 provides the execution environment for web applications. The web API server 55 provides APIs.

[0067] Figure 8 shows a block diagram illustrating the functional configuration of the application server 54 and the web API server 55. The application server 54 and the web API server 55 have a drive waveform suggestion function, an ink temperature / viscosity calculation engine, and a drive waveform selection algorithm. Furthermore, the application server 54 and the web API server 55 have dedicated databases in the database 57, including a coefficient database, a serial number database, an operation log database, and master data. In addition, the application server 54 and the web API server 55 provide administrators with update functions for the ink temperature / viscosity calculation engine and the drive waveform selection algorithm. In the diagram, functions provided only to administrators are indicated by shading (the same applies to other diagrams described below).

[0068] The application server 54 and the web API server 55 receive parameters from a logged-in and authenticated external terminal 30, including the usage conditions and ink information of the inkjet head 25. The drive waveform suggestion function uses an ink temperature / viscosity calculation engine and a dedicated database to analyze the parameters, including the usage conditions and physical properties, and derives the drive waveform of the inkjet head 25 using a drive waveform selection algorithm based on data analysis. The drive waveform selection algorithm is an algorithm that derives a drive waveform using the type of ink, the specific gravity of the ink, the type of inkjet head, etc., as input variables. The drive waveform suggestion function provides setting value data for generating the derived drive waveform. Furthermore, the drive waveform suggestion function corrects the setting value data based on the viscosity or temperature of the ink. Examples of ink types include UV-curing ink, oil-based ink, solvent ink, ceramic ink, and water-based ink.

[0069] Figure 9 shows a block diagram illustrating the functional configuration of the database server 56. The database server 56 has data management functions. Furthermore, the database server 56 contains a coefficient database, serial number database, customer database, master data, user database, operation log database, user interface database, whitelist, etc., within the database 57. The database server 56 also provides data update functions and user management functions to administrators.

[0070] In the drive waveform proposal system 50 configured in this way, the web server 51 functions as a communication unit that communicates with the external terminal 30 via the cloud. The web server 51, application server 54, and web API server 55 work together with the database server 56 and database 57 to create response information for the received information from the external terminal 30 and function as a response unit that provides the response information to the external terminal 30.

[0071] The external terminal 30 transmits parameters including the usage conditions and ink information of the inkjet head 25 of the liquid ejection device 10, as well as a request for register identification or a request for drive waveform proposal, to the drive waveform proposal system 50.

[0072] If access from the external terminal 30 is deemed appropriate, the drive waveform suggestion system 50 receives parameters via the web server 51, calculates setting value data for generating a suitable drive waveform for the inkjet head 25 in the application server 54 or web API server 55, and transmits the calculated setting value data to the external terminal 30 via the web server 51.

[0073] If the external terminal 30 is a PC 31 that controls the liquid ejection device 10, the application server 54 receives parameters including the usage conditions and ink information of the inkjet head 25 and outputs them to the database server 56. The database server 56 stores them in the database 57.

[0074] The application server 54 calculates setting value data for generating a suitable drive waveform for the inkjet head 25. The application server 54 stores the setting value data in the database 57 via the database server 56. The application server 54 also transmits the setting value data to the PC 31 via the firewall 53 and the web server 51.

[0075] PC31 transmits the received setting value data to the liquid ejection device 10 automatically or under command from the PC31 user. The liquid ejection device 10 receives the setting value data via the communication interface 16 and stores it in memory 13. When setting up (configuring) the inkjet head 25, the processor 12 reads the setting value data from memory 13 and transmits it to the head controller 26.

[0076] Furthermore, if the external terminal 30 is a control server 32 that controls the liquid dispensing device 10, the web API server 55 performs the same operations as the application server 54 described above. That is, the web API server 55 receives parameters including the usage conditions and ink information of the inkjet head 25 and outputs them to the database server 56. The database server 56 stores the parameters in the database 57 via the database server 56.

[0077] The web API server 55 calculates setting value data for generating a suitable drive waveform for the inkjet head 25. The web API server 55 stores the setting value data in the database 57 via the database server 56. The web API server 55 also transmits the setting value data to the control server 32 via the firewall 53 and the web server 51.

[0078] The control server 32 transmits the received setting value data to the liquid ejection device 10. The liquid ejection device 10 receives the setting value data via the communication interface 16 and stores it in the memory 13. When setting up (configuring) the inkjet head 25, the processor 12 reads the setting value data from the memory 13 and transmits it to the head controller 26.

[0079] (Hardware configuration of the drive waveform proposal system) The drive waveform suggestion system 50 may be composed of a computer. The hardware configuration of a computer 60 that may constitute the drive waveform suggestion system 50 will be described below with reference to Figure 10. Figure 10 is a block diagram showing an example of the hardware configuration of a computer 60 that constitutes the drive waveform suggestion system 50.

[0080] The computer 60 includes a processor 61, a ROM (Read Only Memory) 62, a RAM (Random Access Memory) 63, an auxiliary storage device 64, an input device 65, an output device 66, and a communication device 67.

[0081] The processor 61, ROM 62, RAM 63, auxiliary storage device 64, input device 65, output device 66, and communication device 67 are electrically connected to each other via a bus 68, enabling the transmission and reception of data and information via the bus 68.

[0082] The processor 61 is composed of a general-purpose hardware processor, such as a CPU (Central Processing Unit) or a GPU (Graphical Processing Unit). The processor 61 controls the entire system, including the ROM 62, RAM 63, auxiliary storage device 64, input device 65, output device 66, and communication device 67.

[0083] ROM62 is a non-volatile memory that constitutes part of the main memory. ROM62 non-temporarily stores the startup program required when the processor 61 starts up. The processor 61 starts up by executing the program in ROM62. ROM62 is, for example, composed of EPROM (Erasable Programmable Read Only Memory) and stores various startup settings in addition to the startup program.

[0084] RAM63 is a volatile memory that constitutes part of the main memory. RAM63 temporarily stores the program necessary for processing by the processor 61 and the data necessary for executing the program. The processor 61 executes the program in RAM63, performs calculations on the data in RAM63, and stores the calculation results in RAM63.

[0085] The auxiliary storage device 64 consists of non-volatile memory such as an HDD (Hard Disk Drive) or SSD (Solid State Drive). The auxiliary storage device 64 non-temporarily stores programs executed by the processor 61 and data necessary for program execution. The processor 61 reads the programs and data from the auxiliary storage device 64 into the RAM 63 and executes various functions by running the programs.

[0086] For example, the input device 65 is composed of a keyboard, mouse, touch panel, etc. The input device 65 is not limited to these and may be composed of any other input device. For example, the output device 66 is composed of a display, etc. The output device 66 is not limited to these and may be composed of any other output device. The input device 65 and the output device 66 may be composed of an input / output device that has the functions of both. For example, the input / output device may be composed of a tablet, disk drive, etc. Note that the computer 60 that can constitute the drive waveform proposal system 50 does not necessarily have to be equipped with the input device 65 and the output device 66. By communicating with an external input device or output device operated by the administrator of the drive waveform proposal system 50 via the communication device 67, output data from the processor 61 can be output to the external output device, or input data from the external input device can be input to the processor 61.

[0087] The communication device 67 has the function of transmitting and receiving data and information to and from the external terminal 30. For example, the communication device 67 has a receiving device and a transmitting device.

[0088] Programs stored non-temporarily in the auxiliary storage device 64 are provided to the computer, for example, via a computer-readable recording medium on which the program is stored non-temporarily. Such recording media are called non-temporarily computer-readable recording media. Examples of non-temporarily computer-readable recording media include disks such as flexible disks, optical disks (CD-ROM, CD-R, DVD-ROM, DVD-R, etc.), magneto-optical disks (MO, etc.), and semiconductor memory.

[0089] Programs stored non-temporarily in the auxiliary storage device 64 are read into the auxiliary storage device 64 via the input device 65, for example, through the disk drive if the recording medium is a disk, and stored non-temporarily. Alternatively, the program may be stored on a server on a network, downloaded from the server, and stored non-temporarily in the auxiliary storage device 64.

[0090] At startup, the processor 61 executes a program in the ROM 62 and loads the OS into the RAM 63 to start up. Under the control of the OS, the processor 61 monitors instruction inputs and the connection of external devices. Also, under the control of the OS, the processor 61 sets up a program area and a data area in the RAM 63. In response to an instruction input to start the drive waveform proposal system 50, the processor 61 loads the drive waveform proposal program from the auxiliary storage device 64 into the program area of ​​the RAM 63, and loads the data necessary for executing the drive waveform proposal program from the auxiliary storage device 64 into the data area of ​​the RAM 63. The processor 61 calculates the data in the data area according to the drive waveform proposal program and writes the calculation results to the data area. Through these operations, the processor 61, RAM 63, and auxiliary storage device 64 work together to execute the functions of the drive waveform proposal system 50: web server 51, authentication server 52, firewall 53, application server 54, web API server 55, database server 56, and database 57.

[0091] The external terminal 30 may also be composed of a computer. The hardware configuration of the external terminal 30 is the same as that of the computer 60.

[0092] (Example of operation of the drive waveform proposal system) Next, an example of the operation of the drive waveform suggestion system 50 will be described with reference to Figures 11 to 13. Figures 11 to 13 are flowcharts showing the processing flow of an example of the operation of the drive waveform suggestion system 50. For convenience, the external terminal 30 is assumed to be a PC 31. In the flowcharts of Figures 11 to 13, the processing of the external terminal 30 (PC 31 and user) is shown on the left, and the processing of the drive waveform suggestion system 50 is shown on the right. In the flowcharts of Figures 11 to 13, the drive waveform suggestion system is abbreviated as "system". Also, in the flowcharts, the inkjet head is abbreviated as "head" and register data as "register".

[0093] When a user inputs an instruction to start using the drive waveform suggestion system 50 into the PC 31, the PC 31 sends a request to start using the system 50. In ACT 11, the drive waveform suggestion system 50 uses the web server 51 to determine the source of access and checks the result. The web server 51 queries the whitelist and allows access only to specific addresses registered in the whitelist. If access is denied, for example, the drive waveform suggestion system 50 instructs the PC 31 to display an access error, causing the PC 31 to display an access error on its screen.

[0094] If access permission is granted, the drive waveform suggestion system 50 uses the web server 51 to create a UI screen for the login process. Hereinafter, the UI screen for the login process will be referred to as the login screen. The drive waveform suggestion system 50 provides the login screen to the PC 31 and instructs it to display the login screen. The PC 31 receives the login screen from the drive waveform suggestion system 50 and, in ACT 12, displays the login screen on its screen to prompt the user to log in.

[0095] The login screen, which is the interface for accepting login requests, has, for example, a user ID input field, a password input field, and a "Sign In" button. Users log in by entering their user ID in the user ID input field, entering their password in the password input field, and clicking the "Sign In" button. Once the user logs in, the PC 31 transmits the information entered on the login screen, namely the user ID and password, to the drive waveform proposal system 50.

[0096] In ACT13, the drive waveform suggestion system 50, via the authentication server 52, queries the user database for the user ID and password, performs user authentication, and checks the authentication result. The user database stores, for example, the user ID and the password associated with the user ID. Both the user ID and password are unique identification information. The user ID and password are linked one-to-one. The authentication server 52 determines that the authentication result is OK if the user ID and password entered on the login screen match the user ID and password stored in the user database, respectively, and determines that the authentication result is NG if they do not match. If the authentication result is NG, the drive waveform suggestion system 50 can instruct the PC 31 to display an error message, displaying an error message on the PC 31's screen and waiting for the user ID and password to be re-entered. The number of times this re-entry is allowed may also be limited.

[0097] If the authentication result is OK, the drive waveform suggestion system 50 allows login. Next, the drive waveform suggestion system 50 uses the web server 51 to create the UI screen for the home screen of the drive waveform suggestion web service. Hereinafter, the UI screen for the home screen of the drive waveform suggestion web service will be referred to as the home screen. Next, the drive waveform suggestion system 50 provides the home screen to the PC 31 and instructs it to display the home screen. In ACT 14, the PC 31 displays the home screen on its screen and prompts the user to select the desired service.

[0098] Figure 14 shows an example of the home screen 71. The home screen 71 is an interface that accepts the user's selection of desired services. The home screen 71 includes a menu icon 72 and waveform provision options 73. The waveform provision options 73 include a waveform suggestion icon 731 and a register identification icon 732. Clicking or pressing each icon displays the corresponding UI screen.

[0099] For example, clicking menu icon 72 will display various menus in a pop-up window.

[0100] Clicking the waveform suggestion icon 731 switches to a UI screen related to the operation of providing setting value data for generating a suitable drive waveform for any combination of inkjet head 25 and ink, i.e., suggesting a drive waveform. Clicking the register identification icon 732 switches to a UI screen related to the operation of identifying inks that can use common register data.

[0101] The home screen 71 shown in Figure 14 is the screen displayed on PC 31 when a user logs in. On the other hand, the home screen 71 displayed on PC 31 when an administrator logs in will also display management menus (user management, API issuance management, coefficient DB management, S / N_DB management, head registration management, etc.).

[0102] When a user performs any operation on the home screen 71, the PC 31 transmits operation information indicating the content of that operation to the waveform suggestion system 50. In ACT 15, the waveform suggestion system 50, using the application server 54, determines whether the received operation information is a waveform suggestion request made by clicking the waveform suggestion icon 731.

[0103] If it is not a waveform proposal request (NO in ACT15), the drive waveform proposal system 50, in ACT16, determines whether the operation information, which is the received information, is a register discrimination request due to clicking the register discrimination icon 732, based on the application server 54.

[0104] If the request is not for register identification (i.e., NO in ACT16), the drive waveform suggestion system 50 proceeds to other processing corresponding to other operations on the home screen 71. Since these other processes are not relevant to the gist of the present invention, their explanation is omitted.

[0105] When the system receives a waveform suggestion request from a user who clicks the waveform suggestion icon 731 on the home screen 71 (if the response is YES in ACT15), the drive waveform suggestion system 50 uses the web server 51 to create a UI screen for inputting the serial number. Hereinafter, the UI screen for inputting the serial number will be referred to as the serial number input screen. Next, the drive waveform suggestion system 50 provides the serial number input screen to the PC 31 and instructs it to display the serial number input screen. The PC 31 receives the serial number input screen from the drive waveform suggestion system 50 and, in ACT17, displays the serial number input screen on its screen to prompt the user to input the serial number of the inkjet head 25.

[0106] The serial number input screen is an interface that accepts the input of the serial number of the inkjet head 25. The serial number input screen has, for example, a serial number input field, an "OK" button, and a "Cancel" button. The user inputs the serial number by entering it in the serial number input field and clicking the "OK" button. The "Cancel" button is a UI controller for discontinuing the use of the drive waveform suggestion system 50. When the user clicks the "Cancel" button, the PC 31 sends a request to discontinue use to the drive waveform suggestion system 50, and the drive waveform suggestion system 50 stops processing the drive waveform suggestion service.

[0107] When a user inputs the serial number of the inkjet head 25 for which they wish to receive setting value data suggestions, the PC 31 transmits the input information from the serial number input screen, i.e., the serial number, to the drive waveform suggestion system 50. In ACT 18, the drive waveform suggestion system 50 performs a verification process by querying the serial number received by the authentication server 52 against the serial number database and checks the verification result.

[0108] The serial number verification process verifies whether the user of PC31 is a legitimate user authorized to use the drive waveform suggestion system 50. Specifically, the serial number database and customer database are used to check whether the customer associated with the serial number matches the customer associated with the user ID.

[0109] The serial number database stores serial number linkage information, which associates the serial number of the inkjet head 25 with a customer. This serial number linkage information creates a one-to-one correspondence between the serial number and the customer. A customer is a specific user authorized to use the drive waveform suggestion system 50, such as the legitimate purchaser of the inkjet head 25. The customer database also stores user ID linkage information, which associates user IDs with customers. This user ID linkage information creates a one-to-one correspondence between user IDs and customers. Serial number linkage information is registered in the serial number database when the inkjet head 25 is purchased. User ID linkage information is newly registered or added to the customer database when the inkjet head 25 is purchased.

[0110] The authentication server 52 determines that if the customer associated with the serial number matches the customer associated with the user ID, the user of the drive waveform suggestion system 50 is a legitimate user and the verification result is OK. If the customer associated with the serial number does not match the customer associated with the user ID, the authentication server 52 determines that the user of the drive waveform suggestion system 50 is an unauthorized user and the verification result is NG.

[0111] If the serial number verification result is NG, the drive waveform suggestion system 50 instructs the PC 31 to display an error message. The PC 31 then displays the error message on the screen, waits for user confirmation, and then displays the serial number input screen again to prompt the user to enter the serial number. For example, if the verification result is NG three times in a row, the drive waveform suggestion system 50 instructs the PC 31 to display an error message indicating that the serial number verification has failed three times and the drive waveform suggestion service will be forcibly terminated. After waiting for user confirmation, the drive waveform suggestion service is forcibly terminated.

[0112] If the serial number verification result is OK, the drive waveform suggestion system 50 uses the web server 51 to create a UI screen for suggesting setting value data for the inkjet head 25 specified by the serial number. This UI screen is for inputting the parameters necessary for drive waveform suggestion. The parameters necessary for drive waveform suggestion include the usage conditions and ink information of the inkjet head 25. Hereinafter, the UI screen for inputting the parameters necessary for drive waveform suggestion will be referred to as the waveform suggestion screen. Next, the drive waveform suggestion system 50 provides the waveform suggestion screen to the PC 31 and instructs the PC 31 to display the waveform suggestion screen. In ACT 19, the PC 31 displays the waveform suggestion screen on the screen and prompts the user to input parameters.

[0113] Figure 15 shows an example of the waveform suggestion screen 74. The waveform suggestion screen 74 is an interface that accepts input processing of parameters including ink information and usage conditions to be applied to one inkjet head 25. The waveform suggestion screen 74 includes a head selection field 75, an AL rank selection field 76, an ink selection field 77, a usage condition selection field 78, a printing condition selection field 79, an ink temperature / viscosity input field 80, a "Create Waveform" button 81, a drive voltage display field 82, a head / waveform type and waveform value display field 83, a "Create Register Data" button 84, a "Create / Save Register Data" button 85, and a "Apply Register Data" button 86.

[0114] The head selection field 75 includes a head type selection field and a serial number display field. The head type selection field allows the user to select the head type using a pull-down function. The serial number display field displays the serial number entered on the serial number input screen shown in ACT17.

[0115] The AL rank selection field 76 includes a rank selection field, a face selection field, and an AL rank field. The rank selection field has two options: "Head-Specific AL Rank" and "Variable AL Rank". The "Head-Specific AL Rank" option uses the serial number database. The "Variable AL Rank" option specifies the AL rank. Either of these options can be selected using radio buttons or option buttons. The face selection field allows for face selection using a pull-down function. The AL rank field allows for AL rank selection using a pull-down function.

[0116] When selecting the AL rank, selecting the serial number database applies the AL rank associated with the serial number. In other words, selecting "Head-Specific AL Rank" in Figure 15 applies the AL rank associated with the serial number. Since the AL rank of the inkjet head 25 is measured before shipment, the AL rank of the inkjet head 25 associated with the serial number is determined before shipment. The AL rank of the inkjet head 25 associated with the serial number is managed in the serial number database.

[0117] AL (acoustic length) is half the natural vibration period of the ink in the pressure chamber of the inkjet head 25, and is also called the pressure propagation time. AL has different values ​​depending on the inkjet head 25. Ranking is performed based on the AL value, and an AL rank is assigned.

[0118] The ink selection field 77 includes an ink type selection field and an ink specific gravity input field. The ink type field allows selection of the ink type using a pull-down menu. The ink specific gravity input field allows direct input of the ink specific gravity value. Additionally, a message prompting input within the recommended range (0.70 to 3.0) is pre-displayed in the ink specific gravity input field.

[0119] The usage conditions selection field 78 includes a drop count selection field and a frequency input field. The drop count selection field allows selection of the drop count using a pull-down function. The drop count selection field may also allow direct input of the drop count value. The frequency input field allows direct input of the drive frequency value. In addition, a message prompting input within the recommended range (1.0 to 30.0) is displayed in the frequency input field.

[0120] The print condition selection field 79 is for selecting print conditions, or ejection conditions. The print condition selection field 79 includes the "Resolution [dpi]" selection field, the "Print Direction" selection field, and the "Gradation Mode" selection field. The "Resolution [dpi]" selection field is for selecting the print resolution. The "Print Direction" selection field is for selecting the print direction, which is the direction in which the image is formed on the printing medium. The "Gradation Mode" selection field is for selecting the number of gradations for printing. These selection fields are accessible via a pull-down menu.

[0121] The ink temperature / viscosity input field 80 includes a temperature / viscosity selection field and a calculation / input field. The temperature / viscosity selection field has "Recommended Temperature" option, "Desired Temperature" option, and "Desired Viscosity" option. The "Recommended Temperature" option is for selecting the recommended temperature. The "Desired Temperature" option is for selecting the desired temperature. The "Desired Viscosity" option is for selecting the desired viscosity. One of these options can be selected using either a radio button or an option button. The calculation / input field has "Value Input" option and "Value Calculation" option. The "Value Input" option is for selecting value input. The "Value Calculation" option is for selecting value calculation. One of these options can be selected using either a radio button or an option button. The calculation / input field also includes an "Ink Temperature / Viscosity Calculation Input" button. The "Ink Temperature / Viscosity Calculation Input" button is a UI controller that instructs the execution of an ink temperature, viscosity, or both calculation when the "Value Calculation" option is selected. The "Ink Temperature / Viscosity Calculation Input" button is disabled when the "Value Input" option is selected. The ink temperature / viscosity input field 80 also displays an input field for entering values ​​when the "Value Input" option is selected in the calculation / input field, and a display field for displaying the calculation result when the "Value Calculation" option is selected.

[0122] In the waveform suggestion screen shown in Figure 15, the recommended temperature is selected in the temperature / viscosity selection field, and therefore the ink temperature / viscosity input field 80 displays the ink temperature at a viscosity of 10 mPa·s. When the user clicks the "Ink Temperature / Viscosity Calculation Input" button to instruct the calculation to be performed, the ink temperature / viscosity input field 80 displays the calculation result in the ink temperature at a viscosity of 10 mPa·s.

[0123] Furthermore, for example, if a desired temperature is selected in the temperature / viscosity selection field and a value input is selected in the calculation / input field, the ink temperature / viscosity input field 80 will display a display field for the ink temperature at a viscosity of 10 mPa·s and an input field for the desired ink temperature. In this case, the user enters the ink temperature in the input field for the desired ink temperature.

[0124] The "Waveform Creation" button 81 is a UI controller that instructs the drive waveform suggestion system 50 to estimate waveform pulses for generating an appropriate drive waveform for the inkjet head 25 and to output waveform data for those waveform pulses. The drive voltage display field 82 displays the drive voltage of the waveform pulse. The head waveform type and waveform value display field 83 displays the waveform type and waveform value of the waveform pulse. The waveform type has element 1, element 2, ... and the waveform value has pulse 1, pulse 2, ... Element 1, element 2, ... represents the constituent elements of the waveform pulse that determine the waveform type, and pulse 1, pulse 2, ... represents the time width of element 1, element 2, ...

[0125] The "Create Register Data" button 84 is a UI controller that instructs the drive waveform suggestion system 50 to derive a waveform pulse for generating an appropriate drive waveform for the inkjet head 25, and to output setting value data for the waveform pulse. The setting value data contains the drive voltage of the waveform pulse and register data for the waveform value of the waveform pulse. The register data is data obtained by converting each element of the waveform type of the waveform pulse and each pulse, i.e., each time width, of the waveform value to match the format of the driver IC 251 mounted on the inkjet head 25. Furthermore, if the type of inkjet head 25 identified by the serial number has a configuration like the second configuration example described above, the setting value data can be waveform digital data generated from the drive voltage of the waveform pulse and the register data converted to match the format of the driver IC 251. For example, the drive waveform suggestion system 50 outputs the setting value data of the drive waveform as a file to the PC 31.

[0126] The "Create / Save Register Data" button 85, like the "Create Register Data" button 84, is a UI controller that instructs the drive waveform suggestion system 50 to output set value data, and further instructs it to save the register data within that set value data.

[0127] The "Apply Register Data" button 85 is a UI controller that instructs the drive waveform suggestion system 50 to calculate and output setting value data using the saved register data in response to the click of the "Create / Save Register Data" button 85. When using saved register data, it is possible to omit the input of parameters including usage conditions and ink information required for calculating the setting value data.

[0128] The following explanation assumes that the user has entered the necessary parameters on the waveform suggestion screen 74 and clicked the "Create Register Data" button 84. When the user clicks the "Create Register Data" button 84, the PC 31 sends the input parameters from the waveform suggestion screen 74 and an instruction to output the drive waveform setting value data to the drive waveform suggestion system 50.

[0129] In ACT20, the drive waveform suggestion system 50 determines, based on the application server 54, whether the instruction to output the received setting value data includes an instruction to apply the stored register data. In other words, it determines whether the instruction to output the setting value data corresponds to a click of the "Create Register Data" button 84 or the "Create and Save Register Data" button 85, or to a click of the "Apply Register Data" button 86.

[0130] If the instruction to output the setting value data does not include an instruction to apply the stored register data (NO in ACT20), in ACT21, the drive waveform suggestion system 50 performs input parameter check processing via the application server 54. The targets of the check processing in ACT21 are ink information and usage conditions.

[0131] If the check result is NG (NG in ACT21), the drive waveform suggestion system 50 updates the waveform suggestion screen 74 via the web server 51 to display an error message in the message display area. Next, the drive waveform suggestion system 50 provides the updated waveform suggestion screen 74 to the PC 31 and instructs it to display the updated waveform suggestion screen 74. The PC 31 receives the updated waveform suggestion screen 74 from the drive waveform suggestion system 50 and displays the updated waveform suggestion screen 74 on the screen in ACT19, prompting the user to input parameters again.

[0132] If the check result is OK (OK in ACT21), then in ACT22, the drive waveform proposal system 50 performs ink temperature and viscosity calculation processing using the application server 54.

[0133] Next, in ACT23, the drive waveform suggestion system 50, using the application server 54, derives a drive waveform suitable for the inkjet head 25 based on the input parameters of the waveform suggestion screen 74, using a drive waveform selection algorithm and a dedicated database. Specifically, the waveform estimation algorithm takes the input parameters of the waveform suggestion screen 74 as input variables and derives waveform pulses to generate an appropriate drive waveform.

[0134] Next, the drive waveform proposal system 50 calculates the setpoint data for the waveform pulse using the application server 54 in ACT24. The setpoint data includes register data and the drive voltage. The register data includes each element of the waveform pulse and each pulse value.

[0135] In ACT25, the drive waveform suggestion system 50 determines, based on the application server 54, whether or not to save the register data from the calculated setting value data. This determination is based on whether the instruction to output the received setting value data included an instruction to save the register data. In other words, it determines whether or not the instruction to output the setting value data corresponds to a click of the "Create / Save Register Data" button 85.

[0136] If register data is not saved (NO in ACT25), the drive waveform suggestion system 50 outputs the setting value data to the PC 31 in ACT26. For example, the drive waveform suggestion system 50 uses the application server 54 to create a file containing the setting value data, and the web server 51 sends that file to the PC 31. For example, the file containing the setting value data is a text file. The file containing the setting value data may also be a CSV file or other format.

[0137] In ACT27, PC31 receives and saves a file containing the setting value data. This completes the processing for any inkjet head 25 and any ink that wish to output the setting value data when waveform suggestion is selected. After that, PC31 returns to processing in ACT14 and displays the home screen 71 on the screen to prompt the user to select the desired service.

[0138] When multiple inkjet heads 25 exist, individually acquiring setting data by inputting parameters including the serial number, usage conditions, and ink information for each inkjet head, while far simpler and time-saving compared to conventional ejection observation, still requires considerable effort and time. Strictly speaking, if the physical properties of each ink differ even slightly, the optimal register data will also differ. On the other hand, in some cases, inks with similar physical properties can be used with the same register data without practical problems. For example, when using inks with similar physical properties but different colors, such as YMCK, under the same head type / usage conditions / printing conditions, the register data acquired for one ink can be used as the register data for the other inks. Therefore, when using the same head type / usage conditions / printing conditions, i.e., one liquid ejection device 10, the register data acquired for one ink can also be used for inks with similar physical properties, eliminating the need to acquire individual register data for them and significantly reducing effort and time. However, this requires knowing which of the multiple inks used by the multiple inkjet heads 25 can utilize such common register data. In the following, the process of identifying available inks using common register data will be referred to as register identification.

[0139] Furthermore, regarding the drive voltage data, which is determined by the combination of inkjet head and ink, it is not desirable to standardize it, as it is affected by manufacturing variations even among inkjet heads of the same type. Therefore, it is necessary to calculate it individually.

[0140] The user can initiate the register identification process in the drive waveform proposal system 50 by clicking the register identification icon 732 on the home screen 71. Specifically, when the user clicks the register identification icon 732 on the home screen 71, the PC 31 sends a register identification request to the drive waveform proposal system 50 instructing it to perform register identification.

[0141] If this register discrimination request is received (if YES in ACT16), the drive waveform suggestion system 50, as in the case of waveform suggestion, creates a serial number input screen via the web server 51 and instructs the PC 31 to display the serial number input screen. As a result, in ACT28, the PC 31 displays the serial number input screen on the screen, as in ACT17 in the case of waveform suggestion, prompting the user to input the serial number of the inkjet head 25.

[0142] When a user inputs the serial number of one of the multiple inkjet heads 25, the PC 31 transmits the input information from the serial number input screen, i.e., the serial number, to the drive waveform suggestion system 50. In ACT 29, the drive waveform suggestion system 50 performs serial number verification processing by the authentication server 52, similar to ACT 18 in the case of waveform suggestion.

[0143] If the serial number verification result is OK, in ACT30, the drive waveform suggestion system 50 refers to the master data via the application server 54 to determine the conditions to be used in common by multiple inkjet heads 25, such as usage conditions and printing conditions. The master data includes not only the master data of data distributed and stored in each database, but also various supplementary data that is not stored in those databases. This supplementary data includes data on the specified common usage conditions for each type of inkjet head 25. Therefore, by referring to the master data, the drive waveform suggestion system 50 can obtain the common usage conditions corresponding to the type of inkjet head 25 that matches the verified serial number.

[0144] Once the common usage conditions have been determined, the drive waveform proposal system 50 uses the web server 51 to create a UI screen for register identification. This UI screen is for inputting the parameters necessary for register identification. The parameters necessary for register identification include the head type, usage conditions, printing conditions, ink type, ink physical properties, etc., for each inkjet head 25. Of these parameters, the head type, usage conditions, printing conditions, and ink type have already been determined as common usage conditions. The number of inkjet heads 25 in the liquid ejection device 10 can be determined from the number of serial numbers of the inkjet heads 25 associated with the customer, based on the customer information associated with the verified serial number. Hereinafter, the UI screen for inputting the parameters necessary for register identification will be referred to as the register identification condition input screen. Next, the drive waveform proposal system 50 provides the register identification condition input screen to the PC 31 and instructs the PC 31 to display the register identification condition input screen. In ACT 31, the PC 31 displays the register identification condition input screen on the screen and prompts the user to input parameters.

[0145] Figure 16 shows a first example of the register discrimination condition input screen 87. The register discrimination condition input screen 87 is an interface that accepts input processing of parameters including ink information and usage conditions to be applied to each of the multiple inkjet heads 25. The register discrimination condition input screen 87 includes a common usage conditions display field 88, an ink specific gravity input field 89, an ink viscosity input field 90, an ink viscosity temperature input field 91, and a "Discriminate" button 92.

[0146] The common usage conditions display area 88 displays the common usage conditions, including the head type, usage conditions, printing conditions, and ink type, as determined by the drive waveform suggestion system 50. The usage conditions include the number of drops and frequency [kHz], while the printing conditions include the resolution [dpi], printing direction, and gradation mode.

[0147] The ink specific gravity input field 89 allows direct input of the ink specific gravity value, one of the ink's physical properties, for each ink. Similarly, the ink viscosity input field 90 allows direct input of the ink viscosity [mPa·s] value, another of the ink's physical properties, for each ink. The ink viscosity temperature input field 91 allows direct input of the ink temperature value.

[0148] The "Discrimination" button 92 is a UI controller that instructs the drive waveform suggestion system 50 to distinguish between inks that can use common register data and to output the discrimination result.

[0149] Thus, the register discrimination condition input screen 87 is an example of a physical property input screen that accepts input of the physical properties of multiple inks, such as ink specific gravity and ink viscosity.

[0150] The following explanation assumes that the user has entered the necessary parameters on the register discrimination condition input screen 87 and clicked the "Discriminate" button 92. When the user clicks the "Discriminate" button 92, the PC 31 sends the input parameters from the register discrimination condition input screen 87 and the register discrimination instruction to the drive waveform suggestion system 50. In ACT 32, the drive waveform suggestion system 50 performs the register discrimination process via the application server 54.

[0151] Figure 17 is a flowchart showing the register discrimination process of ACT32. First, the drive waveform proposal system 50 calculates the average specific gravity Xave, which is the average value of the specific gravity of all inks, which is the input parameter value entered in the ink specific gravity input field 89 of the register discrimination condition input screen 87 in ACT3211.

[0152] Once the average specific gravity Xave is determined, the drive waveform proposal system 50 calculates the difference between each of the ink specific gravity values ​​X1, X2, X3, ... and the average specific gravity Xave, assuming that the input parameter values ​​for each ink, X1, X2, X3, ..., are X1, X2, X3, ... in ACT3212. That is, the drive waveform proposal system 50 calculates the specific gravity difference values ​​X1-Xave, X2-Xave, X3-Xave, ...

[0153] Once the specific gravity difference values ​​X1-Xave, X2-Xave, X3-Xave, ... have been determined for each ink, the drive waveform proposal system 50, in ACT3213, sets a specified threshold for ink specific gravity, for example, ±0.1, and extracts inks from the determined specific gravity difference values ​​X1-Xave, X2-Xave, X3-Xave, ... whose values ​​are within ±0.1 of the specific gravity.

[0154] Furthermore, the drive waveform proposal system 50 calculates the average viscosity Yave, which is the average value of the viscosity of all inks, which is the input parameter value entered in the ink viscosity input field 90 of the register discrimination condition input screen 87 in ACT3214.

[0155] Once the average viscosity Yave is determined, the drive waveform proposal system 50 calculates the difference between each of the ink viscosity values ​​extracted in ACT3213, for example, ink viscosity values ​​Y1, Y2, Y3, ..., and the average viscosity Yave, assuming that the input parameter values ​​for each ink, Y1, Y2, Y3, ..., are Y1, Y2, Y3, ... in ACT3215. That is, the drive waveform proposal system 50 calculates, for example, viscosity difference values ​​Y1-Yave, Y2-Yave, Y3-Yave, ...

[0156] Once viscosity difference values ​​Y1-Yave, Y2-Yave, Y3-Yave, ... are determined for each of the extracted inks, the drive waveform suggestion system 50, using ACT3216, sets a specified threshold for ink viscosity, for example, ±1 mPa·s, and extracts inks from the obtained viscosity difference values ​​Y1-Yave, Y2-Yave, Y3-Yave, ... whose values ​​are within ±1 mPa·s of the viscosity. The drive waveform suggestion system 50 then determines that these extracted inks, that is, inks whose ink specific gravity and ink viscosity values ​​are both within the specified threshold, are inks that can use the same register. In other words, the inkjet head 25 that can use the same setting value data is identified.

[0157] Note that the register discrimination condition input screen 87 shown in Figure 16 and the flowchart shown in Figure 17 are examples. For example, while ACT3211 and ACT3214 calculate the average value, the discrimination method is not limited to the above; for instance, if there are inks with significantly different values ​​among multiple inks, those inks may be excluded. Also, as shown in Figure 15, there are various input parameters, and the type of discrimination method adopted depends on the input fields of the register discrimination condition input screen 87 and the parameter values ​​entered in those input fields, depending on the parameters used to distinguish inks that can use the same register.

[0158] Once the inks that can use the same register have been identified, the drive waveform suggestion system 50 uses the web server 51 to create a UI screen to display the determination result. Hereinafter, the UI screen for displaying the determination result will be referred to as the determination result screen. Next, the drive waveform suggestion system 50 provides the determination result screen to the PC 31 and instructs it to display the determination result screen. The PC 31 receives the determination result screen from the drive waveform suggestion system 50 and displays the determination result screen on the screen in ACT 33, presenting the register determination result to the user.

[0159] Figure 18 shows an example of the discrimination result screen 93. The discrimination result screen 93 is an interface that displays inks that have been determined to be usable for the same register through register discrimination. The discrimination result screen 93 has a message display field 94 and an "OK" button 95.

[0160] The message display area 94 displays a list of inks that can use the same register, as well as a list of inks that cannot use the same register.

[0161] The "OK" button 95 is a UI controller that instructs the drive waveform suggestion system 50 to end the display of the discrimination result screen 93 and return to the display of the home screen 71.

[0162] When the user clicks the "OK" button 95, PC31 returns to processing ACT14, displays the home screen 71 on the screen, and prompts the user to select the desired service.

[0163] For inks indicated in the message display area 94 as being unavailable for use with the same register, such as inks 4 and 6 in the example of Figure 18, the user can select the waveform suggestion icon 731 on the home screen 71 and input parameters including the usage conditions and ink information of the inkjet head 25 that uses ink 4 or 6, thereby individually obtaining the setting value data for the inkjet head 25 that uses that ink, as described above.

[0164] Furthermore, for inks indicated in the message display area 94 as being usable with the same register, such as inks 1, 2, 3, 5, and 7 in the example of Figure 18, the user selects the waveform suggestion icon 731 on the home screen 71 and enters the serial number of the inkjet head 25 that uses one of the inks indicated as being usable with the same register, for example, ink 1, on the serial number input screen. Then, on the waveform suggestion screen 74, the user enters parameters including usage conditions and ink information. In this way, as described above, the setting value data for the inkjet head 25 that uses ink 1 can be obtained. However, in this case, the user clicks the "Create Register Data" button 85 on the waveform suggestion screen 74, rather than the "Create Register Data" button 84, to instruct the calculation of the setting value data and the saving of the register data. As a result, the drive waveform suggestion system 50 in ACT25 determines that the register data should be saved.

[0165] If register data is to be saved (if YES is selected in ACT25), in ACT34, the drive waveform suggestion system 50 saves the register data from the calculated setting value data and the parameters used in its calculation, as calculated by the application server 54. There are no particular restrictions on where this register data and parameters are saved, but they may be stored in one of the dedicated databases, for example. For example, they may be saved in the serial number database linked to the inkjet head 25, or they may be saved as supplementary data to the master data. After performing the processing in ACT34, the drive waveform suggestion system 50 proceeds to the processing in ACT26.

[0166] In this way, once the register data and parameters of one of the multiple inks, for example ink 1, are saved, the user can use this saved register data and parameters to calculate the setting value data for the inkjet head 25 that uses the other inks 2, 3, 5, and 7. For example, if the user wants to obtain the setting value data for the inkjet head 25 that uses ink 2, the user selects the waveform suggestion icon 731 on the home screen 71, enters the serial number of the inkjet head 25 on the serial number input screen, and clicks the "Apply Register Data" button 86 on the waveform suggestion screen 74. In this case, it is not necessary to enter parameters including usage conditions and ink information on the waveform suggestion screen 74. As a result, the drive waveform suggestion system 50 determines in ACT20 that the instruction to output the setting value data includes an instruction to apply the saved register data (YES in ACT20), and skips the processing of ACT21 to ACT22 and proceeds to the processing of ACT23. Then, in ACT23, the drive waveform suggestion system 50 uses the drive waveform selection algorithm and the dedicated database based on the parameters saved in the dedicated database by the application server 54 to derive the drive waveform. Furthermore, in ACT24, the application server 54 calculates the set value data for the waveform pulse. However, in this case, since the register data is stored in a dedicated database, only the drive voltage needs to be calculated.

[0167] (modified version) Figure 19 shows a second example of the register discrimination condition input screen 87. This second example of the register discrimination condition input screen 87 is different from the first example of the register discrimination condition input screen 87 shown in Figure 16 in that it allows the input of a reference ink value in the ink specific gravity input field 89 and the ink viscosity input field 90. The reference ink value can be any value entered by the user, or it can be the value of an ink for which setting value data has been output in the past.

[0168] Figure 20 is a flowchart showing the flow of the register discrimination process of ACT32 corresponding to the register discrimination condition input screen 87 of the second example shown in Figure 19. In this second example, since the specific gravity and viscosity of the reference ink are used, it is not necessary to calculate the average value of the specific gravity and viscosity of all inks as in the first example.

[0169] First, the drive waveform proposal system 50 calculates the difference between the specific gravity value Xsta of the reference ink and the specific gravity value X1, X2, X3, ... of each ink in ACT3221. That is, the drive waveform proposal system 50 calculates the specific gravity difference values ​​X1-Xsta, X2-Xsta, X3-Xsta, ...

[0170] Once the specific gravity difference values ​​X1-Xsta, X2-Xsta, X3-Xsta, ... have been determined for each ink, the drive waveform proposal system 50, in ACT3222, sets a specified threshold for ink specific gravity, for example, ±0.1, and extracts inks from the determined specific gravity difference values ​​X1-Xsta, X2-Xsta, X3-Xsta, ... whose values ​​are within ±0.1 of the specific gravity.

[0171] Furthermore, in ACT3223, the drive waveform proposal system 50 calculates the difference between the viscosity value Ysta of the reference ink for each ink viscosity value extracted in ACT3222, for example, Y1, Y2, Y3, ... That is, the drive waveform proposal system 50 calculates, for example, viscosity difference values ​​Y1-Ysta, Y2-Ysta, Y3-Ysta, ...

[0172] Once viscosity difference values ​​Y1-Ysta, Y2-Ysta, Y3-Ysta, ... have been determined for each of the extracted inks, the drive waveform proposal system 50, in ACT3224, sets a specified threshold for ink viscosity, for example, ±1 mPa·s, and extracts inks from the obtained viscosity difference values ​​Y1-Ysta, Y2-Ysta, Y3-Ysta, ... whose values ​​are within ±1 mPa·s of the viscosity. The drive waveform proposal system 50 then determines that these extracted inks, that is, inks in which both the ink specific gravity and ink viscosity are within the specified threshold relative to the reference ink, are inks that can be used with the same register.

[0173] Figure 21 shows an example of a discrimination result screen 93 corresponding to the register discrimination condition input screen 87 of the second example shown in Figure 19. In this case, the message display field 94 will display messages indicating which inks can use the same register as the reference ink and which cannot.

[0174] In this case, the waveform suggestion screen 74 is replaced with a "Apply Reference Register Data" button, which instructs the output of setting value data with the register data from the reference ink applied, instead of the "Create / Save Register Data" button 85 and the "Apply Register Data" button 86. When this "Apply Reference Register Data" button is clicked, the drive waveform suggestion system 50 determines in ACT20 that the instruction to output setting value data includes an instruction to apply the saved register data (YES in ACT20). Therefore, in ACT23, the drive waveform suggestion system 50 derives a drive waveform using parameters including usage conditions and ink information corresponding to the reference ink stored in the master data, and in ACT24, calculates the setting value data using the register data stored in the master data. The processing in ACT25 and ACT34 is omitted.

[0175] (effect) The drive waveform proposal system 50 according to the first embodiment receives parameters such as ink information and usage conditions from an external terminal 30 via the cloud, calculates setting value data for generating a drive waveform suitable for the inkjet head 25, and outputs it to the external terminal 30 via the cloud. Therefore, users of the external terminal 30 can receive the output of setting value data without having to perform ejection observations. This eliminates the need to perform ejection evaluations and reduces evaluation costs. The setting value data includes drive voltage data determined according to the combination of the inkjet head 25 and ink, and register data determined according to the ink. Therefore, in the case where there are multiple inkjet heads 25 that wish to output set value data, the drive waveform proposal system 50 according to the first embodiment further determines, in response to the received register identification request from the external terminal 30 instructing the system to identify inks to which the same register data can be applied, that the multiple inkjet heads 25 are of the same model and have the same usage conditions and ink ejection conditions, and that the system identifies inks with similar physical properties among the multiple inks used by the multiple inkjet heads 25, and creates a determination result as response information to the external terminal 30 indicating that the multiple inks identified as having similar physical properties are inks to which the same register data can be applied. In this way, the drive waveform proposal system 50 according to the first embodiment determines that among the multiple inks used by the multiple inkjet heads 25, the same register data can be applied when they are used with the same head type / usage conditions / printing conditions. Therefore, for multiple inkjet heads 25 that use inks to which the same register data can be applied, the system calculates the set value data for only one of the inkjet heads 25, and the register data contained in that set value data can be used for the other inkjet heads 25. Therefore, it is possible to omit the input of parameters, including usage conditions and ink information, related to the calculation of setting value data for inkjet heads 25 other than the one specified. Accordingly, the drive waveform suggestion system 50 according to the first embodiment can output setting value data suitable for the inkjet head 25 while minimizing the effort and time required from the user.

[0176] Furthermore, the drive waveform proposal system 50 according to the first embodiment presents a register discrimination condition input screen 87, which is a physical property value input screen that accepts input of the physical properties of each of the multiple inks, such as ink specific gravity and ink viscosity. For each of the multiple inks, the system calculates the difference between the average value and the ink specific gravity and ink viscosity entered on the register discrimination condition input screen 87, and identifies inks with ink specific gravity and ink viscosity whose calculated difference is within a specified threshold as inks with similar physical properties. Thus, the drive waveform proposal system 50 according to the first embodiment can easily identify inks with similar physical properties based on the physical properties of each of the multiple inks that have been input.

[0177] Alternatively, the drive waveform proposal system 50 according to the first embodiment presents a register discrimination condition input screen 87, which is a physical property value input screen that accepts input of ink specific gravity and ink viscosity, which are physical property values ​​of each of the multiple inks and a reference ink. For each of the multiple inks, the system calculates the difference between the ink specific gravity and ink viscosity of the reference ink, which are also input, for each ink specific gravity and ink viscosity input on the register discrimination condition input screen 87, and identifies inks with ink specific gravity and ink viscosity whose calculated difference is within a specified threshold as inks with similar physical properties. Therefore, the drive waveform proposal system 50 according to the first embodiment can easily identify inks with similar physical properties to the input reference ink based on the physical property values ​​of each of the multiple inks that have been input.

[0178] Furthermore, in response to the received information instructing the generation of a drive waveform in response to a click of the waveform suggestion icon 731 on the home screen 71, the drive waveform suggestion system 50 receives input on the waveform suggestion screen 74, which specifies an inkjet head 25 that uses one of the multiple inks, as well as parameters including usage conditions and ink information. Based on this, it calculates setting value data including register data, and stores the calculated setting value data containing register data in the database 57 as register data used in common by multiple inks. Thus, the drive waveform suggestion system 50 in the first embodiment can calculate and store register data used in common by multiple inks and apply it to other inks.

[0179] Furthermore, in the second example of the register discrimination condition input screen 87, by inputting the value of an ink that has undergone register discrimination in the past as the value of the reference ink, it is possible to apply the previously acquired setting value data of the inkjet head 25 using the reference ink to multiple inks that have been determined to have similar physical properties to the reference ink. Therefore, it is not necessary to calculate register data for multiple inkjet heads 25 that use multiple inks that have been determined to have similar physical properties to the reference ink. In addition, for example, when using an ink with slightly modified physical properties to comply with environmental regulations for various inks, it becomes possible to determine whether it is acceptable to apply the register data of the reference ink for which register data was previously output.

[0180] [Second Embodiment] Next, the drive waveform suggestion system 50 according to the second embodiment will be described. However, the same configuration and operation as the drive waveform suggestion system 50 according to the first embodiment will be denoted by the same reference numerals as in the first embodiment, and their description will be omitted.

[0181] Figures 22 to 24 are flowcharts showing the processing flow of an example operation of the drive waveform proposal system 50 according to the second embodiment. Here, the processing of ACT11 to ACT24 is the same as in the first embodiment. In this second embodiment, after the processing of ACT24, the process proceeds to ACT26 without performing the processing of ACT25 as in the first embodiment. Then, the processing of ACT27 to ACT33 is performed as in the first embodiment. However, in this second embodiment, the discrimination result screen 93 displayed on the PC31 screen in ACT33 is different from that of the first embodiment.

[0182] Figure 25 shows a first example of the discrimination result screen 93. This first example of the discrimination result screen 93 corresponds to the first example of the register discrimination condition input screen 87 shown in Figure 16. That is, in the discrimination result screen 93 of the first example, a message prompting the user to select the ink to be used to output the register data is displayed in the message display area 94, compared to the discrimination result screen 93 shown in Figure 18. Furthermore, the discrimination result screen 93 of the first example includes an ink selection area 96 at the position corresponding to the message prompting the user to select an ink. The ink selection area 96 allows the user to select the ink to be used to output the setting value data from among the inks that have been determined to be usable for the same register using a pull-down function. In addition, the discrimination result screen 93 of the first example has a "Cancel" button 97 instead of the "OK" button 95 in the discrimination result screen 93 shown in Figure 18. The "Cancel" button 97 is a UI controller for canceling the register discrimination process.

[0183] On the determination result screen 93, when the user clicks on any ink from the ink selection field 96, PC31 sends a register output request to the drive waveform suggestion system 50, instructing it to output the setting value data for that ink in this register determination process. Also, when the user clicks the "Cancel" button 97, PC31 sends a cancel request to the drive waveform suggestion system 50, instructing it to cancel the register determination process. In ACT41, the drive waveform suggestion system 50, using the application server 54, determines whether the request sent from PC31 is a register output request or not.

[0184] If the request sent from PC31 is a cancellation request (NO in ACT41), the drive waveform suggestion system 50 does not output the set value data, but instead performs a process to display the home screen 71 in ACT14 to PC31.

[0185] Furthermore, if the request sent from PC31 is a register output request (YES in ACT41), the drive waveform suggestion system 50 creates a waveform suggestion screen using the web server 51. In this case, the drive waveform suggestion system 50 may automatically set information already entered for register identification, such as the ink specific gravity for the selected ink, on the waveform suggestion screen and create the waveform suggestion screen. Also, the waveform suggestion screen in this second embodiment does not have a "Create / Save Register Data" button 85. The drive waveform suggestion system 50 then provides the created waveform suggestion screen to PC31 and instructs PC31 to display the waveform suggestion screen. Similar to ACT19, in ACT42, PC31 displays the waveform suggestion screen on the screen and prompts the user to input parameters.

[0186] When the user enters the necessary parameters on the waveform suggestion screen 74 and clicks the "Create Register Data" button 84, the PC 31 sends the input parameters from the waveform suggestion screen 74 and an instruction to output the drive waveform setting value data to the drive waveform suggestion system 50. In ACT43, the drive waveform suggestion system 50, as in ACT21, performs input parameter check processing via the application server 54.

[0187] If the check result is OK (OK in ACT43), then in ACT44, the drive waveform proposal system 50, similar to ACT22, performs ink temperature and viscosity calculation processing using the application server 54.

[0188] Next, in ACT45, the drive waveform suggestion system 50, similar to ACT23, uses the application server 54 to derive a drive waveform suitable for the inkjet head 25 based on the input parameters of the waveform suggestion screen 74, using a drive waveform selection algorithm and a dedicated database.

[0189] Next, in ACT46, the drive waveform proposal system 50 calculates the setpoint data for the waveform pulse using the application server 54, similar to ACT24. The setpoint data includes register data and the drive voltage. The register data includes each element of the waveform pulse and each pulse value.

[0190] Subsequently, in ACT47, the drive waveform proposal system 50 saves the register data from the calculated setting value data and the parameters used for its calculation, similar to the processing in ACT34 of the first embodiment, via the application server 54. In other words, in this embodiment, the saving of register data is performed immediately without making a determination as in the processing of ACT25 in the first embodiment, regarding whether or not to save the register data.

[0191] Next, the drive waveform proposal system 50 outputs the set value data to the PC 31 in ACT48, similar to ACT26.

[0192] In ACT49, PC31 receives and saves a file containing the setting value data, similar to ACT27. This completes the register identification process. Furthermore, within this register identification process, the process of saving the calculated register data for one of the selected inks that were deemed usable with the same register, and the process of outputting the calculated setting value data are completed. Afterward, PC31 returns to the process of ACT14, displays the home screen 71, and prompts the user to select their desired service.

[0193] (modified version) Figure 26 shows a second example of the discrimination result screen 93. This second example of the discrimination result screen 93 corresponds to the second example of the register discrimination condition input screen 87 shown in Figure 19. That is, in the discrimination result screen 93 of the second example, a message is displayed in the message display field 94 asking whether to output the register using the reference ink parameter, compared to the discrimination result screen 93 shown in Figure 21. In addition, the discrimination result screen 93 of the second example includes an output selection field 98 in the position corresponding to this inquiry message. The output selection field 98 allows selection of "OK" or "Cancel" using a pull-down function. Therefore, the discrimination result screen 93 of the second example does not have the "OK" button 95 shown in the discrimination result screen 93 shown in Figure 19.

[0194] In the second example's discrimination result screen 93, if the user selects "OK" in the output selection field 98, PC31 sends a register output request to the drive waveform suggestion system 50 instructing it to output the setting value data using the reference ink. If the user selects "Cancel" in the output selection field 98, PC31 sends a cancellation request to the drive waveform suggestion system 50 instructing it to cancel the register discrimination process.

[0195] Therefore, in ACT41, the drive waveform suggestion system 50 can perform the same operation as in the first example described above by having the application server 54 determine whether or not the request sent from the PC 31 is a register output request. However, in this second example, as in the second example in the first embodiment described above, the waveform suggestion screen 74 is equipped with a "Apply Reference Register Data" button that instructs the output of setting value data to which register data using a reference ink has been applied, instead of the "Create / Save Register Data" button 85 and the "Apply Register Data" button 86. When this "Apply Reference Register Data" button is clicked, the drive waveform suggestion system 50 skips the processing of ACT43 and ACT44 and proceeds to the processing of ACT45, and derives a drive waveform using parameters including usage conditions and ink information corresponding to the reference ink stored in the master data.

[0196] Alternatively, the drive waveform suggestion system 50 may have previously calculated setting value data for the inkjet head 25 that used a reference ink and store this data in master data. In this way, when the drive waveform suggestion system 50 determines that it has received a register output request in ACT41, it can save the register data and output the setting value data without having to perform the processing in ACT42 to ACT47.

[0197] (effect) In the first embodiment described above, in order to obtain register data, it is necessary to perform the register discrimination process, return to the home screen 71, select the waveform suggestion icon 731, and re-enter the serial number. In the second embodiment, the drive waveform suggestion system 50 not only presents the register discrimination result on the discrimination result screen 93, but also accepts the selection of the ink to be used to output the register data. The system calculates setting value data including the register data of the inkjet head 25 that uses the ink selected on the discrimination result screen 93, and saves the register data included in the calculated setting value data in the database 57 as register data to be used in common with multiple inks. Therefore, the drive waveform suggestion system 50 in the second embodiment does not require the user to return to the home screen 71 and perform operations, and it is possible to save register data to be used in common with multiple inks with less effort and time required from the user than in the first embodiment.

[0198] [Other embodiments] The procedure flow for the operation example of the drive waveform proposal system 50, as explained with reference to the flowchart, is just one example and is not limited to this order. For example, the order of the processes in ACT15 and ACT16 may be reversed. In this way, the order of processes may be changed as long as there is no discrepancy with preceding or succeeding processes. In addition, multiple processes may be performed in parallel.

[0199] Furthermore, the program executed by the drive waveform proposal system according to the embodiment may be transferred while stored in an electronic device, or it may be transferred while not stored in an electronic device. In the latter case, the program may be transferred via a network, or it may be transferred while stored in a storage medium. The storage medium is a non-temporary tangible medium. The storage medium is a computer-readable medium. The storage medium can be any medium that is capable of storing a program and is readable by a computer, such as a CD-ROM or memory card, and its form is not limited.

[0200] While embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included within the scope and spirit of the invention, as well as within the scope of the invention and its equivalents as described in the claims. [Explanation of Symbols]

[0201] 10…Liquid dispensing device, 11…Control unit, 12…Processor, 13…Memory, 14…Display, 15…Operating unit, 16…Communication interface, 21…Transport motor, 22…Motor drive circuit, 23…Pump, 24…Pump drive circuit, 25…Inkjet head, 26…Head controller, 27…System bus, 28…Power supply circuit, 31…PC, 32…Control server, 50…Drive waveform suggestion system, 51…Web server, 52…Authentication server, 53…Firewall, 54…Application server, 55…Web API server, 56…Database server, 57…Database, 60…Computer, 61…Processor, 62…ROM, 63…RAM, 64…Auxiliary storage device, 65…Input device, 66…Output device, 67…Communication device, 68…Bus, 71…Home screen, 72…Menu icon, 73... Waveform provision options, 731... Waveform suggestion icon, 732... Register identification icon, 74... Waveform suggestion screen, 75... Head selection field, 76... AL rank selection field, 77... Ink selection field, 78... Usage condition selection field, 79... Printing condition selection field, 80... Ink temperature / viscosity input field, 81... "Create Waveform" button, 82... Drive voltage display field, 83... Waveform value display field, 84... "Create Register Data" button, 85... "Create / Save Register Data" button, 86... "Apply Register Data" button, 87... Register identification condition input screen, 88... Common usage condition display field, 89... Ink specific gravity input field, 90... Ink viscosity input field, 91... Ink viscosity temperature input field, 92... "Identify" button, 93... Identification result screen, 94... Message display field, 95... "OK" button, 96... Ink selection field, 97... "Cancel" button, 98... Output selection field.

Claims

1. A drive waveform proposal system that outputs multiple setpoint data for generating multiple drive waveforms to drive multiple inkjet heads using different inks, A communication unit that communicates with an external terminal that controls the liquid ejection device having the aforementioned multiple inkjet heads via the cloud, A response unit that creates response information in response to the received information received by the communication unit from the external terminal and provides the response information to the external terminal via the communication unit, It has, The aforementioned setting value data includes register data determined according to the ink, The response unit is In response to a registered identifier request that instructs the determination of inks to which the same registered identifier data can be applied, if the multiple inkjet heads are of the same model and have the same operating conditions and ink ejection conditions, the system will determine which of the multiple inks used by the multiple inkjet heads have similar physical properties. The response information is created as a determination result that multiple inks determined to have similar physical properties are inks to which the same register data can be applied. Drive waveform suggestion system.

2. The response unit, in response to the received information of the register discrimination request, A physical property input screen is provided that accepts input of the physical property values ​​for each of the aforementioned multiple inks. The average value of the physical properties of the multiple inks entered on the physical property input screen is calculated. For each of the aforementioned multiple inks, the difference between the physical property value entered in the physical property value input screen and the calculated average value is calculated. Ink having the physical properties such that the calculated difference is within a specified threshold is determined to be ink having the same physical properties as described above. The drive waveform proposal system according to claim 1.

3. The response unit, in response to the received information of the register discrimination request, A physical property input screen is provided that accepts input of the physical property values ​​for each of the aforementioned plurality of inks and the reference ink. For each of the aforementioned multiple inks, the difference between the physical property value entered in the physical property value input screen and the physical property value of the reference ink entered in the physical property value input screen is calculated. Ink having the physical properties such that the calculated difference is within a specified threshold is determined to be ink having the same physical properties as described above. The drive waveform proposal system according to claim 1.

4. The response unit is For received information instructing the output of register data to be used in common by the multiple inks, the system further receives a designation for one of the multiple inkjet heads and one of the multiple inks, and calculates setting value data including the register data. The register data included in the calculated setting value data is stored in a database as register data to be used commonly by the multiple inks. A drive waveform proposal system according to any one of claims 1 to 3.

5. The response unit is The system provides a determination result screen that includes the aforementioned determination result and accepts the selection of an ink to be used for outputting register data that is commonly used by the multiple inks. Based on the selection of the ink on the aforementioned determination result screen, setting value data including the register data is calculated, The register data included in the calculated setting value data is stored in a database as register data to be used commonly by the multiple inks. A drive waveform proposal system according to any one of claims 1 to 3.

Images