JP2007265305A - Communication system and peripheral device used therefor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a communication system for spontaneously starting a specific communication event by a user operation at a peripheral equipment side although the direction of issuing a command controlling the execution of a communication event is restricted to one direction from a PC side to the peripheral equipment side. <P>SOLUTION: The transmission of the selection content of a data file by a manual operation part is requested to peripheral equipment, and the selection content of the data file is received as reply information, and the selected data file is read by peripheral equipment, and transmitted to a host device, and the data file received by the peripheral equipment is stored in a predetermined storage area on a storage device at the host device side. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a communication system in which a peripheral device is connected to a personal computer (hereinafter abbreviated as “PC”), a workstation, or the like as a host device, and a peripheral device used therefor.

JP 2005-18645 A JP 2005-107875 A

  In recent years, a so-called memory card (an example of a recording medium) in which a nonvolatile memory such as a flash memory is packaged in a card type is widely known. This memory card is rapidly spreading as a data storage medium used in digital devices such as digital cameras and portable music players. The specifications of the memory card are not unified. For example, compact flash (registered trademark, hereinafter abbreviated as “CF”), smart media (registered trademark, hereinafter abbreviated as “SM”), memory stick (registered trademark, hereinafter referred to as “SM”). Various products such as “MS” and SD memory card (registered trademark, hereinafter abbreviated as “SD”) are on the market.

  By using a memory card reader / writer (an example of a peripheral device, hereinafter abbreviated as “reader / writer”) connected to a PC or the like, the memory card can be accessed from the PC. It becomes possible. As a result, data communication can be performed between the PC and the memory card. Such reader / writers include a single slot type having one slot for inserting a memory card, and a multi-slot type having a plurality of slots and capable of reading / writing data from / to a plurality of memory cards (Patent Documents 1 to 3). 2).

  By the way, the reader / writer as described above has also been generalized to perform data transmission with a PC by serial communication due to the background of the dramatic increase in data transfer capacity due to the spread of multimedia. However, in the control for data access, there are many devices that take over the method used in the arbitration / access control of peripheral devices for parallel communication from the viewpoint of easy handling of a plurality of storage media. As a typical example, a system designed to perform data communication between a PC and a reader / writer based on a protocol defined by a so-called SCSI standard (hereinafter also referred to as a SCSI protocol) can be exemplified. The SCSI standard is a communication protocol standardized by ANSI (American National Standard Institute) and widely internationally compliant. This protocol is widely used because it can enhance the versatility of PCs and reader / writers. In the following description, the SCSI standard mainly indicates SCSI-2.

  In the SCSI protocol, a PC serving as a host device functions as an initiator to which a communication event activation decision right is given, and a peripheral device is defined as a target that is a communication target of the host device. A command for instructing execution of a communication event is sequentially issued from the PC to the peripheral device, while the peripheral device that has received the issued command performs processing corresponding to the command (for example, data read, write, erase, And various incidental processes) are sequentially executed, and response information corresponding to the execution result is returned to the host device side. The issue direction of the command that controls the execution of the communication event is restricted to one direction from the host device side to the peripheral device side.

  As described above, the SCSI communication is bidirectional communication between the PC and the peripheral device. However, as described above, the command issuing direction for executing the communication event is unidirectional from the PC side to the peripheral device side. It is regulated, and the initiative to start communication processing is always held by the PC side that is the initiator. In other words, as long as the SCSI protocol is followed, it is impossible for the peripheral device side to reversely issue a command for starting a communication event to the host device side, and there is a method for spontaneously starting a specific communication event on the peripheral device side. I did not. For example, when data files stored in a memory card attached to a reader / writer are read on the PC side or stored in a storage device on the PC side such as a hard disk drive (HDD), the user must read and write them on the PC side. Processing operations (that is, command execution input) must be performed. For this reason, even if a memory card storing a data file is attached to a reader / writer placed at a location away from the PC, if the data file is to be stored on the PC, the data file must be saved unless it is bothered to the PC position. It was very inconvenient because it could not be operated.

  The problem of the present invention is that, although the issue direction of the command for executing the communication event is restricted to one direction from the PC side to the peripheral device side as described above, the command is issued by a user operation on the peripheral device side. An object of the present invention is to provide a communication system capable of spontaneously starting a specific communication event and a peripheral device used for the communication system.

Means for Solving the Problems and Effects of the Invention

The communication system of the present invention for solving the above problems is as follows.
A host device having a communication event activation decision right and a peripheral device to be communicated with the host device connected to the host device, and a command for instructing execution of the communication event is transmitted from the host device to the peripheral device. The peripheral device that has issued the issued command sequentially executes the data processing corresponding to the command, and returns response information corresponding to the execution result to the host device side. And in a communication system having a main communication protocol in which the command issuing direction is regulated in one direction from the host device side to the peripheral device side,
Peripheral device-side trigger generating means provided in the peripheral device for generating a peripheral device-side trigger for prompting the host device to start a target communication event having a predetermined content based on a user operation on the peripheral device side; ,
A trigger report request command is provided on the host device side to request the trigger occurrence report information reflecting the presence or absence of the peripheral device side trigger as response information in order to monitor the generation of the peripheral device side trigger in the peripheral device. , Trigger report request command issuing means for issuing to the peripheral device according to the main communication protocol,
Trigger occurrence report information return means provided on the peripheral device side for returning trigger occurrence report information as response information to the host device according to the main communication protocol,
Report information receiving means provided on the host device side for receiving trigger generation report information from the peripheral device;
Based on the content of the trigger occurrence report information, the presence or absence of a peripheral device side trigger is determined, and when it is determined that there is a peripheral device side trigger, the target communication event activation means for activating the target communication event,
The peripheral device is configured as a storage device in which at least a storage medium capable of data access relating to data reading is detachably mounted, and configured to perform data access to the storage medium by a communication event. A manual operation unit for performing a file selection operation for selecting a data file and a setting operation for setting a storage processing condition for the selected data file. As the host device side grasps the occurrence of the confirmation operation trigger as the peripheral device side trigger to confirm the file selection content from the trigger occurrence report information from the peripheral device, the manual operation unit sends the data file selection confirmation content. A request is sent from the host device to the peripheral device, and the data file selection confirmation is sent to the peripheral device. The host device requests the peripheral device to transmit the first communication event received on the host device side as response information and the setting details of the storage processing condition by the manual operation unit, and the setting information of the storage processing condition is transmitted to the peripheral device. Data file selection / save event execution that includes the second communication event received on the host device side as response information from the host device and the third communication event that reads the selected data file at the peripheral device and transmits it to the host device Means are provided,
The host device is provided with data file storage control means for storing the received data file in a predetermined storage area of the storage device on the host device side under the storage processing condition.

