Its aimed towards the average joe, making backyard tuning affordable to everyone.Tre-Cool wrote:Taz, who's your intended target / end user of your app?
I assume with the amount of time your putting into it your not making it freeware.
J2534 tools are getting cheaper so there is no reason why it cant be done on a budget.
What I want to see is essentially remote tuning, where the average joe can read his tune, send it to a tuner for modifications and then upload them. Gone are the days of sending ECUs via mail.
Or better yet, people offering cheap services to turn specific options on/off or helping out their local enthusiasts on cruises/meetups.
Like always though, its free to everyone that helps contribute to it (basically all of pcmhacking.net), which Im hoping to have a first release by end of this week to pop up on here.
I am only looking at the flashing side of it all right now, adding support to as many ECUs as possible with the core functions of identifying valid bins, read/write, identify ECU and security negotiation.
I have hundreds of hours of development behind me in PowerPC now, so feel pretty confident in being able to develop for basically any of the E series ECUs except for the E40 (which can die in hell). I even started building a web service to handle the 5byte seed/key stuff in the newer ecus!
But because I have dealt with all kinds of end users with things I provide now, the application needs to be absolutely bullet proof (Or stupid proof?) to minimise chances of bricking an ECU.
Even little things like comparing the bin files OS to the ECUs OS when doing a cal write and indicate if they are different since it could cause issues. Or reading battery voltage before flashing to verify they are not about to try reprogram with something like 10volts.
*Edit
Also, Im about over developing software for private businesses, I want something for the general public.. its been quite a time!
