Project: BMW S54B32 with Vanos, ETC, Alpha-N
- Headproting, Race Camshafts, Airbox.
VR, HALL, HALL (Primtrig, Sectrig, Thirdtrig)
New Install
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).
1st. RS232 EC18/14-15 rx-tx, RS232-GND (dsub-pin5) Common GND, EC36 Gnds meetpoint.
EC10 pinout
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.
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. 100 times wiring checked. Weird was, that the time till comm hanged was varying.
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.
I checked everything 1000 times, than i was fed up... A whole day for that Problem, and it is a costumer car.
Than i connected our V3/11317, and everything worked fine, I made the calibrations,setups, the whole wiring.
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, and we have fix race appointments, so he sad we have no time to find out what is that, so car must run with V3/11317 and other we send back. That`s why i have no log, because the car not even ran with 17315.
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. What i also saw, 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) and v3/17315 (oid14067) 1st
- ...
- hmm, the specs seems similar indeed... (VR,HALL) 8 IGBT, offboard MAP,
- low-Z flyback (what is the reason behind this ? Is flyback connected ?
- low-Z injectors ?
- or high-Z injectors ? Is there some diode in the harness, like 18V or 30V transient diode (to make high-Z inj closing faster ?)