[go: up one dir, main page]

WO1999034560A1 - Interface pour plusieurs reseaux de traitement de donnees can et procede permettant d'exploiter une interface de ce type - Google Patents

Interface pour plusieurs reseaux de traitement de donnees can et procede permettant d'exploiter une interface de ce type Download PDF

Info

Publication number
WO1999034560A1
WO1999034560A1 PCT/EP1998/008431 EP9808431W WO9934560A1 WO 1999034560 A1 WO1999034560 A1 WO 1999034560A1 EP 9808431 W EP9808431 W EP 9808431W WO 9934560 A1 WO9934560 A1 WO 9934560A1
Authority
WO
WIPO (PCT)
Prior art keywords
memory
interface
interface according
input
central
Prior art date
Application number
PCT/EP1998/008431
Other languages
German (de)
English (en)
Inventor
Rolf Wilhelm Kemper
Ralf Usling
Jens Kurt Eltze
Original Assignee
Nec Electronics (Europe) Gmbh
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 Nec Electronics (Europe) Gmbh filed Critical Nec Electronics (Europe) Gmbh
Publication of WO1999034560A1 publication Critical patent/WO1999034560A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4604LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462LAN interconnection over a bridge based backbone
    • H04L12/4625Single bridge functionality, e.g. connection of two networks over a single bridge
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L12/407Bus networks with decentralised control
    • H04L12/413Bus networks with decentralised control with random access, e.g. carrier-sense multiple-access with collision detection [CSMA-CD]
    • H04L12/4135Bus networks with decentralised control with random access, e.g. carrier-sense multiple-access with collision detection [CSMA-CD] using bit-wise arbitration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L2012/40208Bus networks characterized by the use of a particular bus standard
    • H04L2012/40215Controller Area Network CAN
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/35Switches specially adapted for specific applications
    • H04L49/351Switches specially adapted for specific applications for local area network [LAN], e.g. Ethernet switches

