High-Speed CAN (HSC) for Vehicle Applications at 500 kbps with CAN FD Data at 2 Mbps
- Ground Vehicle Standard
- J2284/4_201606
- Issued
Scope
Rationale
Topic
Data Sets - Support Documents
Title | Description | Download |
---|---|---|
Unnamed Dataset 1 | ||
Unnamed Dataset 2 | ||
Unnamed Dataset 3 | ||
Table 1 | Basic communication network parameters | |
Table 2 | Multiple on-board ECU topology requirements | |
Table 3 | Physical media parameters for unshielded twisted pair | |
Table 4 | Fault Behavior | |
Table 5 | ECU maximum bus wire voltage - no damage to ECU (12 V system) | |
Table 6 | ECU operating parameters – CAN data communication | |
Table 7 | ECU DC parameters - output behavior recessive - bus disconnected | |
Table 8 | ECU DC parameters - output behavior dominant - bus disconnected | |
Table 10 | ECU DC parameters - input behavior - bus disconnected | |
Table 12 | ECU DC parameters - recessive bus state - bus connected | |
Table 13 | ECU DC parameters - dominant bus state - bus connected | |
Table 14 | ECU internal capacitance - ECU disconnected | |
Table 15 | ECU termination characteristics | |
Table 16 | ECU connector characteristics | |
Table 17 | ECU CAN bit timing - min/max | |
Table 18 | ECU CAN register settings for first standard time quanta | |
Table 19 | ECU CAN register settings for second standard time quanta | |
Table 20 | ECU - Basic CAN interface functional requirements | |
Table 21 | Bus transceiver - basic requirements | |
Table 22 | Bus transceiver - maximum bus pin voltage - no damage to transceiver (12 V system) | |
Table 23 | Bus transceiver - general operating conditions | |
Table 24 | Bus transceiver - DC parameters - output behavior - recessive/off state | |
Table 25 | Bus transceiver - DC parameters - output behavior - dominant state | |
Table 26 | Bus transceiver - DC parameters - input behavior/threshold - sleep mode absent | |
Table 27 | Bus transceiver - DC parameters - input behavior/threshold - sleep mode present | |
Table 28 | Bus transceiver - AC parameters | |
Table 29 | CAN controller - basic requirements |
Issuing Committee
Vehicle Architecture For Data Communications Standards
The ever-increasing consumer expectations of vehicle internal functions and connectivity to the environment are outstripping the capability of current data communication architecture design. To address this vulnerability, this committee will investigate and endorse new vehicle architectures that meet system requirements such as: Reliability, System design metrics, Data security, Fault Tolerance, Built in testability, Validation/Verification , Compatibility, and Redundancy. This committee's mission is the investigation and development of vehicle architecture and data communication protocols and methods required to achieve the growth expected in the area of vehicle electronics. The committee shall continue to contribute to the understanding and use of semiconductor devices such as microprocessors, power devices, and other integrated circuits and the data transmission media used in these systems. Thus, all vehicle architectures (excluding aircraft) and devices used in these systems shall be included. Specific objectives shall include: Address the effect of electrical power environments (e.g., 42V, ground offsets) , Sponsor forums to evaluate new technologies (e.g., MOST, Bluetooth, Firewire), Publish technical reports on vehicle architecture and system partitioning, interfacing, modes of operation, protocol standards, recommended conformance test methods, and evaluation methods of those standards , Maintain the existing documents relevant to this committee (e.g., glossary of automotive electronics terms, SAE J1213/1), Encourage the applicable industries, government and educational institutions to support the efforts of this committee.
Reference
Number | Title |
---|