SAE J1850_198811

The objective of this document is to define a minimum set of physical and data link layer requirements applicable to a vehicle data communication network that is cost effective for simple applications and flexible enough to use in complex applications. Network requirements "above" the physical and data link layers are generally application specific and are, therefore, left to the system designer. The requirements contained in this document define a data communications network philosophy that satisfies the needs of the automotive manufacturers. In its present form, this document defines a cohesive set of data link layer requirements. On the other hand, several alternative physical layer approaches are specified to accommodate a variety of application requirements. Although devices may be constructed that can be configured to meet all of the physical and data link layer requirements defined in this document, it is expected that most manufacturers will use subsets of these requirements depending on their specific application and corporate philosophy toward data link usage. However, low volume users of network interface devices may still find it more effective to use a generic interface capable of handling essentially all of the requirements specified in this document. Designers of integrated circuit(s) associated with these requirements are encouraged to innovate and add flexibility in their designs in order to gain broader market acceptance of their specific product offerings. This SAE document is under the control and maintenance of The Vehicle Network for Multiplexing and Data Communications (Multiplex) Committee. This committee will periodically review and update this document as needs dictate. In the document's present form, as a recommended practice, it contains information that is intended as a guide to standard engineering practice. It is the eventual goal of this committee to upgrade this document to an SAE Standard. To accomplish this upgrade, the document must contain information describing a broadly accepted engineering practice. This means hardware must be developed requiring most likely refinements, technical advancements, and a broad acceptance of a single cohesive set of network features.