JP3379493B2 - Network compatible input / output system - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network compatible input / output system for transferring data between an input / output device and an interface device for connecting the input / output device to a network in units of packets, and more particularly to a printer and a printer. The data transfer method between print servers is IEEE
(Institute of Electrical and Electronics Engineer
s) A network compatible input / output system suitable for a printer system according to standard 1284.4.

[0002]

2. Description of the Related Art Conventionally, as an interface of an input / output device such as a printer or a scanner, an IEEE (Instit
ute of Electrical and Electronics Engineers) Bidirectional parallel interface based on standard 1284-1994 has become widespread.

In recent years, this IEEE standard 1284-199
4 is used for the purpose of constructing multiple logical channels,
IEEE standard 1284.4 has been proposed. This IEEE
In the standard 1284.4, it is possible to transfer data in units of packets.
The use of the data transfer method based on the EEE standard 1284.4 has the following advantages.

That is, by checking the format of the received packet, it is possible to detect a data transfer error such as a packet that has become defective due to the influence of noise or the like. Then, when a data transfer error such as a defective packet is detected, the subsequent operation is stopped, and the garbled data (garbled data) is endlessly printed due to the influence of the defective packet. It is possible to prevent such a situation.

[0005]

By the way, with the spread of networks such as LAN (local area network), a printer is shared by a plurality of client terminals also connected to the network via a print server connected to the network. The form to be used after that is becoming popular.

[0006] Now, in such a form that the printer is shared via the print server, IEEE standard 1284.4 is used for data transfer between the printer and the print server.
When a method conforming to (4) is used to stop subsequent operations when a data transfer error such as a defective packet is detected as described above, the following problems occur.

That is, when the operation of the printer is stopped due to a data transfer error, the printer and the print server must be restarted so that the printer can be used again. That is, unless somebody restores the printer or the print server, all the client terminals sharing the printer cannot use the printer. In the form of sharing the printer via the print server, it is also possible that the client terminals are installed in separate locations. In such a case, the user of the client terminal closest to the printer can restore the printer or print server. Although it is expected that work will be performed, it is not convenient for the user to perform such work each time the operation of the printer is stopped due to a data transfer error.

The present invention has been made in view of the above circumstances, and an object of the present invention is to recover a system operation stop due to a data transfer error in a network-compatible input / output system capable of transferring data in units of packets. To reduce the burden.

[0009]

In order to solve the above problems, the present invention has an input / output device and an interface device for connecting the input / output device to a network. A network-compatible input / output system for performing data transfer between output devices in packet units, wherein the input / output device and the interface device each include error detection means for detecting a data transfer error with a partner device, and When the error detection unit detects a data transfer error, at least a first command for clearing the job being executed is transmitted to the partner device, and when the error detection unit detects the data transfer error and the partner device. To clear at least the running jobs when more first commands are received Characterized in that it comprises an initialization means for performing an initialization process, the.

Here, as the data transfer between the interface device and the input / output device in packet units, as described above, for example, the IEEE (Institute of Institute)
Electrical and Electronics Engineers) Standard 128
There is 4.4.

Further, as a specific method for detecting a data transfer error with the partner device, it is possible to check whether or not the packet received from the partner device is in a predetermined format, and This can be done by checking whether or not a response to the command packet transmitted by has been received within a predetermined time.

Further, at least the initialization process for clearing the job being executed means a process sufficient to discard the data relating to the job being executed so that a new job can be accepted. To do. This processing can be realized by restarting with software reset or hardware reset.

According to the present invention, with the above configuration, when an error occurs in data transfer between the input / output device and the interface device, the job being executed is cleared and a new job can be accepted. Since the input / output device and the interface device are moved, the burden on the recovery work of the system operation stop due to the data transfer error can be reduced as compared with the above-mentioned conventional system in which the operation is stopped by the detection of the data transfer error.

[0014]

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of the present invention will be described below.

FIG. 1 is a schematic configuration diagram of a network system to which an embodiment of the present invention is applied. As shown in the figure, the printer 2 is shared by a plurality of clients 3 also connected to the network 4 via the print server 1 connected to the network 4 such as a LAN. Here, as a data transfer method between the print server 1 and the printer 2, IEEE standard 1284.4 is used.

The print server 1 transfers the print data sent from the client 3 connected to the network 4 to the printer 2.

FIG. 2 is a schematic configuration diagram of the print server 1 shown in FIG.

