KR100753065B1 - Image supply device, recording apparatus, recording system, and control method therefor - Google Patents

Abstract

In a recording system in which a DSC and a PD printer are directly connected through a communication interface, and image data is transmitted and recorded from the DSC to the PD printer, a predetermined state is established within a predetermined time after the DSC issues a predetermined command to the PD printer. It is determined whether or not the information is being received from the PD printer. When it is determined that the predetermined state information has not been received, it is determined that the state is a state predicted from the general process, and the process continues. In order to confirm the status of the PD printer, the DSC requests status information from the PD printer, and acquires the status of the PD printer based on the status information returned in response to the request.

Digital Camera, Direct Print, Status Information, Printer Status, Command Issuance

Description

Image supply device, recording device, recording system and control method thereof {IMAGE SUPPLY DEVICE, RECORDING APPARATUS, RECORDING SYSTEM, AND CONTROL METHOD THEREFOR}

The present invention relates to an image supply device such as a digital camera, a recording apparatus, a recording system, and a control method thereof.

In recent years, digital cameras (imaging apparatuses) capable of capturing images by simple operation and converting them into digital image data have been widely used. When printing an image picked up with such a camera and using it as a photograph, the digital data of the shot is first downloaded from the digital camera to a PC (computer), the image processing is executed by the PC, and the processed image data is transferred to a PC. It is common to output to a color printer from a printing machine.

On the other hand, in recent years, for example, a color printing system in which a digital camera directly transmits digital image data to a color printer and prints it without going through a PC, and a memory card that stores images captured in a digital camera BACKGROUND ART A so-called photo-direct (PD) printer has been developed that can be directly mounted on a color printer and print out captured images stored in the memory card.

In particular, in order to transfer image data directly from a digital camera to a printer and print the image data, a request for standardization of interface specifications, operation methods, and the like between digital cameras and printers of respective manufacturers has been raised. One proposal for standardization is a guideline for realizing a Direct Print System (DPS).

However, a printer that receives image data directly from a digital camera and prints the image may also receive print data from a PC or the like in addition to the digital camera and print the data. For this reason, when a preprocessing procedure for receiving image data is executed between the printer and the digital camera, the response to the command from the digital camera may be delayed due to the issuance of a print request from the PC. For example, when a print start request is issued by the digital camera and received by the printer, the status indicating that the next command can be received is changed from "true" to "false", and this status is changed to the camera. You are notified. However, for example, if a print request is issued simultaneously from a PC, the printer cannot promptly notify the camera of the change of status. During this period, the camera may determine that the next command may be received by the printer, and issue a command to the printer even when the printer is busy.

The present invention has been made in view of the above situation, and when a response according to a predetermined procedure between the image supply device and the recording apparatus is not received from the recording apparatus, it is determined that the state of the recording apparatus is a state predicted from the general procedure. And an image supply device, a recording apparatus, a recording system, and a control method thereof for determining a subsequent processing procedure.

According to the present invention, there is provided an image supply device for use in a recording system in which an image supply device and a recording apparatus are directly connected through a communication interface, and image data is transmitted and recorded from the image supply device to the recording apparatus. The supply device includes receiving means for receiving state information from the recording apparatus, and after the image supply device issues a predetermined command to the recording apparatus, the receiving means receives a predetermined state from the recording apparatus within a predetermined time. And judging means for judging whether or not the information has been received, and if the judging means judges that the predetermined state information has not been received, it is determined that the state is expected from the normal processing and continues with the processing means. It features.

According to the present invention, there is provided a recording apparatus for use in a recording system in which an image supply device and a recording apparatus communicate with each other via a communication interface, and image data is transmitted and recorded from the image supply device to the recording apparatus. Means for issuing a predetermined command to the image supply device, receiving means for receiving a signal from the image supply device after the command issuing means issues the predetermined command, and the receiving means. Judging means for judging whether or not a signal received by the terminal is a response corresponding to the predetermined command, and when the judging means determines that the signal is not a response corresponding to the predetermined command, Control means for controlling the timing of issuance of the next command for It features.

Other features and advantages of the invention will be apparent from the following description taken in conjunction with the accompanying drawings, in which like reference characters designate the same or similar parts.

The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.

1 is a schematic perspective view of a PD printer according to an embodiment of the present invention;

2 is a schematic view of an operation panel of the PD printer according to the present embodiment,

3 is a block diagram showing a configuration of main parts related to the control of the PD printer according to the present embodiment;

4 is a block diagram showing the configuration of a DSC according to the present embodiment;

5 is a diagram for explaining a connection between a PD printer and a digital camera according to the present embodiment;

6 is a view for explaining command exchange between the PD printer and the DSC in the printing system according to the present embodiment,

7 is a view for explaining an example of the print start command issued by the DSC according to the present embodiment;

8A and 8B are diagrams illustrating JobStatus and DeviceStatus according to the present embodiment,

9 is a flowchart showing print restart processing by DSC according to the first embodiment,

10 is a flowchart for describing processing by DSC according to the third embodiment,

11 is a flowchart for explaining processing associated with button operations for continuing printing in DSC according to the fourth embodiment,

Fig. 12 is a flowchart for explaining processing associated with button operations for stopping printing in DSC according to the fourth embodiment,

13 is a flowchart for describing processing by DSC according to the fifth embodiment,

14 is a flowchart for describing processing by the PD printer according to the sixth embodiment,

15 is a flowchart for explaining further processing by the PD printer according to the sixth embodiment.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a schematic perspective view of a photo direct printer (hereinafter referred to as "PD printer") 1000 according to an embodiment of the present invention. The PD printer 1000 functions as a general PC printer that receives data from a host computer (PC) and prints the data, and directly reads and prints image data stored in a storage medium such as a memory card, or a digital camera. It has a function of receiving image data from and printing the data.

Referring to FIG. 1, the main body forming the exterior of the PD printer 1000 according to the present embodiment has a lower case 1001, an upper case 1002, an access cover 1003, and an output tray 1004 as an exterior member. have. The lower case 1001 constitutes approximately the lower half of the PD printer 1000, and the upper case 1002 constitutes the approximately upper half of the main body. The combination of these cases constitutes a hollow structure having a storage space for storing the mechanism (to be described later). Openings are formed in the upper and front surfaces of the main body, respectively. One end of the discharge tray 1004 is rotatably supported by the lower case 1001, and opens and closes an opening formed in the front surface of the lower case 1001 by the rotation of the tray 1004. When performing the printing operation, the discharge tray 1004 is rotated toward the front side to open the opening. The printing sheet may be discharged from the opening and sequentially stacked on the discharge tray 1004. The discharge tray 1004 houses two auxiliary trays 1004a and 1004b. If necessary, the auxiliary tray can be pulled out to enlarge / reduce the support area of the printing sheet in three steps.

