Universal patcher master j1939 logging

[04colyZQ8]

I want to capture all traffic from tool to pcm or perhaps any traffic on protocol J1939 at can baud 500k, I think it’s 29 bit bit might be 11.

I know 500k is unconventional for j1939

Typically it’s 250k

Can I use either mongoose pro 2 gm
Or avt852

To log this? If so what settings?

I never seem to have great luck with using universal patchers j console

The tool is f4, and the pcm header as set in elm format would be:
At sh 7f0

[antus]

I have been using it for vpw so I cant speak to can bus and havnt tried filtering. but either tool should be capable. you'd need to use mongoose for the j2534 logger tool. j1939 is a different layer to can and speed, so that you want j1939 isnt relevant to can 500k. Depending how much data is on the bus and what filtering you use you can over run the pc side easily. something to keep in mind. if you hit this then log to file not to screen usually helps as streaming to disk is less taxing than so many display updates.

[MudDuck514]

I want to capture all traffic from tool to pcm or perhaps any traffic on protocol J1939 at can baud 500k, I think it’s 29 bit bit might be 11.

I know 500k is unconventional for j1939

Typically it’s 250k

Can I use either mongoose pro 2 gm
Or avt852

To log this? If so what settings?

I never seem to have great luck with using universal patchers j console

The tool is f4, and the pcm header as set in elm format would be:
At sh 7f0

Isn't the J1939 Protocol for "Heavy Duty Vehicles" such as 18-Wheeler Tractors and Busses?
Is that what you are working on? Or are you working on a smaller vehicle such as a car or light truck?
Mike
p.s. I THINK the "J1939 Protocol" uses a round connector. Not the typical 16-pin one found in a passenger car.

[antus]

I think there are several different parts of the standard and it has evolved and changed over the years like other standards. A friend of mine works in commercial vehicle telematics and I know they come across it often in commercial vehicles, and the ones that have it they can easily support. Often the data is on the normal OBD connector, and often the round one.

This document summarises it well, and then lists various parts of the standard by name that come under the same umbrella.

https://cdn.vector.com/cms/content/know ... _J1939.pdf

Code: Select all

7.0 Additional Sources
SAE Documents
[1] SAE J1939 Recommended Practice for a Serial Control and Communications Vehicle Network
[2] SAE J1939-01 Recommended Practice for Control and Communications Network for On-Highway Equipment
[3] SAE J1939-02 Agricultural and Forestry Off-Road Machinery Control and Communication Network
[4] SAE J1939-03 On Board Diagnostics Implementation Guide
[5] SAE J1939-05 Marine Stern Drive and Inboard Spark-Ignition Engine On-Board Diagnostics Implementation Guide
[6] SAE J1939-11 Physical Layer - 250k bits/s, Twisted Shielded Pair
[7] SAE J1939-13 Off-Board Diagnostic Connector
[8] SAE J1939-14 Physical Layer, 500k bits/s
[9] SAE J1939-15 Reduced Physical Layer, 250K bits/sec, Un-Shielded Twisted Pair (UTP)
[10] SAE J1939-21 Data Link Layer
[11] SAE J1939-31 Network Layer
[12] SAE J1939-71 Vehicle Application Layer
[13] SAE J1939-73 Application Layer - Diagnostics
[14] SAE J1939-74 Application - Configurable Messaging
[15] SAE J1939-75 Application Layer - Generator Sets and Industrial
[16] SAE J1939-81 Network Management
[17] SAE J1939-82 Compliance - Truck and Bus
[18] SAE J1939-84 OBD Communications Compliance Test Cases for Heavy Duty Components and Vehicles 

[MudDuck514]

Antus, thanks for the info as it is good to know, as this is how we learn!

Mike

[04colyZQ8]

Yes I’ll check that guide out it falls under marine in my case