Following a sabbatical which included driving around Australia in my Land Rover. I’ve started to tidy up the code base that I was working on for the next release version.
A lot has changed since the last release with new iOS releases, new iOS devices, new beta testing options and Roving Networks being consumed by MicroChip.
The iOS changes have at least resolved a few issues – the problems I was having supporting new versions of iOS without alienating users who wanted to use the app on old devices have been resolved.
The new release will be an iOS 8 app, it will run on iOS 7 and should be OK on iOS 7 but it will not be possible to test on iOS 7.
I will be using Apple’s TestFlight to ship test versions of the app to “beta testers” and with this in mind anyone wanting to test the app will need to apply using the contact form.
Sadly this project has fallen victim to a lack of time and priority compared to all the other things that take up my spare time.
There has been some progress as, yet again, I embarked on another architecture change, this time around the way the logs are created and stored and the way the incoming data is analysed. This is aimed at streamlining the data capture process and, hopefully, this will speed up the entries per second for the logs which have been down on where they should be, particularly on the MS2/MS2-Extra devices.
The iPhone 5 question has been resolved once and for all as Apple will no longer accept apps or updates to apps that don’t support iPhone 5. Anyone still using an iPhone with an iOS version prior to 4.3 will no longer be supported through the app store although I will continue to support older versions in the test version of the app for a while at least.
At the moment I’m not sure when I’ll get any real time to devote to this project but I’m optimistic that in the next couple of months I will at least be able to get the current test version into a state where it can be submitted to the app store.
While the test versions of the app work quite happily on both the iPhone 5 and the iPhone 3G and earlier it seems that the App Store version can’t have that luxury unfortunately. At some point soon I’ll need to make a final decision on how to handle it but my current thinking is that I may create a new version of MobiSquirt on the App store that will support legacy hardware and iOS versions while at the same time allowing the “main” app to take advantage of the latest and greatest iOS developments. Of the current user base of around 800 active users there are 10 users that have devices that don’t support iOS 4.3 and later according to the analytics.
Going down the legacy app route will have the advantage that, when and if I can no longer update the legacy version at least the legacy version will remain on the App Store should an older device need a factory reset or similar and lose the app.
The next App Store release will not support iPhone 5 natively as I want to get the RPM fix out while I pontificate further and see how other developers handle the iPhone 5/iPhone 3G problem.
I’ve been contacted by a few people concerned about the possibility of dropping iPhone 3G and earlier device support. As a result and after some experimentation I’ve found I can, for the time being, support all the existing devices that are supported and also support the new iPhone 5 by using an older compiler.
I’ve been trying to get to the bottom of the problems some people have been experiencing with incorrect RPM readings on MS1Extra. After analysing files supplied by those experiencing the problem and running the configurations up in my test environment I’ve finally got to the bottom of the problem and the latest test version contains a fix. It turned out to be a problem with the way the app was determining the number of cylinders and this was then leading to rogue calculations.
I’ll release this version to the app store after testing is complete.
I’ve got some test logs and configurations from people experiencing odd displays/logging on MS1-Extra versions. In particular this seems to effect the hi res rpm calculation and I currently think it’s related to installations where the spark table isn’t being used. I’m going to load one of the supplied configurations on a spare ECU and see if I can reproduce the problem.
The launch of the iPhone 5 with it’s new processor and screen size has left me in a bit of a quandry. To fully support the iPhone 5 (which I want to do) I’ll need to drop support for the iPhone 3G and iPod Touch gen 2 and earlier and any devices running iOS version prior to iOS 4.3. The stats I have suggest this shouldn’t be a problem BUT if it is a problem for you, please let me know.
Obviously I’m looking to support the iPhone 5’s new screen size in the next release.
I now have a working MegaJolt Lite Jr that has been lent to me for testing and development so I’m beginning work on the connection and logging classes to support it. Not sure yet which versions of MegaJolt it will be compatible with initially but hopefully that will become apparent as development progresses and I work my way through the tech notes.
The outstanding MegaSquirt version support (MS2 B&G code) is also on my list of things to add. I may end up adding them both as part of a single update or add and release each one as a subsequent release. I’m not sure how many users there are of the MS2 firmware but no doubt there will be some.
As always I’m open to any other suggestions and/or bug reports for the current release versions or the test versions. Feedback from users always gives a boost to the development effort, if only because it lets me know I’m not the only one using the app ! Version 1.1 now has over 200 users since it was released so hopefully some of those users are using it for logging and display !
V1.1 of the MobiSquirt app is now available on the App Store. This version contains a number of improvements, new features and bug fixes.
The most obvious changes from v1.0 are…
- This version adds support for logging of MS2-Extra firmware revision ECUs
- The app is now a universal app, running on both iPhone/iPod and iPad devices with new view layouts tailored to the iPad.
- The design of the main gauges views have, in my opinion, been much improved over the last version. Users who prefer the original look can still use that design via a switch on the settings screen.
- An AFR gauge option has been added that uses configurable lookup .ini file that can be customised by the user to suit their lambda sensor. This gauge does not currently work on log playback as the data to reproduce it isn’t available in the log files. This may change in a future version.
- The architecture used to handle the low level communications with your MegaSquirt ECU has undergone a complete rewrite. This improves initial connection establishment speeds and should result in a more stable connection.
You can view/download the app from the App Store here
I’ve submitted v1.1 of the MobiSquirt app to the App Store. Hopefully it will get through the review process and become available within the next couple of weeks.
I’ve run out of devices to test against now. I’m trying to track down a MegaJolt ECU I can test/develop against next and will continue to build up a library of raw data and pages files for my test environment so I can perform regression testing against them.
Anyone using the latest test versions or, when it becomes available, v1.1 or greater on the app store, can contribute raw data and pages file to have their setup included in the regression testing. More details in the user manual troubleshooting page.
As I’ve not received any substantiated error/bug reports for the current test release I’m anticipating submitting this to the app store at the end of this week.
There seems to be a problem with some MS1-Extra installs but I haven’t been able to reproduce it and none of the people reporting the problem have submitted the required files so I’m assuming it’s a local problem with their WiFi setup that they have since resolved.
I’ll be reviewing access to test versions for subsequent releases as the lack of any kind of feedback from “testers” is starting to make testing more difficult rather than easier. This in turn has started delaying development as I’ve ended up chasing bugs based on insufficient information.
If anyone does have a problem with the current test release please let me know after following the steps in the troubleshooting guide
This version is being treated as a release candidate and will be released to the App Store unless any problems are reported. If any problems are encountered please let me know via the forum or email so they can be resolved prior to release.
There are a few changes in this build with a couple of bug fixes. The most obvious change is a UI change with the gauges views having undergone a major overhaul. The new gauge design also allows a new visual indicator when a gauge is in a wanting or alarm condition. The original gauge style can still be used by turning it back on in the settings view.
The new gauge control classes should allow some level of customisation in future releases. I’ll document the files it uses at some point but if anyone has an idea for any gauge designs in the meantime, send them to me and I’ll look at implementing them into a future version.