AN1230

SAE J1708/J1587 Communications with the EUSART

INTRODUCING J-1708
Author: Joseph Julicher
Microchip Technology Inc.
History
The J1708 serial communications link specification
INTRODUCTION was issued by SAE in 1986. It is intended to describe a
hardware and protocol to standardize the
The Enhanced Universal Synchronous Asynchronous communications between modules in heavy-duty
Receiver Transmitter (EUSART) was developed to vehicle applications. The objectives of the link are:
address the demands created by higher clock speeds • Minimize hardware costs and overhead
and automotive low-speed networks. The EUSART is
• Provide flexibility for expansion and
found on many PIC® microcontrollers. PIC16F688 will
advancements without impacting existing systems
be used for the examples in this application note. This
document demonstrates the EUSART used to • Utilize standard hardware
communicate on an SAE J1708 data bus, such as • Be electromagnetically compatible with the rest of
those found in a modern heavy truck. the vehicle
• Provide flexibility for suppliers to customize the
FEATURES link for proprietary reasons
The J1708 link is a bidirectional communications link
The features of the EUSART are as follows: which links electronic modules that contain
• Selectable 16-bit Baud Rate Generator mode microcomputers. The actual J1708 specification
• Interrupt on Sync Break character received defines hardware and the protocol requirements to
• 12-bit Break character transmit maintain the link. The actual data that is communicated
on the link is defined by a separate J1587 document.
• Auto-baud calibration on Sync character
• Clock polarity select for Synchronous mode Today, the J1708 data bus is alive and well in heavy
trucks. It is used to communicate general status
• Transmit polarity select for Asynchronous mode
information between electronic modules. A federal
• Receiver Idle flag requirement for the trailer anti-lock braking system to
• Receive Shift register empty Status bit during light a fault lamp in the tractor has led to the
Sleep development of a power line carrier version of the
J1708 data bus. The hardware interface is changed to
Further Reading allow communications over the 12V DC power bus, but
the protocol and communications timing remain the
Additional information can be found in the data sheet same.
for PIC16F688, the SAE J1708 and the SAE J1587
specification.
J1708 Overview
Note: Any microcontroller with an EUSART is
J1708 is a simple multi-master bus interface built upon
suitable for this application note.
a USART peripheral in a microcontroller. While any
Appropriate changes must be made to
wired-or type physical layer works with J1708, the
adapt the software from PIC16F688 to a
specification describes a physical layer based upon an
different device.
RS-485 bus (see Figure 1). By using a recessive state
and a dominate state for the bus, multiple masters can
share the transport media without fear of contention.
The J1708 protocol includes methods for claiming the
bus, resolving collisions, and transmitting data. The
data is transmitted at 9600 baud with 1 Start bit, 8 data
bits and 1 Stop bit. The packet length is 2 to 21 bytes
including a checksum for error detection. Parameter
Identification (PID) numbers identify the data on the
bus. Groups of PIDs are reserved for data that are of

© 2008 Microchip Technology Inc. DS01230A-page 1

AN1230
different lengths. Module Identifiers (MID) identify Since the J1708 specification was released, a few
different transmitters on the bus. The MIDs are companies have released custom silicon designed to
numbered to provide an implicit priority scheme. In this simplify J1708 bus interfaces. Maxim and National
way, engine modules get a higher priority than vehicle Semiconductor are two companies that sell a simple
modules or diagnostic tools. J1708 transceiver.
Additional information concerning J1708 is covered in If an application does not require J1708 physical
later sections. compatibility but you do want to use the techniques
with the EUSART, then a CAN or LIN type transceiver
Other Uses may be appropriate.

The hardware and software that makes up the basics

of a J1708 data bus can easily be used in other STANDARD J1708 DATA BUS
applications. A robot could use J1708 and custom HARDWARE
messages to share data between multiple CPUs.
The standard J1708 node, from the SAE J1708
J1708 can even be used with optical or RF components
specification, is shown in Figure 1. This circuit is
to create a wireless network. Interfacing a J1708 bus to
designed for an RS-485 type bus transceiver. Notice
a PC requires very simple hardware because the PC
that R1 and R2 pull the bus into the logic 1 state. Notice
serial port can understand the data with an appropriate
that the transmit line from the microcomputer (Tx) is
physical layer transceiver.
driving the data enable (DE) line of the transmitter. Due
to the logic state of the transmit enable line, the Tx
BASIC J1708 HARDWARE signal must be inverted before it enters the RS-485
transceiver. On a PIC16F688, this inversion can be
The SAE J1708 specification describes the basic
handled within the EUSART. The data input (DI) line of
interface using an RS-485 transceiver. This transceiver
the RS-485 transceiver is held at the ground level.
is used because:
Modulating the enable line and using pull-up resistors
• It is inexpensive
eliminates the possibility of electrical bus contention.
• It is available Logic 0 will always win a bus collision in this design.
• Despite being used in an unusual way, it is The resistors R3 and R4 and the capacitors C1 and C2
adequate for low-speed work are low-pass filters to prevent EMI from causing bit
errors at the receiver and prevent EMI causing
transients during transmits.
J1708 specifies up to 20 nodes on a bus with a
maximum length of 40 meters.

