Im running $od and was wondering if it was possible to use a different mask. Its a 7747 ecm. Im starting to get a grasp on on of this but am wondering about the differences in mask?
Printable View
Im running $od and was wondering if it was possible to use a different mask. Its a 7747 ecm. Im starting to get a grasp on on of this but am wondering about the differences in mask?
Also unrelated, I just installed a new Davis Unified dizzy and screamin demon coil and the instructions with coil says to open plug gap to .065! has anyone else used these coils and that much gap, seems way extreme to me. Thanks
Not so extreme. My Chevy v6 calls for a factory setting of 0.060".
$0D is not correct mask for '7747 ECM...Quote:
Originally Posted by gttagO
Agreed! You cannot change the code in a 7747 easily. With the C3 ecm the easiest way to change mask is to change ecm.
Sorry I meant 7427! been doin a lot of reading on here and got mixed up. Anyways what I was wondering about is using a diff spark table outa another bin that is a little more aggressive to play with. Currently using BJLF adv. $Od TPS v251 and was wanting to know how to use more aggressive spark table while tuning ve. Im way rich now so thinkin more adv. wont hurt. Any suggestions for diff spark tables? The more I read on hear the better Im understanding how things work and what their for.
And can u/what benefits if any to using diff definition files for same bin? Hope this isn't to confusing as im trying to explain it on a limited knowledge base. HOPEFULLY I can keep putting this stuff together until I can use it effectively. THANKS and sorry for so many probably stupid questions.
tunerpro doesn't know how your bin works at all. it's just a collection of numbers in certain placesQuote:
And can u/what benefits if any to using diff definition files for same bin?
so to modify your bin, tunerpro needs each table, constant, switch etc. to be defined so it knows where it's located in the bin, and also how to do some math so you're seeing something you can read '2000 RPM' instead of a raw value 0x1234 or whatever
a 'better' definition file might have more tables and variables defined, more accurate math, have them named better, have them in categories so they're easy to find, and might even have some notes built-in so you know how things work.
a definition can also have patches in it that change the actual programming in your bin, so a better definition might have more of those patches
usually there's a 'best' xdf definition out there to use for each bin mask since people work on them together, so it's more using the newest one rather than looking for the right one
this should be obvious but if you use a definition file not designed specifically for your bin mask it'll mostly be gibberish and you'll break stuff.