0% found this document useful (0 votes)
106 views6 pages

Can-Bus J1939

This application note provides an overview of the J1939 communication protocol used in commercial vehicles, detailing its key features such as 29-bit identifiers, parameter groups, and network management. It explains the structure of parameter groups, the interpretation of CAN identifiers, and transport protocols for data transmission. The document aims to facilitate manufacturer cooperation by standardizing control unit communication mechanisms.

Uploaded by

agnieszkachirrek
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
106 views6 pages

Can-Bus J1939

This application note provides an overview of the J1939 communication protocol used in commercial vehicles, detailing its key features such as 29-bit identifiers, parameter groups, and network management. It explains the structure of parameter groups, the interpretation of CAN identifiers, and transport protocols for data transmission. The document aims to facilitate manufacturer cooperation by standardizing control unit communication mechanisms.

Uploaded by

agnieszkachirrek
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Introduction to J1939

Version 1.0
02/05/2004
Application Note AN-ION-1-3100

Author(s) Markus Junger


Restrictions Public Document
Abstract This application note presents an overview of the fundamental concepts of J1939 in order to give a
first impression.

Table of Contents

1.0 Overview ..........................................................................................................................................................1


2.0 Parameter groups ............................................................................................................................................2
3.0 Network management......................................................................................................................................3
4.0 Interpretation of the CAN Identifier ..................................................................................................................4
5.0 Transport protocols ..........................................................................................................................................5
6.0 Summary..........................................................................................................................................................6
7.0 Additional Sources ...........................................................................................................................................6
8.0 Contacts...........................................................................................................................................................6

1.0 Overview
J1939 is used in the commercial vehicle area for communication in the engine compartment and between the
tractor and trailer. In this application note, the properties of J1939 should be described in brief.

Bridge Bridge

Truck bus Trailer bus

Engine Transmission Brakes Brakes Lighting

The particular characteristics of J1939 are:


• 29-bit identifier
• Peer-to-peer and broadcast communication
• Transport protocols for up to 1785 data bytes
• Network management
• Definition of parameter groups

Copyright © 2004 - Vector Informatik GmbH 1


Introduction to J1939

2.0 Parameter groups


Parameter groups combine similar or associated signals. In the specification SAE J1939-71 the parameter groups
are defined with the signals they contain. In addition, some manufacturer-specific parameter groups can be used.
Parameter groups with up to 8 data bytes are transmitted in a CAN message. With more than 8 bytes, a transport
protocol is used.
Each parameter group is addressed uniquely via a number (Parameter Group Number). For this number, a 16-bit
value is used that is composed of the PDU format and PDU specific. There are two types of parameter group
numbers (PGNs):
• Global PGNs for parameter groups that are sent to all (broadcast). Here all 16 bits of the PGN are used;
the value of the upper 8 bits (PDU format) must be greater than 239.

PGN = FE0116
>= F016

• Specific PGNs for parameter groups that are sent to particular devices (peer-to-peer). With these PGNs,
only the higher-value 8 bits (PDU format) are valid and the value must be smaller than 240. The lower-
value byte (PDU specific) is always 0.

PGN = ED0016
< F016 always 0

With this breakdown of the PGN, 240 + (16 * 256) = 8672 different parameter groups are possible. With the
transmission of a parameter group, the PGN is coded in the CAN identifier.
Sample of a parameter group definition:
Name: Engine temperature
Transmission rate: 1s
Data length: 8 bytes
Data page: 0
PDU format: 254
PDU specific: 238
Default priority: 6
PG Number: 65,262 (FEEE16)

Description of data:
Byte: 1 Engine coolant temperature
2 Fuel temperature
3,4 Engine oil temperature
5,6 Turbo oil temperature
7 Engine intercooler temperature
8 Not defined

Application Note AN-ION-1-3100 2


Introduction to J1939

3.0 Network management


On a J1939 network, each device has a unique address. Each message that is sent by a device contains this
source address. There are 255 possible addresses:
0..253 – Valid addresses of an ECU
254 – Zero
255 – Global
Each device type has a preferred address (see [1]). Before a device may use an address, it must register itself on
the bus. This procedure is called "address claiming." Thereby the device sends an "AddressClaim" parameter
group with the desired source address. This PG contains a 64-bit device name. If an address is already used by
another device, then the device whose device name has the higher priority has received the address.
The device name contains some information about the device and describes its function.

3 Bit 8 Bit 3 Bit