FIGURE 1: STANDARD J1708 NODE

+ 5V
4.7K

+ 5V
R3

RX
R1
U1

1 RO VDD 8 47
2 7
RE A
3 6
TX DE B R2
4 5
DI GND
Inverter
47
2.2μ F

2.2μ F

4.7K
R4
C2
C1

RS-485 Transceiver
Serial
Data Bus

DS01230A-page 2 © 2008 Microchip Technology Inc.

 AN1230
J1708 NETWORK ACCESS The arbitration technique is very simple, but has a few
requirements that must be defined.
Devices that require access to the bus must perform a
1. What is a bit time?
process called arbitration.
2. When is the bus Idle?
The steps to arbitration are as follows:
3. What are the priority delays?
1. Wait for the bus to become Idle. 4. How do we determine the pseudo-random
2. Wait the required priority delay after the Idle number?
period has started.
3. Make sure the bus is still Idle. If the bus is not
Idle, go back to step 1.
BIT TIME
4. Transmit the device MID on the bus. The bit time is the time required to send 1 bit of data.
5. Receive the transmitted MID and determine that For the J1708 specification, 1 bit time is 104.16
the sent MID matches the received MID. microseconds. This time corresponds to 9600 baud. All
other times specified by the J1708 specification are
6. If the match was successful, we have claimed
multiples of bit times.
the bus. Send the packet.
7. If the match failed, we lost the arbitration.
Continue to step 8. BUS IDLE
8. If this was the first collision for this packet, go to Per the J1708 specification, the bus is Idle after 10-bit
step 1. times have elapsed from the previous character with no
9. Wait for the bus to become Idle. received Start bits. This is very important and must be
10. Wait for a pseudo-random number of bit times accurately determined because the J1708 specification
(between 0-7). defines the end-of-packet condition as the bus going to
11. Go to step 3. Idle. After the 10-bit times have elapsed and the
receiver is not receiving, then we know the bus is Idle
so the previous packet can be validated and any
arbitration can continue.

FIGURE 2: BUS IDLE

MID Data 0-19 bytes Checksum

Bus Busy

Stop bit of last Bus is Idle. 10-bit times

character after the last character.
Bus Idle Diagram

MESSAGE PRIORITY Therefore, a message priority of 1 will result in a 2-bit time

or 208.32 µS delay from the bus Idle point.
All messages on the J1708 bus are assigned a
Message priorities are assigned as numbers between
message priority by the defining application document.
1 and 8. The J1708 specification defines the following
The message priority is converted into a message classes of message priorities.
priority delay by the following equation:

EQUATION 1:
Pd = Tb*2*P

Pd = Priority Delay in µS
Tb = Bit time or 104.16 µS
P = Message Priority

© 2008 Microchip Technology Inc. DS01230A-page 3

AN1230
TABLE 1: CLASSES OF MESSAGE MESSAGE CHECKSUM
PRIORITIES
The checksum is calculated by adding each packet and
Priority Message Assignment subtracting the total from zero. By adding up the data in
1 and 2 Messages that require immediate access the receiver, the total should reach zero. If the total is
to the bus not zero, an error occurred in the data transmission.
J1708 does not specify any error correction or data
3 and 4 Messages that prevent Mechanical
retransmission when a mismatch occurs. The data is
Damage
simply assumed to be invalid and should be discarded.
5 and 6 Messages that control economy or
Keeping track of the message checksum can provide a
efficiency
useful bus diagnostic. If the checksum is consistently
7 and 8 All other messages bad it can mean:
1. Another node is behaving poorly.
PSEUDO-RANDOM NUMBERS 2. An intermittent connection is disrupting commu-
Pseudo-random numbers are used by J1708 to prevent nications,
a deadlock condition where two MIDs become synchro- 3. The baud rate is not very accurate, or
nized in their attempt to gain access to the data bus. 4. Electrical interference.
This is most likely to occur if two identical systems are It is very simple to store the checksum mismatch count
sharing the bus. A robust random number source is not in the EEPROM of the microcontroller. This data can be
required, but simply a reasonably non-deterministic reported on request to debug bus problems.
source of data to prevent the deadlock. Good choices
for a PIC microcontroller are: To compute a checksum:
1. ADC value of a noisy channel, 1. add all the bytes
2. Timer0 LSBs, or 2. invert the sum
3. Number of bus collisions seen by this receiver. 3. add 1, and
4. transmit, as the last byte.
There are many other possibilities, but these are a
good start. The code included in this application note Consider the following data.
uses a bus collision counter as the random number
128 95 23 45 123 XXX
source for choosing the retry interval.
What should be inserted at XXX to assure a proper
checksum?
J1708 DATA FORMAT
128 + 95 + 23 + 45 + 123 = 158 (assuming an 8-bit
The data in a J1708 packet is very simple (see Table 2). adder with an 8-bit result)
The two most critical elements of the packet are the Bitwise inversion of 158 results in 97.
MID and the checksum. The MID is used to identify
Adding 1 yields 99, so XXX should be 98.
who is sending the information as well as establish
message priority and collision detection. The The receiver will add all the numbers and expects to
checksum is required to prevent invalid data from being see 0.
used. Between the MID and the checksum is the data. 128 + 95 + 23 + 45 + 123 + 99 = 512 or 0 for an 8-bit
Data is preceded by the Parameter Identifier (PID) sum with an 8-bit result.
which informs the receiver of the data type, data size
This would be valid.
and data scale factor. The J1708 specification
establishes the broadcast interval for each PID. After The receiver has two choices after discarding the bad
the first PID and its data, additional PIDs can be packet, if the data is a regularly scheduled broadcast,
transmitted one after another until the maximum packet the receiver can simply wait for the next broadcast
length is reached. while using the stale data. Or, the receiver can send a
request for the data to be resent.
TABLE 2: DATA FORMAT
byte 3 to N
byte 0 byte 1 byte 2 byte N + 1
(N not to exceed 20)

