Closing in on a problem

[ony]

did you down load the driver from tp web site for your cable?

[1great40]

After everyone went to bed last night and I could spend some quality time with TunerPRO. I believe it's configured. I just didn't feel like playing in the garage at 1 AM to try it out, But I found some stuff Mark has published links to in one of his posts and I got the $42 BIN and the other 2 definition files so now my TunerPro window has all of the files showing in the header. I couldn't find a BIN for the exact PROM I have (AKMH) But I did download one that's supposed to be for a 4.3 model years 88-91, 700R4 . I'm thinking this just might work. Right now I'm just trying to look at IAC counts. I have been told that I will need to start the data flow with the 10K resistor in place but once it starts, I can remove the resistor and see actual data at normal idle speed. I hope the guy was right.

Yes Ony, When I got the cable, it came with a CD containing the drivers. I thought I would use the drivers that came with the cable. The guy who sold me the cable claims compatibility with TP. It was't unlike the drivers I had to load when I set up the Actron Dashboard on my computer to view data from the Actron scanner that I borrowed.

Right now I think the cable/drivers are correct. Thanks for asking!

[dave w]

Congratulations! As far as I know, the 10K resistor is Not Needed for $42 data logging.

dave w

[jim_in_dorris]

No, the 10k resistor should not be used on $42 data logging.

[1great40]

Well, I finally got TP talking to my truck. It seems I had a com port problem but that's straightened out. The good news is that the IAC counts are about 10-13 in park but they barely go up at all, maybe to 15 in drive. Also the software is reporting that it's in closed loop operation, but the idle is open loop. What does that mean? Am I correct to assume that the computer cannot achieve target idle if the engine is operating in open loop idle mode? I'm going to need some help on how to log data that I can post up so minds greater than mine (almost anyone) can comment on it.

[jim_in_dorris]

Some bins are open loop idle, the go closed loop shortly after the vehicle starts moving. If the software says it's closed loop, then you are running a closed loop bin, better still. It should go closed loop when it warms up. to Data log, do this:
start your vehicle first.
1: in the Acquisition menu, choose start/stop data scan (ctrl F4)
2: to record, after starting a data scan, choose start recording from the same menu (Ctrl Alt Space)
3. to stop recording choose stop from the same menu (ctrl space)
4. name your log file
then you can upload it here to get looked at.

[1great40]

Thank you for the lesson Jim! I followed your instructions and I'm attaching my first data log!

[ony]

DO YOU HAVE THE CAPABLITY TO BURN YOUR OWN CHIPS"""?

[1great40]

Let me assure you,if I have ever burned a chip, it has been totally unintentional! No, I do not have the hardware or the expertise to program my own chips. Mark made me a chip, all i needed changed was the idle speed but it didn't work. That's what got me into TP. I thought that all it took to get the computer to control the idle was a correct minimum air setting, no pulses from the VSS and the engine to be operating in closed loop.

Right now I am using the stock PROM but I'm toying with the idea of installing Mark's modified prom and seeing what happens, since I have reset the minimum air setting. All I was originally looking for was to boost the idle speed a little

[jim_in_dorris]

1 Great40. You are WAY LEAN In dangerous territory at idle. What fuel pressure are you running? Your AFR is way out of whack. You are running almost 17.5 to 1 AFR. I am seeing rich lean cross counts, so your O2 sensor is swinging like it is supposed to. I don't know if that is an async bin, but you are in async mode at idle. Pull you plugs and check them. You may need to add fuel pressure as a first step in gettin your fuel close.

[1great40]

Thanks for finding that Jim. I will check the fuel pressure. I suppose that's why my BLM values seemed out of whack? Can you please explain async bin and and async idle mode.

[jim_in_dorris]

Asynchronous fueling is both injectors firing each DRP (Distributor Reference Pulse)

Synchronous fueling is alternating injector firing each DRP (Distributor Reference Pulse)

http://www.gearhead-efi.com/Fuel-Inj...Asynch-fueling


What bin are you using. Don't get to confused, Async fueling adjusts the injector pulse width to a smaller value, so less fuel. My truck used to go Async all the time, then I put in the correct bin and now it doesn't do that. It can make tuning difficult, most guys like to run Sync fueling. If you have a copy of the bin you are using loaded in tunerpro, the flag "Synchronous Fuel At Idle" may be unchecked. You can only change flags by burning a new chip, so we will work first with fuel pressure to get you out of the lean area. Then we can adjust the pulse width when you start burning chips. Once it is close, then you can adjust your fuel mapping then spark.

[1great40]

Thank you again! I'm really confused about the bin. Correct me, but is the bin not the file that's burned into the PROM? If that's the case, how then can I accurately read what the engine is doing if I don't have the same exact bin loaded in TP as I have in my PROM, or am I missing something?

[steveo]

the bin and what the ecm puts out for diagnostic data are seperate things.

you can check sync/async operation and other things via datalogging without having a bin at all

but it's most useful to have a copy of your working bin so you can do things like data tracing...

[jim_in_dorris]

Thanks steveo, It really is helpful, but not totally necessary until you want to start changing things. What BCC are you currently running 40?