|
|
SAE J2366 - Family of ITS Data Bus (IDB) Protocol Standards
This Fact Sheet was written on Jul 12, 2006. The statuses of the standards at the time were as follows: SAE J2366-1 (published November 2001), SAE J2366-1L (published November 2001), SAE J2366-2 (published November 2001), SAE J2366-4 (published March 2002), SAE J2366-7 (published April 2002).
This Fact Sheet was written on July 12, 2006.
This Fact Sheet was last verified on October 14, 2009
Overview
The IDB is intended to be used by vehicle manufacturers to prepare their vehicles for consumer electronics devices, and by the consumer electronics manufacturers to be able to build one interface for their products that can be used in any vehicle. Additionally, it may be used by the after market electronics industry to simplify integrated installation of add-on automotive electronics. The ultimate users are the consumers, the vehicle buyers, who will be able to configure their vehicles much the same way as they configure their home theaters and personal computers. A quick survey in March 2006, including contact with the IDB Forum indicates that no vehicle or consumer electronics manufacturers are currently using the IDB-C standards. The IDB Forum is currently focused on IDB-1394, a family of specifications designed for high-speed multimedia applications that are based on the IEEE-1394 FireWire standards.
What are these standards for?
IDB-C is an open, non-proprietary serial communications protocol designed to allow a wide variety of consumer devices to share information across a common network in the vehicle. The IDB has been developed by the SAE ITS Data Bus Committee with the support of the Consumer Electronics Association (CEA) division of the Electronics Industry Association (EIA). Its primary goal is to provide a means of connecting consumer devices to a common network in a vehicle without requiring the consumer electronics manufacturers to develop interfaces to the different proprietary original equipment manufacturer (OEM) vehicle buses, nor to have to complete automotive-type safety and interoperability qualifications on every product which might be added to the vehicle.
Who uses them?
The IDB is intended to be used by vehicle manufacturers to prepare their vehicles for consumer electronics devices, and by the consumer electronics manufacturers to be able to build one interface for their products that can be used in any vehicle. Additionally, it may be used by the after market electronics industry to simplify integrated installation of add-on automotive electronics. The ultimate users are the consumers, the vehicle buyers, who will be able to configure their vehicles much the same way as they configure their home theaters and personal computers. A quick survey in March 2006, including contact with the IDB Forum indicates that no vehicle or consumer electronics manufacturers are currently using the IDB-C standards. The IDB Forum is currently focused on IDB-1394, a family of specifications designed for high-speed multimedia applications that are based on the IEEE-1394 FireWire standards.
How are they used?
The documents define the complete operation of the IDB-C. Equipment designers can use these documents to develop software drivers and hardware interfaces for their products so that they will be "IDB-compliant."
Scope
The IDB specifications encompass the definition of the physical medium (unshielded twisted pair), the topology (multidrop bus), media access control mechanisms (token passing), initialization of an IDB network, plug-and-play insertion and removal of devices, message fragmentation and defragmentation, guaranteed delivery of messages, and the application message syntax.
The four standards: SAE J2366-1 Physical Layer; SAE J2366-2 Link Layer; SAE J2366-4 Thin Transport Layer; and SAE J2366-7 Application Message Layer, define the different layers of the IDB protocol stack.
Related documents
The following ITS standards are related and should be considered when using this family of standards:
- SAE J2355 - ITS Data Bus Architecture Reference Model Information Report
- SAE J1760 - ITS Data Bus Data Security Services
The following standards and documents, while not part of the ITS standards, should also be considered when using this standard:
- https://www.iso.org/standard/20269.html
- https://www.iso.org/standard/35684.html
- https://www.sae.org/standards/content/j2590_200112/
- CAN 2.0 - Robert Bosch GmbH, Specification for Controller Area Networks (CAN), Version 2.0B
- https://www.sae.org/standards/content/j2284/2_200203/
- https://www.sae.org/standards/content/uscar2-4/
How to obtain Standards
- https://www.sae.org/ Phone: 877-606-7323
|