96 replies to this topic

[StentS]

Well the general manager at the dealer just called. He wants me to bring it back in and leave it overnight again so he can drive it himself. What a crock of shit this is getting to be. I think maybe I will just have arrington build me a motor and change out the pcm and screw the warranty. Hell, obviously there is no warranty anyway. Bought it December 8th. It has been in the shop for 11 days now WTF..............
Vince

[StevoHemi]

Man... you are going through hell. I would have run out of patience by now.

Deliver the car in the morning with a couple of LEMON signs taped to the front, side and rear windows.

I hope it all works out for you mate.

Stevo

[HemiSam]

I'd pay for a lawyer to write a letter. Won't cost much and it usually acts as a social lubricant....

HemiSam

[skialfs]

yea and I suppose the "General Manager" is a chief mechanic and he'll be able to determine the problem...what a crock. I would be behind bars already.

[Speedy]

I'd be standing in front of that dealership with a big yellow sign with a lemon on it that said "this dealer sold me a lemon"

[rdrdr90]

lawyer up. they are daring you to. call their bluff.

[StentS]

LMFFAO.... Chrysler just called me for a customer satisfaction survey.... now that's some funny shit right there..... straight zeros across the board and a few choice remarks about their warranty and their ability to satisfy their customers.
Vince

[skialfs]

So I was able to data log an event similar to your "stumbling" during cold operation. Unfortunately, my datalogger seems to only log every 1.2 seconds nominally. So I'm still trying to confirm the data over three PID groups. This was in open loop as I see when I data log in closed loop the amount of sensor data grows considerably. Does anyone of you guys know what the sample rate of a Diablo Tuner is? This may be a better solution. I'm also very interested in the CT discussion you started, specifically the remarks pertaining to a garaged car and cold weather performance. Does anyone else see any merit in this possibility? Basically the computer can get confused starting up 30-40 degrees warmer then when you actually take off.

[HemiSam]

How many PID's are you recording? The data can be lumpy but I'm a bit surprised the gap is 1.2 secs. You try datalogging with the Pred hooked up to a laptop to see if you have any more joy? Unfortunately, I have not found a setting where you can adjust the granularity of the logs. The Trinity is not as granular as it could be either. Perhaps it's the output (i.e. the PCM)...dunno.

On a lighter note...






HemiSam

[skialfs]

How many PID's are you recording? The data can be lumpy but I'm a bit surprised the gap is 1.2 secs. You try datalogging with the Pred hooked up to a laptop to see if you have any more joy? Unfortunately, I have not found a setting where you can adjust the granularity of the logs. The Trinity is not as granular as it could be either. Perhaps it's the output (i.e. the PCM)...dunno.



HemiSam

Sorry, I should have reminded everyone I'm not using the Diablo,(which is why I ask about data rate). I'm using a simple Code reader with data logging capabilities.It is the Equus Innova 3130. It's a great tool but I'm sure the diablo is better. I am logging 21 PID's in open loop. The data may tell us something though as my rpm does drop when I take off, I just want to be sure it's not a normal drop when the clutch is disengaging. Here are the sensors being monitored.
time
rpm
timing advance
absolute throttle
speed
coolant temp
%long term fuel trim bank1 & 2
%short term fuel trim bank 1 & 2, (B1-S1), (B1-S2), (B2-S1), (B2-S2)
intake manifold absolute pressure (inHg)
calculated load (I would love to know what this is!!!)
Oxygen sensor outputs in voltage for B1-S1,B1-S2,B2-S1,B2-S2
intake air temp
and time since engine start

I'm not sure what is the best way to present the data, the Equus interface leaves a lot to be desired, however, I have populated an Excel sheet with the three seconds of data which covers the "event". Can we drop an Excel sheet in out post?

[skialfs]

The Trinity is not as granular as it could be either. Perhaps it's the output (i.e. the PCM)...dunno.

HemiSam

I bet there's someone here who does...all you guys are awesome.

[sharkcohen]

You could derive a nice graph from your sheet in excel and then post that.

[KeavDog]

Try the 'more reply options' attach file feature.

[Speedy]

The amount of pids recorded effect the granularity of the logs. The CAN BUS can only support so much data and it's a queue type setup where it sends one signal, then the next, next, etc. The more pids you record the worse the granularity. From memory I think it takes .4 seconds per PID on the Trinity. If you need exact on the Trinity vs. laptop I can go dig up some logs and have a look. I believe the .4 is more a limit of the can bus than the Trinity itself though.

[skialfs]

The amount of pids recorded effect the granularity of the logs. The CAN BUS can only support so much data and it's a queue type setup where it sends one signal, then the next, next, etc. The more pids you record the worse the granularity. From memory I think it takes .4 seconds per PID on the Trinity. If you need exact on the Trinity vs. laptop I can go dig up some logs and have a look. I believe the .4 is more a limit of the can bus than the Trinity itself though.

So Speedy, are you saying that each PID (Parameter-Identification-Data, if that's correct) GROUP takes 400 milliseconds? Or each sensor's response? My code reader is grabbing each group every 1.2 seconds. If the Diablo grabs each group(21 sensor inputs) in .4, then that would be 3 times the data I can record and view. That would be much better.

You could derive a nice graph from your sheet in excel and then post that.

I could, but which data to graph? There are 21 columns...better to attach the workbook and let the viewer plot.
I get your point, graphing excel data's a cinch.

Try the 'more reply options' attach file feature.

Tried that but it won't allow the excel workbook to attach.
Perhaps I'll just type out what I think is interesting and we can discuss.
I'll work on that tonight, back to work...

[Speedy]

I checked a couple of my logs. I get PID data updates in .4 seconds in my logs. I think it's a limit of the can bus, but i've never tried to log just a single pid to see if it's any faster.

[HemiSam]

That's about right, the .4 seconds. You really notice it when you're logging say a quarter mile run and you're seeing the jumps. As sexy as .4 seconds sounds compared to 1.2, it's still rather coarse once you start spending time with the logs and trying to understand say timing dropped between shifts, AFR, boost within an rpm range, shift points, etc...

vroom vroom...

HemiSam