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, ...
You are Right! I will do it better..
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
WBO2-s: 2x LSU4.9
| 1st Wbo2: | 2ndWbo2: |
| EC18/7 -> Sensor pin2 pump- | EC18/7-> Sensor pin2 pump- |
| EC18/9 -> Sensor pin1 pump+ | EC18/8-> Sensor pin1 pump+ |
| EC18/13-> Sensor pin6 nernst | EC18/1-> Sensor pin6 nernst |
| EC18/18-> Sensor pin3 heater- | EC18/17->Sensor pin3 heater- |
| Sensor pin4 to 12V+ trought a 5A fuse, separately for both |
2nd WBO2 tested OK (on bench, but with real LSU4.9 sensor).
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.
EC10 pinout
EC10/1- Analog ch0 PPS1
EC10/5- analog ch5 PPS2
EC10/9 5V+ Pedal sensor 5V
EC10/10GND Pedal sensor GND.
EC36/1 TPS IN
TPS sensor GND to common GND, And
E36/29 TPS+ 5V+ (Fused).
EC18/16 Analog ch1 TPS2 sensor.
Bridge Output Driver EC10
EC10/1-2 ETC DC motor
EC10/4-9 12V+ Through a Fuse (10A)
EC10/5-10GND Chassis, were ECU common GND 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 ?
-Of course not :( , but i will send a log from the testrun...
-The problem was, when i started to do that, the controller started to switch on and off.
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.
--That i understend not, i have the same config as in the other ECU, i send that config file. I never did such a stupid thing.
http://www.vems.hu/files/PGfiles/Andybeinditva.zip
Repeated serious communication problem when engine runs - couldn't reproduce so far, running more tests
No the Problems came earlier, i did not try to start the engine, because the ECU switched on and off. The sympthom was that first the ECU communication was over than some seconds later started to switch on and off.
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 ?
-Noname USB-RS232 adapter, i use it for years,
- 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).
-Yes, it is not easy a good adapter to find..
In the time, when i had no comm, ETC was working i just saw no data.
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... (like of v3/17315 is misconfigured, while v3/11317 is not)
No indication of v3/17315 HW problem during any tests, including 2nd WBO2 tests with real LSU4.9 sensor. So far the only explanation of field behavior is misconfiguration (indicated by VT validate warnings also).
My boss was really angry, because it was a lot of time
- understandable. Ignoring instructions and neglecting VT warnings usually results in a lot of time wasted
- 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.
You are right again.
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 ?
-- http://www.vems.hu/files/PGfiles/AndyBilterBergLog.zip
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.
-The main Problem was that the Ecu switched on and off, but with the other ECU not in the same harness.
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,
Originally it was our "log" Ecu, than i modified it. 2nd. WBO2,
3. Trigger.
- 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
-No PWM-ing
- 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 (+8ch active flyback)
- (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
Question: Have you find something with the ECU?
No indication of HW problem during any tests, including 2nd WBO2 tests with real LSU4.9 sensor. So far the only explanation of field behavior is misconfiguration.
- note: when uploading full config from another ECU (different serialnr), than "calibration" data is intentionally NOT changed
- so not ruined, but not fixed either - in case it was somehow misconfigured before (as in the case of v3/17315 indicated by PLENTY of warnings shown by VemsTune validate, like pump_pw_zero=255)