MSQ Saves

Forum for discussing Tuner StudioMS tuning & datalogging software.
Forum rules
Read the manual to see if your question is answered there before posting. If you have questions about MS1/Extra or MS2/Extra or other non-B&G code configuration or tuning, please post them at http://www.msextra.com The full forum rules are here: Forum Rules, be sure to read them all regularly.
Post Reply
LT401Vette
Helpful Squirter
Posts: 75
Joined: Sat Jul 16, 2005 7:07 am
Location: Charlotte, NC
Contact:

MSQ Saves

Post by LT401Vette »

Eric,
When opening and modifying this MSII 2.36 msq in MegaLogViewer, then savinging, MT generates Warnings when reloading it.

Code: Select all

   WARNING(04): Constant "IACcoldtmp" units mismatch, "°F" in msq, expected "°F" from ini.

   WARNING(04): Constant "IdleHyst" units mismatch, "°F" in msq, expected "°F" from ini.

   WARNING(04): Constant "clt0" units mismatch, "°F" in msq, expected "°F" from ini.

   WARNING(04): Constant "egoTemp" units mismatch, "°F" in msq, expected "°F" from ini.

   WARNING(04): Constant "fastIdleT" units mismatch, "°F" in msq, expected "°F" from ini.

   WARNING(04): Constant "mat0" units mismatch, "°F" in msq, expected "°F" from ini.

   WARNING(04): Constant "tempTable" units mismatch, "°F" in msq, expected "°F" from ini.
So the errors all appear to be around the "°F". But it I open the original MT saved MSQ and the MLV saved MSQ, It do not see the funky a. It looks fine.

Any insight? Is my XML parser maybe just turning the ° from ASCII to Unicode? Then MT see's and extra byte in front of the °?
Phil Tobin
EFI Analytics
http://www.efiAnalytics.com/
LT401Vette
Helpful Squirter
Posts: 75
Joined: Sat Jul 16, 2005 7:07 am
Location: Charlotte, NC
Contact:

Post by LT401Vette »

I copied the °F from both MSQ's into a hex editor and sure enough there is an extra byte in front of the °. Then I checked the encoding, uh oh.... MSQ's are in "ISO-8859-1"
MLV is encoding to UTF-8

Code: Select all

°F
Phil Tobin
EFI Analytics
http://www.efiAnalytics.com/
efahl
Site Admin
Posts: 232
Joined: Mon Feb 16, 2004 3:15 pm
Location: San Clemente, California, USA
Contact:

Post by efahl »

Phil,

I saw this in some of the ini files that James had, I think it was the editor he was using. I use gvim to edit them (old unix habit of editing everything with vi), so I saw the funky characters right away. I'm guessing that it's wordpad that's doing the damage.

Eric
LT401Vette
Helpful Squirter
Posts: 75
Joined: Sat Jul 16, 2005 7:07 am
Location: Charlotte, NC
Contact:

Post by LT401Vette »

It was actually the encoding I was using when I did the xml transformation. I was using the default UTF-8 instead of ISO-8859-1. This put things in unicode and added an extra byte in front of the ANSI character.
Phil Tobin
EFI Analytics
http://www.efiAnalytics.com/
Post Reply