JP2007036632A - Gateway apparatus - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a gateway apparatus capable of automatically setting a frame ID to be passed by having only to execute connection for interrupting the gateway apparatus to a bus. <P>SOLUTION: When on-vehicle devices A1, A2 (B1, B2) request the gateway apparatus 1 to transmit data of on-vehicle devices B1, B2 (A1, A2) connected to another network connected by the gateway apparatus 1, the gateway apparatus 1 discriminates the presence/absence of the on-vehicle devices B1, B2 (A1, A2) connected to the other network and whose data are requested, and when the on-vehicle devices B1, B2 (A1, A2) whose data are requested exist in the other network, a CPU 2 of the gateway apparatus 1 registers the on-vehicle devices B1, B2 (A1, A2) to a RAM 24 as a transfer destination or a transfer source. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention belongs to the technical field of gateway devices that perform communication of devices belonging to different networks, and is particularly useful for enabling communication between different communication networks between in-vehicle devices.

Conventionally, a registration list of IDs of in-vehicle devices is prepared in advance, and the connection with a new in-vehicle device is checked against the registration list. If the list cannot be confirmed, reception from the new in-vehicle device is received. If there is, the user is notified that it is not registered (see, for example, Patent Document 1).
JP 2004-247944 A (page 2-11, all figures)

  However, in the past, for the frame data gatewayed by the gateway unit, for the purpose of reducing the bus load, it is necessary to register the ID of the frame data to be passed so as not to transfer the frame data that does not need to be transferred. Therefore, in order to connect to buses with different specifications, each setting is required, and the types of gateway units increase.

  The present invention has been made paying attention to the above-mentioned problems, and the object of the present invention is to provide a gateway device that can automatically set a frame ID to be passed only by connecting the gateway device to interrupt the bus. It is to provide.

  In order to achieve the above object, in the present invention, a plurality of in-vehicle networks are formed by in-vehicle devices in a vehicle, different networks formed are connected, and data received from the network is temporarily stored and converted to be separated. In the gateway device, the data of the in-vehicle device belonging to another network connected from the in-vehicle device to the gateway device is exchanged between the in-vehicle devices connected to different networks. When requested, the presence / absence of the requested in-vehicle device in another network is determined, and when there is the requested in-vehicle device, transfer setting registration means for registering as a transfer destination or transfer source of the gateway device is provided. It is provided.

  Therefore, in the present invention, it is possible to automatically set the frame ID to be passed by simply connecting the gateway device to the bus, without increasing the number of types of units, or eliminating the ID registration work. it can.

  Hereinafter, an embodiment for realizing the gateway device of the present invention will be described based on the first embodiment.

First, the configuration will be described.
FIG. 1 is a diagram illustrating a network configuration using the gateway device according to the first embodiment. FIG. 2 is a block diagram of the gateway device according to the first embodiment.
The gateway device 1 according to the first embodiment performs low-speed communication between the network A configured to connect the controllers A1 and A2 of the in-vehicle devices of the vehicle via the bus A that performs high-speed communication and the controllers B1 and B2 of the in-vehicle devices of the vehicle. It is provided so as to connect to the network B configured to be connected by the bus B.

As shown in FIG. 2, the gateway device 1 includes a CPU 2, transceivers 3a and 3b, a power supply circuit 4, an oscillator 5, and termination resistors 6a and 6b as main components.
The CPU 2 includes communication units 21a and 21b, a watchdog timer unit 22, a ROM 23, and a RAM 24, and performs calculation and control.
The communication units 21a and 21b perform data transmission / reception of CAN communication with the transceivers 3a and 3b in accordance with an input / output request of the CPU 2 or in accordance with a predetermined timing or the like and in accordance with a CAN communication protocol.
The watchdog timer unit 22 monitors whether or not an abnormality has occurred in the processing executed by the CPU 2, for example, by detecting a flag at the end of the routine to be executed.

