Changes by last author:
Added:
| 2nd WBO2 tested OK (on bench, but with real LSU4.9 sensor). |
| 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.... |
|
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). |
| * understandable. Ignoring instructions and neglecting VT warnings usually results in a lot of time wasted |
| * (v3/17315) 1X Ecu for BMW S54 Vr+hall+hall (third trigger, Vanos, ETC) + Bridge Outputdriver + 2xWBO2 |
| * (v3/17315) 1X Ecu for BMW S54 Vr+hall+hall (third trigger, Vanos, ETC) + Bridge Outputdriver + 2xWBO2 (+8ch active flyback) |
| Thanks |
|
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) |