JP4556493B2 - Information processing device - Google Patents

Description

  The present invention relates to an information processing apparatus that performs information processing such as image output based on information such as image data, such as an image forming apparatus such as a printer or a copier using an electrophotographic system or an inkjet system, and more particularly a controller or the like. The present invention relates to an information processing apparatus capable of maintaining the correspondence of commands between the first apparatus and a second apparatus such as a printer engine.

JP 2000-222334 A JP 2001-92604 A

  2. Description of the Related Art Conventionally, in an image forming apparatus such as a printer or a copier that employs this type of electrophotographic system or ink jet system, image output is performed by communicating between a controller and an image output apparatus (IOT), for example. Some are configured to control a device, such as an apparatus (IOT). In the case of such an image forming apparatus, in order for the controller to control the image output apparatus (IOT), the controller that is the controlling side grasps the state of the image output apparatus (IOT) that is the controlled side. It is necessary to keep. For this reason, messages are exchanged between the controller and the image output device (IOT) so that the controller always keeps track of the state of the image output device (IOT).

  However, the message is exchanged between the controller and the image output device (IOT) by serial communication or the like, so that a certain amount of time is required for communication, and communication cannot be performed in real time, mainly communication delay. For this reason, there may be a temporary shift between the state of the image output device (IOT) recognized by the controller that is the controlling side and the state of the actual image output device (IOT). Normally, the difference between the state of the image output device (IOT) recognized by the controller and the state of the actual image output device (IOT) is not a problem, but inconvenience occurs in the following cases. There is a fear.

That is, in the case of the said prior art, it has the following problems.
FIG. 13 shows a case where the system is reset for some reason or the system is restarted after the printer engine as an image output device (IOT) has sent a notification of the completion of printing of the second page to the controller. A sequence is shown.

  In this case, as viewed from the printer engine side, as shown in FIG. 13B, whether the controller side has normally received and processed the second page print completion notification is shown in FIG. 13A. In this way, before the controller side receives the second page print completion notification, it is determined whether a system reset factor has occurred and the second page print completion notification could not be received normally and was not processed. Can not do it. In the case shown in FIG. 13A, the controller side cannot determine whether or not the printer engine has completed the printing operation for the second page and has transmitted a printing completion notification for the second page. Although the print completion notification of the second page has been transmitted from the printer engine, it cannot be determined whether it has not been received normally or whether the second page has been notified of completion.

  FIG. 14 further shows a specific example when a communication error occurs between the controller and the printer engine.

  FIG. 14A shows a case where the printer engine transmits an error notification to the controller after the printer engine receives the second print instruction from the controller, and also continuously transmits the error resolution notification to the controller after the error is resolved. It is shown. FIG. 14B shows a state in which the printer engine sends an error notification to the controller immediately before the printer engine receives the second print instruction from the controller, and the printer engine receives the second print instruction. This shows a case where the printer engine sends an error resolution notification to the controller. Further, FIG. 14C shows that before the printer engine sends the second print instruction from the controller, the printer engine sends an error notification to the controller, and before the printer engine receives the error notification, the controller This shows a case where the print instruction is transmitted to the controller by the printer engine before transmitting the print instruction for the second sheet and before the printer engine receives the print instruction for the second sheet.

  14A, 14B, and 14C, when viewed from the controller, an error occurs when an error notification is received immediately after the second print instruction is sent to the printer engine. In addition to knowing that it has been received, an error resolution notification is received, and it can be seen only as if the error has been resolved immediately.

  As shown in FIGS. 14 (a), 14 (b), and 14 (c), a completely different state occurs on the printer engine side, so that the following problems may occur depending on the specifications of the printer engine. Become.

  That is, when the printer engine is configured to simply clear the previous print instruction when an error occurs or when the error is resolved, that is, as shown in FIG. 14B, all print instructions are cleared. On the other hand, in the case shown in FIG. 14C, since the second print instruction is received after the error cancellation notification, the second print instruction remains as it is. . For this reason, the controller side cannot identify the states shown in FIGS. 14A, 14B, and 14C, and in some cases, the second sheet is not printed or the second sheet is not printed. There has been a problem that inconveniences such as redundant printing occur.

  FIG. 15 shows an example of the operation at the start of the operation of the control software between the controller and the printer engine.

  As shown in FIG. 15, when the operation of the control software starts, the controller transmits messages 1 and 2 for information exchange to the printer engine. On the other hand, if the printer engine software that should receive these messages 1 and 2 starts operating, the information exchange starts as it is, but if the printer engine software does not start operating, it is sent from the controller. There is a disadvantage that the messages 1 and 2 are wasted.

  At that time, at least the software of the communication part is operating in the controller itself, and the message transmission itself is normally completed. Therefore, the controller determines whether or not the transmitted message is normally transmitted to the software on the printer engine side. Can only be known by receiving a response to the message. Therefore, the controller is configured to appropriately set the timeout time and continue to send the same message until a response is returned. As a result, if the timeout time is set short, the response is improved, but there is a problem that the load on the controller increases, for example, the controller must frequently send messages.

  Also, if the printer engine software is restarted when an error occurs, the procedure must be restarted from the beginning. However, the controller does not send a message to the printer engine or does not send a message to the printer engine. There is a problem that it is not possible to know whether it has been restarted.

  Therefore, the present invention has been made to solve the above-described problems of the prior art, and it is assumed that there is at least a first device such as a control device and a second device such as a controlled device. In the information processing device configured to control the second device by the first device by communicating with each other, communication of commands and the like between the first device and the second device It is an object of the present invention to provide an information processing apparatus that can reliably determine whether or not the communication has been normally performed and can maintain communication of commands and the like.

