JPH1083315A - Decentralized test unit, diagnostic network system, and diagnosing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the costs for monitoring, maintenance, and inspection by providing a diagnostic unit which discriminates the operation state of one abnormal device that needs to be inspected and repaired among devices. SOLUTION: The sample capability of system data is given by a decentralized unit(DTU) 12 arranged at a predetermined test position in a blood vessel imaging system. For example, the DTU 12 is arranged in a component such as the dosemeter, console cabinet, and high-voltage transformer 34 of the blood vessel imaging system. Different DTUs are arranged at test positions of those components and monitor specific parameters of their relative components. Then the DTUs 12 function as 'sensors' of a diagnostic network system 10 in this case to gather and send out data to a system monitor box 16.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001] One microfish consisting of 28 frames is attached as Appendix A to the specification of the present application.

[0002]

BACKGROUND OF THE INVENTION The present invention relates to a modality having a number of different modular devices connected to one another and having a particular function (e.g., a vascular X-ray imaging system, MR).
Monitoring (maintenance (inspection)) and diagnosis (test, inspection, management) methods including monitoring, maintenance (inspection), and repair of target systems such as I (magnetic resonance imaging) systems, X-ray CT scanners, nuclear medicine diagnostic devices, biomagnetic field measurement devices, etc. About.

[0003]

2. Description of the Related Art Conventionally, various types of medical modalities have been proposed as examples of such a modular system. For example, in the case of a blood vessel X-ray imaging system as a medical modality, a patient table,
An operator console, a control panel, and a high-voltage transformer are provided as module devices, and these module devices are electrically connected. This makes it possible to perform vascular imaging of a patient as a whole.

[0004]

The cost of servicing each component of these modalities is expensive. With a modular design, the system can be built to meet individual customer requirements. On the other hand, repair and maintenance become complicated. That is, the repairs and maintenance must be performed in accordance with the individual modules, so that the entire cost required for the repairs and maintenance increases.

[0005] To perform repairs and maintenance, the field service engineer must have on-site technical manuals and repair procedures to check for any problems that may arise at any time. However, again, one problem arises because of the modular nature of the system. A blood vessel X-ray imaging system is typical. Since a variety of modules are used in this system, technical manuals and procedure manuals for each of the modules become on hand of a field service engineer. This was a considerable amount of paperwork, very inconvenient and not very mobile.

[0006] When diagnosing a system trouble (problem) of a modality, a problem solving method based on the result of the diagnosis may be appropriate, but may be deviated, and the problem solving always involves trial and error. In. In other words, it often took a lot of time and effort to arrive at an appropriate problem solution. For example, in order to diagnose a trouble, a field service engineer needs to execute a procedure for solving a problem or frequently execute such a procedure by referring to a technical manual. In many cases, even if the first processing procedure is executed, the trouble is not solved. In that case, it is necessary to execute an additional processing procedure.
This is extremely time consuming and has diagnostic costs.
Further, as a result of executing the processing procedure, it may be necessary to replace parts. In some cases, the system still does not work as expected when the part is replaced.

In some cases, it is necessary to execute a processing procedure for solving two or more times to determine the cause of the trouble. Once the cause of the trouble has been determined, more procedures need to be performed to determine how to repair or replace such a malfunctioning component. Even if an experienced field service engineer can more easily identify a problem and know the steps to solve it, even an experienced field service engineer can identify the cause. The more you misdiagnosed,
Moreover, there are some problems that do not occur clearly.

Another cost-increasing factor is the effort to ensure optimum performance after maintenance and inspection. This optimal performance is often owned empirically by the user. That is, each physician who uses the images generated by the system has unique performance parameters, which are the optimal parameters for each physician. It is important, therefore, that the state of optimal performance can be easily reproduced after diagnosis (testing, inspection, management) and that the system be returned to a setting that can exhibit the performance characteristics preferred by individual users. In the past, it took a lot of time and effort to reproduce this optimum performance.

Conventionally, monitoring the state of the system performance of a modality requires a lot of trouble because it is modularized. In particular, in the case of a blood vessel imaging system, the trouble is often complicated. This is because a large number of system components are typically located in different rooms and may be powered by separate power sources. In general, problems of electrical safety, grounding and distance arise.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned various problems related to conventional monitoring, maintenance, and inspection in a modular system, and has as its main object to significantly reduce the cost of such monitoring, maintenance, and inspection. Can provide a reliable solution when a problem occurs,
It is to provide a diagnostic system and a diagnostic method for a modular system.

Another object of the present invention is to contribute to the reduction of diagnostic costs by reducing the on-hand, convenient, and mobility of field service engineers who maintain and inspect the modular system. Is what you do.

Still another object of the present invention is to eliminate or reduce trial and error factors in diagnosing a trouble (problem) in a modular system, efficiently present a problem solution, and reduce the cost of diagnosis. They try to contribute.

Yet another object of the present invention is to enable even an experienced field service engineer to present an accurate solution to a modular system trouble that occurs in a difficult manner. It is to be.

Yet another object of the present invention is to allow a modularized system to be easily returned to its previous optimal performance state after maintenance, inspection or troubleshooting, thereby also reducing the total time for maintenance and the like. And to reduce labor.

Still another object of the present invention is to easily and surely monitor the performance state of a modular system online and improve the reliability of system management.

[0016]

SUMMARY OF THE INVENTION A diagnostic network system according to the present invention is a system for communicating with a plurality of devices, and the system communicates with each one of the plurality of devices individually. Distributed Test Units (DTUs) that perform the communication, a master DTU, a network for transmitting information between the master DTU and the plurality of DTUs, and a plurality of DTUs through the master DTU
And a system monitor unit that communicates with the system. The system monitor unit includes a control unit for collecting information from a plurality of DTUs, a database storing information edited from information collected from the plurality of DTUs,
And a diagnostic unit that analyzes the collected information and identifies an operating state of one or more of the devices that require service.

For example, if the system having a plurality of devices is a blood vessel imaging system, using a network having a DTU connected to selected devices (dosimeters, control consoles, etc.) of the blood vessel imaging system, The DTU collects the data and transfers the data to the system monitor. A field service engineer connects a field service notebook (laptop computer) to the system monitor to access data collected by the DTU. Using this gathered data, an accurate measure of system performance can be created that can be easily monitored and played back, providing optimal performance levels based on preset criteria. With the storage capacity of the system monitor's electronic database, field service engineers are provided with support systems and reference materials, including component lists, manuals, and current software releases, which allows for the rapid and , Less troublesome, more accurate repair is possible.

The present invention further provides an automated system that reduces the likelihood of errors that occur during manual data transfer and that requires hard copy support and field service engineers to be brought to the site. The amount of technical data that has to be reduced can be reduced, and the required analysis of the performance data can be performed with high accuracy by the system monitor, thus reducing human error in diagnosis and repair.

Such a diagnostic network system increases the efficiency of troubleshooting and repairs, leading to shorter downtime, thereby reducing costs and improving customer satisfaction. The test network system also allows non-invasive testing of the system under test (eg, a vascular imaging system) so that data can be collected from a predetermined test location, for example, while the system under test is in use. This allows the field service engineer to proactively detect and correct system performance degradation before, for example, the vascular imaging system goes down.

An off-site Technical Assistance Center (TAC) can be used to remotely contact the system monitor, access the DTU network to check system operation status, and provide information stored in the system monitor. Can be updated.

According to the present invention, the evaluation time can be reduced by automation. The diagnostic system of the present invention employs an expert system, which has software processed by a system monitor processor, which analyzes data collected and stored from the DTU. Expert systems can more quickly refer to similar past problem situations and recall solutions. This expert system can therefore give the field service engineer an indication of how and how to solve on such a system. The expert system also proactively directs the field service engineer to an alternative correct solution, if an incorrect procedure is performed. This reduces the time-consuming guesswork and trial and error associated with normal repair processes and allows for faster repair or adjustment of the vascular imaging system.

Other features and advantages of the present invention will become apparent in the following description of the embodiments of the present invention.

[0023]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The diagnostic network system 10 of the present invention has three main components as shown in FIGS. 1) A hardware network of distributed test units (DUTs) 12, which are pre-defined on various modules that make up a vascular system 14 (see FIG. 2). Test position (test p
oints), components that can be attached to
2) a system monitor box 16 for receiving and handling data from the DTU 12, and 3) a field service notebook 18 (conventional laptop computer), which functions as an interface to the field service engineer's system monitor box 16. And a component that allows a user to access the diagnostic network system of the present invention. A Technical Assistance Center (TAC), shown conceptually in FIG. 3, also forms another component of the present invention.

System Architecture One preferred embodiment of the diagnostic network system 10 of the present invention, as shown in FIGS.
This is the simplest configuration in which are connected in series. With this configuration, operation data is continuously collected at the designated test position of each device (module device) of the blood vessel imaging system 14 and the information is sent back to the system monitor box 16. As shown in FIG.
The vascular imaging system 14 used for radiography includes a high voltage transformer 78, a patient couch 17, a C-arm 15, a control panel 32, and a console 30.
It consists of a collection of module devices. This DTU
The network 13 and the system monitor box 16 are located on-site, and are connected to the module device of the blood vessel imaging system 14. DTU12
Are connected to each other by a fiber optic network 24. According to a preferred embodiment, the fiber optic network 24 comprises "Toshiba America Electronic
TOTX173 available from "Components Co., Ltd."
/ TORX173 and TOCP172 fiber optic cables are used. The maximum length of the fiber optic network 24 between each DTU 12 is 10 meters. Field Service Notebook 18 is a field service notebook.
Brought to the site by a service engineer,
It is connected to the system monitor 16 using the Ethernet connector 20. The field service notebook 18 has a graphical user interface (GU).
I) 22 is provided so that the field service engineer can communicate directly with the DTU network 13.

As shown conceptually in FIG. 3, TAC 19 provides additional technical support, functional statistics, expert knowledge, and external data via modem link 26 or other suitable data lines. Obtained offsite. This off-site support is provided to the on-site field service engineer, which helps the diagnostic network system of the present invention to function effectively.

As can be seen in FIGS. 1 and 2, the ability to sample system data is provided by a DTU 12 located at a predetermined test location of the vascular imaging system. For example, the DTU 12 is a blood vessel imaging system 1
4, dosimeters 28, console 30, control cabinet 32, and high voltage transformer 34. Each of these component test locations is provided with a different DTU, which is provided to monitor certain parameters of its associated component. For example, dosimeter 28 is dosimeter DTU3
X-ray dose information is collected. The DTU network 13 is connected to a master DTU 34, which is connected to the system monitor 16 by a multi-pin cable 36, such as a conventional 25-pin cable.

A plurality of DTUs 12 are connected in series, forming a closed loop with a loop beginning and ending at master DTU 34. A star-shaped connection as shown in FIG. 4 may be made, which overcomes some of the drawbacks envisioned for series connection.

In the case of the hardware configuration shown in FIG.
The TU 34 has a parallel port 40A through which the master DTU 34 communicates with the system monitor box 16A.
To the LPT port 40. This LPT port 4
At 0, 4 bits are used for data input and the remaining 4 bits are used for output data. The master DTU 34 has an optical receiver / transmitter 54 (see FIG. 6) to enable communication with the optical fiber network 24. The master DTU 34 receives a digital signal from the system monitor box 16 and converts it into an optical signal for the DTU network 13. The master DTU 34 has individual D
When receiving the data returned from the TU 12, the signal is converted from the optical signal form to the digital signal form, and the signal is passed to the system monitor box 16 for analysis.

During operation of the master DTU 34, the master DTU 34 sends data to the first DTU 12 in a closed loop, and the first DTU 12 retransmits the data to the second DTU 12, which in turn transmits the data. The last DTU 12 sends such data back to the master DTU 34 to complete the loop. In the case of the serial network of the DTU 12, the cost advantage is the best since only one optical fiber network 24 is required to connect the entire DTU 12 to form a loop.

[0030] Disadvantages of this serial connection method include:
a) If one DTU is powered down, the entire network loop will be inoperable; and, b) optical pulses may be distorted during transmission, which may degrade the performance of high speed optical communications. That is, it becomes the low-speed mode. These disadvantages can be explained using a combination of star-loop type network configurations as shown in FIG.

FIG. 4 shows an example of the star loop type network. In the present embodiment, four or more optical input / output channels are used so that all the DTUs 12 essential for the diagnostic network system can be accessed by individual links of the optical fiber cable network 24. Second, the DTU 12 can also be connected in a loop. The main DTU 12 can be accessed directly,
Even if one DTU 12 fails, the situation that the entire network becomes inoperable is prevented. One disadvantage of the star configuration is that additional optical cables are required for separate connections. However, each loop can have a dedicated master DTU circuit assigned to that loop, and the master DTU circuit can be similar to the master DTU 34 described in connection with the closed loop embodiment of FIG. Alternatively, it is also possible to adopt a multiplex arrangement in which the master DTU circuit set is shared by several loops.

Distributed Test Unit The DTU 12 will now be described in more detail with reference to FIGS. The DTU 12 is a portable data acquisition unit that is configured to be connectable to a predetermined test location on a component (modular device) of the vascular imaging system 14 and that the normal operation of the imaging system or the imaging system is used. Such a connection is possible without affecting the image quality produced. The DTU 12 has the function of the “sensory organ” of the diagnostic network system of the present invention, collects data and sends it to the system monitor box 16.

As shown in FIG. 5, three basic modules are provided in the shape of a shoulder wheel to form one DTU. 1) Microprocessor module (MM)
46, 2) power module 48 (PM), and 3) sample control module (SCM) 5
0. These modules are preferably connected by a stackable multi-pin connector 52 as shown in FIG. The DTU 12 is provided with the appropriate SCM module 50
Can be selected and stacked with the microprocessor module 46 and power module 48 to suit a particular test location. Microprocessor module 46 and power module 48 are preferably unchanged for each DTU 12. DT
The U12 is equipped with an LED 104 (shown in FIG. 1), which provides status information and indicates whether the DTU 12 is operating after startup.

The microprocessor module 46 includes:
Toshiba 68HC11A capable of turning off battery power
O microprocessor 44 with memory and connectivity optical input / output capabilities within the network. DT
U12 has analog or digital inputs and outputs for connection, at least one pair of which is optical to one component of the vascular imaging system, for example a dosimeter.

Each of the test locations where the DTUs 12 of the vascular imaging system are located serve various functions. Therefore, various types of SMCs 50 are used. However, the power module 48 and the microprocessor module
The module 46 is common to each DTU 12. All D
Although TUs 12 are generally similar, input conditions and operating levels (voltages and values) may vary.

The predetermined test location for mounting the DTU 12 is the location that is considered most important for obtaining the highest possible image quality. Each DTU 12 performs several functions. This function includes 1) an optical fiber network 24
Waiting while monitoring commands from the system monitor 16 viewed through the system, 2) monitoring input to a predetermined test location, and / or 3) changing the test location to maintain a predetermined value. It is. For example, DTU1
2 can operate as a positive feedback control system,
In that system, the output is fed back as an input until it reaches a certain value. Thus, for example, if the user wishes to increase the radiation of the dosimeter 28 to a certain value, the dosimeter DTU 38 will incrementally increase the radiation until the specified output value is reached.

The microprocessor module 46 is integrated into the power module 48 and the test location specific SCM 50. Via the multi-pin connector 52,
Signals necessary for controlling the SMC 50 are provided from the microprocessor 44. The preferred architecture of the microprocessor module 46 shown in FIG. 6 includes an optical receiver and transmitter 54, a Toshiba model 68HC11.
Microprocessor 44, such as A1 or equivalent, EPROM 58, RAM 2000 memory 56A
Bank, RAM 6000 bank of memory 56, R
Bank of AM 8000 memory 56C and field programmable gate array (FPGA) 64
Is included. Microprocessor 44 transmits information via a data / address bus connected to multi-pin connector 52. FIG. 9 shows an example of signal assignment of the multi-pin connector to each of all the DTUs 12.

The optical receiver and transmitter 54 converts the optical pulses received from the fiber optic network 24 into electrical signals, which are recognized by the communication port of the microprocessor 44. As shown in FIG. 6, the microprocessor 44 operating in the extended multiplex mode includes an external R
Access the AM 56A, 56B, 56C and EPROM 58, and I / O. FIG. 10 shows a typical example of the memory map of the microprocessor.

Each DTU 12 transmits and receives data using two 68HC11A0s connected in series in the microprocessor 44, and has a serial communication interface (SCI or RS232) 60 and a serial peripheral interface (SP).
I) 62 is as shown in FIG. Using the crossbar switch 64, as dictated by the format of the information that is switched between the system monitor and the test position,
The optical and electrical links are placed in the test position, ie, R
Connect to S232 60 port or SPI 62 port. The crossbar switch 64A is connected to the F as shown in FIG.
Implemented as part of PGA. Code / decode logic 65 converts signals in MOSI / SCK format to Rx / Tx format and vice versa.

Instead of having all traffic on the network go through the microprocessor 44, the SP
I62 receives the information from the optical receiver and retransmits the signal to optical transmitter 54. The retransmitted signal is re-modulated to compensate for optical pulse width distortion. (See PAL retransmission switch 53.) Thus, many DTUs 12 can be connected in series without accumulating pulse width distortion.

In the case of a general DTU 12, eight analog signals (0 to 2.5 V range) can be sampled. The microprocessor 44 has an A / D converter 66 therein. Analog data sent from the test position passes through the multi-pin connector 52,
A microprocessor 44 is reached which is directly coupled to the connector. The analog data is then sent to the A / D converter 6
6 to be converted into a digital format in the microprocessor 44. The SCM 50 uses an external data / address bus together with chip select logic, and can interface with another DTU from its DTU 12 (address range 0800-OFFF, FIG. 7). The first four (A ₀ − + 5
_V, A 1 - BATT. _1, A 2 - BATT. 2,
A ₃ - the input channels + 12V) is used to monitor the power module 48 (see FIG. 5). Monitor the + 5V supply voltage on the first channel. Second
And monitor the two batteries utilized in DTU 12 on the third channel. The fourth channel monitors the voltage of the internal DC / DC converter. The last four analog channels can be used to sample data from any one of the test locations.

Each DTU 12 has a battery 68 and a 24 VDC input 7 to hold the necessary data for up to one hour.
It is desirable to have a proprietary power module 48 with 0 (FIG. 5). This battery has an internal DC / DC
Charged from converter 72. During "power on" of a DTU 12, the 24V power applied to input 70 can be generated from one of an external power supply or a DC power line inside the vascular imaging system. D
The C / DC converter 72 converts the input voltage of 24 V to a maximum current of 5
It is converted to a 12 mA output voltage of 00 mA. If the machine cannot access the 24V power supply, the output will be 24V
An external wall plug transformer that is DC is used. The converter has a 500V 3000V input / output isolation rating. FIG. 7 shows an example of a system diagram of the power module 48 (common to each DTU).

The power module 48 is connected to a DC / DC converter 72 through a relay switch 74. When high noise immunity is required, the power module 48 is physically separated from the DC / DC converter 72 and X
Power can be supplied from the internal battery 68 for a short period of time required for data collection during the line exposure.

Each of the DTUs 12 has the special properties of the DTU 12 from the SCM 50 it has. The system diagram of the SCM 50 is shown in FIG.
Common to the ADTU 76, master DTU, dosimeter DTU 38, and PMT DTU 80.

As shown in the examples of FIGS. 12 and 13, since an appropriate SCM 50 is selected, a general DTU1 is used.
2 or dosimeter DTU 38 or console DTU, depending on where it is located in vascular imaging system 14.
It can function as another specific DTU type, such as 88. (See FIG. 2.) From dosimeter 28,
Data from the test location is received by the DTU 12 via the test location connector 51 on the SCM 50. Switch 200 is controlled by commands on lines B4 and B5 to switch between a reference voltage and a test position signal. Divider 59 provides the full scale and graduated level of the signal from switch 200 to instrumentation amplifier 202.

Instrumentation amplifier 202 then connects to lines AIN6 and AIN7 leading to multi-pin connector 52.
Drive. To this end, data is sent to the microprocessor module 46 through pins AIN6 and AIN7 of the multi-pin connector 52. SCM50
RS232 to communicate with the monitor or field service engineer's laptop computer
The connector 55 is provided. MAX232 RS232
A chip 57 is provided and this is the data signal RS
From 232 format (and to this format)
Convert to ± 5V format used by SCM50. DT used in the diagnostic network system of the present invention
The types of U12 and their respective SCMs 50 are exemplified below.

KV , mA DTU The kV, mA DTU 76 SCM 50 is a TER located on the HV generator tank 78 (high voltage transformer).
MINAL-A PWB or FEEDBACK P
Can be connected to WB. (See FIG. 2.) k
The V, mA DTU 76 measures the voltage and / or current at test location 51. The SCM 50 functions as an interface between the test position and the DTU 12. A set of operational amplifiers converts the mA signal to a voltage level proportional to this current level. With the same circuit, + kV /-
The kV signal is identified and becomes an absolute kV signal. This mA
The amplifier needs to operate within the signal range of 4 to 1500 mA (indirect imaging / imaging mode). Thus, a programmed amplification is provided via the programmable register divider 59 of FIG. 8 to accommodate the various ranges.

