The Central Hub for DSM Community and Information

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. This is where the DSM platform history is documented and archived. Log in to help us in our mission, and to remove most ads from the browsing experience.

First PocketLOGGER Datalog... advice??

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

95CarbonEclipse

15+ Year Contributor
1,279
5
Sep 16, 2005
Yakima, Washington
So, here she is. This log is of a 1st gear launch and continues through til the end of 3rd gear. What kind of things should I be looking for? Anything strange showing up in here? Is that 'knock' at Time: 14:05?? Any advice would be much appreciated.

Thanks
 

Attachments

You must be registered for see attachments list
Log only RPM's, timing, TPS, and front O2 sensor (O2 1). You don't need time or fuel trims.
Also, do a third gear pull; WOT in third gear from about 2500 to 7000 RPM's. No shifting, no letting up, floor it all the way. Log that and post. :thumb:
 
Really don't mean to hijack your thread, but can you please reply or PM me how you uploaded your log and what kind of PDA you used?

I have a PALM m105 and I can't figure it out.
 
GoldÐiamond;151343622 said:
Really don't mean to hijack your thread, but can you please reply or PM me how you uploaded your log and what kind of PDA you used?

Ditto.
 
So, here she is. This log is of a 1st gear launch and continues through til the end of 3rd gear. What kind of things should I be looking for? Anything strange showing up in here? Is that 'knock' at Time: 14:05?? Any advice would be much appreciated.

Thanks


Could be knock, but until you post a 3rd gear pull as suggested by turbolarry, there's not really enough to go on. We need more data points.

I'd suggest tossing out the TPS after verifying that it's good...no need to always log that value, as long as you know your foot is on the floor thereafter. Instead, I'd log airflow. That way you can get a handle on which timing map you are on, which will answer potential questions about higher RPM timing numbers. I personally get good, usable results by logging only RPM, Timing, and Airflow.
 
Yea, I just took a screen shot of the data view in PLviewer. I'm going to go out right now and log 2 - 3rd gear pulls. One with the TPS and the other with the airflow. I'll post back in a bit.
 
Okay, here's both logs: (Time and O2 Trim are logged automatically apparently). Not sure if it's a factor but, for the record, my car was up to operating temp and Intake air temp ranged from 39* - 46*

Again, thanks for taking the time to view these.
 

Attachments

You must be registered for see attachments list
Those look pretty solid...a lot like mine.

You do drop a little timing on the top end, though. Probably lean knock, but could be that you are jumping back to a higher timing map (although your posted airflow vs. rpm numbers don't suggest that). I wouldn't worry too much about that, as I would guess that you aren't seeing much time at 7K, especially given that the E3 falls off a bit above 6.5K...at least mine does (I'm usually shifting at 6500). There's a big gap b/t 6100 & 6700 in the second pull...I'm interested in knowing what's going on there, as you could be bouncing around a little (timing wise). Chances are not, though.

I see in your profile that you have an afc on your wish list...do you have it yet? If yes, and it's installed, then please post your corrections@rpm from 3K and up. This will answer the timing map question. And if it is installed, then I'd say add a little at 7K to get rid of the issue up there, unless you are already at 0% correction at the upper end of the afc and bumping into fuelcut.
 
The AFC is still on the "wishlist" :(

Would you mind explaining what exactly you're looking at so that, in the future, I can diagnose my own logs (other then what you've already posted)? I think I may need to re-adjust my byte rate because I'm only getting about 5s/s. :notgood:

Romeen... I never answered you question regarding my Palm. I'm using PocketLogger on a Palm m515 and using PLviewer v2.05e (Oct. '07)
 
Sure. And this got long...sorry.

Some people tune using all manner of variables: wideband o2, egt, timing, knock, etc. I have no means of reading knock (stock 2g ECU's don't show this), I don't trust my stock o2 sensor to give an accurate reading, I don't have an egt probe/gauge....so I use the timing values. They are a fairly reliable place to look to with respect to what's going on with your motor as you increase power.

What you want to see is your timing curve rising in a steady manner. As your turbo comes on, building boost, your timing will drop in an attempt to hold off knock (looks like you hit full boost at about 3500rpm w/ 4*timing). The ECU will slowly add timing back in as your boost rises. This rising value is what you want to watch. If the timing curve is smooth, no dips or peaks, then you are generally in a safe place. The timing can drop and jump back up any number of times during a WOT run, indicating a number of places that a correction needs to be made. The only corrections you can make at this point are less boost and higher octane (see below).

Timing can get pulled back for a number of reasons, but the most common is knock. I'll assume you know what knock is, why it's bad, etc. You can knock from being too lean and too rich, but it's generally from a lean condition. Using a piggyback (afc) or a true tuning tool (dsmlink) will allow you to change airflow and fuel input values, and modify the amount of fuel injected. Which will allow you to help to control knock (one of many ways). Since you have no way of doing this, then your two tools are: boost and octane.

I "tuned" with boost for a while, and basically what you are doing is looking for the highest boost you can run before you begin to knock, and subsequently see a timing drop. The other way you can "tune" is to increase the octane rating of the fuel you are using. This allows you to run a higher amount of boost without knocking. But what that really leads you to is another opportunity to increase boost pressure :)

So, if you are inclined, turn up your boost another psi and see if you get a dip in timing somewhere in the curve. And then perhaps again, until you see a dip. Then back it off to the a point just below where you started to knock. DO THIS AT YOUR OWN RISK! As always, raising boost pressure can lead to any number of things going wrong, from blowing off a coupler, to melting your motor. But, I have never had a problem by using merely the timing numbers as a tuning tool.
 
