Yeah, I thought the same thing too so I decided to download it and install it again. I was able to install it without any problems and it isn't an RAR archieved file. I have no idea why you are using WinRAR, I suggest uninstalling WinRAR and redownloading/installing ECUFlash again.

 

I tried again and got the same thing. I thought it might be a zip file thats why I got WIN RAR. It downloads really fast. l would think it would take longer. Do I need to change something on my net book? Or download it to a different location?

I have the older version on my laptop. but it is old and solw and the battery is shot, but it works. So I think I installed mode23 with my laptop, and I thought I would just use my net book to make some logs, but the net book dose not have the driver for the openport 2.0 cable. Where can I get the driver just for the 2.0 cable?

 

when is the new evoscan gonna be released

 

Soon, I hope. And from what the beta testers are saying, it shouldn't be long: https://www.evolutionm.net/forums/ec...ml#post8109420

 

maybe this has already been explained but while looking at something else I noticed what I thought was a duplicate in the first post but the address's are different???

55580005
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" address="7f107" type="1D" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" address="8ad43" type="1D" scaling="Hex8"/>
<table name="DoMode 0x4D -> 0x5D" category="Misc" address="8ad4a" type="1D" scaling="Hex16"/>

55580005
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" type="1D" address="0x7f10b" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" type="1D" address="0x8ad4b" scaling="Hex8"/>
<table name="DoMode 0x4D -> 0x5D" category="Misc" type="1D" address="0x8ad52" scaling="Hex16"/>

 

Cool, on E-85 I am seeing

2.6ms at idle

25 ms at 23.5 psi of boost

18.6ms at redline around 16 psi of boost.

Looks about right

Now what is wrong with my IDC calculation? I am getting way high numbers for IDC... at idle my IDC is reading 73% !!!

I used the formula [IPW]*3.90625*x/1200 where "x" is the address for RPM.

The interesting thing is that my actual RPM calculation uses 31.25*x and I notice that the IDC formulas that use 3.09625 have RPM values that also use 3.09625.

Here is the strangest part. When I plug the above formula [IPW]*3.90625*x/1200 into a spread sheet and input my data for IPW and RPM I get correct output (about 90% duty cycle at peak boost).... but using that same formula in the "function" block for my IDC calculation in EVOscan I get jacked up results that are way too high (3,210% instead of 90%)

I am soooo confused right now!

Keith

 

depends what RPM you are logging:

2byte formula = x*1000/256
1byte formula = x*31.25

 

Well, my RPM logging appears to be 1 byte. But for my IDC calculation it appears to be 2 byte. If I put everything in the IDC logging to match 1 byte should that correct the problem?

Now that I have a functional MUT Table perhaps I can actually understand the difference between 1 byte and 2 byte values and how they are used... do you have a tutorial on that type of thing somewhere in here?

Also, I can't find the thread dealing with making tuning not affected by LTFT's... I think that is what it was, and I remember implementing the changes in my ROM code... would that be why my LTFT's are a constant 12.5?

Thanks,

Keith

 

if the memory address for IDC is the same as RPM, and your RPM formula has 31.25*x, then use 31.25 instead of 3.90625

https://www.evolutionm.net/forums/ev...t-fueling.html

 

wow ! . lots of good reading here ... my eyes are burning ,

 

I had to do it myself :P

I have gone thru MUT communication again today.
I have a suspicion that we are unable to connect via MUT due to

ECU_OPTIONS_3 & 0x01 (bit 0) aka MUT Enable bit.
Is somebody willing to test changed ECU_OPTIONS_3 and logging via MUT EFI?

I am still awaiting ECU from HB Speed

Before you all jump on me:

 

Hey all,

I was wondering if any of you EvoScan beta testers have been able to get the Evo X ECU Reset to work.

I'd love to have this feature, especially for dialling in fuel trims. The Canadian ECUs have an anti-tamper shield on them, so if I ever go to help a local person out with trims, we either need to disconnect the battery and wait, or dremel off the shield so that we can pull the harnesses out.

Or, is there a manual command that we can send? ECU gods?

 

Tried it
Sorry does not work

 

What cable have you been using for logging?
If you are in posession of 1.3 can you repeat the test?

Otherwise I have to wait for the ecu.

 

Using a 2 . will try to get hold of a 1.3 and let you know