EP2957075A1 - Appareil maître pour bus de communication embarqué d'un véhicule à moteur - Google Patents

Appareil maître pour bus de communication embarqué d'un véhicule à moteur

Info

Publication number
EP2957075A1
EP2957075A1 EP14709182.1A EP14709182A EP2957075A1 EP 2957075 A1 EP2957075 A1 EP 2957075A1 EP 14709182 A EP14709182 A EP 14709182A EP 2957075 A1 EP2957075 A1 EP 2957075A1
Authority
EP
European Patent Office
Prior art keywords
schedule
bus device
master
bus
master bus
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP14709182.1A
Other languages
German (de)
English (en)
Other versions
EP2957075B1 (fr
Inventor
Andre Hasse
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Audi AG
Original Assignee
Audi AG
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Audi AG filed Critical Audi AG
Publication of EP2957075A1 publication Critical patent/EP2957075A1/fr
Application granted granted Critical
Publication of EP2957075B1 publication Critical patent/EP2957075B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4004—Coupling between buses
    • G06F13/4022—Coupling between buses using switching circuits, e.g. switching matrix, connection or expansion network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/36—Handling requests for interconnection or transfer for access to common bus or bus system
    • G06F13/362—Handling requests for interconnection or transfer for access to common bus or bus system with centralised access control
    • G06F13/364—Handling requests for interconnection or transfer for access to common bus or bus system with centralised access control using independent requests or grants, e.g. using separated request and grant lines
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40006—Architecture of a communication node
    • H04L12/40019—Details regarding a bus master
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40143—Bus networks involving priority mechanisms
    • H04L12/4015—Bus networks involving priority mechanisms by scheduling the transmission of messages at the communication node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/40208—Bus networks characterized by the use of a particular bus standard
    • H04L2012/40234—Local Interconnect Network LIN
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/40267—Bus for use in transportation systems
    • H04L2012/40273—Bus for use in transportation systems the transportation system being a vehicle

Definitions

  • the invention relates to a master bus device for a motor vehicle, which is designed to exchange messages with slave bus devices via a vehicle communication bus of the motor vehicle.
  • the master bus device is designed in particular for a LIN bus (LIN - Local Interconnect Network).
  • the invention also includes a motor vehicle and a method for operating a master bus device.
  • a LIN bus messages are sent from the master bus device to the other bus subscribers, so the slave bus devices in predetermined time slots in a predetermined order.
  • the message type is also defined.
  • message type is meant here that a message is sent to a specific addressee with a very specific request, eg the request: sending or receiving data of a certain type, eg the current temperature.
  • the specifications for the transmission times and the message type are derived from a schedule, which is stored in a memory of the master bus device.
  • the flowchart is processed cyclically by a master bus device, ie after the end of the last step of the flowchart, the master bus device restarts again in the flowchart.
  • the schedule must be set at the time of development of the master bus device and stored in the memory.
  • the master bus device exchanges messages with the slave bus devices regarding the operation of the motor vehicle.
  • a slave bus device is, for example, a sensor
  • sensor data can be transmitted from the slave bus device to the master bus device by means of responsive messages.
  • the slave bus device an actuator, ie
  • a control unit with an attached motor for example, a sunroof it can be sent to activate by the master bus device by means of a corresponding message a control command.
  • the master bus device can exchange messages with the slave bus devices for diagnosis or reconfiguration of the slave bus devices. Therefore, in the flowchart of the master bus device, some transmission timings or timeslots in the flowchart must be reserved for such diagnosis communication with the slave bus device. These time slots are then not used in Normalbrete, ie the master bus device has here in normal operation of the motor vehicle here each a transmission break. Only during maintenance work in a workshop can it then happen that the master bus device uses the time slot for diagnostic communication. In that case, however, the remaining time slots for exchanging the measured data and control data are usually unused.
  • the ratio of messages for normal operation to messages for, for example, diagnostic communication is a matter of reconciliation.
  • a flowchart contains only one or two time slots for the diagnosis communication. Normally, there are two time slots, one for sending the diagnostic request and one for receiving the diagnostic response. A much larger number, typically 20 to 30, is intended for normal operation.
  • a workshop visit or in the development of a motor vehicle it may happen that, in the context of maintenance of a slave bus device, very large amounts of data have to be transferred from the master bus device to the slave bus device. This can be the case, for example, when re-programming a control device which is operated as a slave bus device.
  • the invention has for its object to use a vehicle communication bus through a schedule-controlled master bus device more efficient.
  • the master bus device is a development of a master bus device for a motor vehicle, which is designed to exchange messages with slave bus devices via a vehicle communication bus of the motor vehicle.
  • the master bus device is determined in the known manner by an operating schedule, which exchanges messages the master bus device with the slave bus devices.
  • the operating schedule is stored for this purpose in a memory of the master bus device.
  • the master bus device is a master bus device for a LIN bus, i. the messages exchanged over the LIN bus are then LIN messages, as known from the prior art per se from the LIN standard.
  • the master bus device has a further memory for storing a further flowchart and a switching device.
  • the further memory stores a maintenance schedule that is different from the operational schedule.
  • the switching device is configured to switch from the operating schedule to the maintenance schedule so that after the switchover, the maintenance schedule is used when exchanging messages.
  • the switching takes place in response to a control signal, which receives the master bus device from another device, such as a diagnostic device that is connected in a workshop to the car.
  • This further device is referred to as external device Transmitter designated because it is outside the master bus device.
  • the method also belonging to the invention specifies the operation of a master bus device accordingly.
  • messages are exchanged with slave bus devices based on an operation schedule. If a control signal from the off-board transmitter device is received by the master bus device, a maintenance mode is entered in which the operational schedule is deactivated and the maintenance schedule is activated, and so the master bus device reports messages based on the maintenance schedule exchanges the slave bus devices.
  • the invention thus has the advantage that, if necessary, e.g. For a re-programming large amounts of data can be transferred quickly via the communication bus to a particular slave bus device, while in a normal operation of a motor vehicle in contrast many individual, operated as slave bus devices ECUs can be addressed in short time intervals in a row. For this purpose, it is only necessary in the invention to provide two schedules accordingly, one for normal operation for exchanging many different messages in short time intervals, and one for maintenance for exchanging the large amount of data, i. for unidirectional transmission to a particular slave bus device.
  • the term "schedule” is generally understood to mean a data record which prescribes which messages (message type) the master bus device exchanges with slave bus devices via the vehicle communication bus. Exchanging is understood here to mean that the master bus device either receives data from or sends data to the slave bus devices.
  • the message type specifies the addressee or the addressee group and the data content to be exchanged for the respective message. If the messages are those for reading out data from the slave bus devices, this can be done according to the LIN standard.
  • the sequence of the messages to be exchanged and the respective time for sending out the corresponding message are preferably also defined by the operating and the maintenance schedule (time slot information). ment), that is, by the currently active flowchart, the master bus device is given a clocking for the transmission of messages or, in other words, the time slots for the transmission of messages. Depending on the data content read or sent, this is an application message for the normal operation of the motor vehicle or a diagnostic or configuration message for maintenance of one or more of the slave bus devices.
  • the messages for normal operation can now be summarized in the operating schedule and the messages for the maintenance and configuration mode in the maintenance schedule.
  • the operating schedule is thus preferably designed for normal operation of the motor vehicle, ie the operation during which a driver uses the car.
  • the operating schedule then preferably gives complete, but at least for the most part, only messages concerning the operation of the motor vehicle during normal operation, ie messages relating exclusively to the reading out of sensor data or the sending of control commands for the operation. This has the advantage that no or at least less time slots must be provided for the diagnostic communication in the operating schedule.
  • messages of a message type for the diagnostic communication are preferably summarized in the maintenance schedule which is designed for a maintenance operation of the motor vehicle, i. an operation in which at least one slave bus device is changed for maintenance or further development or during its manufacture.
  • the maintenance flowchart then has at least a predominant part, but preferably completely, only messages for a diagnosis and / or a data transmission of configuration data and / or an operating software to at least one of the slave bus devices.
  • the configuration data mentioned differ from the control data intended for normal operation in that they comprise parameter values for the configuration of an operating software, while the control data cause the activation of functionalities of a control unit.
  • the described maintenance schedule has the advantage that it can be dedicated exclusively to the transmission of such data, which during a maintenance of the motor vehicle or a reconfiguration in the frame a vehicle development or during the manufacture of a motor vehicle are necessary. This significantly speeds up these operations because most of the time slots in a cycle are dedicated to this communication in the flowchart.
  • a development of the master bus device provides for receiving the data record via a data input from a device-external data source, for example a programming device which was connected to the car in a workshop.
  • the data record can be, for example, replacement software for troubleshooting a software of a slave bus device.
  • a development of the master bus device provides that the maintenance flowchart provides messages for transmitting the data record by means of a predetermined transport protocol. Messages for a transport protocol according to the standard ISO 15765-2 are preferably specified here.
  • the maintenance schedule is designed to use a majority or all of the time slots of a cycle of the flowchart for the transmission of the data set.
  • a corresponding development of the master bus device comprises a receiving device for receiving a new maintenance schedule from a device-external transmitting device and for storing the received new maintenance schedule in the memory for the maintenance schedule.
  • the maintenance schedule should preferably be permanently stored in the master during the development time. It then only has to be switched over with a control signal between the flowcharts.
  • the master bus device also provides here to provide at least one further memory, each with a further maintenance schedule in the master bus device, in which case the conversion Switching device is designed to switch to one of the then then available maintenance schedules depending on the described control signal.
  • This refinement has the advantage that several maintenance flowcharts optimized for different situations can already be provided when the master bus device is manufactured.
  • the master bus device according to the invention, it is of course also provided in a corresponding manner to switch back to the operating schedule in response to a further control signal, so that again the operating schedule in the master bus device is effective. Additionally or alternatively, according to a further embodiment of the master bus device is provided to switch back from the maintenance schedule back to the operating schedule at a timeout. Thus, a time elapsed since switching to the maintenance schedule is detected and then switched back to the operation schedule if the detected time is greater than a predetermined threshold.
  • the threshold may, for example, have a value between 0.5 seconds and 20 seconds.
  • the invention also includes a motor vehicle.
  • the motor vehicle according to the invention has a vehicle communication bus to which an embodiment of the master bus device according to the invention is connected.
  • the invention also includes developments of the method according to the invention, which include method steps that have already been described in connection with the developments of the master bus device according to the invention. For this reason, the corresponding developments of the method according to the invention will not be described again here.
  • the single figure shows a schematic representation of an embodiment of the motor vehicle according to the invention.
  • the described components of the embodiment as well as the described steps of the method in each case constitute individual, independently of one another striving features of the invention, which each further independently develop the invention and thus individually or in any other than the combination shown are to be regarded as part of the invention.
  • the described embodiment can also be supplemented by further features of the invention already described.
  • a motor vehicle 10 is shown in a schematic representation, which may be, for example, a passenger car.
  • the motor vehicle 10 has a vehicle communication bus 12, which may be, for example, a LIN bus, via which messages are transmitted according to the LIN standard (as so-called LIN messages).
  • the communication on the vehicle communication bus, hereinafter bus 12 for short is controlled in the motor vehicle 10 by a master bus device or bus master 14 for short.
  • the bus master 14 exchanges the messages with slave bus devices, or slaves 16 for short.
  • the devices are all connected to the bus 12 for this purpose.
  • a slave device 16 can be, for example, a circuit with a sensor, for example a temperature sensor, or an actuator, for example a motor control for a window lifter.
  • a slave device 16 can also be a control device with its own operating software.
  • the bus master 14 is connected to the bus 12 via a bus connection 18.
  • the messages which the bus master 14 exchanges with the slave devices 16 via the bus 12 can be generated by a control device 20 of the bus master 14.
  • the control device 20 may be, for example, a microcontroller.
  • a message may be a transmission message with which the bus master 14 transmits data to one or more of the slave devices 16.
  • a message may also be a read message by which the bus master 14 causes one or more of the slave devices 16 to send data over the bus 12 to the bus master 14.
  • the bus master 14 cyclically repeatedly exchanges messages of the same type in a predetermined sequence and at predetermined times with the slave devices 16.
  • a transmission message is sent.
  • a slave device with a temperature sensor can therefore be repeatedly cyclically prompted by the bus master 14 at specific times to send a current temperature value to the bus master 14.
  • the bus device 14 has two flowcharts, namely, an operational flowchart 22 and a maintenance flowchart 24.
  • the operational flowchart 22 is designed for an application mode of the master device 14 and determines an order and timing (transmission time slots) for messages as appropriate are to exchange the sensor data or control data with the slave devices 16 in a normal operation of the motor vehicle, so for example while driving, as required for a smooth operation of the motor vehicle 10.
  • the operational flowchart 22 may be optimized in such a way that no messages, i. no time slots are reserved for messages that do not have to be exchanged during normal operation of the motor vehicle, for example, diagnostic messages or configuration messages for setting the operating behavior of the slave devices 16.
  • the maintenance schedule 24 may be provided, which may have a correspondingly high number and dense sequence of messages for the maintenance and configuration of the slave devices 16.
  • the maintenance schedule 24 may be optimized to be exclusively for maintenance and reconfiguration. In other words, during a drive of the motor vehicle 10 using the maintenance schedule 24, an operation of the slave devices 16 would be impossible or at least impaired.
  • the operating schedule 22 and the maintenance schedule 24 are each stored in a memory 26, 28.
  • the memories 26, 28 may, for example, also be different memory areas of a non-volatile memory, for example a flash memory, EEPROM or a hard disk.
  • the control device 20 is coupled via a switching device 30 with the memories 26, 28.
  • the switching device 30 may also be part of the mentioned microcontroller.
  • the switching device 30 may be, for example, a program module in an operating program of the microcontroller. For the further explanation of the exemplary embodiment, it is assumed that the motor vehicle 10 has been brought into a workshop in order to check or re-adjust the functioning of the slave devices 16.
  • a driver of the motor vehicle 10 may have found that he has difficulties with the operation of one of the slave devices 16, for example, the operation of a control unit for a sunroof.
  • the motor vehicle 10 may also be a prototype which is under development.
  • the motor vehicle 10 is regularly brought to the workshop after test drives in order to reprogram the slave devices 16 (re-programming).
  • a vehicle-external control unit 32 to a control interface 34 and a data input 36 of the bus master 14 are connected.
  • the control device 32 is a transmitting device which can switch the switching device 30 via the control interface 34 by means of a control signal, so that the operating schedule 32 for the definition of the messages generated by the control device 20 is no longer active, rather than the maintenance flowchart 24 is.
  • the controller 32 may be, for example, a tester for motor vehicle diagnostics and need not be connected to the bus 12.
  • control unit 32 is to transmit new operating software 38 for one of the slave devices 16 via the bus master 14 and the bus 12 to the slave device 16 and to write it to a memory there.
  • This process is also called flashing.
  • the operation of the bus master 14 on the basis of the maintenance schedule 24 results in a communication channel to the slave devices 16 for the control device 32, which is much broader in bandwidth for the transmission of the operating software 38 and other data than a conventional flowchart in which Both for operating purposes of the motor vehicle 10 and for maintenance purposes, transmission times and message types must be provided.
  • the communication channel allows the controller 32 to communicate with the slave devices 16 via the data input 36 and the bus connector 18.
  • an application mode results in the bus master. in which the operating schedule 22 is active and thereby messages are exchanged for the intended operation of the slave devices 16 via the bus 12 at short intervals in succession, and a flash mode for generating a plurality of similar messages for transmitting large data sets, such as the operating software 38.
  • the memories 26, 28 can also be provided separately in the motor vehicle 10 outside the bus master 14. It can also be provided that the control device 32 has the memory 28 and transmits the maintenance flowchart 24 to the bus master 14 after connection of the control device 32 to the latter.
  • the controller 32 may send an explicit command to switch over the control interface 34 to the switching device 30.
  • large amounts of data such as the operating software 38, can then be quickly transferred via the bus 12 to the slave device 16. Subsequently, the controller 32 can switch back from the flash mode to the mode for the transmission of different messages in quick succession by a further explicit command for switching to the application mode.
  • the switching device 30 can also be used to measure the time that has elapsed since switching from the application mode to the flash mode. At a timeout and simultaneous inactive communication of the bus master 14 can then be switched by the switching device 30 independently of the flash mode back into the application mode.
  • the example shows how a period of time required for re-programming a slave device in a motor vehicle can be shortened by having the bus master of the vehicle communication bus have two different schedules for message exchange over the vehicle communication bus.
  • One of the schedules is designed for normal operation, while the other is optimized for the exchange of data, for example, operating software for the slaves.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mathematical Physics (AREA)
  • Computer Hardware Design (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne un appareil de bus maître (14), destiné à un véhicule à moteur (10), qui est adapté pour échanger des informations avec des appareils de bus esclaves (16) par l'intermédiaire d'un bus de communication embarqué (12) du véhicule à moteur (10). Dans l'appareil de bus maître (14), un programme de fonctionnement (22) stocké dans une mémoire (26) de l'appareil de bus maître (14) détermine les informations que l'appareil de bus maître (14) échange avec les appareils de bus esclaves (16). L'invention a pour but de permettre à l'appareil de bus maître (14) commandé par programme d'exploiter plus efficacement le bus de communication embarqué (12). Pour cela, l'appareil de bus maître (14) comporte un système de commutation (30) adapté pour recevoir un signal de commande venant d'un dispositif émetteur (32) extérieur à l'appareil et, en fonction de ce signal de commande, pour basculer de la mémoire (26) contenant le programme de fonctionnement (22) à une autre mémoire (28) contenant un programme de maintenance (24) différent du programme de fonctionnement (22) et pour définir ainsi le programme de maintenance (24) en tant que programme utilisé lors de l'échange des informations.
EP14709182.1A 2013-02-15 2014-01-24 Appareil maître pour bus de communication embarqué d'un véhicule à moteur Active EP2957075B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102013002648.2A DE102013002648B3 (de) 2013-02-15 2013-02-15 Master-Busgerät für einen Fahrzeugkommunikationsbus eines Kraftwagens
PCT/EP2014/000178 WO2014124731A1 (fr) 2013-02-15 2014-01-24 Appareil maître pour bus de communication embarqué d'un véhicule à moteur

Publications (2)

Publication Number Publication Date
EP2957075A1 true EP2957075A1 (fr) 2015-12-23
EP2957075B1 EP2957075B1 (fr) 2017-01-18

Family

ID=50241357

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14709182.1A Active EP2957075B1 (fr) 2013-02-15 2014-01-24 Appareil maître pour bus de communication embarqué d'un véhicule à moteur

Country Status (5)

Country Link
US (1) US9715471B2 (fr)
EP (1) EP2957075B1 (fr)
CN (1) CN104798345B (fr)
DE (1) DE102013002648B3 (fr)
WO (1) WO2014124731A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SE524201C2 (sv) * 2002-12-17 2004-07-06 Lars-Berno Fredriksson Anordning vid distribuerat styr- och övervakningssystem
DE102017200669A1 (de) * 2017-01-17 2018-07-19 Robert Bosch Gmbh Verfahren und Vorrichtung zum Betreiben eines Steuergeräts, Computerprogramm und Verfahren zum Generieren des Computerprogramms
DE102017211721B4 (de) * 2017-07-10 2021-09-09 Continental Automotive Gmbh Masterkommunikationseinrichtung und Ethernet-Netzwerk zum Betreiben eines Ethernet-Netzwerkes
US11463555B2 (en) * 2020-08-04 2022-10-04 Nxp B.V. Local interconnect network (LIN) messaging between LIN partitions separated by a backbone communication network
DE102020215329A1 (de) 2020-12-03 2022-06-09 Continental Automotive Gmbh Verfahren zum schnellen Flashen von Sensorknoten über ein Ethernetnetzwerk

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4142493A (en) * 1977-09-29 1979-03-06 The Bendix Corporation Closed loop exhaust gas recirculation control system
US5506844A (en) * 1994-05-20 1996-04-09 Compression Labs, Inc. Method for configuring a statistical multiplexer to dynamically allocate communication channel bandwidth
DE19530719A1 (de) * 1995-08-18 1997-02-20 Kiekert Ag Verfahren zum Betrieb einer elektrischen Steuerungsanlage für ein Kraftfahrzeug mit einer Werkstattbetriebsweise
US5854978A (en) * 1996-04-16 1998-12-29 Nokia Mobile Phones, Ltd. Remotely programmable mobile terminal
US6385198B1 (en) * 1998-06-11 2002-05-07 Synchrodyne Networks, Inc. Signaling for timely forwarding in packet switching network with a common time reference
US6665601B1 (en) * 1998-12-22 2003-12-16 Case Corporation Communications system for managing messages across a vehicle data bus
DE19939568C1 (de) 1999-08-20 2001-02-08 Pilz Gmbh & Co Verfahren zur Einstellung einer Datenübertragungsrate in einem Feldbussystem
DE10000302B4 (de) 2000-01-05 2011-08-11 Robert Bosch GmbH, 70469 Verfahren und Vorrichtung zum Austausch von Daten zwischen wenigstens zwei mit einem Bussystem verbundenen Teilnehmern
US7218637B1 (en) * 2001-07-20 2007-05-15 Yotta Networks, Llc System for switching data using dynamic scheduling
US7272309B1 (en) * 2002-05-08 2007-09-18 Yotta Networks, Llc System and method of routing data at a photonic core
JP2004349802A (ja) * 2003-05-20 2004-12-09 Sharp Corp Ｉｐ電話装置
DE102004026994B3 (de) 2004-06-03 2005-12-01 Siemens Ag Minimierung von Kommunikationsunterbrechungen in einem Kommunikationssystem
US7788418B2 (en) 2005-06-01 2010-08-31 Siemens Ag Measurement or protective device with independent software modules
DE102006032217A1 (de) * 2006-07-12 2008-01-24 Robert Bosch Gmbh Verfahren zum Betreiben eines LIN-Busses
EP2129045B1 (fr) * 2006-12-27 2015-05-20 Kabushiki Kaisha Yaskawa Denki Système de communication maître-esclave et procédé de communication maître-esclave
KR100900882B1 (ko) * 2007-06-11 2009-06-04 성균관대학교산학협력단 상호 상이한 복수의 네트워크 프로토콜을 사용하는 차량에적용되는 게이트웨이 디바이스, 네트워크 시스템 및 데이터변환방법
US8209076B2 (en) * 2008-10-06 2012-06-26 International Business Machines Corporation Tracking vehicle maintenance using sensor detection
DE102010023071B4 (de) 2009-10-01 2017-10-19 Volkswagen Ag Verfahren und Netzknoten zur Übertragung ereignisgesteuerter Botschaften
US9481304B2 (en) * 2010-05-24 2016-11-01 Magna Mirrors Of America, Inc. Automotive exterior mirror heater control
DE102010039488B4 (de) 2010-08-18 2012-06-06 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Zeit- und Prioritäts-gesteuerter Sende/Empfangsknoten
DE102010040785A1 (de) 2010-09-15 2012-03-15 Bayerische Motoren Werke Aktiengesellschaft Datenübertragungsverfahren und Vorrichtung
DE102011012572B3 (de) * 2011-02-26 2012-03-08 Audi Ag Kraftfahrzeug mit einem FlexRay-Bus
JP2013030906A (ja) * 2011-07-27 2013-02-07 Fujitsu Ltd プログラマブルロジックデバイス
DE102011117083A1 (de) * 2011-10-27 2013-05-02 Volkswagen Aktiengesellschaft Slave-Steuergerät und Verfahren zur Programmierung eines Slave-Steuergeräts
DE102011085764A1 (de) * 2011-11-04 2013-05-08 Robert Bosch Gmbh Verfahren zum Betreiben einer Busanordnung
CN202424755U (zh) * 2011-12-30 2012-09-05 上海博泰悦臻电子设备制造有限公司 车机数据通讯装置
US9092307B2 (en) * 2012-10-09 2015-07-28 Oracle International Corporation Adaptive preventive maintenance for computing systems
CN102857397B (zh) * 2012-10-09 2015-10-28 南京国电南自电网自动化有限公司 一种多主异步双工差分总线及通讯方法
US9576259B2 (en) * 2013-08-13 2017-02-21 Siemens Industry, Inc. Systems, methods and apparatus for optimizing fuel mix, fuel allocation and scheduling of generator resources

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2014124731A1 *

Also Published As

Publication number Publication date
EP2957075B1 (fr) 2017-01-18
US9715471B2 (en) 2017-07-25
CN104798345B (zh) 2017-12-15
US20150356043A1 (en) 2015-12-10
WO2014124731A1 (fr) 2014-08-21
DE102013002648B3 (de) 2014-05-22
CN104798345A (zh) 2015-07-22

Similar Documents

Publication Publication Date Title
EP3669550B1 (fr) Procédé pour faire fonctionner un ensemble de détection dans un véhicule à moteur sur la base d'un protocole dsi
EP2957075B1 (fr) Appareil maître pour bus de communication embarqué d'un véhicule à moteur
WO2005064546A1 (fr) Enregistrement de donnees dans une automobile
EP2957074B1 (fr) Véhicule à moteur équipé d'un bus de communication embarqué et procédé de génération d'informations de bus
EP1796051B1 (fr) Dispositifs de diagnostic dans un véhicule doté d'une unité d'informations de diagnostic pour un module de diagnostic
EP1979790B1 (fr) Procédé et dispositif d'attribution d'adresses dans un système comportant plusieurs unités de générateur disposées de façon parallèle
DE10219832A1 (de) Verfahren zum Kodieren von Steuergeräten in Verkehrsmitteln
DE102006023274A1 (de) Verfahren und Vorrichtung zum Steuern von Netzwerksegmenten eines Netzwerks in einem Kraftfahrzeug
DE102014001462A1 (de) Feldbusmodul, Maschinensteuerung und Verfahren zur Parametrierung eines, insbesondere sicherheitsgerichteten, Feldbusmoduls
DE102005038183A1 (de) Verfahren zum Betreiben eines Netzwerks
EP3298730B1 (fr) Système de bus et procédé d'attribution d'adresses à des abonnés d'un système de bus
DE102013105097A1 (de) Steuerungseinrichtung und Verfahren zum Umschalten von Ein-/Ausgabeeinheiten einer Steuerungseinrichtung
EP1979793B1 (fr) Procédé et dispositif d'attribution d'adresses dans un système comportant plusieurs unités de générateur disposées de façon parallèle
EP2133255B1 (fr) Commande de véhicule ferroviaire avec deux systèmes de transmissions de données différents
DE102009005399A1 (de) Verfahren und Kommunikationssystem zum Konfigurieren eines einen Logikbaustein enthaltenden Kommunikationsmoduls
EP3647794B1 (fr) Procédé de commande d'une communication entre une unité d'enregistrement et un capteur de vitesse d'un système de tachygraphe d'un véhicule automobile, ainsi qu'un système de tachygraphe correspondant et unité d'enregistrement pour le système de tachygraphe
EP3132322B1 (fr) Procédé de diagnostic d'un système de véhicule automobile, appareil de diagnostic d'un système de véhicule automobile, appareil de commande d'un système de véhicule automobile et véhicule automobile
DE102019132428A1 (de) Funktionsorientierte Elektronik-Architektur
EP2533113B1 (fr) Procédé destiné au fonctionnement d'un appareil d'automatisation
DE102016003013A1 (de) Überwachungsvorrichtung und Verfahren zum Überwachen eines Betriebs eines Steuergeräts eines Kraftfahrzeugs
EP3808038A1 (fr) Procédé destiné à faire fonctionner un système de capteurs dans un véhicule automobile sur la base d'un protocole dsi
EP2911309B1 (fr) Appareil radio et procédé de transmission d'informations
DE102015106378A1 (de) Vorrichtung und Verfahren zum Übertragen und Empfangen von Parametern
DE102009004327A1 (de) Bussystem für ein Fahrzeug und Verfahren zum Betreiben eines Bussystems
DE112018007474T5 (de) Übertragungssystem und übertragungsverfahren

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20150915

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20161014

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 4

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 863457

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170215

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 502014002510

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20170118

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170131

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170419

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170418

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170518

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170518

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170418

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 502014002510

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170131

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170131

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170124

26N No opposition filed

Effective date: 20171019

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 5

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20170131

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170124

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20140124

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 863457

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190124

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190124

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170118

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230125

Year of fee payment: 10

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230530

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240131

Year of fee payment: 11

Ref country code: GB

Payment date: 20240124

Year of fee payment: 11