In order to solve the above problems, the invention described in claim 1 includes at least a controller and a printer engine for exchanging information by communicating with each other, and at least one device operates in cooperation with the other device. In an information processing apparatus that processes information by performing
The controller is
Prior notification means for informing the printer engine in advance that the cooperative operation cannot be continued when the controller detects a restart factor ;
Response waiting means for waiting for a confirmation response from the printer engine ;
Processing means for processing information received before waiting for a confirmation response from the printer engine ;
An execution means for executing a restarting operation upon receipt of a confirmation response of the prior notification from the printer engine ;
With
The printer engine is
Receiving means for receiving notification from the controller that a restart factor has been detected ;
When receiving a notification that the cooperative operation cannot be continued, the information processing apparatus includes response means for returning a response indicating that the notification is received to the controller .

  According to a second aspect of the present invention, in the information processing apparatus according to the first aspect, the response waiting means treats a response as a response when there is no response for a predetermined time.

  Furthermore, the invention described in claim 3 is the information processing apparatus according to claim 1 or 2, wherein the processing means does not process information that is wasted even if processing is performed.

  According to a fourth aspect of the present invention, in the information processing apparatus according to any one of the first to third aspects, the processing means does not process information received after the response means returns a response. Device.

Furthermore, the invention described in claim 5 is characterized in that the processing means does not process only the processing that affects the state of the controller when processing is performed on the information received after the response means returns a response. An information processing apparatus according to any one of claims 1 to 3.

According to a sixth aspect of the present invention, in the information processing apparatus according to any one of the first to fifth aspects, the notification unit notifies the information on whether or not the influence of the return processing of the controller affects the printer engine. The information processing apparatus described.

Furthermore, the invention described in claim 7 includes at least a controller and a printer engine for exchanging information by communicating with each other, and at least one of the devices performs an operation in cooperation with the other device. In the information processing apparatus that processes
The controller is
Prior notification means for informing the printer engine in advance that the cooperative operation cannot be continued when the controller detects a restart factor ;
Response waiting means for waiting for a confirmation response from the printer engine ;
Processing means for processing information received before waiting for a confirmation response from the printer engine ;
An execution means for executing a restarting operation upon receipt of a confirmation response of the prior notification from the printer engine ;
With
The printer engine is
Receiving means for receiving notification from the controller that a restart factor has been detected ;
When receiving a notification that the cooperative operation cannot be continued, a response means for returning a response indicating that the notification has been received to the controller ;
Post-processing means for performing post-processing for terminating the cooperative operation;
An information processing apparatus characterized by comprising:

  The invention described in claim 8 is the information processing apparatus according to claim 7, wherein the post-processing performed by the post-processing means is saving of the apparatus state to the nonvolatile storage means. .

  Furthermore, the invention described in claim 9 is the information processing apparatus according to claim 7, wherein the post-processing performed by the post-processing means is retraction of the apparatus mechanism to an appropriate position.

  The invention described in claim 10 is the information processing apparatus according to claim 7, wherein the post-processing performed by the post-processing means is a complete stop of the information processing operation.

  According to the present invention, in an information processing apparatus configured to control a controlled device by the control device by communicating with each other between the control device and the controlled device, the control device and the controlled device It is possible to reliably determine whether or not communication of commands or the like has been performed normally, and it is possible to provide an information processing apparatus capable of maintaining correspondence of communication of commands or the like.

  Embodiments of the present invention will be described below with reference to the drawings.