Definitions

  • the invention relates to an interface (controller) according to the preamble of claim 1 and a method for operating the interface.
  • Data processing systems with distributed computer nodes that are connected via a serial data bus are mainly used in industrial and automotive local networks.
  • the computer nodes include data processing devices or signal processing devices that are designed for a specific application. This includes data exchange between control units, sensors and actuators.
  • CAN Controller Area Network
  • 2nd OB 2nd OB
  • Each CAN unit ie each computer node, is connected to all other computer nodes via a serial data bus, and essentially two different "levels" are defined for CAN, namely a protocol level and one, for the exchange or management and processing of data Object level.
  • Data is exchanged between the CAN units in the form of so-called "notification objects".
  • In this case includes a "Communication object" in addition to the actual data to be processed, yet '' for example, an identification field (ID), status fields, fields for clock control, etc.
  • ID identification field
  • the term "level” both an implementation by software than also through hardware as well as through combinations of both.
  • 1 shows the schematic structure of a CAN unit.
  • the protocol level 1 is shown, which is connected to an external CAN bus 5 and is responsible for the correct handling of data on the CAN bus.
  • message objects are checked for correct data format, and incoming message objects are converted from serial data format to parallel data format.
  • the adjoining object level 2 is used for filtering data, and in particular for data management, and forms the interface between the protocol level and a CAN memory 3.
  • the object level takes over the data management and the storage of data and outputs the necessary data to a memory 3 control unit, not shown.
  • the CAN memory 3 is normally connected directly to the object level and, for example in the case of the “fill CAN”, is designed as RAM with two inputs (dual port).
  • the illustration in FIG. 1 is only a rough schematic structure. In fact, the functions can be shifted between the object level and the protocol level, and a clear separation is often not possible.
  • An example of a known CAN system is shown in DE-A-4140017, the disclosure of which is expressly incorporated by reference here.
  • FIG. 2 the "classic" way is shown to exchange data between different networks.
  • the interface 20 shown in FIG. 2 each comprises two CAN units 10, 10 ', which are connected to different networks via their assigned buses 5 and 5'.
  • Each of the CAN units 10, 10 ' essentially corresponds in structure to the unit 10 shown in FIG. 1.
  • the units are connected to one another via an internal bus 4, and a central processor unit (CPU) 100 is additionally provided.
  • CPU central processor unit
  • the data are read by the CPU from the first CAN unit 10 and then written into the other unit 10 '. This means that the CPU load is dependent on the number of data transfers, the number of bytes to be transferred, etc.
  • FIG. 3 An alternative embodiment, which is not prior art, is shown in FIG. 3.
  • a bridge module 12 is also provided, which supports data transfer.
  • the bridge module could be implemented as a hardware implementation, and the mode of operation of the bridge module for the direct data transfer between two CAN units must be specified depending on the application. Often, CPU activity is also required, since not all transmission mechanisms can be implemented using such a bridge.
  • the invention has for its object to develop an interface of the type mentioned, in which the load on the central processor unit is largely minimized and which is characterized by high flexibility; a method for operating such an interface is also to be specified.
  • This object is achieved in that a central message object memory is provided, and a memory area can be assigned to each input / output unit (CAN unit).
  • a machine bus is preferably provided, via which the data transfer between the input / output units and the CPU on the one hand and the central memory on the other hand.
  • a central memory access control is preferably provided, which controls all data transfers from and to the memory.
  • Each input / output unit preferably comprises a protocol level and an object level.
  • the central message object memory is preferably designed as a content-addressable memory (CAM) and / or as a free access memory (RAM);
  • CAM content-addressable memory
  • RAM free access memory
  • an event sequence memory can also be provided, in which a sequence is recorded which is to be triggered when a change in status of a notification object is determined.
  • At least one bridge module is preferably provided, which is connected between the machine bus and the internal bus in the same way as the input / output units.
  • the bridge module can copy data from one memory area into another memory area or transfer it there.
  • a modular construction of the interface is thus achieved according to the invention, in which various units of the interface are designed as modules which are only connected between the internal bus and the machine bus.
  • the modules can be designed as CAN modules (input / output unit) with protocol and object level or as bridge modules for transmitting data between the networks.
  • CAN modules input / output unit
  • bridge modules for transmitting data between the networks.
  • self-defined functional modules in the same way; by using an event Follow-up control can trigger, for example, the change of a notification object (event) a certain sequence (action).
  • Each memory access is made via the central memory access control, so that there is complete control over all storage processes.
  • each module (input / output unit, bridge module, function module, etc.) is assigned its own machine number, and the notification object of each individual network is supplemented by the machine number.
  • CAN network data processing network
  • the corresponding memory area can also be assigned for each individual module. This proves to be particularly advantageous when using a content-addressable memory (CAM) in which at least part of the message object, preferably the machine number and the identification field, is stored; remaining data such as semaphores, status fields etc. can be saved in a correspondingly assigned RAM.
  • CAM content-addressable memory
  • FIG. 1 shows the schematic structure of a CAN node
  • FIG. 2 shows the structure of a conventional interface
  • FIG. 3 shows a possible approach for simplifying data transmission between CAN units
  • Figure 4 shows the schematic structure of an interface according to the invention.
  • Figure 5 shows the schematic structure of a message object memory.
  • Semaphores are bit sequences that indicate states of message objects (for example, topicality, etc.).
  • the time stamp is used to synchronize different data processing networks, and with regard to the details of clock synchronization, reference is made to DE-A-4140017 mentioned at the beginning.
  • an event sequence field refers to a memory area of an event sequence memory when the state of the semaphore changes. For example, it can be provided in the memory 50 3 that when a certain event occurs (state change of a semaphore of a message object) a certain sequence should occur, e.g. change of another message object or generate a new message object, * such as by arrows B and A in Figure 5 is shown.
  • the event list in RAM 50 2 refers to a corresponding sequence (action) ACT1 in event sequence memory 50 3 ; wherein the action ACT1 ... ACTN specified in the memory 50 3 again causes the change of a notification object, which again represents an event.
  • action ACT1
  • ACTN ACTN
  • central memory access controller 40 controls access to the message object memory, preferably according to an access plan. That is, the memory access controller provides each module and the CPU 100 with a time window for the memory access.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multi Processors (AREA)