One end of the access cover 1003 is rotatably supported by the upper case 1002 to open and close the opening formed in the upper surface. By opening the access cover 1003, a printhead cartridge (not shown), ink tank (not shown), and the like stored in the main body can be exchanged. Although not shown, when the access cover 1003 is opened and closed, a protrusion formed on the rear surface of the cover 1003 rotates the cover opening and closing lever. By detecting the rotational position of the lever with a micro switch or the like, the open / closed state of the access cover 1003 can be detected.

The power key 1005 is disposed on the upper surface of the upper case 1002. On the right side of the upper case 1002, an operation panel 1010 including a liquid crystal display portion 1006, various key switches, and the like is provided. The structure of the operation panel 1010 will be described later in detail with reference to FIG. 2. Reference numeral 1007 denotes an automatic feeding unit, which automatically feeds the printing sheet into the apparatus main body. Reference numeral 1008 denotes a paper gap selection lever, which is used to adjust the gap between the printhead and the print sheet. Reference numeral 1009 denotes a card slot, which accommodates an adapter for accommodating a memory card. Through this adapter, image data stored in the memory card can be directly read and printed. Examples of the memory card PC are a compact flash (registered trademark) memory card, a smart media card, and a memory stick. Reference numeral 1011 denotes a viewer (liquid crystal display unit), which is detachable from the main body of the PD printer 1000, and when the user searches for an image to be printed from among the images stored in the PC card, an image for one frame. , Index images and the like are used. Reference numeral 1012 denotes a USB terminal used for connecting a digital camera (to be described later). Further, on the back of the PD printer 1000, another USB connector for connecting a personal computer (PC) is provided.

2 is a schematic diagram of the operation panel 1010 of the PD printer 1000 according to the present embodiment.

Referring to FIG. 2, the liquid crystal display 1006 displays menu items for setting various types of data related to items printed on the left and right sides of the display unit 1006. The items displayed on the liquid crystal display 1006 include, for example, the head number or designated frame number (start / specified) of the picture to be printed, the last picture number (end) for the print end operation, and the number of copies to be printed (copies). ), The type of paper (print sheet) to be used for printing (paper type), the number of photos to be printed on one print sheet (layout), the quality of the print (quality), and whether to print the shooting date or not. (Date printing), designating whether or not to print photographs after correction (image correction), and displaying the number of print sheets required for printing (number of sheets). These items are selected or specified by the user using the cursor keys 2001. Reference numeral 2002 denotes a mode key. Each time the mode key 2002 is pressed, the type of printing (index printing, full frame printing, one frame printing, etc.) can be changed, and a corresponding one of the LEDs 2003 lights up according to the selected printing type. Reference numeral 2004 denotes a maintenance key, which is used to perform maintenance of the printer such as cleaning of the printhead. Reference numeral 2005 denotes a print start key, which is pressed when instructing to start printing or when establishing a setting for maintenance. Reference numeral 2006 denotes a print stop key, which is pressed when the printing or maintenance is stopped.

Hereinafter, with reference to FIG. 3, the structure of the main part under control of the PD printer 1000 which concerns on a present Example is demonstrated. In Fig. 3, parts common to those in the foregoing drawings are denoted by the same reference numerals, and description thereof is omitted.

Referring to FIG. 3, reference numeral 3000 denotes a controller (control board). Reference numeral 3001 denotes an ASIC (Dedicated Custom LSI). Reference numeral 3002 denotes a digital signal processor (DSP). A CPU is built in various control processes (described later), conversion from a luminance signal RGB to a density signal CMYK, scaling, gamma conversion, error diffusion, and the like. Image processing is performed. Reference numeral 3003 denotes a memory having a program memory 3003a for storing a control program for the CPU of the DSP 3002, and the RAM area has a memory area functioning as a work memory for storing image data and the like. Reference numeral 3004 denotes a printer engine. In this embodiment, a printer engine for an inkjet printer that prints a color image using a plurality of color inks is mounted in the printer. Reference numeral 3005 denotes a USB connector acting as a port for connecting a digital camera (DSC) 3012. Reference numeral 3006 denotes a connector for connecting the viewer 1011. Reference numeral 3008 denotes a USB hub. When the PD printer 1000 executes printing based on the image data from the PC 3010, the USB hub 3008 passes through the data from the PC 3010 and passes through the USB 3021 to the printer engine 3004. Output the above data. The connected PC 3010 can execute printing by exchanging data and signals directly with the printer engine 3004 (functioning as a general PC printer). Reference numeral 3009 denotes a power supply connector, which inputs a DC voltage converted from a commercial AC power supply from the power supply 3019. The PC 3010 is a general personal computer. Reference numeral 3011 denotes a memory card (PC card) described above, and reference numeral 3012 denotes a digital camera (hereafter referred to as a DSC: Digital Still Camera).

On the other hand, signals are exchanged between the control unit 3000 and the printer engine 3004 via the USB 3021 or the IEEE 1284 bus 3022.

4 is a block diagram showing the configuration of the DSC (digital still camera) 3012.

Referring to Fig. 4, reference numeral 3100 denotes a CPU that controls the entire DSC 3012, and reference numeral 3101 denotes a ROM that stores a processing sequence (control program) of the CPU 3100. Reference numeral 3102 denotes a RAM used as a work memory of the CPU 3100, and reference numeral 3103 denotes a switch group used for performing various operations. The switch group 3103 includes various switches, cursor keys, and the like. Reference numeral 2700 denotes a liquid crystal display, which is used to display an image currently shot or an image captured / memorized, and to display a menu for performing various settings on the DSC 3012. Reference numeral 3105 denotes an optical unit, and mainly includes a lens and a drive system thereof. Reference numeral 3106 denotes a CCD element, and reference numeral 3107 denotes a driver for driving and controlling the optical unit 3105 under the control of the CPU 3100. Reference numeral 3108 denotes a connector for connecting the storage medium 3109 (compact flash memory card, smart media card, etc.), and reference numeral 3110 denotes a connector for connecting a PC or the PD printer 1000 of the present embodiment. Shows the USB interface (USB slave side).

5 is a diagram illustrating a connection between the PD printer 1000 and the DSC 3012 according to the present embodiment. The parts common to those in the above drawings are denoted by the same reference numerals, and description thereof is omitted.

Referring to FIG. 5, the cable 5000 includes a connector 5001 connected to the connector 1012 of the PD printer 1000, and a connector 5002 connected to the connector 5003 of the digital camera 3012. . The digital camera 3012 can output image data stored in the internal memory (memory card) through the connector 5003. The digital camera 3012 can adopt various structures, such as a structure which incorporates a memory as a storage means, and a structure which has a slot for inserting a removable memory. The PD printer 1000 and the digital camera 3012 are connected via the cable 5000 shown in FIG. 5, and the image data from the digital camera 3012 is directly transmitted to the PD printer 1000 so that the PD printer 1000 can be connected. Can be printed by

Based on the above structure, the operation example of the printing system which concerns on this embodiment is demonstrated as an Example.

[First Embodiment]

