GMW GMW3122 PDF

Introduction

Note: Nothing in this standard supercedes applicable laws and regulations.

Note: In the event of conflict between the English and domestic language, the English language shall take precedence.

Purpose. This document specifies the physical layer requirements for a Carrier Sense Multiple Access/Collision Resolution (CSMA/CR) data link which operates on a dual wire medium to communicate among Electronic Control Units (ECU) on road vehicles at normal transmission rates of:

• High Speed Bus 500 kbits/s
• Medium Speed Bus 95.24 kbits/s and 125 kbits/s

This document is to be referenced by the particular Component Technical Specification (CTS) which describes any given ECU in which the dual wire data link controller and physical layer interface is located. The performance of the data link layer and physical layer is specified in this document. ECU environmental and other requirements shall be provided in the CTS. Functional as well as parameter requirements in this document generally apply over the applicable operating conditions and aging. This includes, for example, operating ambient temperature, operating supply voltage and age drift over component lifetime unless otherwise noted. The intended audience includes, but is not limited to, ECU suppliers, component release engineers, platform system engineers and semiconductor manufacturers of Controller Area Network (CAN) controller and CAN transceiver Integrated Circuits (IC).

Applicability. This specification describes the data link and physical layer requirements for a dual wire data link capable of operating with CSMA/CR protocols such as CAN version 2.0A (standard frame format). All ECUs shall tolerate CAN version 2.0B (29-bit identifier extended frame format) messages, i.e., ECUs may not disturb such messages unless bit errors were detected. This serial data link network is intended for use in applications where a high data rate is required.

Remarks. Within this document the following conventions are applied:

The word ʺShallʺ shall be used in the following ways:

a. To state a binding requirement on the network or the nodes which comprise the network, which is verifiable by external manipulation and/or observation of a node or the network.

b. To state a binding requirement upon a node's requirements document that is verifiable through a review of the document.

The word ʺMustʺ shall be used to state a binding requirement upon nodes on the network components which will have a corresponding ECU or component requirements document. These requirements will be verified as part of the component verification. The word ʺShouldʺ denotes a preference or desired conformance.