This page is an attempt to start professional install, by clear
- wiring
- setup
- including injectors, and related PWM-ing (config)
- measurements, logs
- no project page created, despite explicite request 2018-01-29
- no logs, no config for review
- VemsTune validate shows PLENTY of warnings. Even basic variables are misconfigured, like WBO2 pump_pw_zero (255! So extremely misconfigured there is no chance of WBO2 working properly)
- been configured correctly when sent out: 102 (also documented on paper)
- so neglecting advice from crew.
- also neglecting hint from VT validate
- what is the plan ?
- this does not rule out some hidden ECU problem, of course (tests show no anomaly so far), but does not help to identify what is going on
- an ETC install should never be done this way.
- One way to proceed could be to open your saved .vemscfg and list all VT warnings, and comment which are intentional, which are accidental, ...
Project: BMW S54B32 with Vanos, ETC, Alpha-N
- Headproting, Race Camshafts, Airbox.
VR, HALL, HALL (Primtrig, Sectrig, Thirdtrig)
New Install
1st. RS232
- EC18/14-15 rx-tx
- RS232-GND (dsub9/pin5) Common GND, EC36 Gnds meetpoint.
2nd WBO2 wiring
- please fill in...
The Problem was the following. I started with the basic wiring first with V3/17315.
So EC36/5-21-22-26-32 GND, E36/25 +12V. Cable length as written in the instruction and as i always did.
I made several V3 installations, newer had similar problem (first was V3/2626).
EC10 pinout (please format !)
EC10/1- Analog ch0 PPS1, EC10/5- analog ch5 PPS2 EC10/9 5V+ Pedal sensor 5V and EC10/10GND Pedal sensor GND.
EC36/1 TPS IN, TPS sensor GND to common GND, And TPS+ 12V+ (Fused). EC18/16 Analog ch1 TPS2 sensor.
Bridge Output Driver, EC10/1-2 ETC DC motor, EC10/4-9 12V+ Through a Fuse (10A), EC10/5-10GND Chassis, were ECU also connected.
EC36/16 P259 ch1 Safety ch. for ETC, relay,switch power supply for Bridge Output Driver.
Than I started to set up the ETC first. Calibrate the Pedal sensors, TPS, and so on.
- any Vemslog showing good transient response ?
WBO2 misconfigured, any WBO2 issues not considered now
eg. pump_pw_zero=255! So extremely misconfigured there is no chance of WBO2 working properly.
So WBO2 related issues not considered.
Repeated serious communication problem when engine runs - couldn't reproduce so far, running more tests
At the beginning, everything was ok. Than i realized that communication is over. Switched off the Ecu , checked the whole wiring again.
Switched on , worked again, carried on calibration,settings than communication over again. Wiring again..., ON, working...than no Communication, OFF, check everything. ON working, than no Comm, OFF.
- type of RS232 adapter ?
- 100 times wiring checked. Weird was, that the time till comm changed was varying (same happens with USB problem, or ground loop, unfortunately USB are usually quite trash).
Than i connected LCD, that i can see something. Comm over, ETC worked, I let the ECU ran, than suddenly LCD turned ON/OFF also background light, and Safety relay for ETC switched also on and off. First slowly than faster and faster, than i switched off the ECU.
- good hint/indication. We measure supply current.
I checked everything 1000 times
- apparently didn't check the most basic VT validate, though
- than i was fed up... A whole day for that Problem, and it is a costumer car.
The car ran with that ECU without problems.
Last try, I connected V3/17315, to see if it works, started the car, ran, than there was no 2nd.WBO2 reading'''. V3/11317 again, 2nd WBO2 works, V3/17315 again, the same problem again, no 2nd.WBO2 reading....
My boss was really angry, because it was a lot of time
- yes, and professional install started at 2018-04-11, despite explicite request on 2018-01-29 to start a page, especially for an ETC install. Without professional method of install, it's almost always a lot of time, and impossible to follow/review.
Car must run with V3/11317 and other we send back.
- No log with 17315, because the car not even ran with 17315.
- but logs are normally captured before starting engine, especially obligatory with ETC, to capture throttle transient behavior
- so you have logs with V3/11317, right ? Can you publish ?
The car works perfect with 11317, we were on testing, Dyno run, Trackday also...
Engine is BMW S54B32, with Vanos controll,ETC,and so on with 400PS. We do not wanted to risk to damage the engine, to carry on trying with 17315.
Funny is if i only power up 17315, only 12V and RS232 than no problem, comm runs.
- this most often happens with RS232 adapter or connection problem, or if RS232 DSUB9/pin5 GND is not connected AT ALL
- yes, with RS232 GND not connected, often comm works when engine is off, but unreliable, and disconnects easily
- also: in VT in communication menu, if i detect ECU, i have receive and tramsmit data also but it says find no ECU.
Gergely Papp
So imperative to compare exact specs of V3/11317 (oid11801 single WBO2) and v3/17315 (oid14067 2 WBO2) 1st
- other than the dual WBO2
- hmm, the specs seems similar indeed... (VR,HALL) 8 IGBT, offboard MAP,
- low-Z active flyback 8ch
- low-Z injectors ? NOT
- or high-Z injectors ?
- configured for PWM-ing ? ECU can be configured for ETC, or for PWM-ing, but NOT at the same time
- if gut-replacement is granted (for no charge), 30V high-Z flyback will be used (not low-Z active flyback, which makes no sense if only used for ETC setups).
Oid14067 has 2 ECUs (but despite explicite request from shop crew, no project page to clarify):
- (v3/17315) 1X Ecu for BMW S54 Vr+hall+hall (third trigger, Vanos, ETC) + Bridge Outputdriver + 2xWBO2
- (v3/17076) 1X Ecu for BMW S62 Vr+hall ( No Vanos, but ETC) + Bridge Outputdriver+ 2xWBO2+Input Multiplexer
Good to verify, but apparently no misunderstanding there