JPH03241417A - Data transfer equipment - Google Patents

Abstract

PURPOSE:To connect a hardware equipped with a different data transfer system without changing a hardware in the main body of a system by reading data transferred by a first data transfer system corresponding to dummy information and transferring the data by a second data transfer system. CONSTITUTION:An interface means 21 is provided to input/output the data in the first transfer system, and a monitoring means 16 is provided to monitor the state of the input/output. Then, a storing means 12 is provided to store information required for driving the interface means 21 by the first transfer system, and a means 15 is provided to read the information from the storing means 12 according to the monitored result and to apply the information to the interface means 21. Further, a means 11 is provided to output the inputted data by converting the data in the first transfer system to the data in the second transfer system and converting the data in the second transfer system to the data in the first transfer system. Thus, for an equipment equipped with no SCSI (Small Computer System Interface), the data can be transferred to the equipment equipped with the SCSI without changing the hardware in the main body of the system.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a data transfer device that enables data transfer between two ASs using different data transfer methods.

[Conventional technology]

BACKGROUND OF THE INVENTION Conventionally, in electronic I/L devices to which a microprocessor is applied, such as a microcomputer system or a word processor sensor, when data is to be transferred to an external device, a dedicated interface has been installed to control the data transfer.

[Problem to be solved by the invention]

However, in the case of a dedicated machine such as a word processor, expanding the interface has many hardware limitations and requires changing the hardware and mechanism, so it is usually difficult for the user to do so.

Under these circumstances, the present invention has an interface for driving a floppy disk driver, and has an external connector or a similar connection part, but an SCSI interface for hard disk drivers, streaming tape devices, etc. (Small Con+puter Sy
The purpose of the present invention is to provide a data transfer device that enables data transfer between a device that does not have a STEM interface and a device that has an SCS R without changing the hardware of the device itself.

[Means to solve the problem]

The present invention converts data transferred by a first transfer method into data of a second transfer method, and also converts data transferred by the second transfer method into data of the first transfer method and transfers the data. In a data transfer device, an interface means for inputting and outputting data of the first transfer method, a monitoring means for monitoring the input/output state of the interface means, and a data transfer device for transmitting data using the first transfer method. storage means storing information necessary for driving according to the method; means for reading out the information from the storage means according to the monitoring result of the monitoring means and providing it to the interface means; Means for converting data of a first transfer method into data of a second transfer method and outputting the data, and supplying the data of the second transfer method to the interface means for converting the data into data of the first transfer method and outputting the data. It is characterized by having the following.

[Effect]

In the data transfer device of the present invention, the data transferred by the first data transfer method is read in accordance with the pseudo information generated by the pseudo information generating means, and is transferred by the second data transfer method, and vice versa. The data transferred by the second data transfer method is output in accordance with the pseudo information generated by the pseudo information generating means.

〔Example〕

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described in detail below based on drawings showing embodiments thereof.

FIG. 1 is a block diagram showing the configuration of a data transfer device according to the present invention and the state of connection with other devices.

In FIG. 1, reference numeral 1 is a data transfer device of the present invention, and in this embodiment, it is an FD (Floppy Disk).
) driver interface is equipped, but it is equipped with a 5CSI (Sllall Coa+putre) interface for hard disk drivers or streaming tape devices.
A target 3 compatible with 5C5I is connected to the system body 2 which is not equipped with a SystemInterface.

Note that the system main body 2 is, for example, a word processor.
As the target 3, a hard disk driver, a streaming tape device, etc. are used.

Between the system main body 2 and the target 3 as shown in Fig. 1,
Since they do not have a common interface, it is conventionally impossible to directly connect and transfer data. For this reason,
By interposing the data transfer device f1 of the present invention between the system main body 2 and the target 3, data transfer between the system main body 2 and the target 3 is made possible.

The configuration of the data transfer device 1 will be described below.