The ROM 23 stores contents and data of processing performed by the CPU 2.
The RAM 24 temporarily stores data and the like. In the first embodiment, registration data of an ID code for which transfer is permitted is stored (the CPU 2 and the RAM 24 correspond to transfer setting registration means and abnormality storage means).
The transceivers 3a and 3b are connected to the buses A and B, which are communication lines, via the terminating resistors 6a and 6b, and also to the CPU 2, from the bus A and the bus B each consisting of two lines. The received signal is converted into a signal that can be input to the CPU 2 and output to the CPU 2, and the signal output from the CPU 2 is converted into a signal that can be sent to the bus A and bus B consisting of two lines and output to the bus A and bus B. .
The power supply circuit 4 supplies power to the CPU 2 and peripheral circuits.
The oscillator 5 outputs to the CPU 2 an oscillation signal used for synchronization processing and signal generation with the CPU 2 for communication.

Next, the operation will be described.
[Transfer process and ID registration process]
FIG. 3 is a flowchart showing the flow of transfer processing and ID processing executed by the gateway device of the first embodiment. Each step will be described below.
For the sake of explanation, it is assumed that the network A is channel 1 (hereinafter abbreviated as CH1) and the b network B is channel 2 (hereinafter abbreviated as CH2).

  In step S11, it is determined whether or not data has been received. If there is reception, the process proceeds to step S12. If there is no reception, the process ends.

  In step S12, it is determined whether or not the reception is from CH1, and if the reception is from CH1, the process proceeds to step S13. If the reception is not from CH1, the process proceeds to step S17.

  In step S13, it is determined whether or not the frame data is to be transferred by the gateway device. If the frame data is to be transferred, the process proceeds to step S14. If the frame data is not to be transferred, the process proceeds to step S15.

  In step S14, the frame data is transferred to CH2.

  In step S15, it is determined whether the received frame data is a setting request frame. If it is a setting request frame, the process proceeds to step S16, and if it is not a setting request frame, the process ends.

  In step S16, the CH2 ID setting mode processing is performed. This process will be described later.

  In step S17, it is determined whether or not reception is from CH2, and if reception is from CH2, the process proceeds to step S18, and if not reception from CH2, the process is terminated.

  In step S18, it is determined whether or not the frame data is to be transferred by the gateway device. If the frame data is to be transferred, the process proceeds to step S19. If the frame data is not to be transferred, the process proceeds to step S20.

  In step S19, the frame data is transferred to CH1.

  In step S20, it is determined whether or not the received frame data is a setting request frame. If it is a setting request frame, the process proceeds to step S21. If it is not a setting request frame, the process ends.

  In step S21, the CH1 ID setting mode processing is performed. This process will be described later.

[ID setting registration process]
FIG. 4 is a flowchart showing the flow of ID setting registration processing executed by the CPU 2 of the gateway device of the first embodiment. Each step will be described below.
Note that the processing of the flowchart of FIG. 4 is the details of the processing of steps S16 and S21 in FIG.

  In step S31, the timer is started and the elapsed time is measured.

  In step S32, it is determined whether or not the data of the ID requested to be set is received from the other CH (channel). If received, the process proceeds to step S33, and if not received, the process proceeds to step S35.

  In step S33, an ID frame is registered in the other CH. As a result, it is determined to transfer in the processing of steps S13 and S18 from the next time.

  In step S34, the information related to the ID is deleted from the corresponding request ID unmatch information, that is, the information stored as abnormal without receiving the corresponding ID.

  In step S35, it is determined whether or not the timer has reached a predetermined time. If the timer has reached a predetermined time, the process proceeds to step S36, and if not, the process returns to step S32.

  In step S36, information relating to this ID is added as request ID unmatch information, that is, information stored as abnormal without receiving from the corresponding ID.

