454 TBI Swap 78 K30 Trouble with TunerproRT and Winaldl, etc.

[5cottymac]

I lost the paper i had written the injector #'s on, but i had previously looked up the color and verified the # to be the 94-95 7.4, lower flow rated, but higher pressure ones.

Every time I go through the process to select the xdf, it still shows at top no XDF selected. I follow the steps outlined in your tutorial I printed. The cursor over the initialize emulation is just a fluke. I was clicking the double arrow and all that changed was at the bottom: DA Not Connected to DA Connecting. I changed the com port in the tuner pro and did the test and it recognizes the cord.

[5cottymac]

What I'm doing, according to the tutorial:

Here's what your need to download, read through then below more instructions how to put them in TunerPro.

First your bin/chip/ASDU.bin

Then you need the mask (xdf) to read the bin in English, not hex, $42-1227747-V3.xdf

Then you need the file for data/scanner (adx) file for the bin/chip/ECM which is the $42-1227747-V3.adx

The data logged is saved in a file with .xdl at end and can be named anything... you do not need this but it is in the thread above so you can see what a data log looks like and play it back to see how your engine is doing and where changes need to be made. It is file named 11-27-11-3.xdl
With TunerPro downloaded and installed open it. Then...

1. CHIP: .bin extension. TunerPro, File, Open Bin. Choose your bin you downloaded and saved. Now your bin is loaded in TunerPro.
My file saved in Bins folder: BMHM.bin

2. MASK: .xdf file extension. TunerPro still open, XDF, select your xdf you downloaded and saved, now your mask is loaded in TunerPro. You can now make changes to your chip/bin file.
My file: Saved in Bin definitions folder: A219 TP5 v250 $31.xdf

3. SCANNER/Data Logger: .adx file extension. TunerPro still open, Acquisition, Load Definition file you downloaded and saved . Now your acquisition file is loaded in TunerPro. You can now record data from car. Or play back a data log if you do next step.
MY file: A219 TP5 v250 $31.adx

4. DATA LOG: .xdl file extension. TunerPro still open, Acquisition, Load Log file.

[EagleMark]

Sounds like you have all correct files. Except forget step 4, that is if you want to look at your already recorded data log. You do not need the XDF file to data log. But why won't it load in TunerPro?

In title bar, XDF then drop down, Select XDF, click on your XDF, Open and it should be there.

Data is what we want right now so: SCANNER/Data Logger: .adx file extension. TunerPro still open, Acquisition, Load Definition file you downloaded and saved . Now your acquisition file is loaded in TunerPro. You can now record data from car. Hook up cable to vehicle, start and run engine, click double arrows or Acquisition, Start/Stop Data Scan, when you see data Acquisition, Record!

You never said what your CEL is doing. If it's in LHM you may not get data as something is catastrophically wrong!

[5cottymac]

So I received new, not homebuilt aldl to usb cable, with driver software and installed everything. Cable and driver are installed as com5. After searching, I discovered the thread about that driver version to use and I am now using the .14 driver for the cable. However when I get tunerprort set up with bin file, xdf, and ADX, when I go to preferences and configure for the cable on com5, every time I check cable it gives me same message as cable not found tested at 8192 baud.

Capture1.JPG
Capture2.JPG
Capture3.JPG
Capture4.JPG

Thanks for the help guys,

Eagle Mark I will have more answers about the CEL when I get the truck out from the snow and warmed up. Trying to resolve this cable issue before I head out and try to knock out this one bird with an RPG....

again, thanks for the help.






Also, Cant figure out why I unplug the ALDL USB cable, and plug it in to any other port and it always comes up COM5, is this because the driver always recognized the cable as COM5?

As well, I used HyperTerminal program and selected COM 5 with 9600 Baud, and no signals showing on COM5 when I turn key on.

[EagleMark]

The cable test is done with cable hooked to PC and not vehicle, it will fail if hooked to vehicle.

Wondering on the cable, who made it? Red Devil River was the one who found big issues with new FTDI chips and drivers and he had 2.8.24.0 as driver. Just looked at my in car tuning laptop and still at 2.08.14 driver. This is the only one that goes into vehicles any more... All my cables and devices are years old though. The driver issues started popping up with newer FDTI chips.

Also the driver needs to be same in Com Port and USB Serial Converter!

Then once I did get a brand new ALDLCables.com cable that was faulty? There is always a possibility that a brand new cable like any other brand new part can be faulty?

I've been told it does not matter what USB port you plug into once a cable is installed... but I've found to many times that the cable needs to be used with same USB port or it fails or needs to be reinstalled? I forget but all my laptops use USB port on left side or if 2, left side rear as the cable points to dashboard when on the pass seat. I never change USB ports anymore!

I also do not change any defaults on Com port settings.

