Lucid

iTrader: (4)

I am running a $6E modified ARAP bin and am not quite happy with all the little tweaks necessary to get it to run right on the iron headed 86 305 that I have.

I already did the long crank fix, copied over the spark tables and maf tables, and some other tweaks.

Comparing the BINs, I noticed that the $32 XDF is a little on the skimpy side, so I decided to take a look at the Hac.

The main problem I am having with the ARAP is getting it to idle correctly and smoothly. Comparing to the other $6E iron headed BINs has had varied results. I would just like to tinker with the settings to see if I can get results from a non roller setup. My 87 roller seems to be more tolerant of the ARAP settings.

I would like to add the Warm IAC Park Steps vs Coolant Temp Table to the XDF but I am a little foggy on how to do it. I have added a constant before but not sure about doing a whole table.

From the BUA hac:

;------------------------------------------------------
; Warm Park Posit vs Coolant Temp
;
; TABLE = STEPS
;
;
;------------------------------------------------------
ORG $0690
LC690: FCB 8 ; 9 Lines in Tbl
;------------------------------------------------------
;
; DEG c COOL
;------------------------------------------------------
FCB 145 ; -40
FCB 145 ; -16
FCB 113 ; 8
FCB 90 ; 32
FCB 80 ; 56
FCB 65 ; 80
FCB 50 ; 104
FCB 50 ; 128
FCB 50 ; 152
;------------------------------------------------------
*******************************************************

Am I seeing (FCB) values or just place holders here for the actual IAC steps?

JP86SS

iTrader: (1)

The FCBs just indicate that these are single byte values (8 bit)
The value following the FCB is thae actual value (be careful because some hacs are in decimal, hex or Steps) These are in IAC Steps

I've added the actual address to the lines so you can see how it goes in sequence from the starting point of the table.
The table values actually start at C691 (the "L" represents Line number in the code)

To start,
Open your XDF





Under XDF menu, Create new item

• Select Table
• Enter the name you wish to call the item
• Enter the starting address of the table "0691"
• Output type should be Integer because these values will be whole numbers only.
• Go to the "Rows" Tab
• Since there are 9 rows indicated by temperatures, put 9 in the box
• Unit will be "Deg C"
• Row Lable type should be floating point (If you wish to make data tracing work)
• Enter the Row values starting with the first one in the table (-40, -16..etc until done)
• Go to the "Columns" tab
• There is only 1 column since this is a 2D table.
• Units will be in "steps" because this is an IAC function
• Column lable will be Integer (again so the tracing can work)
• Go to the "Conversion Tab (although nothing will be changed here because the values are already in "Steps" of IAC movement.

Last but not least you can click the ALDL Association tab and set the data to come from the Coolant temp when Data Tracing is enabled.

I've attached the pics to help.

JP86SS

iTrader: (1)

Once all is entered you can click the item for editing.

Lucid

iTrader: (4)

JP86SS,

You are a life saver man. I did it wrong at first, I put the address thats in the hac and I got wrong values. Then I was looking through the $6E hac and I noticed that the actual starting address is the first line of the data 0691

Then I pulled the values correctly.

The stuff you posted about FCB's went over my head, I do not know how to tell the difference, but maybe if I find that source code for dummies all that will be in there?

Anyhow, I did notice that the $32 Park Steps are very different from ARAP:

Deg F ARAP LB9
306 5 45
262 5 45
219 5 45
176 10 45
133 25 60
90 50 80
46 75 95
3 100 110
-40 125 110

I copied over this to my arap bin and noticed that the off idle transitions and transitions from steady state were more responsive and smoother for my 86.

JP86SS

iTrader: (1)

The "FCB" is just what the disassembler indicates as a size.
Some use .byte or another designation.
In this case, The FCB = 8 bits, You would specify that in the item definition( 1st pic)
If this was FDB, (meaning double) that would be a 16 bit value and would need to set it that way to display properly.
There is a value at the starting address of most tables that defines how many lines there are. That's why you need to go to the first "Data" point address after that.
3D tables can have 3 values defining the table parameters so you would need to go that many addresses farther to get the the actual data to display correctly.

Lucid

iTrader: (4)

Holy crap thats complicated!

I wanted to do the crank PW multiplier vs DRP table next but I am definitely not in my element right now....

How does it run with the park steps being all the way up to 145 on your car?

JP86SS

iTrader: (1)

Aw, come on, That's an easy one
Do the same thing as above but use 37F for the starting point address.
I believe this table is already indicating full fuel during crank. Seeing how the values are already at the maximum of 255 (that is the max value for an 8 bit number), you could only lower the amount of fuel with this table.
This one will require a conversion factor. it would be 1/255 = 0.003922 (the box should read X * 0.003922)

I run SD $8D, not the MAF so I can't comment on the table except the 145 would only happen at -16 C to -40 C
(That's pretty cold even for Cleveland)

In $8D on my car having a few more steps helps to freewheel and is quicker when starting. If I keep them low it seems to be harder to crank.