Further, the peripheral device of the present invention is a peripheral device constituting the communication system of the present invention,
As a storage device that is detachably mounted with a storage medium capable of data access related to data reading, and performs data access to the storage medium by a communication event Composed and
A manual operation unit for performing a file selection operation for selecting a data file in the storage medium, and a setting operation for a storage processing condition of the selected data file;
Peripheral device side trigger generating means for generating a peripheral device side trigger for prompting the host device to start a target communication event having a predetermined content based on a user operation on the peripheral device side;
Trigger occurrence report information return means provided on the peripheral device side and returning the trigger occurrence report information corresponding to the trigger report request command from the host device as response information to the host device in accordance with the main communication protocol. Features.

  According to the present invention, the peripheral device-side trigger for prompting the host device to start the target communication event is generated based on a user operation, and the host device side monitors the generation of the peripheral device-side trigger in the peripheral device. A trigger report request command is issued to the peripheral device according to the main communication protocol. The host device receives the trigger occurrence report information from the peripheral device that has received this, and activates the target communication event when it is determined from the content of the trigger occurrence report information that there is a peripheral device side trigger. As a result, even though the direction of issuing a command for executing the communication event is restricted to one direction from the host device side to the peripheral device side, a specific communication event is controlled by a user operation on the peripheral device side ( It can be activated spontaneously (on the host device side).

  In the present invention, as the peripheral device-side trigger, the selection of the data file by the manual operation unit as the host device side grasps the generation of the selection operation trigger by the manual operation unit from the trigger generation report information from the peripheral device. The peripheral device is requested to transmit the data file, and the selected data file is received as response information from the peripheral device. The selected data file is read by the peripheral device, transmitted to the host device, and received from the peripheral device. The data file is stored in a predetermined storage area on the host device side storage device provided on the host device side. At this time, the manual operation unit of the peripheral device can set the save processing condition of the selected data file, and the setting contents of the save processing condition are returned to the host device side as response information from the peripheral device. On the host device side, data file storage processing is performed under the received storage processing conditions. As a result, the data file storage process can be executed by the user operation on the peripheral device side, and the storage processing conditions can be set by the user operation on the peripheral device side, so the peripheral device is connected away from the host device. Even in this case, the image data file can be stored appropriately by remote operation from the peripheral device side.

  In the present invention, when a data file having a file name that overlaps with a data file to be stored in the storage medium exists in the storage area on the host device side, a storage processing condition for the data file having the duplicate file name However, it is possible to select and set from a plurality of conditions according to the operation content by the manual operation unit. If there is a data file with the duplicate file name and the normal save process is performed, the data file in the save area is overwritten by the data file from the storage medium against the user's intention. Prone to trouble. Therefore, if it is possible to select from several types of storage processing conditions when such duplicate file names exist, an appropriate method for rationally saving the data file while avoiding such troubles has been found. It can be made easier.

  In this case, if a condition for changing the data file name on the host device side or the storage medium side is set as the storage processing condition, the data file name is intentionally changed on either the transmission destination or the transmission source. The data file overwrite loss can be effectively prevented.

  Further, in the above configuration, when the peripheral device has a display unit and a data file having a file name overlapping with the data file to be stored in the storage medium exists in the storage area on the host device side, the data file selection / In the save event, a fourth communication event is executed in which the duplicate data file name is transmitted as character information from the host device side to the peripheral device, and the duplicate data file name is displayed on the peripheral device on the display unit. Data file name display means can be provided. In this way, it is possible to easily grasp which data file is duplicated by the display on the peripheral device side.

  As the main communication protocol, in the present invention, the SCSI protocol (either SCSI-1, SCSI-2, or SCSI-3: in particular, SCSI-2 that is still used in many OS kernels) is adopted. However, it is not limited to this.

  The trigger report request command issuing means can repeatedly issue the trigger report request command to the peripheral device at a predetermined time interval. By issuing the trigger report request command repeatedly and continuously, the host device can reliably acquire the peripheral device-side trigger no matter what timing it occurs.

  In the present invention, a communication interface (for example, IEEE 1394 to 1394b) compliant with another protocol capable of peer-to-peer communication with a peripheral device is incorporated on the host device side, and the peripheral device is connected to the terminal of the communication interface. It is also possible to connect them. In this hardware configuration, since a command for communication processing can be issued from the peripheral device side to the communication interface (that is, the host device), trigger report request command issuing means (host device side) or trigger occurrence report information return It is possible to shift to a reference technical mode that does not belong to the present invention, omitting the function according to the main communication protocol such as means (peripheral device side). However, this reference technical aspect has a drawback in that it is necessary to incorporate a module for handling another protocol for enabling the peer-to-peer communication in the system on the host device side, and the cost of the communication interface cannot be avoided. Because it is, it is not realistic.

  On the other hand, in the present invention, the peripheral device and the host device can be polled by the peripheral device from the host device side through a serial communication mechanism in which the reverse polling of the host device from the peripheral device side is impossible. Information transfer between the host device and the peripheral device for connecting and executing a communication event can be configured to be executed by serial communication in a form in which the host device polls the peripheral device. In this configuration, since the host device cannot be polled from the peripheral device side (that is, the peripheral device side is not given the right to start communication), the effect of the present invention is more effectively exhibited. In addition, the communication interface on the host device side for directly connecting the peripheral devices is greatly simplified, and the system configuration can be reduced in weight and cost. An example of such a serial communication standard is USB (Universal Serial Bus). Further, in this specification, a peripheral device that adopts the SCSI protocol as a main communication protocol and is connected to the host device by a serial communication bus according to the USB protocol is also referred to as a USB / SCSI type peripheral device.

  When USB is adopted, the peripheral device can be configured more specifically as follows. That is, a command analysis step for receiving a command from the host device and analyzing the command content, a data processing step for executing data processing reflecting the analysis content of the command, and response information indicating the result of the data processing are sent to the host device. A response information return step for replying is executed in this order, and an access control device for controlling communication processing on the peripheral device side, and mutual transfer of the command and response information is performed by the host device with a plurality of access control devices. And a serial communication unit that executes serial communication in a polling format. The access control device includes a transmission / reception unit that transmits / receives command and response information to / from the serial communication unit, and a control execution entity that interprets the command and performs data processing according to the content. The transmission / reception unit and the serial communication unit can be integrated in a dedicated IC. In this configuration, commands or response information according to a main communication protocol such as SCSI can be exchanged without problems via a bus for serial communication according to the USB protocol.

  More specifically, the serial communication unit on the peripheral device side performs the communication processing of the command and response information between the communication bus connection terminal for connecting the serial communication bus from the host device and the serial communication bus and the transmission / reception unit. A communication control unit that executes communication protocol unit connected to the communication bus connection terminal, and the protocol engine unit via a bidirectional endpoint for control including a FIFO memory. A control command unit that is connected and controls the transfer communication process can be provided. The transmission / reception unit has an input / output path to the protocol engine unit via an input endpoint to the protocol engine unit including a FIFO memory and an output endpoint from the protocol engine unit including a FIFO memory. Can be connected separately. In addition, the communication control unit receives from the host device side the identification information of the transmission / reception unit to be accessed and the identification information of the endpoint corresponding to the transmission / reception unit, and polls each transmission / reception unit as a target device. It can be configured to be. Endpoints serving as transmission / reception data buffers are provided independently on the transmission side and the reception side, and the data transfer direction can be easily specified depending on which endpoint is designated at the time of polling.

Next, in the communication system of the present invention,
A predetermined frame that is provided on the host device side and issues a survey request command requesting the peripheral device itself to perform a survey report process on the peripheral device, and indicates the content of the survey report instruction when the survey request command is issued Survey instruction data creating means for creating survey instruction data having a format and additional information written in a predetermined field of the frame, and survey instruction data transmitting means for transmitting the created survey instruction data to the peripheral device ,
Survey report data generating means provided in the peripheral device, receiving survey instruction data, and generating survey report data having a predetermined frame format;
A survey report data transmitting means provided in the peripheral device for transmitting the survey report data as response information to the host device;
Additional information extraction means provided on the peripheral device side for extracting additional information from a predetermined field of the received survey instruction data can be provided.

  In the present invention, the main communication protocol is mainly for transmitting / receiving data files to / from a storage device constituting a peripheral device, and control processing not supported by the main communication protocol (particularly, communication events on the peripheral device side). It is necessary to handle the information related to the processing that starts the process as additional information independent of the control information supported by the main communication protocol. It is meaningless to write such additional information in the main body of the data file to be transmitted / received. This is because when the content of the additional information is referred to on the host device side or peripheral device side for control execution etc., it is necessary to start up application software for opening the data file, which is not realistic at all. is there. However, according to the above configuration, additional information desired to be transmitted from the host device side to the peripheral device side can be obtained by using the investigation request event for requesting the peripheral device to perform the investigation report processing on the peripheral device itself. By writing in the predetermined field of the survey instruction data created when the command is issued, the data can be reliably transmitted without going through the data file under the control of the main communication protocol.

  Further, the investigation report data generation means can write corresponding additional information corresponding to the additional information from the host device side in a predetermined frame of the investigation report data, and the investigation report data transmission means The investigation report data in which the additional information is written can be transmitted as response information to the host device. Thus, the corresponding additional information that is to be sent from the peripheral device side to the host device side is written in a predetermined field of the investigation report data that is response information to the investigation request command, so that the data file is controlled under the control of the main communication protocol. It can be transmitted reliably without going through.

  Specifically, a survey request command can be used as the above-described trigger report request command. In this case, the peripheral device side trigger occurrence report instruction information is written as additional information in the investigation instruction data, and the trigger occurrence report information is written as corresponding additional information in the corresponding investigation report data. As a result, the peripheral device side trigger generation report instruction can be accurately transmitted to the peripheral device side, and the peripheral device side trigger on the peripheral device side is surely grasped by the trigger generation report information in the investigation report data. be able to.

  On the other hand, the investigation request command can also be used to start a communication event in which character information to be displayed on the display unit is transmitted from the host device to the peripheral device. In this case, character code information for specifying a character to be transmitted as additional information is written as additional information in the survey instruction data. Further, on the peripheral device side, display character data storage means for storing character data for display on the display unit in association with the character code, and character code information as additional information extracted by the additional information extraction means are supported. Display control means for reading the display character data from the display character data storage means and displaying it on the display unit is provided. In this way, even if there is no character string transfer command in the main communication protocol (especially the SCSI protocol), the character code of the character to be displayed on the display unit on the peripheral device side is transferred using the investigation request command. It becomes possible. By providing the display character data storage means on the peripheral device side, it is possible to display characters on the display unit using the display character data corresponding to the received character code. When the character string to be displayed is long, it can be divided and transmitted by executing a plurality of investigation request commands. Also, if the data size of the character code corresponding to one character, such as a 2-byte character (double-byte Kanji, symbol, etc.) exceeds the field size of the survey instruction data, one character code is divided and multiple survey requests are made. It is also possible to send it by executing a command.

  The investigation request command can also be used to start a communication event that notifies the peripheral device when a data file having a file name that overlaps with the data file received from the peripheral device exists in the storage area. . In this case, duplicate file name specifying information is written as additional information in the survey instruction data. Further, the peripheral device is provided with a duplicate file name display means for displaying the duplicate file name on the display unit based on the received duplicate file name specifying information, and there is a storage processing condition for instructing the host device for the displayed duplicate file. Selection input can be performed from the manual operation unit. In this case, the storage report condition instruction information for instructing the storage process condition can be written in the investigation report data as the corresponding additional information based on the input information from the manual operation unit, and the data file storage control means on the host device side The data file storage process can be executed in accordance with the storage process condition received from the peripheral device.

  With the above configuration, when the data file selected on the peripheral device side already exists in the storage area on the host device side, information indicating the existence can be displayed on the peripheral device side, and the duplicate file can be displayed. The corresponding processing can be instructed appropriately by setting the storage processing condition on the peripheral device side. In this case, it is possible to select one of the storage processing conditions to change the file name of the data file on the host device side or to change the file name of the data file on the storage medium side.

  The investigation instruction data creation means uses the occurrence report instruction information as the main storage information in the field defined in the main communication protocol so that information other than the occurrence report instruction information is stored as the main storage information to be stored in the investigation instruction data. It can be written in the form of When the main communication protocol conforms to an off-the-shelf communication standard such as the SCSI protocol, a dedicated field for (trigger) occurrence report instruction information, which is a technical concept generated for the first time in the present invention, is newly added in the frame of the investigation instruction data. There may be no room for setting. At this time, as described above, the occurrence report instruction information (including additional information) is written in the field prepared for the main storage information that is completely different from the original occurrence report instruction information in a form that is also used as the main storage information. By doing so, even when there is no room for providing a dedicated field as described above, the occurrence report instruction information can be written without any problem.

  For example, in the survey instruction data, when executing a communication event related to reading or writing of data to the storage medium according to the main communication protocol, the allocation length of the memory area on the storage medium assigned to the reading or writing process is set. The field to be used can be secured as an allocation length setting field. In this case, the occurrence report instruction information that is also used as the allocation length information can be written in the allocation length setting field, with the allocation length information as the main storage information. In this way, it is possible to transmit specific additional information not defined in the main communication protocol to the peripheral device side in a form that is also used as allocation length information, and the peripheral device side trigger generation report instruction information is transmitted to the peripheral device. Can be sent to the other side without any problems.

  In the main communication protocol, when the size of the allocation length setting field is set to a certain bit length, the following clever method exists to form a free area in which the additional information is written in the allocation length setting field. That is, the number of bits when the maximum value that can be set as the allocation length is expressed in bytes is set to be less than the total number of bits in the allocation length setting field. If an allocation length exceeding the maximum value is described in the allocation length setting field, the maximum value is determined as the actual setting value of the allocation length regardless of the described allocation length value. Then, different additional information contents including the occurrence report instruction information can be defined in a manner that uniquely associates with the redundant allocation length description value exceeding the maximum value. For example, when a CDB of an inquiry command (to be described later) in the SCSI protocol is used as the survey instruction data, this CDB consists only of fields allocated for SCSI protocol control, and there is no room for the user to write new data. Looks like not. However, by setting the maximum value that can be set as the allocation length as described above in the allocation length setting field that is originally the main storage information of the SCSI protocol, the maximum value is set to be less than the total number of bits of the allocation length setting field. It is possible to give a meaning as additional information including occurrence report instruction information to the setting description value of the redundant allocation length exceeding.

  Next, in the case of the SCSI protocol or the like, there are cases where some types of investigation request commands are prepared. In this case, what type of investigation request command is used as a trigger report request command may be a problem. For example, the peripheral device is configured as a storage device in which a storage medium capable of data access for both reading and writing of data is detachably mounted and data access to the storage medium is performed by a communication event. When the storage medium is replaced, the peripheral device includes a replacement notification information holding unit that holds replacement notification information for notifying the host device of the replacement of the storage medium, When the first type command is received, the exchange notification information held in the exchange notification information holding unit is cleared after the execution of the command, and when the second type command other than the first type command is received, In some cases, after the execution of the command, there is provided an exchange notification information holding control means for holding the exchange notification information holding state by the exchange notification information holding means. That. In this case, the use of the second type command is strongly recommended as the investigation request command used as the trigger report request command. This is because when the first type command is used for such a purpose, the exchange notification information is cleared at the end of the process, even though it is a trigger report request event that does not particularly require the exchange notification information. The system component (for example, a file system) that originally needs the exchange notification information on the side may not be able to obtain it, which may lead to troubles such as the storage contents of the storage medium being destroyed. It is.

  As the investigation request command, for example, a configuration / attribute investigation request command for instructing a peripheral device to report configuration / attribute identification information that is information for identifying the configuration and attributes of the peripheral device itself can be employed. Such a communication event related to specifying the configuration and attributes of the peripheral device itself indicates, for example, what type of peripheral device (device: target in the case of SCSI) is connected on the main communication protocol. In many cases, this is used for the purpose of executing recognition at the time of start-up. In the present invention, this is repeated at a predetermined timing even after device start-up for monitoring the generation of a peripheral device-side trigger in the peripheral device. Issue. The communication event defined by the configuration / attribute investigation request command is originally intended only to recognize the so-called “feature” of the peripheral device (which remains unchanged when the device is in use). When the storage medium is exchanged before and after the occurrence, it should not be unnecessarily affected in the exchange notification information holding state or the like, so it is desirable to prepare it as the second type command. By using this for monitoring the generation of the peripheral device side trigger, no matter how many times the command is repeatedly issued, the holding state of the exchange notification information is not affected, and the above-mentioned trouble can be prevented.

  When the main communication protocol is the SCSI protocol, it is desirable to use an inquiry command as the above-mentioned investigation request command. In this case, the investigation instruction data sent from the host device (initiator) to the peripheral device (target) describes the detailed contents of the inquiry command, CDB (Command Descriptor Block: command description block, and the frame format for each command conforms to the SCSI protocol. The investigation report data returned from the peripheral device (target) to the host device (initiator) is inquiry data (the frame format is defined in detail by the SCSI protocol). Table 1 shows a CDB format corresponding to the inquiry command.

  In the SCSI protocol, the type of inquiry data returned from the peripheral device (target) can be specified on the host device (initiator) side. Specifically, a field called EVPD (Enable Vital Product Data) (1 bit) and a field called page code (8 bits) are formed in the CDB corresponding to the inquiry command. As shown in Table 2, for a CDB in which “0” is described in the EVPD field (hereinafter abbreviated as CDB (0)), the inquiry data is related to the peripheral device specifications as shown in Table 3. Instead, standard inquiry data (hereinafter abbreviated as S / I data) whose format and contents are defined in common is returned. Of the S / I data, a free area that is not directly used for communication control by the SCSI protocol can be used as a description field of response information unique to the present invention (hereinafter referred to as unique response information) such as trigger generation report information.

  For example, in the S / I data, a fixed-length field (hereinafter referred to as a vendor-specific area) for describing information specific to a device vendor is provided. If there is a free area in this field, It can be used as a description field for response information unique to the present invention. Although the number of bits is very small, the following free space can also be used as a description field for response information unique to the present invention. In other words, the additional data length field (data length after byte 5 of S / I data) set to 8 bits may have a maximum data length of less than 8 bits due to the upper limit of the data frame length in S / I data. is there. In this case, when a data length exceeding the maximum data length is specified in the additional data length field, the maximum data length is specified regardless of the description content of the additional data length field. As a result, a range of bit values exceeding the maximum data length can be utilized as a “free area” for describing the specific response information substantially.

  On the other hand, as shown in Table 4, a CDB in which “1” is described in the EVPD field (hereinafter abbreviated as CDB (1)) provides detailed or device-specific information to the host device (initiator). As shown in Table 5, special inquiry data called VPD (Vital Product Data) is returned.

The VPD are defined several types, or to specify the VPD of which type to describe (specifically page code field of the CDB, pages Listing (Page _Code: 00 h), FRU ASCII information (page _code: 01 h _~7F h), the unit serial number (page code: ₈₀ h), the operation mode definition (page _code: 81 h), ASCII operation mode definition (page code: ₈₂ h), and vendor-specific format (page _code: C0 h _~FF h)). The peripheral device creates a VDP of the type specified in the page code field and returns it to the host device. In particular, in the VPD in the FRU ASCII information format and the ASCII operation mode definition format, a data length field in which necessary ASCII information is written and an ASCII information field specified by the data length are formed following the page length field. However, the following fields can be used as a “free area” for describing unique response information as a vendor specific area. For example, in the ASCII operation mode definition format VPD, if the ASCII information field is defined as a field having a small number of bytes (for example, 1 to 3 bytes) for describing the version information of the device, the remaining vendor-specific area It is possible to ensure a relatively large field length, and to write specific response information that is somewhat large in size.

  In the SCSI protocol, a change in an event or a state on a target (peripheral device) or one or a plurality of logical units included therein (or one or a plurality of storage medium mounting slots when the peripheral device is a storage device). However, when the operation occurs asynchronously with the operation of the host device (initiator), a function is provided for generating a unit attention condition for notifying the initiator. When the storage medium is exchanged in the peripheral device, the exchange notification information is reflected in the generated unit attention condition. In the SCSI protocol, when an inquiry command is issued to a peripheral device that has such a unit attention condition pending, the peripheral device does not clear the pending unit attention condition (however, Copy The issued Inquiry command is executed (created / returned Inquiry data) only when the Aborted (CA) state is generated. Therefore, when the response request event of the specific response information such as the trigger occurrence report information is activated, even if the storage medium is exchanged by using the inquiry command, the unit attention including the exchange notification information is used. Conditions are maintained and loss of exchange notification information can be prevented. It is clear that the inquiry command corresponds to the above-described second type command.

  In the SCSI protocol, another investigation request command called a Request Sense command can also be used. The Request Sense command is a command for requesting sense data for reporting, for example, an error cause and type to a peripheral device (target), and the sense data is described and returned as a survey report data in a frame of a prescribed format. In the present invention, it is also possible in principle to write specific response information such as trigger occurrence report information using the empty space of the sense data and return it to the host device. However, in the SCSI protocol, in the SCSI protocol, when a Request Sense command is issued to a peripheral device that is holding a unit attention condition, the peripheral device is configured to clear the pending unit attention condition. (However, only before the creation of the Copy Aborted (CA) state) When a storage medium is replaced, the unit attention condition including the replacement notification information is cleared and the replacement notification information is lost. There is a fear. That is, the Request Sense command corresponds to the first type command described above.

  Hereinafter, a communication system 1 according to an embodiment of the present invention will be described with reference to the drawings as appropriate. 1 is a perspective view of a multi-reader / writer 2 (storage device: an example of a peripheral device) applied to the communication system 1, FIG. 2 is a block diagram showing a schematic configuration of the multi-reader / writer 2, and FIG. It is a block diagram which shows schematic structure of PC3 (an example of a host apparatus) performed. Note that the configuration of the communication system 1 described below is merely an example for embodying the present invention, and it is natural that the configuration can be appropriately changed without departing from the gist of the present invention.

  As shown in FIG. 1A, the multi-reader / writer 2 includes a first slot 16 for inserting a first memory card 11 (for example, CF) as a removable storage medium on the front surface thereof, and a second memory card. A second slot 17 for inserting 12 (for example, SM), a third slot 18 for inserting a third memory card 13 (for example, MS), and a fourth memory card 14 (for example, SD). And a fourth slot 19. In the present embodiment, the multi-reader / writer 2 is described as an example of the peripheral device, but the present invention can also be applied to a single slot type reader / writer. Also, when a disk recording medium such as a CD-ROM, a DVD-ROM or a removable hard disk is used instead of a memory card such as CF or SM, an insertion section is provided that allows the disk recording medium to be detachably inserted. This is a so-called changer-type drive peripheral device. The present invention is also applicable to a communication system configured with the peripheral device.

  The multi-reader / writer 2 is configured as a USB / SCSI type peripheral device, and a USB terminal 24 for connecting a USB cable 25 (see FIG. 2) is provided on the back of the multi-reader / writer 2 as shown in FIG. 1B and FIG. Yes. In this embodiment, it is assumed that the SCSI-2 protocol is adopted as the main communication protocol. As shown in FIG. 2, the multi-reader / writer 2 includes therein a CPU 27 that controls each component, a ROM 28 that stores a control program, various data, and the like, and a RAM 29 that is a work area for operations by the CPU 27. An input / output control LSI 31 and a USB chip 32 are provided, and these are connected via a bus 33 so that data can be transferred to each other. The multi-reader / writer 2 performs data communication according to the SCSI protocol with the PC 3 to which the multi-reader / writer 2 is connected.

  Specifically, the ROM 28 stores a communication control program created based on the SCSI protocol and a table list of analysis data used for analyzing data (CDB) transmitted from the PC 3. In order for the reader / writer 2 to function as a target of a SCSI compatible device, a communication event execution control process corresponding to the received SCSI command is performed. The first to fourth memory cards 11 to 14 that are detachably mounted in the slots 16 to 19 are, for example, compact flash (CF: registered trademark), smart media (SM: registered trademark), memory stick (MS). : A registered trademark), an SD memory card (SD: registered trademark), and the like, a card-type storage medium equipped with a flash memory capable of data access such as data writing, rewriting, erasing, reading, and media loading confirmation by the PC 3. As the storage device, a drive device that reads data from a read-only storage medium such as a CD-ROM, a DVD-ROM, or a removable hard disk may be used.

  In accordance with the SCSI protocol, the PC 3 is given the right to determine a communication event as a host device, and the multi-reader / writer 2 connected to the PC 3 (host device: initiator) becomes a communication target (target) of the PC 3 (host device). . SCSI commands for instructing execution of communication events are sequentially issued from the PC 3 (host device) to the multi-reader / writer 2 (peripheral device), while the multi-reader / writer 2 (peripheral device) that has received the issued command. ) Sequentially executes data processing corresponding to the SCSI command, and returns response information corresponding to the execution result to the host device side. Further, the issuing direction of the SCSI command is restricted to one direction from the PC 3 (host device) side to the multi-reader / writer 2 (peripheral device) side.

  Next, the multi-reader / writer 2 generates a peripheral device-side trigger for prompting the host device to start a target communication event having a predetermined content based on a user operation on the peripheral device side. A function of trigger generation means is provided. Specifically, a keyboard 22 is provided on the upper surface of the casing as a manual operation unit that constitutes peripheral device side trigger generating means. Each button 22a, 22b, 22 constituting the keyboard 22 is provided with a switch that is independently energized by the pressing operation of the button, and the level of the switch output signal changes with the pressing / release of the button. This switch output signal can be used as a peripheral device side trigger signal. The peripheral device side trigger signal is input to the input control LSI 30 in FIG. In addition, a liquid crystal display panel (hereinafter referred to as an LCD) 21 constituting a display unit is connected to a bus 33 via a display control LSI 34.

  The input control LSI 30 receives the trigger signal on the peripheral device side and outputs a trigger detection data signal (which is a level signal) on the data bus at a different address for each button. The trigger detection data signal on the data bus is referred to when executing an inquiry command to be described later. If the trigger detection data at the address corresponding to each button indicates a “triggered” state, it corresponds to the created inquiry data. The corresponding additional information of the content of the button operated is written. That is, the operation state of the keyboard 22 is detected according to an instruction from the PC 3. Note that the trigger detection data signal is reset after the inquiry data is created. In this embodiment, the button 22a and the button 22b are scroll keys for scrolling up and down a plurality of lines of character strings displayed on the LCD 21 (reference numeral 22a is an up scroll key and reference numeral 22b is a down scroll key). Reference numeral 22c denotes an execution key for performing an operation of selecting a character string displayed on the LCD 21 (for example, when single-clicking) and confirming (for example, when double-clicking).

  Next, the USB chip 32 includes a command / data / status transmission / reception unit (hereinafter simply referred to as “transmission / reception unit”; transfer element transmission / reception unit) 341 provided in common to the external memory input / output control units 51 to 54. The USB protocol engine (protocol engine unit) 321 connected to the USB terminal (communication bus connection terminal) 24 and the USB control unit (control command unit) 331 for controlling the transfer communication processing are integrated.

  Here, a portion composed of a USB protocol engine (protocol engine unit) 321 and a USB control unit (control command unit) 331 corresponds to the communication control unit, and this communication control unit and a USB terminal (communication bus) The portion composed of the connection terminal 24 corresponds to the serial communication unit.

  Each USB control unit 331 is connected to a corresponding USB protocol engine 321 via a bidirectional endpoint for control including a FIFO memory. The transmission / reception unit 341 inputs / outputs the USB protocol engine 321 via an input endpoint to the USB protocol engine 321 including a FIFO memory and an output endpoint from the USB protocol engine 321 including a FIFO memory. Routes are connected in a separate form.

  Each of the communication control units including the USB protocol engine 321 and the USB control unit 331 receives the specific information of the transmission / reception unit 341 and the specific information of the endpoint corresponding to the transmission / reception unit 341 from the PC side. By polling the transmission / reception unit 341 as a target device, the data access destination is the external memory input / output control units 51 to 54 and the data transmission / reception direction is specified. As a matter of course, reverse polling of the PC 3 as the host device from the transmission / reception unit 341 side serving as the target device is not permitted in the USB protocol.

  The transmission / reception unit (transfer element transmission / reception unit) 341 performs transmission / reception with the USB protocol engine 321 according to the SCSI protocol. Here, the transfer element is a command (SCSI command) for specifying the content of the communication event exchanged with the PC 3 via the USB bus, and is returned from the peripheral device side corresponding to the execution of the communication event process. (If the processing content specified in the SCSI command is data access processing related to transmission / reception of data stored in the memory card, the data is also a transfer element).

  As shown in FIG. 3, the transmission / reception unit 341 includes a control register 81 (see FIG. 4), a status register 82 (see FIG. 5), a SCSI command buffer 83, a SCSI status buffer 84, a SCSI data DMA address register 85, a SCSI A data DMA count register 86 is provided. Details of these will be described later.

  The CPU 27 analyzes the command analysis step for analyzing the SCSI command received by the transmission / reception unit 341 and the communication event having the content specified by the SCSI command into the target external memory input / output control units 51 to 54 (that is, the reader / writer 2). When the target is a target, an event execution step performed with a plurality of logical units) and a status transmission step for transmitting the status to the transmission / reception unit 341 are performed in this order.

  In the multi-reader / writer 2, when reading / writing data from / to the inserted memory card, a memory area used for reading data from the memory card or a memory area used for storing data in the memory card Is assigned. The data length of the allocated memory area is called an allocation length. In general, the allocation length is set to a specified data length from the PC 3 that accesses the multi-reader / writer 2, but in this embodiment, the maximum value of the allocation length that can be set by the multi-reader / writer 2 is from the PC 3 side. It is set to less than the maximum value that can be specified.

  As shown in FIG. 6, the PC 3 includes a CPU 41 that controls each component, a ROM 42, a RAM 43, an HDD 44 that stores various software programs and data, a video control LSI 45, a USB chip 46, and a video terminal 47. And a USB terminal 48 having a plurality of input / output ports, which are connected to each other via the bus 100 so that data can be transferred to each other. These parts are integrated into a main control board called a so-called mother board. A display 56 is connected to the video terminal 47 via a video cable. The USB terminal 48 has a USB hub function. Input means such as a keyboard 57 and a mouse 58 are connected to the USB terminal 48, and the multi-reader / writer 2 is further connected.

  The ROM 42 stores instruction data that is transmitted to the multi-reader / writer 2 and causes the CPU 27 of the multi-reader / writer 2 to execute predetermined processing. The instruction data is stored in the HDD 44 or the ROM 42 in the form of a table list. In addition, in the program storage area of the HDD 44, it is possible to write and read data to / from the Windows 3 (registered trademark) SP3 (hereinafter referred to as “WIN2000”), which is an operation system of the PC 3, and the multi-reader / writer 2. A software program such as an R / W application is stored. These software programs are read by the CPU 41 and subjected to predetermined calculation processing, whereby each application can operate on the PC 3. The program storage area stores a data communication program according to the SCSI protocol with the multi reader / writer 2. In this embodiment, the PC 3 on which WIN2000 is installed will be described as an example. However, an OS such as Linux series or MacOS series may be installed. Of course, SP3 in Windows 2000 can be replaced with SP4.