Embodiment 1
FIG. 2 is a block diagram showing a printer as an image processing apparatus according to the first embodiment.

  As shown in FIG. 2, the printer 100 includes a controller 200 as a first device and a printer engine 300 as a second device. The controller 200 provides functions for a CPU 201 that controls the controller 200 and the printer engine 300, a RAM 202 that is used as a work area, a ROM 203 that stores basic software such as a bootstrap, and complicated controls and functions for users. Therefore, the hard disk 204 for storing software and the like, a network interface controller 205 for connecting to a network, and a serial interface controller 206 for communicating with the printer engine 300 are provided.

  On the other hand, the printer engine 300 communicates with the controller, as shown in FIG. 2, a CPU 301 that controls the printing operation of the printer engine 300, a RAM 302 that is used as a work area, a ROM 303 that stores control software, and the like. A serial interface controller 304 for printing and a printing device 305 used for printing.

  The controller 200 and the printer engine 300 are connected to each other through a communication line 400 so that they can communicate with each other. The controller 200 and the printer engine 300 are connected to each other by serial interface controllers 206 and 304 through the communication line 400. The printer engine 300 is configured to control a printing operation as an information processing operation.

  FIG. 1 is a logical configuration diagram when the configuration of the printer is functionally represented.

  As shown in FIG. 1, information is exchanged between the controller 200 and the printer engine 300 using the communication modules 210 and 310. The communication modules 210 and 310 are provided in both the controller 200 and the printer engine 300, and enable communication while initializing hardware and software as appropriate. The communication modules 210 and 310 are configured to manage communication buffers and perform appropriate communication between the controller 200 and the printer engine 300.

  The controller 200 is further provided with a system control module 211 that controls the system, a function module 212 that realizes each function of the controller, and a network communication module 213.

  The network communication module 213 performs input / output control related to the network 500. The network communication module 213 has a function of receiving, for example, data to be printed described in PDL (Page Description Language) from a host computer (not shown). The function module 212 is for realizing each function of the controller 200. For example, the function module 212 creates (renders) a printing bitmap from print data described in PDL received from the network 500, Or realize a function.

  Further, the system control module 211 is for controlling the entire system, and functions to control the engine control module 311 of the printer engine 300 via the communication module 210. The system control module 211 and the engine control module 311 communicate with each other via the communication modules 210 and 310, but the message communication start between the control modules 211 and 311, the buffer initialization instruction before the message communication start, etc. The control modules 211 and 311 perform, and the communication modules 210 and 310 only ensure that communication with the communication modules 210 and 310 on the other side is possible.

  The printer engine 300 is provided with an engine control module 311 in addition to the communication module 310, and the engine control module 311 is configured to control a printing operation in accordance with an instruction from the system control module 211. Yes.

  By the way, in this embodiment, as shown in FIG. 1, at least a controller 200 and a printer engine 300 that exchange information by communicating with each other are provided, and at least one device operates in cooperation with the other device. By doing so, in the printer 100 that processes information, the controller 200 communicates with the communication module 210 as notification means for notifying the printer engine 300 that the controller 200 cannot continue the cooperative operation, and the response from the printer engine 300. A system control module 211 serving as a response waiting means for waiting for a response, and a function module 212 for processing information received until a response from the printer engine 300 is waited. Communication module 310 as a receiving means for receiving a notification that the notification cannot be continued, and a response means for returning a response indicating that the notification has been received to the controller 200 when receiving a notification that the cooperative operation cannot be continued. An engine control module 311 is provided.

  In the above configuration, the printer according to this embodiment is configured to control the controlled device by the control device by communicating with each other between the control device and the controlled device as follows. In the information processing apparatus, it is possible to reliably determine whether or not communication of commands or the like has been normally performed between the control device and the controlled device, and maintain correspondence of communication of commands or the like. It is possible.

  That is, in this embodiment, when the controller 200 detects a reset factor, an operation as shown in the flowchart of FIG. 3 is executed.

  First, when a factor for resetting occurs, the system module 211 of the controller 200 notifies the printer engine 300 that resetting is to be performed with a reset advance notification, as shown in FIG. 4, via the communication module 210 (step 101). . Here, examples of the reset factor include a reset request by the user and a reset factor set in advance in the system function module 211. At this time, the reset prior notification is set with a flag for notifying whether the entire system including the printer engine 300 is reset or only the controller 200 is reset.

  Next, the controller 200 prepares in advance for executing the reset process (step 102). Examples of the advance preparation include saving cache data to the hard disk 204.

