Reading timing on 7747

For those of you brave enough to try the beta releases, please ask your questions and post your issues here! Remember, the more info the better!

Moderators: robertisaar, dex

Locked
jp78
Posts: 3
Joined: Sat Jul 25, 2009 1:47 pm

Reading timing on 7747

Post by jp78 » Sat Jul 25, 2009 1:49 pm

Read over on thirdgen about being able to read SA and PW through ALDL. Anyone know how to set it up?

User avatar
Six_Shooter
Posts: 590
Joined: Sun May 06, 2007 7:32 am

Post by Six_Shooter » Sat Jul 25, 2009 4:30 pm

It requires changing look up addresses in the bin. Use of a hex editor is required.

For actual address changes and values talk to RBob on TGO.

User avatar
honken
Posts: 111
Joined: Wed Dec 15, 2004 6:05 am
Location: sweden

Post by honken » Sun Jul 26, 2009 1:05 am

Hade it on my computer havent used it(using another ecm), i think its from rob.

tuning issue

--------------------------------------------------------------------------------

Since it's usually a one time deal I just edit the BIN directly and leave it. To do that open the BIN in Tuner Pro (TP) and open the hex editor:

Tools->Advanced->Hex Editor

Now you have a screen of gobbydy-gook. The left most column being the address within the PROM/BIN. The center being the hex, and the right being the hex in text.

For the '7747 we want to change these locations:

PW in place of PromID:

Addr: Value:
$D4E7 $00
$D4E8 $AB
$D4E9 $00
$D4EA $AC

SA in place of PromID:

Addr: Value:
$D4E7 $00
$D4E8 $66
$D4E9 $00
$D4EA $67

Now you won't find those addresses directly. They are the logical addresses once the PROM has been inserted into the ECM. To get the physical address need to drop the Dxxx portion off (or subtract $D000 from each address).

So we are looking for $4E7, scroll down through the hex editor until the address line 000004E0 is found. Each byte across is one more address. So $4E7 is the 8th byte over and is $D0 in value (the bottom status bar shows the address the cursor is at.

The 4 byte values in sequence is $D0 $02 $D0 $03, which is the location of the PROM ID. So type over those values with the data above:

$00 $AB $00 $AC

Then save it:

Action->Commit Changes

That BIN when used will now output the injector PW in place of the PromID.

Can put the SA value in place of O2 x-counts. For this edit BIN location: $50B

Go to that address in the hex editor and find: $00 $BA

Over write with $00 $67 (only need the LSB).

Then commit the changes. You may also need to save the BIN itself from the TP File->Save.

This will update the checksum.


the '747 junkies out there a bunch of tables have the RPM scaling as follows:

400
600
800
1200
1600
2000
2400
3200
4000

Nine RPM values for a 9 line table. The tables include:

TPS vs RPM THRESH FOR WOT TBL @ $D47D
WOT FUEL @ $D486
RETARD ATTACK RATE vs RPM @ $D18D
MAX KNK RETARD LIMITS IN PWR ENR vs RPM @ $D17F
RETARD RECOVERY RATE vs RPM @ $D196

Then to get the sync PW on the ALDL line make these changes at the addresses shown:

Addr: Value:
$D4E7 $00
$D4E8 $AB
$D4E9 $00
$D4EA $AC

This puts the PW into the PROMID field of the scan tool. Take whatever value is displayed and multiply it by .01526 and add in the injector bias value (from $D2DA) and the end result is the PW in milli-seconds. So if the PROMID is 232 and the injector bias is .397 msec, then 232 * .01526 + 0.397 = 3.94 milli-seconds.

jp78
Posts: 3
Joined: Sat Jul 25, 2009 1:47 pm

Post by jp78 » Mon Aug 17, 2009 6:18 pm

Got it to work on 7747. Prom ID displays PW and cross counts shows SA.
Does anyone know if this applies to an 8747?

User avatar
honken
Posts: 111
Joined: Wed Dec 15, 2004 6:05 am
Location: sweden

Post by honken » Tue Aug 18, 2009 1:33 am

Mistake hade for 8746...
delated.

Locked