The R / W application, the data communication program on the PC 3 side, and the control program on the reader / writer 2 side cooperate with each other to perform processing for functionally realizing the following means.
Trigger report request command issuing means: Peripheral device side that is realized by the R / W application on the PC 3 (host device) side and that occurs when the button (manual operation unit) 3 is operated in the reader / writer 2 (peripheral device) In order to monitor the trigger, according to the SCSI protocol (main communication protocol), a trigger report request command for requesting trigger generation report information as response information is an inquiry command, specifically, the above-mentioned CDB (1) is used. It is issued to the reader / writer 2 (peripheral device) as an inquiry command (hereinafter referred to as an Inq (1) command).
Trigger occurrence report information return means: The function is realized by the control program (in the ROM 28) on the reader / writer 2 side, and the trigger occurrence report information reflecting the presence or absence of the trigger on the peripheral device side is sent to the PC 3 (host device) as response information to the SCSI. Reply according to protocol.

Report information receiving means: The function is realized by the R / W application, and trigger generation report information is received from the reader / writer 2.
Target communication event activation means: When the function is realized by the R / W application, the presence or absence of the peripheral device side trigger is determined based on the content of the received trigger occurrence report information, and it is determined that the peripheral device side trigger exists Trigger the target communication event. As means for executing the target communication event, the following means are realized.

