WO2011105259A1

WO2011105259A1 - Medical device system

Info

Publication number: WO2011105259A1
Application number: PCT/JP2011/053226
Authority: WO
Inventors: 隆齊藤; 雄吾小泉; 大山　雅英; 宏玉井
Original assignee: オリンパスメディカルシステムズ株式会社
Priority date: 2010-02-24
Filing date: 2011-02-16
Publication date: 2011-09-01

Abstract

A medical device system is provided with: a pair of connection units which are respectively provided to devices used for analysis or treatment and which are connected to transfer paths for connecting the devices; and first switching units which are respectively provided to the devices, control the connection between the pair of connection units provided to the devices, and form a bus network consisting of the devices. The system facilitates the replacement and addition of devices and enables reliable communications.

Description

Medical equipment system

The present invention relates to a medical device system, and more particularly to a medical device system that performs observation and / or treatment of living tissue by combining an endoscope, a video processor, a light source device, an electrosurgical device, and the like.

In the medical field, various medical device systems have been proposed in which an endoscope is inserted into a living body for observation, and further treatment is performed by combining an electrosurgical device or the like.

In such a medical device system, a desired function may be realized by combining several devices.

For example, in Japanese Patent Application Laid-Open No. 2004-33755 (hereinafter referred to as Document 1), a high-intensity light source and a CCU (camera control unit) are connected to enable endoscopic observation by adjusting the intensity of light output. A medical device system is shown. When the devices are combined in this way, bus-type communication may be used for the purpose of simplifying the connection. In the invention of Document 1, the high-intensity light source and the CCU are connected using a digital communication bus.

Also, Japanese Patent Laid-Open No. 2000-316864 (hereinafter referred to as Document 2) discloses a medical device system in which more devices are connected by a data transfer bus inside an image processing device.

In the invention of Document 1, the high-intensity light source and the CCU are coupled to the bus by a bus interface, and the light source device and the CCU cannot be exchanged. Also in the invention of Document 2, each device is directly connected to the data transfer bus, and the combination of devices cannot be changed by replacing each device or adding a new device.

Also, multiple devices of the same type may be connected in the system. Even in this case, the devices of Documents 1 and 2 cannot detect that a plurality of devices of the same type are connected, and can recognize this even if a wrong connection occurs between devices. Can not. Therefore, it is impossible to notify the user that a connection change is necessary for such an erroneous connection. Furthermore, in such a case, the same type of device may transmit at the same timing, and the communication line may not operate at all.

Also, a device having a circuit termination function required for a bus network may be connected to the network. In this case, if the connection order of such devices is not appropriate between devices, communication may not be performed normally. In addition, a device having a switch for turning on and off the circuit termination function may be connected to a network, or a termination resistor may be connected to the network. Even in these cases, transmission / reception may not be performed normally due to a misconfiguration on the network when the apparatus is installed.

Also, even if a device having a circuit termination function is connected to the network, if the power of the device is turned off, the circuit termination function may not operate and communication may not be performed normally.

The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a medical device system capable of facilitating the exchange and addition of devices and enabling reliable communication.

A medical device system according to an aspect of the present invention is provided in each of a plurality of devices used for diagnosis or treatment, and a pair of connection units connected to a transmission path that connects the devices to each other; A first switching unit that is provided in each of the plurality of devices, and controls a connection between the pair of connection units provided in each device to form a bus network by the plurality of devices.

1 is a block diagram showing an overall schematic configuration of a medical device system according to an embodiment of the present invention. The block diagram which shows the specific structure of the communication control block 1 between apparatuses of each apparatus. FIG. 2 is a block diagram showing an example of a specific configuration of

termination detection circuits

206A and 206B and an example of a specific configuration of a network error detection circuit 209. The timing chart for demonstrating control of CPU210 when there exists a change of a network structure. The flowchart for demonstrating communication of each apparatus on a network. Explanatory drawing for demonstrating the display of error information. The flowchart which shows the error detection process at the time of apparatus ID duplication in an own apparatus. The flowchart which shows the return process from the error by apparatus ID duplication in an own apparatus. The flowchart which shows the error detection process at the time of apparatus ID duplication in another apparatus, or the time of circulation connection. The flowchart which shows the return process from the error at the time of apparatus ID duplication in other apparatuses, or a circulation connection. The flowchart which shows the error detection process at the time of cluster duplication. The flowchart which shows the return processing from the error at the time of cluster duplication.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing an overall schematic configuration of a medical device system according to an embodiment of the present invention.

The medical device system shown in FIG. 1 employs a chain connection in which each device is connected by an inter-device cable, and performs communication between devices by adopting a configuration in which the inter-device cables are connected within each device. A bus type connection is adopted as the network form.

In the example of FIG. 1, an endoscope video processor 110, a light source device 120, an electric scalpel device 130, an ultrasonic coagulation / cutting device 140, a washing machine 150, and a scope shape recognition device 160 (hereinafter referred to as a device) 110-160)).

The endoscope video processor 110 is connected to the endoscope scope 100. The endoscope scope 100 outputs an image signal of an observation image in the patient body. The image processing unit 12 of the endoscope video processor 110 performs predetermined image processing on the image signal from the endoscope scope 100 and then outputs the image signal to the combining unit 13.