An outline of the operation of the printing system including the DSC 3012 and the PD printer 1000 based on the above configuration will be described. In the printing system according to the first embodiment, the DSC 3012 and the PD printer 1000 can operate in accordance with the Direct Print System (DPS) specification.

FIG. 6 is a diagram for explaining a sequence when the DSC 3012 issues a print request to the PD printer 1000 to print in the printing system according to the first embodiment.

This processing sequence is executed after confirming that the PD printer 1000 and the DSC 3012 are connected via the cable 5000 and confirm that they conform to the DPS specification. The DSC 3012 transmits "ConfigurePrintService" to the PD printer 1000 to acquire the state of the PD printer 1000 (600). In contrast, the PD printer 1000 notifies the DSC 3012 of the current state of the PD printer 1000 (in this case, an "idle" state) (601). The DSC 3012 inquires about the capability of the PD printer 1000 (602), and issues a print start request (StartJob) according to the capability (603). The print start request is issued at 601 under the condition that " newJobOK " (FIG. 8B) in the state information (to be described later) from the PD printer 1000 is " True. &Quot;

In response to the print start request, the PD printer 1000 requests file information from the DSC 3012 based on the file ID of the image data to be printed (604). In response to this, the DSC 3012 transmits file information. The file information includes items of information such as file capacity (file size), presence or absence of a thumbnail image, and file attributes. If the PD printer 1000 receives the file information and determines that the file can be processed, the PD printer 1000 requests the file to the DSC 3012 (605). The DSC 3012 transmits image data of the requested file. Then, when the PD printer 1000 starts printing processing, the PD printer 1000 transmits status information indicating "Printing" to the DSC 3012 by "NotifyDeviceStatus", at 606. After the print process of one page is finished, the PD printer 1000 notifies the DSC 3012 of the end of the print process by " NotifyJobStatus " 607 at the start of the process of the next page. In the case of printing only one page, the PD printer 1000 notifies the DSC 3012 of the " idle " status by " NotifyDeviceStatus " 608 at the end of printing of the requested one page. In the case of N-up printing in which a plurality of (N) images are laid out and printed on one page, each time N images are printed, the PD printer 1000 sends a "NotifyJobStatus" 607 to the DSC 3012. do. In this embodiment, the issuance timing and image data acquisition order of "NotifyJobStatus" and "NotifyDeviceStatus" are merely examples, and various cases may be considered depending on the specifications of the product.

The print process includes a case where the file ID of the image data to be printed is sent to the print start request (StartJob) from the DSC 3012 at one time to perform printing, and for the DPOF file used in general photo development. Only the file ID is included in the print start request (StartJob) from the DSC 3012 and sent to the PD printer 1000, and the PD printer 1000 interprets the DPOF file, obtains the file ID of necessary image data, and prints it. It also includes the case.

FIG. 7 is a view for explaining an example of a print start request issued to the PD printer 1000 by the DSC 3012. As shown in FIG.

In FIG. 7, reference numeral 720 denotes a configuration of a print job (jobConfig), and reference numeral 721 denotes print information (printInfo).

The configuration 720 will be described. Reference numeral 700 (image quality) designates print quality such as "standard" or "high image quality". Reference numeral 701 (paper size) designates a paper size, and reference numeral 702 (paper type) designates a paper type such as "plain paper", "photo paper" or "inkjet paper". Reference numeral 703 (file type) designates the type of image file to be printed. For example, in the case of using DPOF, the type representing DPOF is designated by the file type 703. Reference numeral 704 (date printing) designates the presence or absence of date printing, reference numeral 705 (file name printing) designates whether or not a file name is printed, and reference numeral 706 (image optimization) designates whether image optimization is performed or not. Reference numeral 707 (fixed size) designates whether or not printing of a fixed size is performed, and reference numeral 708 (cut) designates whether or not to print a specified range of an image.

The print information 721 includes a file ID 709 (fileID) and date information 710 (date).

8A and 8B are diagrams illustrating items of information included in the above-described JobStatus and DeviceStatus. JobStatus (FIG. 8A) and DeviceStatus (FIG. 8B) are sent from the PD printer 1000 to the DSC 3012. The DSC 3012 may require the PD printer 1000 to transmit information of those items at any timing.

In Fig. 8A, "prtPID", "ImagePath" and "copyID" become valid when printing of a DPOF file is specified. "prtPID" is identification information (ID) of the print section specified by the DPOF file. "ImagePath" is information of a path for specifying an image file designated by a DPOF file. "copyID" designates the number of copies being printed when designating a plurality of copies. In printing based on the DPOF file, the DSC 3012 describes the "fileID" of the DPOF file in the print start request StartJob, and sends the print start request to the PD printer 1000. In response to this, the PD printer 1000 can start printing the DPOF file. The PD printer 1000 acquires a DPOF file based on "fileID" of the DPOF file, executes "GetFileID", and specifies "fileID" of the image file specified in the DPOF file. The PD printer 1000 requests the image file from the DSC 3012 to obtain the image data. As a result, the image specified in the DPOF file can be printed. During the printing execution based on the DPOF file, the PD printer 1000 notifies the DSC 3012 of "prtPID", "ImagePath", and "copyID" which indicate the progress of printing by "NotifyJobStatus".

When the print process is restarted after the print process is stopped for some reason during the printing of the DPOF file, the print process is restarted from the beginning of the page where the print process is stopped.

"progress" represents the current page (N / T) of the number of sheets to be printed. N represents the current print page, and T represents the total number of print pages to be printed. "imagePrinted" indicates the number of printed images.

DeviceStatus (FIG. 8B) is demonstrated.

"dpsPrintServiceStatus" designates the status of the PD printer 1000 and is sent from the PD printer 1000 to the DSC 3012. "dpsPrintServiceStatus" includes idle, print and pause status. "jobEndReason" designates the end state of the print process, and is sent to the DSC 3012 when the printing of the last page is completed. "errorStatus" indicates an error status and is sent when an error occurs. "errorReason" means the reason for the occurrence of the error and is sent with "errorStatus".

"disconnectEnable" means that the USB cable 5000 can be printed even if the USB cable 5000 is disconnected from the PD printer 1000. The PD printer 1000 notifies the DSC 3012 of "disconnectEnable". "capabilityChanged" means that the performance in the PD printer 1000 has changed, and is sent to the DSC 3012. "newJobOK" means that the PD printer 1000 can accept a print request, and is sent to the DSC 3012.

9 is a flowchart showing print restart processing in the DSC 3012 according to the first embodiment. The program which executes this process is stored in the ROM 3101, and the CPU 3100 executes the control process in accordance with the program to realize the process.

In this process, if the cable 5000 is disconnected, for example, during the execution of a print job, the print operation is stopped. Thereafter, the DPS reconnection is established, and the print button of the DSC 3012 is designated, and the PD printer 1000 is instructed to restart the print operation. Thus, the PD printer 1000 resumes printing.

This processing assumes that the stop of the print process in the PD printer 1000 and the stop of the print process in the DSC 3012 are recognized by the PD printer 1000 and the DSC 3012.