Abstract

L'invention concerne une interface permettant de coupler au moins deux réseaux CAN comportant chacun des noeuds de données CAN répartis. Une interface de ce type sert à transmettre de données d'un réseau CAN à un autre. Afin de minimiser à cet égard dans une large mesure la sollicitation de l'unité centrale et de mettre au point une interface de conception plus souple pour relier d'autres réseaux par la suite, il est prévu selon l'invention que ladite interface comporte une mémoire centrale pour stocker des informations, une zone mémoire propre pouvant être allouée à chaque réseau CAN. De préférence, il est également prévu un bus machine supplémentaire spécifique et une commande d'accès à la mémoire, de manière que la gestion des accès à la mémoire ne pèse pas davantage sur l'unité centrale.
PCT/EP1998/008431 1997-12-29 1998-12-23 Interface pour plusieurs reseaux de traitement de donnees can et procede permettant d'exploiter une interface de ce type WO1999034560A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE1997158032 DE19758032A1 (de) 1997-12-29 1997-12-29 Schnittstelle für mehrere CAN-Datenverarbeitungsnetzwerke und Verfahren zum Betreiben einer Schnittstelle
DE19758032.7 1997-12-29

Publications (1)

Publication Number Publication Date
WO1999034560A1 true WO1999034560A1 (fr) 1999-07-08

Family

ID=7853476

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP1998/008431 WO1999034560A1 (fr) 1997-12-29 1998-12-23 Interface pour plusieurs reseaux de traitement de donnees can et procede permettant d'exploiter une interface de ce type

Country Status (2)

Country Link
DE (1) DE19758032A1 (fr)
WO (1) WO1999034560A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19830803C2 (de) * 1998-07-09 2000-06-08 Siemens Ag CAN-Modul
US6292862B1 (en) * 1998-07-28 2001-09-18 Siemens Aktiengesellschaft Bridge module
DE10329179A1 (de) * 2003-06-30 2005-03-17 Volkswagen Ag Anordnung und Verfahren zur Verwaltung eines Speichers
DE10335075A1 (de) * 2003-07-31 2005-03-10 Nec Electronics Europ Gmbh Vorrichtung und Verfahren zur Diagnose in Mehrkanal-CAN-Anwendungen
US7209490B2 (en) * 2004-07-01 2007-04-24 Temic Automotive Of North America, Inc. Rapid vehicle bus network activity
US10727954B2 (en) * 2016-06-14 2020-07-28 Teledyne Instruments, Inc. Long distance subsea can bus distribution system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4133030A (en) * 1977-01-19 1979-01-02 Honeywell Information Systems Inc. Control system providing for the transfer of data in a communications processing system employing channel dedicated control blocks
EP0692893A1 (fr) * 1994-07-12 1996-01-17 Ascom Tech AG, Gesellschaft für industrielle Forschung + Technologien der Ascom Dispositif de commutation dans un réseau de commutation numérique à mode de transfer asynchrone
US5633865A (en) * 1995-03-31 1997-05-27 Netvantage Apparatus for selectively transferring data packets between local area networks

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2187067B (en) * 1986-02-21 1989-11-29 Fuji Xerox Co Ltd Stellate store and broadcast network with collision avoidance
AU5951690A (en) * 1989-06-20 1991-01-08 Halley Systems, Inc. Local area network bridge module
DE3927968A1 (de) * 1989-08-24 1991-02-28 Bosch Gmbh Robert Verfahren zur datenuebertragung ueber einen seriellen datenbus in verteilten systemen
JPH07101886B2 (ja) * 1990-05-15 1995-11-01 三菱電機株式会社 ブリツジ装置
DE4140017C2 (de) * 1991-12-04 1995-01-05 Nec Electronics Germany Verfahren zum Betreiben von über einen Datenbus durch seriellen Datenaustausch miteinander kommunizierenden Rechnereinheiten
US5329618A (en) * 1992-04-02 1994-07-12 Fibronics Ltd. Look-up table for a bridge in a data communications system
DE19534330A1 (de) * 1995-09-15 1997-03-20 Siemens Ag Verfahren zum Speichern von teilnehmerbezogenen Daten in Kommunikationssystemen

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4133030A (en) * 1977-01-19 1979-01-02 Honeywell Information Systems Inc. Control system providing for the transfer of data in a communications processing system employing channel dedicated control blocks
EP0692893A1 (fr) * 1994-07-12 1996-01-17 Ascom Tech AG, Gesellschaft für industrielle Forschung + Technologien der Ascom Dispositif de commutation dans un réseau de commutation numérique à mode de transfer asynchrone
US5633865A (en) * 1995-03-31 1997-05-27 Netvantage Apparatus for selectively transferring data packets between local area networks

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
EKIZ ET AL: "Performance Analysis of a CAN/CAN Bridge", PROCEEDINGS OF THE 1996 INTERNATIONAL CONFERENCE ON NETWORK PROTOCOLS, 29 October 1996 (1996-10-29) - 1 November 1996 (1996-11-01), Columbus, US, pages 181 - 188, XP002104040 *
RAAB: "CAN-Controller Area Network", ELEKTOR ELECTRONICS., vol. 18, no. 203, September 1992 (1992-09-01), CANTERBURY GB, pages 56 - 59, XP000309926 *

