(12) United States Patent
`Tasler
`
`I lllll llllllll Ill lllll lllll lllll lllll lllll 111111111111111111111111111111111
`US006470399Bl
`US 6,470,399 Bl
`Oct. 22, 2002
`
`(10) Patent No.:
`( 45) Date of Patent:
`
`(54) FLEXIBLE INTERFACE FOR
`COMMUNICATION BETWEEN A HOST AND
`AN ANALOG 1/0 DEVICE CONNECTED TO
`THE INTERFACE REGARDLESS THE TYPE
`OF THE 1/0 DEVICE
`
`(75)
`
`Inventor: Michael Tasler, Wiirzburg (DE)
`
`(73) Assignee: Labortechnik Tasler GmbH,
`Wuerzburg (DE)
`
`( *) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(21) Appl. No.:
`
`09/331,002
`
`(22) PCT Filed:
`
`Mar. 3, 1998
`
`(86) PCT No.:
`
`PCT/EP98/01187
`
`§ 371 (c)(l),
`(2), ( 4) Date:
`
`Jun.14, 1999
`
`(87) PCT Pub. No.: W098/39710
`
`PCT Pub. Date: Sep. 11, 1998
`
`(30)
`
`Foreign Application Priority Data
`
`Mar. 4, 1997
`
`(DE) ......................................... 197 08 755
`
`Int. Cl.7 ................................................ G06F 13/14
`(51)
`(52) U.S. Cl. .............................. 710/16; 710/62; 710/63
`(58) Field of Search ............................... 710/15, 16, 11,
`710/12, 62, 63, 64; 703/23, 24, 25
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`5,291,611 A
`5,297,124 A *
`5,430,855 A *
`5,444,644 A
`5,487,154 A
`5,499,378 A *
`5,506,692 A
`5,510,774 A
`5,548,783 A *
`6,012,113 A *
`
`3/1994 Davis et al.
`................ 703/25
`3/1994 Plotkin et al.
`7/1995 Walsh et al. .................. 703/23
`8/1995 Divjak
`1/1996 Gunji
`3/1996 McNeill et al. ............... 703/24
`4/1996 Murata
`4/1996 Loncle
`8/1996 Jones et al. ................... 710/15
`1/2000 Tuckner ...................... 710/64
`
`FOREIGN PATENT DOCUMENTS
`
`DE
`EP
`EP
`JP
`JP
`WO
`
`195 28 889 Al
`2/1997
`0 436 458 A2
`7/1991
`0 685 799 Al
`12/1995
`06301607 A
`10/1994
`08110883 A
`4/1996
`W094/19746
`9/1994
`OTHER PUBLICATIONS
`Steve Martin, "PC-based Data Acquisition in an Industrial
`Environment," pp. 1-3 (1990).
`Payne et al., "High Speed PC-based Data Acquisition Sys(cid:173)
`tems," IEEE, pp. 2140-2145 (1995).
`National Instruments Corporation, "Dynamic Signal Acqui(cid:173)
`sition and DSP Board for the PC AT," IEEE 488 and VXIbus
`Control, DataAcquuisition, and Analysis, pp. 3-118-3-123,
`(1994).
`IBM Corporation, "Communication Method between
`Devices through FDD Interface," IBM Technical Disclosure
`Bulletin, vol. 38 (No. 05), p. 245 (May, 1995).
`* cited by examiner
`Primary Examiner-Thomas Lee
`Assistant Examiner-Thuan Du
`(74) Attorney, Agent, or Firm-Patton Boggs LLP
`(57)
`ABSTRACT
`
`An interface device (10) provides fast data communication
`between a host device with input/output interfaces and a data
`transmit/receive device, wherein the interface device (10)
`comprises a processor means (13), a memory means (14), a
`first connecting device (12) for interfacing the host device
`with the interface device, and a second connecting device
`(15) for interfacing the interface device (10) with the data
`transmit/receive device. The interface device (10) is config(cid:173)
`ured by the processor means (13) and the memory means
`(14) in such a way that, when receiving an inquiry from the
`host device via the first connecting device (12) as to the type
`of a device attached to the host device, regardless of the type
`of the data transmit/receive device, the interface device
`sends a signal to the host device via the first connecting
`device (12) which signals to the host device that it is
`communicating with an input/output device.
`
`15 Claims, 2 Drawing Sheets
`
`16
`
`10
`
`1420
`
`1515
`
`1510
`
`1505
`
` 10/13/2016, EAST Version: 3.0.0.6
`
`