MID PID Data Additional PIDs and Checksum

Data

DS01230A-page 4 © 2008 Microchip Technology Inc.

 AN1230
Packet Message Identifier (MID) For example, J1587 extension on J1708 specifies the
MID for an engine to be 128. An instrument cluster is
The message identifier serves two purposes. The first assigned MID 140. If both of these devices attempt to
purpose is to allow a device access to the J1708 bus. gain access to the bus at the same time, the result of
To accomplish this function, no two transmitting device the MID collision will be the bitwise AND of the two
on the bus can have the same MID. If your bus must MIDs (see Table 3).
have many similar transmitters, then you will have to
allocate a block of MIDs for that function. The second Notice that the data that ends up on the bus is the same
purpose of the MIDs is to create a message priority as MID 128. This means that the only device that will
scheme. See Appendix B. see a collision is MID 140. MID 140 will begin the
collision retry procedure and will lose because the bus
J1587 defines the data format when the MID is > 127. will remain busy until MID 128 finishes sending its data.
The J1708 rules still apply, but the data payload is Once the bus is free again, MID 140 will be able to try
specified. again for bus access.

TABLE 3: MESSAGE IDENTIFIER COLLISION ARBITRATION EXAMPLE

Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7
MID128 0 0 0 0 0 0 0 1
MID140 0 0 1 1 0 0 0 1
Result 0 0 0 0 0 0 0 1

Payload A PID is a one byte number between 0 and 255. The

data size associated with a PID is determined by
The payload of a J1708 packet is a block of up to 19 allocating blocks of PID numbers for each required
bytes of data. J1708 does not define a data format for data size. A second page of PIDs is available by using
the payload. However, if your MID is ≥ 128, then your the extension PID 255 (see Table 5). This allows an
payload must conform to the J1587 extension to the additional 255 PIDs to be used. A third and fourth page
J1708 specification. Of course if you are not going live could also be defined by the same mechanism but the
on a real J1708/1587 data bus, then your data format current J1587 specification from SAE does not go
is your own business. beyond 1 extension.
All PIDs, after an extension PID, are taken for the next
Parameter Identifiers (PID) page. If a packet has 3 extension PIDs, then the
When you are using the J1587 extension, your payload remaining PIDs will be from page 4.
data consists of a series of Parameter Identifiers (PIDs)
followed by parameter data (see Table 4).

TABLE 4: PARAMETER IDENTIFIER USAGE

MID PID DATA PID DATA PID DATA Checksum

TABLE 5: EXTENSION PID USAGE

MID 255 (extension PID) PID from page 2 DATA PID from page 2 DATA Checksum

EUSART and J-1708 Library

To simplify the effort involved with creating a J1708
Advantages access node, a library was written to perform the low-
The EUSART aids in proper J1708 communications by level task of sending and receiving messages.
providing a busy bit indicating when the receive state The library continuously receives data from the J1708
machine is in operation, using a 16-bit Baud Rate bus into a pair of buffers. Transmissions to the J1708
Generator for a wide oscillator frequency range and by bus are scheduled and sent, but they are not queued.
allowing the transmit pin to be inverted, eliminating an The resources used by the driver are shown in Table 6.
external component.

© 2008 Microchip Technology Inc. DS01230A-page 5

