I’m capturing raw GM CAN traffic with a Macchina M2 and mapping it to usable ECM and TCM logging channels. My current focus is E92 and E38 ECMs and their transmission interfaces.
In my current setup, I’m recording about 2,800 frames per second to SD without observed loss. That’s an observed rate, not a confirmed limit of the M2 or card.
Does anyone know of public maps, DBCs, documentation, or previous threads identifying message IDs, sending modules, signal positions, scaling, units, and validity bits? I’m also interested in methods for matching broadcasts and diagnostic responses to known scanner channels.
I’ve looked through the Giuthub, commaai and a few other public sources, but I’m looking for additional controller-specific mappings or validation methods.
GM Gen III, IV, V and V+ CAN data mapping
-
gixxer92
- Posts: 19
- Joined: Sat Mar 03, 2018 3:08 pm
- cars: 1986 Camaro IROC (LS7/Tremec Magnum 6-speed)
1988 Firebird Trans Am
2017 Chevrolet Silverado, 6.6L L8T, 10 Speed
2017 Indian Road Master
-
kur4o
- Posts: 1153
- Joined: Sun Apr 10, 2016 11:20 am
Re: GM Gen III, IV, V and V+ CAN data mapping
If you have bin files out of pcm and tcm you can easily find what is being sent and received through bin analysis, there is some RX and TX tables, you can even trace each message format to specific ram and figure what it is.
Broadcast data vs data logging format is vastly different, most data logging uses active communication and request specific PIDs or Ram addresses.
broadcast data is for passive logging and is limited to what is configured in module, with fixed rates and data.
Broadcast data vs data logging format is vastly different, most data logging uses active communication and request specific PIDs or Ram addresses.
broadcast data is for passive logging and is limited to what is configured in module, with fixed rates and data.
-
fl0wl0w
- Posts: 34
- Joined: Thu Jun 21, 2018 4:44 pm
- cars: L83/8L90 swapped 2013 W204 Mercedes, 1986 LS3 Swapped BMW E30, 1995 LS swapped GMC Truck, Custom Vehicle
-
gixxer92
- Posts: 19
- Joined: Sat Mar 03, 2018 3:08 pm
- cars: 1986 Camaro IROC (LS7/Tremec Magnum 6-speed)
1988 Firebird Trans Am
2017 Chevrolet Silverado, 6.6L L8T, 10 Speed
2017 Indian Road Master
Re: GM Gen III, IV, V and V+ CAN data mapping
Thanks, that’s the path I’m working down now. I’ve also got the 2018 revisions of GMW3110 and the GMW8772. They’ve really helped make sense of what I’m seeing in the BINs, especially how the transmitted CAN data ties back to the variables used in the algorithms and calculations.
Pretty cool to see the amount of data coming on to the SD card that you can't funnel through a USB cable.
-
KingAustraliaggGG
- Posts: 60
- Joined: Fri Nov 15, 2024 2:19 pm
- cars: 323i 1999 e46 sedan m52tub25 ms42 hx35w
328ci 1999 e46 coupe m52tub28 ms42
vy 2002 holden wagon executive l67 bottom end/36 top swap corn fed boost manifold ex44 external turbo hx40 holset
vs holden sedan turbo gt3582r
Re: GM Gen III, IV, V and V+ CAN data mapping
Anyone got adx files for ve ss l98
-
antus
- Site Admin
- Posts: 10060
- Joined: Sat Feb 28, 2009 10:34 am
- cars: TX Gemini 2L Twincam 8psi
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Subaru WRX 2007
Re: GM Gen III, IV, V and V+ CAN data mapping
Not the right tool for the job. No native can bus support. Try the latest pcmlogger from the latest pcmhammer development version. It has a default dash/monitor and can import ADX and let you map can pids to the guages.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396