Further, the controller 200 sets a predetermined time-out time (step 103), and waits until a confirmation response for the prior reset notification is returned from the printer engine 300. Meanwhile, the controller 200 is configured to process only output information that is meaningful as information even if it is reset, among the information sent from the printer engine 300. It should be noted that even if the controller 200 receives other information, it simply ignores it.

  Actually, the controller 200 performs the operation as shown in FIG. 5 while waiting for the confirmation response. When the controller 200 is in the state of waiting for a reset prior confirmation response (step 201), the controller 200 manages how far the page of the document has been output only in the case of a message notifying the printed page. For this reason, the printed page is updated (step 202). Further, as shown in FIG. 3, when the controller 200 receives the confirmation response of the advance notification from the printer engine 300 (step 104), the controller 200 naturally goes out of the confirmation response waiting state of FIG. 4 and executes the reset operation. (Step 105). In the case of a message other than this, the controller 200 is reset even if it is processed, so it simply acquires the message without performing the process. Further, the controller 200 is set to exit from the confirmation response waiting state as a timeout as shown in FIG. 5 even when the confirmation response to the prior reset notification is not notified within a certain time.

  This is because, when the controller 200 waits for the confirmation response of the reset prior notification, if the response from the printer engine 300 is not longer than a predetermined time, a timeout time is set in advance so as to forcibly reset. It is.

  On the other hand, as shown in FIG. 3, the printer engine 300 side performs the following operation when it receives a prior reset notification.

  First, as shown in FIG. 3, the printer engine 300 determines whether or not the printing process is in progress (step 106). If the printing process is in progress, the printer engine 300 starts the stop process of the printing operation (step 107). . This printing operation stop process is performed as quickly as possible. The reason is that there is no guarantee that information is sent from the controller 200 side because a factor causing the reset is generated on the controller 200 side. On the other hand, if the printer engine 300 is not printing, the process proceeds to the next process.

  Next, the printer engine 300 transmits the minimum necessary information that has not yet been transmitted but must be transmitted to the controller 200 (step 108). The minimum necessary information is information on the state of the printer engine 300 that is normally managed regardless of whether the power is on or off. Thereafter, the printer engine 300 determines whether or not the printer engine 300 is also reset at the same time (step 109). If it is notified by the reset advance notification that the printer engine 300 is also reset at the same time, the printer engine 300 is reset. If so, a process is prepared (step 110). For example, when the printer engine 300 is reset at the same time as the controller 200, the printer engine 300 must be surely stopped, so that the stop process is performed. In this case, when only the controller 200 is reset, it is assumed that the print engine 300 can complete the stop process without a response from the controller 200. In the case of resetting only the controller 200, the printer engine 300 does nothing at this time. Finally, as shown in FIG. 4, the printer engine 300 returns a response to the reset advance notification (step 111), and there is no more information to be processed before the controller 200 is reset. Is supposed to be notified.

  Note that a message from immediately after returning a response to the prior reset notification until the actual reset is performed may be transmitted to the controller 200. These messages are transmitted for reasons such as ease of implementation, but do not affect the controller 200 in any way.

  FIG. 6 is an explanatory diagram showing a transmission / reception message used in this embodiment.

  Here, a system reset notification flag is transmitted together with the reset advance notification. When the entire system of the printer 100 is reset together with the controller 200, the fact is notified. It has become.

  As described above, in the first embodiment, when the controller 200 is reset for some reason, the controller 200 transmits a reset advance notice to the printer engine 300, and the printer engine 300 confirms the reset advance notice. Is configured to perform a reset operation after receiving the signal. For this reason, it is possible to reliably determine whether or not communication of a command such as a reset notification has been normally performed between the controller 200 and the printer engine 300, and it is possible to maintain communication of the command and the like. It has become.