AN1230
TABLE 6: RESOURCES USED BY THE DRIVER
Resource Used Purpose
USART TX and RX IRQ Data I/O
TIMER0 T0 IRQ Bus access timer and packet completion detector
GPR 73 bytes Buffers and working data
Program Memory 332 Words All driver code
To use the driver to monitor the data bus, simply watch To use the driver to send data to the data bus, simply
the j1708_active_buffer flag for a state change. load bytes into the j1708_tx_buffer. Put the
This flag points to the current buffer in use by the driver. number of bytes to send in j1708_tx_length and
There are two buffers, so the opposite buffer has fresh then call j1708_tx_data. The function,
data. If the flag is set, then the fresh data is stored in j1708_tx_data, will return as soon as the
j1708_rx_buffer0. If the flag is cleared, then the transmission is scheduled. This does not ensure that
fresh data is stored in j1708_rx_buffer1. The the data has been sent. As soon as the transmission is
number of bytes received into the buffer is stored in scheduled, the flag, j1708_tx_busy, will be set. The
j1708_rx_buffer0_count or j1708_rx_buffer1_count. application software must monitor this flag. When the
If the flag, j1708_checksum_error, is set, then the last flag clears, the transmission has been sent and the
reception had a checksum error. Once it is set by the transmitter is ready for a new message. Do not modify
driver, it stays set until cleared by the application the contents of the j1708_tx_buffer while
software. j1708_tx_busy is set.

FIGURE 3: J1708 DATA SEQUENCE FIGURE 4: J1708 RECEIVE

FLOWCHART
Begin
Begin

Yes
j1708_active_buffer changed? No
j1708_tx_busy==1

No Yes

Place data in j1708_tx_buffer. Yes j1708_checksum_error

Only 19 bytes.
Clear
j1708_checksum_error
No

Place byte count in j1708_tx_length.

0-19 are valid. Yes
j1708_active_buffer is 1
No

Call j1708_tx_data Read PID data from Read PID data from
j1708_rx_buffer 0 j1708_rx_buffer 1

End
End

DS01230A-page 6 © 2008 Microchip Technology Inc.

 AN1230
CONCLUSION
The J1708/1587 bus is a simple, robust, low-speed,
multi-master data bus that has been successfully used
in heavy trucking for many years. This bus has many
aspects such as low-cost and multi-master that could
be useful for other applications. The features of the
EUSART and the attached library simplify the task of
using J1708 in an application.

© 2008 Microchip Technology Inc. DS01230A-page 7

DS01230A-page 8
APPENDIX A:

U3
AN1230

680 Ω +12V
+5V
3 Output 1 12V
Input

5W

Ground
Ground

C7
C4
C5
14V

C6
C3

1μF
1μF
GND

10μF

0.1μF

0.1μF
4
2
LM294ØIMP

+5V
SCHEMATICS

+5V
+5V
U1
+5V

R9
4.7
J3 1 10 RCØ +5V
VDD RCØ/AN4/C2+ R3
4.7K

13 9
1 RAØ/ANØ/C1+/PD RC1/AN5/C2- RC1 U2
12 8 R5
2 RA1/AN1/C1-/Vref/PC RC2/AN6 RC2 1 RO VDD 8 B
11 RA2/AN2/TØCKI/INT/C1 7 2 7
3 RC3/AN7 RC3 47
4 6 3 RE
B 6
4 RA3/MCLR/VPP RC4/C2OUT/TX/CK R6
3 5 4 DE A5
RA4/AN3/T1G/OSC2 RC5/RX/DT DI GND A
5

HDR - 1X6
2 47
6 RA5/T1CK1/OSC1 GND 14 DS75176-SO
R4

4.7K

PIC16F688
C1
C2

2.2 μF
2.2 μF

RC1

RCØ
RC2
+5V

R2

R1
R7

220
220

220
3

CW
RC3

2
R8

D1
D2
D3
CCW

© 2008 Microchip Technology Inc.

 AN1230
APPENDIX B: MESSAGE ID ASSIGNMENT LIST
171 Driver Information Center
0-127 Defined by SAE J1708 172 Off-board Diagnostics #1
128 Engine #1 173 Engine Retarder
129 Turbocharger 174 Cranking/Starting System
130 Transmission 175 Engine #2
131 Power Takeoff 176 Transmission, Additional
132 Axle, Power Unit 177 Particulate Trap System
133 Axle, Trailer #1 178 Vehicle Sensors to Data Converter
134 Axle, Trailer #2 179 Data Logging Computer
135 Axle, Trailer #3 180 Off-board Diagnostics #2
136 Brakes, Power Unit 181 Communication Unit – Satellite
137 Brakes, Trailer #1 182 Off-board Programming Station
138 Brakes, Trailer #2 183 Engine #3
139 Brakes, Trailer #3 184 Engine #4
140 Instrument Cluster 185 Engine #5
141 Trip Recorder 186 Engine #6
142 Vehicle Management System 187 Vehicle Control Head Unit
143 Fuel System 188 Vehicle Logic Control Unit
144 Cruise Control 189 Vehicle Head Signs
145 Road Speed Indicator 190 Refrigerant Management Protection and
146 Cab Climate Control Diagnostics
147 Cargo Refrigeration/Heating, Trailer #1 191 Vehicle Location Unit – Differential
148 Cargo Refrigeration/Heating, Trailer #2 Correction
149 Cargo Refrigeration/Heating, Trailer #3 192 Front Door Status Unit
150 Suspension, Power Unit 193 Middle Door Status Unit
151 Suspension, Trailer #1 194 Rear Door Status Unit
152 Suspension, Trailer #2 195 Annunciator Unit
153 Suspension, Trailer #3 196 Fare Collection Unit
154 Diagnostic Systems, Power Unit 197 Passenger Counter Unit
155 Diagnostic Systems, Trailer #1 198 Schedule Adherence Unit
156 Diagnostic Systems, Trailer #2 199 Route Adherence Unit
157 Diagnostic Systems, Trailer #3 200 Environment Monitor Unit
158 Electrical Charging System 201 Vehicle Status Points Monitor Unit
159 Proximity Detector, Front 202 High Speed Communications Unit
160 Proximity Detector, Rear 203 Mobile Data Terminal Unit
161 Aerodynamic Control Unit 204 Vehicle Proximity, Right Side
162 Vehicle Navigation Unit 205 Vehicle Proximity, Left Side
163 Vehicle Security 206 Base Unit (Radio Gateway to Fixed End)
164 Multiplex 207 Bridge from SAE J1708Drivetrain Link
165 Communication Unit – Ground 208 Maintenance Printer
166 Tires, Power Unit 209 Vehicle Turntable
167 Tires, Trailer #1 210 Bus Chassis Identification Unit
168 Tires, Trailer #2 211 Smart Card Terminal
169 Tires, Trailer #3 212 Mobile Data Terminal
170 Electrical 213 Vehicle Control Head Touch Screen

