I added an update to msqur today. Just a small update to the landing page since it was kind of blank. Moved the settings icon to the view page instead of every page. Also fixed the readme and license files for formatting. I get a lot of hits from Russia on that site. Actually, I get a lot of hits from Russia on all my sites. I imagine most of them are bots probing for weaknesses.

As mentioned previously, I wanted to open the source to msqur up and put development on the backburner. I have added an appropriate license for it (although I do need to add library licenses/notices in there as well). It is now GPL licensed, and I have made the repository public. Some things I added: Added basic charts for the 2D tables Added table header text to tables Added reingest script to allow for easier MSQ cache updates Fixed some of the documentation up Known issues, mostly the same as before:

I dug in this past weekend and updated a few things: INI Parsing revamp. Support for more tables and curves. UI Update so that all this new information is somewhat organized A few minor bug fixes and enhancements Known issues: MS3 file support is poor Constants are just blurted out without any organization INI Parsing of formulas and directives not implemented yet I plan on opening the source code up under some kind of OSS license, after fixing a few more issues and updating the documentation.

A little while ago I updated msqur.com to 0.60b. Changes include: Added engine make/code fields for uploads Added view count and increment And less visibly: Finished OO refactor Update API documentation (not public yet) Added deployment scripts I still haven’t finished INI file parsing 100%. There’s a bit more to do, but I’ve been busy with work and other projects. I’m thinking of releasing the project under an appropriate open-source license once I finish that, so hopefully others can join in on the fun.

I’ve rolled out the update 0.53b to msqur.com. This includes: INI Parsing (i.e. better MSQ support) Bug fixes and better error handling So now it is a bit more usable. The INI Parsing turns out to be a bit more complex than I anticipated, but I rolled out a decent intermediate update in the meantime. Before completing the INI parsing (or anything else for that matter), I’ve decided to overhaul the entire codebase.

Well, the holidays are long over and I haven’t updated msqur.com in a while. I’m adding some configuration management to it, so nothing visible will happen for a while. What’s planned, however, is .ini file parsing so that .msq files can be parsed according to the INI file version they use. That is, I will parse the INI file for the schema to a .msq file instead of hardcoding it. This way showing a .

Well, I’ve only been working on it a little so far, but I suppose it’s good enough to post about at this point. The site is msqur.com, and it’s for Megasquirt ECU users to share their tunes (from the TunerStudio MS software). You can upload (multiple) .msq files, assign some engine information to them at upload, and share them with other people for troubleshooting or tuning help. The goal is to make something easier than attaching a file to a forum post that others have to download and fire up the full tuning software suite to just view it.