M42club.com - Home of the BMW E30/E36 318i/iS
DISCUSSION => Engine management => Topic started by: Alpine003 on February 12, 2007, 12:24:10 PM
-
I've only found some makeshift Porsche Motronic Editors and some trying to use the Nissan editors to crack the Motronic code while others trying to use romeditor. I tried some Honda editors but that's a no go.
Anyone else have any resources for editors for the M42 out there?
-
You could use winOLS but it's not cheap. You can also use a plain hex editor if you know where the maps are it's not hard to get good results with one.
Are you trying to do anything special?
MarkD
-
You could use winOLS but it's not cheap. You can also use a plain hex editor if you know where the maps are it's not hard to get good results with one.
Are you trying to do anything special?
MarkD
Thanks Mark for the response. I have contemplated on using a plain Hex editor but I feel I would be rolling the dice at that point as I wouldn't be certain if I would be making a mistake on any parameters. I just haven't analyzed enough chips to know for sure which locations the various parameters are at.
I would rather try to edit the stock ECU first rather than go through the hassles of installing MSII for a future turbo project.
-
I messed with an EPROM dump from my stock chip for a while. You can download WinOLS as a 30 day demo version or something. I was using it for a month. Other projects called though, and honestly, it is a fair amount of work just figuring out where things are on the chip. Once you find maps and actually learn what parameters are what (and how they are scaled), you need to find all the related checksums and modify them according to map changes. The M42 chip is an extra pain...it has all the program code on it, not just maps. The Siemens 80C535 microprocessor in the Motronic only executes the code on the external EPROM module (no onboard program memory), so you have EVERYTHING to wade through. I even tried disassembling the code, but it was a cluttered mess.
In the end, editing the stock chip is probably going to take as long or longer than doing a Megasquirt. Had my first car not been my DD when I was doing MS on it, I probably could have had it all done in a month. Back then, I knew next to nothing of electronics beyond basic analog electronic principles (resistors, caps, inductors, etc). Good luck on this!
-
Yeah, I knew it was going to be a big pain to sift through all the info.
I will try WinOLS and see what I come up with. Were you able to load .bin files directly to WinOLS? I know some programs work off proprietary files.
I know Jim Conforti had mentioned coming out with an editor at one point but I don't think that ever materialized as that would kill his business.
-
Haha, aaah yes, the infamous Conforti DME-Ed. I think he is/did come out with one, but it lacked support for the older DME's that his initial version included. I doubt it would have killed his business. Unless you want to drop $1000+ on dyno testing, you still are better off trusting his tuning by buying his chips. Anyone who is actually capable of tuning their own maps would not buy a chip, but those sorts of folks are a severe minority.
I think I was able to stick the BIN files right in. I am not gonna lie...it is not easy to pick out the maps (for me anyway). There is a lot of stuff in there that looks like what you'd imagine a map looks like, but it is not. They are in stack format...byte one is like the input parameter, second is the number of cells, then like the last byte represents the highest RPM/(some constant). Each byte before the last one is a table cell...and it is some offset from the max RPM subtracted from it, over and over. You get the idea...a little complicated. I had a thread somewhere in here months and months ago that actually had in detail which bit is which.
-
I may help with maps locations, but need a bit of time and exacly code of your ecu...