In step S1, it is determined whether the DSC 3012 and the PD printer 1000 are physically connected by the connection of the cable 5000 or the like, and whether or not the reconnection of the DPS is established. If the connection is established, the process proceeds to step S2. If the DSC 3012 specifies to restart printing, it is determined whether or not the print processing is stopped. If the print processing has not been stopped, the processing flow advances to step S3 to perform general print processing, such as a process for starting a new print process in accordance with a print instruction.

If the print processing is stopped, the processing flow advances to step S4. The same model (<dpsVersion> and <productName> are the same), the same manufacturer's model (<productName>), or the same as the PD printer 1000 to which the newly established PD printer 1000 has stopped the previous print process. It is determined whether or not the vendor's model (<vendorName>). In this procedure, the model of the PD printer 1000 is determined based on the contents sent as a response from the PD printer 1000 to the "ConfigurePrintService" issued by the DSC 3012. The problem does not occur when the same PD printer is reconnected. For other types of printers, if the printer's manufacturer or vendor is the same and the reprinting process according to the first embodiment is possible based on the design of the manufacturer or vendor, it can be determined that the printing can be restarted. The process flow proceeds to the next process step S6. If NO in step S4, the flow advances to step S5 to determine that the continuation of the print process is impossible, and displays a message on the display portion 2700 of the DSC 3012. If necessary, a user menu window (UI) displayed on the display unit 2700 may be changed.

If it is determined in step S4 that the reconnected device is a compatible model, the processing flow advances to step S6 to determine whether print processing is being performed using the DPOF file. If YES in step S6, the flow advances to step S7 to transmit the file ID of the DPOF file to the PD printer 1000. In this case, " prtPID ", " ImagePath " and " copyID " described above are transmitted together with the file ID of the DPOF file, thereby specifying a file to be restarted in the print process using the DPOF file.

In step S6, when print processing is not performed using the DPOF file, that is, when printing by designating each image file, the file of the image file except the printed image file among the file IDs of the image file to be printed. The ID is sent to the PD printer 1000 at once to execute printing. On the other hand, as a print restart instruction, a print button is instructed among the operation buttons of the DSC 3012, and " StartJob " is sent from the DSC 3012 to the PD printer 1000 to restart the print process.

The PD printer 1000 indicates the end of printing of each page, "jobStatus" (meaning the start of printing of the next page) sent from the PD printer 1000 at the start of the next page, or "deviceStatus" in the case of the last page. The DSC 3012 is notified by " jobEndReason " Therefore, the DSC 3012 can confirm the number of printed images. When printing images one by one, depending on whether the number of images specified by the print command is printed or when the print process is based on the DPOF file, the progress of the DPOF file ("prtPID", "ImagePath" and "copyID") or based on whether or not the print process is completed, it can be determined whether or not the print process is stopped.

When one image is printed on one page, the number of print sheets and the number of images coincide. However, when a plurality of N images are laid out and printed on one sheet of paper, the number of images to be printed does not match the number of printing sheets. The DSC 3012 must make the number of print sheets and the number of image data coincide with each other in accordance with the print mode.

Second Embodiment

In FIG. 7, when the date print <datePrint> 704 of the <jobConfig> 720 is specified, the <date> 710 included in the <printInfo> 721 is printed. Date printing of <jobConfig> 720 If <datePrint> 704 is not specified, even if <date> 710 is included in <printInfo> 721, the date data is ignored and is not printed.

This is because the degree of freedom of data contained in <printInfo> 721 can be increased. For example, the startJob command can be created by directly attaching the image data and the date list being used by another job to the <printInfo> 721.

Third Embodiment

10 is a flowchart for explaining processing in the printing system according to the third embodiment of the present invention.

In the third embodiment, when the DSC 3012 issues a command to the PD printer 1000 and the state of the PD printer 1000 changes, the PD printer 1000 is in that state by the above-described "NotifyDeviceStatus". The DSC 3012 is notified. However, if the state of the PD printer 1000 does not change or the response is delayed, the DSC 3012 determines that a change in the state naturally predicted in the PD printer 1000 has occurred by a previously issued command (inferred). And the corresponding process is executed. In order to confirm the status of the PD printer 1000, the DSC 3012 issues "GetDeviceStatus" to the PD printer 1000, obtains the status of the PD printer 1000, and corresponds to the acquired status of the printer. Run the process.

An example of this process will be described with reference to the flowchart in FIG. 10.

In step S10, a print start request "StartJob" is issued to the PD printer 1000. The processing flow advances to step S11 to determine whether or not a predetermined status response "NotifyDeviceStatus" is received from the PD printer 1000. When the PD printer 1000 is a product type capable of accepting only one print job, after the print start request "StartJob" is issued to the PD printer 1000, the PD printer 1000 receives the next print job. NewJobOK in NotifyDeviceStatus should indicate "false", indicating that it can. If a normal response (newJobOK is "false") is received in step S11, the process flow goes to step S12, and waits until "newJobOK" changes to "true". Then, general print processing for issuing the next command or outputting image data or the like in response to a request from the PD printer 1000 is executed.

In step S13, it is determined whether or not "NotExecuted" has been received indicating that "StartJob" could not be executed. If "NotExecuted" is received, the process flow advances to step S20 to issue "GetDeviceStatus" to the PD printer 1000 to obtain the current status of the PD printer 1000. If this reason proves why the command was not executed, and " StartJob " can be reissued, a message about this result is displayed in the UI of the display portion 2700 of the DSC 3012. Then, if the user designates the reissue of the command using the button 3103, the processing flow advances from step S21 to S22, and reissues the unstarted "StartJob" command to the PD printer 1000. In step S21, when no reissue instruction is input, the process flow advances from step S22 to step S19.

In step S13, when "NotExecuted" is not received, the process proceeds to step S14 to determine whether or not "NotSupported" has been received. If "NotSupported" is received, the process proceeds to step S15. In this case, the previously issued " StartJob " is not supported by the PD printer 1000, and on the UI of the display portion 2700, to indicate that a print command is not supported by the PD printer 1000, for example, For example, an unsupported item (not assignable) is displayed.

Meaning that the "StartJob" command is not supported includes the case where the PD printer 1000 does not support the "StartJob" command itself, and the PD printer 1000 supports the "StartJob" command itself, but the paper size is not supported. This also includes cases where the "StartJob" command currently issued is not supported because the paper type is specified. In this case, as in the above example, the UI of the DSC 3012 is reconstructed so that it is impossible to select an inappropriate paper size or paper type (item set for a print operation). This may reduce the likelihood of receiving "NotSupported" again when the "StartJob" command is executed again for the PD printer 1000. Here, for example, a process of confirming the paper size or paper type supported by the PD printer 1000 may be performed.