You really seem to be doing everything properly! I'd restart computer with nothing plugged into any USB ports, plug in cable to original USB port it was installed on, check Device manager for Com Port number, open TunerPro and there should only be one Com port available. If more then one port is shown in TP? Choose the one in {Com x} IIRC.

I'm out of tips? Hope that helps?

I've asked Mark M at TunerPRo why installing cables is such and issue when there's never issues with other Data Logging programs and his answer was... "Other programs only take pass through cables but TunerPro accepts pass through cables and devices like Autoprom etc...

[EagleMark]

Once you get the cable and TP happy... we still have a major malfuntion which is probably why it's running so poorly! Also the reason I asked what CEL is doing. You said:

This brings me to building an ALDL cable per instructions on several forums. Can run it on either direct serial port or Serial to usb converter. Verified cable operation by plugging it in to 89 4.3L s10 blazer, and had all functions of WINALDL and Freescan. I have downloaded tunerproRT, Winaldl, and Freescan and nothing will communicate with the 95 ECM. The goal is to further diagnose the terrible rich condition by using TunerproRT as a glorified scan tool, and decide how to fix the truck, and get it to run better.

If you can get data with other vehicle and same laptop and cable, but not this vehicle? You may not have data? Could be a wiring issue? Although Howell makes good stuff they are still human, so are you. So need to check serial data wire from ALDL port to PCM, check the serial wire is in correct location on ALDL port, check ground on ALDL port etc... if a couple wires got swapped at ALDL port... well obviously you won't get data!

Also what does Howell do for the chip nowadays? Do they use a G1 adapter? If so is it installed correctly? Look at this thread with pictures

http://www.gearhead-efi.com/Fuel-Inj...er-form-Moates

[5cottymac]

The Check Engine Light operates as follows

Key off position: obviously light off
Key run position: light flashes once and then remains on
key start, then to run: light remains on, until engine fires and runs, light goes off and remains off

Only DTC shown is 1-2 : verifying operation of "Short" in ALDL cable asking for DTC display

I have two laptops and two cables,

Laptop A: Dell with Tunerpro RT with all same .bin, .adx, and .xdf Has serial port and usb port. Loaded with all same drivers as Laptop B
Laptop B: HP with usb only ports, loaded with tunerprort, same bin,adx, and xdf files. same drivers as laptop A

Cable 1: Homeade cable with switch to allow direct "short" to retrieve DTC codes, 3.9K ohm resistor can be switched on, 10k ohm resistor can be switched on. This cable goes direct ALDL to Serial.

Cable 2: ALDL to USB cable from www.aldlcable.com Has moveable bar to change from open to 10k ohms, to direct short.


To explain in better detail.

I hooked Laptop A and cable 1 to 89 4.3 s10 blazer, and view ALDL information using FreeScan program. I was able to view dashboard as well as sensor data. Switched to direct "short" condition, and viewed DTC code for TPS voltage low, which matched sensor data and flags. This confirmed that the cable we had built was working correctly with 89 4.3 S10 blazer.

I then hooked laptop A and cable 1 to 78 K30 454, and using Freescan, and nothing happened. This is when i downloaded and installed TPRT on both laptops, and installed all corresponding bin files, adx files, and xdf files, all for $31 mask. I also ordered the cable 2 at this point.

Then I hooked cable 1 to laptop B using usb to serial adapter and TPRT failed to recognize cable, with correct drivers and COM port settings.

Next I hooked cable 2, to laptop B direct to usb, changed COM settings and TPRT failed to recognize cable.

Next I hooked cable 1 to Laptop A, direct to serial port, TUNERPRORT recognized the cable!!!. Next i hooked to 78 K30 7.4 Still using $31 mask files, still failed to connect to ECM. I then verified that cable 1 is still working with ECM, by switching to direct "short" to display DTC, and i get a code 1-2, verify operation. I then tried Freescan, Winaldl and tunerprort again, with no info from ECM.

My thoughts were then, maybe the ALDL plug was wired incorrectly from howell: But-> we had our resident tune up guy bring himself and an OBD1 scanner, early on trying to make sure all sensors were working correctly and he could view all data, and see that all sensors were working correctly. The fact that he could, and I witnessed the data on his screen, makes me think the Chip Howell did and the aldl plug they wired are both correct. He had the truck for over a month going over everything and could find nothing wrong with any sensor, or any other hardware or wiring issue.

So where we are now:

Laptop A, with cable 1, is the only way TPRT will recognize any cable, but still no data stream from ECM on 78 k30 7.4. When I click the double arrow button to connect to ECM, for 1.5 seconds, it says DA Connecting: then goes back to DA not connected.


Capture1.jpg

P.s. IIRC it is switching between open and closed loop, this info from when tune up guy had his professional scanner plugged in.

Base Timing with tan wire disconnected is set at 4 degrees. Note: when i unplugged that connector to check timing, the idle definitely got much smoother, and truck ran better. Then disconnect battery, reconnected the tan wire connector(for setting timing) and truck is back idling terrible.