You can plot dyno's with either by importing them into data log lab.

So it looks like others are having problems with the zt2 map sensor on mitsulogger?

 

Anyone have the link to download .99? I paid and have my key and everything.. spam filter must have got the email this time or something.

 

My ZT2 works fine on Mitsulogger...but I am having problems w/ Evoscan v.99 in that it does not capture my boost from the ZT2.

 

If your 0.99 didn't get to you you can try finding your original 0.97 email with your serial number and the limitless.nz.paymentrecieved link.

Not sure if it will be the current 0.99 but it will be 0.99 nonetheless

 

That's my problem lol. I lost all my email when I upgraded (downgraded) to windows vista. Luckily I wrote the serial # down

 

I haven't heard of anyone having trouble with the map sensor. There was an issue with the RPM signal if it was hooked up. That was addressed in a later version though. But thats off topic for this thread.

 

Ditto and i'm trying to search around on why. I like how well the zt2 software captures boost but can't get the same out of Evoscan right now I know I'm needing to get an updated definition file for DLL but I don't see it in the excel file at all. I haven't had enought time to look into it further but hope to soon.

Crap I just saw your post malibujack: I was having problems with mitsulogger/zt2 getting boost as well but to be quite honest haven't had time to troubleshoot or anything. I'm just trying to get some good logs so a tuner can help me out.

 

I don't know that Evoscan logs boost from the ZT2, I think the value it shows as MAP is actually an ECU value, and therefore not really accurate on the USDM cars.

I know for certain that boost works fine in my app, because I've been using it for some time and it was developed with the unit on my bench and I had the ability to hook the sensor up to a vacuum/pressure source.

The log stream is not well documented, I worked directly with Zeitronix to get their device supported, I can see it being difficult to reverse engineer without having access to the device.

 

Anyone had an issue with .99 changing their LC-1 fuel type settings to custom?

 

is anybody having a problem with the dyno plots in 0.99? it does not plot the whole run and is always the same numbers no matter what the run is. 289whp 265wtq both @ 0rpm. lol.

also, my lc-1 flatlines at 10.44:1 in evoscan. the sensor can see down into the low 8's using logworks.

any ideas?

CJ

 

You are doing better than us, Our Evo IX puts out 900hp on stock turbo. lol

 

lol, at least my numbers are closer to reality....but yours are much more impressive!

Seriously, it seems to be working for some people but not others. I wonder what the deciding factor is. I am only logging needed channels, i.e. speed, rpm and 2 byte load and WB AFR. Still, no good plots.

CJ

 

Even logging 2 byte load and rpm I am making 335whp @ 0 and 269 ft lbs of torque if I leave it on auto calc. If I change it to a gear (for instance the gear I was in when I did the pull) I get results like Scott.

I am only using it as a comparison from one run to the next for a rough idea of changes.


edit- Okay so I spent some more time looking at the power graph in detail and if you zoom in and then run the cursor over the graph it will give you calculated hp/torque at any given rpm. The aforementioned run made 335 at 7031rpm according to this but the peak torque value is also showing 269 ft lbs at that rpm.

 

can somebody tell me what is the difference between the two cables? http://www.limitless.co.nz/Cables/

 

One is for JUST datalogging using a cable to hook up to the OBDII port. The other more expensive one is for logging and flashing the ECU using ECUFlash, a free application. The second mentioned cable has a white connector in addition to the black OBDII connector.

CJ