0.988.7 Release

[LT401Vette]

0.988.7 was just put out and I figured I would give a list of changes before someone asks. These are the changes that come to mind anyway, it certainly isn't a comprehensive list:

Burst Logging
Curves have text based inputs. (Press A)
MegaLogViewer Launch from DataLog menu
Rearranged the Project/File menu, if a Project is open, project options are put on a sub menu.
Comm Timings slow all timings with slower data rate.
FRD file logging on menu
several improvements to Complex dialog layouts
LiveGraphs like in the Accel Wizard can now be defined in the ini and added to any dialog
Increased button size and spacing for 2D table toolbar
Specified Character set encoding for ini loading, Linux defaulted to something weird and created degree symbol errors. This will cause a warning of units mis-match when loading any msq's that were saved on linux with an earlier version of TS.
CAN work, blockingFactor reads.
Improved ini mismatch handling.
Bug fix - data log empty if started before connecting.
Bug in handling hex values in enable conditions
Bug Fix - MS2 Narrowband calibration incorrect.

[Jesper H]

Cant open "Warmup Wizard", It says: Error showing Dialog - null

[LT401Vette]

Ouch I see a problem for MS1...
I'll get a fix out this evening.

[justins71]

I can't seem to load any saved dashboards... It shows that it's saved, but will only load the default dash.

[LT401Vette]

Any Dash? Or a particular one you have saved?
If you right click and select Load / Save --> Load Saved Dashboard

What do you get?

[justins71]

Just the ones I've saved. It works on some, but i've been goin and doin save as, then save again.

Doin some quick tests, it seems that it won't save if i load another dashboard before closing/restarting. Example, make a dash, save it, load another, then try to reload one earlier saved, doesn't work. Restart program, still won't load. Now if i make a dash, save it, restart the program, everything works like normal. I can switch between dashes at will, no loading issues.

[LT401Vette]

There is definitely something screwy going on there.... It looks like it starts doing all saves to the Save As file until you restart.

Thanks for pointing it out, I'll get it worked out.

[Southcross]

Hey, would it be possible to have the dialog windows like Warm Up Enrichment, ASE, etc to be toggleable between Celsius and Fahrenheit (without actually changing anything else, just the display of data)? I'm looking at other's screen shot'ed MSQ data and it drives me nuts trying to convert it in my head when I copy it over... why in the world would you use Fahrenheit on a European car where all the gauges (sensors, thermostats, etc etc) are in Celsius

[Southcross]

had a bright idea of changing the project to Fahrenheit and just change it back... ack, did it ever freak out

16 Warnings:
Warning: MSQ Units Mismatch for egoTemp! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for tempTable! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for clt0! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for IdleHyst! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for fastIdleT! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for IACcoldtmp! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for mat0! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for pwmidle_crank_clt_temps! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for matCorrTemps! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for pwmidle_clt_temps! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for temp_table_p5! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for fc_clt! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for matTemps! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for N2OClt! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for idleadvance_clt! °F found in current configuration, °C found in MSQ, values were converted to °F.
Warning: MSQ Units Mismatch for RevLimLookup! °F found in current configuration, °C found in MSQ, values were converted to °F.

[LT401Vette]

It would be possible...

If you read those warning messages, it does actually convert the °C msq into °F values. So you are fine loading a °C msq while you are set for F, you will just get warning messages, but the values will be converted.

[Southcross]

sure... it worked (I did it that way already)... but saving your tune, changing your project properties, re-load the tune (it auto changes temp values), make new changes, re-save the tune, change project properties back, re-load the tune (it changes temp values), burn, save final MSQ... uhg

[Eales V8]

Could someone explain what burst logging is please


Nige

[LT401Vette]

Burst logging had 2 purposes, and I have found that for it to truly do both on all firmwares I needed to divide them. I just did this last night after learning that on some firmwares the burstCommand in the ini can not be used against a Palm. PalmLog is always expecting a single character. In the next release there will be separate menu options for both and they look like this:

Burst Data logging - Turns off all application functions including the dashboard and captures a the log at the fastest rate the firmware will give. In this mode MS2Extra will run at about 40 records/sec

Palm Log Extract - For pulling log files from a Palm that were captured using PalmLog

[Eales V8]

So,

If I have this for say MS1 V3 connected to a Quad core laptop Burst logging has no beneifit ?

Not being clever, seriously trying to learn more / understand !!

Nige

[LT401Vette]

If I have this for say MS1 V3 connected to a Quad core laptop Burst logging has no beneifit ?

Not being clever, seriously trying to learn more / understand !!

Actually, you may get a bit better throughput regardless of your cpu, because the timings are more aggressive. I get about 5 records a second faster on a the laptop with a 2.2 GHz duo core and it never sees 20% CPU utilization. That is against MS2 Extra though. I don't think you will get as much of a gain out of an MS1, but I haven't measured that yet.

[LT401Vette]

I just gave it a try against an MS1 with HiRes code on it.
Normal logging at max data rate: 19.2 records/sec
Burst Mode Logging: 20.4 records / sec

so there is an improvement, but only about 1/sec. I doubt I would go to far out of my way for that The MS1 Extra might go just a tick faster as there are a couple less bytes in the payload, but that wouldn't be too significant.

Something else to note though is that some firmwares do return an occasional bad value if you try to pull the data at the max rate. Typically it will just be a value of 0 for the last byte or 2. The HiRes code does this. Where if you run with a data rate of 20/sec, it should always be good and still do the 19/sec.

The MS2Extra is the fastest firmware, that will give over 40 records/sec in burst mode even though it has the biggest payload, in my tests it is always clean data too.

But the MS3 SD logger will put that to shame

[kritip]

40/s, nice Another great feature. Will try this later on my 3 hour drive. Should see some large logs, adn also double check if the alpha code chucks out any erronous data

What limits this data, the MS2 processor speed, or the interface chip or serial controller. Just asking as my ftdi usb adapter can run much higer that 115000

[racingmini_mtl]

40/s, nice Another great feature. Will try this later on my 3 hour drive. Should see some large logs, adn also double check if the alpha code chucks out any erronous data

I'm also interested in that even though it seems to be behaving well.

Jean

[LT401Vette]

I'll try to get a release out tonight, I have made several changes to the burst logging since 0.988.7a

[kritip]

OK, I will log in a few hours, I will be returning in a few day, so will then log with the newer TS release