Data file selection / save event execution means: Generates a confirmation operation trigger as a peripheral device side trigger for confirming the selection contents of the data file by the keyboard 22 (manual operation unit). As the host device grasps the trigger occurrence report information from the multi-reader / writer 2 (peripheral device), the host device requests the peripheral device to transmit the data file selection confirmation contents and selects the data file. The host device requests the peripheral device to transmit the setting contents of the first communication event received on the host device side as the response information from the peripheral device and the storage processing condition by the manual operation unit, and the storage processing condition The second communication event is received on the host device side as the response information from the peripheral device, and the third communication event is that the selected data file is read by the peripheral device and transmitted to the host device.

  First, an outline of data communication performed between the PC 3 and the reader / writer 2 connected via USB to the PC 3 via the USB-I / F 78 will be described with reference to FIG. The OS 70 includes a GUI (Graphical User Interface) 71, a file system 72, and an OS kernel 73, and the basic system is configured. The GUI 71 is a user interface that realizes a user input operation using a computer graphics and a pointing device such as a mouse, and the file system 72 is a method of managing data using files and folders in the computer and its management system. It is. The OS kernel 73 is software that implements basic functions such as monitoring applications and peripheral devices. The PC 3 is preinstalled with driver software 74 so that the reader / writer 2 can be accessed. The driver software 74 is installed in the OS kernel 73 in a modular state.

  For example, it is assumed that an explorer 75 and an R / W application 76, which are examples of applications for accessing the reader / writer 2, are activated on the PC 3. As is well known, the explorer 75 is for managing files and folders. The explorer 75 is created in conformity with the OS 70 system and is generally recognized as a function of the OS 70. Therefore, the explorer 75 communicates with the reader / writer 2 via the file system 72. On the other hand, the R / W application 76 is unique application software developed by the manufacturer of the reader / writer 2, for example, and performs a process of writing data to a recording medium inserted in the reader / writer 2 or a process of reading data. Is. Generally, the R / W application 76 is created without conforming to the OS 70 because the specification of the file system 72 is not disclosed.

  First, a case where the reader / writer 2 is accessed from the explorer 75 will be described. When the OS 70 is activated and the explorer 75 is activated, the explorer 75 issues an inquiry command to the OS kernel 73 via the file system 72. All SCSI commands including the inquiry command are issued to the SCSI command processing entrance 79 virtually provided in the OS kernel 73. When the inquiry command is issued, the corresponding CDB (here, CDB (0); Table 2) is transmitted to the reader / writer 2, and the reader / writer 2 receives the model, device name, SCSI-ID, Inquiry data (in this case, S / I data (Table 3)) including configuration information such as presence / absence of LUN (Logical Unit Number) and memory card type is created and returned to the PC 3. Thereby, the reader / writer 2 is recognized.

  When the reader / writer 2 is recognized, a drive icon of the reader / writer 2 is generated on the explorer 75 by the GUI 71. When a data read instruction is input, for example, when the user accesses the drive icon using a mouse or the like, the explorer 75 works on the file system 72 to read the OS kernel 73 with a Read command (SCSI command). Issue an example). On the other hand, similarly, when a write instruction is input, a write command (an example of a SCSI command) is issued to the OS kernel 73. These command data are transferred to the reader / writer 2 via an I / F such as a USB, and reading or writing according to the command is executed on the reader / writer 2 side. The Inquiry command is also issued when the reader / writer 2 is connected to the PC 3 or when the power of the PC 3 is reset while the reader / writer 2 is connected.

  Next, a case where the reader / writer 2 is accessed from the R / W application 76 will be described. When the R / W application 76 is activated, a request to release the data bus only to the R / W application is issued to the OS kernel 73. In response to this request, the OS kernel 73 makes the R / W application 76 occupy the data bus. In other words, the SCSI command issued from the file 72 to the SCSI command processing entrance 79 is not accepted by the SCSI command processing entrance 79. Therefore, the file system 72 cannot access the reader / writer 2 while the R / W application 76 is activated. When the R / W application 76 is activated, an input screen (user interface screen) programmed by the R / W application 76 is displayed on the display by the GUI 71. Also, the driver software 74 issues an inquiry command to the OS kernel 73, and returns the inquiry data (in this case, S / I data in Table 3) as response information. Configuration information is acquired. Thereby, the reader / writer 2 is recognized. Thereafter, reading or writing of data is executed on the reader / writer 2 side in accordance with a Read command or a Write command issued to the OS kernel 73 by the driver software 74.

  The reader / writer 2 is recognized as follows. That is, first, CDB (0) (Table 2) generated when an inquiry command is issued to the OS kernel 73 is transmitted to the reader / writer 2. The reader / writer 2 that has received the CDB (0) refers to various information included in the CDB (0), generates configuration information according to the information, and generates S / I data including the configuration information ( Table 3) is returned to PC3. The reader / writer 2 is recognized based on the returned S / I data.

  When a memory card is exchanged (that is, an event or a state is changed) on any slot (or external memory input / output control unit: logical unit) on the reader / writer 2 (target: peripheral device), A unit attention condition for notifying the PC 3 (initiator) is generated. The file system of the PC 3 recognizes the replacement of the memory card with reference to the unit attention condition, and updates file information such as FAT (file allocation table). When an inquiry command is issued to a logical unit that holds such a unit attention condition, the logical unit executes the inquiry command without clearing the pending unit attention condition. That is, even when the inquiry command is executed, the replacement notification information of the memory card reflected in the unit attention condition is not erased and is retained. Access can be performed without problems.

  Next, a more specific operation of the reader / writer 2 will be described using the flowchart of FIG. In the following description, only processing for one slot is performed. For a plurality of slots, the processing is performed in parallel by interrupt processing. When the CPU 27 is turned on by the power (bus power) supplied from the PC 3 via the USB cable (T1), the CPU 27 enters a state of permitting an interrupt from the USB chip 32 (T2). In the USB chip 32, the command transmitted on the USB bus from the PC 3 side is transferred to the transmission / reception unit 341 by the operation of the USB protocol engine 321 and the USB control unit 331. Note that no response indicating that a command has been received is returned yet.

  When receiving the command, the transmission / reception unit 341 sets the “command reception completion” bit of the status register 82 to 1 and interrupts the CPU 27. In this case, the CPU 27 can grasp what the interrupt is for by referring to the status register 82. The received command is stored in the SCSI command buffer 83.

  When there is an interrupt (T3: YES) and the reception of the SCSI command is completed (T4: YES), the CPU 27 interprets the command received by the transmission / reception unit 341 (T5). That is, when the CPU 27 refers to the status register 82 of the transmission / reception unit 341 and knows that the transmission / reception unit 341 has received a command, the CPU 27 acquires the command from the SCSI command buffer 83 and interprets it. Thereby, the CPU 27 grasps the presence / absence, transmission direction, and size of the SCSI data.

  When the CPU 27 recognizes that there is no SCSI data by interpreting the command (for example, in the case of an inquiry command or a test unit ready command), and the CPU 27 recognizes that the transmission direction of the SCSI data is device → PC (transmission) (for example, In the case of a Read command) (T6: YES), 1 is written in the “command acceptance complete” bit and “status register clear” bit of the control register 81 of the transmission / reception unit 341 (T7).

  The transmission / reception unit 341 returns a response indicating that the command has been received to the PC when 1 is written in the “command acceptance complete” bit in T7. Here, when the response is received, the PC 3 side receives the SCSI status if there is no SCSI data, and if the SCSI data transmission direction is device → PC, the next is reception of the SCSI data. Transition to a device waiting state.

  On the other hand, when the CPU 27 recognizes that the SCSI data transmission direction is PC → device (reception) by interpreting the command (for example, in the case of the Write command) (T6: NO), the CPU 27 receives the SCSI data from the PC3. Prepare to receive (T8). Specifically, an area necessary for reception is secured on the RAM 29, the head address is written in the SCSI data DMA address register 85, and the number of received bytes is written in the SCSI data DMA count register 86. Thereafter, 1 is written in the “command acceptance complete” bit and “status register clear” bit of the control register 81 of the transmission / reception unit 341 (T9).

  The transmission / reception unit 341 returns a response indicating that the command has been received to the PC 3 when 1 is written in the “command acceptance complete” bit in T9. Here, when receiving the response, the PC 3 side interprets the command on the device side and recognizes that it is ready to receive the SCSI data, and starts transmission of the SCSI data.

  Then, when the SCSI data DMA count register 86 becomes 0, the transmission / reception unit 341 sets the “data reception completion” bit of the status register 82 to 1 and interrupts the CPU 27.

  When there is an interrupt (T10: YES), the CPU 27 writes 1 to the “data reception completion” bit and the “status register clear” bit of the control register 81 of the transmission / reception unit 341 to complete the reception of the SCSI data (T11: YES). Here, the PC 3 side is notified that the SCSI data has arrived at the device, and the next is the reception of the SCSI status.

  After T7 and T11 (YES), the CPU 27 executes the command (T12). For example, if it is a Test Unit Ready command, it is determined whether or not the first to fourth memory cards 11 to 14 are inserted. For example, in the case of a Read command, data is read from the first to fourth memory cards 11 to 14. For example, in the case of the Write command, since the data to be written is received from the PC 3 at this time (T8 to T11 described above), it is written to the first to fourth memory cards 11 to 14.

  Next, when the transmission direction of the SCSI data is device → PC (transmission) (for example, in the case of a Read command) (T13: YES), the CPU 27 prepares to transmit the read data to the PC 3 (T14). ). More specifically, the read data is stored on the RAM 29 while securing the area necessary for transmission, the head address is written in the SCSI data DMA address register 85, and the number of received bytes is stored in the SCSI data DMA count register 86. Write. Then, 1 is written in the “data transmission start” bit of the control register 81 of the transmission / reception unit 341.

  The transmission / reception unit 341 starts transferring SCSI data to the PC 3 when 1 is written in the “data transmission start” bit in T14. Then, when the transfer of the SCSI data is completed, the transmission / reception unit 341 sets the “data transmission completion” bit of the status register 82 to 1 and interrupts the CPU 27.

  When there is an interrupt (T15: YES), the CPU 27 grasps that the transfer of the SCSI data is finished. Therefore, the CPU 27 writes 1 to the “status register clear” bit of the control register 81 of the transmission / reception unit 341 to transmit the SCSI data. Is completed (T16: YES).

  After T13 (NO) and T16 (YES), the CPU 27 starts transmission of the SCSI status (T17). Specifically, since the CPU 27 has already determined the status to be returned to the PC 3 in the above processing, the status is written in the SCSI status buffer 84 and “status transmission start” of the control register 81 of the transmission / reception unit 341 is written. Write 1 to bit and start sending SCSI status.

  The transmission / reception unit 341 starts transmission of the SCSI status to the PC 3 when 1 is written in the “status transmission start” bit in T17. Upon receiving the response that received the SCSI status from the PC 3 side, the transmission / reception unit 341 sets the “status transmission complete” bit in the status register 82 to 1 and interrupts the CPU 27.

  When there is an interrupt (T18: YES), the CPU 27 grasps that the transmission of the SCSI status is finished. Therefore, the CPU 27 writes 1 to the “status register clear” bit of the control register 81 of the transmission / reception unit 341 to transmit the SCSI data. Is completed (T19: YES). As a result, the status register 82 of the transmission / reception unit 341 is cleared, and the original state is restored.

  Next, an example of the flow of data communication processing according to the main function of the present invention using inquiry data in the communication system 1 will be described. Note that the processing in each step (function implementation means described in claims) is performed by each component being controlled by the CPU 41 of the PC 3 or the CPU 27 of the multi-reader / writer 2. FIG. 9 is a flowchart showing the flow of main processing. That is, when the multi-reader / writer 2 is connected to the PC 3 and each apparatus is powered on, first, a drive allocation process (S1) for allocating a drive to an unknown device connected to the PC 3 is executed. In this embodiment, since only the multi-reader / writer 2 is connected as a device, a drive is assigned only to this.

  Next, drive setting processing (S2) for setting the drive selected by the user as the communication partner is performed. When the drive is set, a device (multi-reader / writer 2 in the present embodiment) corresponding to the set drive is recognized as a communication partner. Then, a memory card monitoring process (S3) and a file selection monitoring process (S4) for monitoring whether or not the memory cards 11 to 14 are mounted (or exchanged) on the multi-reader / writer 2 are performed. The main processing routine is repeatedly and regularly executed at regular time intervals (for example, 100 ms to 1000 ms: 500 ms, for example) by using an activation trigger periodically issued from the activation management timer routine.

  FIG. 10 shows the details of the drive allocation process (S1) executed by the CPU 41 in the PC 3. First, a drive to be referred (hereinafter referred to as “reference drive”) is initialized to A drive (S101). The reference drive means a drive that can be allocated on the PC 3 side, and when there are a plurality of the drives, they are referred to in ascending order during the drive allocation process. The reference drive is managed by the OS kernel of WIN2000 of PC3. In the present embodiment, the number of drives that can be allocated is 26 from A to Z.

  When the reference drive is set, the CPU 41 then issues an inquiry command (hereinafter referred to as “Inq (0) command”) for returning S / I data from the device to which the drive is assigned to the reference drive. (S102). Actually, the CPU 41 issues the Inq (0) command to the OS kernel, and the OS kernel treats the Inq (0) command as being issued to the reference drive. Then, a CDB (0) in which the EVPD area is set to “0” is generated by the OS kernel and transmitted to the unknown device associated with the reference drive. The SCSI standard defines that S / I data is returned when the EVPD area is set to “0”. Specific examples of CDB (0) are shown in Table 2 as described above. In the data column of Table 2, each data is shown in hexadecimal notation. Unless otherwise specified in this specification, all data fields are shown in hexadecimal notation.

  If there is a device associated with the reference drive and the device is a device that can process a SCSI command (a SCSI command compatible device), S / I data is returned from the device. On the other hand, if the device does not exist, or if the device exists, the device cannot process the SCSI command (device that does not support the SCSI command), the S / I data is not returned from the device. In S103, the CPU 41 makes an error determination based on whether or not S / I data is returned (S103). Specifically, when no S / I data is returned, it is determined as an error (Yes in S103). In this case, the subsequent processing proceeds to step S107. Further, when there is a reply of S / I data, it is not determined as an error (No side of S103). That is, it is determined that there is a device associated with the reference drive. In this case, the subsequent processing proceeds to step S104.

  If it is determined in S103 that there is no error, whether or not the device associated with the reference drive is a device that can be communicated based on the returned S / I data, that is, whether or not it is a communicable device. Determined. In the present embodiment, this step is performed to determine whether or not the device associated with the reference drive is the multi-reader / writer 2. In the present embodiment, the S / I data shown in Table 3 is returned from the multi-reader / writer 2 to the PC 3, and the determination process in this step is byte 0 of the returned S / I data. The data of the area of byte 1 and the area of byte 1, or the vendor ID of the area of bytes 8 to 15 and the product ID of the area of bytes 16 to 31 match the ID information registered in advance on the PC 3 side. Done depending on whether or not. If it is determined in this step that the device is communicable (Yes in S104), the process proceeds to step S105. If it is determined that the device is not communicable (No in S104), the process proceeds to S107. Proceed to In Table 3, the data “0x00” in the byte 0 area indicates a direct access device, and the data “0x80” in the byte 1 area indicates a removable storage medium. Since the contents described in each byte area are defined by the SCSI standard, refer to the standard for details.

  When the process proceeds to S105, the CPU 41 determines whether or not the LUN of the reference drive is “0” based on the returned S / I data. This determination is made based on the data in the area of byte 54 of the vendor specific area in the S / I data. In the present embodiment, as described above, the S / I data shown in Table 3 is returned from the multi-reader / writer 2 to the PC 3. Further, as described in the remarks column of the byte 54 area of Table 3, when the multi reader / writer 2 returns S / I data, the multi reader / writer 2 is added to the upper 4 bits of the byte 54 area. Information indicating the physical I / F (information indicating USB in the present embodiment) is stored, and programmed to store the LUN number in the lower 4 bits. Therefore, the CPU 41 can acquire the LUN information by referring to the data in the byte 54 area. Thereby, the determination process of the said step can be performed. For example, when “0x10” is stored in the area of the byte 54, it is acquired that the physical I / F is a USB connector and LUN is 0, and “0x23” is stored. Is obtained that the physical I / F is a SCSI connector and the LUN is 3.

  If it is determined in S105 that the LUN is “0” (Yes in S105), the process proceeds to S106, and if it is determined that the LUN is not “0” (No in S105), the process proceeds to S107. When connected to the PC 3 on which WIN2000 is installed, even if information such as LUN = 1 is stored in the byte 54 area on the multi-reader / writer 2 side, it is recognized that LUN = 0 on the PC 3 side. It has become. Therefore, the process of S105 always proceeds to the Yes side. In this case, the determination process in S105 does not make sense and may be omitted.

  In S106, a process of adding the current reference drive to the corresponding drive list is executed. The corresponding drive list is a list of reference drives to which drives are finally assigned. Specifically, the corresponding drive list is expanded in a predetermined storage area of the RAM 43, and the corresponding reference drive is written in the storage area. Thereafter, the process proceeds to S107.

  In S107, the CPU 41 determines whether or not the reference drive is the Z drive. For example, it is possible to determine whether the current reference drive is the Z drive by causing the counter memory or the like to count the reference order of the drives and monitoring the counter value by the CPU 41. Such determination is performed to determine whether the set reference drive is the last. Here, if it is determined that the reference drive is the Z drive, there is no drive that can be referred to, and the subsequent process advances to S109. If it is determined that the reference drive is not the Z drive, after setting the reference drive as the next drive (S108), the processing from S102 is repeated until it is determined Yes in S107.

  When the process proceeds to S109, here, a drive is allocated based on the corresponding drive list. Thereby, a series of drive allocation processes (S1) are complete | finished. In the present embodiment, since only the multi-reader / writer 2 is connected as an external storage device, the multi-reader / writer 2 is assigned to the A drive and is not assigned to any other drive.

  Next, FIG. 11 shows details of the drive setting process (S2). In S201, it is determined whether there is a drive (hereinafter referred to as “corresponding drive”) allocated by the drive allocation process (S1) (S201). That is, it is determined whether or not a predetermined device is assigned to any of the drives that can be assigned by the PC 3. In the present embodiment, since there is an A drive to which the multi-reader / writer 2 is assigned, it is determined that there is a corresponding drive. Thereafter, it is determined whether there is one corresponding drive (S202). On the other hand, if it is determined in S201 that the corresponding drive does not exist (No side in S201), the process ends because there is no communication target.

  If it is determined in S202 that there is one corresponding drive (Yes in S202), the corresponding drive is set as a communication target (S205). That is, a device associated with the corresponding drive is set as a communication target. In the present embodiment, the A drive is set as a communication target. In other words, the multi-reader / writer 2 is set as a communication target device.

  On the other hand, when it is determined that there are a plurality of corresponding drives (No in S202), an icon indicating the corresponding drive is displayed in a dialog (S203). Thereafter, when a desired corresponding drive is selected by selecting any icon from the user (S204), the selected corresponding drive is set as a communication target (S205). Even when no icon is selected, for example, when a priority is set for each corresponding drive, the corresponding drive with the highest priority is automatically set as a communication target. Thereby, a series of drive setting processes (S2) are complete | finished.

  Next, FIG. 12 shows the details of the peripheral device side trigger monitoring process (S3). First, on the PC 3 side, an inquiry command (hereinafter referred to as “Inq (1) command”) for returning a VPD (Vital Product Data) of the multi-reader / writer 2 is issued from the multi-reader / writer 2 to the A drive. (S301). Actually, the Inq (1) command is issued to the OS kernel 73 and is treated as being issued to the A drive by the OS kernel 73. When the Inq (1) command is issued, the OS kernel 73 generates a CDB (1) in which the EVPD area is set to “1”, and the USB cable 25 is connected to the multi-reader / writer 2 associated with the A drive. Sent through. Table 4 shows the CDB (1) generated at this time. That is, the page code “0xE0” is described in the byte 2 area of the CDB (1).

  In the area of byte 4 of the CDB (1), that is, the allocation length area, “0x10” (“00010000” in binary notation) is stored. Originally, the data length required for the connected device is stored in the allocation length area. In the present embodiment, the maximum value of the allocation length of the multi-reader / writer 2 is set in advance to a fixed length (here, it is assumed to be 15 bytes, but is not limited to this). This number “15” can be expressed by the lower 4 bits. According to the SCSI standard, the allocation length of the multi-reader / writer 2 is set to the maximum value, that is, 15 bytes even if a numerical value greater than or equal to the maximum value set in the multi-reader / writer 2 is designated as the allocation length. . Therefore, even if “0x10” is described in the allocation length area, or “0x11” or more is described, the allocation length is set to 15 bytes. This means that if any one of the upper 4 bits of the allocation length area data is “1”, the data in the allocation length area is any data (also used as the setting value of the allocation length). It means that it can be used freely as additional information). That is, by setting any one of the upper 4 bits to “1”, bits other than the bit in the allocation length area can be reserved as a virtual free area. By adding arbitrary data to the virtual empty area secured in this way, data communication according to the additional information can be performed between the PC 3 and the multi-reader / writer 2.

  The allocation length is not always set to a fixed length (here, 15 bytes), but may be set to a maximum value according to the page code of CDB (1). For example, in the case of page code “0xE0”, the maximum value of the allocation length is set to a fixed length of 15 bytes, and in the case of page code “0xE2”, it is set to a fixed length of 9 bytes. The setting process corresponds to the fixed length correspondence list stored in the ROM 28 in advance according to the read content of the page code read by the CPU 27 of the multi-reader / writer 2 that has received the CDB (1). This is done by selecting a fixed length. Of course, the allocation length set to 15 bytes or 9 bytes can be arbitrarily set.

  Tables 6 and 7 categorize the communication data added to the empty area secured in the allocation length area. As shown in the data content column of each table, each data defines what it means. Specifically, refer to the description in the data content column. Table 6 shows communication data transmitted when the page code is “0xE0”, and Table 7 shows communication data transmitted when the page code is “0xE2”. If this page code (investigation instruction data type identification information) is changed in CDB (investigation instruction data), another investigation instruction data format having a different allocation length maximum value and additional information content can be generated.

  The left column of Tables 6 and 7 shows the data itself described in the allocation length area, and the right column shows the meaning of the data. When the data in the left column is transmitted from the PC 3 side to the multi-reader / writer 2, on the multi-reader / writer 2 side, the CPU 27 extracts the allocation length area data from the received CDB (1), and the extracted data The contents are analyzed, and processing according to the contents of the analyzed data is executed. The contents shown in Tables 6 and 7 are made into a table list and stored in advance in the HDD 44 or ROM 42 of the PC 3 and the ROM 28 of the multi-reader / writer 2.

  In CDB (1) generated by issuing the Inq (1) command in S301, “0x10” is described in the allocation length area as shown in Table 5. Therefore, the Inq (1) command means a command for causing the multi-reader / writer 2 to detect whether or not a memory card is installed from the PC 3. On the other hand, on the multi-reader / writer 2 side, the transmitted CDB (1) is received. Thereafter, the CPU 27 extracts the data “0x10” of the allocation length area in the CDB (1), and performs a process of detecting whether or not a memory card is installed according to the data (S302).

  When the detection of the presence / absence of the memory card is completed, the detection result is returned to the PC 3 by the CPU 27 (S303). Specifically, the reply process is performed by writing the detection result in the VPD that is generated after receiving the CDB (1) and returned to the PC 3. More specifically, as shown in Table 8, the presence / absence of occurrence of the memory card is written in the area of byte 7. In this embodiment, “0x00” is written when there is no mounting, and “0x01” is written when there is mounting. Table 8 shows the VPD in the case where the attachment has occurred.

  Subsequently, the PC 3 side receives the VPD in Table 8 returned from the multi-reader / writer 2 and refers to the byte 7 area of the VPD to determine whether or not a memory card is attached (S304). ). Here, if it is determined that the memory card is not installed (B side in S304), the following steps are all skipped and the process ends.

  On the other hand, if it is determined that a memory card is installed (A side in S304), the PC 3 side uses the file system already described to search for a data file in the installed memory card, and a file list (folder). Including structure).

  Then, based on the created file list data, character string data for displaying the file list on the LCD 21 on the reader / writer 2 side is created (S308), and stored in the RAM 29 as file list character string data. The character string data is bit code data (character code) corresponding to the character to be displayed on a one-to-one basis, and an off-the-shelf code such as a JIS code, a shift JIS code, or an ASCII code may be used as it is. May be used. However, if the display character data table on the peripheral device side (for example, in the ROM 28: the display data itself is bitmap type or outline type font data) is created using the off-the-shelf code, A table indicating the correspondence with the unique code may be separately prepared on the peripheral device side (for example, in the ROM 28), and the unique code may be converted into the ready-made code with reference to this table and used for display.

  The created character string data is transmitted to the multi-reader / writer 2 (S309). Such transmission processing is performed according to the processing procedure after step S401 shown in the flowchart of FIG. First, an Inq (1) command is issued (step S401). The CDB (1) data generated by issuing this Inq (1) command is transmitted to the multi-reader / writer 2. Note that the VPD is returned from the multi-reader / writer 2 by issuing the Inq (1) command, but it is determined that no reply data is added to the VPD in the case of character string transmission. Therefore, the description of the VPD reply process is omitted here.

  More specifically, in step S401, CDB (1) data in which “0xE2” is described in the byte 2 area and “0x18” is described in the allocation length area is generated as a page code. Accordingly, the Inq (1) command issued in this step sets a pointer at the head of the character string storage area (storage area in the RAM 29) corresponding to the character string number indicated by “0x90” based on Table 7. It is a request command to make it happen. Of course, this request command is issued to the multi-reader / writer 2. The pointer means an index that indicates a position for storing a character cut out in step S402 described later.

  Subsequently, in step S402, characters are cut out from the file list display character string data stored in the RAM 43 of the PC 3 in order from the beginning. Thereafter, in step S403, the CPU 41 determines whether or not the character cut out in step S402 is a terminal character (S403). Such processing is determined by whether or not the data indicating the extracted character is “0x00”. Since “0x00” does not indicate a character, if it is determined in this step that it is “0x00”, it is determined that it is a terminal character. If it is determined that the extracted character is a terminal character, the process proceeds to step S406. On the other hand, if it is determined that the extracted character is not a terminal character, the process proceeds to step S404. Here, the Inq (1) command is issued, and “0xE2” is generated as the page code, and the CDB (1) data in which the character data extracted in step S402 is described in the allocation length area is generated. Then, the generated CDB (1) data is transmitted to the multi-reader / writer 2.

  After the transmission of the CDB (1) data, the character data cut-out position is set to the next character (S405), and then the processing from step S402 is repeatedly executed. Thereafter, when the process proceeds to step S406, an Inq (1) command is issued, and CDB (1) data in which “0xE2” is described in the byte 2 area and “0x17” is described in the allocation length area as the page code is obtained. Generated. This is a request command for filling all bit areas after the area where the last stored character (that is, the last character) is stored in the current character string storage area with “0x00”. In other words, “0x00” is added after the end of the data transmitted to the multi-reader / writer 2 and stored in the RAM 29 to align the stored data with bit data of a predetermined length (for example, 128 bits). It is a request command. After step S406, the transmission process (S309) of FIG. 12 is completed.

  When data is transmitted by the transmission process (S309) shown in FIG. 12, the transmitted data is received on the multi-reader / writer 2 side, and the received data is stored in the RAM 29 (S310). Actually, each time the characters cut out in step S406 (see FIG. 8) are transmitted one by one, the character data is sequentially stored in the RAM 29.

  After the transmission process (S309), the Inq (1) command is issued again on the PC 3 side, and the CDB (1) data generated thereby is transmitted to the multi-reader / writer 2 (S311). Table 9 shows the CDB (1) data generated at this time. As shown in Table 9, since “0xE0” is described in the byte 2 area and “0x11” is described in the allocation length area, the Inq (1) command issued at this time is Is a request command for transferring the data stored in the character string storage area (storage area in the RAM 29) of the character string number corresponding to the number indicated by the data transmitted to the liquid crystal display unit 21 of the multi-reader / writer 2. Understandable.

  Thereafter, the Inq (1) command is issued again, and “0xE0” is described as the page code in the byte 2 area, and data “0x90” indicating the character string number in which the character data is stored in the allocation length area is described. (1) Data is transmitted to the multi-reader / writer 2 (S312). Therefore, when the CDB (1) data is received by the multi-reader / writer 2, the received data (character data) stored in the character string storage area corresponding to the character string number transmitted in step S310 by the CPU 27 is obtained. It is read out and transferred to the liquid crystal display unit 21. As a result, the data transmitted from the PC 3 is displayed on the liquid crystal display unit 21.

  In the present embodiment, the character data for displaying the file list is transmitted to the reader / writer 2 at the same time when the memory card is mounted and stored in the RAM 29 in FIG. The display on the LCD 21, the scroll processing on the LCD 21 for browsing, and the file selection processing on the displayed file list are all performed by the display control program on the reader / writer (peripheral device) side in the ROM 28. This is executed in cooperation with the display control LSI 34. The output of the keyboard 22 is also distributed to the display control LSI 34.

  As described above, the printing apparatus for the CDB (1) data in which the issue of the Inq (1) command on the PC 3 side and the additional information (in this case, information requesting the presence or absence of the selection confirmation operation of the image data file) is written. Corresponding additional data for transmitting to 80 (multi-reader / writer 2) and responding to the additional data from the printing apparatus 80 (multi-reader / writer 2) (in this case, information reporting the presence / absence of a selection confirmation operation) A series of communication processing peculiar to the present invention for returning the VPE in which is written is also referred to as “Inq (1) / VPE additional communication”.

  Step 1 in FIG. 15 shows a display example of the file list on the LCD 21. A plurality of character string data indicating the folder name of the upper folder F are acquired, but only a part of the character string data is displayed on the display screen of the LCD 21. When the scroll keys 22a and 22b in FIG. 2A are operated, the character string data (upper folder F) is scrolled up and down as shown in step 2, and the hidden character string data can be displayed.

  Select the upper folder F that is displayed (in this embodiment, the state displayed on the LCD 21 by scrolling also serves as the selected state, but a cursor may be used separately), and the confirmation button 22c is single-clicked. For example, as shown in step 3, the upper folder F is opened and a list of lower folders SF inside the upper folder F is displayed. In this state, as shown in step 4, if the corresponding upper folder F is selected again and single-clicked, the upper folder F is closed and the state returns to step 3. On the other hand, if one of the lower folders SF is selected and the confirm button 22c is single-clicked, as shown in step 5, the selected lower folder SF is opened, and a list of data files DF therein is displayed. As described above, the process of repeatedly clicking to move between folder hierarchies is well known.

  If a list of data files DF is displayed, if a desired data file DF is selected and the confirmation button 22c is single-clicked, the data file DF is temporarily selected as shown in step 6 (if single-clicking again, temporary selection is performed). The display of the temporarily selected data file DF is changed to a temporarily selected display state different from the unselected state by inversion, emphasis, etc. When the provisional selection is completed, the temporarily selected data file is displayed. If one of the DFs is displayed on the LCD 22 and the confirm button 22c is double-clicked, the selection state of the temporarily selected data file DF is confirmed as shown in step 8.

  Next, FIG. 14 shows the details of the file selection monitoring process (S4). On the PC 3 side, a new Inq (1) command for acquiring file selection information from the reader / writer 2 is issued, and “0x13” is described in the allocation length area of the generated CDB (1) (S1301). . From Table 6, this Inq (1) command means that this is an instruction for transmitting the selected state of the data file DF from the PC 3 to the multi-reader / writer 2. On the other hand, on the multi-reader / writer 2 side, the transmitted CDB (1) is received. Thereafter, the data “0x13” of the allocation length area in the CDB (1) is extracted by the CPU 27, and the selection state of the data file DF is set in the VPD generated after receiving the CDB (1) according to the data. Write (S1304) and return to PC 3 (S1305).

  The PC 3 receives the VPD returned from the multi-reader / writer 2 and refers to the byte 7 area of the VPD to determine what the data file DF has been selected and confirmed (S1306). If the data file DF selected and confirmed in S1307 exists, the data corresponding to the selected data file of the memory card (storage medium) attached to the multi-reader / writer 2 is added to the operation-linked file processing routine described later. Command predetermined file processing (communication event) including file reception.

  On the PC 3 side, setting customization processing relating to storage of the received data file can be performed in advance. FIG. 17 shows the flow of setting customization processing. In S501, the file transfer mode from the multi-reader / writer 2 is input / selected with the mouse 58 or the keyboard 57. In the file transfer mode, the data file transferred from the memory cards 11 to 14 is copied to a predetermined folder (storage area) on the HDD 44 (data file storage means) (in this case, from the memory cards 11 to 14). Data file is not deleted) and copy mode and move mode (moving: the data file is deleted from the memory cards 11 to 14), and either of them is performed in S502 to S506 in accordance with the above input contents. Selectable. In S507, an input for designating the storage destination of the data file is performed. For example, as is well known, the file directory structure is displayed on the display 56 in the form of a folder tree, and a folder to be stored can be selected by clicking with the mouse 58. The folder selected in S508 is set as the file storage destination. If no setting customization is performed, the default setting is followed.

  FIG. 16A is a flowchart showing the processing flow of the operation-linked file processing routine (this routine is repeatedly executed periodically). In S501, information on the data file selected and confirmed by the above-described processing is acquired. In step S502, the data file storage destination folder set in the HDD 44 of the PC 3 is searched to check whether there is a data file having a file name that overlaps with the selected and confirmed data file. If it does not exist, the process proceeds to S508, a communication event for reading the data file of the memory card using the OS file system is started, and the data file read from the multi-reader / writer 2 is received. In step S404, the received data file is written in the folder in the HDD 44 designated as the storage destination. When the move mode is selected, a communication event for deleting the data file that is the transmission source of the memory card is activated.

  On the other hand, if there is a data file having a file name that overlaps with the data file selected and confirmed in S503, the process proceeds to S504, and a communication event user for notifying this to the reader / writer 2 is activated. Also in this case, a new Inq (1) command (investigation request command) is issued, and information (character string data) for specifying a duplicate file name as additional information in the created CDB (1) data (investigation instruction data) may be used. However, it is preferable to simplify and specify with the order code on the file list) and transmit it to the reader / writer 2. The reader / writer 2 searches the file list already stored in the RAM 29 for a data file corresponding to the received duplicate file name specifying information, and as shown in FIG. 16B, the file name (ie, duplicate file name). Is displayed on the LCD 21 display section. Possible storage processing conditions in this case can also be displayed on the LCD 21 (in FIG. 16B, a plurality of corresponding processes can be sequentially displayed by scrolling). The character information indicating the type of the corresponding processing can be prepared in advance on the reader / writer 2 side such as the ROM 28 because the content is constant, and in this case, it is not necessary to receive character string data from the PC 3. .

  On the reader / writer 2 side, the storage processing conditions are scrolled on the LCD 21 using the keyboard 22 and selected / confirmed by double-clicking the confirmation button (the keyboard 22 is also used as a corresponding processing selection input unit). The types of save processing conditions that can be selected are file name change (1) of the copy destination (HDD 44), file name change (2) of the copy source (memory card (storage medium)), and copy cancellation (3). Then, which storage processing condition is selected is written in the VPD (investigation report data) and returned to the PC 3 side.

  The storage destination setting process (which is also a kind of storage process condition) performed on the PC 3 side can be executed on the peripheral device 2 side. In this case, the directory (folder) hierarchical structure information of the storage destination on the PC 3 side is acquired from the PC 3 side and displayed on the liquid crystal display unit 21 of the reader / writer 2, and the storage destination folder is similarly selected using the keyboard 22. The processing may be performed using Inq (1) / VPE additional communication.

  Referring back to FIG. 16B, the PC 3 side identifies the type of the corresponding process from 1 to 3 based on the information written in the received VPD, and performs the process (S506, S507). In other words, if it is 1, the file name of the copy destination (HDD 44) is rewritten (for example, a character string such as “copy” is added to the original file name). If it is 2, the copy source (memory card (memory The communication event for changing the file name of the medium)) is started. If the file name change is completed, the process proceeds to S508. Thereafter, the same processing is repeated until the processing for all data files for which selection has been confirmed (copying is regarded as processing completion) (S509 → S503).

  In addition, embodiment mentioned above is only an example of this invention, and can change suitably embodiment in the range which does not change the summary of this invention.

