MembersPage/RijaBmwMthree (2017-06-05 08:47:06)

Collecting explicite information on some BMW E46 M3 engine install.

We've guessed way too much already, and been on the wrong path because of misinformation.

PLEASE make measurements, and REPLACE QUESTIONS WITH ANSWERS so you specify every significant aspect of your setup


ECU is v3/10172 - confirmed

Originally vemslog from another ECU: v3/10112 (originally manufactured as HALL/HALL) was provided, so it was suspected that ECU has HALL primtrig input and VR primtrig sensor was actually used

[here] is is the right vemslog file of the V3/10172

OK, so serialnr is corrected, still no explicit information that VR trigger is used (although suspected so, but no verification measurement)

Not specifying (=> guessing) trigger type or falsely specifying serialnr (=>guessing) ECU serialnr (or, in this case both :-) makes support impossible.

Be exact about the sensor type, measurement details so practical advice can be formed and support can be attempted.


P259 outputs

If LM1815 input is good, but no output (logic level signal to processor): it can be suspected that p259 got damaged and LM1815 +5V (shared small regulator for p259 and LM1815) is pulled near GND, preventing LM1815 operation.

Possible causes of p259 damage

If p259 is confirmed to have failed, and grounding is absolutely good (or better), p259 can be removed (ECU can run without p259 chip if GND is good)


Measure, and FILL IN / CORRECT / CONFIRM details

Primary trigger ... VR or HALL ?

Check basic things

If VR:

If HALL trigger (now unlikely):

With HALL sensor you can even measure with DVM, pushing the car a bit in gear5 the signal will change 0/5V or similar.

I hope that helps, we can continue with some useful input.


In anything trigger related the trigger type is important to mention. A working ... sensor is used ?

v3/10112 has HALL/HALL inputs and it will NOT work with VR sensor; the spare ECU might have VR input and that explains why it works.

In VT report v3/10172 is explicitely mentioned, but v3/10112 in the filename was more believable (when discrepancy: usually the filename is correct and human text is errenous)

v3/10112 (the original .vemslog was from, but it seems was misleading info (from oid10258):

1 x ECU VEMS V3

- withSDcard: no

- Service: normal

- secondary_trigger: HALL

- primary_trigger: HALL

- mounting-style: flanged case

- MAP connection: 300 kPa simplenipple

- LCD connection: no

- Knock input channels: 1

- ignition driver: 8

- Flyback: HighZ-only 30V flyback

- EGT input: no

- 1-wire interface: no


Note : 10172 seemed FALSE originally, but now we consider v3/10172 from OID10493 to be the ECU in the setup with trigger problem, which has VR !!!! :

1 x ECU VEMS V3

- 1-wire interface: no

- EGT input: 1

- Flyback: HighZ-only 30V flyback

- ignition driver: 8

- Knock input channels: 2

- LCD connection: no

- MAP connection: 300 kPa simplenipple

- mounting-style: flanged case

- primary_trigger: EC36/27 VR

- secondary_trigger: EC36/13VR