Bug with recent beta: EAE CLT units (deg vs. ºF or ºC)

This is a forum for discussing the development and testing of alpha MS2/Extra code. Documentation
(Runs on MS2 and Microsquirt)

Moderators: jsmcortina, muythaibxr

Post Reply
Shad Laws
MS/Extra Newbie
Posts: 18
Joined: Fri May 04, 2007 9:58 am
Location: Palo Alto, CA

Bug with recent beta: EAE CLT units (deg vs. ºF or ºC)

Post by Shad Laws »

Hello-

I've tried to upgrade from MS2Extra v1.0.2 to recent beta versions a couple of times without success. Before I quickly gave up and went back to v1.0.2, but this weekend I'd like to change that :-).

Anyway, one thing I've noticed is that the EAE CLT bins (both adhered and sucked) get wonky when upgrading. If you simply use the same msq, the units go from "ºF" to "deg" and the bin values change radically. If I go into an msq that was saved with a recent beta and manually change these by hand, they get changed back when I reload it. Is this a bug, or am I missing something?

Now, if I can just figure out my engine never fires up with beta but always do when I downgrade back to v1.0.2 I'll be set :-).

Thanks!

Take care,
Shad
Last edited by Shad Laws on Sat Feb 16, 2008 2:00 pm, edited 3 times in total.
Shad Laws
MS/Extra Newbie
Posts: 18
Joined: Fri May 04, 2007 9:58 am
Location: Palo Alto, CA

Post by Shad Laws »

An update: I poked around the megatune ini file and found out why this was happening... the lines that set the units for Celsius and Fahrenheit now have "deg" in them instead of "ºC" and "ºF". If I change them to what I'd expect (i.e. "ºC" and "ºF"), Megatune and the msq behave normally. I haven't yet gotten this running on the car, so I don't yet know if this is a good or a bad idea... any thoughts? BTW, to find the lines in the megatune ini, search for "EAEAWWCLTbins"

Thanks!

Take care,
Shad
Shad Laws
MS/Extra Newbie
Posts: 18
Joined: Fri May 04, 2007 9:58 am
Location: Palo Alto, CA

Post by Shad Laws »

Another update: I've confirmed that it works like a charm if you fix that. My car fired up without a second thought!

So, here's the bug: the lines in the Megatune's ini file that read:

#if CELSIUS
EAEAWWCLTbins = array, S16, 932, [ 12], "deg", 0.05555, -320.000, -40.00, 2500.00, 0
EAESOWCLTbins = array, S16, 956, [ 12], "deg", 0.05555, -320.000, -40.00, 2500.00, 0
#else
EAEAWWCLTbins = array, S16, 932, [ 12], "deg", 0.10000, 0.000,-40.00, 215.00, 1
EAESOWCLTbins = array, S16, 956, [ 12], "deg", 0.10000, 0.000,-40.00, 215.00, 1

Should read:

#if CELSIUS
EAEAWWCLTbins = array, S16, 932, [ 12], "°C", 0.05555, -320.000, -40.00, 2500.00, 0
EAESOWCLTbins = array, S16, 956, [ 12], "°C", 0.05555, -320.000, -40.00, 2500.00, 0
#else
EAEAWWCLTbins = array, S16, 932, [ 12], "°F", 0.10000, 0.000,-40.00, 215.00, 1
EAESOWCLTbins = array, S16, 956, [ 12], "°F", 0.10000, 0.000,-40.00, 215.00, 1

Does that sound right to you guys? It definately made a difference for me...

Thanks!

Take care,
Shad
muythaibxr
Site Admin
Posts: 8228
Joined: Thu Oct 14, 2004 12:48 pm

Post by muythaibxr »

That change by itself should not have fixed the problem, as the thing you changed only changed what is displayed in megatune, and not how the numbers themselves displayed.

James found at one point or another that when you have odd symbols (like the degree symbol) in the ini, it crashes megatune on some computers, which is why we changed it to "deg"

Ken
Shad Laws
MS/Extra Newbie
Posts: 18
Joined: Fri May 04, 2007 9:58 am
Location: Palo Alto, CA

Post by Shad Laws »

That makes sense that it shouldn't have made a difference... but it did. At bare minimum, it made a difference in the way Megatune set up the tables.

With the "deg" ini file, if I loaded up an msq I made with v1.0.2, the EAE CLT temperatures went nuts. Instead of going from 0-180 like I had them, they started at 200-something and ended at 300-something. This caused error messages. With the "ºF" ini file, I loaded up the msq seamlessly - it all translated perfectly.

Also, I noticed that "deg" was only used in the ini file where it referred to crank angle degrees (a.k.a. CAD). The only place it was used for temperature was in the EAE CLT bins... nowhere else. <shrug>

Thanks!

Take care,
Shad
muythaibxr
Site Admin
Posts: 8228
Joined: Thu Oct 14, 2004 12:48 pm

Post by muythaibxr »

Well, first off, you shouldn't load a 1.0.2 msq in 2.0

That'll cause all kinds of problems, and I'm not surprised that you had the problem you're seeing.

On that upgrade, the settings should be re-entered manually.

Ken
Shad Laws
MS/Extra Newbie
Posts: 18
Joined: Fri May 04, 2007 9:58 am
Location: Palo Alto, CA

Post by Shad Laws »

Hey Ken-

True - updating the msq blindly is a bad idea. After loading it, I went through each screen one at a time to ensure that each setting was correct. But, at least in my configuration, the only other oddball was the 12x12 vs. 16x16 fuel table, which was to be expected. Everything else translated beautifully with the "deg" thing changed.

At minimum, it appears that Megatune uses the "deg" thing for more than a units label. Otherwise, changing it wouldn't make it import things any better (I repeated these results a few times - it's consistent at least on my computer). Also, there is some inconsistency in the ini file that "deg" is only used for EAE CLT temperatures - it's still "ºC" and "ºF" everywhere else. <shrug>

However, your point is well taken: this shouldn't mean that I should blindly import msq. Dumb question: if I import a v1.0.2 msq and then go through every screen to double-check stuff, is that still inadvisable?

Take care,
Shad
Post Reply