if the baud rate is to high or low could i possibly change it to where it needs to be without anything bad happening and why would this change it was working fine then i closed the program then reopend and tried to read again and then it just started doing that and no i didnt flash or anything just closed out evoscan. BTW thanks for the input already.

 

NVM thank you just took a chance and changed the baud rate and it works fine now thank you so much i was panicing so thanks again codgi you are a life saver

 

Yeah sorry I didn't see that question until after .

The text box actually just needs a stray number to go in there and it will remember it. It really should display as a read-only box and only if someone clicks on some hard button (change baud rate) then should it allow itself be edited. I seem to remember debug mode for Wideband also changing the value but oh well just watch out for it in future.

 

How can you capture "2-byte Load" using MitsuLogger? Does anyone know how to alter registerID.xml to make it work?

MJ had it on other thread: Add below to the MitsuLogger registerID.XML file
----------------------
<Request LogReference="requestID00" RequestID="00" Eval="x" Unit="INT" Logged="y" Response="2"/>
<Request LogReference="requestID01" RequestID="01" Eval="x" Unit="INT" Logged="y" Response="2"/>
<Request LogReference="2ByteLoad" RequestID="FF" Eval="((256*requestID00)+requestID01)*10/32" Unit="2byteLoad" Logged="y" Response="2"/>

Also, don't forget the 2-byte load setup on other thread where you need to flash your ECU with different set of number...

 

anyone log both a ZT2 and evoscan at the same time (err, meaning using the WB input of evoscan)? Im using a serial to usb adapter (COM 5), but when I try to log via evoscan it doesnt work, get a "unable to open port" error, or the signal get get fubared and it wont log at all

any ideas?

 

I have never seen a benefit in logging ZT2 afr to evoscan. Logging them concurrently at the same time on both loggers is the best way to obtain data.

 

Im lazy and havnt hooked up the rpm input to the ZT2, so logging in evoscan gives me rpm reference

 

Its one freakin wire, green to green on the 2nd harness plug, lower row, 2nd wire to the right.

Do it... Do it now!

 

Im not sure where the harness is, and getting to the green wire will require me to rip my center console out since thats where I mounted the brain

 

up

 

This question pertains to Evoscan 1.0 Alpha.

Today I logged a Lancer Evolution VII GSR. Everything logged fine except 2Byte Load:



Why are the readings so off? The car was feeling down on power but I didn't see anything wrong in the logs.

Here is a copy of the log for assistance: http://download.yousendit.com/7E27787E72F994B4

 

problem with evoscan:

Was using it to log WB with my LC-1...unclicked it last night (cause i didnt feel like connecting the LC-1 to the laptop) to do some timing tuning.

When i clicked back on the WB, it only reads 1-5v...not the actual AFR's anymore.
I didnt change anything in the .xml.

The LC-1 still works fine with all the other programs, Logworks, Mitsulogger, etc...

p.s. using Evoscan v.99

 

I found a few threads that address the same problem...but i already checked gas type, and its set on Gasoline. The LC-1 works fine with Logworks.

https://www.evolutionm.net/forums/sh...n+LC-1+problem

https://www.evolutionm.net/forums/sh...56#post3842556

 

:bump: ...its still doing it. anyone have any insight?

 

my v1.0 is logging lc1 afr fine