[rockin_rick]

With the help of Barney (95BlackTan50), I believe that we have found the ISC Transfer TABLE (FN8000?) and matching scaling functions in CBAZA. The ISC Transfer is at location E994h. It is a 6x10 table with air as the X axis, and load (perload) as the Y axis. Note, in CBAZA this is a table, not a function like in A9L. The CRAI8 strategy document shows the ISC Transfer as a table, too.

The X and Y scaling shown is what we believe them to be -

X = FN061 - X_Scaling_ISC_Air (CBAZA location E822h)
Y = FN060 - Y_Scaling_ISC_Load (CBAZA location E802h)

FN060 and FN061 are what the CRAI8 doc uses for the scaling functions of the ISC Transfer (FN8000). Barney searched out these scaling functions in the binary.

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

We had a bit of help with this from a web page that Barney found on the internet:

http://eelink.net/~p-nowak/EEC-Archive/msg09272.html

In this, Alex Smith (anybody know who he is?) describes how he has decoded the EARS (anybody know what this is?) strategy or calibration. He also mentions that it is "VERY similar to CBAZA". It lists FN8000, FN060, and FN061 as what we have them as. In the list of EARS, it says that ISC Transfer is physically located in the binary between FN875N (ISC_idle_air_neutral) and LUGTIM (spark/fuel_lug_time_limit). CBAZA also has these in the same order, and I searched in between them and found this 6x10 table that made sense as ISC Transfer. I then did continue to search the other parts of the binary, and didn't come up with another 6x10 table with values that made sense.

I tested this with my J4J1 based tune by setting all rows of columns 1 - 4 to about 5% more DC. Columns 0 & 5-9 remained unchanged. I loaded this calibration into another switch position. Then I drove the car around a bit with the 'stock' J4J1 setting to get it stabilized. I then pulled into a parking lot, and watched the ISCDC value in calcon. It was about .29 when idling, and when I turned the switch, it jumped right up to ~.34 and RPMs increased about 50. It then started creeping down in it's adaptive fashion. I then turned the switch back, and the ISCDC jumped back down to .29. These values seemed right in line with the table.

For another test, I was going down the interstate, and switched to the test calibration. I went down the off ramp to the stop light, and sat there for a minute. When I came to a stop, the ISCDC was higher than normal, and the RPMs were about 200 more than usual.

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

This is J4J1 & ZA0-



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

This is T4M0, W4H0, & U4P0-





Rick

[95BlackTan50]

Rick,

I haven't tried any changes yet but I did go back to some old datalogs to check on something that I could never quite figure out. When I was setting up my ISC_Drive_Idle_Air for my AODE, I could never get the ISCDC to be above 0.8125 even though I set the Idle Air to 3ppm at 1500 RPM. According to the stock ISCTF, a value of 3ppm will set the ISCDC to 0.8115. Pretty close in my book.

I've posted the BinComp and BinEdit programs that Rick and I have been using at the following link:

http://home.comcast.net/~barney.anderso ... inComp.zip

I've just redone the setup program so it may not be completely bug free. Just download the zip file, unzip the contents to a dummy directory then run the setup program. You should get two icons BinComp and BinEdit in your startup directory under Ford Binary Applications unless you change the path during setup. Here's a few notes on it:

1) It only works reliably for CBAZA strategies. There is an A9L definition file, but I spent absolutely no time verifying it. If someone wants to check it out, feel free.

2) I haven't included the ISC Transfer Function table in the definition file yet. I'll update it and post the update when it's done. There are a few additions that are not available with TwEECer like Adaptive update rate, Time to CL and maybe one more that Rick found that I can't remember.

3) There are a couple of bugs in the program. For example, I added a feature to add tuning notes for individual bin files. I've noticed that sometimes they mysteriously dissapear.

4) Documentation is poor. These programs were done as a means to compare and edit binary files for my own personal use. I'll share them but I can't promise a lot of support due to time constraints. Do give me feedback so that I can at least make it useable to the general public.

Good luck.

[Daren Woodall]

2) I haven't included the ISC Transfer Function table in the definition file yet. I'll update it and post the update when it's done. There are a few additions that are not available with TwEECer like Adaptive update rate, Time to CL and maybe one more that Rick found that I can't remember.

When you guys find new tables/functions/etc, what do I edit to expose them in CalEdit? Are you guy making a file I can included in my install?

Daren

[Dale McPeters]

Alex Smith (anybody know who he is?)

Yep, he is a memeber here but he does not post much anymore. He is known as stangage70 from what I remember. He is also a member of the Yahoo EEC-Tuner/TwEECer list if again I remember correctly.

I used to have his email address until the big computer crash from a now known hacker......

[95BlackTan50]

When you guys find new tables/functions/etc, what do I edit to expose them in CalEdit? Are you guy making a file I can included in my install?

What you need to do is edit the binary in a true binary editor that has a definition file that includes the "new" functions/scalars/tables. The editor at the link above is what we have been using to add these variables.

Once you have edited your binary file, load it into CalEdit and write to the TwEECer.

I've sent Mike information concerning my first "new" find but haven't heard anything back from him. I don't know if he plan to add these variables to CalEdit or not. For the time being you need to make the tuning changes outside of CalEdit.

[rockin_rick]

Alex Smith (anybody know who he is?)

Yep, he is a memeber here but he does not post much anymore. He is known as stangage70 from what I remember. He is also a member of the Yahoo EEC-Tuner/TwEECer list if again I remember correctly.

I used to have his email address until the big computer crash from a now known hacker......

Thanks, Dale. I have PM'ed him (stangage was the closest U/N) and we'll see what happens...

Rick

[rockin_rick]

Rick,

I haven't tried any changes yet but I did go back to some old datalogs to check on something that I could never quite figure out. When I was setting up my ISC_Drive_Idle_Air for my AODE, I could never get the ISCDC to be above 0.8125 even though I set the Idle Air to 3ppm at 1500 RPM. According to the stock ISCTF, a value of 3ppm will set the ISCDC to 0.8115. Pretty close in my book.

[as Peter Griffin] Frickin' sweet

2) I haven't included the ISC Transfer Function table in the definition file yet. I'll update it and post the update when it's done. There are a few additions that are not available with TwEECer like Adaptive update rate, Time to CL and maybe one more that Rick found that I can't remember.

That other one was Fuel Shutoff Deceleration min MPH hysteresis.... not that critical, but Barney found it, and it was easy to test out.


I now use only Barney's binary editor to edit my calibrations. When I'm ready to send it to the tweecer, I load caledit, and then load the binary. Works great.

Also, with his editor, you need to use an arrow key to move off of a cell after entering a new value for it to 'take'. You can't enter a new value, then use the mouse to point to another cell...

Rick

[stangage]

The FN8000, FN060 and FN061 locations suggested here are correct...

FN8000 type=table address=e994 rows=6 cols=10 size=1 unsigned BP=8
FN060 type=function address=e802 rows=8 xsize=2 xbp=15 unsigned ysize=2 ybp=8 unsigned
FN061 type=function address=e822 rows=10 xsize=2 xbp=12 unsigned ysize=2 ybp=8 unsigned

[Dale McPeters]

Thanks Stangage, for the confirmation.

[rockin_rick]

I had a request for some of this info, so I've attached the original pics that inadvertently gotten broken over time. I've been out of tuning for several years and have forgotten a lot so I don't know for sure if this is accurate or what, but FWIW these were the pics that I posted...

Rereading my original post I see that then I believed that J4J1 and ZA0 were the same (as the pics show), and that W4H0 and U4P0 were the same as T4M0.

Rick