Congrats on the new version. Is there any actual plan for an iPad release? There are a couple of dead threads about that question unanswered, and my support emails also unanswered. Just want to know as I am planning a new setup for convenient and continuous logging.

 

Hello,

Thanks to Hamish, finally I could install and test mode23 logging with this brand new 2.9.0017 today. Great improvements! I donated via PayPal.

Hamish, I have a trouble : EvoScan 2.9.0017 automatically disconnects logging. This is very troublesome so I want to solve it as soon as possible.

I found one condition, when I release ( or loosen ) my accel pedal, EvoScan 2.9.0017 disconnects logging ( and never reconnects automatically again ).

This unexpected auto disconnect occurs while idling, too. When my car is idling, EvoScan 2.9.0017 seems to disconnect logging randomly.

I assume that it is related to throttle sensor reading but not sure.

Hamish, could you please help me?

 

sorry for newbie question, what does this message mean?

I don't understand what "cap at 485nm" means,though it seems to show some kind of logging speed limit for developer...

 

It could just be PC related, you have PM, I will check it out for you.

that notes field relates to which ever data item you have selected in the left hand side. you might be selected on EvoX EFI Engine Torque calculation? it is true for that data item from the ecu, it is capped at 485nm due to internal Mitsubishi ecu calculation limitations.

 

Hello,

Hamish, thank you for your help.

Ummm...I don't know about "EvoX EFI Engine Torque calculation" at all. Is there any instruction/explanation/manual about it?
Attached is a pic of my EvoScan screen. I was selecting "EVOX EFI". No need to select it for usual logging?

 

Congrats and thank you on shipping the latest version!


-Bink

 

I have just found a bug. It's not possible to log Injector Duty %, it's always a zero. Yes, I have selected Injector Pulse Width (this one is working). While tryng to log Injector Duty %, "No Response from Vehicle ECU" can be seen in Notes screen on the right.
Can it be related with the fact, that I have edited Data Settings several times?

 

It works fine for me, but if you have the Injector Pulse Width after the IDC, it won't log IDC, they have to be in the correct order.

I found TPS is shown as deg instead of % and ZTX Boost Response is 38 instead of ZTX.

 

I will check if it works now. Thank's!
About TPS: if we look at EvoScan v2.8, we can see, that TPS data settings are the same, just units are "%" instead of "Degrees".
Moreover, I have noticed, that with v2.9 I get a slightly slower logging speed, than with v2.8, it feels a little bit laggy. With "Disable Multithreading" checked it's much better, although...

 

lol, it doesn't feel laggy. it just looks laggy, because the UI isn't keeping up with the Faster logging speed . check your csv logs, you'll find its logging more data at a faster speed. In fact turn off log to screen will give you another performance boost. With "disable multithreading" checked, will actually slow you down.

 

Thanks Greg, I'll correct this and a few other minor xml things in the next auto update.

Crimson_Red I will also include your 2010 EvoX mode23 requestids. It might be the way you have edited your xml file to include the missing mode23 requestids, I'll look at it a bit closer.

 

I hadn't any chance to do some logs to file yet Played with new version only once...

 

I saw this posted in another thread for EvoX mode23 datalogging... thought it might be useful to some people on here.

 

Hamish, I've never sent my EvoScan xml file to you. If you need it, I'll send it to you.

 

yep, post it here. or email it to evom at evoscan.com

thanks.