- #GREDDY EMANAGE BLUE JUMPING CONNECTOR TO WORK INSIDE DRIVERS#
- #GREDDY EMANAGE BLUE JUMPING CONNECTOR TO WORK INSIDE SOFTWARE#
- #GREDDY EMANAGE BLUE JUMPING CONNECTOR TO WORK INSIDE PC#
Until I've gotten half decent with programming, I've set out on an endeavor to try and use a Gameboy Color with a flash cartridge and usb port to tinker with at first, then move my project over to the Raspberry.
#GREDDY EMANAGE BLUE JUMPING CONNECTOR TO WORK INSIDE SOFTWARE#
A few changes to my plan as well, instead of actually using the Pi to tune the emanage, I'd like to just have plain statistics/diagnostics readings to begin with, then move on to tuning after the software runs stable.
I don't mean to resurrect this from the dead but i am still very interested in getting this to work, however since finding the protocol between the two devices is (supposedly) going to be the hardest part I'm going to try and tackle that first. SirLagz - its a bit late, but yes its an emanage, emanage blue in fact not ultimate :/
#GREDDY EMANAGE BLUE JUMPING CONNECTOR TO WORK INSIDE PC#
Rurwin - I'm a bit confused by what you posted - do you mean that the ECU talks to the E-Manage using ASAP3 ? or is that what the E-Manage talks to the PC with ? Judging by the first post, it would seem that what we require is software to talk to the E-Manage. That may mean that e-manage supports ASAP3, but then again it may not - there's no mention in the user-manual - and if it does you still need a PC running e-manage - the piggyback unit wont talk the same language.ĪSAP3 was originally a Bosch standard, so it might be available without joining ASAM, but I can't find it in a quick search. And if memory serves me right, GReddy's name has been mentioned.
#GREDDY EMANAGE BLUE JUMPING CONNECTOR TO WORK INSIDE DRIVERS#
One of the drivers I wrote communicates with the software that would be in the place of GReddy's e-manage application. In my day job I write device drivers for engine test systems. Interesting - there may be light at the end of the tunnel, but it's probably a train. But I still don't think realtime operating will come into it unless you actually want the RasPi to become the ECU itself (which I highly doubt is happening now with your laptop as presumably that isn't using a realtime OS either). Will most likely be a lot harder to make work on newer ECUs. However, this is on an older car pre-dating CANBUS and with a pretty basic ECU with a simple 256K EPROM chip. You have the programming software running on the laptop/RasPi/whatever and it has a representation of the lookup tables, you make your changes and when you are ready you click an "upload" button which overwrites the contents of the flash memory with the new values. The ECU is still running the engine, there's no need for the programmer to be real-time at all. The programmer hardware (seems to be called an "emulator" in the trade although all it is really emulating is the EPROM chip) is actually consists of a writeable flash memory that plugs into the socket where the EPROM usually sits in the ECU that holds the various lookup tables for fuel, ignition advance etc… I have some experience of doing this on Bosch Digifant ECUs on 1990s VWs. I think this is both very much possible and quite a good idea. I'm not saying it's not do-able, but it ain't gonna be easy. Good luck getting the specs from the manufacturers. Proprietary and usually non-standard in terms of how they talk down USB (or serial). Then there's the currently available dongles themselves. And if you get it wrong, there's a non-zero chance of blowing up your motor. Once you're past that little hurdle, there's the little matter of the tuning parameters, which, by definition, differ (in terms of settings available, values, minima and maxima) between vehicles. Once you have the protocols down pat, manufacturers implement different sub / supersets of the commands used, and different models of car within the same manufacturer (or even different versions of the same model) can differ as well.
Do you have any more info? The problem is that almost all the standard protocols are proprietary or members-only. I don't know what this piggyback ECU might be or what protocol it might talk. You should not need true real-time performance just to tune the timing and AFR, since that is just communicating with the ECU and setting parameters.
0 kommentar(er)