ECU Instance Function Industry
Group

1 Bit
Arbitrary
Address
Capable
21 bit 11 Bit 5 Bit 7 Bit
Identity Number Manufacturer Function Vehicle
Code Instance System

1 Bit 4 Bit
Reserved Vehicle
System
Instance

Since the function of a device is contained in the name, the address can be changed at will and the correct device
is always addressed that provides the required functionality.

Application Note AN-ION-1-3100 3


Introduction to J1939

4.0 Interpretation of the CAN Identifier


The CAN identifier of a J1939 message contains PGN, source address, priority, data page bit, and a target
address (only for a peer-to-peer PG).
The identifier is composed as follows:

Priority Reserved Data PDU format PDU specific Source address


3 Bit 1 Bit page 8 Bit 8 Bit 8 Bit
1 Bit

With PDU format < 240 (peer-to-peer), PDU specific contains the target address. Global (255) can also be used as
target address. Then the parameter group is aimed at all devices. In this case, the PGN is formed only from PDU
format.
With PDU format >= 240 (broadcast), PDU format together with PDU specific forms the PGN of the transmitted
parameter group.

Application Note AN-ION-1-3100 4


Introduction to J1939

5.0 Transport protocols


Parameter groups that contain more than 8 data bytes are transmitted with a transport protocol.

Divided up into multiple packets

TP PGN Transmitted Parameter Group (>8 Byte)


(8 bytes)

For peer-to-peer and broadcast transmission, there are two different protocols. For the transport protocols, there
are two special parameter groups available, which are used for the connection management (TP.CM) and the
transmission of the data (TP.DT).
For broadcast transmission, the BAM protocol is used. Here, after a BAM-PG (Broadcast Announce Message), the
transmitter sends all data PGs at a minimum interval of 50ms.

Transmitter Receiver
TP.CM_BAM

TP.DT

TP.DT

TP.DT

t
t
With the peer-to-peer transmission, the transmitter initiates the connection with a "request to send" message. The
receiver then controls the transport protocol with "clear to send" and "end of message acknowledge."

Transmitter Receiver
TP.CM_RTS

TP.CTS

TP.DT

TP.CTS

TP.DT

TP.EoMA
t t

Application Note AN-ION-1-3100 5


Introduction to J1939

6.0 Summary
With the specification of the parameter groups, CAN identifier scheme, and the network management, a
manufacturer-spanning cooperation of control units should be ensured.
J1939 describes, in addition to the mechanisms presented here, the physical properties, diagnostic functions, and
use of bus subsegments.

7.0 Additional Sources


SAE DOCUMENTS
[1] SAE J1939 Recommended Practice for a Serial Control and Communications Vehicle Network
[2] SAE J1939-11 Physical Layer—250K Bits/s, Shielded Twisted Pair
[3] SAE J1939-13 Off-Board Diagnostic Connector
[4] SAE J1939-15 Reduced Physical Layer, 250K Bits/s, Un-Shielded Twisted Pair (UTP)
[5] SAE J1939-21 Data Link Layer
[6] SAE J1939-31 Network Layer
[7] SAE J1939-71 Vehicle Application Layer
[8] SAE J1939-73 Application Layer - Diagnostics
[9] SAE J1939-81 Network Management Protocol

8.0 Contacts

Vector Informatik GmbH Vector CANtech, Inc. VecScan AB


Ingersheimer Straße 24 39500 Orchard Hill Pl., Ste 550 Lindholmspiren 5
70499 Stuttgart Novi, MI 48375 41756 Göteborg
Germany USA Sweden
Tel.: +49-711-80670-0 Tel: +1-248-449-9290 Tel: +46-31-764-7600
Fax: +49-711-80670-111 Fax: +1-248-449-9704 Fax: +46-31-764-7619
Email: info@vector-informatik.de Email: info@vector-cantech.com Email: info@vecscan.com

Vector France SAS Vector Japan Co. Ltd.


168 Boulevard Camélinat Seafort Square Center Bld. 18F
92240 Malakoff 2-3-12, Higashi-shinagawa,
France Shinagawa-ku, J-140-0002 Tokyo
Tel: +33-1-4231-40 00 Tel.: +81 3 5769 6970
Fax: +33-1-4231-40 09 Fax: +81 3 5769 6975
Email: information@vector-france.fr Email: info@vector-japan.co.jp

Application Note AN-ION-1-3100 6

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy