Guys,

I've been datalogging with the Datalogit and noticed a few issues about the PFC N and P map references. When I compare the N (PFC rpm, map columns) and P (PFC boost, map rows) to the datalogged rpms and PIM values they do not agree with the PFC maps. The boost levels are off by over 1000 and the rpms are off by 200-400 rpm. Weird, may be some electronic delays or the datalogged map reference data is off due to interpolation between cells? Anyone know?

I also noted a difference in the basic and advanced knock readings, anybody else?

Last item, the FCEdit software will lose connection with the PFC about every 20 minutes. Most times, I just click OK and then restart the datalogging but once I had to kill the engine and then restart for the program to recognize the PFC.

Otherwise, it is such a relief to see streams of wideband O2 data along with knock, injector duties, etc, etc. Starting off with rich AFRs of 10.5 and very low knock levels, time to play with fuel, then timing. I hope it holds together this time around.

Kyle

 

I was helping Kyle yesterday with his logging. He failed to mentioned one another problem with the DATALOGIT.

The monitor screen will not display ACTIVE data unless the log function is STARTED. Is this normal???

 

That's been my experience as well, however I haven't compared knock levels or map positions. Evidently, the dataloging streams are a feature of the PFC, not a Datalogit creation, so the problem my be inherent to the PFC. Probably should ask Glen/Steve to be sure. I haven't had a problem with connection dropping.

Alan

 

Kyle.
Did you send your comments to Glen??
Are you using a wideband??
John

 

I'm waiting to collect more lap time with the datalogit before communicating with Glen.

Yep, using a UEGO wideband with sensor in the DP.

Kyle

 

Heard back from Glen ...

They experience the same inconsistency in the rpm and PIM when datalogging, no real recommendations though. They warn of the delay in the datalogged stream of the various sensors, the data is taken sequentially so each line of log is taken one data/value at a time ... there is a delay between each value listed even on the same row of data. No surprise, just confirmation. This explains why the basic and advanced data for knock is different even on the same line of the log.

They are working on a fix to prevent the Datalogit from losing signal from the PFC.

Next version will activate the monitor screen (show live values) without having to start a datalog.

They are working to save the Watch Box settings so you don't have to redo them each time.

In response to the slow intake air temp sensor response there is no recommendation, but you can set all the correction values to a constant and tune around it. I may move the sensor to the intake piping to attempt to read intake air temp instead of manifold temp, until then I'm going to rethink the correction values. A percent under full load is typically less than 0.1 AFR anyway, but an 0.7 change in AFR can be scary.

Kyle

 

I got my datalogit last night, and I am really happy with it. Those guys made a really great product (hardware and software) and made it available for a very good price. I've done a little data logging and general fiddling with it, and it is damn cool. This is a kick-*** product in every regard.

I can't wait to get a wide-band hooked up and do some tuning. Now if only my laptop battery would last for more than 30 minutes...

-Max

 

max get a power inverter....problem solved for that laptop

 

or rig your laptop to plug right into your cig lighter. laptops have no problem running on 12-14 volts. they have built in voltage regulators to smoothe things out. mine even charges the battery when hooked up that way

 

This is why I requested that we can choose items we want datalogged individually. I really don't want to clutter the stream of info coming from the FC with useless info. I don't thin Glen will be doing this unless more people request it.
John

 

The individual items really need to be seperate otherwise you get more data than you really wanted. I noticed more differences in the P map than the N map myself. It seem consistant at like 1000 offset.

 

Kyle,

About the intake temp sensor, I've wondered about moving it too. I wonder if putting it in the IC outlet pipe or IC end tank would make the temps change faster, or if it is a function of the sensor itself being very slow to react?

If anyone tries moving it, please let me know what you find.

Wade

 

I'm going to move mine in the next couple of weeks. I'm going to put in the air temp sensor that Haltech guys use (supposed it should work) so I'll let you know as I do A/B comparisions.

 

Carson, where are you going to install the other sensor? In the elbow? I've been wanted to place on in the elbow to compare with stock but havent had the time. I've always thought that the sensor just gets heat soaked.

You think its possible that the uim gets so hot that it could heat the air as its going thru? I would imagine its going thru to fast to heat up that much but maybe its possible. The uim does get vary heat soaked.

Later,
STEPHEN

 

I'm sure it might raise the temps a degree or two but I have no data on this. I will weld on bung to my intercooler pipe and screw in the new sensor. Then I'll just tap into the stock wiring.

 

I would say the air has insufficient time to heat up as it passes through the uim. Another datapoint about how slow the intake temp sensor reacts is the lack of any movement in the temperature reading once the water injection kicks on. My datalogs show constant intake air temp throughs pulls in gear 2-3-4 with or without water injection ... doesn't make sense.

I have an extra intake air temp sensor now and I might install it in the Greddy elbow. The elbow is pretty thick and should be able to be drilled and tapped as I did for the h2o injection. If I do this I'll post in the results.

 

I moved my airtemp sensor to the oulet of my greddy FMIC aand the sensor reacts a lot faster and more accurate reading. I have the datalogit software and
had to set the airtemp correction values the same
to stabalize for a flatter reading in degC cahnge.
Also I found that by moving the temp sender up in
front by the intercooler that the heatsoak after turning
motor off and then on was a lot less.

 

Xcessive,

Why did you decide to modify your settings in the PFC to stabalize things after moving the airtemp sensor? Did you adjust the fuel correction values, ignition correction values, ...? Just curious.

 

Where did you guys get this datalogit from?

Is it on back order?

How much $?

What wide band do you have to use?