The endoscope video processor 110 is provided with a keyboard 104 and a panel 103 on which various switches are arranged for a user to access the endoscope video system. The CPU 2-110 in the endoscope video processor 110 performs various processes according to the stored contents of the nonvolatile memory 3-110. For example, the CPU 2-110 generates characters and the like to be superimposed on the observation image based on the operation of the keyboard 104 and the panel 103, and outputs them to the synthesis unit 13. The combining unit 13 superimposes characters and the like from the CPU 2-110 on the observation image, and then outputs them to the monitor 105. In this way, various displays including the observation image are performed on the display screen of the monitor 105.

Further, as will be described later, the CPU 2-110 can display a warning display regarding the device connection status on the monitor 105 to the user.

The light source device 120 can supply illumination light to the endoscope scope 100. The light source device 120 can control the amount of light supplied to the endoscope scope 100.

The electrosurgical device 130 connected to the network is a treatment machine for incising the skin of the body, the ultrasonic coagulation and incision apparatus 140 is a treatment machine for incising the skin of the human body, and the cleaning machine 150 is the endoscope used. The scope scope 100 is for cleaning, and the scope shape recognition device 160 recognizes the shape of the endoscope scope 100 inserted into the body.

The devices 110 to 160 connected to the network are connected to each other by

connectors

4A and 4B. That is, the connector 4B provided in the endoscope video processor 110 is connected to the connector 4A of the light source device 120 via the inter-device cable, and the connector 4B of the light source device 120 is connected to the connector of the electric female device 130 via the inter-device cable. Connected to 4A. Similarly, the devices 130 and 140, the devices 140 and 150, and the devices 150 and 160 are connected to each other by

connectors

4B and 4A via the respective devices.

In other words, in the present embodiment, by sequentially connecting the

connectors

4A and 4B in the form of a chain using inter-device cables, it is possible to easily replace, add or change the devices.

These devices 110 to 160 connected to the network include an inter-device communication control block 1-110 to 1-160 (hereinafter referred to as inter-device communication control block 1), and CPUs 2-110 to 2-160 (representatively). Hereinafter, representatively referred to as CPU 2) and nonvolatile memories 3-110 to 3-160 (hereinafter, representatively referred to as nonvolatile memory 3) are provided.

In the present embodiment, the inter-device cables can be connected within the inter-device communication control block 1 of each device. That is, a network adopting a bus connection as a network form is constructed by the network bus 5 formed by the inter-device cables and the wiring in each device. The inter-device communication control block 1 of each device performs communication control, termination control, network error detection, and the like in bus network communication.

As described above, by adopting a bus connection as the network connection form, in this embodiment, it is possible to perform inter-device communication by serial communication such as FlexRay, CAN, ARCNET, and Ciclink.

The CPU 2 provided in each device controls each part of each device and controls the network. The CPU 2 in each device is connected to the inter-device communication control block 1 in each device, and each inter-device communication control block 1 is connected to the network bus 5 via the

connectors

4, 4A, 4B.

Note that the dimming control unit 23 and CPU 2-120 of the light source device 120 and the image processing unit 12 of the endoscope video processor 110 are connected via a cable 7 and a connector. The CPU 2-120 of the light source device 120 controls the dimming control unit 23 on the basis of information obtained through network communication and a control signal from the image processing unit 12 of the endoscope video processor 110, so that the endoscope scope 100 can be controlled. Controls the amount of illumination light to be supplied.

Further, each of the devices 110 to 160 is equipped with a non-volatile memory 3 and is connected to the CPU 2 in each device to store the log information and various settings.

FIG. 2 is a block diagram showing a specific configuration of the inter-device communication control block 1 of each device. FIG. 2 shows the inter-device communication control block 1 of any two devices among the devices 120 to 160 in FIG. For example, the block 200 is an inter-device communication control block 1-130 of the electric knife device 130, and the block 300 is an inter-device communication control block 1-120 of the light source device 120.

Note that the

connectors

200A and 300A in FIG. 2 correspond to the connector 4A of each device in FIG. 1, and the

connectors

200B and 300B correspond to the connector 4B of each device in FIG. Since the configurations of the

blocks

200 and 300 are the same, the same components are denoted by the same reference numerals, and only one block 200 will be described.

As shown in FIG. 2, in the block 200, the connector 200A and the connector 200B can be connected by a wiring 201A, a termination switching relay 202A, a wiring 203, a termination switching relay 202B, and a wiring 201B. By electrically connecting the

connectors

200A and 200B to each other, as described above, a bus-type network can be configured even in the case of chain connection.

Connectors

200A and 200B are connected to

termination detection circuits

206A and 206B via

path switching relays

205A and 205B, respectively. The

end detection circuits

206A and 206B can detect whether or not the

connectors

200A and 200B are connected to the inter-device communication control block 1 of other devices via unillustrated inter-device cables. Yes.

When the

termination detection circuits

206A and 206B detect that other devices are connected to the

connectors

200A and 200B, the termination detection relays 202A and 202B connect the

wirings

201A and 203 or the wiring 201B and the wiring 203, respectively. A termination detection signal for output is output. Further, when the

termination detection circuits

206A and 206B detect that no other device is connected to the

connectors

200A and 200B, respectively, the termination switching relays 202A and 202B are connected to the wiring 201A and the termination resistor 204A, and the wiring 201B. And a termination detection signal for connecting the termination resistor 204B. The termination detection signals from the

termination detection circuits

206A and 206B are also supplied to the network error detection circuit 209 and the CPU 210.

For example, in the example of FIG. 1, the

connectors