© 2008 Microchip Technology Inc. DS01230A-page 9

AN1230
Appendix B – Message ID Assignment
List (Continued)
214 Silent Alarm Unit
215 Surveillance Microphone
216 Lighting Control Administrator Unit
217 Tractor/Trailer Bridge, Tractor Mounted
218 Tractor/Trailer Bridge, Trailer Mounted
219 Collision Avoidance Systems
220 Tachograph
221 Driver Information Center #2
222 Driveline Retarder
223 Transmission Shift Console – Primary
224 Parking Heater
225 Weighing System, Axle Group #1
226 Weighing System, Axle Group #2
227 Weighing System, Axle Group #3
228 Weighing System, Axle Group #4
229 Weighing System, Axle Group #5
230 Weighing System, Axle Group #6
231 Communication Unit – Cellular
232 Safety Restraint System
233 Intersection Preemption Emitter
234 Instrument Cluster #2
235- Reserved – to be assigned
255

DS01230A-page 10 © 2008 Microchip Technology Inc.

 AN1230
APPENDIX C: J1587 PARAMETER IDENTIFICATION ASSIGNMENT LIST
62 Retarder Inhibit Status
PID Parameter 63 Transmission Actuator Status #1
Single Data Character Length Parameters 64 Direction Switch Status
0 Request Parameter 65 Service Brake Switch Status
1(1) Invalid Data Parameter 66 Vehicle Enabling Component Status
Transmitter System Status 67 Shift Request Switch Status
2(1)
68 Torque Limiting Factor
3(1) Transmitter System Diagnostic
69 Two Speed Axle Switch Status
4 Reserved – to be assigned 70 Parking Brake Switch
5 (1) Underrange Warning Condition 71 Idle Shutdown Timer Status
(1) Overrange Warning Condition 72 Blower Bypass Value Position
6
73 Auxiliary Water Pump Pressure
7-30 Reserved – to be assigned
74 Maximum Road Speed Limit
31 Transmission Range Position
75 Steering Axle Temperature
32 Transmission Splitter Position
76 Axle Lift Air Pressure
33 Clutch Cylinder Position
77 Forward Rear Drive Axle Temperature
34 Clutch Cylinder Actuator Status
78 Rear Rear-Drive Axle Temperature
35 Shift Finger Actuator Status #2
79 Road Surface Temperature
36 Clutch Plates Wear Condition
80 Washer Fluid Level
37 Transmission Tank Air Pressure
81 Particulate Trap Inlet Pressure
38 Second Fuel Level (Right Side)
82 Air Start Pressure
39 Tire Pressure Check Interval
83 Road Speed Limit Status
40 Engine Retarder Switches Status
84 Road Speed
41 Cruise Control Switches Status
85 Cruise Control Status
42 Pressure Switch Status
86 Cruise Control Set Speed
43 Ignition Switch Status
87 Cruise Control High-Set Limit Speed
44 Attention/Warning Indicator Lamps
Status 88 Cruise Control Low-Set Limit Speed
45 Inlet Air Heater Status 89 Power Takeoff Status
46 Vehicle Wet Tank Pressure 90 PTO Oil Temperature
47 Retarder Status 91 Percent Accelerator Pedal Position
48 Extended Range Barometric Pressure 92 Percent Engine Load
49 ABS Control Status 93 Output Torque
50 Air Conditioner Compressor Clutch 94 Fuel Delivery Pressure
Status/Command 95 Fuel Filter Differential Pressure
51 Throttle Position 96 Fuel Level
52 Engine Intercooler Temperature 97 Water in Fuel Indicator
53 Transmission Synchronizer Clutch 98 Engine Oil Level
Value 99 Engine Oil Filter Differential Pressure
54 Transmission Synchronizer Brake 100 Engine Oil Pressure
Value
101 Crankcase Pressure
55 Shift Finger Positional Status
102 Boost Pressure
57 Transmission Actuator Status #2
103 Turbo Speed
58 Shift Finger Actuator Status
104 Turbo Oil Pressure
59 Shift Finger Gear Position
105 Intake Manifold Temperature
60 Shift Finger Rail Position
106 Air Inlet Pressure
61 Parking Brake Actuator Status

