Modifying Motronic 2.3.2 ECU hardware and software.

[Sonic]

This thread is locked for now to try and assist the organisation of the thread by Prj. Any problems please drop me a message.

[prj]

If you want to discuss the M2.3.2 ECU, post here:

https://www.s2forum.com/forum/technical/m232-org

If you want to discuss truly aftermarket management, start a thread in this section.

I will browse through the thread and pick up and move some of the information into the M2.3.2 forum.

[bmwman91]

Great idea! It looks like like there is a V2.0 firmware available for it which simulates a bunch of toothed wheels...maybe you can load that into your board? It is super cool that you are emulating the engine...I have always wanted to try that. I might see about picking up a JimStim.

For the most part, I am just a curious hobbyist. I had zero idea of what I was going to get when I busted the plastic package off of S702 lol. As with most things in life, I find that simply being willing to try something new and not being afraid of failure leads to good things. It also happens that I am an engineer in the electronics industry and I have access to all sorts of tools which I could never afford myself (and an employer that is cool with after-hours projects as long as nothing gets damaged)!

[vwnut8392]

Very awesome work BMWman91! i'll have to catch up and read up on your posts. you could be a very dangerous person with the ability to access chips like this especially if you can capture the raw data from them while they are exposed.

For bench testing you could look at the jimstim engine simulator. it may not simulate the BMW crank triggers but it will do just about everything else. i have simulated everything for the M2.3.2 but the crank/cam sensors. i have done TPS, IAT, CLT, 0-1v oxygen sensor input, tested all of the analog inputs tied directly to the processor by either grounding, applying 12v, and 0-5V via jimstim potentiometer to them. i would imagine you could do the same with the BMW ECU especially if its a normal 60-2 crank sensor and 1 window cam sensor than you could even run the ECU from the simulator. check it out.

[Acki]

I'm lost :-D

[Rikki Kitto]

I feel so stupid, great work guys, i think

[vwnut8392]

No fault codes.
But when i put the emulator on the 87c257 chip, i see no tracing.
Here is the log, but the boost is made by manual boost controller.

I noticed the same problem when i tested the speed density software in my car as well. I have an older version of the boost chip with logging that worked, im going to try that code base with the PRJmod speed density motor chip and see if everything works from the boost side. if that does work than it narrows down a problem in the in the boost chip software.
I think i had the MFTS boost cut patch enabled, not sure if it disables the logging output as well because N75 DC and N75 base stay 0 on my testing.

Dumb question, but you do use a latch adapter for the boost eprom? Like boost button.

yes but boost button does not sell them anymore. you have to buy they raw PCB and assemble it yourself. its not very difficult if you have basic soldering skills.

[-ice-]

Dumb question, but you do use a latch adapter for the boost eprom? Like boost button.

[macof]

No fault codes.
But when i put the emulator on the 87c257 chip, i see no tracing.
Here is the log, but the boost is made by manual boost controller.

[prj]

Any fault codes?

[macof]

At first many thanks on the creator of this mod.
I have tested it and almost all is working nice.
But i have problem with boost regulation.
All the time i see only spring pressure and n75 dc is zero, target boost is only 150 kpa. In map is 270 kpa.
Please, can somebody help me what i m doing wrong?

[prj]

I need to check the code, but you don't really need to know much about how the actual logic works. You need to apply some 5v/gnd to some of the pins that you can see on schematic that go to the I/O extender. The autobox stuff such as S_FS is a good candidate among others.
Then you need to log the bitfields in the main ECU, you can hijack the MAF_T/MAF_C in the stream for that as those are 1:1. It is then possible to map what is what where.

I did this a long time ago, but I don't have any notes, because it was a one-off.

[vwnut8392]

The NLS and the map switch don't have to be on analog pins.
There are IIRC 4 free logic level pins, many of them already wired to the Motronic connector, a free PWM output and so on.
Those are realized through the I/O extender.

When I needed more analog inputs in the past I made use of them.

The problem is, some of them are short to ground via 0 ohm resistor and so on, so I used the analog inputs for the coding plug and the MFTS, because those are present in all ECU's and ready to use without making any modifications.