4A and 4B of the devices 120 to 150 are connected to each other, but the connector 4B of the scope shape recognition device 160 is not connected to other devices. Accordingly, the termination switching relay 202A of the scope shape recognition device 160 connects the

wirings

201A and 203, and the termination switching relay 202B connects the wiring 203 and the termination resistor 204B.

In this way, the termination detection relays 202A and 202B are controlled on the network by determining whether or not the

termination detection circuits

206A and 206B need to implement termination resistors that enable stable communication in the bus-type connection. This makes it possible to automatically place the termination resistor at the correct position.

The

path switching relays

205A and 205B connect the

connectors

200A and 200B to the

termination detection circuits

206A and 206B when the apparatus is turned on, and connect the

connectors

200A and 200B when the apparatus is turned off. Thus, when the apparatus is turned off, the

connectors

200A and 200B are connected regardless of the state of the termination switching relays 202A and 202B, and a signal is passed between the

connectors

200A and 200B.

For example, in the example of FIG. 1, when only the power supply of the cleaning machine 150 is off, the

connectors

4A and 4B of the cleaning machine 150 are through, and the ultrasonic coagulation / cutting device 140 is not connected to the cleaning machine 150 as a network configuration. This is equivalent to the direct connection between the scope shape recognition device 160 and the scope shape recognition device 160, and the terminal resistance provided in the scope shape recognition device 160 can be made effective. Therefore, even when there is a power-off device among the devices connected to the network, it is possible for the terminal resistor to effectively act and perform communication.

The CPU 210 controls each part in the block 200. The wiring 203 is connected to the communication driver 212. The communication driver 212 is controlled by the communication controller 211 to control the physical layer of the network. The communication controller 211 exchanges data with the CPU 210 and controls communication between the own apparatus and another apparatus. The communication controller 211 has a function of recognizing an apparatus ID.

The

connectors

200A and 200B are connected to each other by a wiring 208, and the wiring 208 is connected to a network error detection circuit 209. A network error signal supplied from the outside is supplied to the network error detection circuit 209 via the wiring 208. Further, a network error signal from the CPU 210 is sent out from the wiring 208 via the network error detection circuit 209. The network error signal includes network error information indicating that the network having the bus structure has a loop structure.

The network error detection circuit 209 generates a status signal indicating the network status based on the termination detection signals and network error signals from the

termination detection circuits

206A and 206B, and outputs them to the CPU 210.

The termination detection circuit 206A generates a termination detection signal indicating that the

connectors

200A and 300B are connected to each other by connecting the

connectors

200A and 300B of the

blocks

200 and 300 in FIG.

FIG. 3 is a block diagram showing an example of a specific configuration of the

termination detection circuits

206A and 206B that perform such an operation and an example of a specific configuration of the network error detection circuit 209. In FIG. 3, the same components as those of FIG. Note that the block 200 and the block 300 in FIG. 3 have the same configuration, and the same components are denoted by the same reference numerals and only the block 200 will be described.

2 is configured by a resistor 206A1 and transistor switches (TR-SW) 206A2 and 206A3 in FIG. The resistor 206A1 is a pull-up resistor. When the connector 200A is not connected to the connector of another device, the transistor 206A2 is supplied with the voltage from the resistor 206A1 at the base, and the low level (hereinafter referred to as the output terminal). ) (L level) is output.

In FIG. 3, the termination detection circuit 206B shown in FIG. 2 includes a resistor 206B1 and transistor switches (TR-SW) 206B2 and 206B3. The resistor 206B1 is a pull-down resistor, and the transistor switch 206B2 is configured such that when the connector 200B is not connected to a connector of another device, the voltage from the resistor 206B1 is supplied to the base and the L level termination detection is performed from the output terminal. Output a signal.

When the connector 200A is connected to the connector 300B of another device, the transistor switch 206A2 is supplied with a voltage based on the resistors 206A1 and 206B1 to the base, and is at a high level (hereinafter referred to as H level) from the output terminal. Outputs the end detection signal. Similarly, when the connector 200B is connected to the connector 300A of another device, the transistor switch 206B2 is supplied with the voltage from the resistors 206B1 and 206A1 to the base, and outputs an H level termination detection signal from the output terminal. Output.

The termination detection signal from the transistor switch 206A2 is supplied to the termination switching relay 202A and also to the CPU 210 via the transistor switch 206A3. The termination detection signal from the transistor switch 206B2 is supplied to the termination switching relay 202B and also to the CPU 210 via the transistor switch 206B3.

The termination switching relays 202A and 202B connect the

wirings

201A and 201B and the wiring 203 by an H level termination detection signal, and connect the

wirings

201A and 201B and the

termination resistors

204A and 204B by an L level termination detection signal.

The network error detection circuit 209 in FIG. 2 includes an OR circuit 2091, an AND circuit 2092, a transistor switch (TR-SW) 2093, and an open collector circuit 2094 in FIG.

A wire 208 is commonly connected to the

connectors

200A and 200B, and a network error signal is transmitted by the wire 208. The network error signal is generated from any device on the network including its own device. The network error signal is generated, for example, when there are devices with duplicate IDs on the network, when a circular connection occurs, or when cluster overlap occurs.

That is, when the CPU 210 detects a network error by detecting the communication controller 211 or the like, the CPU 210 gives a detection result to the open collector circuit 2094. When the CPU 210 informs that a network error has occurred, the open collector circuit 2094 sets the network error signal of the wiring 208 to the L level. As described above, when detecting a network error, the CPU 210 sets the wiring 208 to L level, and when the error is resolved, sets the wiring 208 to Hi-Z.