As shown in the figure, the print server 1 has a network interface section 11, a printer interface section 12, a protocol conversion section 13, a transfer error detection section 14, and an initialization section 15. These components are ASIC (Application Specific Integrate)
d Circuits), FPLA (Field-Programmable LogicAr)
ray) or other integrated logic IC. Alternatively, the information processing device such as a personal computer may be realized as a process by executing a predetermined program (print server program). This predetermined program is an FD or CD that can be read by an information processing device.
-It may be provided to the information processing device by a portable storage medium such as ROM, or may be provided to the information processing device via a communication medium such as a network.

The network interface section 11 includes
Data communication is performed with the client 3 via the network 4.

The printer interface section 12 is an IE.
Data communication is performed with the printer 2 according to the data transfer method of the EE standard 1284.4.

The protocol conversion unit 13 is used for the network 4
In order to enable data communication between the printer 2 and the printer 2, protocol conversion between the communication protocol on the network 4 side and the communication protocol on the printer 2 side is performed.

The transfer error detection unit 14 detects a data transfer error between the printer interface unit 12 and the printer 2. Here, the transfer error detection unit 14 detects a data transfer error by dividing it into an error that can be recovered by software reset and a fatal error that cannot be recovered by software reset.

Specifically, when the packet from the printer 2 received by the printer interface unit 12 is a defective packet that is not in a predetermined format with the printer 2, or a response to a command packet transmitted by the device itself. Is not received from the printer 2 within a predetermined time (for example, 5 minutes), it is determined that the error can be recovered by software reset.

On the other hand, when the device itself transmits a packet to the printer 2, the reception operation of the printer 2 does not proceed and the transmission is not completed within a predetermined time (for example, 5 minutes), or when the packet is received from the printer 2. If the transmission operation of the printer 2 does not proceed and the transmission is not completed within a predetermined time (for example, 5 minutes), it is determined that the fatal error cannot be recovered by software reset.

When the transfer error detection unit 14 receives an error packet indicating that the printer 2 has detected a transfer error from the printer 2 via the printer interface unit 12, it notifies the initialization unit 15 to that effect. .

The initialization unit 15 controls the operation of its own device according to the instruction from the transfer error detection unit 14. Specifically, when the transfer error detection unit 14 detects a recoverable error due to software reset, the printer 2 is transferred to the printer 2 via the printer interface unit 12.
An error packet indicating that a transfer error has been detected is transmitted, and then the device itself is software reset. Here, the software reset is at least sufficient to discard the data related to the job being executed stored in the memory or buffer (not shown) so that a new job can be accepted. Means processing. On the other hand, when the transfer error detection unit 14 detects a fatal error that cannot be recovered by software reset, the operation of the own device is stopped. When the transfer error detector 14 receives an error packet from the printer 2, it resets its own software.

Next, returning to FIG. 1, the printer 2 will be described.

The printer 2 receives print data (job) from the client 3 via the print server 1,
Print on print media.

FIG. 3 is a schematic configuration diagram of the printer 2 shown in FIG.

As shown in the figure, the printer 2 has an interface section 21, a controller section 22, a printer engine section 23, an instruction receiving section 24, a transfer error detecting section 25, and an initializing section 26. Here, the interface unit 21, the controller unit 22, the transfer error detection unit 2
5 and the initialization unit 26, the ASIC (Application Spec
ific Integrated Circuits), FPLA (Field-Progra
It may be configured in hardware by an integrated logic IC such as an mmable logic array). Further, it may be realized as a process by causing a microprocessor to execute a predetermined program.

The interface unit 21 uses the printer 2 according to the data transfer method of IEEE standard 1284.4.
And data communication.

The printer engine unit 23 includes a mechanism for printing data on a print medium (for example, a print head for ejecting ink, a platen, a carriage drive mechanism for driving a carriage carrying the print head, a paper feed mechanism, and printing). A paper feeding / discharging mechanism for performing paper feeding / discharging processing).

The controller unit 22 controls the printer engine unit 2 so as to print on the print medium according to the print data.
Control 2

The instruction receiving section 24 is composed of an operation panel or the like and receives an instruction from the operator.

The transfer error detecting section 25 detects a data transfer error between the interface section 21 and the print server 1. Here, the transfer error detection unit 25 detects a data transfer error by dividing it into an error that can be recovered by software reset and a fatal error that cannot be recovered by software reset.

