Modifying Motronic 2.3.2 ECU hardware and software.

[vwnut8392]

so this is proper?
7868800/(147*2^3) = 7200

what does this mean? (^)

according to the motronic.ws web site if you take the factor and divide it by 8 it creates a short cut to the real world rev limiter value.

7868800/8=983600

than i take the short cut value of 983600 and divide it by 0X9C HEX or 147 DEC. The i get a value of 6691.15. thats pretty far from 7200 RPM.

983600/147=6691.15 RPM.

[andy10v]

2 to the power of 3, 2x2x2=8 iirc.

[andy10v]

Is this correct then?

C/(147x2^3)=7200
C/(147x8)=7200
C/1176=7200
C=1176X7200
C=8467200

8467200/8=1058400

1058400/147=7200

[vwnut8392]

so the conversion factor on the motronic.ws web site for the RS2 is wrong because i get 6691.15RPM?

if i do this the conversion factor comes out to be 1058400
7200*147=1058400

This is using the short cut backwards thats posted on the motronic.ws web site.

[andy10v]

Where did 7868800 come from?

[vwnut8392]

That seems right to me. as for them saying that the automatic rev limiter and manual rev limiter bin files have different rev limiters makes no sense to me because im sitting here staring at them in a hex comparison program and the there is no difference at hex offset 0XA37C. The RS2 on the other hand has the values changed.

4A0907551C manual VS 4A0907551D automatic


4A0907551C manual VS 8A0907551C RS2

[-ice-]

Please think about the logic behind this..

You KNOW the rev limit of 7200. With the equation you can THEREFORE calculate a conversion factor. With this conversion factor you are able to calculate the (real world) rev limit for THE GIVEN hex values.

The conversion factor is the same for auto and manual transmission.

So you have a equation from hex->rev limit an the otherway from rev limit-> hex.


The equation doesn't say devide your result by 8


Bye

[vwnut8392]

Been working on this for the past few days. i started tracing out the fuel/timing board, im far from done but its progress. this is bottom side of the PCB over the top of the PCB. I feel this is something that needed to be done to bring this ECU more into the public eye. cant wait till its done to share it with everyone.

[prj]

What is your goal? I have factory data on the insides.
No, I am not going to post it, but if you have a specific question then ask.

[vwnut8392]

what was your goal for reverse engineering the ECU and figuring out how it works? probably to tune your car like the rest of us wish to do. i just dont believe in being selfish with information, i enjoy to give as much as i can to the community and see how everything evolves. look at all the info that went public for ME7 and how the community has evolved that ECU, alot of useful functions and features have been added which is great! i envy what the DSM and honda community have and i'd like to see open source tuning just like they have.

[prj]

ok, this is going nowhere then as always.
The schematics are under Bosch NDA.

[-ice-]

The schematic is interesting for the analog-inputs. The multiplexer is set by software. So i if you know which Sensor is physically connected to which AIN you know which sensor is actually sampled in the software. This will help to understand the software...

I haven't done this yet. So i you want to trace something, the Analog inputs please

Bye

[vwnut8392]

The schematic is interesting for the analog-inputs. The multiplexer is set by software. So i if you know which Sensor is physically connected to which AIN you know which sensor is actually sampled in the software. This will help to understand the software...

I haven't done this yet. So i you want to trace something, the Analog inputs please

Bye

this is one of the reasons why i am doing what im doing. basically im doing all of the pain in the butt tedious work for everyone and giving it away. once im done with it life should be alot easier for everyone to trace out the ECU.

ok, this is going nowhere then as always.
The schematics are under Bosch NDA.

I could care less what their under in all honestly. if its re-typed and worded a different way than its no longer bocsch's document. i was close to getting them through my friend who owns a local porsche/audi dealership and an RS2 but he died in january sadly. besides theres no law that says i cant create my own diagrams and distribute them freely. there stuff isnt going to be a complete secret forever and im going to make sure of that. once i finish these schematics im going to move on to working with the I/O ports and seeing what they connect to like -ice- said and im going to write up more schematics and documents for that as well and eventually move back to decompiling the software and posting all of my findings for that too. its only a matter of time before this info spreads like wild fire around the audi community and people will be able to tune their cars freely.

Here's an update on the bottom so far, i have to beep a few tracks out with the multimeter and than that side will be done. these are just screen shots, the real pictures are super high resolution, i had a friend who's a professional photographer take the ECU pictures for me.


on another note im making an attempt to retrofit motronic 4.4 from a volvo S70 to an ANN engine. its looking very promising, i have work on a crank trigger setup and a few other sensors. if this all works out than it will be great! this ECU is full open source and the volvo community has been very open about the ECU. i think it will make a great update over stock 2.3.2 ECU. These guys have implemented some pretty cool features to the ECU like map switching and a knock light. i like the work they did on the data logging end of things in relation to doing it in turnerproRT. they have a plugin to use a generic 20.00 VCDS cable in tunerproRT for data logging along with a tunerpro definition thats very complete plus a tunerpro checksum plugin and the best part is its all free unlike the greedy VW/audi community.

Here's a wiki that someone created that relates to tuning and datalogging the motronic 4.4 ECU. http://m44.wikia.com/wiki/M44_Wiki

[prj]

The schematic is interesting for the analog-inputs. The multiplexer is set by software. So i if you know which Sensor is physically connected to which AIN you know which sensor is actually sampled in the software. This will help to understand the software...

I haven't done this yet. So i you want to trace something, the Analog inputs please

Bye

You do not need this information to reverse engineer how sensors are read.
Disassemble the measuring blocks in OBD II diagnostics and you will see how every single value is sampled.
It is not so difficult to do and I did this long before I had any schematics.

[-ice-]

Hi,

is it possible to highlight one of this yellow lines? This would be nice to trace a single connection.
I don't think it's a waste of time. Sure, factory documents are better, but it could be helpful.


Bye