Embodiment 2
In the second embodiment, the basic configuration of the apparatus is the same as that of the first embodiment, and FIG. 7 shows the characteristic part of the second embodiment. To describe with the same reference numerals, the second embodiment includes at least a first device and a second device that exchange information by communicating with each other, and at least one device is the other device. In the information processing apparatus that processes information by performing an operation in cooperation with the first apparatus, the first apparatus transitions the operation state of the first apparatus to the second operation state when a specific condition occurs. Transition means, notification means for notifying the second device that a specific condition has occurred, recognition means for causing the second device to recognize that the specific condition has been resolved, and the specific condition Second action when it is resolved And it is configured to be provided with a return means for returning to the state of the original operating state of the first device.

  In this embodiment, the specific condition is that the first device detects an error.

  Further, in this embodiment, the means for notifying the second device that the specific condition has occurred is configured to be notified by the first device.

  In this embodiment, the means for the second device to recognize that the specific condition has been resolved is configured to be notified by the first device.

  Furthermore, in this embodiment, a part of the information is not processed and ignored during the transition to the second operation state.

  That is, in the printer according to the second embodiment, a correspondence example when an error occurs is shown.

  FIG. 7 is a state transition diagram of the operation performed by the controller when an error occurs.

  As shown in FIG. 7, the controller 200 first operates in a normal processing state (first operation state) (step 301). Next, when notified from the printer engine 300 that an error has occurred, the controller 200 transitions to an error processing state (second operation state) (step 302). While an error occurs, the controller 200 issues an instruction to the user using a UI (user interface) or the like, and executes an operation for eliminating the error. Here, since there is no relation with the means for error elimination, no further explanation will be given. In addition, even if another error newly occurs in the error processing state, the controller 200 remains in the error processing state and remains in the error processing state. On the other hand, when the error is eliminated by the user, the controller 200 notifies the printer ethidine 300 that the error handling state is to be released, and transitions to a normal processing state (step 301). At this time, since all the print instructions held by the printer engine 300 without completing printing are regarded as being discarded, the controller 200 newly starts again from the print instructions.

  FIG. 8 is a state transition diagram of the printer engine when an error occurs.

  In FIG. 8, a normal operation state (first state) means a state in which the printer engine 300 can perform a print operation (step 401). When an error occurs in the printer engine 300 in this state, the printer engine 300 transmits an error occurrence notification to the controller 200 as shown in FIG. 9, and transitions to an error occurrence state (second state) ( Step 402). In the error occurrence state, even if a new error occurs thereafter, there is no change in the error occurrence state, so there is no change in state. Further, when the error is resolved in the error occurrence state, the printer engine 300 immediately transmits the error resolution notification to the controller 200 without shifting to the normal operation state, and the error resolved state (second state). (Step 403).

  The error occurrence state and the error-resolved state are mutually different sub-states in the state of the error handling state as the second state. That is, if the error is solved, as shown in FIG. 9, it remains in the error handling state and does not immediately return to the normal operation state. In the error handling state, processing such as paper feed tray selection switching is executed, but all new print instructions from the controller 200 are ignored. The printer engine 300 transitions to the normal operation state only when the error handling state cancellation notification (see FIG. 7) for the error cancellation completion notification notified in the error cancellation completed state comes from the controller 200 (step 401). At this time, if the printer engine 300 transmits the error-resolved notification a plurality of times in the error-resolved state, an error handling state release notification for the last-resolved error-resolved notification has arrived from the controller 200. Only when the transition to the normal operation state (step 401).

  That is, as shown in FIG. 8, when a new error occurs in the error-resolved state, the printer engine 300 transmits an error occurrence notification to the controller 200 and transitions to the error-occurring state again. Then, when the error is solved in the error occurrence state and the transition to the error eliminated state is made, an error eliminated notification may be transmitted to the controller 200 again.

  At that time, in order to identify the error handling state release notification for the last error-resolved notification, the error-resolved notification is distinguished by attaching an ID (identification code) or only according to the number of error-resolved notifications. The error handling state release notification is received, so that it is identified that the error handling state release notification for the last error resolved notification has been received.

  If there is a print instruction from the controller 200 that has not been printed when the error handling state transitions to the normal operation state, these print instructions are discarded.

  As described above, in the second embodiment, when an error occurs in the normal operation state in the printer engine 300, the controller 200 is notified of the error and the state is changed to the error occurrence state. Further, when the error is resolved, the printer engine 300 notifies the controller 200 to that effect and immediately shifts to the error-resolved state which is a sub-state without shifting to the normal operation state. Only when the error handling state release notification corresponding to the notified error-resolved notification has arrived from the controller 200, it is configured to transition to the normal operation state.

  Therefore, in the second embodiment, after the printer engine 300 transmits an error-resolved notification to the controller 200, even if an error occurs for some reason, an error handling state release notification for the error-resolved notification has arrived from the controller 200. Until the printer engine 300 maintains an error handling state, the printer engine 300 and the controller 200 can know that the error state has not been completely eliminated. It is possible to reliably determine whether or not the communication of the command such as the print instruction has been normally performed, and the correspondence of the communication of the command or the like can be maintained.

