Vehicle control unit with adjustable cycle time for a vehicle bus system
The vehicle control unit allows cycle time adjustments via data entry, addressing the inefficiency of reprogramming for cycle time changes, thus reducing software variants and enhancing flexibility.
Patent Information
- Application Number
- DE102014217213
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2014-08-28
- Publication Date
- 2024-12-05
- Estimated Expiration
- 2034-08-28
AI Technical Summary
Existing vehicle control devices require separate software variants for each cycle time deviation in vehicle bus system messages, necessitating reprogramming or complete software reinstallations to adjust cycle times, leading to inefficiencies and increased variant management.
A vehicle control unit with a communication interface that allows changing cycle times via an application interface using data, eliminating the need for software reinstallation or reprogramming by utilizing a preinstalled datatable area for specifying cycle times.
Enables quick and efficient adjustment of cycle times without software changes, reducing the need for multiple software variants and minimizing downtime.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[0001] The invention relates to a vehicle control unit, in particular a vehicle transmission control unit, with a communication interface for the cyclic exchange of at least one bus system message with a vehicle bus system depending on a cycle time for the bus system message stored in the vehicle control unit.
[0002] From DE 100 00 303 A1, a method and a device for exchanging data between at least two participants connected to a bus system are known. It is provided that at least one of the participants determines a time correction value and adjusts its time information and / or its time base depending on the time correction value.
[0003] In vehicle bus systems, messages exchanged between system participants are transmitted cyclically. At least one participant in the bus system cyclically provides a message by repeatedly feeding it into the system. The other participants also expect and retrieve the message cyclically. Communication is therefore time-controlled and periodic. The cycle time for a message determines the frequency with which the specific message is exchanged between the vehicle bus system participants. Thus, each message exchanged within the bus system has its own cycle time, both for providing the message and for retrieving or expecting it.It is of course possible to provide an identical cycle time for several of the bus system messages that can be exchanged in the bus system.
[0004] There are known vehicle bus systems where the cycle times of the bus system messages are standardized. This is the case, for example, with a vehicle bus system that uses the SAE J1939 bus protocol. Here, the cycle time for some of the bus system messages is specified as 10 ms. However, it may be advantageous to deviate from this standard. If this is the case, the changed cycle time must be set identically for all participants in the vehicle bus system for the bus system messages affected by the change. If this is not done, a sufficiently large difference between the respective set cycle times will result in so-called timeout errors.This occurs, for example, when one participant operates with a cycle time of 10 ms, i.e., expects a bus system message at this frequency, and another participant provides the bus system message at a cycle time of 50 ms, i.e., at this frequency. As a result, the first participant receives the message from the second participant significantly late, or not at all, leading to the aforementioned timeout error.
[0005] Up to now, it has been standard practice to set the cycle times for each bus system message on bus system participants. This means that each cycle time for each bus system message is hard-coded into the participant, making subsequent changes possible only through reprogramming or a complete reinstallation of the participant's software. Therefore, a separate ECU software variant is typically required for control units if even a single cycle time deviates from the standard. Similarly, a separate ECU software variant must be provided for each additional cycle time deviation. Consequently, a correspondingly large number of ECU software variants must be maintained.
[0006] German patent DE 103 41 514 A1 discloses a CAN controller module in which cycle times are freely configurable up to a maximum cycle time. Data for creating a CAN message list can be read into a configuration tool via an input unit and / or an interface, whereby the number and number of identifiers, as well as the payload and cycle times, are configurable.
[0007] The purpose of the invention is to reduce the variety of vehicle control units.
[0008] This task is solved by the features of the claim. Accordingly, a vehicle control unit is proposed that has a communication interface for communicating with a vehicle bus system, i.e., for exchanging (sending / receiving) at least one bus system message with the vehicle bus system. Communication occurs cyclically, depending on a cycle time for the bus system message stored in the vehicle control unit. Furthermore, the vehicle control unit has an application interface for configuring the vehicle control unit. It is provided that the cycle time for the bus system message can be changed via the application interface by configuring the vehicle control unit.
[0009] Accordingly, it is intended that, for specifying the specific cycle time of the bus system message, for example during initial setup or subsequent modification, access is made via the application interface to a configurable area of the vehicle control unit software already pre-installed in the vehicle control unit. This area is designated for specifying and storing the cycle time. The specific cycle time for the bus system message is then defined there by appropriately configuring this area. In contrast to a new installation, reprogramming, or initial installation of the vehicle control unit, this procedure for setting the cycle time is very fast. This can therefore be carried out, for example, at the end of an assembly line for the vehicle control unit or a vehicle component associated with the vehicle control unit, or during customer service.
[0010] Furthermore, this approach requires only a single software variant for the vehicle control unit (ECU), regardless of the number of cycle time variants for the bus system messages. The ECU is then configured with the specific cycle time for the bus system message required for the respective application as needed, for example, during the final assembly of the ECU or a vehicle component to which the ECU is attached. If an adjustment of the bus system message cycle time is required at a later time, this can also be easily accomplished by configuring the ECU, i.e., without reinstalling or reprogramming the ECU software.
[0011] As explained earlier, the cycle time is the frequency at which the corresponding bus system message is exchanged within the vehicle bus system, i.e., between the participants of the bus system. It is the frequency at which at least one participant of the vehicle bus system sends the message and at which another participant of the vehicle bus system expects to receive the bus system message. The cycle time for the bus system message stored in the vehicle control unit must correspond to the cycle time for the bus system message of the bus system itself, or rather, to the cycle time of the other participants of the bus system; otherwise, the timeout errors mentioned earlier can occur.
[0012] The vehicle control unit serves in particular to actuate, i.e., control (regulate or control) a vehicle component, such as a vehicle drive motor, a vehicle transmission, or a vehicle cooling unit, etc. Preferably, however, the vehicle control unit is a vehicle transmission control unit, i.e., a vehicle control unit for actuating / controlling an automatic vehicle transmission, such as an automatic transmission or automated manual transmission.
[0013] The invention provides a method for adapting the cycle time of a bus system message from a vehicle control unit to a vehicle bus system. The vehicle bus system has a first cycle time for a bus system message, with which at least one participant in the vehicle bus system cyclically awaits the bus system message. In contrast, the vehicle control unit has a second cycle time stored within it, with which the vehicle control unit cyclically provides the bus system message to the vehicle bus system, i.e., to at least one other participant in the vehicle bus system, via a communication interface. It is provided that the second cycle time for the bus system message can be modified via an application interface of the vehicle control unit by entering data. Accordingly, the second cycle time is adjusted to the first cycle time by entering data via the application interface.
[0014] In other words, the process aligns the (first) cycle time for the bus system message stored in the vehicle control unit with the (second) cycle time for the bus system message used by the other participants in the vehicle bus system. As explained above, specifying the cycle time no longer requires modifying or reinstalling the basic control unit software present in the vehicle control unit.
[0015] An application parameter is provided for each bus system message that the vehicle control unit (ECU) can exchange (receive and / or send) via the communication interface. This parameter corresponds to the aforementioned configurable area of the ECU software already pre-installed in the ECU. The cycle time for the bus system message is stored in the application parameter. The default value for the cycle time is typically the cycle time specified in the relevant standard. For example, the SAE J1939 standard specifies a cycle time of 10 ms for some bus system messages. The application parameter can be modified via the ECU's application interface by configuring the data.Accordingly, the standard cycle time for the bus system message, which is already stored therein, can be changed via the application interface by means of data entry, provided that the bus system is to operate with a different cycle time for the bus system message than the standard. Preferably, the application parameter for each received message is located in middleware within the software of the vehicle control unit.
[0016] The vehicle control unit (ECU) is equipped with software structured in a layered architecture. Within the middleware of this ECU software, a separate application parameter is provided for each of the bus system messages exchanged via the communication interface. This application parameter can be modified via the application interface by entering data, and it contains the cycle time for the respective bus system message. Accordingly, the application parameter and its stored cycle time can be accessed via the application interface, and the cycle time for the respective bus system message can be specified by entering data into the application parameter.
[0017] The aforementioned communication interface and / or application interface may in particular be a hardware or software interface of the vehicle control unit.
[0018] The invention also enables the application of a vehicle bus system with multiple participants, which cyclically exchange (send / receive) a bus system message with each other depending on a cycle time, wherein the described vehicle control unit is one of the participants.
[0019] The invention is explained in more detail below by way of example with reference to a figure of an advantageous embodiment of the invention, from which further advantageous features of the invention can be derived.
[0020] The figure shows a schematic representation of a vehicle powertrain in a top view.
[0021] The vehicle powertrain depicted in the figure is, in particular, a powertrain of a passenger car or a truck. The basic components of such a vehicle powertrain are known and therefore require no further explanation. The vehicle powertrain has a vehicle drive motor 1, which serves to propel the vehicle. The drive motor 1 delivers drive torque. This drive torque is supplied to an automatic vehicle transmission 2. This is, for example, an automatic transmission or an automated manual transmission. The vehicle transmission 2 is designed with multiple stages. Thus, several gear ratio stages of the vehicle transmission 2 can be selectively engaged. This is done by means of actuators 3 of the vehicle transmission 2. The actuators 3 are controlled by a vehicle transmission control unit 4 (in the control engineering sense).For this purpose, the vehicle transmission control unit 4 is coupled with sensors 5, for example speed sensors and / or temperature sensors.
[0022] Furthermore, a selector device 6 is provided. Using the selector device 6, a vehicle operator, for example a driver, can specify a driving mode to the vehicle transmission control unit 4. The vehicle transmission control unit 4 is therefore designed to actuate, i.e., control (steer or regulate), the vehicle transmission 2 according to the specified driving mode.
[0023] Furthermore, a vehicle bus system 7 is provided. Several participants of the vehicle bus system 7 are coupled to each other to communicate, i.e., to exchange (send / receive) bus system messages. One of the participants is the vehicle transmission control unit 4. Another participant can be the selector device 6. Alternatively, a direct connection between the selector device 6 and the vehicle transmission control unit 4 can be established (shown as a dashed line), for example, via a proprietary vehicle transmission bus system. One of the other participants of the bus system 7 can be, for example, the engine control unit 8. This is used to control the vehicle's drive motor 1. Examples of other participants of the bus system 7 are a cooling fan control unit 9 for controlling a vehicle cooling fan, and a retarder control unit 10 for controlling a continuous brake (retarder) of the vehicle, etc.Communication between participants 4, 8, 9, 10 of bus system 7 takes place through cyclically transmitted bus system messages.
[0024] The vehicle transmission control unit 4, like the other participants 8, 9, and 10 of the bus system 7, has a communication interface 4a for communication with the bus system 7, i.e., with the other participants 8, 9, and 10 of the bus system 7. Via communication interface 4a, the vehicle transmission control unit 4 can therefore cyclically exchange bus system messages with the participants, depending on a specific cycle time for each bus system message. The vehicle transmission control unit 4 also has an application interface for data entry into the vehicle transmission control unit 4 or for data entry into the control unit software of the vehicle transmission control unit 4. This application interface can, for example, be implemented as a separate hardware interface 4b on the vehicle transmission control unit 4.Alternatively, the application interface can be implemented as a software interface and share a common hardware interface with the communication interface 4a. In this case, access to the application interface of the vehicle transmission control unit 4 is possible via the bus system 7.
[0025] As explained, communication within the vehicle bus system 7 depends on a specific cycle time for each bus system message. This cycle time of the bus system message, which the vehicle transmission control unit 4 uses to exchange messages with the other participants 8, 9, and 10 of the bus system 7 via communication interface 4a, is stored in the vehicle transmission control unit 4. Specifically, the vehicle transmission control unit 4 provides bus system messages to the bus system 7 (sending), with the timing of this provision depending on the specific cycle time for each bus system message stored in the vehicle transmission control unit 4.The vehicle transmission control unit 4, in turn, awaits and receives bus system messages from the other participants 8, 9, and 10 of bus system 7 (receiving), whereby the timing of the awaiting / receiving also depends on the specific cycle time of the respective bus system message stored in the vehicle transmission control unit 4. These stored cycle times can be changed via the application interface by data entry.
[0026] To prevent timeout errors within the communication of bus system 7, the cycle time stored in the vehicle transmission control unit 4 for each bus system message must correspond to the cycle time used by the other participants 8, 9, 10 of bus system 7 for that bus system message. Therefore, if this specific cycle time of the vehicle transmission control unit 4 differs from the specific cycle time of the other participants 8, 9, 10 of the vehicle bus system 7, the cycle time stored in the vehicle transmission control unit 4 for the respective bus system message can be adjusted to the cycle time of the other participants 8, 9, 10 via the application interface. This can be done with the vehicle transmission control unit 4 fully installed or during the installation of the vehicle transmission control unit 4 or the vehicle transmission 2 to which the vehicle transmission control unit 4 is physically attached.Because the cycle time can be changed via data entry, no reprogramming or reinstallation of the control unit software of the vehicle transmission control unit 4 is required to specify the cycle time.
[0027] The control unit software of the vehicle transmission control unit 4 is implemented with a layered architecture. The control unit software includes middleware 4c. A separate application parameter is provided for each of the bus system messages that can be exchanged, i.e., communicated, via the communication interface 4a. This application parameter contains the cycle time for the respective bus system message. The application parameter can be modified via the application interface of the vehicle transmission control unit 4 by entering data, thereby also changing the cycle time stored within it. The basic control unit software remains untouched for specifying the cycle times.
[0028] The vehicle bus system 7 is specifically a vehicle bus system that communicates using the SAE J1939 communication protocol. This means that the messages exchanged between the participants of vehicle bus 7 are encoded according to the SAE J1939 communication protocol. The SAE J1939 protocol specifies a cycle time of 10 ms for some of the bus system messages. However, deviations from this standard are possible. Because the cycle times of the vehicle transmission control unit 4 can be modified via data settings, it is not necessary to require a different version of the vehicle transmission control unit 4 or its control unit software for every deviation from the standard (different cycle time).
[0029] For accessing and specifying the cycle times stored in the vehicle transmission control unit 4, or the corresponding application parameter, an external application device 11 is provided, for example. This is, for example, an external computer that has the appropriate application software.
[0030] It should be noted that the concept presented here for changing the specific cycle times of the bus system messages is not only applicable to vehicle transmission control units 4, but also analogously to participants 8, 9, 10 of the bus system 7 that are not vehicle control units. For example, the drive motor control unit 8, the cooling fan control unit 9, or the retarder control unit 10 can be structured analogously. These vehicle control units can therefore each have an application interface through which the cycle times stored in the respective vehicle control unit 8, 9, 10 can be accessed and modified by data transmission. Reference sign 1 Vehicle drive motor 2 Vehicle transmissions 3 Actuator 4 Vehicle transmission control unit 4a Communication interface 4b Application interface 4c Middleware 5 sensors 6 Selector device 7 Bus system 8 Vehicle control unit 9 Fan control unit 10 Retarder control unit 11 Application device
Claims
[1] Vehicle control unit (4, 8, 9, 10), in particular vehicle transmission control unit (4), with a communication interface (4a) for the cyclic exchange of at least one bus system message with a vehicle bus system (7) depending on a cycle time for the bus system message stored in the vehicle control unit (4, 8, 9, 10), wherein the cycle time for the bus system message can be changed by means of an application interface (4b) of the vehicle control unit (4, 8, 9, 10), characterized by that the vehicle control unit (4, 8, 9, 10) has control unit software constructed in the form of a layered architecture, wherein in a middleware (4c) of the control unit software an application parameter that can be changed via the application interface (4b) by means of data input is provided for each of the bus system messages that can be exchanged via the communication interface (4a), wherein the cycle time for the respective bus system message is stored in the application parameter.
Citation Information
Patent Citations
Data communication method for bus system subscribers has time information provided by one subscriber used for correcting local clock source at each other subscriber
DE10000303A1
Controller area network (CAN) controller module, for motor vehicle, has serial interface for connection to external computer unit, via which it can be freely programmed, and connected to CAN analysis and simulation module
DE10341514A1