`
`d .
`\JJ. .
`~
`~ ......
`......
`
`~ =
`
`0 I")
`!""'"
`N
`~N
`N
`
`c c
`
`N
`
`~
`~
`
`....
`'"""' 0 .....,
`
`N
`
`e
`
`rJ'J.
`O'I
`1;.
`""-l
`Q
`~
`\0
`\0
`~
`lo-"
`
`TO DATA
`URANSMIT/
`.ECEIVE
`1EVICE
`
`I
`
`1s
`
`10
`
`I
`
`13
`l
`
`TO I
`
`HOST
`
`1 5 t CD
`
`11'
`
`I
`
`I
`
`L
`
`12
`
`DSP
`
`14
`
`-----.
`
`I
`
`.. , MEMORY
`\
`14
`
`1.
`
`I
`J
`
`~~nd CD
`
`)
`15
`
` 1
`
`0/13/2016, EAST Version: 3.0.0.6
`
`FIG.l
`
`~ . rF.J. =-
`
`

`
`d .
`\JJ. .
`~
`~ ......
`......
`
`~ =
`
`0 I")
`!""'"
`N
`~N
`
`N c s
`
`rF.J. =(cid:173)~
`~ ....
`
`N
`0 .....,
`N
`
`e
`
`rJ'l
`O'I
`1;.
`""-l
`Q
`~
`\0
`\0
`~
`lo-"
`
`>-3
`0
`0
`;J>
`t-3 >
`t-3
`:0
`;J> z
`(/)
`3:
`H
`t-3
`.......
`:0
`t<I
`0
`t<l
`H <
`
`t<l
`0
`
`l'l < H
`
`0
`t<l
`
`1800
`
`EXTERNAL AC/DC CONVERTER
`
`+ SV .DIGITAL POWER SUPPLY
`
`I
`
`~±5V,±.15V ANALOG POW!rn.SUPPLY
`
`DC/DC
`CONV]\:RTER
`
`1850 1810
`I I
`9-PIN
`p,a3o1 i iou#.>rJ'
`CONNECTOR
`
`AMPLIFIER
`
`I .I
`112-BIT. 0.6 MHz DAC
`1 1530
`11300)
`
`! r184~
`[
`f_
`
`PRECISION
`182fl VOLTAGE
`REFERENCE
`1525 " - - - - - i
`
`PROGRAMM-H 8-CHANNEL
`ABLE
`MULTI(cid:173)
`AMPLIFIER
`PLEXER
`
`8 DEVICE
`AMPLIFIER
`WITH
`t.75 v
`.OVER(cid:173)
`VOLTAGE
`PROTECTIOl
`
`8 BNC
`INPUTS
`WITH
`CALI(cid:173)
`BRATION
`RELAY
`
`16
`
`1284
`\
`
`TAL
`OUTPUT
`8 DIGI-
`TAL
`INPUT
`
`1 MB/s
`EPP
`
`1260
`
`11c
`
`1282
`
`~:..::::~--I
`
`/
`
`10
`
` 1
`
`0/13/2016, EAST Version: 3.0.0.6
`
`1535
`
`SAM(cid:173)
`PLING
`
`TIMER ---
`
`'
`512 KB (1024 KB
`15 ns RAM
`
`1420
`
`"\,.1320
`
`EPROM
`
`1400
`
`FIG.2
`
`1515
`
`1510
`
`1505
`
`

`
`US 6,470,399 Bl
`
`1
`FLEXIBLE INTERFACE FOR
`COMMUNICATION BETWEEN A HOST AND
`AN ANALOG I/0 DEVICE CONNECTED TO
`THE INTERFACE REGARDLESS THE TYPE
`OF THE I/0 DEVICE
`
`FIELD OF THE INVENTION
`
`The present invention relates to the transfer of data and in
`particular to interface devices for communication between a
`computer or host device and a data transmit/receive device
`from \Vhich data is to be acquired or \Vith \Vhich t\vo~v;ay
`communication is to take place.
`
`BACKGROUND OF THE INVENTION
`
`Existing data acquisition systems for computers are very
`limited in their areas of application. Generally such systems
`can be classified into two groups.
`In the first group host devices or computer systems are
`attached by means of an interface to a device whose data is
`to be acquired. The interfaces of this group are normally
`standard interfaces which, with specific driver software, can
`be used with a variety of host systems. An advantage of such
`interfaces is that they are largely independent of the host
`device. However, a disadvantage is that they generally
`require very sophisticated drivers which are prone to mal(cid:173)
`function and which limit data transfer rates between the
`device connected to the interface and the host device and
`vice versa. Further, it is often very difficult to implement
`such interfaces for portable systems and they offer few
`possibilities for adaptation with the result that such systems
`offer little flexibility.
`The devices from which data is to be acquired cover the
`entire electrical engineering spectrum. In a typical case, it is
`assumed that a customer who operates, for example, a
`diagnostic radiology system in a medical engineering envi(cid:173)
`ronment reports a fault. A field service technician of the
`system manufacturer visits the customer and reads system
`log files generated by the diagnostic radiology system by
`means a portable computer or laptop for example. If the fault
`cannot be localized or if the fault is intermittent, it will be
`necessary for the service technician to read not only an error
`log file but also data from current operation. It is apparent
`that in this case fast data transfer and rapid data analysis are
`necessary.
`Another case requiring the use of an interface could be,
`for example, when an electronic measuring device, e.g. a
`multimeter, is attached to a computer system to transfer the
`data measured by the multimeter to the computer. Particu(cid:173)
`larly when long-term measurements or large volumes of data
`are involved is it necessary for the interface to support a high
`data transfer rate.
`From these randomly chosen examples it can be seen that
`an interface may be put to totally different uses. It is
`therefore desirable that an interface be sufficiently flexible to
`permit attachment of very different electrical or electronic
`systems to a host device by means of the interface. To
`prevent operator error, it is also desirable that a service
`technician is not required to operate different interfaces in
`different ways for different applications but that, if possible,
`a universal method of operating the interface be provided for
`a large number of applications.
`To increase the data transfer rates across an interface, the
`route chosen in the second group of data acquisition systems
`for the interface devices was to specifically match the
`
`2
`interface very closely to individual host systems or computer
`systems. The advantage of this solution is that high data
`transfer rates are possible. However, a disadvantage is that
`the drivers for the interfaces of the second group are very
`closely matched to a single host system with the result that
`they generally cannot be used with other host systems or
`their use is very ineffective. Further, such types of interface
`have the disadvantage that they must be installed inside the
`computer casing to achieve maximum data transfer rates as
`10 they access the internal host bus system. They are therefore
`generally not suitable for portable host systems in the form
`of laptops whose minimum possible size leaves little internal
`space to plug in an interface card.
`
`15
`
`DESCRIPTION OF PRIOR ART
`
`40
`
`A solution to this problem is offered by the interface
`devices of IOtech (business address: 25971 Cannon Road,
`Cleveland, Ohio 44146, USA) which are suitable for laptops
`such as the WaveBook/512 (registered trademark). The
`20 interface devices are connected by means of a plug-in card,
`approximately the size of a credit card, to the PCMCIA
`interface which is now a standard feature in laptops. The
`plug-in card converts the PCM CIA interface into an inter(cid:173)
`face known in the art as IEEE 1284. The said plug-in card
`25 provides a special printer interface which is enhanced as
`regards the data transfer rate and delivers a data transfer rate
`of approximately 2 MBps as compared with a rate of approx.
`1 MBps for known printer interfaces. The known interface
`device generally consists of a driver component, a digital
`30 signal processor, a buffer and a hardware module which
`terminates in a connector to which the device whose data is
`to be acquired is attached. The driver component is attached
`directly to the enhanced printer interface thus permitting the
`known interface device to establish a connection between a
`35 computer and the device whose data is to be acquired.
`In order to work with the said interface, an interface-
`specific driver must be installed on the host device so that
`the host device can communicate with the digital signal
`processor of the interface card. As described above, the
`driver must be installed on the host device. If the driver is
`a driver developed specifically for the host device, a high
`data transfer rate is achieved but the driver cannot be easily
`installed on a different host system. However, if the driver is
`a general driver which is as flexible as possible and which
`can be used on many host devices, compromises must be
`accepted with regard to the data transfer rate.
`Particularly in an application for multi-tasking systems in
`which several different tasks such as data acquisition, data
`50 display and editing are to be performed quasi(cid:173)
`simultaneously, each task is normally assigned a certain
`priority by the host system. A driver supporting a special
`task requests the central processing system of the host
`device for processor resources in order to perform its task.
`55 Depending on the particular priority assignment method and
`on the driver implementation, a particular share of processor
`resources is assigned to a special task in particular time slots.
`Conflicts arise if one or more drivers are implemented in
`such a way that they have the highest priority by default, i.e.
`60 they are incompatible, as happens in practice in many
`applications. It may occur that both drivers are set to highest
`priority which, in the worst case, can result in a system
`crash.
`EP 0685799 Al discloses an interface by means of which
`65 several peripheral devices can be attached to a bus. An
`interface is connected between the bus of a host device and
`various peripheral devices. The interface comprises a finite
`
`45
`
` 10/13/2016, EAST Version: 3.0.0.6
`
`

`
`US 6,470,399 Bl
`
`3
`state machine and several branches each of which is
`assigned to a peripheral device. Each branch comprises a
`data manager, cycle control, user logic and a buffer. This
`known interface device provides optimal matching between
`a host device and a specific peripheral device.
`The specialist publication IBM Technical Disclosure
`Bulletin, Vol. 38, No. 05, page 245; "Communication
`Method between Devices through FDD Interface" discloses
`an interface which connects a host device to a peripheral
`device via a floppy disk drive interface. The interface
`consists in particular of an address generator, an MFM
`encoder/decoder, a serial/parallel adapter and a format signal
`generator. The interface makes it possible to attach not only
`a floppy disk drive but also a further peripheral device to the
`FDD host controller of a host device. The host device
`assumes that a floppy disk drive is always attached to its
`floppy disk drive controller and communication is initiated
`if the address is correct. However, this document contains no
`information as to how communication should be possible if
`the interface is connected to a multi-purpose interface
`instead of to a floppy disk drive controller.
`
`SUMMARY OF THE INVENTION
`It is an object of the present invention to provide an 25
`interface device for communication between a host device
`and a data transmit/receive device whose use is host device(cid:173)
`independent and which delivers a high data transfer rate.
`In accordance with a first aspect of the present invention,
`this object is met by an interface device for communication
`between a host device, which comprises drivers for input/
`output devices customary in a host device and a multi(cid:173)
`purpose interface, and a data transmit/receive device com(cid:173)
`prising: a processor; a memory; a first connecting device for
`interfacing the host device with the interface device via the 35
`multi-purpose interface of the host device; and a second
`connecting device for interfacing the interface device with
`the data transmit/receive device, wherein the interface
`device is configured by the processor and the memory in
`such a way that the interface device, when receiving an 40
`inquiry from the host device as to the type of a device
`attached to the multi-purpose interface of the host device,
`sends a signal, regardless of the type of the data transmit/
`receive device attached to the second connecting device of
`the interface device, to the host device which signals to the 45
`host device that it is an input/output device customary in a
`host device, whereupon the host device communicates with
`the interface device by means of the driver for the input/
`output device customary in a host device.
`In accordance with a second aspect of the present 50
`invention, this object is met by an interface device for
`communication between a host device, which comprises a
`multi-purpose interface and a specific driver for this
`interface, and a data transmit/receive device comprising: a
`processor; a memory; a first connecting device for interfac- 55
`ing the host device with the interface device via the multi(cid:173)
`purpose interface of the host device; and a second connect(cid:173)
`ing device for interfacing the interface device with the data
`transmit/receive device, wherein the interface device is
`configured using the processor and the memory in such a 60
`way that the interface device, when receiving an inquiry
`from the host device as to the type of a device attached at the
`multi-purpose interface of the host device, sends a signal,
`regardless of the type of the data transmit/receive device
`attached to the second connecting device of the interface 65
`device, to the host device which signals to the host device
`that it is an input/output device customary in a host device,
`
`4
`whereupon the host device communicates with the interface
`device by means of the specific driver for the multi-purpose
`interface.
`In accordance with a third aspect of the present invention,
`this object is met by a method of communication between a
`host device, which comprises drivers for input/output
`devices customary in a host device and a multi-purpose
`interface, and a data transmit/receive device via an interface
`device comprising the steps of interfacing of the host device
`10 with a first connecting device of the interface device via the
`multi-purpose interface of the host device; interfacing of the
`data transmit/receive device with a second connecting
`device of the interface device; inquiring by the host device
`at the interface device as to the type of device to which the
`15 multi-purpose interface of the host device is attached;
`regardless of the type of the data transmit/receive device
`attached to the second connecting device of the interface
`device, responding to the inquiry from the host device by the
`interface device in such a way that it is an input/output
`20 device customary in a host device, whereupon the host
`device communicates with the interface device by means of
`the usual driver for the input/output device.
`The present invention is based on the finding that both a
`high data transfer rate and host device-independent use can
`be achieved if a driver for an input/output device customary
`in a host device, normally present in most commercially
`available host devices, is utilized. Drivers for input/output
`devices customary in a host device which are found in
`practically all host devices are, for example, drivers for hard
`30 disks, for graphics devices or for printer devices. As how(cid:173)
`ever the hard disk interfaces in common host devices which
`can be, for example, IBM PCs, IBM-compatible PCs, Com(cid:173)
`modore PCs, Apple computers or even workstations, are the
`interfaces with the highest data transfer rate, the hard disk
`driver is utilized in the preferred embodiment of the inter(cid:173)
`face device of the present invention. Drivers for other
`storage devices such as floppy disk drives, CD-ROM drives
`or tape drives could also be utilized in order to implement
`the interface device according to the present invention.
`As described in the following, the interface device accord(cid:173)
`ing to the present invention is to be attached to a host device
`by means of a multi-purpose interface of the host device
`which can be implemented, for example, as an SCSI inter(cid:173)
`face or as an enhanced printer interface. Multi-purpose
`interfaces comprise both an interface card and specific driver
`software for the interface card. The driver software can be
`designed so that it can replace the BIOS driver routines.
`Communication between the host device and the devices
`attached to the multi-purpose interface then essentially takes
`place by means of the specific driver software for the
`multi-purpose interface and no longer primarily by means of
`BIOS routines of the host device. Recently however drivers
`for multi-purpose interfaces can also already be integrated in
`the BIOS system of the host device as, alongside classical
`input/output interfaces, multi-purpose interfaces are becom(cid:173)
`ing increasingly common in host devices. It is of course also
`possible to use BIOS routines in parallel with the specific
`driver software for the multi-purpose interface, if this is
`desired.
`The interface device according to the present invention
`comprises a processor means, a memory means, a first
`connecting device for interfacing the host device with the
`interface device, and a second connecting device for inter(cid:173)
`facing the interface device with the data transmit/receive
`device. The interface device is configured by the processor
`means and the memory means in such a way that the
`interface device, when receiving an inquiry from the host
`
` 10/13/2016, EAST Version: 3.0.0.6
`
`

`
`US 6,470,399 Bl
`
`5
`device via the first connecting device as to the type of a
`device attached to the host device, sends a signal, regardless
`of the type of the data transmit/receive device, to the host
`device via the first connecting device which signals to the
`host device that it is communicating with an input/output
`device. The interface device according to the present inven(cid:173)
`tion therefore simulates, both in terms of hardware and
`software, the way in which a conventional input/output
`device functions, preferably that of a hard disk drive. As
`support for hard disks is implemented as standard in all 10
`commercially available host systems, the simulation of a
`hard disk, for example, can provide host device-independent
`use. The interface device according to the present invention
`therefore no longer communicates with the host device or
`computer by means of a specially designed driver but by 15
`means of a program which is present in the BIOS system
`(Basic Input/Output System) and is normally precisely
`matched to the specific computer system on which it is
`installed, or by means of a specific program for the multi(cid:173)
`purpose interface. Consequently, the interface device 20
`according to the present invention combines the advantages
`of both groups. On the one hand, communication between
`the con1puter and the interface takes place by n1eans of a
`host device-specific BIOS program or by means of a driver
`program which is matched to the multi-purpose interface 25
`and which could be regarded as a "device-specific driver".
`On the other hand, the BIOS program or a corresponding
`multi-purpose interface program which operates one of the
`common input/output interfaces in host systems is therefore
`present in all host systems so that the interface device 30
`according to the present invention is host device(cid:173)
`independent.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`In the following, preferred embodiments of the present
`invention will be explained in more detail with reference to
`the drawings enclosed, in which:
`FIG. 1 shows a general block diagram of the interface
`device according to the present invention; and
`FIG. 2 shows detailed block diagram of an interface
`device according to a preferred embodiment of the present
`invention.
`
`6
`according to the present invention simulates a hard disk with
`a root directory whose entries are "virtual" files which can
`be created for the most varied functions. When the host
`device system with which the interface device according to
`the present invention is connected is booted and a data
`transmit/receive device is also attached to the interface
`device 10, usual BIOS routines or multi-purpose interface
`programs issue an instruction, known by those skilled in the
`art as the INQUIRY instruction, to the input/output inter-
`faces in the host device. The digital signal processor 13
`receives this inquiry instruction via the first connecting
`device and generates a signal which is sent to the host device
`(not shown) again via the first connecting device 12 and the
`host line 11. This signal indicates to the host device that, for
`example, a hard disk drive is attached at the interface to
`which the INQUIRY instruction was sent. Optionally, the
`host device can send an instruction, known by those skilled
`in the art as "Test Unit Ready", to the interface device to
`request more precise details regarding the queried device.
`Regardless of which data transmit/receive device at the
`output line 16 is attached to the second connecting device,
`the digital signal processor 13 informs the host device that
`it is communicating with a hard disk drive. If the host device
`receives the response that a drive is present, it then sends a
`request to the interface device 10 to read the boot sequence
`which, on actual hard disks, normally resides on the first
`sectors of the disk. The digital signal processor 13, whose
`operating system in stored in the memory means 14,
`responds to this instruction by sending to the host device a
`virtual boot sequence which, in the case of actual drives,
`includes the drive type, the starting position and the length
`of the file allocation table (FA1), the number of sectors, etc.,
`known to those skilled in the art. Once the host device has
`received this data, it assumes that the interface device 10
`according to a preferred embodiment of the present inven-
`35 tion is a hard disk drive. In reply to an instruction from the
`host device to display the directory of the "virtual" hard disk
`drive simulated by the interface device 10 with respect to the
`host device, the digital signal processor can respond to the
`host device in exactly the same way as a conventional hard
`40 disk would, namely by reading on request the file allocation
`table or FAT on a sector specified in the boot sequence,
`normally the first writable sector, and transferring it to the
`host device, and subsequently by transferring the directory
`structure of the virtual hard disk. Further, it is possible that
`45 the FAT is not read until immediately prior to reading or
`storing the data of the "virtual" hard disk and not already at
`initialization.
`In a preferred embodiment of the present invention, the
`digital signal processor 13, which need not necessarily be
`50 implemented as a digital signal processor but may be any
`other kind of microprocessor, comprises a first and a second
`command interpreter. The first command interpreter carries
`out the steps described above whilst the second command
`interpreter carries out the read/write assignment to specific
`55 functions. If the user now wishes to read data from the data
`transmit/receive device via the line 16, the host device sends
`a command, for example "read file xy", to the interface
`device. As described above, the interface device appears to
`the host device as a hard disk. The second command
`interpreter of the digital signal processor now interprets the
`read command of the host processor as a data transfer
`command, by decoding whether "xy" denotes, for example,
`a "real-time input" file, a "configuration" file or an execut(cid:173)
`able file, whereby the same begins to transfer data from the
`65 data transmit/receive device via the second connecting
`device to the first connecting device and via the line 11 to the
`host device.
`
`DETAILED DESCRIPTION OF PREFERRED
`EMBODIMENTS
`FIG. 1 shows a general block diagram of an interface
`device 10 according to the present invention. A first con(cid:173)
`necting device 12 of the interface device 10 can be attached
`to a host device (not shown) via a host line 11. The first
`connecting device is attached both to a digital signal pro(cid:173)
`cessor 13 and to a memory means 14. The digital signal
`processor 13 and the memory means 14 are also attached to
`a second connecting device 15 by means of bidirectional
`communication lines (shown for all lines by means of two
`directional arrows). The second connecting device can be
`attached by means of an output line 16 to a data transmit/
`receive device which is to receive data from the host device
`or from which data is to be read, i.e. acquired, and trans(cid:173)
`ferred to the host device. The data transmit/receive device 60
`itself can also communicate actively with the host device via
`the first and second connecting device, as described in more
`detail in the following.
`Communication between the host system or host device
`and the interface device is based on known standard access
`commands as supported by all known operating systems
`(e.g. DOS, Windows, Unix). Preferably, the interface device
`
` 10/13/2016, EAST Version: 3.0.0.6
`
`

`
`US 6,470,399 Bl
`
`20
`
`7
`Preferably, the volume of data to be acquired by a data
`transmit/receive device is specified in a configuration file
`described in the following by the user specifying in the said
`configuration file that a measurement is to last, for example,
`five minutes. To the host device the "real-time input" file
`then appears as a file whose length corresponds to the
`anticipated volume of data in those five minutes. Those
`skilled in the art know that communication between a
`processor and a hard disk consists of the processor trans(cid:173)
`ferring to the hard disk the numbers of the blocks or clusters
`or sectors whose contents it wishes to read. By reference to
`the FAT the processor knows which information is contained
`in \Vhich block. In this case, communication betv;een the
`host device and the interface device according to the present
`invention therefore consists of the very fast transfer of block
`numbers and preferably of block number ranges because a
`virtual "real-time input" file will not be fragmented. If the
`host device now wants to read the "real-time input" file, it
`transfers a range of block numbers to the interface device,
`whereupon data commences to be received via the second
`connecting device and data commences to be sent to the host
`device via the first connecting device.
`In addition to the digital signal processor instruction
`memory, which comprises the operating system of the digital
`signal processor and can be implemented as an EPROM or 25
`EEPROM, the memory means 14 can have an additional
`buffer for purposes of synchronizing data transfer from the
`data transmit/receive device to the interface device 10 and
`data transfer from the interface device 10 to the host device.
`Preferably, the buffer is implemented as a fast random
`access memory or RAM buffer.
`Further, from the host device the user can also create a
`configuration file, whose entries automatically set and con(cid:173)
`trol various functions of the interface device 10, on the
`interface device 10 which appears to the host device as a 35
`hard disk. These settings can be, for example, gain, multi(cid:173)
`plex or sampling rate settings. By creating and editing a
`configuration file, normally a text file which is simple to
`understand with little prior knowledge, users of the interface
`device 10 are able to perform essentially identical operator 40
`actions for almost any data transmit/receive devices which
`can be attached to the second connecting device via the line
`16, thus eliminating a source of error arising from users
`having to know many different command codes for different
`applications. In the case of the interface device 10 according 45
`to the present invention it is necessary for users to note the
`conventions of the configuration file once only in order to be
`able to use the interface device 10 as an interface between
`a host device and almost any data transmit/receive device.
`As a result of the option of storing any files in agreed
`formats in the memory means 14 of the interface device 10,
`taking into account the maximum capacity of the memory
`means, any enhancements or even completely new functions
`of the interface device 10 can be quickly implemented. Even
`files executable by the host device, such as batch files or
`executable files (BAT or EXE files), and also help files can
`be implemented in the interface device, thus achieving
`independence of the interface device 10 from any additional
`software (with the exception of the BIOS routines) of the
`host device. On the one hand, this avoids licensing and/or
`registration problems and, on the other hand, installation of
`certain routines which can be frequently used, for example
`an FFT routine to examine acquired time-domain data in the
`frequency domain, is rendered unnecessary as the EXE files
`are already installed on the interface device 10 and appear in
`the virtual root directory, by means of which the host device
`can access all programs stored on the interface device 10.
`
`8
`In a preferred embodiment of the present invention in
`which the interface device 10 simulates a hard disk to the
`host device, the interface device is automatically detected
`and readied for operation when the host system is powered
`up or booted. This corresponds to the plug-and-play standard
`which is currently finding increasingly widespread use. The
`user is no longer responsible for installing the interface
`device 10 on the host device by means of specific drivers
`which must also be loaded; instead the interface device 10
`10 is automatically readied for operation when the host system
`is booted.
`For persons skilled in the art it is however obvious that the
`interface device 10 is nol necessarily signed on when lhe
`computer system is powered up but that a special BIO