Cougar281
September 13th, 2024, 08:07 AM
Figured I'd post this here, since there doesn't really seem to be a better place, and try to tag @Blacky.
I was trying to build a CAX8, and was finally successful, but frankly, with zero credit to the 'template' file provided by EFILive. I read that file multiple times, but was unable to create a file that worked using it.
I finally resorted to looking for a cax8 that someone had posted that was in line with what I was looking to make. So I found a Cummins/transmission DTC CAX8 that fit the bill, and from there, with the info I had, I was able to make a CAX8 that works.
For example, this was my first iteration:
24668
After I added a few more, each one had it's own folder and parameters table, which was 'kludgy'. So after some thinking and tinkering, this was my cleanup result:
24669
My suggestion is, in addition to having the long drawn out explanation of everything, which is CERTAINLY not bad to have, include some actual examples of simple things like DTCs, more complex things like tables, etc (with bogus addresses if you want to obfuscate). Using that cax8 that was posted for the Cummins world, I was able to build a functional cax8 for the application I was looking for in the GM world, and in the format that it was posted, it was 'messy', at least how I initially applied it (I'm not sure how it shows up with the controller it was made for), and I was actually able to clean it up. It would be even better if DTC related cax files could be in a separate branch similar to how it's done with EFILIve mapped DTCs, but from what I've gathered, that functionality isn't possible with cax/cax8 files.
I was trying to build a CAX8, and was finally successful, but frankly, with zero credit to the 'template' file provided by EFILive. I read that file multiple times, but was unable to create a file that worked using it.
I finally resorted to looking for a cax8 that someone had posted that was in line with what I was looking to make. So I found a Cummins/transmission DTC CAX8 that fit the bill, and from there, with the info I had, I was able to make a CAX8 that works.
For example, this was my first iteration:
24668
After I added a few more, each one had it's own folder and parameters table, which was 'kludgy'. So after some thinking and tinkering, this was my cleanup result:
24669
My suggestion is, in addition to having the long drawn out explanation of everything, which is CERTAINLY not bad to have, include some actual examples of simple things like DTCs, more complex things like tables, etc (with bogus addresses if you want to obfuscate). Using that cax8 that was posted for the Cummins world, I was able to build a functional cax8 for the application I was looking for in the GM world, and in the format that it was posted, it was 'messy', at least how I initially applied it (I'm not sure how it shows up with the controller it was made for), and I was actually able to clean it up. It would be even better if DTC related cax files could be in a separate branch similar to how it's done with EFILIve mapped DTCs, but from what I've gathered, that functionality isn't possible with cax/cax8 files.