Data Acquisition From HD Vehicles Using J1939 CAN Bus
AUTOMOTIVEData Acquisitionfrom HD VehiclesUsing J1939 CAN BusRichard P. WalterEric P. Walter
Table of ContentsChapter 1 Benefits and Applications of the In-Vehicle Network forData Acquisition. 11.1 Overview—Data Gold Mine.11.2 Focus and Assumptions of This Book.21.3 Access to the Data.21.4 Normal and Requested Messages.21.4.1 Normal Messages.21.4.2 Requested (Diagnostic/Polled/Event) Messages.31.4.3 Requested Versus Normal Messages.31.5 Comparing Light- and Heavy-Duty Vehicle Designs.31.6 Medium-Duty Vehicles.51.7 Applications.51.8 How to Use This Book.5References.6Chapter 2 Comparison with Traditional Data Acquisition.72.1 Acquiring Data with Our Own Sensors.72.2 In-Vehicle Network Data.82.3 Acquiring Parameters from the Network.92.4 Complications of Network Versus Direct Sensors.9Chapter 3 Binary, Hex, Bits, and Bytes.113.1 Introduction to Bits, Binary, and Hexadecimal Conventions. 113.2 Hexadecimal Designations.123.3 Introduction to Bits and Bytes.123.4 11- and 29-Bit CAN IDs.123.5 Data Conventions.133.5.1 Conversion Format.133.5.2 Byte Format.133.5.3 Byte Order.14Chapter 4 Controller Area Network (CAN) Protocol . 174.1 What is CAN?.174.2 What Does CAN Define?.194.2.1 Layer 1—Physical Layer.194.2.2 Level 2—Data Link Layer.204.3 Applications of CAN.224.4 CAN on Light-duty Vehicles Using ISO 15765.23References.23v
Chapter 5 J1939 Standard Overview. 255.1 Introduction.255.2 Previous In-Vehicle Network Standards (J1708 and J1587).275.3 J1939 Overview and Industry-Specific Standards.285.3.1 J1939 – Top-Level Document.285.3.2 J1939DA – Digital Annex.295.3.3 J1939/01 – On-Highway Equipment Control and CommunicationNetwork.295.3.4 J1939/02 - Agricultural and Forestry Off-Road Machinery Controland Communication Network.305.3.5 J1939/05 Marine Stern Drive and Inboard Spark-Ignition EngineOn-Board Diagnostics Implementation Guide.315.4 J1939/7x – Background Application Standards.315.4.1 J1939/74 – Application Configurable Messaging.315.4.2 J1939/75 – Generator Sets and Industrial.325.5 J1939/8x.325.5.1 J1939/81 – Network Management.325.5.2 J1939/82 – Compliance—Truck and Bus.335.6 Most Important J1939 Standards.34References.34Chapter 6 J1939 Lower Layer Specifications. 356.1 Physical Layer.356.1.1 J1939/11—Physical Layer—250 kbits/s, Shielded Twisted Pair.356.1.2 J1939/13—Off-Board Diagnostic Connector.366.1.3 J1939/14—Physical Layer, 500 kbits/s.386.1.4 J1939/15—Physical Layer, 250 kbits/s, Unshielded Twisted Pair.386.2 Data Layer.386.2.1 J1939/21—Data Link Layer—Message Format.396.2.2 J1939/21—Data Link Layer—Transmitting Messages.446.2.2.1 Broadcast Announce Message (Global).456.2.2.2 Broadcast Long Message Example: PGN-FEE3 (65251)—Engine Configuration.456.2.2.3 Connection Management (Targeted).456.2.2.4 Request Messages.466.3 Network Layer (J1939/31).46References.49Chapter 7 Application Layer (J1939/71). 517.1 PGNs and SPNs.517.2 J1939 Message Data Format.537.3 Scaling Information.547.4 Transmission Rate.557.5 Digital Annex (J1939DA).55vi
7.6 Logging J1939 Data with a Test Tool.557.6.1 Example J1939/71 Database Editor.567.6.2 Selecting Parameters to Acquire.577.6.3 Finding Available Parameters.577.6.4 Sorting by Name, Unit, or PGN.587.6.5 Defining the Acquisition Rate and Source Address.587.6.6 Importing Proprietary Messages.587.7 Sample J1939 Message File.58References.60Chapter 8 Diagnostics (J1939/73).618.1 Overview.618.2 Diagnostic Messages.628.3 Diagnostic Trouble Codes.648.3.1 Lamp Status (First Byte).648.3.2 Second Byte.658.3.3 HD DTC Parameters (Bytes 3 through 6).658.3.3.1 Suspect Parameter Number.658.3.3.2 Failure Mode Identifier.658.3.3.3 Occurrence Count.668.3.3.4 SPN Conversion Method.668.3.4 Controller ID.668.3.5 Example.668.3.6 Multiple DTCs Reported.678.4 Comparing HD OBD with LD OBD-II.688.5 Targeted or Global Requests.69References.70Chapter 9 Heavy-Duty On-Board Diagnostic (HD-OBD) . 719.1 Introduction of OBD.719.2 Worldwide Harmonized On-Board-Diagnostics (WWH-OBD).729.3 J1939/03 On-Board Diagnostics Implementation Guide.739.4 J1939/84 OBD Communications Compliance Test Cases for Heavy-DutyComponents and Vehicles.739.5 Comparing LD with HD-OBD.749.5.1 Comparing HD and LD Standards.749.5.2 Comparing HD and LD Approaches.749.5.3 Comparing HD Messages with LD Test Modes.759.6 Example Fault Codes.769.6.1 Example Fault Codes Using J1979 for OBD-II.779.6.2 Example Fault Codes Using UDS ISO 14229 for EOBD.789.6.3 Example Fault Codes Using J1939.809.6.4 Example Fault Codes Using WWH-OBD.80References.83
Chapter 10 Examples of J1939 Data. 8510.1 Sample J1939 Message File.8510.2 Debugging Controllers and Reverse Engineering non-Standard J1939Messages.8610.3 Example Scaled Engineering Data.8910.4 Web-Based Dashboards and Example Applications.9210.4.1 Fleet Data.9210.4.2 Diagnostics and Alerts.9310.4.3 Diagnosing Intermittent Problems.9410.4.4 Fuel Economy.9610.4.5 Duty Cycle and Drive Cycle Analysis.97References.97Chapter 11 Data Storage and Transfer. 9911.1 File Size.9911.1.1 Estimating File Size.9911.1.2 File Format and Compression.10011.2 Data Transfer Options and Data Rates.10011.2.1 WiFi.10111.2.2 Cellular.10211.2.3 Bluetooth.10211.2.4 USB.10211.3 Real-Time Data Versus Logging.10311.3.1 Real-Time Data.10311.3.2 Logging.10311.3.3 Acquisition, Storage, Display, and Analysis Trade-Offs.104Appendix A Abbreviations.105Index. 111
Data Acquisition from HD Vehicles Using J1939
Model Year 2015 Fuel Economy Leaders / 5 2015 Model Year Vehicles / 6 Diesel Vehicles / 29 Electric Vehicles / 31 Plug-in Hybrid Electric Vehicles / 33 Compressed Natural Gas Vehicles / 35 Fuel Cell Vehicles / 35 Hybrid Electric Vehicles / 36 Ethanol Flexible Fuel Vehicles / 38
The Army operates a fleet of ground combat vehicles—vehicles intended to conduct combat opera-tions against enemy forces—and plans to continue to do so. Expanding on the Army's stated plans, . Background 1 Historical Acquisition Appropriations 2 Projected Acquisition Costs 3 Five Current Families of Army Ground Combat Vehicles 4
AA001.003.01 Data Acquisition Didactic Panel (NI USB 6003) AA001.002.01 Data Acquisition Didactic Panel (NI USB 6002) AA001.001.01 Data Acquisition Didactic Panel (NI USB 6001) AA001.000.01 Data Acquisition Didactic Panel (NI USB 6008) 10 11 Data acquisition, processing and Monitoring The didactic panels
vehicles powered by alternative energy (basically, electric vehicles, plug-in hybrid electric vehicles and fuel-cell electric vehicles) are twice as energy efficient as current ICE vehicles. 4 Srivastava et al (2010) report that the plug-in hybrid vehicle is the next candidate for replacing existing ICE vehicles. The plug-in hybrid vehicle can .
Selection Defense Business Systems Middle Tier of Acquisition Acquisition of Services Major Capability Acquisition . Reference Source: DoDI 5000.80, Paragraph 1.2.b The MTA pathway is intended to fill a gap in the Defense Acquisition System (DAS) for those capabilities that have a level of maturity . Acquisition programs intended to be .
intelligent vehicles in recent years. Intelligent vehicles tech-nologies are based on the information of the ego vehicle and its surroundings, such as the lanes, roads, and other vehicles, using the sensors of intelligent vehicles [4], [5]. The sensors in intelligent vehicles can be divided into internal and external sensors.
For tailored, one-to-one advice on how plug-in vehicles could work in your business, including a full analysis of your existing vehicles, email us at: pifi@est.org.uk Contents Types of plug-in vehicles 02 The business case for plug-in vehicles 03 Charging modes and types 04 Practicalities of running plug-in vehicles 05
Diesel-powered vehicles Biodiesel-powered vehicles Unlikely/Very Unlikely Not Sure Likely/Very Likely Likelihood to Consider Purchasing (Ranked by "Likely/Very Likely") 6% 30% 37% 41% 68% 69% 76% 9% 24% 24% 26% 16% 22% 17% 85% 47% 39% 33% 16% 10% 7% Gasoline-powered vehicles Hybrid vehicles Electric vehicles (EVs) Plug-in hybrid vehicles .
