EP2443798A1 - Procédé de mise en uvre d'un système de bus, en particulier d'un bus can - Google Patents
Procédé de mise en uvre d'un système de bus, en particulier d'un bus canInfo
- Publication number
- EP2443798A1 EP2443798A1 EP10723596A EP10723596A EP2443798A1 EP 2443798 A1 EP2443798 A1 EP 2443798A1 EP 10723596 A EP10723596 A EP 10723596A EP 10723596 A EP10723596 A EP 10723596A EP 2443798 A1 EP2443798 A1 EP 2443798A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- identifier
- stations
- station
- message
- bus system
- 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.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- 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
-
- 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/40215—Controller Area Network CAN
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0681—Configuration of triggering conditions
Definitions
- CAN Controller Area Network
- every transmitted message contains a so-called
- the stations connected to the CAN bus decide whether the transmitted message is relevant for them.
- the identifier is added by the transmitting station to the user data to be transmitted.
- Each station can send any number of messages with different identifiers. However, each identifier may only be used by a specific station or the same identifier may not be added to a message by different stations.
- a CAN bus is designed so that new stations can be connected without much effort. Among other things, in this way it is possible that an identifier that is already being used by an existing station is also erroneously used by another, for example, newly added station.
- the object of the invention is errors in connection with the use of
- the invention solves this problem by a method according to claim 1.
- a particular identifier may only ever be used by a single station.
- Each of the stations compares the identifier of a transmitted message with the identifiers used by itself. If there is a match, an error message is generated.
- Message with a specific identifier can only come from a single station.
- Figure 1 shows a schematic block diagram of an embodiment of a bus system according to the invention
- Figure 2 shows a schematic representation of a message in the bus system of Figure 1
- Figure 3 shows
- the bus system 10 of FIG. 1 is designed as a serial bus system, to which, for example, four stations 11, 12, 13, 14 are connected. If the bus system 10 is used, for example, in a motor vehicle, the stations 11, 12, 13, 14 may be, for example, a motor control and / or a drive control or the like.
- the stations 1 1, 12, 13, 14 of the bus system 10 are formed gleich Schltigt each other and can send and receive messages 20. The structure of such a message 20 will be described in more detail below with reference to FIG. At any given time, only one of the stations 1 1, 12, 13, 14 can access the bus system 10 and send its message 20. The transmitted message 20 can then be received by all other stations 11, 12, 13, 14 and processed if necessary.
- Each message 20 transmitted via the bus system 10 has a predetermined value
- FIG. 2 shows a detail of such a message 20.
- the message 20 contains at least a so-called ldentifier IDENT and the user data DATA to be transmitted.
- the identifier IDENT and the user data DATA are generated by the transmitting station.
- the identifier IDENT may be 11 bits or 29 bits long.
- Each of the stations 11, 12, 13, 14 can send any number of messages 20 with different identifiers IDENT.
- the non-sending stations then decide on the basis of the ldentifiers IDENT whether the received
- Message 20 is relevant to you or not. If the message 20 is relevant for one of the stations 11, 12, 13, 14, the message 20 is read in by this station and processed.
- Identifier IDENT It is essential that a specific Identifier IDENT can only ever be sent from a single station. This means that a given identifier always represents a unique reference to a single particular station. In other words, one and the same Identifier IDENT must not be used by two different stations.
- the station 1 1 sends messages with the identifier IDENT1, the station 12 messages with the identifier IDENT2 and the station 13 messages with the identifier IDENT3. It is further assumed that the station 14 - erroneously - sends messages with the identifier IDENT2. This error can not be detected by the stations 1 1, 13, since there is always assumed that the IDENT2 due to the ldentifiers associated message comes from the station 12, so even if it is the - erroneous - message from the station 14.
- the method 30 of FIG. 3 is provided. This method 30 is performed continuously by each of the stations 11, 12, 13, 14.
- the basis of the method 30 is a list stored in the respective station, in which all identifier identifiers are used, which are used by the respective station, and which must therefore not be used by other stations for sending messages.
- the method 30 will be explained below with reference to the illustrated example scenario in which the station 14 erroneously uses the identifier IDENT2, which may only be used by the station 12.
- the station 12 If the station 12 is in a state in which it is not transmitting, the station 12 reads in a first step 31 at least the identifier IDENT of those messages 20 which are transmitted by other stations via the bus system 10. In a subsequent step 32, the station 12 compares the read-in identifier IDENT with the identifiers stored in its own list. Since, as explained, the station 12 uses at least the identifier IDENT2, at least this identifier IDENT2 is contained in the list of the station 12.
- the station 12 thus compares the IDentifier IDENT read by the bus system 10 with the stored identifier IDENT2. If the read ldentifier IDENT is the ldentifier IDENT2 erroneously used by the station 14, the station 12 determines a match with the stored ldentifier IDENT2.
- the station 12 generates an error message in a step 33 and sends this error message via the bus system to all other stations.
- the error at all stations 11, 12, 13, 14 known and can then be remedied example of the fault-acting station 14.
- station 14 may also be the station that determines the use of identifier IDENT2 by station 12. In this case, the station 14 generates the error message according to step 33 of the method 30. When troubleshooting must then first be checked which station is working incorrectly. It is also understood that the method 30 of FIG. 3 intervenes even if more than two stations send the same identifiers.
- the method 30 is performed continuously by all stations 11, 12, 13, 14. Each of the stations 11, 12, 13, 14 thus compares the identifier IDENT of a transmitted message 20 with the identifier IDENTx used by itself. If - for whatever reason - any identifier IDENTx of two different stations is used, then this is detected at the latest then by one of the two stations using the method 30 when the other station for the first time the already occupied identifier IDENTx in the context of a message 20 shipped. The error can then be reported and corrected.
- the method 30 is executed by means of a computer program.
- the computer program is stored in the individual stations 11, 12, 13, 14 on an electronic memory and is processed by an electronic computer.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Small-Scale Networks (AREA)
Abstract
La présente invention concerne un procédé de mise en œuvre d'un système de bus (10), en particulier d'un bus CAN, auquel il est possible de raccorder plusieurs postes (11, 12, 13, 14). Tout message transitant par ce système de bus (10) est pourvu d'un identifiant, un même identifiant (p.ex.: IDENT2) devant toujours être utilisé que par un seul et même poste (p.ex.: 12). Chacun des postes compare l'identifiant du message transmis aux identifiants qu'il a lui-même utilisés (p.ex.: IDENT2). En cas de concordance, il y a production d'un message d'erreur.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102009026995A DE102009026995A1 (de) | 2009-06-17 | 2009-06-17 | Verfahren zum Betreiben eines Bussystems, insbesondere eines CAN-Busses |
PCT/EP2010/058147 WO2010145985A1 (fr) | 2009-06-17 | 2010-06-10 | Procédé de mise en œuvre d'un système de bus, en particulier d'un bus can |
Publications (1)
Publication Number | Publication Date |
---|---|
EP2443798A1 true EP2443798A1 (fr) | 2012-04-25 |
Family
ID=42340787
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP10723596A Withdrawn EP2443798A1 (fr) | 2009-06-17 | 2010-06-10 | Procédé de mise en uvre d'un système de bus, en particulier d'un bus can |
Country Status (6)
Country | Link |
---|---|
US (1) | US8799520B2 (fr) |
EP (1) | EP2443798A1 (fr) |
CN (1) | CN102804698B (fr) |
DE (1) | DE102009026995A1 (fr) |
RU (1) | RU2568774C2 (fr) |
WO (1) | WO2010145985A1 (fr) |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2982066B1 (fr) * | 2011-10-28 | 2013-12-20 | Peugeot Citroen Automobiles Sa | Procede de compensation de la corruption d'une memoire d'un calculateur electronique. |
DE102011089587A1 (de) * | 2011-12-22 | 2013-06-27 | Robert Bosch Gmbh | Teilnehmerstation eines Bussystems und Verfahren zur Übertragung von Nachrichten zwischen Teilnehmerstationen eines Bussystems |
DE102012224234A1 (de) * | 2012-12-21 | 2014-06-26 | Continental Teves Ag & Co. Ohg | Verfahren zur Kontrolle von Daten-Frames mit redundantem Identifikator auf einem Datenbus sowie Datenbus-Schnittstellenmodul |
BR112015008318A2 (pt) | 2013-09-23 | 2017-07-04 | Farmobile Llc | dispositivo de retransmissão, e, sistemas de troca de dados de agricultura e de servidor |
DE102015219996A1 (de) | 2015-10-15 | 2017-04-20 | Robert Bosch Gmbh | Verfahren und Vorrichtung zum Abwehren einer Manipulation an einem CAN-Bus durch einen mittels eines CAN-Controllers an den Bus angebundenen Knoten |
US20170213043A1 (en) * | 2016-01-27 | 2017-07-27 | Mentor Graphics Corporation | Security hardened controller area network transceiver |
DE102016212816A1 (de) | 2016-07-13 | 2018-01-18 | Robert Bosch Gmbh | Verfahren und Vorrichtung zum Betreiben eines Bussystems |
DE102016214279A1 (de) | 2016-08-02 | 2018-02-08 | Robert Bosch Gmbh | Verfahren und Vorrichtung zum Betreiben eines Bussystems |
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 |
DE102017209557A1 (de) * | 2017-06-07 | 2018-12-13 | Robert Bosch Gmbh | Verfahren zum Schutz eines Fahrzeugnetzwerks gegen manipulierte Datenübertragung |
DE102017209556A1 (de) | 2017-06-07 | 2018-12-13 | Robert Bosch Gmbh | Verfahren zum Schutz eines Fahrzeugnetzwerks gegen manipulierte Datenübertragung |
CN110753912A (zh) | 2017-06-23 | 2020-02-04 | 罗伯特·博世有限公司 | 用于通过检查通信中的异常来检测车辆的通信系统中的中断的方法 |
DE102017210787A1 (de) | 2017-06-27 | 2018-12-27 | Robert Bosch Gmbh | Verfahren und Vorrichtung zum Ermitteln von Anomalien in einem Kommunikationsnetzwerk |
DE102017213119A1 (de) | 2017-07-31 | 2019-01-31 | Robert Bosch Gmbh | Verfahren und Vorrichtung zum Ermitteln von Anomalien in einem Kommunikationsnetzwerk |
DE102018210744A1 (de) * | 2018-06-29 | 2020-01-02 | Robert Bosch Gmbh | Verfahren zum Identifizieren eines Netzwerkknotens in einem Kommunikationsnetzwerk und Kommunikationsnetzwerk |
DE102018217964A1 (de) | 2018-10-19 | 2020-04-23 | Robert Bosch Gmbh | Verfahren und Vorrichtung zur Überwachung einer Datenkommunikation |
CN109542806B (zh) * | 2018-11-27 | 2020-07-24 | 湖南中联重科智能技术有限公司 | 总线数据解析方法、装置及存储介质 |
DE102019001978A1 (de) * | 2019-03-21 | 2020-10-08 | Volkswagen Aktiengesellschaft | Verfahren zur Überwachung der Kommunikation auf einem Kommunikationsbus, elektronische Vorrichtung zum Anschluss an einen Kommunikationsbus sowie Fahrzeug |
DE102020212452B3 (de) | 2020-10-01 | 2022-01-13 | Volkswagen Aktiengesellschaft | Verfahren zur Reduzierung der Auswirkungen von einer auf einem Kommunikationsbus eingeschleusten Botschaft |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS6215950A (ja) * | 1985-07-15 | 1987-01-24 | Canon Inc | デ−タ伝送制御方式 |
CA2047321C (fr) * | 1990-07-19 | 1997-11-18 | Henry Yang | Recherche des stations a deux adresses dans un reseau de communication |
US5327534A (en) | 1990-07-30 | 1994-07-05 | Digital Equipment Corporation | Detection of duplicate alias addresses |
US6587968B1 (en) * | 1999-07-16 | 2003-07-01 | Hewlett-Packard Company | CAN bus termination circuits and CAN bus auto-termination methods |
US6654355B1 (en) * | 1999-12-14 | 2003-11-25 | Schneider Automation Inc. | Bridge for CAN to TCP/IP connection |
US6273771B1 (en) * | 2000-03-17 | 2001-08-14 | Brunswick Corporation | Control system for a marine vessel |
WO2002025859A1 (fr) * | 2000-09-12 | 2002-03-28 | Kvaser Consultant Ab | Agencement avec un nombre d'unites pouvant communiquer entre elles via un systeme de connexion sans fil et procede de mise en oeuvre avec un tel systeme |
SE0003217L (sv) * | 2000-09-12 | 2002-03-05 | Kvaser Consultant Ab | Arrangemang för att i distribuerat styrsystem höja framkomligheten för data och/eller styrkommandon |
US7747747B1 (en) * | 2002-05-06 | 2010-06-29 | Apple Inc. | Method and arrangement for supressing duplicate network resources |
JP5308802B2 (ja) * | 2008-12-16 | 2013-10-09 | ルネサスエレクトロニクス株式会社 | Canノード |
-
2009
- 2009-06-17 DE DE102009026995A patent/DE102009026995A1/de active Pending
-
2010
- 2010-06-10 WO PCT/EP2010/058147 patent/WO2010145985A1/fr active Application Filing
- 2010-06-10 CN CN201080026985.5A patent/CN102804698B/zh active Active
- 2010-06-10 EP EP10723596A patent/EP2443798A1/fr not_active Withdrawn
- 2010-06-10 US US13/379,011 patent/US8799520B2/en active Active
- 2010-06-10 RU RU2012101207/08A patent/RU2568774C2/ru active
Non-Patent Citations (2)
Title |
---|
None * |
See also references of WO2010145985A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO2010145985A1 (fr) | 2010-12-23 |
CN102804698A (zh) | 2012-11-28 |
CN102804698B (zh) | 2015-12-02 |
US8799520B2 (en) | 2014-08-05 |
US20120210178A1 (en) | 2012-08-16 |
RU2012101207A (ru) | 2013-07-27 |
RU2568774C2 (ru) | 2015-11-20 |
DE102009026995A1 (de) | 2011-03-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2010145985A1 (fr) | Procédé de mise en œuvre d'un système de bus, en particulier d'un bus can | |
DE102006018163B4 (de) | Verfahren zur automatischen Adressvergabe | |
EP2090031B1 (fr) | Procédé et installation de communication sur un bus lin | |
DE102009030774A1 (de) | Verfahren zur rechnergestützten Erfassung von Fehlern beim Ablauf von einem oder mehreren softwarebasierten Programmen in einem System aus Komponenten | |
EP3523703A1 (fr) | Procédé d'actualisation de logiciel pour des passerelles vers le cloud, programme informatique ayant une implémentation dudit procédé et unité de traitement pour mettre en oeuvre ledit procédé | |
EP0974901B1 (fr) | Méthode de détermination d'une vue globale homogène des états d'un réseau d'ordinateurs distribué | |
DE102014111361A1 (de) | Verfahren zum Betreiben einer Sicherheitssteuerung und Automatisierungsnetzwerk mit einer solchen Sicherheitssteuerung | |
DE102011081477A1 (de) | Stellwerksrechner | |
DE102016102282B4 (de) | Verfahren und Vorrichtung zum Überwachen einer Datenverarbeitung und -übertragung in einer Sicherheitskette eines Sicherheitssystems | |
DE102012022299A1 (de) | BUS-System, Verfahren zum Betrieb eines BUS-Systems und fluidisches System mit einem BUS-System | |
DE102014105207A1 (de) | Verfahren zum Betreiben eines Kommunikationsnetzwerks und Kommunikationsnetzwerk | |
DE102010003448A1 (de) | Adressierungsverfahren und Kommunikationsnetzwerk mit einem solchen Adressierungsverfahren | |
DE102013211772A1 (de) | Verfahren und Vorrichtung zum Austausch von Daten in einem Kraftfahrzeug zum Betreiben eines Aktors, vorzugsweise einer automatisierten Reibungskupplung und/oder eines automatisierten Getriebes | |
BE1025127B1 (de) | Kommunikationssystem zur seriellen Kommunikation zwischen Kommunikationsgeräten | |
EP2418580A1 (fr) | Procédé destiné au fonctionnement d'un réseau et réseau | |
WO2011072958A1 (fr) | Procédé d'attribution d'une adresse d'interrogation à un appareil de terrain | |
DE10121061B4 (de) | Überwachungsvorrichtung und Überwachungsverfahren | |
DE112013006760T5 (de) | Ablaufsteuerungssystem und Adresseneinstellungsverfahren | |
EP3096970B1 (fr) | Procédé de fonctionnement d'un réseau haute tension d'un véhicule à moteur et véhicule à moteur | |
DE102020206262A1 (de) | Datenumschreibverfahren und Datenumschreibsystem | |
EP2449438A1 (fr) | Procédé et système pour commander au moins un actionneur | |
EP3779797A1 (fr) | Procédé d'entretien anticipé assisté par ordinateur d'un système technique | |
DE102021004815B3 (de) | Verfahren zum Betreiben einer technischen Anlage und technische Anlage | |
DE102016013669A1 (de) | Verfahren zum Betrieb eines Datenkommunikationssystems | |
WO2006061033A1 (fr) | Procede de mise en memoire structuree d'enregistrements de defaillances |
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: 20120117 |
|
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 SE SI SK SM TR |
|
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20170130 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20170610 |