In the present embodiment, when a network error is detected, the CPU 210 invalidates transmission / reception data for a certain period. Furthermore, in this embodiment, transmission / reception data can be invalidated for a certain period not only when a network error is detected but also when an abnormal termination condition occurs. Thereby, it is possible to prevent the processing based on invalid data from being performed when a network or termination abnormality occurs. In the present embodiment, as will be described later, a return process can be automatically performed for a network abnormality and a termination abnormality.

The termination detection signals from the transistor switches 206A2 and 206B2 are also given to the OR circuit 2091. The OR circuit 2091 has an L-level termination state indicating that the termination state is abnormal when a termination detection signal indicating that the connector of another device is not connected to any of the

connectors

200A and 200B is given. The signal is output to the AND circuit 2092.

The network error signal is also given to the AND circuit 2092. The AND circuit 2092 outputs an L level error signal only when at least one of the termination state signal and the network error signal is at the L level. The output of the AND circuit 2092 is supplied to the CPU 210 via the transistor switch 2093.

Next, the operation of the embodiment configured as described above will be described with reference to FIGS.

The medical device system according to the present embodiment employs a bus network, and devices on the network communicate with each other in cooperation. Each device connected to the network bus 5 uses a protocol such as FlexRay, CAN, etc., and each node occupies the bus at a predetermined timing, or priorities when transmission conflicts are determined. Communicate after arbitrating so that multiple nodes do not transmit at once. That is, when each device on the network is activated, each device recognizes each device connected to the network bus 5 and realizes a predetermined function in response to a request from the user.

For example, the endoscope video processor 110 sets internal parameters according to the type of the endoscope scope 100 connected to the processor after the apparatus is activated, and performs signal processing of the endoscope image in the image processing unit 12. . The endoscope video processor 110 controls the light source device 120 by a communication signal via the network bus 5 and a control signal transmitted through the cable 7. The endoscope video processor 110 transmits light source control information corresponding to the connected endoscope scope 100 to realize dimming control.

For example, even when the user requests a transition from the normal observation mode to the NBI (narrowband light) observation mode, the endoscope video processor 110 performs communication via the network bus 5 to Control the amount of light and the aperture state.

The electric knife device 130 performs energy control by using the network bus 5 and transmitting and receiving data necessary for the electric knife. The ultrasonic coagulation / cutting device 140 uses the network bus 5 to perform energy control by transmitting and receiving data necessary for ultrasonic output. The cleaning machine 150 performs cleaning function control by using the network bus 5 and transmitting and receiving data necessary for the cleaning machine. The scope shape recognition device 160 performs shape recognition control by using the network bus 5 and transmitting and receiving data necessary for scope shape recognition. In addition, the electric knife 130 and the ultrasonic coagulation / cutting device 140 communicate with each other via the network bus 5 and transmit information indicating whether the output cooperation function is supported, thereby confirming that the output cooperation function is supported. In some cases, the output linkage function is enabled and the user is notified that the function is usable. If not, notify that the function cannot be used with the current combination.

Further, the endoscope video processor 110 transmits time information to the electric scalpel device 130, the ultrasonic coagulation / cutting device 140, the washing machine 150, and the scope shape recognition device 160 via the network bus 5, and the endoscope Match the time as a system. In addition, information such as operation history and error log stored in the nonvolatile memory 3 mounted in each apparatus is also collected in the endoscope video processor 110 by communication via the network bus 5.

From the keyboard 104 and the panel 103 connected to the endoscope video processor 110, patient information input, observation mode switching, and video processing switching are performed, and the user selection information is sent to the monitor 105 connected to the endoscope video processor 110. Confirm with.

In the present embodiment, each device is connected in a chain, and

wiring

201A, 201B, 203 is provided in the inter-device communication control block 1 in each device, thereby forming a network that is bus-type connected. Yes.

In the present embodiment, since the termination resistor can be automatically mounted, network communication is not disabled even when a device on the network is removed or added.

(Termination control)
As shown in FIGS. 2 and 3, the

termination resistors

204A and 204B necessary for the bus type connection are wirings 201A and 201B constituting the network bus 5 in the inter-device communication control block 1 by the termination switching relays 202A and 202B. It is connected with. Connection of

termination resistors

204A and 204B is controlled by

termination detection circuits

206A and 206B.

Termination detection circuits

206A and 206B detect whether or not

connectors

200A and 200B are connected to

connectors

300B and 300A of other devices, respectively, and control termination switching relays 202A and 202B based on the detection results. When the

connectors

200A and 200B are connected to the

connectors

300B and 300A, the

termination detection circuits

206A and 206B control the termination switching relays 202A and 202B to connect the

wirings

201A and 201B with the wiring 203. Further, when the

connectors

200A and 200B are not connected to the connectors of other devices, the

termination detection circuits

206A and 206B determine that the device is the terminal and control the termination switching relays 202A and 202B, The

wirings

201A and 201B are connected to the terminating

resistors

204A and 204B, respectively.

For example, in the state of FIG. 1, terminal resistors are connected in the inter-device communication control block 1-110 of the endoscope video processor 110 and the inter-device communication control block 1-160 of the scope shape recognition device 160. In this state, for example, the inter-device cable between the washing machine 150 and the scope shape recognition device 160 is removed from the

connectors