Photomultiplier tube DTU Photomultiplier tube (PMT)
Is measured. Simple O
If a P-amplifier circuit is used, the PMT voltage is converted to a microprocessor module 46 (similar to kV, mA SCM).
Can be converted to the level to be measured.

Dosimeter DTU Dosimeter DTU 38 (shown in FIG. 12) is typically connected to dosimeter 28 and measures radiation incident on the imaging tube. The dosimeter DTU 38 controls the 35050A or equivalent dosimeter 28 using the RS232 link, sets the appropriate range and mode, requests data, and sends the data to the system monitor box 16 through the fiber optic network 24. Transmit. The SCM 50 (shown in FIG. 8) for this dosimeter DTU 38 is "Kei
It is designed for a "thley" type dosimeter, but can be modified to use a different type of dosimeter. This SC
A device similar to the MAXIM MAX 232 is used for the M50.
The 0-5V RS232 level from 4 is converted to the 9V level required by dosimeter 28. The dosimeter 28 is powered only by the internal battery and cannot be turned on remotely. The operator says "POWER O
It must be activated by pressing the "N / OFF" button. However, the dosimeter turns itself off after a user-selected 1 to 255 minute "unattended operation" period.

Technique Selector / Console DTU This technique selector (TS / console) DTU
Reference numeral 88 (shown in FIG. 2) is connected to the operator console 30 and queries the operator's console 33 to determine whether this technique selector has been selected by the operator. In addition, the DTU monitors and reports on all actions taken by the user. For example, the DTU monitors and records the selection of techniques such as kV, mA settings, focus selection, X-ray tube selection, and the like. The state or technique of kV, mA can be selected and confirmed remotely from the TS DTU 88 without operator intervention, and many procedures can be fully automated. As described later, the calibration state of the blood vessel imaging system 14 can be confirmed by comparing the measured value of the DTU 12 with the set value of the operator console 30.

The TS / console DTU 88 also drives the automatic test function of the operator console 30. Therefore, the blood vessel imaging system of the present invention uses the measurement values of the test position reported by each DTU 12 and converts these measurement values into the technique selector DTU8.
8 can be compared with the set values recorded in the operator console 30 to ensure accuracy.

Master DTU This master DTU 34 is the first and last DTU in the loop as shown in FIG. Master DTU34
Are adapted to perform protocol storage and data buffering functions between the system monitor 16 and the fiber optic network 24. Master DTU34 S
FIG. 8 schematically shows the CM 50. The SCM outputs necessary signals and outputs the master D through the parallel port 40A.
The TU 34 is linked to the LPT port 40 of the system monitor box 16. This communication includes "Standard
A "Lap-LINK" or "Interlink" protocol is used. SCM 50 between master DTUs 34
The buffer 20 for digital signals is provided between the multi-pin connector 52 and the LPT port 40 of the system monitor 16.
4 are used.

Using eight data lines and one strobe line, the input signal is set to L in the system monitor box.
Parallel port 40A from PT40 to master DTU34
Sent to "SELECT", "PAPER EN
D, “ACKNOWLEDGE”, “BUSY”, and “ERROR”
6 is used as an output signal from the master DTU 34. The master DTU 34 collects 4-bit (+1 strobe) nibbles using a protocol similar to RS232, and packs the nibbles into blocks that can be accepted by the network protocol. As a result, communication between the system monitor 16 and the optical fiber network 24 can be simplified using the standard LPT port 40.

The blood vessel imaging system of the present invention can be configured without the master DTU 34. In this case, the master DTU 34 is connected to the system monitor box 1
6 and a circuit in a system monitor box adapted to perform high-speed optical communication between the DTU network 13.

System Monitor Box This system monitor box 16 (FIGS. 1, 2 and 14)
) Through the master DTU 34, all other DTs
It controls the U12, inquires the DTUs 12 about information, and processes the data returned by the DTUs. System monitor box 16
Can individually communicate with any of the DTUs 12. When the system monitor box 16 sends a request / command to each DTU 12, the DTU 12 responds accordingly.
12 collects sample data from each of the devices to which they are assigned. The system monitor box 16
The data provided by the TU 12 can be analyzed to determine changes that have occurred in the vascular imaging system 14.
The system monitor box 16 can also provide commands to one DTU 12 to reconfigure itself to another type of DTU 12.

The system monitor box 16 is a computer as conceptually shown in FIG.
A parallel port interface (LTP) port 40 for connecting to the master DTU 3 via a multi-pin cable connector 36 and an Ethernet connector 20 for connecting to the field service notebook computer 18. Have. The system monitor box 16 has a CD-ROM as its hardware.
ROM storage 94 or equivalent, multimedia capability, modem 96, Ethernet connection 20, sound board 98 with speakers, graphics capability, hardware key 100, and bar code reader 102
Having. The system monitor box 16 also has a CD-R
It can also be booted from OM94. The system monitor 16 preferably runs on Microsoft-based Windows-based software. The system monitor 16 may also run on a next generation software platform such as WINDOWS '95 or UNIX.

As shown in FIG. 14, the system monitor box 16 controls all the main system functions of the diagnostic system. Diagnostic network system 1 according to the present invention
0, except for the graphical user interface (GUI) 22 by software, are shown in FIGS.
As shown in FIGS. 9 and 40, the system monitor box 1
6 are included. The current and past performance information files of this system are stored in the on-site database 11.
0 is stored. The system monitor box 16 is equipped with a remote access capability 111, which communicates with the site by this remote access capability, and
Monitoring is enabled by C19. CD-ROM 9
4 includes documentation (manuals and procedures), equipment specifications, and a CD of the video support needed to perform service activities at the site.

Also, using the remote access function 111, a remote user can transfer files (eg, error logs, site history information) from the system monitor box 16, access the database of the system monitor box 16, and access the diagnostic or DTU 12 Perform remote functions such as control, receive software correction information,
(I.e., a remote command to the system monitor box 16 such as "sample DTU # 2 every 10 seconds"), and an operation execution schedule of the system. The system monitor box 16 also performs self-diagnostics and diagnostics on CD-ROM access, the network of DTUs 12, LPT port 40, serial port 108, and Ethernet connection 20.

The field service engineer makes a field service notebook (computer) 18
Is connected to the system monitor box 16 through the Ethernet connector 20, network data can be accessed. Diagnosis information is obtained through the system monitor box 16, and troubleshooting and holding of each DTU 12 can be performed. The system monitor box 16 also uses the diagnostic procedure to
We can assist service engineers. Both the field service engineer and the TAC 19 are remotely connected via the modem 96 to the system monitor box 16.
To access the network of the DTU 12 and check the operation of the system. The system monitor box 16 can also initiate contact with the TAC 19. The TAC 19 can also send email or technical report information to the system monitor box 16 for reading by a field service engineer.

The system monitor box 16 stores each DTU 1
After analyzing the data sent from 2, the result can be automatically sent to the TAC 19 via the modem 96. If the TAC 19 line is occupied for some reason, the system monitor box 16 spools the data to be sent for later transmission. Further, the system monitor box 16 allows the user to make a schedule for data log or file transmission from the system monitor box 16 to the TAC 19. For example, an error log and an operation log of the system monitor box can be scheduled to be transmitted every eight hours.

The system monitor box 16 stores each DT
Analyze test position data such as dose, signal amplitude, resolution, and field uniformity sent from U12. During installation and calibration, a field service engineer sets parameters (test position)
Enter an acceptable value for each of the. For example, an acceptable dose value can be set between 0.08 and 0.09. Once these values have been entered, they are stored in the database 110 of the system monitor box. When such a situation is commanded, the system monitor box 16 displays the dosimeter DTU3.
Read the current value from the relevant DTU, such as 8,
Next, the read value is passed to an expert system provided in the system monitor box 16. The expert system 115 compares the read value with a set value and determines whether the read value is within an acceptable range. The decisions of the expert system 115 determine what procedures or actions should be prompted to the user during repair and maintenance of the vascular imaging system.

Since the system monitor box 16 executes a number of diagnostic processing procedures, it is possible to reduce the guesswork involved in repairing the system. As shown by the example in FIG. 15, the field service engineer is guided through the analysis process by the “Resolution Procedure”, and the resolution of the image is corrected. As a result, a video image from the X-ray, such as a thin aorta, is displayed on the screen for observation by a doctor. The image quality may be degraded to little or no value to the physician. In such cases, the degradation in image quality is due to the poorness of the image tube (which costs around $ 40,000 to replace) or the poorness of the X-ray tube (which is quite cheap). It will depend on.

With this resolution processing procedure, a series of separation techniques are performed to determine the true cause of the problem. This procedure causes the instructions to be displayed on the field service engineer's notebook computer. The field service engineer then inserts the phantom object into the x-ray imaging area. The phantom object is a lead screen having wires having a predetermined interval and a predetermined thickness. Using the algorithms written in the C and C ++ languages shown in FIGS. 16 and 17, the resolution processing procedure determines where the image resolution can be measured (normal mode, enlarged I mode, or enlarged II mode). . An image tube is good if the resolution can be measured in any of these three modes. Next, the resolution processing procedure is "Display Master Objective Lens".
ve Lens) ". If the master objective lens is good, then the “Check Focal Spot Size” shown in FIGS.
ze)) is executed.

While the field service engineer has been trying to solve this resolution problem, even if the filament of the X-ray tube is actually defective, it is considered that the defect is caused by the image tube. May have been replaced. The system 10 of the present invention avoids such errors by anticipating all possible causes for the problem that has occurred and automatically rejecting / eliminating inappropriate solutions.

The expert system (expert sys
Other procedures performed by the tem) include a half-value test (which determines, for example, the hardness of the x-ray beam), a quick tube calibration check, a check tube, and the like.
Max Entrance Exposure Rate (Ch
eck Max Exposure Rate), and fluoro dose
Procedures for data (Flouro DoseData) are shown in FIGS. 20, 21, 22, 23, 24, 25, and 2 respectively.
It is shown in FIG.

Those skilled in the art will readily recognize that these procedures are merely examples of the many procedures that can be stored in system monitor box 16 and performed by expert system 115. These procedures are described in Palo Alto, California.
lto) “Neuro Data Cor”
p. On a software package marketed under the name "NexPart".
Source code for the expert system 115 (Nex
An example is shown in Appendix A below in the form of a microfiche.

This system monitor box 16 also has a safety function. Remote users, such as those connected to the system monitor box 16 via the TAC 19 and the field service notebook 18,
User login and authentication is accomplished through a user password associated with a hardware key 100 attached to the parallel port 106 of the field service notebook 18. This certification information is held in the database 110 of the system monitor. A temporary hardware key can be provided for use in installing and testing the diagnostic network system 10. During installation,
When the field service engineer calls the TAC 19 for confirmation, the TAC 19 in turn makes the key site-specific.

The expert system 115 also utilizes execution and history information stored in the database 110 of the system monitor box. The system monitor box database 110 includes an error log, an activity log, a problem solving log, a result log (providing a result of a system evaluation test), hardware key information, and a module version information of the system monitor (for each process and software). Release version and revision information). This information is used collectively to support diagnosis by expert systems.

Field Service Notebook The field service notebook 18 is provided in the diagnostic network system 10 according to the present invention. When the field service engineer arrives at the site, as shown in FIGS.
0 is connected to the system monitor box 16.
Using the graphical user interface software tool 22, the user can then interact with the system monitor box 16 and have access to all diagnostic and maintenance functions, including each DTU 12. The field service engineer notebook 18 contains "I
microprocessor, graphics capabilities, "Windows", and a Windows-based graphic user interface (G), such as a tel 386 "or" 486 "or equivalent portable computer
UI). According to a preferred embodiment of the present invention, G
As the UI, "SmartBook" available from Toshiba America Medical Systems, Inc. of Tustin, California can be used.

Technical Assistance Center The Technical Assistance Center 19 (TAC) is the central information source for the diagnostic network system 10 of the present invention. See FIG. Tools for the TAC engineer are usually available from the user interface, which allows the TAC engineer not only to upload and view images from the on-site system monitor box 16 but also to upload log files, The performance status of the system can be reviewed. The TAC 19 can use not only a complete site history, but an on-line expert system as well. Technical that can be used with TAC19
Experts assist field service engineers with questions in diagnostic network systems that require speed.

The hardware of the TAC 19 includes a plurality of conventional personal computers (PCs) having an internal modem, a plurality of Ethernet cards, and a plurality of 200
A hard disk with a storage capacity of megabytes or more, a plurality of CD-ROM drives (these can be mounted on a file server and used as a sharable resource), a plurality of Ethernet connection networks connecting workstations, one file server One backup system, one uninterruptible power supply (UPS), and one laser printer. Preferably, TAC 19 is a commercially available Novell network, Oracl.
eDatabase Server, Neuron Data Expert System, and Wind Running on All PCs
ows3.1 software is used. TAC19
Workstations are connected via Ethernet and operate on the Novell network.

When the user of the TAC connects to the site,
1) “Get Images”, 2) “DisplayImages”, 3)
The functions of "HW Key Information", 4) "Error Log", and 5) "Site History" can be used. All of these functions are indicated by on-screen buttons or icons and are accessible from the displayed screen. Where possible, accelerator keys can be provided to use those functions for access.
(The term "accelerator key (Ac
"celerator Keys""means a keystroke or combination of keystrokes that can be used in place of a pull-down menu command or click-on button.

Using the “Get Images” function, the TAC engineer can connect to a certain site and search for an image. You have the option of looking at the image as an icon before searching for it, but this icon is somewhat smaller than the original due to its small size. (The smaller the image size, the faster the transfer.) This TAC engineer can also search only the image header instead of the full image. “Display Im
The "ages" feature allows TAC engineers to display images retrieved from the site.Once displayed, it allows "windows level" control to adjust image parameters. "HWKey Informatio"
The "n" feature allows the TAC engineer to connect to a site and invoke a snapshot on the screen of the site's key table of contents. The "Site History" function allows you to scan the data stored on the site
The site history is provided from the site information stored in the AC database 112 and from the site history stored in the ASSIST database 114.

The “Site Histor” stored on the site
y "includes process history / status, key update information, key status, error messages, system execution parameters, DTU records, etc. The site history from the TAC database 112 has problems encountered (troubles). If the TAC engineer selects this option, the display area will be distinguished by either color or font depending on the three sources.
File logs can be updated by connecting directly to a site from the “History” state.

With a series of database server functions, the TAC database 112 holds complete information for all sites. All of the following features have graphical capabilities that allow the user to plot display information under a variety of graphs (pies, lines, bars). With the database server function, the TAC engineer scans the "Site History" log, scans the results log from one site through the previous site, and sees the history of hardware key updates for one site. View updated site and installed upgrade software versions, and selected field service engineers.

Network Protocols and Communities
As shown in FIG. 27, the network protocol of the DTU 12 comprises three logical layers: a data link layer 116, a session layer 118, and a network layer.
It comprises an interface layer 119 and operates via an optical fiber network 24 which is a physical media layer.

After the power is turned on, the R
The S232 port 60 (FIG. 11) has 9600, N, 8,
The optical line 55 is connected to the RS232RxD and TxD pins. Thus, each DTU 12 can be accessed by the fiber optic network 24 using the standard RS232 protocol. Switching between the RS232 and SPI 62 interface formats can be controlled by software. Communication between DTUs 12 is shown in FIG.
This is performed in the state of the data packet 120 as shown in FIGS.

DTU 1 at which data packet 120 arrived
2 includes a physical medium (eg, an optical fiber network 2).
The address is commanded through 4) and is initially manipulated by the network interface hierarchy 119. Thereafter, the data link layer 116 of the DTU 12 in the receiving state checks the checksum, checks the correct address, and receives the packet. Upon completion of this reception, DTU 12 sends the packet to its session layer. This data packet contains the preamble, the start of the frame delimiter, the destination address, the source address,
It consists of a data length field, a data field, the end of a frame delimiter, and two bytes for a cyclic redundancy check (CRC) as shown in FIGS.
The packet length is determined by examining the data length field. Then start frame, end frame and C
Validation is performed by examining the RC field. The data of the frame start and the frame end are known values. CRC validation consists of calculating the CRC on the frame, excluding the CRC field, and comparing it to the embedded CRC. This CRC algorithm used for data packets 120 is conventionally known as a "CRC-CCITT" polynomial.
(1021H) based on the classic CRC hardware circuit. It is important to note that the calculation of the CRC of the data packet 120 is done in software or hardware, depending on the network interface chosen. RS23
2 The CRC of the SCI 60 interface and the parallel port 40 is calculated by software while the SP
The CRC of the I62 interface is calculated by the hardware circuit of the FPGA 64.

The data link frame (DNP) of the DTU network protocol uses a large endian as a byte order network. Therefore, the higher order byte comes to the start address. As an example, FIG. 29 shows the data length and CRC.
Indicates the byte order used for the field. It is important to note that this hierarchy only uses the data portion of the frame to calculate the CRC.

Data Link Hierarchy This data link hierarchy 116 is the logical lowest hierarchy of the protocol. With this hierarchy, the data packet 12
The actual transfer of 0 is performed. This data link hierarchy 11
6 operates by receiving data from the session hierarchy 118 and encapsulating it. As shown in FIG. 28, this containment includes adding an address to the session hierarchy data and calculating a checksum and adding it to the data. The data link layer 116 then sends the data packet 120 shown in FIG.

The data link hierarchy 116 provides three different options for data transfer depending on the needs of a particular application. The three data transfer methods are reliable transmission with positive acknowledgment, transmission without acknowledgment, and reliable transmission with a sliding window.

Reliable transmission is based on the basic technique of "positive acknowledgment by retransmission". This technique requires that the receiving party communicate with the source, that is, send back an acknowledgment message upon receiving the data. The sender keeps a record every time it sends a data packet 120 and waits for an acknowledgment before sending the next data packet 120. The sender also has data packet 1
Sending 20 activates a user-defined timer and retransmits the data packet 120 if the timer expires before an acknowledgment arrives. Retransmission is attempted up to three times. If, for performance reasons, the received message is delivered to the session hierarchy 118 where it can send an acknowledgment and respond with a single message, half of the time required to perform such work can be saved. The data link layer 116 on the sender side always forwards the acknowledgment (embedded response) to the session layer 118 for further processing. In this mode, DT
The buffering need not be performed at the U12 node. The handle of the received message is passed to the application.
The length of this message is "DNP Maximum Transfer U
nit "cannot be exceeded. This reliable transmission service (Riliable TransmissionService)
Using Open Network, Close Network, Annotate, Invoke Addres
s), Invoke Name, Download (Down-load), Upload (Upload) and Me
An mfill module has been implemented.

In the case of transmission without acknowledgment, the message can be transmitted without waiting for the acknowledgment by the application. No message retransmission is performed.
The data link layer 116 can provide a simple transmission service for transmitting a message without waiting for an acknowledgment. The responsibility of the application program is to design it to confirm that the data packet 120 has arrived at the destination without error.

The reliable transmission / window sliding technique is used for larger transmissions than can be achieved using the other transport methods. The technique of window sliding window is a form of aggressive acknowledgment and retransmission, in which multiple data packets 120
Is transmitted before waiting for an acknowledgment. As shown in FIG. 31, instead of issuing an acknowledgment upon receipt of each data packet (packets 1-4) 120, the recipient site
Wait until one data packet 120 is received, spool each acknowledgment, and then send one acknowledgment to the sending site. Data packet 1 with no acknowledgment
The number 20 is enforced by the window size at any given time and is limited to a small fixed number. When the sender receives the acknowledgment of receipt for the first four data packets 120, the window slides by four at a certain time, and the next series of data packets 120 is sent, as shown in FIG.

The lost data packet 120 is retransmitted and acknowledged before its window slides. The sender encodes sufficient information into the barter packet 120 to indicate the state in which the acknowledgment should be returned. When the sender retransmits a lost data packet 120, it requests the receiver to immediately send an acknowledgment for each data packet 120.

Unlike the reliable and unacknowledged transmission methods with positive acknowledgment, in this window sliding method all acknowledgments are made by the data link layer 116. You.
The sender's data link layer 116 accepts a large number of messages from its session layer 118, and the recipient's data link layer 116 passes a large number of messages to its receiver's session layer 118. If the requests are too large, data link hierarchy 116 splits them into individual data packets 120.

[0087] session Hierarchy This session layer (Session layer) 118 is DTU
This is a logically higher layer on the protocol layer of the network 13. This provides a protocol for two types of services required in the DTU network 13. 1) a protocol service standard of the DTU network 13 for each DTU 12, and 2) a unique service determined by the type of the DTU 12, such as, for example, kV, mA or a dosimeter.

The data that the session layer 118 sends to the data link layer 116 consists of two parts: the data length and the data (which includes the header itself as well as the data itself). In the session layer 118, the data packet 12
Only the data part of 0 is used. Based on the first two bytes of the header, as shown in FIG. 30, this session layer 118 can determine the type of service requested by or by the DTU 12. This service includes annotations, network check diagnostics, program and module downloads, module recalls, memory dumps, and DTU 12 time setting and debugging sessions.

Network Interface Hierarchy The network interface hierarchy 119 is responsible for data communication at the lowest level of the network, and includes devices necessary for transmitting and receiving data packets 120.
Consists of drivers and modules. SCI 60 (R
S232), the SPI 62, the parallel port interface 40, and the packet driver at this level perform CRC calculation and validation.

All data packets 120 that have a valid CRC and will be the DNP address assigned to the local node are accepted and passed to the data link hierarchy 116. "Broadcast (broadcas
t) "data packet 120 is accepted as well. All other data packets 120 require no further processing and are dropped (dropped). Master D
The TU 34 is a different exception, and accepts a data packet 120 scheduled in the system monitor box 16 as well as the master DTU. System monitor box 1
The data packet 120 scheduled for 6 or from the system monitor box 16 is passed over the parallel port interface 40 of the system monitor box 16.

DTU software The DTU software is roughly classified into “startup (St)” which is executed when the power of the DTU 12 is turned on.
art Up) software and system monitor box 1
6 is categorized as "Services" software that is executed when requesting service. C and 6
K used in combination with the assembly language of 8HC11
A sample of the source code for the V, mA DTU 38 is included in Appendix A below.

Microprocessor 4 of 68HC11A0
4 starts execution of instructions (code) after power-on / reset. (See the microprocessor memory map in FIG. 10.) This software code is available from San Jose, California.
e) Model N manufactured by XILINX company in
o. Select a bank of EPROM 58 that contains code for FPGA 64, such as XC3064
Copying the code to the FPGA chip 64 and performing a self-diagnosis. The self-diagnosis starts with a memory test of the two RAM chips 56A and 56B in the DTU 12. If during this diagnosis no defects are found that would disable the network, such software initializes the serial port 54 and waits for a data packet 120 appearing on the serial port 54, going around one quick loop. With this software, the memory 200
Bank 0 is selected from the 0 chip 56A, and a necessary communication buffer is set up. Data packets 120 are received using these buffers. The startup pseudocode is shown in FIG.

After power-on, the FPGA 64 executes a logical function according to the program loaded therein. The program can be downloaded from the system monitor box 16 to the RAM memory banks 56A-56C of the microprocessor module 44. This FPGA6
Reference numeral 4 denotes a memory mapped from address 0800 to OFFF (hexadecimal). Port A of the microprocessor 44 of the 68HC11A0 is connected to various FPGA 64 control pins. FPGA64 is RAM
RAM configurable, ie, F
The configuration of the PGA 64 must be downloaded after power-on. Such a configuration program resides in EPROM 58. The initialization process resets the FPGA 64 and then stores such configuration from EPROM 58 at address 0800
(Hexadecimal notation).

To reset the FPGA 64, the FPG
A64 RESET (port A, bit 6) and PR
OGRAM Each pin of DONE (port A, bit 5) is set low for 6 microseconds and returned high. This reset is INIT
Completed when a low-to-high rise is detected on the (Port A, Bit 0) pin. The configuration program is downloaded by writing one byte to address 0800 at a time. The FPGA 64 uses one pin to accept data. In order to properly download such a program, the READY / BUSY pin (port A, bit 1) must be checked to see if it is "ready" before writing the next byte to FPGA 64.

DTU Self-Diagnosis The present invention includes an error reporting mechanism that indicates any device or network defects. If an inconsistency occurs in the DTU 12 read / write processor, an unacceptable level of voltage is detected in this system and a signal is sent to the LED 104 on the relevant DTU 12 to indicate a problem condition. Field service notebook 1 for local diagnostics
8 can be connected directly to the RS232 terminal 55 of the DTU 12.

When the initialization of the FPGA 64 is completed, D
The self-diagnosis of the TU 12 is performed. First, the DTU 12 performs a RAM memory test by writing a unique pattern to each bank of the RAM chips 56A, 56B and 56C. This pattern is read back and compared. The pattern used for this test is a bank number. Since all banks are written and then read, the switching characteristics of the banks are tested simultaneously. If an inconsistency occurs during this read / write process, startup is halted and an error is reported to LED 104.

Next, the battery voltage level and the power supply level are checked. If the voltage level is unacceptable, start-up stops and an error is reported to LED 104. If the voltage is low, but acceptable to allow the electrical system to still function within the specified voltage range, it will be reported to the system monitor box 16 but will not stop.

The SCI interface 60 is initialized by the following settings. That is, the baud rate: 960
0, parity: none, stop bit: (1), and data bit: (8). Next, the network buffer is initialized. Two buffers are required to receive and transmit the data packet 120. These buffers are "BANK 0 RAM2000" 23A
Assigned from.

The DTU operation “Start-up” sequence is shown in FIG. 34, and is a process for initializing all DTUs 12. Each DTU1
2 is self-diagnosed and annotated (annota) when commanded by system monitor box 16 through master DTU 34.
option). "Power on" processing part is DTU
12 in which each DTU 12 has a command
It passes the packet 122 through the DTU network 13 and identifies itself as returning it to the master DTU.

This annotation command enables the configuration of the DTU network 13. At startup, all D
Status of TU12 and status of SCM
50 states are determined. At the time of the annotation time, its state and identification numbers are encapsulated and sent as part of the annotation packet 124. This identification number for DTU 12 and SCM 50 is assigned at the time of EPROM 58 programming and is stored in EPROM 58. Both numbers are useful to the software and are read at startup. The sequence number for the DTU 12 is similarly added to the annotation packet 124.

As shown in FIG. 35, this annotation packet 12
4 is transmitted from the master DTU 34 through the DTU network 13, during which annotation information from each of all DTUs 12 is added to its annotation packet 124. Similarly,
When the DTU 12 examines the annotation packet 124,
The TU 12 determines its sequence number in the network and wraps that sequence number as its network number.

In this annotation session, the fiber optic network 24 is open and each DT
U12 sends the annotation packet 1 after they add the annotation information.
It is assumed that you understand that 24 must be retransmitted. The DTU memory dump command fulfills the ability to request a memory dump of the DTU 12 memory. The system monitor box 16 is a DTU
When a memory dump request indicating a bank is issued at 12, an address and the total number of bytes for dumping are started. DTU 12 responds with the image in memory. The starting source by this EPROM 58
An example of the code (using a combination of C and 68HC11 assembly language) is provided in Appendix A below.

The system monitor box 16 can add a module and download it to the DTU 12. A download command serves to download the program module to any bank of RAM chips on the DTU 12. The bank, start address and number of bytes are specified. The module call command is the R of the DTU 12 where the system monitor box 16 is located.
This is a method of instructing to execute a module downloaded to the AM memory. With this command, DTU
The time of 12 is changed to the time of the system monitor box 19.
After 70 years, it is set in seconds.

Each DTU 12 executes and provides a specific service based on the SCM 50 built in the DTU. General network services (check, open, close, annotate, DTU memory dump, download, module call and time set commands, etc.) are available for all DTs regardless of the specific purpose of each DTU 12.
It is given by U12. These general services are DTU
Performed by 12 network commands. Although the maximum number of DTUs 12 that can be arranged in the network is 255, 12 arrangements are preferable.

The network check is started by the system monitor box 16 (via the master DTU 34). Since the fiber optic network 24 is normally closed (retransmittable), any data packets 120 sent from the master DTU 34 must be returned to and received by the master DTU. This kind of data packet 1
20 is set to indicate that this packet is a "passing" data packet that requires no processing or response. If this transmitted data packet 120 is returned and received by master DTU 34, such fiber optic network 24 is operable.

Using the network open command can instruct all DTUs 12 to disable the automatic retransmission function. For this reason, the DTU 12
Retransmit any data packets 120 that are not addressed to the TU. The annotation packet 124 is an exception as described above. A network close command can command all DTUs 12 to enable the automatic retransmission function.

According to the service requested from a specific DTU 12, the system monitor box 16
After the network annotation that sets up the second function, its D
The appropriate software modules are dynamically downloaded to the TU 12. For this reason, each DTU 12 attached to a separate device has a specific software package and execution module tailored to its function.

For example, the execution module in the kV, mA DTU 76 waits for a request from the system monitor box 16 and samples either kV or mA. When this request is received, its analog port (pin 0 for kV and pin 1 for mA) is sampled and its value is returned in the response data packet 120. Similarly,
The execution module of the PMT DTU 80 waits for a request from the system monitor box 16 and samples the PMT voltage. When this request is received, its analog port (pin 0) is sampled and its value is returned in response data packet 120.

The software module of the master DTU 34 has a parallel port 40A through which the master DTU 34
Communicate with The master DTU 34 waits for a strobe signal from the system monitor box 16, which is received through the LPT port 40 of the system monitor box, and reads 8 bits (1 byte). When the read byte becomes one frame, this frame is transmitted to the optical fiber network 24. This reverse transfer is similar except that half of one byte is transferred at a time.

System Operation The user interface interposed between the field service notebook 18 and the system monitor box 16 is achieved by the GUI 22, which is
Preferably, I is Toshiba's in-house software program "Smartbook" from Toshiba America Medical Systems, Inc. of Tustin, California. This smartbook is available from Asyme, located in Bellevue, Washington.
"Multi Media made by trix
Toolbook ”(“ Toolbook “Toolbook”
k ")), developed on a commercially available software package known as k"). An example of the source code of this smart book is included in Appendix A below in the language of the tool book itself. When using a smartbook, the field service engineer, once authorized for himself, can access the diagnostic network system 10 of the present invention from his field service notebook 18. Through the pull-down menu options provided by the smartbook (this example is shown in FIGS. 36-40)
), The field service engineer has access to a number of options.

The field service engineer can immediately connect the field service notebook 18 to the system monitor box 16, collect data through the serial port 108 using the smartbook software, and The expert system 115 is operated. FIG. 41 shows symbols on the sequence and field service
The following options available to the engineer are illustrated. First, an Ethernet connection is made between the field service notebook 18 and the system monitor box 16 (step 140).

To launch the smartbook tool, the field service engineer plugs the customized hardware key 100 into the parallel port 106 of his notebook (step 14).
2). The hardware key 100 permits user access to the diagnostic network system 10 and incorporates an expiration time therein. If the key has not expired, the smartbook launches a login screen (not shown) displaying a username and password prompt.

When the connection is established and secure access is confirmed, the field service engineer notifies the diagnostic network system 10 of the present invention mounted on the system monitor box 16 of the start of diagnosis (step 14).
4). FIG. 36 illustrates a typical screen image initially provided to a field service engineer and includes a graphical user interface main screen.
It includes a menu 22 and a status bar 134. The main menu 22 presents a number of menu options on a menu bar, including: configure 126, system diagnostics 128, view 13
0, and Utilities 126.

[0114] Status bar on each screen
134 (FIG. 36) indicates whether the site has received any new mail since the last time the user logged in,
System status area
136 indicates the current state of the blood vessel imaging system, and indicates a warning or an emergency error area (Warning or emergency error area).
Emergency Error area 138 indicates a message that requires user attention, and the process area (Pr
ocess area) 140 displays the currently running process. When the user logs in, a status bar 134 is displayed with all subsequent screens. This allows the user to access the key information regardless of the activity. This also provides consistency between screens and facilitates a process that is familiar to the user.

Next, various other options of the main menu 22 will be described in more detail. Referring to FIG. 41, the configure option 126 allows the user to perform an initial configuration and then perform any necessary reconfiguration at a later stage. During installation, the user may be able to access the site 146, the X-ray system 14
8 and the DTU network 13 must be configured (step 150). After the installation, a re-equipment configuration may be required only for the DTU network 13 (see step 152). This reconfiguration is required each time the DTU 12 is moved to a different test location.

In the site configuration (step 146), the user enters site-specific information stored in the system monitor box database 110 and the TAC 19. X-ray equipment configuration (X-ra
The y configuration option (step 148) allows the user to enter information about any system components that need to be replaced. Choosing an X-ray configuration option displays a still picture of the X-ray room on the screen of the field service notebook, showing the various components that make up the vascular imaging system 14. Root bar representations of the various components of the X-ray system are made in a similar manner. Using this display, the user can select specific components that make up the vascular imaging system 14 at such sites. The selections are located in predetermined locations on the display screen of the field service notebook 18, forming a system configuration specific to this site. This specific device configuration is saved in the database 110 of the system monitor.

A replaceable component has a hot area in which, when selected (clicked on), its picture, current part number, model number, and the serial number of the component are displayed. If such a special component is not in the database 110 of the system monitor box, the serial number field is blank and the user is prompted to type the serial number of the new component to be installed. A bar code reader 102 (FIG. 14) that scans the serial number can also be used to reduce the possibility of errors. Once this serial number is entered, the serial number, model number, and part number (part numbe
r) is automatically cross-checked to ensure that the combination is in the TAC database 112. Any discrepancies are communicated to the field service engineer via an e-mail message that the TAC sends to the site and displayed in the status bar area 138. From now on, whenever a field service engineer logs in to this site, the mismatch indication will be displayed in the status bar as “workin”.
g and e-mail "area 138. Component component descriptions and their associated model / serial numbers are automatically updated in the system monitor box database 110 and TAC database 112.

From the menu bar of the device configuration 126, select “VASP
Selecting the “AC Configuration” option launches another submenu (see Figure 41), which lists the most common post-installed configurations for a particular site and provides a menu of accessory tools. Device configuration screen (Configurationscr
een) is displayed on the field service notebook, and this screen displays a picture of the X-ray room in which the test position is marked and a toolbar showing various DTUs 12. Therefore, the user sets the DTU 12 on the D
Drag and drop to various test locations on the display picture corresponding to the TU placement. If an incompatible DTU is dragged to the test location, a mismatch flag is flagged as an error and such a partner is not allowed. For example,
The kV, mA DTU 76 cannot be used in place of the dosimeter DTU 38. The user has the ability to customize, add, and delete DTUs 12 from the customer and adapt the software configuration to the actual physical configuration of the vascular imaging system 14.

By selecting “Accessories”, the multimedia accessory connected to the diagnostic network system allows the user to connect to the diagnostic network system using a camera, sound board, or video coupled to the vascular imaging system 14. Possible hardware can be contacted. Functions that depend on hardware that have not been identified as usable are halted. Critical hardware cannot be selected in the operation of the blood vessel imaging system. That is, if the vascular imaging system does not operate without it, its function will not be stopped.

"Sy" on the main menu (shown in FIG. 41)
Selecting option 128 of "stems diagnostics" provides the user with the most common troubleshooting tools associated with the vascular imaging system 14. This option 128 of "systems diagnostics" allows the field service engineer to Perform calibrations, perform preventive maintenance, troubleshoot, observe system-specific component lists, replace parts on the system, or place the product in a setting that the customer feels provides the best image. Optimal characterization criteria can be generated so that the diagnostic network system 10 can be returned.This "Systems Diagnostics" option 128
By selecting, the processing procedure as shown in FIG. 15 and FIGS. "Resolution"
n ”,“ Half Value Layer ”, a smart book (Sm
A sample menu screen from artBook) is shown in FIGS.

When the user enters "Systems Diagnostics" 128
When is selected, a picture of the blood vessel imaging system 14 is displayed on the screen of the field service notebook 18 as shown in FIG. All selectable components of such vascular imaging system 14 are identified as buttons, and the action buttons are status bar 134 for calibration, preventive maintenance 15
6, troubleshooting 158, components 1
60, snapshot 162, and replacement 164. Therefore, when the user wants to calibrate the X-ray tube, the X-ray tube button and the calibration button are selected. On-screen instructions consisting of text, flowcharts, and / or video chips are then displayed on the screen to assist the user in completing the calibration process.

For example, when the field service engineer selects “troubleshoot”, the diagnostic network system 10 of the present invention guides the user to the evaluation process,
Display, information and suggestions online, generally in Figure 4
2 (see also FIG. 15 and FIGS. 18-26).

When the option of “View” 130 (FIG. 41) is selected, the field service engineer
Il ”166 or online X-ray“ Manuals ”168
Will be accessible. Selecting "Mail" 166 allows the field service engineer to view and respond to the newly saved message for the site, or see the latest information in the TAC 19 documents. The field service engineer who chose the "Manuals" 168 option is CD-
The user can access the X-ray technical manual stored in the ROM storage device 94. These on-screen manuals include text, flowcharts, and both, as well as animated video chip instructions. The field service engineer can scan through the technical data and see the relevant video chips, plus zoom on the components found in another picture to get a list of sub-components And you will be guided step-by-step through the repair or maintenance process. Text, as well as video segments of the screen, are also associated with each other.

The "Utilities" 132 option shown in FIGS. 41 and 43, 44 and 45 allows the field service engineer to
You can see the history of past and present site results, past system problems (troubles)
And how they fixed the problem, and error log 17
8 can be considered. The analysis log of the past results is stored in a configurable results log in the system monitor database 110, and the overflow is automatically sent to the TAC database 112. If the field service engineer has access to a repair procedure for a similar problem that occurred earlier, the information in the resulting log can be used to reduce repair time. Current system status such as logged errors, current activity, and files spooled to the TAC 19 can be viewed as well.

The Fixes Log 176 contains a history of all problems encountered at the site and information on how the problems were fixed. The entire log is also stored in the database 110 of the system monitor box, and a copy of the log is also stored in the TAC database 112. Updates to the on-site database are automatically and electronically sent to the TAC database 112.

Error Log 178 contains a list of vascular imaging system errors logged at the site. The size of this error log is configurable, and overflowing error log information is automatically sent to the TAC database 112.
The user can display the error. That is, within a range of time, at a certain level, at a certain number / string, and by a particular operation. The user may also turn off certain fields while viewing all or a subset of the error log 178.
FF). For example, once all errors associated with a level have been pulled out, the field can be turned off, allowing more information to be displayed per line. The error may be at one of three levels: "Operator", "Service", and "Debugging". This level is communicated to the user by being displayed. For example, when the field service engineer displays the error log 178, all errors at the operator and service level except the debugging level are displayed. But,
When a higher user logs in, all levels of errors are displayed.

The user can use the “Status” utility 17
Error 18 logged in the current session via 2
0, log 1 of activity that occurred in the current session
82, a file 184 spooled (queued) to be sent to the TAC 19, and a hardware key 100 state 186 is included.
The current operation state of the diagnostic network system 10 can be viewed. This status error log (Stat
us Error Log) 180 is the error site history
It has viewing capabilities of “operator”, “inspection and repair”, and “debugging” similar to the log (Error Site History Log) 178. The activity log 182 has a date and time stamp, a logging process name, and a message string. The user can search through the logs and retrieve the activities logged by the particular process. This activity log 182
Is configurable in size. The overflow is automatically sent to the TAC database 112.
By selecting spool 184, files queued to be sent to TAC database 112 can be displayed. The information displayed with each entry includes the name of the process that queued the file, the date and time the entry was spooled, the date and time the entry is scheduled to be sent, the destination (where the file is sent), the expected This includes the transfer time, the current state of the entry (active or pending), and the size of the file.
The user can edit the spool (queue) by adding or deleting entries. The added entry has a user configurable "Send Immediately" option or a "Schedule to be sent at <time>" option. By default, the added entry is scheduled at the end of the current list.

The field service engineer also has the option of running various self-diagnostic tests with the smartbook to check the following key features: That is, self-diagnosis for the Ethernet connection 20 between the field service notebook 18 and the system monitor box 16, the connection between the system monitor box 16 and the master DTU 34, the optical fiber network 24, and the system monitor box 16. . Thus, one tool performs a variety of inspection and repair functions.

Examples of Development of the Present Invention FIGS. 46 and 47 show system blocks of examples in which the above-described diagnostic network system is further developed.

The diagnostic network system shown in FIG. 46 includes a plurality of sites 902a,..., 902c and one TAC 90 via a network 901 (for example, INDS).
3 is connected. Multiple sites 902a,
, 902c are each provided with a medical modality in which a large number of various modules (corresponding to devices or components of the present invention) are connected to each other to perform one function, similarly to the above-described embodiment. Of the plurality of sites 902a,... 902c, for example, one site 902a is a site of a magnetic resonance (MR) imaging system, another site 902b is a site of an X-ray CT scanner, and the remaining sites 902c are blood vessels. It is a site of an imaging system (vascular system: also called an angiography (ANGIO) system). A DTU is installed in each module of each medical modality, and this DTU is incorporated in the same or similar network as described above. The TAC 902 has an FTP (File Transfer Protocol) used when sending information from each site to a file server (File Server) via a hub (HUB) in addition to a workstation (WS).
An access server (ACCESS) used when a server and a field engineer / notebook are connected to access information of a file server is provided.

As a result, a plurality of sites 902a,.
The 902c can communicate individually with the common TAC 902 and can operate the same or similarly as described above. If the TAC is configured to be used in common by a plurality of sites as described above, the cost for constructing and operating the TAC can be reduced. Further, it is possible to provide a diagnostic network system capable of universally dealing with various types of modalities at a plurality of sites.

The number of sites and the types of modalities are not limited to those shown in FIG.
For example, two sites may be connected, or four or more sites may be connected. The type of the modality may be any type, for example, an X-ray TV device, a nuclear medicine diagnostic device, a biomagnetic field measuring device using a SQUID element, and the like.

