ECUFlash / Evoscan / Mitsulogger Questions
If you go on Evoscan's website, they have the 1.3 cables there. The new cable is the 2.0, I heard there is problems with it working with Evoscan. They did just realease Evoscan v2.6 which has a spot to check off that you have a 2.0 cable.
Now Bump for my question! lol
Now Bump for my question! lol
I was searching around to try and better understand 2 byte load...and have a question
if I add the code and the mut valves and what not
does it change anything within my tune or is it strictly a means of better load calc?
will it do anything but log differently?
if I add the code and the mut valves and what not
does it change anything within my tune or is it strictly a means of better load calc?
will it do anything but log differently?
I loaded the two byte mod about a month ago, and noticed the readings have a 10% difference. Where I'd get a 227 load at 7000rpm on one byte, I get 214 load at 7000rpm with 2byte. I just end up using both readings to tune.
anyone else?
well I got the zeitronix all hooked nd ready to tune, and now all of a sudden I try mitsulogger and I cant get any info bcause this. It also says that the openport 1.3 is I guess unreadible,the weird part is that I try it on idle and it collects data the error coms when I go open throttle.
error messege
JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
error messege
JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Last edited by bevolucion; Dec 2, 2008 at 04:23 PM.
I have a question about tuning timing on the IX's, given that they come with 3 ignition maps, is the best way to make the changes across all 3 maps (make all 3 identical) or do you tune a specific one.
Make all three high octane iginition maps the same. The ECU interpolates between them, but we do not know the interpolation logic, so we make them the same.