4B and 4A. Then, the termination detection circuit 206B of the inter-device communication control block 1-150 of the cleaning machine 150 detects that the connector 4B is disconnected, and connects the wiring 201B and the termination resistor 204B to the termination switching relay 202B. . As a result, the terminating resistor is automatically connected to the cleaning machine 150, and network communication is possible.

In the connected state of FIG. 1, only the ultrasonic coagulation / cutting device 140 is turned off. In this case, the

path switching relays

205A and 205B of the inter-apparatus communication control block 1-140 of the ultrasonic coagulation / cutting device 140 connect the connectors 200A (4A) and 200B (4B) to each other by the wiring 207. Thereby, the connector 4B of the electric scalpel device 130 and the connector 4A of the cleaning machine 150 are connected through the ultrasonic coagulation / cutting device 140. As a result, even when any device on the network is turned off, the bus type connection is maintained between the other devices, and the termination detection is automatically performed.

As described above, in the present embodiment, since it has a function of automatically setting the termination resistance, the device can be arranged at any position on the network without being aware of the termination resistance. It is possible to incorporate and remove a new device from an existing system without being aware of the termination resistance. Note that whether to enable or disable the function of automatically setting the termination resistor may be controlled by a user operation. In this case, it is also possible to display a menu display for selecting whether the function is valid or invalid on the monitor 105 so that the user can select it.

By the way, when there is a change in the network configuration, it is necessary to rebuild the network. Therefore, the CPU 210 detects, for example, that a device has been newly connected to the network or that the connection of the termination resistor has been changed after startup, based on termination detection signals from the

termination detection circuits

206A and 206B.

FIG. 4 is a timing chart for explaining the control of the CPU 210 when the network configuration is changed. FIG. 4 shows the network error signal, the termination detection signal, and the control of the CPU 210.

Now, for example, it is assumed that all devices are operating normally in the state of FIG. In this case, the CPU 210 performs normal communication, and normal communication via the network bus 5 is performed between the devices. Here, it is assumed that any device on the network is disconnected from the network. The communication controller 211 of the inter-device communication control block 1 of each device detects that the network state has become abnormal and generates an L level network error signal. Conventionally, when such a network error is detected, a CPU that controls network communication may recognize the disconnection and perform error processing. In order to restore communication to such an error process normally, work by the user is generally required.

In contrast, in the present embodiment, when the device is disconnected from the network, the terminal detection circuit 206A (206B) of the device connected to the device generates an L-level terminal detection signal. This termination detection signal is given to the termination switching relay 202A (202B), and the wiring 201A (201B) is connected to the termination resistor 204A (204B).

Furthermore, the end detection signal is also supplied to the CPU 210. When the CPU 210 detects that the network configuration has changed due to the change in the termination detection signal, the CPU 210 invalidates the communication data for a predetermined period. As shown in FIG. 4, the termination switching relay 202A (202B), the

path switching relays

205A and 205B, and the like operate during this predetermined period, and termination switching, path switching, and the like are performed. Then, when a predetermined period has elapsed from the change in the termination detection signal, the CPU 210 determines that normal communication is possible and returns to normal communication.

As described above, in the present embodiment, after detecting that the network configuration has changed due to the change in the termination detection signal, the communication process and the warning process are performed after a certain delay time.

(Network error control)
The CPU 210 in the inter-device communication control block 1 of each device can perform communication control given the information on the network error detected by the communication controller 211. However, for example, when another device having the same ID as that of the own device is connected to the network, it may be impossible to detect a network error in the own device. Therefore, in this embodiment, when each device detects a network error, it outputs an L level network error signal. Network error signals are communicated to all devices.

For example, a network error signal indicating that the network is in a loop connection instead of a bus type connection or an error state as a protocol is transmitted to each device via the

connectors

4A and 4B. The network error detection circuit 209 of each device receives the network error signal and transmits it to the CPU 210. Thus, the CPU 210 grasps the network error status.

FIG. 5 is a flowchart for explaining the communication of each device on the network, and shows a flow such as activation of each device, error detection and error recovery processing. FIG. 5 shows an example in which the endoscope video processor 110, the light source device 120, and the electric knife device 130 shown in FIG. 1 are connected to another electric knife device (not shown) on the network.

FIG. 5 shows an example in which a protocol (for example, FlexRay) adopting a time trigger method for transmitting data in accordance with a schedule determined in the network is employed. The communication timing is defined so that each device in the network transmits data within a certain time (communication cycle). In order for each device on the network to use a common communication cycle, each device needs to establish clock synchronization. A device ID is assigned to each device on the network according to the type of device. The assigned device ID is a unique value in the device. Examples include a built-in board serial number, a device serial number, an Ethernet (registered trademark) MAC address, a manufacturing date number, a manufacturing location number, and a random number. It is done.

Each device may hold device ID copy data, which is device ID backup data, for device ID maintenance. Also, each device may hold a plurality of copy data, and either device ID or copy data may be stored. Even if such data is damaged, the damaged data may be restored. Hereinafter, an example in which two pieces of copy data are held inside the apparatus in addition to the apparatus ID will be described as an example of the apparatus ID damage detection and restoration method.

(Device ID damage detection and data restoration method)
First, the value of the master data (one) of the device ID is compared with the value of the copy data (two) to determine whether or not all the data match. Here, when all the data match, it is determined that the device ID and its backup data are not damaged.

Next, when it is determined in the above determination that one data is different from the remaining two data, one data that does not match the other data is determined as damaged data.

Then, data restoration is attempted by overwriting the data determined to be the above-mentioned damaged data with two matching data.