© 2008 Microchip Technology Inc. DS01230A-page 11

AN1230
Appendix C – J1587 Parameter ID 150 PTO Engagement Control Status
Assignment List (Continued) 151 ATC Control Status
107 Air Filter Differential Pressure 152 Number of ECU Resets
108 Barometric Pressure 153 Crankcase Pressure
109 Coolant Pressure 154 Auxiliary Input and Output Status #2
110 Engine Coolant Temperature 155 Auxiliary Input and Output Status #1
111 Coolant Level 156 Injector Timing Rail Pressure
112 Coolant Filter Differential Pressure 157 Injector Metering Rail Pressure
113 Governor Droop 158 Battery Potential (Voltage) – Switched
114 Net Battery Current 159 Gas Supply Pressure
115 Alternator Current 160 Main Shaft Speed
116 Brake Application Pressure 161 Input Shaft Speed
117 Brake Primary Pressure 162 Transmission Range Selected
118 Brake Secondary Pressure 163 Transmission Range Attained
119 Hydraulic Retarder Pressure 164 Injection Control Pressure
120 Hydraulic Retarder Oil Temperature 165 Compass Bearing
121 Engine Retarder Status 166 Rated Engine Power
122 Engine Retarder Percent 167 Alternator Potential (Voltage)
123 Clutch Pressure 168 Battery Potential (Voltage)
124 Transmission Oil Level 169 Cargo Ambient Temperature
125 Transmission Oil Level High/Low 170 Cab Interior Temperature
126 Transmission Filter Differential 171 Ambient Air Temperature
Pressure 172 Air Inlet Temperature
127 Transmission Oil Pressure 173 Exhaust Gas Temperature
Double Byte Data Parameters 174 Fuel Temperature
128 Component-specific request 175 Engine Oil Temperature
129-134 Reserved - to be assigned 176 Turbo Oil Temperature
135 Extended Range Fuel Delivery 177 Transmission Oil Temperature
Pressure (Absolute) 178 Front Axle Weight
136 Auxiliary Vacuum Pressure Reading 179 Rear Axle Weight
137 Auxiliary Gage Pressure Reading 180 Trailer Weight
138 Auxiliary Absolute Pressure Reading 181 Cargo Weight
139 Tire Pressure Control System Channel 182 Trip Fuel
Functional Mode
183 Fuel Rate
140 Tire Pressure Control System Solenoid
184 Instantaneous Fuel Economy
Status
185 Average Fuel Economy
141 Trailer, Tag, or Push Channel Tire
Pressure Target 186 Power Takeoff Speed
142 Drive Channel Tire Pressure Target 187 Power Takeoff Set Speed
143 Steer Channel Tire Pressure Target 188 Idle Engine Speed
144 Trailer, Tag, or Push Channel Tire 189 Rated Engine Speed
Pressure 190 Engine Speed
145 Drive Channel Tire Pressure 191 Transmission Output Shaft Speed
146 Steer Channel Tire Pressure Variable and Long Data Character
147 Average Fuel Economy (Natural Gas) Length Parameters
148 Instantaneous Fuel Economy 192 Multisection Parameter
(Natural Gas) 193 (1) Transmitter System Diagnostic Table
149 Fuel Mass Flow Rate (Natural Gas)

DS01230A-page 12 © 2008 Microchip Technology Inc.

 AN1230