[Setting request frame transmission processing]
FIG. 5 is a flowchart showing a flow of setting request frame data transmission processing executed by an in-vehicle device belonging as a node to the networks A and B connected by the gateway of the first embodiment. Each step will be described below.

  In step S41, it is determined whether frame data from another in-vehicle device required by the in-vehicle device is received. If not received, the process proceeds to step S42, and if received, the process is terminated.

  In step S42, a timer is started and elapsed time is measured.

  In step S43, it is determined whether frame data from another in-vehicle device required by the in-vehicle device is received. If not received, the process proceeds to step S44, and if received, the process is terminated.

  In step S44, it is determined whether or not the timer has reached a predetermined time, and if the fixed time has been reached, that is, if the time has expired, the process proceeds to step S43, and if not, the process returns to step S43.

  In step S45, a setting request frame is transmitted to the gateway device.

[Automatic ID registration function]
The in-vehicle devices A1, A2, B1, and B2 connected to the bus A and the bus B periodically transmit message frame data for CAN communication. Further, it monitors the frame data of the ID code that it needs and should receive, and if it does not receive the frame data within a certain time, it sends the setting request frame data including the ID code of the communication partner (FIG. 5). S41->S42->S43->S44-> S45). In this case, the load applied to the buses A and B in order to transmit one frame at regular intervals is small.

Upon receiving the setting request frame data from the in-vehicle device, the gateway device 1 searches the other CH (bus) for the in-vehicle device of the ID code included in the setting request frame data, and the frame data from the in-vehicle device of the ID code. Is registered in the RAM 24 as the gateway ID that the ID exists as a normal communication destination in the other CH (in FIG. 3, S16, S21, in FIG. 4, S31 → S32 → Process of S33).
This ID data registered in the RAM 24 maintains its state as long as power is supplied from the vehicle battery.
As a result, the gateway device 1 does not need to register the ID of data to be transferred in advance, and there is no increase in unit types, product number division, and the like, and costs and work are reduced.

Further, the exchange of signals in the normal operation is a periodic transmission message, but the wake-up command as network management may be only event transmission. However, since such management commands are common to all systems, even if they are registered as defaults, there is no effect of increasing the product number.
The CAN message frame has a maximum transmission cycle of 100 ms. In the case of 500 kbps CAN, the time required for transmission of one frame is about 220 μs, so that registration is completed in about several seconds.

  The gateway device 1 that has received the setting request frame data from the in-vehicle device searches the other CH (bus) for the in-vehicle device of the ID code included in the setting request frame data. If the frame data from the in-vehicle device with the ID code is not received within a certain time, it is assumed that an unmatch has occurred in the network system and is stored in the RAM 24 as an error. This information may be used for analysis by an external diagnostic device or the like, or the user may be able to confirm the abnormality by an indicator output or the like.

Next, the effect will be described.
In the gateway device of the first embodiment, the effects listed below can be obtained.

  (1) In-vehicle devices A1, A2, B1, and B2 in the vehicle form a plurality of in-vehicle networks, connect the formed different networks, and temporarily store and convert the data received from the network. In the gateway device 1 that transmits data to a network and exchanges data between in-vehicle devices connected to different networks, the in-vehicle devices A1, A2, B1, and B2 to another network connected by the gateway device 1 When the data of the in-vehicle devices A1, A2, B1, and B2 to which it belongs is requested, the presence or absence of the in-vehicle devices A1, A2, B1, and B2 requested in another network is determined, and the requested in-vehicle devices A1 and A2 , B1 and B2 are registered in the RAM 24 as the transfer destination or transfer source of the gateway device 1, the gateway device The only connections to interrupt the bus, it is possible to automatically set the frame ID to pass, can not increase the types of units, or can be eliminated ID registration operation.

  (2) When the data of the in-vehicle devices A1, A2, B1, and B2 belonging to another network connected by the gateway device 1 from the in-vehicle devices A1, A2, B1, and B2 is requested, the in-vehicle device requested in the other network The presence or absence of the devices A1, A2, B1, B2 is determined, and if there is no requested in-vehicle device A1, A2, B1, B2, it is assumed that there is an abnormality, and the CPU 2 stores the abnormality content in the RAM 24. It can be used for the analysis of the abnormality, or the user can know the abnormality immediately.

  (3) Individual ID codes for identification are assigned to the in-vehicle devices A1, A2, B1, and B2 connected to the network, and the data transferred by the gateway device 1 is frame-structured data, and the in-vehicle device A1 , A2, B1, and B2, if the data of the in-vehicle devices A1, A2, B1, and B2 of different networks that are required cannot be obtained over a certain time, the corresponding in-vehicle devices A1, A2, B1, and B2 Requesting communication with the device and outputting the setting request frame data including the ID code of the corresponding in-vehicle device. Upon receiving the setting request frame data, the CPU 2 searches for the corresponding ID code in another network and corresponds. In order to register the ID code as the transfer destination or transfer source of the gateway device 1 when data is received from the in-vehicle devices A1, A2, B1, B2 of the ID code By simply connecting the gateway device to the bus, the frame ID to be passed can be automatically set, and the number of types of units can be increased or the ID registration work can be eliminated.

  As mentioned above, although the gateway apparatus of this invention has been demonstrated based on Example 1, it is not restricted to these Examples about concrete structure, The summary of the invention which concerns on each claim of a claim Unless it deviates, design changes and additions are allowed.