The diagnostic network system shown in FIG. 47 is a further development of the system shown in FIG. That is, two systems of the system of FIG.
This is a system in which networks are connected to each other to enable bidirectional or unidirectional communication. In the figure, reference numerals 901 and 911 denote networks, and reference numerals 902a and 902a.
, 902f and 912a,..., 912c indicate sites where medical modalities are installed, and 903, 913a, and 913b indicate TACs, respectively. One of the networks 901 and 911 is formed of, for example, an INDS line, and the other is formed of, for example, an analog transmission line, and is connected to each other. Particularly, one network 911 is characterized in that a plurality (here, two) of TACs are connected.

In the case of a diagnostic network system for connecting networks as described above, one network 9
01 TAC 902 is the TA of the other party's network 911
C912a, 912b can be configured to be directly accessible,
Provides a wide range of information needed for modality testing. Access in the opposite direction can also be configured. For this reason, a system directly connected to one network is constructed in, for example, a domestic region (or one region in Japan), and a system directly connected to the other network is constructed in an overseas region (or another region in Japan). Thus, a wide-area diagnostic network system can be provided. As another embodiment, when connecting networks in this way, three or more networks may be connected to each other.

Note that the modular system that can be diagnosed by the diagnostic network system is not necessarily limited to the medical modality as described above, and a plurality of module devices are connected to each other to perform a specific function. Any system may be used as long as the system has the same operation and effect as the above-described embodiment.

[0136]

As described above, according to the present invention,
To provide a diagnostic network system and a diagnostic method capable of monitoring a modular system such as a blood vessel imaging system more simply, with lower cost and higher reliability, and performing maintenance (inspection) and repair. Can be. Further, it is possible to provide a distributed test unit that can be suitably used for the diagnostic network system and the diagnostic method.

More specifically, the costs for monitoring, maintenance, and inspection can be significantly reduced, and a reliable solution to a problem can be presented when a trouble occurs. In addition, the field service engineer who maintains and checks the modularized system can reduce the on-hand items, improve the convenience, and improve the mobility. Furthermore, it is possible to eliminate or reduce trial and error factors in diagnosing a trouble (problem) in the modular system, efficiently present a solution to the problem, and contribute to a reduction in diagnosis cost. And even experienced field service engineers,
It is possible to present an accurate solution to a problem of the modular system that occurs in a difficult-to-solve manner. Furthermore, after maintenance, inspection, and troubleshooting, the modular system can be easily returned to its previous state of optimal performance, thereby also reducing the total time and labor for maintenance and the like. Furthermore, the performance status of the modular system can be easily and reliably monitored online, and the reliability of system management is improved.

It should be noted that the terms and expressions used in the above description are used as terms for describing the embodiments, and are not intended to limit the present invention. It is to be understood that various modifications are possible within the scope of the claimed invention, without intending to exclude the equivalents or parts thereof described and described.

An example of the source code cited in the above description is attached as Appendix A below.

[0140]

[Outside 1]

[0141]

[Outside 2]

[0142]

[Outside 3]

[0143]

[Outside 4]

[0144]

[Outside 5]

[0145]

[Outside 6]

[0146]

[Outside 7]

[0147]

[Outside 8]

[0148]

[Outside 9]

[0149]

[Outside 10]

[0150]

[Outside 11]

[0151]

[Outside 12]

[0152]

[Outside 13]

[0153]

[Outside 14]

[0154]

[Outside 15]

[0155]

[Outside 16]

[0156]

[Outside 17]

[0157]

[Outside 18]

[0158]

[Outside 19]

[0159]

[Outside 20]

[0160]

[Outside 21]

[0161]

[Outside 22]

[0162]

[Outside 23]

[0163]

[Outside 24]

[0164]

[Outside 25]

[0165]

[Outside 26]

[0166]

[Outside 27]

[0167]

[Outside 28]

[Brief description of the drawings]

FIG. 1 is a diagram showing an example of a diagnostic network system of the present invention.

FIG. 2 is a diagram of an example of a diagnostic network system of the present invention when connected to a blood vessel imaging system.

FIG. 3 is a diagram showing an on / off state of the diagnostic network system of the present invention;
Site part (represented by lower circle) and off-site support provided by TAC (represented by upper circle)
FIG.

FIG. 4 is a diagram of a diagnostic network system having a star arrangement according to the present invention.

FIG. 5 is a cross-sectional perspective view of a generalized DTU module.

FIG. 6 is a functional block diagram of a microprocessor module common to each DTU module.

FIG. 7 is a functional block diagram of a power module common to each DTU module.

FIG. 8 is a schematic diagram of a sample control module common to kV, mA DTU, PMT DTU, dosimeter DTU, and master DTU.

FIG. 9 is a table of a master pin assignment of a multi-pin connector used in a DTU.

FIG. 10 shows a DT comprising a RAM and an EPROM memory.
FIG. 4 is a diagram of a U microprocessor memory map.

FIG. 11 is a diagram of the communication data flow between the network and the sample control module when controlled by a DTU microprocessor.

FIG. 12 is a block diagram of a dosimeter DTU.

FIG. 13 is a block diagram of an operator console DTU connected to the operator console.

FIG. 14 is a conceptual diagram of a function executed by a system monitor.

FIG. 15 is a flowchart of a resolution processing procedure.

FIG. 16 is a diagram showing a problem separation algorithm used in a resolution processing procedure.

FIG. 17 is a diagram showing a problem separation algorithm used in a resolution processing procedure.

FIG. 18 is a flowchart showing a focus test processing procedure.

FIG. 19 is a flowchart showing a focus test processing procedure.

FIG. 20 is a flowchart showing a half value test processing procedure.

FIG. 21 is a flowchart showing a quick pipe calibration / check processing procedure.

FIG. 22 is a flowchart showing a quick pipe calibration / check processing procedure.

FIG. 23 is a flowchart showing a check MAX ERR processing procedure.

FIG. 24 is a flowchart showing a procedure of indirect imaging dose data processing.

FIG. 25 is a flowchart showing a procedure of indirect imaging dose data processing.

FIG. 26 is a flowchart showing a procedure of indirect imaging dose data processing.

FIG. 27 is a conceptual diagram illustrating a session layer, a data link layer, and a physical media connection related to communication between two DTUs according to the present invention.

FIG. 28 is a diagram showing components of the data link layer packet of FIG. 27.

FIG. 29 is a diagram showing a data link frame configuration of the DTU network protocol of FIG. 27.

FIG. 30 is a diagram showing a configuration of a session layer packet of FIG. 27.

FIG. 31 is a diagram illustrating a “sliding technique” for improving the reliability of data transmission.

FIG. 32 is a diagram illustrating a “sliding technique” for improving the reliability of data transmission.

FIG. 33 is a diagram showing a pseudo code for starting a DTU.

FIG. 34 is a diagram showing a schematic startup sequence for a general DTU.

FIG. 35 illustrates an annotation session of a DTU network according to the present invention.

FIG. 36 is a diagram showing an example of a screen from a SmartBook, showing graphical user interface software provided to a field engineer when logging to the present system.

FIG. 37 is a view showing an example of a screen from a smart book (SmartBook), and shows graphical user interface software provided to a field engineer when logging to the present system.

FIG. 38 is a diagram showing an example of a screen from a smart book, showing graphical user interface software provided to a field engineer when logging to the present system.

FIG. 39 is a view showing an example of a screen from a smart book (SmartBook), showing graphical user interface software provided to a field engineer when logging to the present system.

FIG. 40 is a diagram showing an example of a screen from a smart book, showing graphical user interface software provided to a field engineer when logging to the present system.

FIG. 41 is a flowchart illustrating menu options available to a field service engineer in the diagnostic network system of the present invention.

FIG. 42 is an operation sequence diagram showing a “troubleshooting” process of FIG. 41.

FIG. 43 is a flow chart for a “utility” option of the diagnostic software of FIG. 41 according to the present invention.

FIG. 44 is a flowchart for a “utility” option of the diagnostic software of FIG. 41 according to the present invention.

FIG. 45 is a flowchart of a “utility” option of the diagnostic software of FIG. 41 according to the present invention.

FIG. 46 is an explanatory diagram of a diagnostic network system according to one development example of the present invention.

FIG. 47 is an explanatory diagram of a diagnostic network system according to another development example of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 Diagnostic network system 12 DTU 13 DTU network 14 Vascular X-ray imaging system 15 C-arm 16 System monitor box 17 Patient table 18 Field engineer's notebook 19 TAC 20 Ethernet connection 24 Optical fiber cable 28 Dosimeter 30 Console 32 Control Panel 34 Master DTU 36 Multi-pin cable 38 Dosimeter DTU 40A Parallel port 40 LPT port 46 MM (Microprocessor module) 48 PM (Power module) 50 SCM (Sample control module) 76 kV, mA DTU 78 High voltage Transformer 80 PMT DTU 88 Console DTU 104 LED

──────────────────────────────────────────────────の Continuation of the front page (51) Int.Cl. ⁶ Identification number Agency reference number FI Technical indication location G06F 13/00 351 G06F 13/00 351N 19/00 15/42 X (72) Inventor Dimitrios Romankis United States of America 92630 Lake Forest, California Apartment H16, Osterman Road 20041 (72) Inventor Miltin Nicolic United States 92688 California, Santa Margarita, Leonard Ranch 8 (72) Inventor Joyti Rashwani United States 92673 California, San Clemente, Via De Lazno 2522 (72) Inventor Dan Durick United States 92663 Newport Beach, California, No. 40 Doo REIT 213 (72) inventor Hatim El - Sebari United States 92630 California, Lake Forest # 105-195, Tabuko load 25 422 (72) inventor Rec Morgan United States 92,677 California, Laguna Niguel, West gate 57

Claims (49)