Specifically, when the packet from the print server 1 received by the interface unit 21 is a defective packet which is not in a predetermined format with the print server 1 or a command packet transmitted by the device itself. When the response is not received from the print server 1 within a predetermined time (for example, 5 minutes), it is determined that the error can be recovered by the software reset.

On the other hand, when the device itself transmits a packet to the print server 1, the reception operation of the print server 1 does not proceed and the transmission is not completed within a predetermined time (for example, 5 minutes), or the packet is transmitted from the print server 1. When receiving, if the transmission operation of the print server 1 does not proceed and the transmission is not completed within a predetermined time (for example, 5 minutes), it is determined that the fatal error cannot be recovered by software reset.

Further, when the transfer error detection unit 25 receives an error packet indicating that the print server 1 has detected a transfer error from the print server 1 via the interface unit 21, it notifies the initialization unit 26 accordingly. Inform.

The initialization unit 26 controls the operation of its own device according to the instruction from the transfer error detection unit 25. Specifically, when the transfer error detection unit 25 detects a recoverable error by software reset, an error packet indicating that the transfer error is detected is sent to the print server 1 via the printer interface unit 21. Then, the device is reset by software. Here, software reset means at least
This means a process sufficient to discard the data related to the job being executed stored in a memory, a buffer, or the like (not shown) so that a new job can be accepted. On the other hand, when the transfer error detection unit 25 detects a fatal error that cannot be recovered by software reset, the operation of the own device is stopped. When the transfer error detection unit 25 receives an error packet from the print server 1, it resets its own software.

Next, a data transfer error detection process between the print server 1 and the printer 2 having the above configuration will be described.

First, the data transfer error detection processing of the print server 1 will be described.

FIG. 4 is a flow chart for explaining the data transfer error detection processing of the print server 1. This flow is performed via the print server 1 when the data transfer in packet units according to the IEEE standard 1284.4 is performed between the print server 1 and the printer 2, that is, between the printer 2 and the client 3. It is performed while data communication is being performed.

First, the transfer error detection unit 14 determines whether or not an error packet is received from the printer 2 via the printer interface unit 12 (step S1).
01). When the error packet is received, the initialization unit 15 is instructed to that effect. In response to this, the initialization unit 15 resets its own software. At this time, the non-packet mode is restored (step S102). then,
The transfer error detection unit 14 waits for the reception of a command instructing the packet mode transition from the printer 2 via the printer interface unit 12 (step S10).
3). When the command is received, the printer 2 is returned with a response permitting the shift to the packet mode, and then each unit of the device is controlled to shift the data transfer mode from the non-packet mode to the packet mode (step S104).

On the other hand, when the error packet is not received in step S101, the transfer error detection unit 14 determines whether or not a recoverable error is detected by software reset (step S105). When a recoverable error is detected by the software reset, an error packet is transmitted to the printer 2 via the printer interface unit 12 (step S106), and it is initialized that the recoverable error is detected by the software reset. The conversion unit 15 is instructed. In response to this, the initialization unit 15 resets its own software. At this time, the non-packet mode is restored (step S10).
7). Then, the transfer error detection unit 14 waits for a predetermined time (for example, 5 seconds) to elapse (step S10).
8) Send a command instructing the packet mode transition to the printer 2 via the printer interface unit 12, and wait for receipt of a response from the printer 2 permitting the transition to the packet mode. Then, when the response is received, each unit of the own device is controlled so as to shift the data transfer mode from the non-packet mode to the packet mode (step S109). If you do not receive a response,
The data transfer mode is not changed from the non-packet mode to the packet mode.

On the other hand, if no recoverable error is detected by the software reset in step S105, the transfer error detection unit 14 determines whether a fatal error that cannot be recovered by the software reset is detected. (Step S110). When a fatal error is detected, the operation of the own device is stopped (step S11).
1) Wait for the restart by hardware reset. The restart by the hardware reset may be performed by the RST signal “L” drive of the printer 2, for example.

Next, the data transfer error detection processing of the printer 2 will be described.

FIG. 5 is a flow chart for explaining the data transfer error detection processing of the printer 2. This flow is similar to the flow shown in FIG. 4, when data transfer in packet units according to IEEE standard 1284.4 is being performed between the print server 1 and the printer 2.
That is, this is performed when data communication is being performed between the printer 2 and the client 3 via the print server 1.

As shown in FIG. 5, the data transfer error detection process of the printer 2 is basically the same as the data transfer error detection process of the print server 1 shown in FIG.

