BMW M50 Vanos. v3 srl=13013
m50 VANOS column in [xls] was triplechecked, it is correct for the v3srl=13xxx series. Needs config accordingly
injector channel mapping - vemscfg under review
- http://vems.hu/dave/m50_vanos/base_M50_vanos_1.2.31_srl13xxx_injout_corrected.vemscfg
- filename has non-vanos ? corrected, was a copy/paste error
- Dave, can you check ? confirmed good.
- [configs] (since srl is 13xxx)
- vemscfg to be verified (2016-06-24) against xls: http://vems.hu/download/v3/Motronic88/base_M50_vanos_1.2.31_srl13xxx.vemscfg
- of course calibrating TPS and lower req_fuel OK for big injectors
History. Minor misconfiguration, not understood at first; wrong advice and wrong path was followed
- correct (Vanos, 13xxx) base config was uploaded before sending
- on site, he made minor adjustments (good)
- tuned TPS, lowered req_fuel for big injectors,
- However, prohibit was accidentally changed
- Dave: changing prohitbit can happen accidentally, when scrolling the long dialog (ECU calibrations), default focus is on the first line (which is ibutton prohibit top bit); scrolling with mouse will change it
- happened to me a while ago when running bench tests
[full set of changes since uploaded in factory at start of last benchtest before sending]
Most seem intentional (eg bigger injectors), but prohibit_config unintentional:
-prohibit_config=00
+prohibit_config=80
That change was obviously unintentional.
Unfortunately, it was a bad combination of no thematical page, and latenight (+ bad luck)
- there was no page started, just info here and there: so had to start from negative state
- noone in the main lab at night,
- also, our expert in Netherlands just left a few minutes before
- the prohibit accidental change accidentally made at the site was NOT understood at that time: it was suspected that somehow originally wrong config was uploaded (while originally uploaded config was correct: it was also benchtested with that as confirmed next morning)
- and the wrong base file was linked here, sorry ( Vanos 13xxx is correct for this serial=13013 ).
Ign output see m50 VANOS column in [xls] , this is igndualout compatible (since opposite cyls are driven by neighbors 3,2 ; 6,7; 0,1)
| cyl | ignch |
| 1 | 3 |
| 5 | 0 |
| 3 | 6 |
| 6 | 2 |
| 2 | 1 |
| 4 | 7 |
h[2]=00 30 70 10 20 60 10 70
MOT88/pin27 main relay, activated by MISC1 output (ignch5)
- ignch5 as in the xls (equivalent to EC36/pin12)
- misc1out_channel=52
- configured always active (0-25500 RPM, 0-100% TPS, 0-510kPa MAP, ...)
MOT88/pin7 Vanos actuator activated by ignch4
misc2out_channel=42 (ignch4);
- activated 100 < RPM < 4900 (just ON/OFF vanos, not continuous VANOS ; no feedback loop)
17/06/2016 - Jason
customer states 2 coils aren't operational after loading the file from download/v3/Motronic88...
I opened the brd file in Eagle, grabbed a connector to count pins. mot88 pin 23,24,25,50,51,52 are the coils according to both "M50-vanos-vs-s50b32.xls" and bmw_pinouts.xls (both in the downloads Motronic88 directory. Eagle has Drive07 -> mot88/23,
| BMW mot88 | description | v3_output (Eagle BRD verified) | baseM50vanos <10700 | baseM50vanos 13xxx config |
| 23 | ign cyl 4 | drive07 | drive05 | drive07 |
| 24 | ign cyl 6 | drive02 | drive01 | drive02 |
| 25 | ign cyl 5 | drive00 | drive03 | drive00 |
| 50 | ign cyl 1 | drive03 | drive00 | drive03 |
| 51 | ign cyl 2 | drive01 | drive02 | drive01 |
| 52 | ign cyl 3 | drive06 | drive04 | drive06 |
- drive04 goes to mot88/7 which is vanos solenoid on the m50vanos
- drive05 goes to mot88/27 which is the main relay activation.