If "NotSupported" is not received in step S14, the processing flow advances to step S11 '. This step assumes that the response content is substantially "OK". If a predetermined status response is received in step S11 ', the processing flow goes to step S12 to continue normal operation. If the predetermined state information is not received in step S11 ', the processing flow goes to step S16 to determine whether or not to continue the operation as a normal operation. This may be displayed using the UI described above, allowing the user to select a general operation. When the processing shifts to the normal operation, the processing flow goes to step S12. If the user does not input any command, and the process does not proceed to the normal operation, the process proceeds to step S17 to request a status to the PD printer 1000 using "GetDeviceStatus". The process flow proceeds to step S18, where the state of the PD printer 1000 is acquired, and if the state obtained is normal, this state is determined to be generally predicted, and the process flow proceeds to step S12. If another state is acquired, the process flow proceeds to step S19 to execute a process corresponding to the obtained state.

In step S13, the reason why unexpected "NotExecuted" was returned as a response is, for example, that the PC 3010 is connected to the PD printer 1000, and at the same time as the print start request from the DSC 3012, the PC ( This is because the print command from the 3010 is received by the PD printer 1000, and the print processing of the print data from the PC 3010 starts. That is, based on the NotifyDeviceStatus issued by the PD printer 1000, since the DSC "3012 recognizes" newJobOK "=" true "in advance, the DSC 3012 issues a" StartJob "command. , As soon as the "StartJob" command is issued, "newJobOK" = "false", and the PD printer 1000 returns "NotExecuted" as a response. DSC 3012 recognizing "newJobOK" = "true" Receives an unexpected response "NotExecuted" from the PD printer 1000. In step S11, the reason why the predetermined state information is not received is, for example, that the PD printer 1000 cannot accept a plurality of print jobs. Even if the print request "StartJob" is used, "newJobOK" of "DeviceStatus" does not change to "True", so that the PD printer 1000 sets "NotifyDeviceStatus" to the DSC 3012. In this case, the DSC 3012 determines that the PD printer 1000 is set by " GetDeviceStatus ". It is safe to assume that "newJobOK" is "false" until the status is confirmed (because it is possible to delay the issuance of "NotifyDeviceStatus" for some reason "newJobOK" = "false").

The foregoing description assumes that both commands become valid even if a command from the DSC 3012 and a command from the PD printer 1000 are issued at about the same time. However, there may also be a direct print specification that " commands from the DSC 3012 are processed preferentially, and issuance of commands from the PD printer 1000 are discarded and discarded among the commands issued almost simultaneously. &Quot; In this case, the inspection contents in step S11 are "has the command issued from the PD printer 1000 been received?" If YES in step S11, the processing flow proceeds to step S13 through a step (not shown) for ignoring the command from the PD printer 1000, and if no command is received from the printer 1000, The process flow goes directly to step S13.

In the direct printing specification described above, the discarded command of the PD printer 1000 may be reissued by the PD printer 1000. A case where a print command from the PC 3010 is received almost simultaneously with " StartJob " from the DSC 3012, and a print process for printing data from the PC 3010 starts. The DSC 3012, which has previously recognized "newJobOK" = "true" by NotifyDeviceStatus issued by the PD printer 1000, issues a "StartJob" command in advance. At the same time, the PD printer 1000 which starts the print process of printing the data from the PC 3010 changes to "newJobOK" = "false". In order to notify this to the DSC 3012, the PD printer 1000 issues a "NotifyDeviceStatus" command to the DSC 3012. However, the "NotifyDeviceStatus" command issued by the PD printer 1000 is discarded, and the "StartJob" command issued by the DSC 3012 is preferentially processed. Since the PD printer 1000 has already changed "newJobOK" to "false", it returns "NotExecuted" in response to the "StartJob" command. At this time, the PD printer 1000 should reissue the "NotifyDeviceStatus" command to notify the DSC 3012 of "newJobOK" = "false". At this time, when the DSC 3012 issues the next command, the command (command) is issued almost simultaneously from both devices again.

Basically, a situation in which both devices issue a command almost simultaneously and one of them is discarded may occur when the reference state used for issuing the command from both devices is different. In this case, the direct print process is very unstable and dangerous. Accordingly, it is desirable to avoid the situation where both devices issue commands almost simultaneously. For this purpose, for example, when the DSC 3012 detects "issuance of a command from the PD printer 1000" in step S11, issuance of a "GetDeviceStatus" command is prohibited for a predetermined time in step S20 or step S17, Wait for a command from the PD printer 1000.

In addition, in the PD printer 1000 which is the counterpart of direct printing, the command issuance prohibition from the PD printer 1000 and the command wait from the DSC 3012 may be set for a predetermined time. However, if these predetermined prohibition times are exactly the same, after the predetermined time has elapsed, commands will be issued from both devices at about the same time. In view of this possibility, the predetermined time is not fixed, but may be changed discontinuously or irregularly dynamically. On the contrary, the prohibition time used in " issuance of a command by the PD printer 1000 " in step S11 is when " issuance of a command by the PD printer 1000 " is detected in step S11. It may be used up to and may be updated when "issuance of a command by the PD printer 1000" is detected in step S11. As a method of changing the issue timing of the command, the issue timing may proceed quickly. In order to prevent both devices from changing at the same timing, the timing may be changed by a predetermined rule. For example, the timing change method may be set according to a USB host or a slave. Alternatively, both the DSC 3012 and the PD printer 1000 may have means for generating an arbitrary timing signal, and the command issuing timing may be determined in accordance with the timing signal, respectively. As described above, the PD printer 1000 is also set to a state where command issuance from the PD printer 1000 is prohibited for a predetermined time, thereby reducing the possibility of issuing commands from both devices at the same time. Various modifications described above may also be applied.

Fourth Embodiment

Processing for continuing printing from the DSC 3012 of the printing system according to the fourth embodiment and processing for stopping the printing processing will be described. Also in this case, the configuration of the printing system and the configuration of the DSC 3012 and the PD printer 1000 are the same as those described above, and the description thereof is omitted.

FIG. 11 is a flowchart for describing a printing continuity process that is executed when a print button for instructing print start is designated after the print process in the DSC 3012 according to the fourth embodiment is stopped.

In step S110, it is determined whether or not the print button is specified among the operation buttons 3103 of the DSC 3012. If NO in step S110, the flow advances to step S111 to execute other processing, such as a process corresponding to the designated button or waiting for a command by the button. If the print button is specified, the process proceeds to step S112. "GetDeviceStatus" is issued to the PD printer 1000 to request the status information of the PD printer 1000, and obtain the status information transmitted from the PD printer 1000 in response to the request. The flow advances to step S113 to determine whether or not the state of the PD printer 1000 is "pause" based on the acquired state information. If YES in step S113, the flow advances to step S114 to determine whether an error has occurred and is set to "Warning" (for example, cable disconnection), or whether an error does not occur. If YES in step S114, it is determined that the restart of the print process is possible (since the state has been received from the PD printer 1000). The flow advances to step S115 to instruct the PD printer 1000 to restart print processing (send "ContinueJob").

If the "pause" state is not set in step S113 or another error occurs in step S114, it is determined that the restart of the print process is impossible, and a message about this result is displayed on the UI of the display unit 2700. Is displayed. In this case, for example, a message is displayed on the display portion 2700 to notify the user that the print process cannot be restarted and / or the selection of the print button is disabled. By acquiring the state of the PD printer 1000 before determining the press of the print button in step S110, and notifying the user whether the print button is on or off, the user can avoid pressing the print button unnecessarily. .

12 is a flowchart for describing print stop processing performed when a print stop button for instructing stop of print processing in the DSC 3012 according to the fourth embodiment is designated.

In step S121, it is determined whether or not the stop button is specified among the operation buttons 3103 of the DSC 3012. If NO in step S121, the processing flow advances to step S122 to execute other processing such as processing corresponding to the designated button or waiting for an instruction by the button. If the stop button is specified (pressed), the process proceeds to step S123. "GetDeviceStatus" is issued to the PD printer 1000 to request the current status information of the PD printer 1000, and obtain the status information sent from the PD printer 1000 in response to the request. The processing flow advances to step S124 to determine whether or not the status of the PD printer 1000 is "pause" based on the acquired status information. If YES in step S124, the flow advances to step S126, and if no, it proceeds to step S125 to determine whether printing is in progress or not. If YES in step S125, it is determined that the print processing can be stopped, and the flow advances to step S126 to instruct the PD printer 1000 to stop the print processing (send "AbortJob").

In the case of NO in step S125, it is determined that pausing of the print processing is impossible, and a message about this result is displayed on the UI of the display unit 2700. In this case, for example, a message is displayed on the display unit 2700 to notify the user that printing cannot be stopped and / or selection of the stop button is disabled. By determining the state of the PD printer 1000 and notifying the user whether the press of the stop button is valid before determining the press of the stop button in step S121, the user can avoid pressing the stop button unnecessarily.

[Example 5]

Fig. 13 is a flowchart for explaining processing in the printing system according to the fifth embodiment of the present invention. The program which executes this process is stored in the ROM 3101. Also in the fifth embodiment, the configurations of the DSC 3012 and the PD printer 1000 are the same as in the above-described embodiment, and thus description thereof is omitted.

In the fifth embodiment, when the DSC 3012 issues a command to the PD printer 1000, the response from the PD printer 1000 to the command is notified to the DSC 3012. If the response includes unexpected contents, the DSC 3012 issues "GetDeviceStatus" to the PD printer 1000 to obtain the current status of the PD printer 1000. If the acquired state is a state expected from the command issued immediately before the acquisition and the response contents thereof, general processing is executed. On the other hand, if the state is an unexpected state, processing corresponding to the state is executed.

In step S50, a "StartJob" command, which is a print start request, is issued to the PD printer 1000. The process proceeds to step S51, and when a response to the print start request is received from the PD printer 1000, the content is determined. If the above content includes "NotExecuted" indicating that the "StartJob" command cannot be executed, the flow advances to step S52 to issue a "GetDeviceStatus" command to the PD printer 1000. In step S53, the DSC 3012 waits for a response to the command from the PD printer 1000 and acquires the current state of the PD printer 1000. In step S54, the reason why the print start command has not been executed is analyzed. If the reason is found to be clear, the process proceeds to step S55 to change the UI display and wait for a command input from the user using the operation button 3103. In step S56, when a print start request is input, the process proceeds to step S50 to execute the above-described processing. On the other hand, when a command other than a print request is specified in step S50, a corresponding process is performed, but FIG. 13 omits this process.

In step S51, when the response content is not "NotExecuted", the process proceeds to step S57 to determine whether the content is "NotSupported". If the above content is "NotSupported", the process proceeds to step S58. Since the previously issued " StartJob " command is not supported by the PD printer 1000, the UI of the display portion 2700 indicates, for example, that the command is not supported by the PD printer 1000. Impossible) is displayed. Meaning that the "StartJob" command is not supported includes the case where the PD printer 1000 does not support the "StartJob" command itself, and the PD printer 1000 supports the "StartJob" command itself but is not supported. This also includes the case where the "StartJob" command currently issued is not supported because the size or paper type (unsupported item) is specified. In this case, as in the above example, by rebuilding the UI so that an inappropriate paper size or paper type cannot be selected, unsupported printing conditions can be eliminated. This may reduce the possibility of receiving "NotSupported" again from the PD printer 1000 when the "StartJob" command is issued again. At this time, for example, a process of confirming the paper size or paper type supported by the PD printer 1000 may be performed. In this manner, after the UI is changed, the processing flow advances to step S55 to wait for the next command input and proceed to the corresponding processing.

In step S57, when the response content is not "NotSupported", the process proceeds to step S59. This assumes that the response is substantially "OK". In step S59, it is determined whether or not a predetermined status notification "NotifyDeviceStatus" is transmitted from the PD printer 1000 within a predetermined time. Assume that the PD printer 1000 receives only one print job. When the "StartJob" command, which is a print start request, is issued, "newJobOK" of "NotifyDeviceStatus" should indicate "false", indicating that the PD printer 1000 cannot accept the next print job. For this reason, when a predetermined status response corresponding to the print start request is received in step S59, the process proceeds to step S63 to continue the normal operation, and then completes the operation.

In step S59, if the predetermined status information is not received within the predetermined time, the process flow advances to step S60 to issue "GetDeviceStatus" to the PD printer 1000 to obtain the status of the PD printer 1000. do. In step S61, when a response from the PD printer 1000 is received, the process flow advances to step S62 to determine whether the acquired state is an expected state corresponding to the command issued immediately before the acquisition and the response. Determine. If YES in step S62, the flow advances to step S63 to perform general processing. If an unexpected state is obtained, the process flow advances to step S64 to execute a process corresponding to the state.

An example of the "expected state corresponding to the response" in the fifth embodiment is "GetDeviceStatus" when "NotifyDeviceStatus" is not transmitted for a predetermined time even if a print start request is issued in step S50 and receives "OK". After the "is issued", it means "printing". In this case, the general processing can continue under the assumption that the issuance of "NotifyDeviceStatus" is delayed for some reason (for example, it takes a long time to transfer the image file). As a state different from the fifth embodiment, in response to the issuance of "GetDeviceStatus", a state that does not mean "printing" may be returned. In this case, various cases may be considered such that the print start request is not normally processed for some reason or printing is canceled due to the circumstances of the PD printer 1000 within a very short time after the print start request is issued. These reasons must be combined with other state information (eg error information) to determine subsequent processing. Further, by using together with the configuration according to the third embodiment, more stable direct print processing can be realized.

In the fifth embodiment, the request issuing timing changes in accordance with the processing on the image data supply side. More specifically, the image supply device (camera) issues a predetermined command to the recording apparatus (printer). After the image supply device issues the predetermined command, it is determined whether or not the signal received from the recording apparatus is a predetermined command response. When the image supply device determines that the signal is not a predetermined command response, the image supply device changes the issuing timing when issuing the next command.

However, the present invention can also be applied to an apparatus or a recording apparatus that receives image data. More specifically, the apparatus or recording apparatus that receives the image data issues a predetermined command to the image supply device. After the apparatus or recording apparatus issues a predetermined command, it is determined whether or not a signal received from the image supply device is a predetermined command response. When it is determined by the apparatus or recording apparatus that the signal is not a predetermined command response, the apparatus or recording apparatus which receives the image data changes the timing for issuing the next command.

[Sixth Embodiment]

The above embodiment mainly describes the processing in the DSC 3012. The sixth embodiment describes processing when the PD printer 1000 acquires image data from the DSC 3012. As shown in FIG. Since the hardware configuration in the sixth embodiment is the same as that in the above-described first embodiment, the description thereof is omitted.

14 is a flowchart for explaining image data acquisition processing in the PD printer 1000 according to the sixth embodiment of the present invention. The program which executes this process is stored in the program memory 3003a and executed under the control of the DSP 3002.

This process starts when a print request ("StartJob") is sent from the DSC 3012 to designate the start of the print process. In step S31, "GetFileInfo" is sent to the DSC 3012, and the DSC 3012 side requests information about a desired file. In step S32, when information (file size, attribute, etc.) relating to the image file is transmitted from the DSC 3012, an item included in the information and indicating the file capacity is obtained. The processing flow proceeds to step S33 to determine whether or not the entire image file can be received and processed at once. This is determined based on, for example, the memory capacity of the free area of the memory 3003 of the PD printer 1000. If it is determined that it is impossible to receive all the image data at once, the process proceeds to step S34 to read the image file. The start address and the read amount are specified, and request partial image data of the image file. This is done using "GetPartialFile". The DSC 3012 reads the designated partial image data from the image file in accordance with the start address and the read amount, and transmits the partial image data to the PD printer 1000. The PD printer 1000 that has received the partial image data in step S35 processes and prints the partial image data in step S36. The processing flow advances to step S37 to determine whether or not all the image data of the image file has been printed. If NO in step S37, the process flow returns to step S34 to request the next partial image data. This process is repeatedly executed until the entire image file specified in step S32 has been received and printed.

If it is determined in step S33 that the image data of the image file can be received and processed at once, the flow advances to step S38 to request the DSC 3012 for the entire data of the image file. In step S39, all image data of the image file sent from the DSC 3012 is received and printed based on the request.

15 is a flowchart for explaining another example of the image data acquisition processing in the PD printer 1000 according to the sixth embodiment of the present invention. The program which executes this process is stored in the program memory 3003a and executed under the control of the DSP 3002.

This process starts when a print request ("StartJob") is sent from the DSC 3012 to instruct the start of the print process. In step S41, "GetFileInfo" is sent to the DSC 3012 to request information about the image file designated by the DSC 3012. In step S42, when the information about the image file is transmitted from the DSC 3012, the processing flow advances to step S43 to determine whether the image file contains a thumbnail image (index image). If the image file contains a thumbnail image, the processing flow advances to step S44 to determine whether or not index printing is specified using the control unit 1010. If index printing is specified, the process proceeds to step S45 to request the thumbnail image data from the DSC 3012 (issue "GetThumb"), and obtain the data. The processing flow advances to step S46 to perform index printing based on the obtained thumbnail image data.

If the image file does not contain any thumbnail image in step S43 or index printing is not specified in step S44, the flow advances to step S33 (Fig. 14) to execute the above-described image printing process. do.

As described above, according to the sixth embodiment, the amount of image data acquired at one time from the DSC 3012 can be changed and input from the DSC 3012 in accordance with the memory capacity and processing capability of the PD printer 1000.

The fact that the thumbnail image is already stored in the image file of the DSC 3012 can be detected in advance. If index printing is specified in the PD printer 1000, the thumbnail image creation process in the PD printer 1000 can be omitted. Accordingly, the thumbnail image (index image) can be printed quickly.

The present invention may be applied to a system composed of a plurality of devices (for example, a host computer, an interface device, a reader, a printer), or a device (for example, a copier, a facsimile device) consisting of one device.

It is also an object of the present invention that a storage medium (or recording medium) storing a software program code for realizing the functions of the above-described embodiments (processes performed on the camera side and various print processes performed on the printer side) is provided. This is also achieved when the computer (or CPU or MPU) of the system or the device is supplied to the device and read and executes the program code stored in the storage medium. In this case, the program code read out from the storage medium realizes the functions of the above-described embodiment, and the storage medium storing the program code constitutes the present invention. The functions of the above-described embodiments are also realized when the computer executes the read program code. The present invention also includes a case in which the functions of the above-described embodiments are realized when an operating system (OS) or the like running on a computer performs part or all of the actual processing based on the instruction of the program code.

In addition, the present invention, after the program code read from the storage medium is recorded in the memory of the function expansion card inserted into the computer, or the memory of the function expansion unit connected to the computer, based on the instruction of the program code, the function This includes the case where the CPU of the expansion card or the function expansion unit realizes the functions of the above-described embodiments by performing some or all of the actual processing.

As described above, according to the present embodiment, when the cable connecting the DSC and the PD printer is disconnected, when the print processing in the printer is stopped, and the cable is restarted, the print processing can be restarted. After that, the print process can be reliably resumed printing.

At the time of the printing restart according to either the print processing based on the DPOF file or the print processing of the image data sequentially transmitted from the DSC to the printer, the image data resent from the DSC to the printer is changed. In either case, printing can be reliably restarted.

When the DSC according to the present embodiment issues a command such as StartJob or AbortJob to the printer, even if there is no response from the printer, the DSC may assume that a predetermined state is set and determine the next operation. The DSC may further issue a command to the printer to confirm the status, thereby identifying the current status (status) of the printer.

If the PD printer returns a specific status as a response to the DSC, the DSC proceeds to the corresponding process. For example, in the case of "NotExecuted" or "NotSupported", the DSC issues a command for querying the state of the printer with respect to the former command, and determines the next command to be issued based on the response. For the latter command, since the previously issued command is not supported by the printer, the DSC executes a process of changing the UI displayed on the display, for example, so as not to issue the same command later. This can prevent unwanted commands from being resent to the printer.

Also, if the PD printer and the DSC issue a command at about the same time, both or at least one of the devices prohibits the issue of the command for a predetermined time. This can reduce the possibility of issuing commands from both devices at about the same time.

According to this embodiment, the amount of image data acquired at one time from the DSC can be adjusted in accordance with the printer's memory capacity or processing capacity. Image data can be accepted, processed and printed.

The present invention is not limited to the above embodiments, and various changes and modifications can be made within the spirit and scope of the present invention. Therefore, to apprise the public of the scope of the present invention, the following claims are made.

Claims (32)