That is, the transfer error detecting unit 25 determines whether or not an error packet is received from the print server 1 via the interface unit 21 (step S).
201). When the error packet is received, the initialization unit 26 is instructed to that effect. In response to this, the initialization unit 26
Software reset the device. At this time, the non-packet mode is restored (step S202). Then, the transfer error detection unit 25 uses the interface unit 21.
Through the print server 1 until it receives a command instructing the packet mode transition (step S20).
3). When the command is received, a response permitting the transition to the packet mode is returned to the print server 1, and then each unit of the device is controlled so as to transition the data transfer mode from the non-packet mode to the packet mode (step S20).
4).

On the other hand, when the error packet is not received in step S201, the transfer error detection unit 25 determines whether or not a recoverable error is detected by software reset (step S205). When a recoverable error is detected by software reset, an error packet is transmitted to the print server 1 via the interface unit 21 (step S206), and
The initialization unit 26 is instructed that a recoverable error has been detected by the software reset. In response to this, the initialization unit 26 resets its own software. At this time, the non-packet mode is restored (step S20).
7). Then, the transfer error detection unit 25 waits for a predetermined time (for example, 5 seconds) to elapse (step S20).
8) Send a command instructing the packet mode transition to the print server 1 via the interface unit 21 and wait for a response from the print server 1 to permit the packet mode transition. Then, when the response is received, each unit of the own device is controlled so as to shift the data transfer mode from the non-packet mode to the packet mode (step S209). If no response is received, the data transfer mode is not changed from the non-packet mode to the packet mode.

On the other hand, when the error which can be recovered by the software reset is not detected in step S205, the transfer error detection unit 25 judges whether or not the fatal error which cannot be recovered by the software reset is detected. Yes (step S210). When a fatal error is detected, the operation of the own device is stopped (step S21
1) Wait for the operator to restart by hardware reset via the instruction receiving unit 24. At this time, the print server 1 may be restarted by a hardware reset using the RST signal “L” drive of the printer 2, for example.

The embodiment of the present invention has been described above.

According to this embodiment, as described above, when an error occurs in the data transfer between the print server 1 and the printer 2, the job being executed can be cleared and a new job can be accepted. Since the print server 1 and the printer 2 can be migrated to, the burden on the recovery work of the system operation stop due to the data transfer error can be reduced as compared with the conventional system in which the operation is stopped by the detection of the data transfer error. .

Further, in this embodiment, the print server 1
When an error occurs in the data transfer between the printer 2 and the printer 2, the job being executed is cleared by software reset, and the non-packet mode is temporarily entered. That is, the print server 1 and the printer 2 are
After reset, commands are always exchanged in non-packet mode, and then the mode is changed to packet mode. If the command is not exchanged, the packet mode is not entered. Therefore, without being aware of whether or not the partner device supports the packet mode,
Processing after reset can be performed. That is, it is not necessary to change the processing after reset depending on whether or not the partner device supports the packet mode.

In the above embodiment, the present invention is applied to a system in which the printer 2 is shared by a plurality of clients 3 via the print server 1 which transfers data according to the IEEE standard 1284.4 system. However, for example, if the scanner is IEEE standard 1284.4
Network correspondence that transfers data between an input / output device and an interface device for connecting the input / output device to the network in packet units, such as a system shared by multiple clients via a server that transfers data by the method It can be widely applied to input / output systems.

[0056]

As described above, according to the present invention,
It is possible to reduce the burden of recovery work for system operation stop due to a data transfer error.

[Brief description of drawings]

FIG. 1 is a schematic configuration diagram of a network system to which an embodiment of the present invention is applied.

FIG. 2 is a schematic configuration diagram of a print server 1 shown in FIG.

FIG. 3 is a schematic configuration diagram of a printer 2 shown in FIG.

FIG. 4 is a flowchart for explaining a data transfer error detection process of the print server 1 shown in FIG.

5 is a flowchart for explaining a data transfer error detection process of the printer 2 shown in FIG.

[Explanation of symbols]

1: Print server 2: Printer 3: Client 4: Network 11: Network interface section 12: Printer interface section 13: Protocol conversion processing unit 14, 25: Transfer error detector 15, 26: initialization unit 21: Interface part 22: Controller section 23: Printer engine section 24: Instruction reception section

Claims (5)

