ADX files

[PowerAddict]

is there an ADX file for the '7727 that shows spark advance?

[Six_Shooter]

For what code?

There are a few differeny codes used in the '7727 due to the variety of vehicles it was used in.

[PowerAddict]

forgive my ignorance, what do you mean by "what code"?

its a '90 TBI truck...although I don't know if that tells you anything.

[EagleMark]

That would tell us you are using the wrong ECM numbers? Or have converted to a MPFI system?

If it is by chance a 7747 which came in many 90 TBI vehicles? Then the latest $42 XDF and ADX will show actual spark advance if you apply the hack to the bin, burn chip and use it. Then the ADX will show spark advance.

Read the comments of the hack. It changes some ALDL data stream output to include spark advance instead of other items like Prom ID or O2 crosscounts etc... worthless stuff...

[PowerAddict]

oops, i meant '7747 you're right.

Where can I find the comments on the hack so I can change it?

Thanks!

[PowerAddict]

okay so:

I found the new ADX files and XDF files and uploaded them and they work...kind of.

Files: V5.2 ADX and 5.9.3 XDF


There's:

Spark advance from hack*
BPW ms from hack*
MPG from hack*
and there's also AutoProm 1 WB AFR

We don't have a wideband on here, is that a calculated number? It almost seems like it'd be right, but it doesn't change too much when driving.
BPW is a large number like 144.77 in RED font, and just stays doesn't do anything
MPG changes but I don't think its accurate
The spark advance kind of seems like it works, but then goes to like 79 and above and is in RED font. Is there a "hack" or something I still need to install for these?

[Six_Shooter]

Since you don't have any of those hacks, more accurately called "patches", applied to your bin, and no Autoprom with a WBO2 sensor connected to one of the ad channels, you ignore those numbers, they do not represent anything of use.

[EagleMark]

Right!

You need to apply the hack/patch to your bin file, then burn a chip and use it! Then the spark advance and BPW including calculation for Injector Duty Cycle will show accuratly in your ADX data log.

AutoProm WB will not work unless you have a AutoProm, Wideband and wired it to AutoProm.

[PowerAddict]

alright, that is what I assumed. But, where do I get the hack? I'd really like to see spark advance.

[EagleMark]

Lets start with Tunerpro RT open, View, Show Parameter Tree. Then in the tree there are a few choices as well. I've set up categories in $42 so use it!

The hack or patch is in there just have to apply it to new bin, burn chip and use it.

[PowerAddict]

okay, i searched an old thread and saw the parameter tree > category > patches > hacks

It says change to 0067. I think I did that? I dont' know it doesn't seem to be working.

[EagleMark]

Save the bin after the change and burn a new chip for ECM...

[PowerAddict]

can I do that while in emulation/datalogging mode?

I'm sorry these are dumb questions!

[EagleMark]

Only if you have an emulator! Do you have an AutoProm or Ostrich?

[PowerAddict]

yeah, I have the AutoProm. I think I understand. I didn't realize I had to save the Bin, I thought it was live when you click the Update button. Which is also why I didn't know I would need to burn to chip - but I suppose that makes sense. I gotcha. Thank you.

[EagleMark]

Well you have to have bin, ADX and XDF loaded in TunerPro. To Emulate you need to change Mask ID to AA, this disables checksum. Then upload bin to emulator, Verify, then Emulate. Turn key on and look for on, flash, on and then it will go off when started.

Not sure the patches apply properly when emulating? I'd have all them done before upload to emulator.

Have you set up Tools, Preferences and Data Acq/Emulation for the AutoProm? Check find hardware at startup and every time you open TP with AP attatached it will find it and beep.

[PowerAddict]

okay, I have all that (as I just mentioned in my other thread, it is possible I wasn't using the .bin from the old EPROM).

I have set up the AutoProm as you mentioned, it beeps just fine. It goes green and says "emulating" when I click emulate.


What do you mean about the change Mask ID to AA?

[EagleMark]

Look up Mask ID in the XDF in PROM Mask ID folder... it should be 42, change it to AA. This will disable checksum or you will have issues when emulating if you change anything.

When it is set to 42 and you make changes, TunerPro updates the Checksum to correct for changes made. The ECM checks to see checksum is correct or you get a code 51 Prom.

After you have bin open in TunerPro, then Upload to emulater, always Verify! It checks Emulater to bin loaded in TunerPRo to make sure the upload went well! Then emulate.