2018 68 CM2350B Stock File

[Kunokeski]

Does anyone have a stock file for the following:
2018 68rfe
D090066.03

[VotableSole]

24197

[Kunokeski]

Thank you!

[Jim P]

That files only been posted on the forum a half dozen times or so lol

[Kunokeski]

That files only been posted on the forum a half dozen times or so lol

Still learning and I also found the OneDrive.

Thanks for the patience [emoji120].

[Kunokeski]

Jim, do you have a CAX for DTCs?

[Jim P]

The ones I’ve got posted on the forum

[Jim P]

FYI, if you are attempting a delete, turning DTC’s off is not enough.

[Kunokeski]

Well known, just trying to learn.

[Jim P]

Each and every calibration and revision has different sized fault tables and the addresses to them are different from calibration to calibration and revision to revision. There’s a table that says which fault codes are in the specific calibration/revision, an error index table/path table, some faults have more than 1 fault path, then there’s the MIL table that matches the error index table and the J2012 “P code” table that matches up a P code to a fault in the index table. They are all 16 bit unsigned integers.

[Jim P]

Searching for these P codes in this order will get you very very near the beginning of the J2012 P code table in the 2018 32370831AD calibration.

P0341
P0336
P2123
P2122
P0524

[Jim P]

The very beginning of the J2012 P code table is P0606 and the table has 1042 elements.

[Kunokeski]

Searching for these P codes in this order will get you very very near the beginning of the J2012 P code table in the 2018 32370831AD calibration.

P0341
P0336
P2123
P2122
P0524

I'm working off of the assumption that the calibration you're referring to is .xcal? Or am I off base?

[Jim P]

.bin file

[Kunokeski]

That would have been my next guess.

Do you think there

[Jim P]

Your question got cut off

[Kunokeski]

Yeah I'm not sure why I even bother to reply on the app anymore. My mistake.

Do you find any value in the xcal conversion tool?

[Jim P]

I do most things in .bin

[Kunokeski]

I'll start there then.

Am I on the right path? Link (https://www.sae.org/standards/content/j2012da_201812/)

[Jim P]

I wouldn’t spend the money on that

[Kunokeski]

I figured as much. Thanks for the direction.

[Jim P]

In the tune files themselves is a table that tells you exactly what Cummins fault codes are used in the tune file, the fault index table, MIL table and a table linking P codes to the fault index table. The fault index table, MIL table and J2012 P code linking table are all the exact same size and matching so the first element in each of those 3 tables are all tied together and so on down the tables. Getting whatever from that site won’t tell exactly what’s in each tune file or where.

[Jim P]

The fault index table uses Cummins fault codes so you need to use the P code table in the tune file to know exactly which Cummins fault code is using what P code.

[Kunokeski]

Referencing your 52210052 file I can see what you're talking about and I agree now that the SAE table doesn't do much good. ( Again I'm learning as quickly as I can and realize that was a bit off in the weeds )

I have other hurdles to get past prior to being able to piece it together. Thank you for the help.

[Jim P]

Nope the SAE table does nothing to help

[Kunokeski]

It’s clear I need a bit more information than what’s floating around. Any suggestions on where to start?

[Kunokeski]

Any suggestions for reading the stock file? My understanding is that I will probably be best off using CalTerm or might be able to use TunerPro with a fair amount of setup.