Appendix C – J1587 Parameter ID Page 2 Single Byte Data Parameters
(modulo 256 value identified in parentheses)
Assignment List (Continued)
256(0) Request Parameter
194 Transmitter System Diagnostic Code
and Occurrence Count Table 257(1) Cold Restart of Specific Component
195 Diagnostic Data Request/Clear Count 258(2) Warm Restart of Specific Component
196 Diagnostic Data/Count Clear 259(3) Acknowledgement of Warm or Cold
Response Restart
197 Connection Management 260–377 Reserved – to be assigned
(4–121)
198 Connection Mode Data Transfer
378(122) Fare Collection Unit Status
199 Traction Control Disable State
379(123) Transit Door Status
200-223 Reserved – to be assigned
380(124) Articulation Angle
224 Immobilizer Security Code
381(125) Vehicle Use Status
225 Reserved for Text Message Acknowl-
edged 382(126) Transit Silent Alarm Status
226 Reserved for Text Message to Display 383(127) Vehicle Acceleration
227 Reserved for Text Message Display Double Data Character Length Parameters
Type 384(128) Component-specific request
228 Speed Sensor Calibration 385-446 Reserved – to be assigned
229 Total Fuel Used (Natural Gas) (129-190)
230 Total Idle Fuel Used (Natural Gas) 447(191) Passenger Counter
231 Trip Fuel (Natural Gas) Variable and Long Data Character
Length Parameters
232 DGPS Differential Correction
448(192) Page 2Multisection Parameter
233 Unit Number (Power Unit)
449(193) Reporting Interval Request
234 Software Identification
450(194) Bridge Filter Control
235 Total Idle Hours
451-499 Reserved – to be assigned
236 Total Idle Fuel Used
(195-243)
237 Vehicle Identification Number
500(244) Intersection Preemption Status and
238 Velocity Vector Configuration
239 Vehicle Position 501(245) Signage Message
240 Change Reference Number 502(246) Fare Collection Unit – Point of Sale
241 Tire Pressure 503(247) Fare Collection Unit – Service Detail
242 Tire Temperature 504(248) Annunciator Voice Message
243 Component Identification 505(249) Vehicle Control Head Keyboard
244 Trip Distance Message
245 Total Vehicle Distance 506(250) Vehicle Control Head Display Message
246 Total Vehicle Hours 507(251) Driver Identification
247 Total Engine Hours 508(252) Transit Route Identification
248 Total PTO Hours 509(253) Mile Post Identification
249 Total Engine Revolutions Special Parameters
250 Total Fuel Used 510(254) Page 2Data Link Escape
251 Clock 511(255) Page 2Extension
252 Date Note 1: These PIDs are superseded by PIDs 194,
253 Elapsed Time 195 and 196.

Special Parameters
254 Data Link Escape
255 Extension

© 2008 Microchip Technology Inc. DS01230A-page 13

AN1230
NOTES:

DS01230A-page 14 © 2008 Microchip Technology Inc.

Note the following details of the code protection feature on Microchip devices:
• Microchip products meet the specification contained in their particular Microchip Data Sheet.

• Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the
intended manner and under normal conditions.

• There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our
knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data
Sheets. Most likely, the person doing so is engaged in theft of intellectual property.

• Microchip is willing to work with the customer who is concerned about the integrity of their code.

• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not
mean that we are guaranteeing the product as “unbreakable.”

Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our
products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts
allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.

Information contained in this publication regarding device Trademarks

applications and the like is provided only for your convenience
The Microchip name and logo, the Microchip logo, Accuron,
and may be superseded by updates. It is your responsibility to
dsPIC, KEELOQ, KEELOQ logo, MPLAB, PIC, PICmicro,
ensure that your application meets with your specifications.
PICSTART, rfPIC, SmartShunt and UNI/O are registered
MICROCHIP MAKES NO REPRESENTATIONS OR
trademarks of Microchip Technology Incorporated in the
WARRANTIES OF ANY KIND WHETHER EXPRESS OR
U.S.A. and other countries.
IMPLIED, WRITTEN OR ORAL, STATUTORY OR
OTHERWISE, RELATED TO THE INFORMATION, FilterLab, Linear Active Thermistor, MXDEV, MXLAB,
INCLUDING BUT NOT LIMITED TO ITS CONDITION, SEEVAL, SmartSensor and The Embedded Control Solutions
QUALITY, PERFORMANCE, MERCHANTABILITY OR Company are registered trademarks of Microchip Technology
FITNESS FOR PURPOSE. Microchip disclaims all liability Incorporated in the U.S.A.
arising from this information and its use. Use of Microchip Analog-for-the-Digital Age, Application Maestro, CodeGuard,
devices in life support and/or safety applications is entirely at dsPICDEM, dsPICDEM.net, dsPICworks, dsSPEAK, ECAN,
the buyer’s risk, and the buyer agrees to defend, indemnify and ECONOMONITOR, FanSense, In-Circuit Serial
hold harmless Microchip from any and all damages, claims, Programming, ICSP, ICEPIC, Mindi, MiWi, MPASM, MPLAB
suits, or expenses resulting from such use. No licenses are Certified logo, MPLIB, MPLINK, mTouch, PICkit, PICDEM,
conveyed, implicitly or otherwise, under any Microchip PICDEM.net, PICtail, PIC32 logo, PowerCal, PowerInfo,
intellectual property rights. PowerMate, PowerTool, REAL ICE, rfLAB, Select Mode, Total
Endurance, WiperLock and ZENA are trademarks of
Microchip Technology Incorporated in the U.S.A. and other
countries.
SQTP is a service mark of Microchip Technology Incorporated
in the U.S.A.
All other trademarks mentioned herein are property of their
respective companies.
© 2008, Microchip Technology Incorporated, Printed in the
U.S.A., All Rights Reserved.
Printed on recycled paper.

Microchip received ISO/TS-16949:2002 certification for its worldwide

headquarters, design and wafer fabrication facilities in Chandler and
Tempe, Arizona; Gresham, Oregon and design centers in California
and India. The Company’s quality system processes and procedures
are for its PIC® MCUs and dsPIC® DSCs, KEELOQ® code hopping
devices, Serial EEPROMs, microperipherals, nonvolatile memory and
analog products. In addition, Microchip’s quality system for the design
and manufacture of development systems is ISO 9001:2000 certified.