If it is determined in the above determination that the master data of the device ID and all of the two copy data are different from each other, it is determined that the data cannot be restored, and this is notified to the user as an error. good.

In the above example, an example in which two pieces of copy data are held has been described, but three or more pieces of copy data may be held.

Now, it is assumed that the endoscope video processor 110, the light source device 120, and the electric knife device 130 are powered on. Each device 110 to 130 establishes clock synchronization after being activated, and transitions to a normal state in which data can be transmitted and received (hereinafter referred to as normal active).

The transmission / reception timing of each device is managed according to the device ID assigned to each device. Each device transmits within the time assigned to the device ID assigned to each device, and the device assigned with a device ID other than the device ID to be transmitted receives data. Each device determines that the communication path is normal if there is no error in the received data, and determines that the system is in error if there is an error in the data.

When transitioning to normal active, communication is performed among the endoscope video processor 110, the light source device 120, and the electric knife device 130. 5, S1, S2,... Indicate communication slots. In the communication slot S1, the endoscope video processor 110 transmits and other apparatuses receive. In the communication slot S2, the light source device 120 transmits and other devices receive. In the communication slot S3, the electric knife device 130 transmits and the other devices receive.

Here, it is assumed that during the period of the communication slot S4, power is supplied to another electric knife device connected to the network. Other electric knife devices have the same device ID as the electric knife device 130. Other electrosurgical units establish synchronization after activation and transition to normal active. Thereby, another electric knife apparatus can communicate with the communication slot S5 on the network.

In the communication slots S5 and S6, the other electric knife devices receive data. However, the communication slot S7 becomes a transmission slot of another electric knife device together with the electric knife device 130. Thereby, in the communication slot S7, the electric knife device 130 and other electric knife devices simultaneously transmit data.

Thereby, the endoscope video processor 110 and the communication controller 211 of the light source device 120 detect a syntax error and recognize that a network error has occurred by an error detection process described later (communication slot S7). The CPU 210 controls the open collector circuit 2094 to transmit an L level network error signal on the network. The network error signal is supplied to each device, and the network error detection circuit 209 of each device transmits the L level network error signal to the CPU 210. As a result, the CPU 210 resets the communication driver 212 and stops network communication.

The CPU 2-110 of the endoscope video processor 110 is notified that a network error has occurred from the inter-device communication control block 1-110. The CPU 2-110 performs error display control for the synthesis unit 13. Thereby, the synthesizing unit 13 performs the Buwei superimposition process, displays the error information on the display screen of the monitor 105, and allows the user to recognize that there is an erroneous connection on the system.

FIG. 6 is an explanatory diagram for explaining the display of such error information.

The monitor 105 can display not only an endoscope image but also error information. FIG. 6 shows an example in which error information indicating that a device with a duplicate device ID exists on the network is displayed on the display screen of the monitor 105. In the example of FIG. 6, it is shown that there are two treatment devices A and B of the same type on the network. The CPU 2-110 can also alert the user to the occurrence of a network error by lighting control of the error alerting LED 110a provided in the device casing of the endoscope video processor 110.

Note that the CPU 2 can display various information on errors on the system and errors in network communication on the monitor 105. For example, the CPU 2 can display warning information and setting information for the user such as error information, duplicated device information, bus termination information, bus connection information, and information regarding termination resistance settings.

Further, when a communication protocol such as FlexRay or CAN is adopted, the device ID can be changed via the network bus 5. Therefore, when an error based on a duplicated device ID is detected on the network, the error may be avoided by changing the setting of the device ID so that no duplicate ID occurs. In this case, the CPU 2 may display a selection display as to whether or not to change the device ID assignment on the monitor 105, and change the device ID based on a user instruction. FIG. 5 shows an example of this case.

Further, when the device IDs are duplicated, an error may be avoided by turning off the power of devices other than one device among the devices having the duplicated device IDs. In this case, the CPU 2 may cause the monitor 105 to display a selection display (see FIG. 6) for selecting a device number to turn off the power, and turn off the power of the device based on a user instruction. . Note that these user instruction operations can be performed using the keyboard 104 or the like.

When each device connected to the network detects an L-level network error signal, it performs a chip reset of the communication driver 212 in the device and stops communication. The endoscope video processor 110 that has set the network error signal to the L level stops transmission for a specified time (for example, 200 milliseconds), sets the network error signal to the H level, and communicates over the network via the communication driver 212. Is started (communication slot S8).

On the other hand, when another device connected to the network other than the endoscope video processor 110 detects the H level of the network error signal, it starts communication on the network via the communication driver 212. After communication is started in this way, network communication is started by a return process from an error described later (communication slot S9).

As described above, in the present embodiment, when a network error is detected, each device is connected to each device via the network until the error is resolved and a recovery process from the error is performed after a predetermined time of error detection. Does not send commands to.

Next, error detection processing and error recovery processing will be described with reference to FIGS. 7 to 12 show error detection processing or error recovery processing when FlexRay is adopted as a protocol on the network.

FIG. 7 is a flowchart showing an error detection process when the apparatus ID is duplicated in the own apparatus.

In step S11, the CPU 210 of the device-to-device communication control block 1 of each device determines whether or not the time from startup to start establishment of synchronization to transition to normal active is within 200 milliseconds. Next, in step S12, the CPU 210 determines whether or not the transition time from normal active to a state where data transmission / reception is stopped (hereinafter referred to as “holt”) is within 200 milliseconds. Further, the CPU 210 resumes communication and determines whether or not the conditions of steps S11 and S12 are satisfied again (step S13).