In FIG. 1, reference numeral 11 is a control section using, for example, a microcomputer. The control unit 11 is connected to a program ROM 12 . Memory R
AM13. FDC (Floppy Disk Con
troller)14. Pseudo trunk information generation circuit 15
．． Input/output port 16.5C3I controller 17 is connected. The control unit 11 controls each of the above-mentioned components according to a control program.

A program ROM (read only memory) 12 stores a control program for the control unit 11, and also stores pseudo trunk data, which will be described later.

A memory RAM (Random Access Memory) 13 is used for temporary storage of transferred data.

FDC14 is usually POD (Floppy Disk).
Here, it operates as an interface means and is connected to the FDC 22 inside the system main body 2 via the FD interface 21.

The pseudo track information generating circuit 15 functions as follows. Normally, trunk information is a signal obtained by reading a floppy disk (media), and when writing data to a floppy disk, the FDC 14 is driven according to the track information obtained from the floppy disk, and the data is written to the floppy disk. be included. However, in the pig transfer device 1 of the present invention, track information such as a lock and ID (Identifier) field, which is necessary for driving the FDC 14 by the pseudo trunk information generation circuit 15, is read from the program ROMI 2, converted into serial data, and sent out. ing.

This pseudo track information is generated according to the monitoring results of the input/output port 6 that monitors the state of the input signal to the FDC 14.
The pseudo trunk information generation circuit 15 generates and outputs the information.

In the data transfer device 1 of the present invention, the FDC 14 can be driven by generating pseudo trunk information as described above.

The input/output port 6 takes in information from the FD interface 21 and outputs settings. In this embodiment, the write protect ("Wri protect'") signal and the step (
"5tep") signal, etc.

The 5C3I controller 17 is an interface controller (5C3I in this case) of the same type as the target 3 that the system main body 2 should originally drive. This 5csr
A controller I7 is connected to the target 3 via a 5csr bus 31.

Therefore, the data transfer device 1 of the present invention has a system main body 2.
The data transfer method of the target 3 is converted to the data transfer method of the target 3, and conversely, the data transfer method of the target 3 is converted to the data transfer method of the system main body 2.

FIG. 2 is a timing chart showing the procedure for transferring data from the target 3 to the target 3 via the data transfer device 1, and conversely from the target 3 to the system main body 2 via the data transfer device 1. . First, an outline of data transfer will be explained with reference to FIG.

When transferring data from the system main body 2 to the target 3, first a data transfer command (write command) is output from the system main body 2, and this is transmitted to the target 3 via the data transfer device 1. It is transferred to target 3 via transfer device I. After receiving all the data, the target 3 sends a status signal to the system body 2 via the data transfer device 1.
send to By receiving this status signal, the system body 2 knows that the data transfer has been completed.

Conversely, when data is transferred from the target 3 to the system main body 2, a data transfer command (read command) is first output from the system main body 2, and this is transmitted to the target 3 via the data transfer device 1. When the target 3 receives the data transfer command, data is transferred from the target 3 to the system main body 2 via the data transfer device 1, and a status signal is sent from the target 3 to the system main body 2 via the data transfer device 1. Sent. Upon receiving this status signal, the system body 2 knows that the data transfer has been completed.

FIG. 3 (al, (bl) shows the data transfer procedure from the system main body 2 to the data transfer device 1 of the present invention having the above-described configuration.
FIG. 4 is a flowchart showing the example procedure (bl) separately. In addition, FIG. It is a chart showing how the FDC 14 and the FDC 22 of the system main body 2 each operate.

First, the pseudo track information generating circuit 15 is set up to operate within the data transfer device 1 (step 5).
ll). The pseudo track information generated by the setup of the pseudo track information generating circuit 15 includes normal data in the 10th field and CRC (Cyclic Redundancy) in the data field.
Check) Each data in which an error occurs is sent. This puts the data writing side, that is, the system main body 2 side, in a state where it can read the 10 fields and write output data into the data fields.

On the other hand, the data reading side, that is, the data transfer device 1 side, uses 1
The 0 field is read and the data field is read accordingly, but if the communication partner (in this case, the system body 2) is not outputting data, a CRC error will occur.