The perspective view which looked at an example of the multi reader / writer applied to the communication system of this invention from the front side. The perspective view similarly seen from the back side. FIG. 3 is a block diagram illustrating an example of an electrical configuration of a multi-reader / writer. Explanatory drawing of SCSI command / data / status transmission / reception unit of multi-reader / writer Explanation of control register Explanation of status register The block diagram which shows schematic structure of PC applied to the communication system of this invention. The conceptual diagram for demonstrating OS which operate | moves on PC, and the application which operate | moves on this OS. The flowchart showing the flow of the process which the SCSI command data data status transmission / reception part of a multi reader / writer performs. The flowchart showing the flow of the process of the data communication process performed in the communication system of this invention. 10 is a flowchart showing the flow of drive allocation processing in FIG. 9. 10 is a flowchart showing the flow of drive setting processing in FIG. 9. 10 is a flowchart showing the flow of the memory card attachment monitoring process of FIG. The flowchart which shows the detail of the character string data transmission process of FIG. The flowchart showing the flow of the file selection monitoring process of FIG. Explanatory drawing which shows the example of a file list display. The flowchart showing the flow of an operation interlocking file processing routine. Explanatory drawing which shows the example of a display at the time of a duplicate file detection. The flowchart showing the flow of a setting customization process.

Explanation of symbols

