Just got my pocketlogger, little help?

[ViciousVendetta]

While I did a great clean job of installing the logger permanently in the slot under my cd player, im still slowly learning how to use it. I plan on reading over digitaltunings site more soon, but do you guys have any other hints for me, like which parameters are best to log and in what order? I just got a new rebuilt longblock put in so i cant log Hi fuel trims yet of course ^^ Also is there a way to log idle fuel trims or is that what Low is? Right now Low is 139, guess I need to lean that out with my MAFT (still need to install that new main chip whch gives even finer tuning) Any other hints or websites that wuld be a good read would help me alot here, thanks!

 

[spoolup]

everyone has there own preference of what to log. I would log timing, knock, throttle pos, F O2, airflow, and the trims until you get it more dialed in. Also there are good tuning guides on fullthrottletech.com for the translator as well as a forum devoted to just those things. Pocketlogger.com has a forum as well.

PS a 139 fuel trim is ECU trying to ADD 139% fuel to get your O2 trims to a descent value. You would want to add fuel not take it away. Plus depeneding the year of your car/ ECU when a trim pegs a high or low value you typically have to reset the ECU to get it to move again. I have also seen vacuum leaks cause high LFT.

Last thing, after adjusting the fuel dont expect the number to just move. It takes quite a deal of time a 1G for that number to move. So you will have to drive it for a few hours.

 

[spyderturbo007]

Couple of hints/tricks

1. Write down your byte timing settings in case you have to reset your palm.

2. Hotsync often.

3. FT's are not used at WOT, so during a 3rd gear pull don't log them as you will only be decreasing your samples/sec.

4. During a WOT pull, log timing, rpm, knock and airflow.

5. A FT of 139% is the ECU adding 39% fuel not 139%

6. Be careful making WOT pulls. You will be reaching some high speeds and we don't want you to hurt yourself or anyone else.

Things to look into:

I have never gotten a chance to look at the GUI associated with the DSM version. I have the OBD-II version which doesn't have as many features. With that said, here are some things that make life a lot easier that will probably be included with your version.

Automated byte timing test.

Allowing the log to be started by tapping anywhere on the screen, not just that really small "go" button.

Visual alarms when a parameter reaches as user specified value. For example: Coolant temp > 210 degrees F

 

[ViciousVendetta]

Thanks for all the hints! One other little thing I was curious about... Under diagnotic, there is a screen where you can "test" things such as egr, bost solenoid, canister purge, and more. When I press the button is just flash that its testing but it gives no feedback. Is the logger supposed to work that way, or is it good that it isnt saying anything?

 

[spyderturbo007]

I can't help you with that question as I am only familiar with the OBD-II version, which doesn't have those features. I can, however, point you in the right direction

www.pocketlogger.com/forum

Post in the DSM newbie section. The mod there, who I believe is also the owner of Digital Tuning, will take care of all your questions.

Enjoy

 

[spoolup]

Both the DSM specific and ODB-II should have those funtions by now. The DSM version was the first to get the touch anywhere to start, big number ect. Then about 1.5 yrs ago pocketlogger began beta testing the new ODB-II version (I was in on the beta) about the same time full thottle started the beta of version 2.08 translator (also in on that beta). I would have thought by now pocketlogger would have released the new version of ODB-II code. looking at the forum again it appears the beta forum has closed for V2.0 and that it is actually released. So both DSM and ODB-II should have big numbers, warnings, automated byte, ect.

Also for the DSM specific testing of solenoids ect. here is a link that describes how to use them please note the ***CAR MUST NOT BE RUNNING*** when testing the solenoids/ fuel pump.
http://www.pocketlogger.com/instructions/quickstart2.html#diag

 

[spyderturbo007]

Both the DSM specific and ODB-II should have those funtions by now. The DSM version was the first to get the touch anywhere to start, big number ect. Then about 1.5 yrs ago pocketlogger began beta testing the new ODB-II version (I was in on the beta) about the same time full thottle started the beta of version 2.08 translator (also in on that beta). I would have thought by now pocketlogger would have released the new version of ODB-II code. looking at the forum again it appears the beta forum has closed for V2.0 and that it is actually released. So both DSM and ODB-II should have big numbers, warnings, automated byte, ect.

That's what I was thinking, but I didn't want to be wrong

Also for the DSM specific testing of solenoids ect. here is a link that describes how to use them please note the ***CAR MUST NOT BE RUNNING*** when testing the solenoids/ fuel pump.
http://www.pocketlogger.com/instructions/quickstart2.html#diag

I was looking for something like that and couldn't find it. Good job...you get a rep point!