CPU 210 determines that an abnormality has occurred due to duplication of device IDs when all the conditions of steps S11 to S13 are satisfied (step S14). If any of the conditions in steps S11 to S13 is not satisfied, CPU 210 determines that an abnormality due to duplication of device ID has not occurred (step S15).

FIG. 8 is a flowchart showing a recovery process from an error due to device ID duplication in its own device.

First, when the CPU 210 determines in step S21 that the network error is a connection error due to duplication of network ID or the like, the CPU 210 performs chip reset of the communication driver 212 (step S22). Due to the chip reset, reconnection to the network is performed, transition to start-up, and transition to normal active (step S23). In step S24, the CPU 210 determines whether or not the transition from startup to normal active has been performed within 200 milliseconds. If the transition is not made within 200 milliseconds, it is determined that recovery from an error is possible, and system recovery is performed (step S26).

Further, the CPU 210 determines whether or not the transition is made to the halt within 200 milliseconds from the transition to the normal active (step S25), and even if the transition is not performed within 200 milliseconds, it is determined that the recovery is performed and the system is restored (step). S26).

FIG. 9 is a flowchart showing an error detection process at the time of device ID duplication or circulation connection in another device. The cyclic connection is a state in which the network is connected in a loop despite being connected by a bus connection.

In FlexRay, when an error other than a fatal error that transitions to a halt is detected, a transition is made from normal active to a state in which only reception is possible and transmission is impossible (hereinafter referred to as normal passive). Yes. Four errors (syntax error, content error, boundary reviolation, and transmission conflict) are defined as conditions for transitioning to normal passive.

In this embodiment, the CPU 210 detects an ID overlap or a circular connection by another node when detecting at least one of the following three conditions.

(1) When a syntax error occurs 3 times or more in 10 communication cycles (However, when there are multiple devices with the same ID in other nodes)
(2) If a content error occurs 3 times or more in 10 communication cycles,
(3) When slot boundary reviolation occurs 3 times or more in 10 communication cycles (when two clusters are combined)
The CPU 210 determines these conditions in steps S31 to S33. If any of the conditions is satisfied, the CPU 210 determines that a connection abnormality has occurred in step S34. If neither of the conditions is satisfied, the CPU 210 connects in step S35. Judge that no abnormality has occurred. The conditions (1) to (3) may be determined in any order.

FIG. 10 is a flowchart showing a recovery process from an error at the time of device ID duplication or circulation connection in another device.

First, when it is determined in step S41 that the network connection is abnormal, the CPU 210 sets the network error signal to L level for 200 msec and returns the network error signal to Hi-Z after 200 msec (steps S42 and S43).

Then, in step S44, the CPU 210 determines whether 500 milliseconds have elapsed since the transition to normal active. If 500 milliseconds have elapsed, it is determined that recovery from an error is possible, and system recovery is performed (step S46).

Further, even when 500 milliseconds have not elapsed since the transition to normal active, the CPU 210 determines whether or not the syntax error is 2 times or less in 10 communication cycles (step S45), and is 2 times or less. In step S46, it is determined that recovery from an error is possible.

FIG. 11 is a flowchart showing error detection processing when a cluster is duplicated. Note that cluster duplication is a state in which an active network is newly connected to a network to which the own apparatus is connected.

In the present embodiment, the CPU 210 detects cluster duplication when the above three conditions (1) to (3) or the following condition (4) are detected.

(4) When the network error signal becomes L level for 100 msec (when the above conditions (1) to (3) are detected in another node or the communication cable is connected in a circular manner)
The CPU 210 determines these conditions in steps S31 to S33 and S51. If any of the conditions is satisfied, the CPU 210 determines that a connection abnormality has occurred in step S34. If neither of the conditions is satisfied, the CPU 210 performs step S35. It is determined that no connection abnormality has occurred. The conditions (1) to (4) may be determined in any order.

FIG. 12 is a flowchart showing a recovery process from an error when a cluster is duplicated. The return process of FIG. 12 is different from the return process of FIG. 10 in that the process of steps S61 and S62 is adopted instead of the process of step S43.

That is, the CPU 210 determines in step S61 that there is an abnormality in the network, performs chip reset, and leaves the network (step S61). Next, when the network error signal becomes H level, the CPU 210 performs reconnection to the network (step S62).

Then, the CPU 210 determines whether 500 msec has elapsed from the transition to normal active or whether the syntax error is twice or less in 10 communication cycles (steps S44 and S45), and the system is restored. (Step S46).

Note that the CPU 210 restarts the return process from the beginning if the conditions (1) to (4) are met when the return is confirmed.

(effect)
The present embodiment has the following effects.

-By providing network wiring in a device having two types of connectors, it is possible to construct a medical device system based on a bus-type network without prescribing device connection.

-In a medical device system connected by a bus network, communication between devices is possible while transmission timing is managed according to the device ID.

In a medical device system connected by a bus network, devices can be removed from the network, and communication between devices via the network can be continued even if the system configuration changes.

-It is possible to detect duplication when there are a plurality of identical devices in a medical device system connected in a bus type network configuration.

-When there are a plurality of identical devices in a medical device system connected in a bus type network form, the result of detecting duplication can be notified to other devices by a communication protocol.

Further, the detection result can be displayed on the monitor or the user can be notified by displaying warning information on the front panel.

-When error information is received from another device in the network, communication can be stopped when duplication is detected.

