Data transmission method and system therefor

Abstract: A data transmission system for a vehicle includes a plurality of control systems installed on the vehicle, and a network bus connecting the plurality of control systems with each other for circulating a transmission right through the plurality of control systems to thereby perform transmission of a message between the plurality of control systems. According to a first aspect, each of the control systems starts transmitting data when it is detected that the transmission right is not generated or lost from the system, and continues transmitting the data when no collision of data transmitted from the present control system with data transmitted from the rest of the plurality of control systems, or when by mediation for avoiding the collision is detected, it is determined to continue data transmission. According to a second aspect, the maximum number of times of retransmission to be permitted is determined according to a type of failure in transmission identified, and the retransmission is performed so long as the number times of retransmission of the data does not exceed the maximum number of times of retransmission to be permitted. According to a fourth aspect, the message comprises a first response field for receiving a first acknowledging response output from a control system having received the transmission right, and a second response field for receiving a second acknowledging response output from a control system having received data.

Description: BACKGROUND OF THE INVENTION Field of the Invention This invention relates to a method of transmitting data and a system therefor between a plurality of electronic control units installed on an automotive vehicle via a common communication line connecting these electronic control units. Prior Art Conventionally, in performing mutual data transmission between a plurality of electronic control units (hereinafter referred to as the "ECU's" installed on an automotive vehicle via a common communication line (hereinafter referred to as "the network bus") connecting the ECU's, a token passing method is employed for circulating a transmission right round the ECU's in a predetermined sequence to permit an ECU having received the transmission right to send out data to the network bus. When a data transmission system employing the token passing method is started, the following methods are conventionally known for initially rendering (i.e. generating) the transmission right to one of the ECU's: (1) Fixed ECU method of initially rendering the transmission right to a particular ECU determined in advance in a fixed manner. (2) Waiting method in which all the ECU's start transmitting data assuming that they are each initially rendered with the transmission right, stop transmitting data when collision of data occurs, and restart data transmission after waiting for predetermined waiting time periods set to the ECU's, respectively, repeatedly carrying out this procedure until no collision occurs, to thereby restrict an initial holder of the transmission right to one of the ECU's. However, the fixed ECU method suffers from a problem that if the particular ECU to which the transmission right is to be initially rendered is in failure, the transmission right cannot be produced for ever. With the waiting method as well, there is an inconvenience that it takes much time to generate the transmission right, and time is wastefully consumed before the ECU's start to cooperate as a network. On the other hand, in the data transmission system using the token passing method, it is a known technique to add broadcast data to a message for transmission to transfer the transmission right to the next ECU, as disclosed e.g. in Japanese Patent Publication (Kokoku) No. 1-58900. However, according to this conventional technique, the message data format is not constructed such that a sending end can confirm safe and accurate transfer of each of the transmission right and data, and hence there is room for improvement thereof to expedite the transmission. Further, Japanese Patent Publication (Kokoku) No. 1-57856 (hereinafter referred to as "the first prior art") discloses a technique that when data transmission is not successfully carried out, retransmission of data is performed upon the transmission right returning to the present ECU after having been transferred round the ECU's, taking into consideration the fact that if retransmission of the data is carried out immediately, there is a high possibility of failure thereof. Further, Japanese Provisional Patent Publication (Kokai) No. 62-159539 discloses a data transmission system (hereinafter referred to as "the second prior art") in which when transmission of the data is not successfully carried out, the data is retransmitted within a limit of a predetermined number of times, which number can be changed or set by another control system. According to the first prior art, the retransmission of data is performed only after the transmission right has been transferred round the ECU's once even if the immediate transmission of data might be successful (e.g. when failure of transmission was caused by a noise during transmission), which is an inconvenience to be eliminated for prompt completion of data transmission. Further, according to the second prior art, the retransmission of data is carried out immediately after failure thereof within the predetermined number of times set by the other control system. However, this number is not set by the sending end itself, and hence it is difficult to perform prompt reaction to failure of transmission. Further, in making a check as to whether connection between one member (ECU) and another (ECU) of the network is safely established, a special message is sent out from the one member for a response from the other, based on which it is determined whether the connection is safely established. When the special message is used, however, the data transmission and transfer of the transmission right cannot be performed while the special message is being sent out, which results in degraded transmission efficiency. Further, when the other member (ECU) goes faulty or disconnected from the network, the state of the connection is not certain until the check therefor is carried out again, and hence there is a possibility of continuing to transfer the transmission right to the ECU disconnected. European Patent Application EP-A-0 216 372 discloses a data bus system for vehicles, wherein a plurality of different users are able to communicate via a common data bus. The system provides the following features: a) the users are each connected with the data bus via a control station, b) the control stations have registers for storing data required or delivered by the affiliated users, c) the stations are permanently connected to the data bus for receiving data required by the affiliated user, d) the stations are sequentially connected to the data bus for sequentially sending data deliverd by the affiliated user, and e) the data handed over to the bus carry an identification sign. SUMMARY OF THE INVENTION It is a first object of the invention to provide a data transmission system for an automotive vehicle which is capable of enhancing data transmission efficiency by immediately generating a transmission right, i.e. initially rendering the transmission right to a sending end. To attain the first object of the invention, according to a first aspect of the invention, there is provided a data transmission system for a vehicle, including a plurality of control systems installed on the vehicle, and a network bus connecting the plurality of control systems with each other for circulating a transmission right through the plurality of control systems to thereby perform transmission of a message between the plurality of control systems and transmitter-receiver means for transmitting data to or receiving data from the rest of the plurality of control systems via the network bus. The data transmission system according to the first aspect of the invention is characterized in that each of the plurality of control systems comprises: collision-detecting means for detecting a collision of data transmitted from the transmitter-receiver means with data transmitted from any of the rest of the plurality of control systems; mediating means for performing mediation on the data transmitted from the transmitter-receiver means and having been detected to be collided with the data transmitted from any of the rest of the plurality of control system to direct the transmitter-receiver means to continue data transmission or stop the data transmission, for the purpose of avoiding the collision, monitor means for monitoring the transmission right; and control means for causing the transmitter-receiver means to start transmitting data when the monitoring means detects that the transmission right is not generated or lost from the system, and causing the transmitter-receiver means to continue transmitting the data when the collision-detecting means does not detect a collision of the data with data transmitted from the rest of the plurality of control systems, or when the mediating means directs the transmitter-receiver to continue data transmission. Preferably, the data transmission system further comprises transfer means for transferring the transmission right to a subsequent control system in a predetermined manner, when the control means controls the transmitter-receiver means to continue the data transmission until the data transmission is completed. Preferably, the mediating means compares the data transmitted from the transmitter-receiver means with the data received via the network bus from the rest of the plurality of control systems, bit by bit, based on the logic considering one of logical levels of transmission data as dominant, and the other of the logical levels of the transmission data as recessive, and directing the transmitter-receiver means to stop the data transmission when the data transmitted from the transmitter-receiver means and the data received from the network bus are different from each other. More preferably, the transfer means transfers the transmission right to the subsequent control unit by increasing an address representative of the each of the plurality of control systems incorporating the transfer means by a predetermined number. The above and other object, features, and advantages of the invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a block diagram showing the whole arrangement of a control system for an automotive vehicle according to an embodiment of the invention; Fig. 2 is a block diagram showing the arrangement of an electronic control unit appearing in Fig. 1; Fig. 3 is a circuit diagram showing details of a bus interface appearing in Fig. 2; Fig. 4a is a diagram showing a format of a message containing a data unit for transmission between electronic control units; Fig. 4b is a diagram showing a format of a message containing no data unit; Fig. 5 is a flowchart showing a program for initially generating a token (transmission right) when the token has not been generated or lost; Fig. 6a to Fig. 6d collectively form a timing chart which is useful in explaining a manner of mediation for settling contention for the transmission right, in which: Fig. 6a shows bit Nos.; Fig. 6b shows data transmitted from a node 1; Fig. 6c shows data transmitted from a node 2; and Fig. 6d shows logical levels on a bus; DETAILED DESCRIPTION The invention will described in detail with reference to drawings showing an embodiment thereof. Fig. 1 shows the whole arrangement of a control system for an automotive vehicle according to the embodiment comprising electronic control units (hereinafter referred to as "the ECU's") 1 to 5 connected with each other via a network bus 6. An ENG control ECU 1 controls operation of an engine in response to operation of an accelerator pedal operated by a driver of the vehicle, etc. An MISS control ECU 2 controls an automatic transmission of the vehicle according to the operating conditions of the engine. A TCS control ECU 3 detects a slip of driving wheels and controls an output torque of the engine. A suspension control ECU 4 controls a suspension (active suspension) system of the vehicle depending on the operating conditions of the engine. A brake control ECU 5 detects a slip of wheels and controls braking operation. These ECU's 1 to 5 are required to be permitted to mutually monitor control parameters and operating parameters detected by sensors, some of the sensors being collectively shown in Fig. 2, and hence are connected to each other by way of the network bus 6 for transmission of data necessitated by each other. Fig. 2 shows the arrangement of the ENG control ECU 1 which comprises a central processing unit (hereinafter referred to as "the CPU") 101, an input/output interface 104 connecting a plurality of sensors 11, and a plurality of actuators, such as fuel injection valves, to the CPU 101. The CPU 101 is connected via a bus line 107 to a RAM (Random Access Memory) 102, a ROM (Read Only Memory) 103, and a communication control IC (Integrated Circuit) 105. The communication control IC 105 is connected via a bus interface 106 to the network bus 6. The CPU 101 determines control parameters based on output signals from the sensors 11 according to a program stored in the ROM 103 for driving the actuators 12. The RAM 102 temporarily stores data of results of computation. The communication control IC controls transmission of a message to the network bus and reception of a message from the network bus. Fig. 3 shows details of the bus interface 106 connected to the communication control IC 105, and the network bus 6 comprised of twisted pair lines 6b and 6c connected at both ends of thereof to each other via respective terminal resistances 6a, 6a. The communication control IC 105 has a first sending terminal connected to a base of a transistor 119 via a resistance 115. The transistor 119 has an emitter thereof connected to a power supply line VSUP and a collector thereof connected via a resistance 116 to an inverting input terminal of a comparator 111 and to one 6b of the twisted pair lines 6b and 6c. The communication control IC 105 has a second sending terminal connected to a base of a transistor 120 via a resistance 117. The transistor 120 has an emitter thereof grounded and a collector thereof connected via a resistance 118 to a non-inverting input terminal of the comparator 111 and to one 6c of the twisted pair lines 6b and 6c. The non-inverting input terminal of the comparator 111 is connected via a resistance 112 to the power supply line VSUP, and also via a resistance 113 to the inverting input terminal of the comparator 111. The comparator 111 has its inverting input terminal grounded via a resistance 114, and delivers an output signal therefrom to a receiving terminal of the communication control IC 105. In the circuitry shown in Fig. 3, the resistances 116 and 118 are each set to approximately 30 Ω, the resistances 112 and 114 to approximately 2 k Ω, the resistance 113 to approximately 200 Ω, and the terminal resistances 6a to approximately 100 Ω. The first and second sending terminals of the communication control IC 106 are supplied with pulse signals reverse to each other in phase. When the first sending terminal is at a low level and the second sending terminal is at a high level, both the transistors 119 and 120 are turned on to set the voltage of the one twisted pair line 6b at the high level and the other twisted pair line 6c at the low level. When the first sending terminal is at the high level and the second sending terminal is at the low level, both the transistors 119 and 120 are turned off to set the voltage of the one twisted pair line 6b at the low level and the other twisted pair line 6c at the high level. Thus, a signal is sent out to the network bus 6. As the potential of the one twisted pair line 6b goes high and low, the output from the comparator 111 goes low and high, thereby receiving a signal loaded on the network bus 6. The ECU's 2 to 5 are basically constructed in the same manner. Therefore, even if one of the ECU's sends out a signal which sets the voltage of the one twisted pair line 6b at the low level (i.e. sets the voltage of the other twisted pair line 6c at the high level), when another ECU sends out a signal which sets the voltage of the one twisted pair line 6b at the high level, the state of the voltage of the twisted pair line 6b is set to the high level. Therefore, in the present embodiment, a state in which the one twisted pair line line 6b is at the high level (the other twisted pair line 6c is at the low level) is defined as a dominant state, and an opposite state thereof as a recessive state. Next, a method of data transmission between the ECU's will be described. In the present embodiment, a token passing method is employed. This takes into consideration the fact that compared with a CSMA/CD (Carrier Sense Multiple Access with Collision Detection) method which is capable settling the collision, the token passing method is advantageous in respect of an electric delay on the network bus, and is capable of easily determining the maximum message delay time period, allowing the network system to be be designed easily. Fig. 4a and Fig. 4b show formats of messages used in data transmission in the present embodiment. Fig. 4a shows a format of a data message (second message) for sending a token (representative of the transmission right) and data, while Fig. 4b shows that of a token message (first message) for sending the token alone. In the following description, the ECU's constituting the network system will be referred to as the nodes 1 to 5. In Fig. 4a, a field F1 (SOM) notifies the start of a message, which is formed by one dominant bit. This field is used for synchronization of all the nodes constituting the network system. A field F2 (TA) designates an address of a destination node to which the token is to be transferred, which is formed by four bits of data. The node address is set e.g. to one of values 0 to 4 in a manner corresponding to the ECU's 1 to 5. A field F3 (CTL) designates a kind of message (token message or data message). A field F4 (DATA UNIT) is a data unit comprised of a DN (Destination Node) field designating a node or nodes which should receive data contained in a DATA field, a DLC (Data Length) filed designating the length of a byte of the DATA field, an ID (Identifier) filed forming an identifier of the data, and the DATA filed containing information to be transmitted. In this connection, the length of the DATA field is variable as can be presumed from the above description, and the total length of the data unit is variable within the range of 32 to 96 bytes. A field F5 (FCS) is a CRC (Cyclic Redundancy Check) field comprised of a sequence (CRC character sequence) of characters for error detection having 16 bits obtained by using the following equation (1) as a generating polynomial: Generating polynomial = X 16 + X 12 + X 5 + 1 A delimitter (dividing character) having one recessive bit is interposed between the field F5 and the field F6. A field F6 (DACK) is a second response field into which a data-acknowledging response (second acknowledge character) should be written by a node having normally or safely received the data, which is formed by an acknowledge slot having two bits. A sending node sends a message having the acknowledge slot as recessive bits, and the node or nodes which is/are designated in the message as one or ones to receive the information and has/have normally or safely received the data make(s) the data-acknowledging response by overwriting two dominant bits therein. A delimitter having two recessive bits is interposed between the fields F6 and F7. A field F7 (TACK) is a first response field into which a token-acknowledging response (first acknowledge character) should be written by a node having normally or safely received the token, which is formed by an acknowledge slot having two bits, similarly to the field F6. The sending node sends a message having the acknowledge slot as recessive bits, and the node having received the token makes the token-acknowledging response by overwriting two dominant bits therein. A delimitter formed by two recessive bits is interposed between the filed F7 and the field F8. A field F8 (EOM) designates the end of the message, and is formed by six recessive bits. In the present embodiment, the field F7 and the field F6 are provided as fields into which acknowledgement of the token and acknowledgement of data are made, respectively, which makes it possible for a sending end to promptly confirm whether or not the transfer of the token and the transmission of data have been successfully carried out. The token message shown in Fig. 4b is constructed such that the fields F4 to F6 are deleted from the data message, and a delimitter is interposed between the fields F3 and F7. Next, a method of circulating the token (transferring the token round the ECU's) will be described. If a node having received the token has data or information to be transmitted, it has to transfer the token together with the data. If the node has no data or information to be transmitted, it has to transmit the token alone. A node to which the token is to be transferred is a node designated in the field F2 (TA). The token address is normally set by adding a value of one to the address of the sending node itself, and a message continues to be sent out until a token-acknowledging response is detected, by sequentially increasing the token address by an incremental value of 1. However, when a calculated value of the token address reaches a value of 16, the token address is set to 0, thus circulating token address through values of of 0 to 15. When the node corresponding to the token address set in the message has received the token, it overwrites two dominant bits into the acknowledge slot of the field F7 (TACK), thereby making the token-acknowledging response. When the token-acknowledging response is thus overwritten and the message normally terminates in the field F8 (EOM), the sending node having sent the token completes the transfer of the token, and the receiving node has acquired the token. Next, a manner of detecting failure in transmission of a message will be described. When roughly classified, there are two types of failure in transmission: one in which there has been no transmission error but no data-acknowledging response is overwritten in the field F6 (DACK) of the acknowledge slot, and the other in which a transmission error has been detected during transmission of a message. When no data-acknowledging response has been made, this type of failure of transmission is detected by the sending node itself. On the other hand, the transmission error is detected by monitoring of data, detection by CRC, detection of bit stuff error, and a message format check. According to the error detection by monitoring of data, a transmission error is detected when data a sending node is transmitting does not coincide with data loaded on the bus. However, this monitoring of data is inhibited with the acknowledge slots of the fields F6 and F7, and one recessive bit subsequent thereto. According to the error detection by CRC, a transmission error is detected when an error is found as to CRC characters set in the field F5 (FCS) and this detection is performed by nodes other than the sending node. According to the bit stuff error detection, it is determined that there is an error in transmission when more than 5 consecutive bits designate the same logical state, and this detection is performed by nodes other than the sending node. However, the fields F6 (DACK), F7 (TACK), F8 (EOM) and the delimitters are executed from objects of monitoring. According to the error detection by the message format check, an error is detected when an illegal logical state is found in the fields of the fixed-logical-state bits (the fields F3, F8 and the delimitters), and this type of error detection is performed by nodes other than the sending node. When any of the above-described errors occurring during transmission is detected, a node having detected the error immediately sends out an error message (six consecutive dominant bits), whereby even if a transmission error is detected by a node or nodes other than the sending node, the sending node can recognize the transmission error. Next, a procedure of generating the token or initially rendering the token to one of the nodes when the token has not been generated or lost from the data transmission system will be described with reference to Fig. 5 and Fig. 6. The communication control IC 105 of each of the ECU's 1 to 5 determines at a step S1 of Fig. 5 whether or not the network bus is idling, to determinate whether the data transmission system is in a state in which the token has not been generated immediately after the start of system, or has been lost due to failure of a node having received the token. If the answer to this question is negative (NO), i.e. if another ECU is sending a message, the present program is immediately terminated. On the other hand, if the network bus 6 is idle, i.e. no other ECU's are sending any message, the present ECU starts data transmission via the communication control IC 105 and the bus interface 106 at a step S2, assuming that the present node has acquired the token. Then, data sent from the present node is compared with data on the network bus 6 bit by bit to determine whether both the data are identical to each other at a step S3. If the answer to this question is affirmative (YES), i.e. the data sent out and the data on the network bus coincide with each other, it means that there is no contention between the data sent out from the present node and data from other nodes, or the present node remains undefeated in contention for acquiring the token, and hence data transmission is continued assuming that the present node has not lost the token yet. That is, the present program proceeds to a step S4, where it is determined whether or not transmission of the whole sequence of data has been completed. If the answer to this question is negative (NO), the program returns to the step S3, where data subsequently sent out is compared with data loaded on the network bus, in the same manner as described above. It goes without saying that there is a case in which the present node is found to be defeated in contention for acquiring the token to stop data transmission when the above-described procedure is carried out. Further, as a method of determining whether the data sent from the present node and the data loaded on the system bus coincide with each other, the above-mentioned method of the error detection by monitoring data is utilized for determining that the data sent out and the data loaded on the system bus do not coincide with each other. In the present case, more specifically, the coincidence of the data is determined by calculating an exclusive OR of the data sent out and the data received from the network bus 6. On the other hand, if the data sent out from the present node is different from the data loaded on the network bus 6, it means that there has been a contention for the token with other nodes, and the present node has been defeated in the contention, so that the data transmission is stopped at a step S5, followed by terminating the present program. If it is determined at the step S4 that the whole sequence of data has been sent out, i.e. if it is determined that the present node remains undefeated throughout the contention for acquiring the token, it is determined at a step S6 whether or not the transfer of the token has been completed, by making a check for the token-acknowledging response. If the transfer of the token has not been completed, a value of 1 is added to the token address of the token message, and then the resulting token message is sent out to the network bus 6 at a step S7. The steps S6 and S7 are repeatedly carried out until the transfer of the token is completed, whereupon the present program is terminated. Further, in determining a winner of contention, data formed by an identical sequence of bits is actually sent out a plurality of times for prevention of an erroneous determination due to noise or the like. Next, details of a manner of determining a winner of the contention will be described with reference to Fig. 6a to Fig. 6d. Let it be assumed that data are transmitted from Node 1 and Node 2 as shown in Fig. 6b and Fig. 6c, respectively. As described hereinbefore, a bit in the logical state "1" is a dominant bit, and a bit in the logical state "0" is a recessive bit. If contention occurs between the dominant bit and the recessive bit, the logical state on the network bus becomes equal to "1". In the case of data shown in Fig. 6b and Fig. 6c, bits corresponding to the bit numbers 1 to 4 shown in Fig. 6a are in the same logical states, respectively, and the logical states of the data sent from Node 1 and Node 2, and the logical state of the network bus are all equal to each other. Accordingly, Node 1 and Node 2 both continue to send out respective messages from bit No. 1 to bit No. 4. However, at bit No. 5, the logical state of data sent from Node 1 is equal to "1", whereas the logical state of data sent from Node 2 is equal to "0". Accordingly, the logical state of the network bus becomes equal to the logical state "1" of the dominant bit sent from Node 1. Therefore, Node 1 having sent the dominant bit determines that it has not lost the token and continues to send the message, whereas Node 2 having the sent the recessive bit determines that it has lost the token and ceases to send the message. In this connection, Fig. 6a to Fig. 6d show a case where two nodes are in contention for the token. However, actually, there can occur a case in which a contention for the token arises among more than two nodes. However, it is impossible for all the nodes to continue sending the same sequence of data, and eventually, one node is necessarily determined to remain undefeated in the contention, without any inconveniences. As can be clearly understood from the above description, according to the present invention, when the control system is started or a node having received the token is in failure, a token is generated or initially given to one of the nodes by contention for the token as described above, and then the token is circulated through or transferred round the nodes. This makes it possible to promptly generate the token by giving a chance of acquiring the token equally to all the nodes, enabling the system to function efficiently. Further, the present invention is not limited to the above embodiment, but as a manner of mediation of contention, the logical state "0" may be used for a dominant bit and the logical state "1" for a recessive bit, inversely to the above embodiment. Further, after the token has been generated through contention, a node to which the token is first transferred is not necessarily restricted to a node having a node address following the address having initially acquired the token, but the token may be first transferred to a predetermined node having the smallest node address, then permitting the node to circulate through the nodes in a predetermined cycle. Next, a procedure of processing performed when no data-acknowledging response has been received after a sending node has sent a data message. In the following description, the first acknowledge character to be overwritten into the field F7 is referred to as "the token ACK", while the second acknowledge character to be overwritten in the field F6 as "the data ACK". (1) When the token ACK is not detected and the data ACK is detected: The token data address is increased by an incremental value of 1 and then the resulting token message is sent out. This is for transferring the token alone to a node subsequent to the node to which the token has not been successfully transferred, since reception of the data written in the field F4 has been acknowledged. (2) When the token ACK is detected, and the data ACK is not detected: Since the transfer of the token is completed, retransmission of data is not carried out. The data is retransmitted, if possible, when the token is acquired next time. (3) When neither the token ACK nor the data ACK is detected: The token address is increased by an incremental value of 1 and the token message containing the resulting token address is transmitted, but the retransmission of data is not carried out. Thus, the circulation of the token is performed in preference to the transmission of data to permit smooth circulation of the token. Further, the data is transmitted again, if possible, when the token is acquired next time. As described above, even if the data ACK is not detected, it is judged, so long as the token ACK is detected, that the transfer of the token is completed, and the retransmission of data is inhibited. Further, when neither the data ACK nor the token ACK is detected, only the transfer of the token is tried again without retransmitting the data, whereby it is possible to circulate the token smoothly. The preference is given to the transfer of the token since the retransmission of data performed immediately after detection of a transmission error requires the maximum delay time of the system to be set to a longer time period than when the transfer of the token is preferentially performed as in the present embodiment. Although in the above example, when neither the token ACK nor the data ACK is detected, the token message is permitted to be sent out immediately, and at the same time retransmission of data is inhibited, this is not limitative, but the transfer of the token may be performed after retransmission of data is tried one or two times.

Claims: A data transmission system for a vehicle, including a plurality of control systems (1, 2, 3, 4, 5) installed on said vehicle, a network bus (6) connecting said plurality of control systems with each other for circulating a transmission right through said plurality of control systems to thereby perform transmission of a message between said plurality of control systems, and transmitter-reciever means for transmitting data to or receiving data from the rest of said plurality of control systems via said network bus, characterized in that each of said plurality of control systems comprises: collision-detecting means for detecting a collision of data transmitted from said transmitter-receiver means with data transmitted from any of the rest of said plurality of control systems; mediating means for performing mediation on said data transmitted from said transmitter-receiver means and having been detected to be collided with said data transmitted from any of the rest of said plurality of control systems to direct said transmitter-receiver means to continue data transmission or stop said data transmission, for the purpose of avoiding said collision, monitor means for monitoring said transmission right; and control means for causing said transmitter-receiver means to start transmitting data when said monitoring means detects that said transmission right is not generated or lost from said system, and causing said transmitter-receiver means to continue transmitting said data when said collision-detecting means does not detect a collision of said data with data transmitted from the rest of said plurality of control systems, or when said mediating means directs said transmitter-receiver to continue data transmission. A data transmission system according to claim 1, further comprising transfer means for transferring said transmission right to a subsequent control system in a predetermined manner, when said control means controls said transmitter-receiver means to continue said data transmission until said data transmission is completed. A data transmission system according to claim 1 or 2, wherein said mediating means is adapted to compare said data transmitted from said transmitter-receiver means with said data received via said network bus from the rest of said plurality of control systems, bit by bit, based on the logic considering one of logical levels of transmission data as dominant, and the other of said logical levels of said transmission data as recessive, and adapted to direct said transmitter-receiver means to stop said data transmission when said data transmitted from said transmitter-receiver means and said data received from said network bus are different from each other. A data transmission system according to claim 2 or 3, wherein said transfer means is adapted to transfer said transmission right to said subsequent control unit by increasing an address representative of said each of said plurality of control systems incorporating said transfer means by a predetermined number.

Inventors: HASHIMOTO HIROSHI, ISHII JUN, NAGATANI YUJI, HASHIMOTO, HIROSHI, ISHII, JUN, NAGATANI, YUJI, Hashimoto, Hiroshi c/o Honda R &amp; D Co., Ltd., Ishii, Jun c/o Honda R &amp; D Co., Ltd., Nagatani, Yuji c/o Honda R &amp; D Co., Ltd.
Applicants: HONDA MOTOR CO LTD, HONDA GIKEN KOGYO KABUSHIKI KAISHA
Application year: 1994
Main classification: H04L12
IPC codes: B60R16, H04L1, H04L12