2E tach ?

[supercoop]

hey guys need some advice

ran a log on a 94 cutlass 3.4l. idling in driveway

an noticed the tach is reading 4800 rpm at idle.

using the 2E.adx an 2E_tpv5.XDF on tunerpro rt v5

whats causing this?

Rob

[EagleMark]

Could be a lot of things like the adx conversion is wrong. How are all other readings?

I find it hard to find correct adx for a lot of cars like that and those years. You positive it is correct mask id?

[EagleMark]

Seems like there are 2 Engine Speeds in that adx file. Engine Speed (back up) seems correct? Maybe there were 2 different ignition systems covered by this mask?

Also Error set on P1640 QDMA may be for different engine?

Your BLM learn is blinking on and off and DFCO says enabled at what looks like idle and your rich!

Robert made that file but he's on intermittent Internet connection so I can try and help. give me year make model engine etc... so I can find ALDL file to match it up. It does not look like there was a TPV5 ADX file available and I imported a 2e.ads file.

Is connection good? No glitches?

[supercoop]

hello EagleMark,
no im not positive . the files came from this link. here

(http://www.gearhead-efi.com/Fuel-Injection/showthread.php?388-16196401-PCM-Information-2E&highlight=16196401)http://www.gearhead-efi.com/Fuel-Injection/showthread.php?388-16196401-PCM-Information-2E&highlight=16196401
o
(http://www.gearhead-efi.com/Fuel-Injection/showthread.php?388-16196401-PCM-Information-2E&highlight=16196401)reviewing the log other readings look normal, except the
IAT sensor is reading low -37 deg

[supercoop]

yes it is a 1994 oldsmobile cutlass supreme with a 3.4l automatic trans

the connection looks stable

[supercoop]

ive had an intermitten ses light , that i thought was an egr related..
which is why i wanted to connect to see whats causing the ses

the only error i see is the p01640 which i guess is
throwing the ses

[EagleMark]

Yeah you need to look into that for sure. Never know what an error code will do, some just show error and others change way ECM/PCM works?

I will look at the adx file for you.

[supercoop]

10/4 thankyou sir

[EagleMark]

So which of these describes your car? Only others I can find for 3.4L are for F body...

DATA STREAM A264
ENGINE USAGE:
3.4L SFI (LQ1) (VIN = X) 1994 1,2,3W
* 3.4L SFI (LQ1) (VIN = X) 1995 1,2,3W

or


DATA STREAM A186 PCM 16149396 $DF
ENGINE USAGE:
3.4L PFI (LQ1) (VIN=X) 92 W-CAR
3.4L PFI (LQ1) (VIN=X) 93 W-CAR
3.1L PFI (LH0) (VIN=T) 93 1W,2W,3W,4W -CAR
3.1L PFI (LH0) (VIN=T) 94 1W

or


DATA STREAM A215
ECM USAGE:
CAR LINE:
3.4L SFI (L32) (VIN = S) 93 1,2F ALL

[historystamp]

If you take a look at you car's vin number, digit # 8 starting on the left of the number. Digit 8 will correspond to the one digit vin number in EagleMark's post.

See article
http://www.gearhead-efi.com/Fuel-Injection/showthread.php?520-Car-VIN-Demystified

Robert

[supercoop]

the first one, 8th dig X car has 16196401 ecm

[EagleMark]

Your error code is stored so clear codes and see if it comes back.

This is a very complicated ADX file. It has data 1 and Extra data 2.

Does it connect OK like it is and record data without glitches? Data looked OK. But ALDL file says it needs a Mode 8, disable communications, then ask for data, it is there but not used. Some cars need this because they have extra modules on ALDL line, some don't.

The DFCO Enabled is because it is same address as something else in data 1. It only works in data 2 so ignore it for now.

Same with BLM learn only works data 2 but same address as something in data 1

I fixed a few things like EGR 1 was wrong. I renamed a few things. I added dashboards but you will have to right click and choose what you want in each spot.

I added monitors to watch data. They have a few things in them, right click and choose what you want.

I don't remember fixing IAT, but I must have because it was not low! It was getting higher as the car idled for 5 minutes to over 115f and I don't think it's that hot anywhere in the country right now. This will happen at idle though like you were doing. So go drive it and data log next time.

I made 2 item lists, one for all engine data and one for error codes.

Your car had AC engaged the whole time but only saw one fan on? Was hot the whole time from like 200 and got up to 224 f at one point this may be why it's running rich. Take it for a drive and record data again.

A few things I was not sure about the conversion on the value but they seem to be OK? They are maked *******

Here's the updated file, you now owe us 2 1/2 hours of helping others! :thumbsup: I'm going to bed...

[supercoop]

wow better than xmas, thanks !

yes i noticed the ac engaged also but thought the climate control was off.
ill take if for a drive an post another log.

Rob

[supercoop]

EagleMark to answer your question about connection.

im using a dell laptop running vista i have a parallax 28031 usb to serial adaptor
an a diy 2 transistor circuit connected to the A , M, on the 12 pin aldl plug.
with 12v connected from cig lighter

then press the acquire data icon to connect.
the connection isnt perfect but im able to move wiring around an start stop connection an restart
tunerpro to get a fairly steady connection. with no errors judging from log.

well this morning i disconnected the battery to clear code .
an tried to connect with the new adx but it was to glitchy with errors
flashing back an forth red blue with pulsing data.

so i loaded the 2E adx back in an was able to get a steady connecton
an took it for a 20min ride . i put it in gear around the 4 min mark.
Rob

[supercoop]

reviewing the log with the V1 adx , at the 13 min mark i ran the ac for couple minutes.an theres a change to ac requested

[EagleMark]

I didn't change anything in connection in the newer adx... so it could have worked the same as old by disconnecting and re connecting. Or open editior and in connection insert Mode 8 disable comunications macro, leave monitor the same. If you want to test I can make a few changes which most old ads files imported need to get rid of glitch?

So the AC status is working right?

I'll look over log later and see what's going on. Maybe add a few things to your adx file...

[EagleMark]

You got a few glitches in there, not bad though, unless it's a loose wire you were talking about in your cable?

Running way cooler, seems to run good...

Nice XDF Robert made for that!!!

Your error came back towards the end...

[supercoop]

that helped :thumbsup: i inserted the mode 8 an was able to connect with the v1 adx. after several attempts of starting an stopping ,I was able to get an error free connection. as for the ac comp , i noticed when i turned the ac on the ac clutch ( engaged) went blank ,an the ac line above showed ac (requested)so that appears to be working. im going to spend some time trying to resolve the trouble code ,could be issue with purge sol ,or tcc circuit or bad quad driver pcm needs to be replaced.the pwm tcc apply seems gittery an shutters on lockup at times this could be where the problem is.
awesome work thanks

[EagleMark]

That's not right. Should hook up first shot. I made a few more, all the same just connection differences. Try v1.1 and if does not connect, dis connect and try again, if fail, turn off car, load V1.2 and rinse repeat till you go through all of them.

[EagleMark]

Forgot one... pulled every trick in the book... wish there was a book...

[supercoop]

ok an update v1, v1.1 ,v1.2 all 3 had pulsing data i could not get a stable connection with freq fluxuating from 1 to 5hzsimilar to this logv1.3,v1.4,v1.5 i was able to get a stable connection with all 3. to be honest i can not tell a differance in the 3. with freq in range between 6 to 8 hz.starting and stopping the connection 1 in 5 times would cause the freq to fluxuate between 1 to 8 hzfor referance what is the differance in each ver ?ill continue to experiment an see which works the best. :homer:

[EagleMark]

That's great feeback and let's me learn. When I find time later I will look at those three you say worked. I am really interested if you find V1.5 better. Remeber to turn of car for a minute, restart and try first shot!

Robert wrote such a good XDF for that mask it needs a good ADX to go along with it.

[supercoop]

10-4rr ,ill do some more experiments with it. following that procedure.

unfortunately i have to set this aside till the 23rd , work calls :rolleye:

ill get back with you in a few days .. Rob thanks again

[RobertISaar]

my XDF was based off of Darren Freed's disassembly of a BSBH file. i added in a few things i found, but largely the MAF masks confuse me.

there's at least a few reasons why 2E can act funny with datastream errors, especially if you have other modules in the car that communicate on the ALDL pin M circuit. HVAC/DIC/DIS/IPC/EBCM...

[EagleMark]

Glad your back! :happy:

I'll have to see what modules could be on this car in ALDL file, maybe supercoop knows? Like ABS air bags ?

[RobertISaar]

a 94 CS 3.4 has the option for automatic climate control, ABS and POSSIBLY airbags? i know for certain the 95 models had them.

however, there are quite a few options from other year cutties you could swap in that also communicate on the ALDL circuit, namely the digital UB3 dash and the DIC/DIS module.

[EagleMark]

Well we'll see how his testing goes, he's getting good data now without a glitch, I'm just hoping one connects first shot each time.

[RobertISaar]

in all of my personal testing, with a good cable, the only time i would get glitches like that was when the monitor or connect command needed modification, or in the rare instance of me trying to connect to the PCM before switching the ignition over to power the PCM. then i got garbled data until i disconnected and reconnected.

worth mentioning IMO, especially if you try connecting almost immediately after switching the ignition over to "Run".

[supercoop]

hello Robert, EagleMark , this is 94 ragtop that has the automatic climate control ,abs,and driverside airbag.
but the dash has analog gauges.. an im not sure about the dic/dis module.

as for the connection i have been hooking everything up first .then starting engine . then starting connection .

[supercoop]

was able do some connection testing
loaded adx started car an then connect .turn car off waited 1 min
then connect.did this 3 times on each version.


v3
1st try. stable 6.71- 8.22 hz
2nd stable 6.77- 8.22 hz
3rd stable 6.76- 8.22 hz


v4
1st try pulsing data 1.64-8.22hz
2nd pulsing data 1.64- 3.29 -6.57 hz
3rd stable 6.71-8.22 hz error count 1


v5
1st try stable 6.71-8.22 hz error count 1
2nd stable 6.69-8.22 hz
3rd pulsing data 1.64-3.29-4.93-6.58


conclusion v3 had a stable connection on all 3 trys.
but v5 seemed to stay steady at 8.22 hz an drop to 6.71 hz every 10 sec
where v3 seemed to fluxuate 6.71 -8.22 every few secs

[EagleMark]

The fluctuations are OK. I'll take a look at what the differeces are later when I have time. But looks like your set with V1.3?

Thanks for the feedback. Everytime I get a good tester I learn a little more to make more files! :thumbsup: