70f05 auto ka24de ecu? incompatible? wrong tables? help!
Posted: Fri Oct 28, 2011 12:59 am
Anyone else here on 70f05 ecu?
I am about at my wits end trying to get my daily back on the road here. I had a bikirom (I know) and after giving up getting that to work I decided to bite the bullet and get nistune, which I love. Problem is I can not for the life of me get it to consistently run right.
I tried importing a basemap I know many people use to start with on ka-t.org,
http://www.liquidmathematics.com/tunes/ ... r-8bit.bin
Since mine was an auto I imported all his tables, uploaded, and went for a drive. Everything seemed REALLY close but after awhile went to hell. I tried taking a new 70f05 bin and manually tweaking it myself, then importing just the fuel tables and scales. Ran and drove like a champ for another half hour of street tuning. Then like the last one it seemed to go to hell. I think the ecu is trying to learn and compensate then flip out when it tries. Eventually my car tries to lean out 20:1, lose idle, and die out.
I did some datalogging and tried some tuning last night and realized something: Half of the map traces are in the wrong spot! No wonder the car wont respond appropriately and just goes sour.
Is nistune supposed to work with the 1995 single wire o2 70f05 ecu? AVP told me it should, but now I wonder if like bikirom there are other issues with auto ecu's. My solder joints are great everything appears solid, I think this is a software issue or maybe it needs a different adr for auto?
I might be idling at 1800 rpm for example and changes to the VE map are traced to the 500 rpm cell. Why idle at 1800 rpm? because my final 230 deg cell for idle target was 1800 and even though coolant temp might be 185 degrees it follows only at the final cell and utilizes that number. I have not yet REALLY spent more time finding each and every table that is referenced inappropriately, but it's happening.
After awhile I can't get my car running right and I might have to increase VE to 150 in the idle cells just to break 19:1 afr. Around there it jumps right to 12/13:1 from 19:1 as if I hit some sort of closed loop flag issue (but the o2 plugged in or not wont change it). I can also jump my latency time from 760us (proper for sr 370cc's) to 1.2ms or so to keep it idling but that feels sloppy.
Here is a screenshot of my map and log of my idling last night. Maf reading feels clean overall not choppy
thoughts? ideas? what gives! bug? just me?
I am about at my wits end trying to get my daily back on the road here. I had a bikirom (I know) and after giving up getting that to work I decided to bite the bullet and get nistune, which I love. Problem is I can not for the life of me get it to consistently run right.
I tried importing a basemap I know many people use to start with on ka-t.org,
http://www.liquidmathematics.com/tunes/ ... r-8bit.bin
Since mine was an auto I imported all his tables, uploaded, and went for a drive. Everything seemed REALLY close but after awhile went to hell. I tried taking a new 70f05 bin and manually tweaking it myself, then importing just the fuel tables and scales. Ran and drove like a champ for another half hour of street tuning. Then like the last one it seemed to go to hell. I think the ecu is trying to learn and compensate then flip out when it tries. Eventually my car tries to lean out 20:1, lose idle, and die out.
I did some datalogging and tried some tuning last night and realized something: Half of the map traces are in the wrong spot! No wonder the car wont respond appropriately and just goes sour.
Is nistune supposed to work with the 1995 single wire o2 70f05 ecu? AVP told me it should, but now I wonder if like bikirom there are other issues with auto ecu's. My solder joints are great everything appears solid, I think this is a software issue or maybe it needs a different adr for auto?
I might be idling at 1800 rpm for example and changes to the VE map are traced to the 500 rpm cell. Why idle at 1800 rpm? because my final 230 deg cell for idle target was 1800 and even though coolant temp might be 185 degrees it follows only at the final cell and utilizes that number. I have not yet REALLY spent more time finding each and every table that is referenced inappropriately, but it's happening.
After awhile I can't get my car running right and I might have to increase VE to 150 in the idle cells just to break 19:1 afr. Around there it jumps right to 12/13:1 from 19:1 as if I hit some sort of closed loop flag issue (but the o2 plugged in or not wont change it). I can also jump my latency time from 760us (proper for sr 370cc's) to 1.2ms or so to keep it idling but that feels sloppy.
Here is a screenshot of my map and log of my idling last night. Maf reading feels clean overall not choppy
thoughts? ideas? what gives! bug? just me?