(57) [Claims] 1. An input / output device, and an interface device for connecting the input / output device to a network,
A network-compatible input / output system that transfers data between the interface device and the input / output device in units of packets, wherein the input / output device and the interface device each detect a data transfer error with a partner device. An error detecting unit and a first unit for clearing at least a job being executed when the error detecting unit detects a data transfer error
Of the above command is transmitted to the partner device, and at the same time when the error detecting means detects a data transfer error and when the first command is received from the partner device, at least initialization processing for clearing the job being executed is performed. An initialization unit for executing the data transfer , wherein the initialization unit transfers data to the partner device of the own device by an initialization process.
Set the mode to packet transfer that transfers data in packet units.
Non-packet that transfers data in non-packet units from transmission mode
Data transfer mode, and the initialization process is performed by the error detection means in the device itself.
Data transfer error detection
The data transfer mode for the other device
Move from non-packet transfer mode to packet transfer mode again
Data transfer mode and packet transfer mode
Send second command to switch to other device
However , the initialization process is caused by the first command from the partner device.
When executed, it receives the second command from the partner device.
Transfers data from the device to the other device when the device is removed
Change the mode from the transitioned non-packet transfer mode to
A network-compatible input / output system characterized by switching to the transfer mode again . 2. The network-compatible input / output system according to claim 1.
A system between the input / output device and the interface device.
The data transfer method is IEEE (Institute of Electrica).
l and Electronics Engineers) Standard 1284.4
Network compatible input / output system characterized by
Mu. 3. A packet for data transfer with an input / output device
Connect the input / output device to the network
Interface device for detecting a data transfer error with the input / output device.
Error detection means and the error detection means detect a data transfer error
The first to clear at least the running jobs
Command is sent to the input / output device, and
If the error detection means detects a data transfer error,
And the first command is received from the I / O device
To clear at least the running jobs
Initialization means for executing initialization processing, wherein the initialization means performs data transfer mode for the input / output device by the initialization processing.
Packet transfer that transfers data in packet units
Non-packet that transfers data from the mode in non-packet units
Transfer to the remote transfer mode, and the initialization process is performed by the error detecting means.
-When executed due to detection, the I / O device
The data transfer mode for the
Switch from send mode to packet transfer mode again.
The data transfer mode to the packet transfer mode.
Send a second command to the I / O device, and the initialization process is initiated by the first command from the I / O device.
If it is executed due to the
To the I / O device when a command is received
Non-packet transfer mode, which is a transfer of data transfer mode
From the packet transfer mode to the packet transfer mode again
Interface device. 4. An interface for connecting the own device to a network.
Data transfer with the interface device in packet units
Which is an input / output device that performs data transfer error with the interface device.
Error detecting means for detecting and when the error detecting means detects a data transfer error
The first to clear at least the running jobs
When you send the command to the interface device
At the same time, the error detection means detects a data transfer error.
And the first frame from the interface device
If you receive a
Initialization means for executing initialization processing for clearing,
The initialization means includes a device for the interface device by an initialization process.
The data transfer mode is set to the packet transfer mode.
Data transfer from packet transfer mode in non-packet units.
The non-packet transfer mode is set, and the initialization process is performed by the error detection means.
-If executed due to detection, the interface
The data transfer mode for the interface device
Transition from packet transfer mode to packet transfer mode again
And set the data transfer mode to the packet transfer mode.
The second command for transferring is the interface
To the interface device , and the initialization process is performed by the first command from the interface device.
If executed due to a command, the interface
When the second command is received from the
The data transfer mode for the interface device
From the transferred non-packet transfer mode to the packet transfer mode.
An input / output device characterized in that it is transferred to the computer again. 5. An input / output device and a network for the input / output device.
To the interface device for connecting to the
It is a data transfer method that transfers data in units of packets.
The input / output device and the interface device are
S, monitors data transfer errors between them, the data transfer error
At least clear running jobs
To send the first command to
If a data transfer error is detected,
In the case of Tsu receive one of the command, at least running
Step to execute the initialization process to clear the job.
And the step of executing the initialization process includes the step of transferring data to the partner device of the own device by the initialization process.
Set the mode to packet transfer that transfers data in packet units.
Non-packet that transfers data in non-packet units from transmission mode
Switch to the transfer mode and the initialization process is
If it is executed by
Data transfer mode is changed from non-packet transfer mode
Switch to packet transfer mode again and transfer data
A second method for changing the mode to the packet transfer mode.
The command is sent to the partner device, and the initialization process is caused by the first command from the partner device.
When executed, it receives the second command from the partner device.
Transfers data from the device to the other device when the device is removed
Change the mode from the transitioned non-packet transfer mode to
Data characterized by switching back to transfer mode
Transfer method.