© 2008 Microchip Technology Inc. DS01230A-page 15

 WORLDWIDE SALES AND SERVICE
AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPE
Corporate Office Asia Pacific Office India - Bangalore Austria - Wels
2355 West Chandler Blvd. Suites 3707-14, 37th Floor Tel: 91-80-4182-8400 Tel: 43-7242-2244-39
Chandler, AZ 85224-6199 Tower 6, The Gateway Fax: 91-80-4182-8422 Fax: 43-7242-2244-393
Tel: 480-792-7200 Harbour City, Kowloon Denmark - Copenhagen
India - New Delhi
Fax: 480-792-7277 Hong Kong Tel: 45-4450-2828
Tel: 91-11-4160-8631
Technical Support: Tel: 852-2401-1200 Fax: 45-4485-2829
Fax: 91-11-4160-8632
http://support.microchip.com Fax: 852-2401-3431
India - Pune France - Paris
Web Address:
Australia - Sydney Tel: 91-20-2566-1512 Tel: 33-1-69-53-63-20
www.microchip.com
Tel: 61-2-9868-6733 Fax: 91-20-2566-1513 Fax: 33-1-69-30-90-79
Atlanta Fax: 61-2-9868-6755 Germany - Munich
Duluth, GA Japan - Yokohama
China - Beijing Tel: 49-89-627-144-0
Tel: 678-957-9614 Tel: 81-45-471- 6166
Tel: 86-10-8528-2100 Fax: 49-89-627-144-44
Fax: 678-957-1455 Fax: 81-45-471-6122
Fax: 86-10-8528-2104 Italy - Milan
Boston Korea - Daegu
China - Chengdu Tel: 39-0331-742611
Westborough, MA Tel: 82-53-744-4301
Tel: 86-28-8665-5511 Fax: 39-0331-466781
Tel: 774-760-0087 Fax: 82-53-744-4302
Fax: 86-28-8665-7889 Netherlands - Drunen
Fax: 774-760-0088 Korea - Seoul
China - Hong Kong SAR Tel: 82-2-554-7200 Tel: 31-416-690399
Chicago
Tel: 852-2401-1200 Fax: 82-2-558-5932 or Fax: 31-416-690340
Itasca, IL
Tel: 630-285-0071 Fax: 852-2401-3431 82-2-558-5934 Spain - Madrid
Fax: 630-285-0075 China - Nanjing Tel: 34-91-708-08-90
Malaysia - Kuala Lumpur
Tel: 86-25-8473-2460 Tel: 60-3-6201-9857 Fax: 34-91-708-08-91
Dallas
Addison, TX Fax: 86-25-8473-2470 Fax: 60-3-6201-9859 UK - Wokingham
Tel: 972-818-7423 China - Qingdao Tel: 44-118-921-5869
Malaysia - Penang
Fax: 972-818-2924 Tel: 86-532-8502-7355 Fax: 44-118-921-5820
Tel: 60-4-227-8870
Detroit Fax: 86-532-8502-7205 Fax: 60-4-227-4068
Farmington Hills, MI China - Shanghai Philippines - Manila
Tel: 248-538-2250 Tel: 86-21-5407-5533 Tel: 63-2-634-9065
Fax: 248-538-2260 Fax: 86-21-5407-5066 Fax: 63-2-634-9069
Kokomo China - Shenyang Singapore
Kokomo, IN Tel: 86-24-2334-2829 Tel: 65-6334-8870
Tel: 765-864-8360 Fax: 86-24-2334-2393 Fax: 65-6334-8850
Fax: 765-864-8387
China - Shenzhen Taiwan - Hsin Chu
Los Angeles Tel: 86-755-8203-2660 Tel: 886-3-572-9526
Mission Viejo, CA Fax: 86-755-8203-1760 Fax: 886-3-572-6459
Tel: 949-462-9523
China - Wuhan Taiwan - Kaohsiung
Fax: 949-462-9608
Tel: 86-27-5980-5300 Tel: 886-7-536-4818
Santa Clara Fax: 86-27-5980-5118 Fax: 886-7-536-4803
Santa Clara, CA
China - Xiamen Taiwan - Taipei
Tel: 408-961-6444
Tel: 86-592-2388138 Tel: 886-2-2500-6610
Fax: 408-961-6445
Fax: 86-592-2388130 Fax: 886-2-2508-0102
Toronto
China - Xian Thailand - Bangkok
Mississauga, Ontario,
Tel: 86-29-8833-7252 Tel: 66-2-694-1351
Canada
Fax: 86-29-8833-7256 Fax: 66-2-694-1350
Tel: 905-673-0699
Fax: 905-673-6509 China - Zhuhai
Tel: 86-756-3210040
Fax: 86-756-3210049

01/02/08

DS01230A-page 16 © 2008 Microchip Technology Inc.