An image supply device for use in a recording system in which an image supply device and a recording apparatus communicate with each other via a communication interface, and image data is transmitted and recorded from the image supply device to the recording apparatus. Receiving means for receiving status information from the recording apparatus; Determining means for determining whether or not the receiving means has received status information from the recording apparatus within a predetermined time after the image supply device issues a command to the recording apparatus; When the judging means determines that the state information has not been received within a predetermined time, it is determined that the state of the recording apparatus is a state predicted from the general process, and the processing means for continuing the process in the image supply device. An image supply device, characterized in that provided. The method of claim 1, If the determining means determines that the status information is not received after the command is issued, the processing means predicts that the state of the recording apparatus is a state in which the next command cannot be received, and in the image supply device And continue the processing of the image supply device. The method of claim 1, Display means for displaying a user interface image; And UI changing means for changing the user interface image displayed on the display means in accordance with the state information received by the receiving means. The method of claim 1, And requesting means for requesting status information from the recording apparatus. delete delete A recording system in which an image supply device and a recording device communicate with each other via a communication interface, and image data is transmitted and recorded from the image supply device to the recording device, Transmitting means for transmitting status information from the recording apparatus to the image supply device; Determining means for determining whether or not the image supply device has received status information within a predetermined time after the image supply device issues a command to the recording apparatus; When the judging means determines that the state information has not been received from the recording apparatus within the predetermined time, it is determined that the state of the recording apparatus is a state predicted from the general processing, and the processing in the image supply device is performed. And a processing means for continuing. The method of claim 7, wherein If the determining means determines that the status information is not received after the image supply device issues the command, the processing means predicts that the state of the recording apparatus is a state in which the next command cannot be received, And continue the processing in the image supply device. The method of claim 7, wherein The image supply device, Display means for displaying a user interface image; And UI changing means for changing the user interface image displayed on the display means in accordance with the state information received by the receiving means. The method of claim 7, wherein And requesting means for requesting status information from said image supply device to said recording apparatus. delete A control method of a recording system in which an image supply device and a recording apparatus communicate with each other via a communication interface, and image data is transmitted and recorded from the image supply device to the recording apparatus. A transmitting step of transmitting status information from the image supply device to the recording apparatus; In the transmitting step, after the image supply device issues a command to the recording apparatus, a determination step of determining whether or not the image supply device has received status information from the recording apparatus within a predetermined time; In the judging step, when it is determined that state information has not been received within the predetermined time, it is determined that the state of the recording apparatus is a state predicted from a general process, and the process of continuing the process in the image supply device. Control method of a recording system, characterized in that it comprises a step. The method of claim 12, A display step of displaying a user interface image; And a UI changing step of changing the user interface image displayed in the display step according to the state information received in the receiving step. An image supply device for use in a recording system in which an image supply device and a recording apparatus communicate with each other via a communication interface, and image data is transmitted and recorded from the image supply device to the recording apparatus. Command issuing means for issuing a command to the recording apparatus; Receiving means for receiving a signal from the recording apparatus after the command issuing means issues the command; Determining means for determining whether a signal received by the receiving means is a response corresponding to the command; And control means for controlling the issuing timing of the next command to the recording apparatus when the determining means determines that the signal is not a response corresponding to the command. The method of claim 14, And when the determining means determines that the signal is not a response corresponding to the command, the control means delays the timing of issuing the next command. The method of claim 15, And when the determining means determines that the signal is not a response corresponding to the command, the control means arbitrarily changes a time for delaying the issuance timing of the next command. The method of claim 15, Each time the determination means determines that the signal is not a response corresponding to the command, the control means updates a time for delaying the issuance timing of the next command. A recording apparatus for use in a recording system in which an image supply device and a recording apparatus communicate with each other via a communication interface, and image data is transmitted and recorded from the image supply device to the recording apparatus. Command issuing means for issuing a command to the image supply device; Receiving means for receiving a signal from the image supply device after the command issuing means issues the command; Determining means for determining whether a signal received by the receiving means is a response corresponding to the command; And control means for controlling the issuing timing of the next command to the image supply device when the determining means determines that the signal is not a response corresponding to the command. The method of claim 18, And when the determining means determines that the signal is not a response corresponding to the command, the control means delays the timing of issuing the next command. The method of claim 18, And when the determining means determines that the signal is not a response corresponding to the command, the control means arbitrarily changes the time for delaying the issuance timing of the next command. The method of claim 19, Each time the determining means determines that the signal is not a response corresponding to the command, the control means updates a time for delaying the issuance timing of the next command. An image supply device for use in a recording system in which an image supply device and a recording apparatus communicate with each other via a communication interface, and image data is transmitted and recorded from the image supply device to the recording apparatus. Command issuing means for issuing a command to the recording apparatus; Receiving means for receiving a signal from the recording apparatus after the command issuing means issues the command; Determination means for determining whether the signal received by the reception means is a response corresponding to the command; Processing means for continuing communication processing between the image supply device and the recording apparatus when the determination means determines that the signal is a response corresponding to the command; And the requesting means for requesting status information from the recording apparatus when the determining means determines that the signal is not a response corresponding to the command. delete A control method of a recording system in which an image supply device and a recording apparatus communicate with each other via a communication interface, and image data is transmitted and recorded from the image supply device to the recording apparatus. A command issuing step of issuing a command between the image supply device and the recording apparatus; A determination step of determining whether or not a signal received from a counterpart is a response corresponding to the command after the command is issued in the command issuing step; And in the determining step, when it is determined that the signal is not a response corresponding to the command, changing the issuing timing of the next command in at least one of the image supply device and the recording apparatus. Control method of recording system. The method of claim 24, And when it is determined in the determining step that the signal is not a response corresponding to the command, in the changing step, the timing of issuing the next command is delayed. The method of claim 25, And when it is determined in the determining step that the signal is not a response corresponding to the command, in the changing step, the timing of issuing the next command is arbitrarily changed. The method of claim 25, Whenever it is determined in the determining step that the signal is not a response corresponding to the command, in the changing step, the timing of issuing the next command is updated. A control method of a recording system in which an image supply device and a recording apparatus communicate with each other via a communication interface, and image data is transmitted and recorded from the image supply device to the recording apparatus. A command issuing step of issuing a command between the image supply device and the recording apparatus; A determination step of determining whether or not a signal received from a counterpart is a response corresponding to the command after the command is issued in the command issuing step; In the determination step, when it is determined that the signal is a response corresponding to the command, a processing step of continuing a communication process between the image supply device and the recording apparatus; And in the determination step, a request step of requesting status information from the counterpart when it is determined that the signal is not a response corresponding to the command. delete A computer-readable storage medium storing a program for executing the control method of the recording system according to claim 24. The method of claim 14, And if the determining means determines that the signal is not a response corresponding to the command, further comprising means for discarding the signal and waiting for a response corresponding to the command issued by the command issuing means. Image supply device. The method of claim 18, If the determining means determines that the signal is not a response corresponding to the command, the control means preferentially processes a command from the image supply device and corresponds to the signal received by the receiving means. And a recording device for issuing a response.

Images