Also Published As

Publication number Publication date
DE19758032A1 (de) 1999-07-01

Similar Documents

Publication Publication Date Title
DE4222043C1 (fr)
EP1410166B1 (fr) Procede de chargement de logiciel
DE112009005344B4 (de) Fahrzeug-gateway-system
DE10029645B4 (de) Verfahren zur Adressierung von Netzwerkkomponenten
EP0597561B1 (fr) Système de transfert pour l'échange de données
DE69324323T2 (de) Mehrstationskommunikationsbussystem, sowie eine Master-Station und eine Slave-Station für den Einsatz in einem solchen System
WO1999034560A1 (fr) Interface pour plusieurs reseaux de traitement de donnees can et procede permettant d'exploiter une interface de ce type
EP0739509B1 (fr) Configuration a unites maitre-esclave
DE19860069B4 (de) Programmierbare Steuereinrichtung
EP1095338B1 (fr) Module can
DE10026246A1 (de) Verfahren zum Datenaustausch zwischen mehreren Teilnehmern
WO2006069763A1 (fr) Procede de configuration d'appareils de terrain
DE19814359C2 (de) Interface-Einrichtung, Verfahren und Überwachungs-System zum Überwachen des Status einer Hardware-Einrichtung
DE19819569A1 (de) Elektronischer Schaltkreis für die Umwandlung von Daten
EP1894389A1 (fr) Combinaison d'appareils de commande comprenant plusieurs appareils de commande et module de memorisation comme element constitutif de la combinaison d'appareils de commande
EP1242852B1 (fr) Procede et dispositif pour integrer des composants d'automatisation
DE102021003609A1 (de) Verfahren und Vorrichtung zur Dokumentation von Betriebsdaten und deren Anwendung für ein Hochvolt-Batteriesystem
EP0849652B1 (fr) Procédé pour administrer des événements basés sur le temps et dispositif pour l'exécution de ce procédé
DE3137313A1 (de) Schaltungsanordnung zur kopplung zweier mikroprozessoren
DE19732941A1 (de) Fahrtschreiber mit einer Schnittstelle für seinen Anschluß an einen Datenbus
EP1642422B1 (fr) Adaptation d'un reseau embarque dans un vehicule a des exigences modifiees
DE102019126704A1 (de) Ein/ausgabe-station für ein feldbussystem, feldbus-koppler für die ein/ausgabe-station, sowie platzhaltermodul für die ein/ausgabe-station
EP0970426B1 (fr) Systeme de commande de dependance pour acces memoire a chevauchement
EP1316891A1 (fr) Dispositif de transmission de données
EP0811926A2 (fr) Méthode, dispositif et sous-station de transfert de données d'information et de commande

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): JP US

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
122 Ep: pct application non-entry in european phase