EMStudio, YATA(Yet Another Tuning Application)(was FreeTune)
Posted: Tue May 08, 2012 2:22 am
So I started working a bit on a Qt/c++ based datalog/live display application for FreeEMS. I eventually want to also work tuning into this application.
I started playing around with this about a week ago, fiddling around with just playing back logs with a lot of help from Fred fortunately, which made it go very quickly. He did a bit of explaining about the serial protocol involved, so with that and the OLV source code for value reference I managed to get the ability to listen to live data integrated. The serial code wasn't quite working properly though, and Fred tried it a couple of times for me without success. I happened to be in the Phoenix AZ area, and seank-efi graciously offered to let me stop by and check out his FreeEms setup. Once I got there, he showed me the hardware and let me attempt to connect to it on the bench with my application. Some thorough debugging later and I got live data to read properly! We took a video of the software running next to his dev board on top of the car http://www.youtube.com/watch?v=ZeYnkznv ... e=youtu.be
Seeing this, made me even more enthusiastic about FreeEms and pretty much sealed the deal for me using this in my car. So I've decided to continue development of FreeTune, and hopefully have it become a truly useful cross platform datalogging and tuning application.
Official name is now EMStudio, and official website is http://www.emstune.com (emstudio.com was taken damnit)
Windows 32bit installer: (Recommend getting that latest, always at the top)
http://mikesshop.net/EMStudio/
Source code:
http://github.com/malcom2073/emstudio
Website:
http://www.emstune.com
If I haven't gotten to putting the notice in by the time this post gets read, it is, and always will be GPLv2. I may extract the base communications library to be lgpl if I see a need, but at the moment it will remain a core part of the main application.
And as another note, until further notice, master branch is considered unstable, until I have an actual stable code base to go off of, then I'll branch off for development. I expect that's going to be a month or so. Feel free to hit me up here or on irc (mal|lappy) if you're interested in using it, or just give it a shot. I can't guarantee it won't ruin your tune or corrupt your memory until it's considered stable, but if you talk to me first I can probably advise you as to the dos and don'ts. Eg: don't use the "write ram block" button, it's not correctly set up yet!!, course there isn't one yet but that sort of thing.
I started playing around with this about a week ago, fiddling around with just playing back logs with a lot of help from Fred fortunately, which made it go very quickly. He did a bit of explaining about the serial protocol involved, so with that and the OLV source code for value reference I managed to get the ability to listen to live data integrated. The serial code wasn't quite working properly though, and Fred tried it a couple of times for me without success. I happened to be in the Phoenix AZ area, and seank-efi graciously offered to let me stop by and check out his FreeEms setup. Once I got there, he showed me the hardware and let me attempt to connect to it on the bench with my application. Some thorough debugging later and I got live data to read properly! We took a video of the software running next to his dev board on top of the car http://www.youtube.com/watch?v=ZeYnkznv ... e=youtu.be
Seeing this, made me even more enthusiastic about FreeEms and pretty much sealed the deal for me using this in my car. So I've decided to continue development of FreeTune, and hopefully have it become a truly useful cross platform datalogging and tuning application.
Official name is now EMStudio, and official website is http://www.emstune.com (emstudio.com was taken damnit)
Windows 32bit installer: (Recommend getting that latest, always at the top)
http://mikesshop.net/EMStudio/
Source code:
http://github.com/malcom2073/emstudio
Website:
http://www.emstune.com
If I haven't gotten to putting the notice in by the time this post gets read, it is, and always will be GPLv2. I may extract the base communications library to be lgpl if I see a need, but at the moment it will remain a core part of the main application.
And as another note, until further notice, master branch is considered unstable, until I have an actual stable code base to go off of, then I'll branch off for development. I expect that's going to be a month or so. Feel free to hit me up here or on irc (mal|lappy) if you're interested in using it, or just give it a shot. I can't guarantee it won't ruin your tune or corrupt your memory until it's considered stable, but if you talk to me first I can probably advise you as to the dos and don'ts. Eg: don't use the "write ram block" button, it's not correctly set up yet!!, course there isn't one yet but that sort of thing.