No, sorry. Changes are temporary only, as in they get copied into a small memory area on the chip for these type of changes. The ECU looks in this area for temporary values before using the normal values. If there is a value there, it uses it. If not, it uses programmed values. I suppose you could modify the map as you went, also putting the numbers into a different plave so that when you were finished, you would have all the new numbers, in combination with the original, thus giving you a new map that could be burned to the chip. BUT - now we are talking about something like Nistune, and that's not what I am trying to achieve. Sorry.
Guys, I am still working on this. I just have to get around some limitations/differences between Android and Windows. Rest assured I have not forgotten you.
Wow, doesn't two months fly by! There have been a couple of deviations because of the Android requirements, but the Windows version of the diagnostics layer is 90% there. Because the majority of people will want to see a piece of software that essentially replicates the functionality of ECUTalk, what I now have won't be too much use to them. I will go through what I have and add the extra bits to allow reporting of multiple sensors concurrently. That's the only missing bit. Wen that's done, I will let you all know. The above does not apply to Android. That is still an issue.
any updates on the project? also has anyone ever got Torque pro to work with the consultBT adapter? how is Nikoz? does it have warnings or just reads the data?
I have recently had a bit of a breakthrough, but it was never intended to be a complete solution. I'll post up a picture describing what I mean as it's clear to me that people want more than I was going to deliver.
if you could clarify, it was my understanding you were making the bones of the app which supplied raw data, so a person could then make their own GUI to suit their own needs. or have I got this totally wrong
I replaced the consult usb cable with one of these to connect via BLT to my G 1080 They work very well indeed
Update!! SUCCESS! Those of you that have me as a Facebook friend may have seen a recent update about reading info from these cars. I have now got my own software working that will extract the following: Part Number Coolant Temperature O2 voltage (left and right) Battery voltage MAF voltage Speed Tacho Codes (I haven't yet got IAA voltage, timing and other sensors, but they are minor things to add) Of course it also allows you to reset Codes. No tests at this stage, though this version doesn't need that. All this is running on an Arduino, which means... ============TECHNICAL STUFF TO FOLLOW=========== I can stream data > 115Kbaud (though the ECU is only offering it at 9600), so I don't know if that's a big deal, other than knowing that I can push it out really quickly and then get back to the job of retrieving it The code is currently only about 14Kbytes (with about 30Kb available with the Duemilanove), so there is a bit of room for other stuff like a GUI, responding to controls, etc. This is all running on an Arduino, so it's written in C++. This gives me a bit of flexibility in deciding what the final hardware is to be. ===============NO MORE TECHY STUFF============= Using an Arduino is great news on two fronts. 1. it is small, and 2 it is cheap. It means I can think about other options and not be too concerned about cost (yet). I have to do a bit of tidying up of the code as it isn't in a great state to work from (as a base), but it does everything I mentioned above in a constant loop, and will do so without error after even 24 hours continually. Nobody will run their car for 24 hours continually, so I take that as being stable enough. It still needs a serial consult adapter, but I am looking to build that into the final design. Now to think a bit on packaging options. Choices I have in mind right now include: In dash screen (ala ECUTalk) In cluster screen (maybe instead of those annoying warning lights below the temperature gauge, but that means I will have to report those as well, which is very easy to do) "External" boxed display (ala ECUTalk) Removeable hand-held diagnostics unit :zlove: Touch screen display in drivers-side sun visor Touch screen display mounted onto dash under it's own sun-hood Those last two options need a lot more functionality though. I also have something else in mind that I'm keeping to myself for now, but suffice to say that when complete it will be a game changer for us, and provide many more options regarding disagnostics and monitoring than what we have open to us today. Thanks for keeping interested in this. [TIS]
Would be great if you could sell it to Google so it can be integrated into their glasses - then we can look at any part of our Z and get instant diagnosis. Granted, it will probably just be in the form of saying 'yep, it's rooted', but still, it'll look cool flashing in front of our eyeballs!
awesome project, quite excited by this I hope to install a decent carputer in my Zed and always wanted to have it display OBD data. I think some kind of OBD monitoring and warning system would be nice, perhaps even a voice system like this Or some kind of laser HUD, perhaps similar to this to display important OBD info and GPS data this sounds interesting "Touch screen display mounted onto dash under it's own sun-hood" /me is watching with great interest