The gateway device 1 registers a transfer destination or transfer source, that is, an ID that permits communication, and permits passage of data of the ID. Therefore, the ID may be registered as passage permission data.
Depending on the content of the abnormality stored by the abnormality storage means, processing to deal with may be performed.

  The present application can be easily used not only in a vehicle network but also in a network configured between controllers, and can be easily used in a network by other methods.

It is a figure which shows the network structure using the gateway apparatus of Example 1. FIG. It is a block diagram of the gateway apparatus of Example 1. 6 is a flowchart illustrating a flow of transfer processing and ID processing executed by the gateway device of the first embodiment. 6 is a flowchart illustrating a flow of ID setting registration processing executed by the CPU 2 of the gateway device according to the first embodiment. 3 is a flowchart showing a flow of setting request frame data transmission processing executed by an in-vehicle device belonging as a node to networks A and B connected by a gateway according to the first embodiment.

Explanation of symbols

1 Gateway device 2 CPU
21a Communication unit 21b Communication unit 22 Watchdog timer unit 23 ROM
24 RAM
3a transceiver 3b transceiver 4 power supply circuit 5 oscillator 6a termination resistor 6b termination resistor

Claims (3)

Forming multiple in-car networks with in-car devices in the car,
Connect between the different networks formed,
Temporarily save and convert data received from the network and send it to another network,
Exchange data between in-vehicle devices connected to different networks,
In the gateway device,
When data of an in-vehicle device belonging to another network connected by the gateway device is requested from the in-vehicle device, it is determined whether there is an in-vehicle device requested in another network, and there is an in-vehicle device requested. Provided with a transfer setting registration means for registering as a transfer destination or transfer source of the gateway device,
A gateway device characterized by that. The gateway device according to claim 1,
When data of an in-vehicle device belonging to another network connected by the gateway device is requested from the in-vehicle device, it is determined whether there is an in-vehicle device requested in another network, and there is no requested in-vehicle device Is provided with an abnormality storage means for storing the contents of the abnormality.
A gateway device characterized by that. In the gateway device according to claim 1 or 2,
In-vehicle devices connected to the network are assigned individual ID codes for identification,
The data transferred by the gateway device is frame structure data,
The in-vehicle device requests communication with the corresponding in-vehicle device and includes the ID code of the in-vehicle device when the data of the in-vehicle device of another necessary network cannot be obtained over a certain time. Output setting request frame data,
When the transfer setting registration unit receives the setting request frame data, the transfer setting registration unit searches for the corresponding ID code in another network, and when there is data reception of the corresponding ID code from the in-vehicle device, the ID code is transmitted to the gateway device. Register as a forwarding destination or forwarding source,
A gateway device characterized by that.

Images