Having now received the documentation for the MegaJolt serial protocols I can’t see any reason why MegaJolt support can’t be included in the app. To all intents and purposes the MegaJolt follows a similar protocol to that that the various MegaSquirt flavours follow so with the new data layer structure it shouldn’t be more than an evenings work to implement the logging and view functionality.
I may be biting off more than I can chew by adding yet another product to support in the app but it scares me a lot less than the pain I’m about to go through adding MS2 and the two different flavours of MS2-Extra to the app !
The app is back together again following the major changes I ended up making to the data layer.
Had some real problems downgrading to standard MS1 code on my test ECU but eventually got it working after a fashion. The CPU appears to be “locked up” as it’s not responding to inputs or firing any outputs but it is responding to serial commands and returning data as if it were running, very odd but good enough to test the basic functionality against.
The app now runs with MS1 and MS1-Extra and switches between the two automatically so, providing the standard conversion tables (thermfactor, kpafactor, throttlefactor etc…) are being used then you don’t need to load any configuration files.
In response to requests I’ve had a quick look at MegaJolt support but I’ve been unable to find any information regarding the serial protocol it uses so haven’t made any decision either way at the moment.
I’ll add MS2-Extra support next as I can use the ECU out of my competition vehicle to test that with, MS2 B&G support/testing will probably have to wait until later in the week when I’m hoping the MS2 daughter cards I’ve ordered will arrive.
The first versions of the app worked well with MS1-Extra because that happened to be the ECU configuration I had on the bench when I started development. Over time though the design of the data engine has caused some issues when trying to support other firmware versions.
I’ve made a start now on breaking the comms and interpretation part of the app apart to make coping with different transport layers and different firmware versions much simpler in the long term. In the short term the app is in a pretty sorry state but I think a few more evenings work and I’ll have it back together again and running.
As part of this process I’ve looked at leveraging the transport layer into a class of it’s own too. That should go a long way towards resolving the problems of running with a log file as a data source, making the gauges and various data views work with a saved log file. That also allows a “demonstration” mode which can use a log file embedded in the app bundle.
Finally took a break from iPhone development to throw this site up so testers and end users can keep track of how the app is coming along and any future developments.
The MobiSquirt app started in September 2010 when I found myself with some time on my hands and getting more and more fed up with the way the onboard PC in my competition vehicle always seems to go on the blink when I want to check what my engine is doing.
It’s been an uphill struggle at times but so far I’m pleased with the progress and I think it’s only a few weeks before I can start shipping it out to beta testers.