Zu exportierende Waren müssen seit dem 1.7.2009 im ATLAS Verfahren erfasst werden. Um Ausfuhranmeldungen in ATLAS Verfahren durchzuführen wird eine zertifizierte Softwarelösung benötigt.
SAE J1939-73 (often styled as SAE J1939/73 ) standard defines the Application Layer for Diagnostics
within the SAE J1939 protocol family. It is the primary framework used for troubleshooting, repair, and regulatory compliance (HD OBD) in heavy-duty vehicles like trucks, buses, and agricultural machinery. CSS Electronics Core Functionality The standard specifies approximately 60 unique Diagnostic Messages (DMs)
used by Electronic Control Units (ECUs) to communicate health and status. CSS Electronics Active Trouble Codes (DM1):
Periodically broadcasts active Diagnostic Trouble Codes (DTCs) and the status of dashboard diagnostic lamps (e.g., Check Engine). Memory Access:
Defines procedures for reading from and writing to ECU memory for calibration or deep diagnostics. DTC Management:
Standardizes the process for clearing fault codes and retrieving previously active (historic) faults. Regulatory Compliance:
Includes specific messages required to meet California ARB, US EPA, and EU emissions standards. CSS Electronics Standard Details & Versions J1939 Explained - A Simple Intro [2025] - CSS Electronics
The SAE J1939-73 document is the definitive standard for the diagnostic application layer in heavy-duty vehicles, such as trucks, buses, and agricultural machinery. It defines the specific messages, known as Diagnostic Messages (DMs), and the Diagnostic Trouble Codes (DTCs) used to report and troubleshoot issues across a vehicle's Electronic Control Units (ECUs). Current Version and Access
As of December 3, 2024, the latest version of this standard is J1939/73_202412. Because it is a proprietary technical report, the full PDF is not typically available for free download. Exclusive access is usually provided through:
SAE Mobilus: The official portal to purchase the J1939/73 PDF directly from the publisher.
Collaborative Licenses: Providers like CSS Electronics offer legal licenses for the J1939-73 standard PDF as part of their J1939-73 DBC file packages, which convert the standard's technical rules into a machine-readable format for data loggers. Core Components of J1939-73
The standard defines over 60 diagnostic messages that facilitate both real-time monitoring and repair-shop diagnostics.
Diagnostic Message 1 (DM1 - PGN 65226): The most critical message, which broadcasts Active DTCs every second. It includes lamp status signals (e.g., Amber Warning Lamp, Protect Lamp) to indicate the severity of a fault to the driver.
Diagnostic Message 2 (DM2 - PGN 65227): Lists Previously Active DTCs, providing a history of faults that have occurred but are no longer active.
Diagnostic Message 3 (DM3 - PGN 65228): Used to Clear/Reset previously active DTC information.
Diagnostic Trouble Code (DTC) Structure: A 4-byte field containing:
SPN (Suspect Parameter Number): Identifies the failed component (e.g., Engine Oil Pressure).
FMI (Failure Mode Identifier): Describes the nature of the failure (e.g., data valid but above normal range).
OC (Occurrence Count): Tracks how many times the fault has happened. Strategic Use Cases
Engineers and fleet managers rely on the J1939-73 standard for several key operations:
Predictive Maintenance: Using DM1 data via telematics to catch failures before they cause a breakdown.
Emissions Compliance: Reporting emissions-related faults required by regulations such as US EPA and EU Euro VI. sae j193973 pdf exclusive
Prototype Testing: Loggers capture DM1 messages during field tests to help OEMs troubleshoot software or hardware bugs in development. Related Products for Implementation
For those implementing J1939-73 diagnostics, specialized hardware and software tools are available:
J1939-73 DBC File: A specialized CSS Electronics file for decoding raw CAN bus data into readable DTCs.
Diagnostic Cables: Tools like the Type 2 Green 9-pin J1939 Cable from Amazon are used to connect diagnostic tools to the vehicle's Deutsch 9-pin connector. Go to product viewer dialog for this item. Googlehttps://www.google.com YPP Type 2 Green 9pin J1939 Female to Open Cable 1ft/30cm
SAE J1939-73 provides the messages and procedures necessary for a technician or an automated system to "talk" to a vehicle's electronic control units (ECUs). It goes beyond simple data reading to enable:
Diagnostic Trouble Codes (DTCs): It standardizes how a vehicle reports a malfunction. A J1939 DTC consists of a Suspect Parameter Number (SPN), Failure Mode Identifier (FMI), Occurrence Count (OC), and SPN Conversion Method.
Memory Access: It defines protocols for DM14 through DM18 messages, which allow tools to read and write to specific memory locations within an ECU for calibration or specialized testing.
Diagnostic Messages (DM): The standard categorizes messages into "Active" (DM1) and "Previously Active" (DM2) faults, allowing for a historical view of vehicle health. Why It’s "Exclusive" to Professional Environments
The documentation for SAE J1939-73 is typically proprietary intellectual property managed by the Society of Automotive Engineers (SAE International).
Access: Full PDF versions are generally not "free" or public; they require a license from the SAE Standards Store.
Implementation: Because it handles sensitive functions like clearing fault codes or modifying ECU memory, implementation is usually restricted to authorized diagnostic tools and OEM software. Key Components of a J1939-73 Message
According to technical breakdowns from Kvaser and National Instruments, these messages rely on the 29-bit CAN identifier: Description Source Address (SA)
The unique 8-bit identifier for the node (e.g., Engine, Transmission) Simma Software. Parameter Group Number (PGN)
A 18-bit value that identifies the specific diagnostic message being sent. Priority
A 3-bit field determining which message gets bus access first in high-traffic scenarios.
SAE J1939-73 standard is a critical part of the SAE J1939 family, serving as the Application Layer for Diagnostics
in heavy-duty vehicle networks. It defines the structure and behavior of "Diagnostic Messages" (DMs) used for identifying faults, repairing vehicles, and ensuring emissions compliance. CSS Electronics Overview of SAE J1939-73
This standard provides the protocol for Electronic Control Units (ECUs) to communicate diagnostic information such as active trouble codes and lamp status. It is widely used in trucks, buses, and off-highway machinery. CSS Electronics Primary Purpose:
To establish a standard architecture for on-board electronic systems to exchange diagnostic data. Latest Revision: The standard was most recently updated in December 2024 (J1939/73_202412). OBD Compliance:
It satisfies regulated On-Board Diagnostic (OBD) requirements for the US EPA, California CARB, and the EU. Key Features and Diagnostic Messages
The standard defines over 60 diagnostic messages that facilitate both real-time monitoring and off-line repair. CSS Electronics SURFACE VEHICLE RECOMMENDED PRACTICE - UNECE SAE J1939-73 (often styled as SAE J1939/73 )
The Story of Jack's Truck
Jack was a truck driver who drove a large rig across the country. One day, he noticed that his truck's engine was experiencing some issues. The engine control unit (ECU) was throwing error codes, and Jack wasn't sure what they meant.
A mechanic friend of Jack's suggested that he take a look at the SAE J1939 protocol, which was used in his truck's engine. The SAE J1939 protocol is a standardized communication protocol used in heavy-duty vehicles, such as trucks and buses.
As Jack's friend explained, SAE J1939 is used for communication between electronic control units (ECUs) in a vehicle. It's like a language that allows different ECUs to talk to each other and share information.
The protocol uses a 29-bit identifier, which allows for a wide range of messages to be transmitted. The identifier includes a priority, a message type, and a source address.
For example, $$Priority = 0 \text to 7$$, where 0 is the highest priority.
Jack's friend showed him how to look up the error codes in the SAE J1939 protocol document, which is available in PDF format. The document explained that the error codes were related to issues with the engine's fuel system.
Using the SAE J1939 protocol, Jack's friend was able to diagnose the problem and make the necessary repairs. Jack was back on the road in no time, and he was grateful for the help of his friend and the SAE J1939 protocol.
Some key points about SAE J1939:
If you're interested in learning more, I can try to provide you with some additional information or point you in the direction of a SAE J1939 PDF document.
The SAE J1939-73 standard is a critical part of the SAE J1939 protocol suite, specifically defining the Application Layer for Diagnostics. It standardizes how Electronic Control Units (ECUs) in heavy-duty vehicles report, clear, and manage diagnostic information. 1. Core Functions of SAE J1939-73
This standard provides the framework for "Diagnostic Messages" (DMs) used during both active vehicle operation and stationary repair.
DTC Management: Defines how Diagnostic Trouble Codes (DTCs) are structured and transmitted.
Status Reporting: Standardizes "lamp" signals (e.g., Check Engine, Stop Engine) to communicate vehicle health to the driver.
Memory Access: Includes protocols for requesting and transferring raw data from an ECU’s memory.
Service Tool Interface: Specifies the diagnostic connector and communication requirements for external service tools to interface with the vehicle. 2. Key Diagnostic Messages (DMs)
The J1939-73 standard defines over 50 specific diagnostic messages. Some of the most common include:
DM1 (Active DTCs): Periodically broadcasts currently active fault codes to the network.
DM2 (Previously Active DTCs): Allows a technician to view historical fault data that is no longer active.
DM3 (Clear/Reset): A request message used to clear active and previously active diagnostic information.
DM11 (Diagnostic Data Clear): Used specifically to clear diagnostic data for all components. SAE J1939 is a communication protocol used in
DM14, DM15, DM16: Support memory access, including read/write requests and binary data transfers. 3. Implementation Requirements
To implement J1939-73, systems must adhere to specific technical constraints:
Addressing: Uses the 8-bit Source Address (SA) unique to each ECU and the 29-bit CAN identifier.
Transport Protocols: For diagnostic messages larger than 8 bytes, the standard relies on J1939-21 transport protocols like BAM (Broadcast Announce Message) or RTS/CTS (Request to Send/Clear to Send).
Flash Rates: Defines specific update rates and flashing behaviors for diagnostic lamps. 4. Regulatory Context
The standard is updated to align with global regulations, including: US EPA and US CARB for heavy-duty emissions.
EU and World Wide Harmonization (WWH) of On-Board Diagnostics (OBD).
For official technical specifications or to purchase the full document, you can visit the SAE J1939-73 Standards Page. SURFACE VEHICLE RECOMMENDED PRACTICE - UNECE
Assuming the typo theory is correct, here is a comprehensive, useful article about the intended standard (most likely SAE J1939-73) and how to obtain an exclusive, legitimate PDF copy.
In the world of heavy-duty vehicle engineering, data is currency. While SAE J1939-71 defines the data parameters (PGNs), it is SAE J1939-73 that defines the language used to retrieve, secure, and diagnose that data.
For developers, calibration engineers, and fleet telematics providers, access to the SAE J1939-73 PDF is not just a reference—it is a blueprint for compliance. This exclusive breakdown covers the core components of the document and explains why this specific standard is critical for modern vehicle architecture.
Once you have your exclusive PDF, you can finally decode what your scan tool is saying. Here is a real-world example using the standard.
The Problem: Your DTC reads: SPN 91 FMI 3
Step 1 (Open J1939-73 PDF): Go to the SPN index. Step 2 (Look up SPN 91): You find "Accelerator Pedal Position 1." Step 3 (Look up FMI 3): You go to the FMI table. FMI 3 = "Voltage Above Normal or Shorted High." Step 4 (The Diagnosis): You don't just guess. The PDF tells you that combination means the ECU sees 5+ volts on the pedal sensor circuit when it should see 0.5-4.5 volts. You now know to look for a short to power.
Without the "exclusive" clarity of the official PDF, you would have wasted hours swapping pedals.
Full Title: SAE J1939-73: Diagnostic Messages – Application Layer
Scope: This document specifies the diagnostic messages used by ECUs to report, log, and clear faults over the Controller Area Network (CAN) bus. It defines:
Use DM1 (PGN 65226) to read active faults from the engine ECU. The standard provides exact byte offsets: byte 1 = number of DTCs, bytes 2-3 = SPN (Suspect Parameter Number), byte 4 = FMI (Failure Mode Indicator), etc.
The PDF details the structure of the DTC, which consists of three main fields:
Exclusive Note: Understanding the conversion between legacy J1587 codes and J1939 SPNs is a frequent challenge solved directly within the appendixes of this document.
Erleben Sie V-LOG® in der neuesten Version