Will the Pocketlogger accurately read AFRs, Timing, and Knock when used in conjunction with the Xede? I'd like to know if the Xede's adjustments to timing and fuel will be seen by the Pocketlogger because I'm thinking about getting one:

PocketLOGGER™ for OBDII
http://www.pocketlogger.com/index.php?pid=plobdii

Are any other Xede users using this?

 

I have autoengenuity pocketpc obd2 logger and only get 6 samples per sec. ...3 samples per sec used for rpm, 3 used for timing.

Zeitronix just released this for pocketlogger http://www.pocketlogger.com/index.php?pid=plzt

 

I don't think the version you provided a linked to can connect to the Xede directly, so it would be unable to read any of the wide-band AFR readings.

The ODBII version only reads stuff sent out by the factory ECU, which can only output the AFR readings from the narrow-band O2 sensor (i.e. 14.7:1 plus/minus a few tenths).

Forced induction engines - like ours - typically need much richer mixtures at high load and rpm, but the factory O2 sensor is designed for idle and part throttle performance and so only works in a very "narrow" band of AFR readings. Same with the MAP sensor, it only goes up to 1 bar. I can't believe a 2.5 bar map sensor is so much more expansive than a 1 bar sensor. Why would Mitsubishi use a 1 bar senor on a car capable of making 2.5 bar (ish)? Baffles me!

There are alternative monitoring software tools like pyXede that would might give you the info you need? Although, you will need a laptop computer.


https://www.evolutionm.net/forums/sh...ghlight=pyxede

 

Pocketloggers read from the OBD-II data port using a protocol standardized by the SAE. To get Xede values, you have to talk to the unit directly, using a protocol specified by chiptorque. It _is_ possible to get software to talk to both simultaneously. It's not even hard really. It just takes time to create such a thing.

That reminds me, I need to find the OBD-II program that works alongside pyxede. It's been in storage somewhere since I moved last summer...

d

 

Thanks for the thoughtful replies. What I was really hoping for was:
1. a logging tool that could log knock accurately.
2. a tool that would show short and long term fuel trims in order to fine tune my fuel system at idle. I've had my ecu reflashed to scale for larger injectors and I thought I could get one last rescale in order to get it perfect.
3. Accurate logging of timing
4. Accurate logging of AFRs.

 

I did not interpret him asking if it connected to the xede but wanting to use obd2 software to read timing. The sample rate of the obd2 scanners offer is useless.

I use a laptop to log boost and afr w/zietronix and commslog6 to datalog xede. I would use pyxede but do not like to click on the log boxes everytime it starts(any way around this donour?)

 

To have the desired boxes always check? Yeah, that's really easy, but I'm probably not going to worry about it until I get time to fix it the right way (have the ones you set stay set until you change them).

If you know even the slightest bit about python programming, I can till you what to hack into the interface code to make this happen. IMHO the real power from that logging code comes from the programmatic features -- oh and the fact that it works.


d

 

My bad. I thought he was "implying" that the he wanted the wide-band AFR signals from the S.M.A.R.T. Xede (i.e. Innovate LC1), which you obviously cannot get through the stock ECU.

pyXede is pretty cool software considering it's free, not trying to start a fight, just stating a fact. And no, other than the fact that we both endure sub-zero temperatures most mortals could not fathom, we are not affiliated.

 

I have no clue on programming I like to use pyxede to import my log csv files. I have to add a # infront of the first 4 rows and the last row for the import to work. But it works

 

Weirdness. As you can probably guess, # is the 'comment character'. It tells pyxede to ignore a line. If you email me some log files (address is in the "about pyxede box"), i'll figure out what it's failing and see if i can make it not do that anymore.

d

 

IMO, since pocketlogger runs on a Palm OS, it's useless for me. If I'm already logging my XEDE data with a Windows machine, then any OBD-II scanner would have to be windows based as well. On the plus side, though, it looks like the Evo will support up to 20 samples per second with the pocketlogger.

l8r)

 

You could always log timing from the ECU directly, and then do the math from an Xede log to see what the *actual* timing is...

The Xede will only output crank signal offset values, not actual timing. The timing that you log from the ECU is what it *thinks* it is running, since it is being "fed" a fake crank signal by the Xede.

 

Donour you have an OBD-II that you wrote software for. In your opinion how many samples per second (per variable) can the Evo's ECU support?

I know the probe that I have will only do 4-5 per second with one variable. The author claims that this is a limitation of the OBD-II protocol.

 

In my case the samplerate is limited by the hardware am using at a horrible 3 hz, so i'm not a very good reference for this one.

d

 

I'll send you copies of some new ones this week since all of mine have the # already.