WOW... thanks for taking the time to type that out. One more question though... what is the importance of the air flow numbers?? Also, I'm assuming it's not an issue or else you would have mentioned it, but shouldn't my TPS be reading closer to 100 at WOT??
 
The airflow and rpm values, when inserted in a handy formula, give you a way to look at calculated airflow as the ECU sees it, expressed as grams/revolution. There are a couple of timing maps (I'll have to find the charts to give you an accurate answer) built into the ECU that relate airflow to timing. When you are flowing more than 2.1 gm/rev, then the ECU puts you onto the highest map, capping the timing at 16* advance on 2g's. The reason I mentioned earlier that there was a "potential question" regarding upper timing was that, at least on my car, as I get into higher rpm's, my turbo can't consistently keep me on the upper map. I go on and off of it, leading my timing to alternately be capped at 16*, rise higher as I fall off the upper map, then drop back down to 16* as I revert back. It can be confusing to try to figure out why you are seeing timing "pulled" at upper rpm's, thinking it's knock, etc., only to figure out that it's the whole map-hopping issue.

As for the TPS signal, I'd say if it's consistently 95% or better, I wouldn't worry about it. You might need a slight adjustment to the throttle cable to get it back to 100%, or it could be a fault with the TPS itself, not registering 100% when you are actually there.

I'll reply tomorrow with the gm/rev equation, and any info I can find on the timing maps.
 
Hi,

Some awesome info in this thread. This document that I attached is more for DSMLink but it is real good at explaining the fuel maps and timing maps. It includes the formula to find gram/rev as well.

Also, Im not taking creadit for this document, just passing it on. Found it on these boards but forget exactly where.

Bill
 

Attachments

You must be registered for see attachments list
^^^ That's what I was going to dig up this morning. Thanks for posting it Bill. Also important is the short list of variables listed at the end of the document that can change timing...more input to consider...yeah!!!

Here's a link to a thread that I've found to be really helpful regarding airflow (thanks to spyder007turbo and his great explanation of things). There is also a much more user-friendly formula for calculating gm/rev in that thread than in the DSMLink paper above. Start at post #51.
http://www.dsmtuners.com/forums/tun...61-tuning-stupid-question-2.html#post50337401
 
WOW this is a great thread full of info. Thank you to everyone.

That DSMlink tuning .pdf is exactly the type of literature that I'm looking for in order to educate myself on tweaking my car's performance and how the ECU itself works. With a little more reading I should have a pretty good understanding of how timing maps and fuel maps effect the overall performance.

God, I wish I had DSMlink. :)
 
Just a few questions guys,

I am going to post 2 logs of my car as an example. Please tell me what you think of these then I want to ask my other question.

first 2 logs are of my car. current mods are in profile. I am still new at useing the pocketlogger so go easy.
air intake temp was around 68* and coolant temp was around 195* boost is supposed to be 15, but was spikeing as high as 21.

-Dan
 

Attachments

You must be registered for see attachments list
Hi,

First for the log on the left:
The timing dips down at 3625 RPM, which should correspond with the turbo spooling. The timing should then steadly increase to max rpm. In your log it kind of stutters around till like 5215 RPM. This most likely is a sign of knock so try to add fuel in at these rpms. The O2's look fine (as fine as they can fo a narrowband, haha). A minor thing is that your tps should be at 100 percent at WOT, so maybe make sure that your throtle plate is opening all the way when the throtle pedal is floored.

The log on the right:
This log looks good except for the fact that the timing dips down at 4672 RPM.

Try to fix some of the timing issues and then post another log. Hope that helped.

Bill
 
Is it possible that the timing flutter and drop has to do with my boost spiking? as of right now the boost is handled by the stock BCS but I have a MBC and a profec 2 that I can use to take more control of it with.
And it was pointed out earlier in this thread that as long as the TPS value was consistantly greater than 95% it would be fine. I have checked my cable though. it is at max. that is the closest that I could get the tps to perfect.

-Dan
 
Is it possible that the timing flutter and drop has to do with my boost spiking? as of right now the boost is handled by the stock BCS but I have a MBC and a profec 2 that I can use to take more control of it with.
And it was pointed out earlier in this thread that as long as the TPS value was consistantly greater than 95% it would be fine. I have checked my cable though. it is at max. that is the closest that I could get the tps to perfect.

-Dan

Hi,

I am not sure of the relationship between timing flutter and boost spiking. I would install the MBC, and see if that helps with the boost spike.

Thanks for pointing out the thing about the TPS.:thumb:

Bill
 
Dan, you might want to try and bump up your data transfer rate on the logger, since you seem to have a lower than normal number of data points. How many samples / second are you seeing on the logger. Also, keep in mind that every parameter you add, cuts into the total number of data points. For example, if you are logging 4 parameters and getting 4 samples/second, you are only going to have one data point for each parameter once every second. However, if you then start logging 2 parameters with the same transfer rate, you are going to get 2 data points for each parameter every second.

As quick as the ECU changes things during a pull, the more the better.

It looks like you guys have a good thread going on here. Keep up the good work. :thumb:
 
Nathan-

Not that I'm an expert in the byte timeing but with the auto testing for byte transfer the max I get is 7 - 8 samples per second. I have tried tweeking the rates and I just get errors. Any tips?
This is frustrating because the pocketlogger site says 99 GSX should sample at 18-19 SPS.

-Dan
 
Add Value - Be Respectful - No Trolling - No Misinformation - Participate Often!
Support Vendors who Support the DSM Community

Build Thread Updates

Latest Classifieds

Back
Top