Embodiment 3
In the third embodiment, the basic configuration of the apparatus is the same as that of the first embodiment, and FIG. 10 shows the characteristic part of the third embodiment. To describe with the same reference numerals, the third embodiment includes at least a first device and a second device that exchange information by communicating with each other, and at least one device is the other device. In the information processing apparatus that processes information, the first apparatus and the second apparatus are operable to notify the other apparatus that one apparatus is operable. Upon receiving the notification means and the notification that the one device is operable from the other device and confirming that the other device is operable, the other device is notified that the one device has been confirmed. Confirm response And at least one of the first device and the second device has notified the operation confirmation notification by the operable notification device or has received the confirmation response by the confirmation response device. On the condition, control means for controlling to transition to a specific operation state is provided.

  In the third embodiment, the fact that the one device is operable is configured so that software for controlling the one device has started operation.

  Further, in the third embodiment, a plurality of different operation states are set as the specific operation state.

  In the third embodiment, the specific operation state is configured such that the state to be changed differs depending on whether an operation confirmation notification is sent or a confirmation response is received by the confirmation response unit.

  FIG. 10 is a state diagram showing the state transition of the operation of the control module. Here, only the state relating to the operation start is particularly noted, and the other states are simplified.

  Here, for the sake of explanation, it is assumed that the system control module 211 of the controller 200 has started operation, but the same applies when the control module 311 of the printer engine 300 starts operation. That is, in the present invention, it is basically assumed that the first device and the second device exist, but which of the controller 200 and the printer engine 300 corresponds to the first device and which is the second device. The controller 200 may correspond to the first device, and the printer engine 300 may correspond to the first device.

  In FIG. 10, the initialization state is a state in which the system control module 211 is performing initialization necessary at the time of module activation (step 501). This initialization state includes an operation of clearing unnecessary messages that may cause a malfunction, such as a message that arrives before the operation starts. For this reason, all messages that have arrived at the controller 200 before the initialization state are lost.

  Next, when the initialization operation is completed, the controller 200 sends a notification that it is operable to the engine control module 311 of the printer engine 300, and transitions to the next processable state (one of the specific operation states). (Step 502). In this processable state, a message from the printer engine 300 is awaited. Of the messages from the printer engine 300, only when an operable notification or confirmation response is received, a transition to a temporary normal state or a normal state, which is one of the following specific operation states, is performed. When the controller 200 is in the processable state, the state in which the operation ready notification is received is, for example, as shown in FIG. 11A, when the controller 200 transmits the operation ready notification. This occurs when the message of the controller 200 is discarded. In this case, after the controller 200 transmits a confirmation response to the printer engine 300, a transition is made to the provisional normal state shown in FIG. 10 (step 503).

  On the other hand, in the case shown in FIG. 11B, after the controller 200 transmits an operable notification and transits to the processable state, an acknowledgment response to the operable notification is received. In this case, as shown in FIG. 10, the processable state transitions to the normal state (step 504). The difference between the temporary normal state and the normal state is a difference in handling of the confirmation response from the printer engine 300. In the normal state, unless the software has a bug or the like, the confirmation response is not received. Therefore, when the confirmation response is received in the normal state, it is handled as an error in principle. In the case of the provisional normal state, since a state as shown in FIG. 11C occurs, there is a possibility that a confirmation response is received.

  More specifically, in the state shown in FIG. 11C, after the controller 200 transmits an operable notification and transits to the processable state, it receives the operable notification from the printer engine 300 and transits to the temporary normal state. Further, since the confirmation response from the printer engine 300 is received, the normal state is entered.

  As shown in FIG. 10, when the controller 200 receives a normal message regarding control from the printer engine 300 when the state is the provisional normal state, the controller 200 transitions to a message execution state (step 505). This message execution state is a state in which a normal message is being executed. When the execution of the message ends, the controller 200 transitions to a normal state (step 504).

  Further, when receiving a response message in the provisional normal state, the controller 200 simply transitions to the normal state (step 504). The normal state is a state in which messages relating to control such as a print instruction are exchanged. Then, every time a new message is received, the controller 200 transitions to the message execution state, and the message processing is performed (steps 504 and 505).

  Incidentally, the state shown in FIG. 10 includes a state where the engine control module 312 of the printer engine 300 is suddenly initialized and the operation is started from the beginning. This also applies to a case where the restart notification cannot be notified to the controller 200 due to a problem such as a sub-module related to message transmission of the engine control module 311.

  The fact that the engine control module 312 of the printer engine 300 has been initialized can be determined by transmitting an operable notification from the printer engine 300. Theoretically, in any state shown in FIG. 10, there is a possibility that an operable notification may be transmitted, but it is simply ignored in the initialization state, and when received in the processable state As described above, the state transits to the provisional normal state. When in the message execution state, since it cannot be recognized that the received message has been received until the normal state is restored, the message reception is delayed until the transition to the normal state.

  Therefore, what is important is when an operational notification is received in the temporary normal state or the normal state, as shown in FIG. In this case, as shown in FIG. 10, the state is shifted to the end initialization state in either state (step 506). In this end initialization state, end processing for ending the printing operation, minimum initialization necessary for returning the system state to the initial state, and the like are performed. For example, when a print process is being performed, the work area such as the RAM 202 is initialized, such as discharging a paper sheet during printing, a cleaning operation, or clearing a queue that holds a print instruction. When the end initialization process ends, the process transits to a processable state (step 502). At this time, an operable notification is transmitted from the controller 200 to the printer engine 300. Subsequent processing is the same as when the normal control module 212 is activated.

  More specifically, as shown in FIG. 12 (a), when the controller 200 is in a normal operation state, if an operational notification is sent from the printer engine 300 due to an unintended restart of the control module, etc., The controller 200 transitions to the end initialization state and starts the end initialization process. When the end initialization process is completed, the controller 200 transitions to a processable state and transmits an operable notification. On the other hand, when a confirmation response is received from the printer engine 300, a transition is made to the normal state, and when a further normal message is received, a transition is made to the message execution state.

  Also, in FIG. 12B, unlike FIG. 12A, when the controller 200 is in a normal operation state, an operable notification is sent from the printer engine 300 due to an unintended restart of the control module or the like. Then, the controller 200 transitions to the end initialization state and starts the end initialization process. When the end initialization process is completed, the controller 200 transitions to a processable state and transmits an operable notification. When an operation enable notification is sent again from the printer engine 300 due to an unintended restart of the control module in this state, the controller 200 transmits a confirmation response and transitions to the temporary normal state as shown in FIG. To do.

  Thereafter, the controller 200 transitions to a normal state when receiving a confirmation response to the operable notification from the printer engine 300, and further transitions to a message execution state when receiving a normal message. After executing the message, the controller 200 enters the normal state. Transition again.

  As described above, in the third embodiment, for example, depending on whether the controller 200 has notified the operation confirmation or received the confirmation response, the process can be performed from the initialization state, the provisional normal state, the normal state, and the message execution state. , It is configured to sequentially transition to an end initialization processing state, etc., and instructions such as operation confirmation notifications and confirmation responses and the state of the controller 200 always correspond one-to-one, and the operation confirmation notifications are normal. Even if it is not received or the arrival of the operation confirmation notification and the confirmation response is changed, the operation can be performed by appropriately transitioning to a specific operation state according to each state, and the controller 200 and the printer engine 300 can be executed. It is possible to maintain communication of commands and the like.

FIG. 1 is a block diagram showing a printer as an information processing apparatus according to Embodiments 1 to 3 of the present invention. FIG. 2 is a functional block diagram showing the information processing apparatus according to Embodiments 1 to 3 of the present invention. FIG. 3 is a flowchart showing the operation of the information processing apparatus according to Embodiment 1 of the present invention. FIG. 4 is an explanatory diagram showing the operation of the printer as the information processing apparatus according to Embodiment 1 of the present invention. FIG. 5 is a state transition diagram showing the operation of the information processing apparatus according to Embodiment 1 of the present invention. FIG. 6 is an explanatory diagram showing messages used for transmission and reception. FIG. 7 is a state transition diagram showing the operation of the information processing apparatus according to Embodiment 2 of the present invention. FIG. 8 is a state transition diagram showing the operation of the information processing apparatus according to Embodiment 2 of the present invention. FIG. 9 is an explanatory diagram showing the operation of the information processing apparatus according to Embodiment 2 of the present invention. FIG. 10 is a state transition diagram showing the operation of the information processing apparatus according to Embodiment 3 of the present invention. FIG. 11 is an explanatory diagram showing a typical sequence of the information processing apparatus according to Embodiment 3 of the present invention. FIG. 12 is an explanatory diagram showing a typical sequence of the information processing apparatus according to Embodiment 3 of the present invention. FIG. 13 is an explanatory diagram showing the operation of the printer in the prior art. FIG. 14 is an explanatory diagram showing the operation of the printer in the prior art. FIG. 15 is an explanatory diagram showing the operation of the printer in the prior art.

