I must of missed something is 2.7 beta 5 still the most current?

 

Disable multi-threading from the logging menu is off by default on my installation of Evoscan, so that wasn't my issue. I actually had a similiar problem on my new Toshiba laptop at WOT, it turns out, its enough to set the Hard Drive motion/drop protection into action, turn it off in the settings. or put your laptop on a jacket on your passenger seat. better yet, get a passenger to hold your laptop. It actually goes to show how hard driving in hard suspension EVO is on a laptop, lol. I heard that Evoscan v2.7 beta has 30 second log file buffering now, but if you are on a bumpy road or at WOT, things are still not going to be happy with your laptop spinning Hard Drive. I've also noticed the standalone evoscan unit can datalog with op2.0 cable very well with no skipping issues, probably because the sdcard has no moving parts, unlike a laptop which has spinning hdds. Laptops are ok on a dyno, because theres no real inertia

 

I'm on about v2.7 beta 20. I think its only available to those on his msn messenger that give him feedback daily.

 

Ahh...OK.

I'll wait till it's "released"

 

hmmm beta 20 huh..yea i'll wait for that one to be released too..

 

That's actually a very likely possibility...

I have multithreading off, but it's entirely possible that the sudden motion protection is causing issues. I'll give it a try, thanks!

 

YEah, EvoX map tracer editor with reflasher all in one tool... sweet.
https://www.evolutionm.net/forums/8078837-post1231.html

 

I got the following results:

start temp 44F

End Temp max aprox 178 then cycle from 172 to 176


F temp . . . . . . x (Unknown temp)
44 . . . . . . . . . . . . . . .51
176 . . . . . . . . . . . . . 126

F =(m*X)+b

Where x is the unknown temp m is slope and b is the intercept


F temp . . x (Unknown temp) . . . . . . . . . . . . . . equation
44 . . . . . . . . . . 51 . . . . . . . . . . . . . . . . 44 = 51m + b => 44-51m = b
176 . . . . . . . . 126 . . . . . . . . . . . . . . . . 176 = 126m + b => 176-126m = b

44-51m = 176-126m => -132 = -75m => -132/-75 = m => m = 1.76

so with m defined we can calculate b

F = m*x +b => 44 = 1.76*51 + b => 44 = 89.76 + b => b = -45.76

So conversion of x to F is F = 1.76*x -45.76... so the "size" of each deg (1.76) is very close to the "size" of a deg C (1.8) when compared to deg F. Assuming they are actually the same, and adjusting the intecpt as well to get correct results we end up with a final formula of:

F = (1.8*x)-50

For the speed formula I was able to verify that kph = 2*x, so the correct formula for mph is mph = kph / 1.609344 and the given formula in EVOscan for kph is x*2 then the formula for mph should be x*2/1.609344. This breaks down to mph = x*1.24274239.... so from now on I will be using
mph = x*1.243

Later,

Keith

 

good work.

don't need the brackets (multiplication always takes effect before additions),

also don't you think its a major coincidence that its basically the universal formula of F = 1.8 × C + 32

x-40 is the universal formula for Mitsubishi DegC

which is effectively: 1.8 * (x-40) + 32 <--- try that one, let us know if it works.

 

First thing I checked That is why I concluded that the standard C = X-40 is incorrect.

If you use 1.8*(x-40)+32 with the data I started off with of 51 for the logged value of x at cold start after sitting all night with ambient temperature of 42F you end up as follows:

1.8*(51-40)+32 => 1.8*11 + 32 => 19.8 + 32 => 51.8 The actual temperature was 44F by the thermometer in the car, 42F by my outside house thermometer (more accurate of the two) so it is off by a full 10 deg. At the other end of the spectrum we have 126 for the value of x

1.8*(126-40)+32 => 1.8*86 +32 => 154.8 + 32 => 186.8 The actual temperature at idle is right around 176F, so once again off by a full 10 deg high.

I don't know who came up with the C=x-40... but it is not correct at least on my car. I can do the math for any of my non-american brothers out there that want the correct value to calculate temp in deg C if anyone requests it

Keith

 

x-40 is correct.

what memory location+romid are you logging?

 

23808653 on ROM ID 55590006. And yes, C=x-40 is specified in the code for this ROM ID.... I think my temp sensor is off by 10 F (5.6 C)

So, if it is a temperature sensor miss calibration on my car so that the ECU thinks my car is 10 F warmer than it is my fans will kick on early, and kick into high speed early... are there any protective functions that will kick in early? The fans are not a real problem, but I wouldn't want the car to go into limp mode of some kind when it is not actually over heating.

Hey Tephra, in the 55590006 code is memory location 23804573 the LTFT idle or LTFT cruise?

And last but not least... is there any way to get ride of this F#$%ing P0139 for 55590006?

I was talking with Hamish tonight, and we were wondering about the Manifold Air Temp. The memory location he has is 2380867A, but that does not work for 55590006... I get a constant -40 indicating that the x value is a constant zero.

We also talked about the next things that it would be useful to log would be injector pulse width and duty cycle.

Just throwing around ideas here

Thanks,

Keith

 

1) leave your car overnight, in the morning compare the temp sensor on the HUD to the logged item - as long as your car isn't/wasn't in the sun they should be the same - within 1-2C

2) not sure on the LTFT, look at the addresses for MUT0C/0D/0E (from memory are low/mid/high OR idle/cruise/high)

3) P0139 is slowly being worked on

4) MAT is usually +5bytes from MUT11

5) IPW = MUT21 + 20

6) IDC you can calculate from IPW*RPM/1200

 

I have just read the first 30 pages and will try and read the rest in the morning. Yes I did read the illistrated "How To"

I have a few noob questions about getting mode 23 working. I down loaded the newest version of EVO SCAN today, and have the 2.0 cable, and ECU FLASH. my ROMID is 52680015.

I am pretty sure I can work my way through this, but what are the Attached Files for in the first post? Are they for a different logger?

I got to this step and was stuck.

Copy the XML from step 5 and paste it BEFORE </rom>


I found it and opened the xxxxx15 file, but could not copy or paste or edit the three lines of text that needed to be inserted. I know now that I needed to open the file with note pad and make the addition. Then do I just hit save when I am in note pad and it will save in the right place and the right type of file?

Thanks for all the hard work that went into this.

 

Yup, you edit the file in notepad and save it. It will save in the same file format and file name that it had to start with. BEFORE doing this make a copy of the original and save it in a separate location just in case you screw up your edit you have a clean backup.

Keith