I was told that the value goes to zero when the boost is at zero, is this true for you too? perhaps its the scaling factor needs tweaking

 

Any ideas on when this 1.0 version will be released, evo4mad?

 

I will try and do another log tonight and see if I can check the values other than it being 0 at 0 psi. I will get into boost and try to compare the data.

 

I looked closely into the datalog and this is what I found:

The Zeitronix boost values go from -245 to 235. For example, in my data log at the ecu 7125 RPMs then the Zeitronix boost was 235 (should be around 23 psi) but the Zeitronix RPMs value was only 3600 so look like it's off.

On my way to full boost at around 5000 rpms (gt35r) the logged Zietronix value did run by 0 value. Also, the Zeitronix RPM values never gone more than 3600.

I was unable to log EGT since my sensor is dead so the value was always at 200.

Let me know if there's anything you need to know. Thank for the good work.

 

Any update on the release, my laptop got a bug and they could not recover so Im waiting on the newest version.

 

Any updates on the 1.0 release?

 

Hamish,

I was finally able to get some time to log this weekend. I can confirm that the boost on the ZT2 logs perfectly for me. I have recorded boost up to 25psi on my zt2 which was confirmed on my gauge which also runs off a map sensor. I have not tested zt2 rpm or egt or tps any further though.

 

SO I WAS JUST WONDERING IF THIS NEW PROGRAM IS COMING OUT?

 

Dude it will be out when its good and ready. Why would you want want a version that not done and has bugs. When he feels its up to his expectations it will be released like always.

 

In the case of evoscan the deadline should be taken with a grain of salt or two...results are good though.

 

yea...this is very true.

The new version of EvoScan usually comes out a bit after it was intended to but it is typically packed with new features and worth the wait.

 

It will probably come out as version 1.1

 

Evo4mad

Could you consider reversing the low and high fuel trims to the following?

In version .98 or .99 you swapped the low and high trims. Was this on purpose or by mistake? It creates confusion for the end users...Thanks

0C = LTFT Lo
0D = LTFT Mid
0E = LTFT High
0F = STFT

 

The low and high trims were reversed. 0x0C is low, 0x0D is mid, 0x0E is high.

 

I love EvoScan, but the one thing that bothers me to no end is the fact that once you log with a wideband attached, there isn't a way to tell it that there is no wideband attached when you want to log again. In other words, it's always searching that COM port for a wideband even if there isn't one attached.

Will there be a "no wideband connected" option in this release?