You can always use the Lambda input, but the logic parsing it will have to be rewritten.
I'd say easiest way is to simply use a wideband that is supported by WinLog, such as Zeitronix or 14point7.

i totally agree that your solution is the simplest without a doubt. you say that some of the logic level pins short to ground, well i would think anyone that is using your speed density BIN files would be able to make a small mod to disable the ground on a chosen input because they have to be able to perform the mod to get the MAP sensor signal to the motor chip processor. i understand your solution using the zetronix wideband but i was just looking to expand the capabilities of your setup so it could be used with any wideband controller. what im not sure about is how they I/O extender is accessed for these pins in the code. i get the analog inputs as they are really simple, their just 0xBE 0xinput pin #. super simple on motor chip. I'd like to try and move the map switching pin to the I/O extender on ECU pin 42. im not sure yet what needs changed on the board if anything for that pin but i did take a quick look at the schematic and the ECU i have been cannibalizing and it looks like that doesnt have a 0 ohm resistor on it.

I have been working on a dash and everything for the logging in tunerproRT as well. i know there's such a thing as too much function but i was looking at keeping everything contained into one nice and neat package in tunerpro. I attached a picture of the dash i modified for tuner pro. i made tuner pro XDF's that are friendly with metric and imperial units of measure too along with options to display boost in KPA and PSI plus display the air fuel on AFR or lambda depending on what the end user is comfortable with. im still running my cars on VEMS at the moment but i will be converting my S6 at least back to a motronic now so i can work with your developments.

[prj]

The NLS and the map switch don't have to be on analog pins.
There are IIRC 4 free logic level pins, many of them already wired to the Motronic connector, a free PWM output and so on.
Those are realized through the I/O extender.

When I needed more analog inputs in the past I made use of them.

The problem is, some of them are short to ground via 0 ohm resistor and so on, so I used the analog inputs for the coding plug and the MFTS, because those are present in all ECU's and ready to use without making any modifications.

You can always use the Lambda input, but the logic parsing it will have to be rewritten.
I'd say easiest way is to simply use a wideband that is supported by WinLog, such as Zeitronix or 14point7.

[vwnut8392]

i was looking into adding the 0-5v signal from a wideband controller into the ECU for dimitri's high speed data logging but alas all of the analog inputs on the motor processor are used up by the added features like clutch switch for NLS, the MAP sensor input for speed density and the race fuel map switching tables. i turned to the boost processor and there are 2 analog inputs available but the problem is they are tied to the ground pin on the processor and this trace is under the processor so it is not easily accessible to the average person. one would have to remove the processor, cut the ground trace with a razor blade right at the processor grounding pin than make a separate cut in between processor pins 14 and 18 to separate them.

i was looking at S702 again in the schematic but i dont understand it specifically. it looks like the inputs there are simple switching inputs like when grounded they set a bit in RAM from 0 to 1. my idea was to move the clutch switch and the map switching to these inputs which would free up AN4 and AN6 on the motor processor. i have already conducted a test on the bench using AN5 for my 0-5V wideband input from a jimstim engine simulator and it matches/works perfectly. im sure AN4 or AN6 would work fine for this as well. when i used AN5 i had to enable ECU pin 43 with jumper than remove R663 0 ohm resistor to lift ground off the circuit.

so, does anyone know how the inputs connected to S702 work and if it can be used for the map switching and NLS enable? im looking at adding a 0-5V input for wideband to appear in the data logging and make it universal to all wideband controllers. so for i have confirmed that AEM uego and innovative LC-1 will work with this configuration. maybe dimitri will chime in and give some input on this idea. i attached a picture of the boost processor removed with a pick tool pointing at the trace that disables the last 2 spare analog inputs.

Also since we are sharing now here is a link to my google drive with ECU related documentation. in there you will find the data sheet for the processor, some other misc info about the motronic 2.3.2 function, ECU schematics, high resolution photo's of both motor and boost boards, a diagram of the ADC chip, and in the aftermarket folder there is info on converting to HFM5 MAF sensor and my now obsolete wideband lambda input for data logging conversion.

https://drive.google.com/drive/folders/1Z9R01f0_BnGu6NbW8HIgVtMoxbx-fXxP?usp=sharing