1 Communication system 2 Multi reader / writer (peripheral device)
3 PC (host device)
11 First memory card (storage medium)
12 Second memory card (storage medium)
13 Third memory card (storage medium)
14 Fourth memory card (storage medium)
21 Liquid crystal display (display unit)
22 Keyboard (manual operation unit, peripheral device side trigger generation means, manual operation unit, corresponding processing selection input unit)
27 CPU (trigger occurrence report information return means, investigation report data generation means, trigger occurrence report information writing means, investigation report data transmission means, exchange notification information holding means, exchange notification information holding control means, data file selection / save event execution means Means, file list display event execution means, data file selection event execution means, data file transmission event execution means, additional information extraction means)
34 Display control LSI (Display control means)
41 CPU (trigger report request command issuing means, report information receiving means, target communication event starting means, data file selecting / saving event executing means, data file saving control means, investigation instruction data creating means, investigation instruction data transmitting means, file List display event execution means, data file selection event execution means, data file transmission event execution means, corresponding processing execution means)
51-54 Input / output control unit (storage medium attachment detection means)

Claims (19)

A host device having a communication event activation decision right and a peripheral device to be communicated with the host device connected to the host device, and a command for instructing execution of the communication event from the host device While sequentially issuing to the peripheral device, the peripheral device that has received the issued command sequentially executes data processing corresponding to the command, and returns response information corresponding to the execution result to the host device side. In the communication system having a main communication protocol in which the command issuance direction is restricted in one direction from the host device side to the peripheral device side,
Peripheral device side trigger generation that is provided in the peripheral device and generates a peripheral device side trigger for prompting the host device to start a target communication event with predetermined contents based on a user operation on the peripheral device side Means,
In order to monitor the occurrence of the peripheral device side trigger in the peripheral device and request trigger occurrence report information reflecting the presence or absence of the peripheral device side trigger as the response information provided on the host device side Trigger report request command issuing means for issuing a trigger report request command to the peripheral device according to the main communication protocol;
Trigger generation report information return means provided on the peripheral device side, which returns the trigger generation report information as the response information to the host device according to the main communication protocol;
Report information receiving means provided on the host device side for receiving the trigger occurrence report information from the peripheral device;
Based on the contents of the trigger occurrence report information, the presence / absence of the peripheral device side trigger is determined, and when it is determined that the peripheral device side trigger is present, target communication event starting means for starting the target communication event is provided. And
The peripheral device is configured as a storage device that is detachably mounted with a storage medium capable of data access related to data reading, and configured to access the storage medium by the communication event, and A manual operation unit for performing a file selection operation for selecting a data file in the storage medium and a setting operation of a storage processing condition for the selected data file, and as the execution means for the target communication event, The manual operation is performed as the host device side grasps the generation of the confirmation operation trigger as the peripheral device side trigger for confirming the selection contents of the data file by the manual operation unit based on the trigger generation report information from the peripheral device. Transmission of the data file selection confirmation contents by the host device from the host device. A request is made to the device, and the first communication event for receiving the data file selection confirmation content as the response information from the peripheral device on the host device side and transmission of the setting content of the storage processing condition by the manual operation unit are transmitted. A request from the host device to the peripheral device, a second communication event for receiving on the host device side the set content of the storage processing condition as the response information from the peripheral device, and the selected data file A data file selection / save event execution means means including a third communication event read by the peripheral device and transmitted to the host device;
The host device is provided with data file storage control means for storing the received data file in a predetermined storage area of the storage device on the host device side under the storage processing condition. Communication system.   When a data file having a file name that overlaps with a data file to be stored in the storage medium exists in the storage area on the host device side, a storage processing condition for the data file having the duplicate file name is: The communication system according to claim 1, wherein the communication system can be set by selecting from a plurality of conditions according to the operation content by the manual operation unit.   The communication system according to claim 2, wherein a condition for changing a data file name on the host device side or the storage medium side is set as the storage processing condition. A display unit is provided in the peripheral device,
When a data file having a file name that overlaps with the data file to be stored in the storage medium exists in the storage area on the host device side, the data file name that is duplicated in the data file selection / storage event is A fourth communication event that is transmitted as character information from the host device side to the peripheral device is executed,
4. The communication system according to claim 3, wherein the peripheral device is provided with a duplicate data file name display means for displaying the duplicate data file name on the display unit.   5. The trigger report request command issuing means repeatedly issues the trigger report request command to the peripheral device at a predetermined time interval. 6. Communication system.   The peripheral device and the host device are connected via a serial communication mechanism in which the peripheral device can be polled from the host device side and the host device cannot be reversely polled from the peripheral device side. The information transfer between the host device and the peripheral device for executing the communication event is executed by serial communication in a format in which the host device polls the peripheral device. The communication system according to any one of claims 1 to 5.   The communication system according to claim 6, wherein the serial communication mechanism conforms to a USB protocol. Provided on the host device side, issues a survey request command for requesting the peripheral device itself to perform a survey report process on the peripheral device, and is accompanied by a predetermined search report instruction content accompanying the issuance of the survey request command. Survey instruction data creating means for creating survey instruction data having a frame format and additional information written in a predetermined field of the frame, and a survey instruction for transmitting the created survey instruction data to the peripheral device Data transmission means;
Survey report data generating means provided in the peripheral device, receiving the survey instruction data, and generating survey report data having a predetermined frame format;
Provided in the peripheral device, a survey report data transmitting means for transmitting the survey report data as response information to the host device;
Additional information extraction means provided on the peripheral device side, for extracting the additional information from the predetermined field of the received survey instruction data;
The communication system according to any one of claims 1 to 7, further comprising: The survey report data generation means writes corresponding additional information corresponding to additional information from the host device side in a predetermined frame of the survey report data,
9. The communication system according to claim 8, wherein the survey report data transmitting means transmits the survey report data in which the corresponding additional information is written as response information to the host device.   The investigation request command is used as the trigger report request command, the peripheral device side trigger generation report instruction information is written as the additional information in the investigation instruction data, and the corresponding additional information is included in the corresponding investigation report data. The communication system according to claim 9, wherein the trigger occurrence report information is written. The investigation request command is used to start a communication event for transmitting character information to be displayed on the display unit from the host device to the peripheral device, and specifies the character to be transmitted as the additional information in the investigation instruction data. Character code information is written as additional information,
The peripheral device side includes a display unit, display character data storage means for storing character data for display on the display section in association with the character code, and the additional information extracted by the additional information extraction means. The communication according to any one of claims 8 to 10, further comprising display control means for reading display character data corresponding to the character code information from the display character data storage means and displaying the read character data on the display unit. system. 3. If the data file having a file name that overlaps with the data file received from the peripheral device is present in the storage area, the peripheral device has the requirement according to claim 2 Is used to start a communication event to be notified, and duplicate file name specifying information is written as the additional information in the investigation instruction data,
The peripheral device is provided with a duplicate file name display means for displaying the duplicate file name on the display unit based on the received duplicate file name specifying information, and instructs the host device for the displayed duplicate file. The storage processing conditions can be selected and input from the manual operation unit,
In the survey report data, as the corresponding additional information, storage processing condition instruction information for instructing the storage processing condition based on input information from the manual operation unit is written,
12. The communication system according to claim 11, wherein the data file storage control means on the host device side executes the data file storage processing in accordance with the storage processing conditions received from the peripheral device.   The survey instruction data creating means stores the additional information in the main storage information in a field defined in the main communication protocol so that information other than the additional information is stored as main storage information to be stored in the survey instruction data. The communication system according to any one of claims 8 to 12, wherein the communication is written in a form commonly used by a computer.   In the survey instruction data, the allocation length information of the memory area on the storage medium allocated to the read process or the write process when executing a communication event related to reading or writing of data to the storage medium according to the main communication protocol Is stored as an allocation length setting field, and the additional information that is also used as the allocation length information is written in the allocation length setting field with the allocation length information as the main storage information. The communication system according to claim 13.   In the main communication protocol, the size of the allocation length setting field is determined to be a constant bit length, and the number of bits when the maximum value that can be set as the allocation length is expressed in bytes is expressed in the allocation length setting field. When the allocation length is set to less than the total number of bits and an allocation length exceeding the maximum value is described in the allocation length setting field, the maximum value is set to the actual setting value of the allocation length regardless of the described allocation length value. 15. The communication system according to claim 14, wherein different additional information contents are defined so as to be uniquely associated with redundant allocation length description values exceeding the maximum value. In the peripheral device, when the storage medium is exchanged, exchange notice information holding means for holding exchange notice information for notifying the host apparatus of the exchange of the storage medium, and predetermined from the host apparatus. When the first type command is received, the exchange notification information held in the exchange notification information holding unit is cleared after the command is executed, and the second type command other than the first type command is received. In this case, it has an exchange notification information holding control means for holding the exchange notification information holding state by the exchange notification information holding means even after execution of the command,
The communication system according to any one of claims 8 to 15, wherein the second type command is used as the investigation request command.   Configuration / attribute survey request that constitutes the second type command for the survey request command to instruct the peripheral device to report configuration / attribute identification information that is information identifying the configuration and attributes of the peripheral device itself. The communication system according to claim 16, wherein the communication system is a command.   The communication system according to claim 17, wherein the main communication protocol is a SCSI protocol, and an inquiry command is used as the investigation request command. The peripheral device constituting the communication system according to any one of claims 1 to 18, wherein at least a storage medium capable of data access relating to data reading is detachably mounted, and As a storage device that performs data access to the storage medium by a communication event,
A manual operation unit for performing a file selection operation for selecting a data file in the storage medium, and a setting operation for a storage processing condition of the selected data file;
The peripheral device side trigger generating means for generating a peripheral device side trigger for prompting the host device to start a target communication event having a predetermined content based on a user operation on the peripheral device side;
Trigger generation report information return means provided on the peripheral device side, which returns the trigger generation report information corresponding to the trigger report request command from the host device as the response information to the host device according to the main communication protocol;
A peripheral device comprising:

Images