-When error information is received from another device in the network, it is possible to continue network communication by detecting and recovering from duplication.

-When error information is received from other IDs in the network, network communication can be normally performed by performing error notification processing and return processing after receiving error information a plurality of times.

When receiving error information from another device in the network, the device that has received the error information can detect various connection states and process them with a certain delay time.

A medical device system that can alert the user to a system warning, and the user can return to a normal system by receiving warning information on a monitor or front panel and changing the system connection.

-When error information is received from another device in the network, or when error information is received by a network error signal, network communication can be stopped.

-With respect to detection of device ID duplication, it is possible to change the transmission timing by changing the device ID.

-This makes it possible to avoid network communication errors.

In this case, the user can change the device ID.

It can detect that it is placed at the end in the network.

It can notify the user that it has been detected that it is located at the end in the network.

-Since it can be detected that the terminal is placed at the end in the network, the terminal resistor can be automatically connected.

Since it is possible to detect that the terminal is placed at the end in the network, it is possible to select whether to automatically connect the terminal resistor.

-Network communication can be performed stably even when the power of devices in the network is off.

This application is filed on the basis of the priority claim of Japanese Patent Application No. 2010-39110 filed in Japan on February 24, 2010. The above-mentioned disclosure content includes the present specification, claims, It shall be cited in the drawing.

Claims

A pair of connection portions provided respectively in a plurality of devices used for diagnosis or treatment, and connected to a transmission path connecting the plurality of devices;
A first switching unit that is provided in each of the plurality of devices, and controls a connection between the pair of connection units provided in each device to form a bus network by the plurality of devices;
A medical device system comprising:
The first switching unit includes the first switching unit according to a state of electrical connection between one connection unit of the pair of connection units and a connection unit of any one of the plurality of devices. The medical device system according to claim 1, wherein the medical device system performs switching control of whether to connect the paired connection portions or to connect the one connection portion to a termination resistor.
A second switching unit that is provided in each of the plurality of devices and connects the pair of connection units of the device when the power of the device is off;
The medical device system according to claim 1 comprising:
A second switching unit that is provided in each of the plurality of devices and connects the pair of connection units of the device when the power of the device is off;
The medical device system according to claim 2 comprising:
An error detection unit that is provided in each of the plurality of devices and detects an error in the bus network;
A presentation unit for presenting an error detection result by the error detection unit;
The medical device system according to claim 1 comprising:
An error detection unit that is provided in each of the plurality of devices and detects an error in the bus network;
A presentation unit for presenting an error detection result by the error detection unit;
The medical device system according to claim 2 comprising:
An error detection unit that is provided in each of the plurality of devices and detects an error in the bus network;
A presentation unit for presenting an error detection result by the error detection unit;
The medical device system according to claim 3 comprising:
The error detection unit is capable of detecting the error based on data received by the own device, and transmitting error information detected by another device of the plurality of devices to detect the error. The medical device system according to claim 5, wherein detection is possible.
The error detection unit is capable of detecting the error based on data received by the own device, and transmitting error information detected by another device of the plurality of devices to detect the error. The medical device system according to claim 6, wherein detection is possible.
The error detection unit is capable of detecting the error based on data received by the own device, and transmitting error information detected by another device of the plurality of devices to detect the error. The medical device system according to claim 7, wherein detection is possible.
The bus network has transmission timings defined according to the types of the plurality of devices,
The error detection unit detects that a plurality of devices of the same type are connected to the bus network,
The medical device system according to claim 5, wherein the presenting unit performs display for selecting which of the plurality of devices of the same type is connected to the bus network or disconnected.
The bus network has transmission timings defined according to the types of the plurality of devices,
The error detection unit detects that a plurality of devices of the same type are connected to the bus network,
The medical device system according to claim 6, wherein the presenting unit performs display for selecting which of the plurality of devices of the same type is to be connected to the bus network or disconnected.
The bus network has transmission timings defined according to the types of the plurality of devices,
The error detection unit detects that a plurality of devices of the same type are connected to the bus network,
The medical device system according to claim 7, wherein the presenting unit performs a display for selecting which of the plurality of devices of the same type is connected to the bus-type network or disconnected.
The bus network has transmission timings defined according to the types of the plurality of devices,
The error detection unit detects that a plurality of devices of the same type are connected to the bus network,
The medical device system according to claim 8, wherein the presenting unit performs display for selecting which of the plurality of devices of the same type is to be connected to the bus network or disconnected.
The control unit according to claim 5, further comprising: a control unit that is provided in each of the plurality of devices, and that processes data flowing in the bus network as invalid for a predetermined period when an error in the bus network is detected by the error detection unit. Medical equipment system.
The control unit according to claim 8, further comprising: a control unit that is provided in each of the plurality of devices, and that processes data flowing in the bus network as invalid for a predetermined period when an error in the bus network is detected by the error detection unit. Medical equipment system.
The control unit according to claim 11, further comprising: a control unit that is provided in each of the plurality of devices, and that processes data flowing in the bus network as invalid for a predetermined period when an error in the bus network is detected by the error detection unit. Medical equipment system.
The controller is
16. The medical device system according to claim 15, wherein error processing for stopping communication by the bus network is not started at least during the predetermined period.
The controller is
The medical device system according to claim 16, wherein error processing for stopping communication by the bus network is not started at least in the predetermined period.
The controller is
18. The medical device system according to claim 17, wherein error processing for stopping communication by the bus network is not started at least during the predetermined period.