[Claims] 1. A diagnostic network system for communicating with a plurality of devices, comprising: a plurality of distributed test units individually communicating with respective ones of the plurality of devices; a master distributed test unit; A network in which the master distributed test unit and the plurality of distributed test units are connected by a communication medium to enable information transmission; and the plurality of distributed test units via the master distributed test unit. And a control unit for collecting information from the plurality of distributed test units; and a system monitor unit for editing based on the information collected from the plurality of distributed test units. A database storing the edited information, and analyzing the collected information. And a diagnostic unit that identifies a plurality of inspection and repair of one or more devices required state of the device, the diagnostic network system, wherein a. 2. The diagnostic network system according to claim 1, wherein the network is an optical network connecting the plurality of distributed test units to each other. 3. The diagnostic network system according to claim 1, wherein the network is an optical network in which the plurality of distributed test units are connected in series in a loop. 4. The diagnostic network system according to claim 1, wherein a sequence of transmitting information on said network starts and ends at said master distributed test unit. 5. The diagnostic network system according to claim 1, further comprising a user interface that communicates with the system monitor unit and allows a user to communicate with each of the plurality of distributed test units. 6. Each of the plurality of distributed test units includes means for receiving information from an upstream distributed test unit, and a selected portion of the received information along with information generated by the distributed test unit. Means for passing to a downstream distributed test unit. 7. The diagnostic network system according to claim 1, wherein each of said plurality of devices has a test location, and each of said plurality of distributed test units has means for monitoring said device at said test location. 8. The plurality of devices have a plurality of test locations, and each of the plurality of distributed test units communicates with the corresponding device, and the device maintains a desired value at the test location. The diagnostic network system of claim 1, further comprising means for controlling said device through said test location. 9. The information transmitted from the master distributed test unit to the distributed test unit includes a device control command, and the control means controls the device according to the device control command, and 9. The diagnostic network system according to claim 8, wherein the device is maintained at a position at a value specified by the device control instruction. 10. The diagnostic network system according to claim 1, wherein the system monitor unit maintains optimum performance data for the plurality of devices, the optimum performance data being adapted to a user of the plurality of devices as a system. 11. The database includes pre-defined operating specifications for selected operating parameters for the plurality of devices, and wherein the diagnostic unit is configured to transmit data received from the device while a test is being performed by a user on the device. 6. The diagnostic network system according to claim 5, further comprising: means for continuously analyzing, and issuing a warning to a user when the analysis result indicates a deviation in operation specifications. 12. The database has a history of past device problems and information on solutions to past device problems,
A step of recognizing a past device problem similar to a current device problem by referring to the database, and resolving the current device problem in consideration of a solution to the past device problem. 2. The diagnostic network system according to claim 1, further comprising means for indicating to the user. 13. The diagnostic network system according to claim 5, wherein said system monitor includes means for communicating with said user interface to guide said user through a procedure for evaluating said plurality of devices. 14. The diagnostic network system according to claim 5, wherein said system monitor includes means for communicating with said user interface to indicate tools required to troubleshoot said plurality of devices. 15. The diagnostic network system according to claim 5, wherein the system monitor includes a unit that communicates with the user interface to indicate a procedure of an inspection and repair that can be performed on the plurality of devices. 16. The diagnostic network system according to claim 1, wherein said database further includes substantially all document information required for service of said plurality of devices. 17. Each of the plurality of data test units receives a signal from the network,
10. The diagnostic network system according to claim 9, including means for retransmitting the signal over the network, the retransmitting means including means for remodulating the signal and transmitting the signal over the network. 18. The diagnostic network system according to claim 1, wherein the distributed test unit includes a self-diagnosis unit performed during startup. 19. The diagnostic network system according to claim 1, wherein said distributed test unit includes means for reporting a voltage or memory mismatch error. 20. The diagnostic network system of claim 1, further comprising a remote interface unit that communicates with said system monitor unit and allows a remote user to communicate with each of said plurality of distributed test units. 21. The diagnostic network system according to claim 1, wherein said network is an optical network in which said plurality of distributed test units are connected in parallel to said master distributed test unit. 22. A diagnostic network system that communicates with a plurality of devices, a plurality of distributed test units that individually communicate with each one of the plurality of related devices, and the plurality of distributed tests. A network for transmitting information between the units; and a system monitor unit for communicating with the plurality of distributed test units through an integrated circuit board. The system monitor unit receives information from the plurality of distributed test units. A control unit to collect; a database compiled from information collected from the plurality of distributed test units; and one or more of the plurality of devices that may need to be analyzed and serviced of the plurality of devices. Between a diagnostic unit that identifies the state of the device and the distributed test unit And diagnostic network system comprising a an integrated circuit board for communicating with these distributed test unit. 23. A diagnostic network system that communicates with a plurality of devices that co-implement a diagnostic system, each issuing instructions to and receiving information from an associated one of the plurality of devices. A plurality of distributed test units capable of: a master distributed test unit for issuing commands to the plurality of distributed test units and receiving information related to the plurality of devices from the plurality of distributed test units; An optical network for transmitting information between a master distributed test unit and a plurality of distributed test units, and a system monitor unit for communicating with the plurality of distributed test units through the master distributed test unit, The system monitor unit includes the plurality of distributed test units. A control unit that collects information from a plurality of distributed test units; a database that compiles information collected from the plurality of distributed test units; and the collected information may be analyzed and service and repair of the plurality of devices may be required. A diagnostic unit for identifying a state of one or more devices. 24. A diagnostic network system for communicating with a plurality of devices forming a medical modality, wherein the plurality of distributed test units individually communicate with an associated device among the plurality of devices; A master distributed test unit that supervises the test operation of the distributed test unit, a network that connects the master distributed test unit and the plurality of distributed test units by a communication medium to enable information transmission, A system monitor unit that communicates with the plurality of distributed test units via a master distributed test unit, the system monitor unit comprising information on functions of the plurality of devices from the plurality of distributed test units. A control unit that collects data from the plurality of distributed test units. A database storing editing information edited on the basis of the obtained information, and a diagnostic unit for analyzing the collected information and diagnosing the operation states of the plurality of devices by referring to the editing information, A diagnostic network system characterized by the following. 25. The system comprising the plurality of distributed test units, the master distributed test unit, the network, and the system monitor unit are individually connected to the plurality of medical modalities.
The diagnostic network system as described. 26. The method of claim 26, wherein the plurality of medical modalities include a blood vessel X.
26. The diagnostic network of claim 25, comprising at least one medical modality of an x-ray imaging system, an x-ray CT scanner, and a magnetic resonance imaging system. 27. A plurality of systems including the plurality of distributed test units, the master distributed test unit, the network, and the system monitor unit are provided, and the networks of the plurality of systems are connected to each other. 25. The diagnostic network system according to claim 24, wherein information is transmitted between the mutual systems in at least one direction. 28. A diagnostic network system for communicating with a plurality of devices, the plurality of distributed test units individually communicating with associated devices of the plurality of devices, and the plurality of distributed tests. A network for communicating information between the units; and a system monitor unit for communicating with the plurality of programmable distributed test units through the network, the system monitor unit comprising the plurality of programmable distributed test units. A diagnostic network system configured to program each one to function in a selected manner and to collect information obtained by said plurality of programmable distributed test units from said plurality of devices as pre-programmed. 29. Each of the plurality of distributed test units is a standardized controller unit programmed by the system monitor unit, and is controlled by the programmed controller unit and is one of the plurality of devices. 29. The diagnostic network system of claim 28, comprising: a sample control module adapted to communicate with the device. 30. The diagnostic network system according to claim 29, wherein said network comprises an optical network connecting said plurality of distributed test units to one another. 31. The diagnostic network system of claim 29, wherein said network comprises an optical network in which said plurality of programmable distributed test units are connected in series in a loop. 32. One of the plurality of programmable distributed test units is a master distributed test unit,
The system monitor is configured to communicate with the remaining plurality of programmable distributed test units through the master distributed test unit, and the order of transmitting information on the network is determined by the master distributed test unit. 29. The diagnostic network system of claim 28, adapted to start and end at a unit. 33. Each of said plurality of programmable distributed test units receives information from an upstream programmable distributed test unit, and selects a portion of the received information into said one programmable distributed test unit. 32. The diagnostic network system of claim 31 including means for relaying to a downstream programmable distributed test unit with information generated by the unit. 34. The plurality of devices have test locations for diagnosing the function of each device, and each of the plurality of programmable distributed test units is associated with a function of each of the devices at the test location. 30. The diagnostic network system according to claim 29, comprising means for monitoring information. 35. The plurality of devices have test locations for diagnosing the function of each device, and each of the plurality of programmable distributed test units relates to the function of each device at the test location. 30. The diagnostic network system according to claim 29, further comprising means for controlling the value at the test position so that the control amount is maintained at a predetermined value. 36. The information transmitted from the system monitor unit to the programmable distributed test unit includes a device control command, and the control means controls the device by controlling the device according to the device control command. 36. The diagnostic network system according to claim 35, further comprising means for holding the control amount at a position at a value specified by the device control instruction. 37. The diagnostic network system according to claim 28, wherein the system monitor unit includes means for maintaining, for the plurality of devices, performance data optimal for a user of the plurality of devices as a system. 38. A means for sampling data from a test location; means for controlling components connected to the test location based on program commands; means for receiving the program commands from an external control unit; Means for communicating with a fiber optic network for data and said program commands. 39. A standardized controller unit programmed by a system monitor unit, and a sample control module controlled by the programmed controller unit and adapted to communicate with a corresponding distributed test unit. Distributed test unit. 40. The distributed test unit according to claim 38, wherein the control unit is a system monitor provided in a diagnostic network system. 41. The distributed test unit according to claim 38, further comprising self-diagnosis means for performing self-diagnosis. 42. The distributed test unit according to claim 38, wherein said control unit is a notebook computer. 43. An automated diagnostic method using a network of distributed test units, the distributed test unit coupled to components of a diagnostic system to diagnose and solve operational problems, comprising: a. . Storing a previous operational problem of the diagnostic system and a previous solution to the operational problem in a database; b. Using the distributed test unit to sample data from test locations of appropriate components of the diagnostic system; c. Comparing said sample data to said stored previous operational problem using an automated expert system to identify a potential cause of said operational problem; d. Iteratively analyzing the identified scattered causes by performing a test procedure to determine whether the sample data matches any of the identified potential causes; e. Outputting a suggested action based on the repeated analysis. 44. The method of claim 43, further comprising using the distributed test unit to collect additional data from the test location that may be required to perform the test procedure. 45. The diagnostic of claim 43, further comprising prioritizing the iterative execution of the test procedure based on a previous operational problem, a previous operational solution, and a predetermined selection criterion. Method. 46. The diagnostic method according to claim 43, further comprising outputting the suggested action using a multimedia format. 47. An automated diagnostic method for performing preventive maintenance of a diagnostic system with multiple components, comprising: a. Connecting a distributed test unit to a test location of each component of the diagnostic system; b. Sampling the data of each of the components from the test location using the distributed test unit; c. Storing said sample data in a database storing a plurality of predetermined data values representing optimal performance, previous service problems, and previous service solutions; d. Comparing said sample data to said predetermined data value using an automated expert system to determine whether said diagnostic system is operating within said predetermined data value range; e. Identifying a potential cause for sample data that does not fall within the predetermined value range; f. Iteratively analyzing the identified scattered causes by performing a test procedure to determine whether the sample data matches the identified potential causes; g. Once all wrong causes are identified, outputting a corrective action procedure. 48. The diagnostic of claim 47, further comprising the step of prioritizing the iterative execution of the test procedure based on a previous operational problem, a previous operational solution, and predetermined selection criteria. Method. 49. The diagnostic method according to claim 47, further comprising the step of outputting the guidance information and the corrective action procedure in a multimedia format.