Yes

 

The Tech 2 datalogging is pretty much useless. It only logs for a very short time. I don't know why they added it. Not only that but it is a bitch to extract to pc.

 

Yeah I couldn't even find in the documentation anything about it's recording capability, just steps to do it. Thanks for writing that software it looks pretty great, I'll be using it tomorrow.

Anyway I double checked the injectors I have installed because I remember the fuel rating was very hard to find and the website I found it on wasn't very reassuring. Well turns out the info I had was wrong and I have 8 injectors meant for a V6 dodge 3.3L that makes 151hp in a 1993 Dodge Intrepid. I just spent 45 minutes and cannot find the flow rating for that engine or even for replacement injectors for that engine. Given that I have almost if not all power at WOT I'd assume they have to be pretty close to stock. I'll be getting my hands on a surefire 24# set to test on Tuesday.

 

I'm having some trouble with GDScan. I've got some version of NET framework newer than 4 installed so it won't let me install 4 but I'd assume the newer version is good, and I got the connector set on MS (mine has another HS setting for other cars) but when I click connect I get the loading symbol and nothing else, and the program is unresponsive. I know there's some connection because if I try to connect on the wrong baud rate it will tell me it cant communicate with the device. I'm on the latest version of windows 10. That's with the car on ignition. I can use HPTuners just fine but this software won't load. Also the proper software is the one in the GDScan zip right? There's almost dozens of executable throughout the files.

I put proper injectors in and the car doesn't run rich at idle anymore, seems normal, fuel trims read about -7- to -10% at idle. I wiggled my IAC wires and the car started surging 600-900 rpms slowly. After I turned it off then back on it stopped surging but still misfires a little bit. The misfires are way less than before and it will still backfire occasionally when I rev it up but nothing like before. I'm going to drive it and try to get more codes, I got P1371 which indicates a bad opti considering it's not the wires because I have a brand new opti harness I ran. This is my 3rd autozone opti. If I have to buy another opti that has a decent change of being good like a reman or from someone who tests them with scopes, I might be in this car more than it's market value.

To see how far I've come, when I bought this car and it had a bad head gasket, egr valve, vacuum lines, icm, weak ignition coil, harness to the CPS, both window motors, cat, exhaust leak because of no gasket, opti, defroster / hvac control unit, tranny mount, high pressure power steering line, radiator cap, A/C, peeling clear coat all around, long gone worn shocks, and more I'm probably forgetting. Everything that isn't the powertrain still needs to be fixed. Obviously if I knew all of this would be broken I would have scrapped the car but you can't really tell for sure some parts are bad until you eliminate the others you know are bad. Or at least that's what the mechanics helping me back then told me.

 

First make sure you have extracted all files from the zip file. Don't try to run the program from inside it.

Framework 4.8 should be fine.

What cable are you using? What function is the switch? For a regullar cable use 115k baud but for a cheap Chinese cable use 38k baud.

Run the gm-enhanced program.

Enable the display in the Console tab and try to connect. Save the file that is produced and post it here.

 

Looking at the HP Tuners data doesn't provide much info, other than at idle, the PCM is adding 24% (end of log) to 37% (beginning of log/closed loop) extra fuel. The MAF readings look low. I converted them to grams/second, because that is what I am more familiar with using in the analysis. At idle/800 RPM it's showing 5.6-5.8 grams/sec, and that is on the low side. Not an impossible reading, but at the low end of the range that the data seems to fall in of 6 to 10 grams per second. Air bypassing the MAF sensor, or faulty MAF sensor calibration. Have you ever cleaned the MAF?

The other odd thing is that the MAP is constant while idling. Is just stays parked at 28.00 kPa (again, converted to units that I work with). It is more normal for the MAP reading to constantly move over a range of +/- 1 or 2 kPa at idle.

The log becomes useless when driving, because it doesn't include the "Cell" number for the long term (LTFT) and short term (STFT) fuel trims. There are 18 cells, and each cell will have its own correction for both sides. And revving the engine while parked is not useful. The fuel trims are tied to RPM and MAP. MAP is used as an indication of engine load. There is no load on the engine when you are just playing with the throttle. The resulting combinations of RPM and MAP do not replicate normal engine operating conditions.

Gary's program will be much more useful. .

 

There is something I forgot to ask. Are you using a special cable for the HP Tuners? Not being familiar with that, I assumed it was an ELM327, but I think it is not and can only be used with HP Tuners. The ELM327 cables can be bought for about $30 online. It's much better to get one with a real FTDI chip inside rather than the cheaper Chinese knockoffs. Also many of the knockoffs do not have the parts installed for your car. Avoid the ones with the blue and orange labels especially.

 

For HPTuners I used their adapter. I do have one of those cheap orange and blue adapters
Here's a screenshot of the console log. I can't save the log as text because the program is frozen after I click connect. https://drive.google.com/open?id=1oH...Q0NiHYP46NK_VT

 

The console screen actually helps I think. It does work when the program resets the cable and sets some options ("OK")

In case you are doing this differently, use the Connect button on the far left, not in the Console tab. Don't click on anything inside the console tab box except the one to enable the display and possibly the one to save to file. Those are advanced use controls only.

The cable is responding but I am not sure it is working and I have doubts. One of the big problems with those cables is that there were missing parts that connect the signal to the car for GM vehicles. They may be simply missing. If you take the box on the cable apart and look at the circuit board, there should not be a lot of missing parts (one or two maybe but not more). By the way, the 4 screws holding the two halves of the box together are under the label at the corners.

 

Yeah I think that issue with the cable is the problem. I'm following the steps correct and clicking the correct connect button too. I just ordered the $30 red cable you linked and I'm gonna return this one. I can't check if it's missing the parts because 3/4 screws came pre stripped and if I drill it I can't return it lol.

 

I've got a new autozone MAF, never cleaned it but it's under 500 miles. I'll get the working cable to datalog Friday with Gary's software and in the meantime I'm gonna drive around and see if I can find anything else going on. I'll look at the map too, it does seem a little odd that there is almost no fluctuation.

 

I tried to duplicate the data that you saw in the screenshot and was not successful. Something is behaving strangely. The program is supposed to be sending the data request for each supported piece of data for your car but is instead repeating the previous setup request for the cable even though the previous setup request was returned with an "OK". I don;t know how that can happen. I even updated my .Net Framework to the latest, ver 4.8, and there were no changes in operation. It may be best to download the program again and unzip the files again.
Another possibility is that HPTuners has rendered the pcm unable to make communications via standard OBD2 scanners as part of the installation. But I have no experience with that.

 

Thanks Gary, when I get the new cable Friday I'll give it all another go. I can't actually do anything but log the most basic data like a cheap scanner with HPTuners because it's not for these cars, so I doubt it messed with the pcm like that, although HPTuners softtware messing with the computers communication with obd2 interfaces is a possibility I suppose.

Sometimes when I'm driving the car cuts all engine power, mostly when I'm driving at 1/3+ throttle. It only happens maybe once or twice on an hour drive. I also received the low resolution too few pulses code. Obviously it appears the cheap autozone opti #3 could be failing. My failed ICM may actually have been the opti failing, and it seems compiling that with the issues starting, this is what's left. Since GaryDougs program, as amazing as it is for free, still can't see the low resolution signal because of the way the PCM reports the data, I think I'm gonna build a small oscilloscope and record the signal while it's running, just to see if I can actually watch the signal fail to be sure. And partially for fun.
It already runs much better with what we've figured out so far. Your guys help is invaluable, thank you so much! We're getting closer!

 

Here are a couple of suggestions for a cheap Chinese-made tiny o-scope. The first one was purchased as shown for about $50 in 2015. The 2nd and 3rd photos is for a kit for $14 in 2016. The first one is shown displaying the low-res Opti pulses. The second is showing it's own test signal. They only display one trace.

 

Thanks for the info I like the kit. I'll figure something out soon.