Next, the data transfer device 1 issues a read command to the FDC 14 (step 512), and repeats issuing the command many times until the data can be read normally (step S
13. Sll, 512). At this time, the system main body 2
The side issues a write command to the FDC 22 (step 521), and repeats this until the write protect signal is turned on (steps 522 and 521). If the data can be read accurately on the data transfer device 1 side, the data transfer device 1 turns on the write protect signal (step 514). Thereby, the system body 2 side knows that the data transfer has been completed.

The data transferred to data transfer device 1 is temporarily transferred to memory RA.
After being stored in the F113, it is transferred to the target 3 via the 5csr bus 31 under the control of the 5C5I controller 17.

Figures 5 (ta) and (bl) are flowcharts showing the data transfer procedure from the data transfer device 1 to the system main body 2 by distinguishing them into the procedure +a+ of one example of the data transfer device and the procedure -) on the system main body 2 side. . FIG. 6 also shows the pseudo track information generating circuit 15. FDC14 and PDC2 of system body 2
2 is a chart showing how each operates.

First, on the data transfer device 1 side, the pseudo trunk generation circuit 1
5 is amplified (step 531), and as in the case of data transfer from the system main unit 2 to the data transfer device 1 described above, normal data is stored in the 10 field and a CRC (Cyclic Redundant) is stored in the data field.
cy Check) Each data in which an error occurs is sent. Thereafter, the data transfer device 1 issues a write command to the FDC 14 (step 532).

At this time, the system body 2 issues a read command to the FDC 22 (step 541), and repeats this until no errors occur (steps 542 and 541).

If the read command is completed normally, the system unit 2
issues a step signal (step 343).

By receiving this step signal, the data transfer device 1 stops issuing write commands (step 533
).

By combining the above operations, data transfer device I
Since data is sent and received between the system main body 2 and the system main body 2, data is transferred from the system main body 2 to the target 3 via the data transfer device 21, and vice versa. Data is transferred to the system main body 2 via the data transfer device 1.

Note that the signals used for data transmission and reception in this embodiment can be replaced with other signals.

Further, for convenience of explanation, the actual procedure will be simplified and explained.

〔effect〕

As detailed above, according to the data transfer device of the present invention, by adding software and external hardware to the system main body, a different data transfer method that is originally impossible to connect without changing the hardware of the system main body is provided. It becomes possible to connect hardware.

[Brief explanation of drawings]

FIG. 1 is a block diagram showing the configuration of the data transfer device of the present invention and its connection state with the system main body and target;
FIG. 2 is a timing chart showing the overall data transfer procedure, FIG. 3 is a flowchart showing the procedure for data transfer from the system main body to the data transfer device, and FIG. 4 is a pseudo trunk information generation circuit at that time, A chart showing how the FDC of the FilCl system main unit in the data transfer location operates. Figure 5 is a flowchart showing the procedure for transferring data from the data transfer device to the system main unit. Figure 6 is a flowchart showing the procedure for transferring data from the data transfer device to the system main unit. pseudo trunk information generation circuit, FDC of the data transfer device, F of the system main body 2
This is a chart showing how the DC works. 1...Data transfer device 2...System body 3.
...Target 1-11...Control unit 12...Program RO gate 13...Memory RAM 14...
FDC (floppy disk controller) 15...
Pseudo track information generation circuit 16...I/O port patent Applicant: Sanyo Electric Co., Ltd.

Claims (1)

[Claims] 1. Converting data transferred by a first transfer method into data of a second transfer method, and converting data transferred by the second transfer method into data of the first transfer method. A data transfer device that converts and transfers data, comprising: interface means through which data of the first transfer method is input/output; monitoring means for monitoring the input/output state of the interface means; and the interface means. storage means storing information necessary for driving according to the first transfer method; means for reading out the information from the storage means and providing it to the interface means according to the monitoring result of the monitoring means; and from the interface means. Converting the input data of the first transfer method into data of the second transfer method and outputting the data,
A data transfer device comprising: means for applying data of a second transfer method to the interface means, converting it into data of a first transfer method, and outputting the data.