Explanation of symbols

  100: printer, 200: controller, 300: printer engine, 400: communication line.

Claims (10)

In an information processing apparatus that includes at least a controller and a printer engine for exchanging information by communicating with each other, and that processes information by performing an operation in which at least one device cooperates with the other device,
The controller is
Prior notification means for informing the printer engine in advance that the cooperative operation cannot be continued when the controller detects a restart factor ;
Response waiting means for waiting for a confirmation response from the printer engine ;
Processing means for processing information received before waiting for a confirmation response from the printer engine ;
An execution means for executing a restarting operation upon receiving a confirmation response of the prior notification from the printer engine ;
With
The printer engine is
Receiving means for receiving notification from the controller that a restart factor has been detected ;
An information processing apparatus comprising: response means for returning a response indicating that the notification has been received to the controller when the notification indicating that the cooperative operation cannot be continued is received. The information processing apparatus according to claim 1, wherein the response waiting unit treats a response as a response when there is no response for a predetermined time. The information processing apparatus according to claim 1, wherein the processing unit does not process information that is wasted even if the processing is performed. 4. The information processing apparatus according to claim 1, wherein the processing means does not process information received after the response means returns a response. 4. The processing unit according to claim 1, wherein the processing unit does not process only the processing that affects the state of the controller when processing is performed on the information received after the response unit returns a response. Information processing device. The information processing apparatus according to claim 1, wherein the notification unit notifies information about whether or not the influence of the return processing of the controller affects the printer engine . In an information processing apparatus that includes at least a controller and a printer engine for exchanging information by communicating with each other, and that processes information by performing an operation in which at least one device cooperates with the other device,
The controller is
Prior notification means for informing the printer engine in advance that the cooperative operation cannot be continued when the controller detects a restart factor ;
Response waiting means for waiting for a confirmation response from the printer engine ;
Processing means for processing information received before waiting for a confirmation response from the printer engine ;
An execution means for executing a restarting operation upon receipt of a confirmation response of the prior notification from the printer engine ;
With
The printer engine is
Receiving means for receiving notification from the controller that a restart factor has been detected ;
When receiving a notification that the cooperative operation cannot be continued, a response means for returning a response indicating that the notification has been received to the controller ;
Post-processing means for performing post-processing for terminating the cooperative operation;
An information processing apparatus comprising: The information processing apparatus according to claim 7, wherein the post-processing performed by the post-processing unit is saving the apparatus state to a nonvolatile storage unit. The information processing apparatus according to claim 7, wherein the post-processing performed by the post-processing unit is retraction of the apparatus mechanism to an appropriate position. The information processing apparatus according to claim 7, wherein the post-processing performed by the post-processing unit is a complete stop of the information processing operation. "

Images