Anybody see this? Looks pretty bad ass.
I was doing that the other day, the Moates Ostrich is wicked .
Making good progress on my XDF, I've managed to compact all the ignition maps into one large one, so it's easier to tune. Gotta sort out which fuel maps to use to do the same thing on the fuel side, it'll make it waaaaaay easier to tune for boost.
Its about time people start using this now wonderful piece of equipment. I predict that very soon people will be putting the OBD1 harnesses back in the cars they just took them out of for the same reasons the honda guys do the OBD1 conversions.
Seems to me that folks are scared of tuning their own OBD1 ecus...
As a teaser, the Neuspeed P-chip for the ABA costs $110 from NS, and all they do is alter the part-throttle ignition maps. That's a $20 mod on a $0.50 chip...
A chip burner is $85, and the software is free..
Probably why the nospeed chips suck. I have a autotech q-chip in mine, and I can tell you for sure they messed with the fuel. Runs pig rich on cold starts in the winter, and with a few quick stabs of the gas it will pump black smoke.
Any chance you will ever mess with obd2? I wish I knew more about dissecting the actual code, we could do some interesting things like anti lag like the dsm people or some form of launch control.
John finally put his chip in ecu, now he has to start it.
Procedure for tuner pro is
Load file to buffer
Program buffer to chip
Is this correct?
Yep, although I usually use a program called Emutility from Moates (free) to upload/download to the emulator. The latest version of TunerproRTv5 is a bit buggy, although it 'seems' to be ok when doing 32kb files. I had some issues doing OBD1 64kb files, and had to play with the settings for a while before it worked out.
I would like to tune OBD1 by emulation or whatever means.
What is a good place to start learning about the data structures and which addresses represent which info, or is that all parsed by tunerpro/other?
I am starting from nowhere here.
Also anybody know what the extra chip tucked under the C2 chip carrier is on OBD1 chip tunes?
I forgot to record that chip's part number. If no one knows I guess I'll have to go back in.
That said there is enough info in the link above to tune your car. All you need to do is play around with the free software untill your comfortable with it and learn the layout from the links I posted. Its not that hard. If someone is actually interested in this then they can ask me specific questions here. I will also archive it elsewhere to make sure this stays public information.
i rescale the rpm axis and the load axis to give more resolution example stock vr6 maps rpm is around
6500 ..i rev to 7500rpm ....so with a stock maps when im 7500rpm the ecu would calculate from the last
used bin at 6500rpm ...you can still get a good tune with stock axis
Just bought this:
Seems to be a great Motronic tuning software package, can't wait to try it out .
The previous version of the software required the user to insert the hex addresses, it did the rest of the calcs. It apparently gives you what you put in, which saves a lot of farting around with tunerpro to set up the axis' (although I've already done that). I've identified most of the 'main' maps, and traced them on a buddy's car, just don't have steady MkIII access right now to experiment .
I'll post up when I get the software, for sure. The owner is out of town right now, so on sunday he's going to send me the download package. Can't wait to play with it .
Tunerpro is still going to be used with my Ostrich, obviously, since the tracing works great. The DME Editor will probably end up being a secondary tool to help sort out the mapping.
I'm down with that .Originally Posted by TIGninja
I have a 'raw' XDF of all 186 M2.9 maps, if you'd like to see it. I think I sent it over before, but there might have been some errors in that version.
I'd love to know exactly which maps are the main, low, mid, WOT maps. Ignition is fairly easy to sort, since there is only one descriptor used, but the fueling confuses me with multiple maps using different descriptors .
If you guys want some help just ask.
Got the software, so far it seems quite interesting. It's necessary to input the addresses of each map, but the program deciphers the header on it's own, making axis population a breeze (if you don't have WinOLS). You have to populate the descriptor lookup table, with the characters and the offsets/conversions, as well as sort out the checksum calculation, but it's fairly simple with the early motronics. There is no need to program in the size of the x-y axis', since it interprets the header automatically, which I like . Tell it to look for a 3D table at XXXX, and it does the rest.
Ah ha, the good stuff .
I just registered, I'm following that thread, DEFINITELY!