BMW S54
VERY, VERY important: S54 needs 4 PFET outputs (high-side drivers) for the vanos actuators. Any other setup is not supported (driving vanos actuators directly from p259 outputs not supported, and might damage the p259 and cause other indirect problems).
- it's even among the examples [product order page] : "BMW S54 dual-VANOS engine: VR, HALL, HALL + 4 * PFET high-side switches for the 4 hydraulic cam-actuator solenoids "
- despite this, v3/9319 has no 4-PFETs installed.
- v3/9319 (the ECU used according to some logs) is originally VR,HALL
- I assume 3d trigger is homemade, so converted to VR,HALL,HALL
According to our knowledge, for S54, it's enough to just
- "BMW S54 high-side drivers for VANOS: 4-PFET outputs" in the order comment
- set up measurement
- and verify that the configuration+wiring makes the desired cam (this was verified, but please take note of wiringbelow)
- move into the desired direction (this wasn't verified, and very likely to be reversed)
- messing up either will cause the control to not work.
- according to:
We'll see if this engine happens to show something tricky.
Trigger
VR, HALL, HALL
- primary trigger VR 60-2
- sectrig HALL: missing 8-1 (exhaust cam)
- thirdtrig HALL: 6 evenly spaced tooth (intake cam)
Cam actuators
- manually actuated outputs actuate the cam, but
- not configured properly
Cam actuator wiring: FILL IN
Trigger errors
Engine is running well, but trigger error is lit continuously...
- sectrig position measurement ?
- position change not seen even when manually actuated (and cam obviously moving)
- third trig measurement ?
- position change not seen even when manually actuated (and cam obviously moving)
triggerlog ?
Note: [old log files] were not captured with this method, and not suitable to reproduce what is going on.
Capture triggerlog:
- start capture triggerlog (preferrably 115200 baud)
- starting engine (this should be in the log)
- advancing cam (actuating manually)
- engine might stop because of this
- don't forget to name/annotate the log, taking note of what is happening, so it's possible to find (among dozens of other)
- preferrably a vemslog should be captured with similar sequence (it's another attempt, as it's not possible to capture 60-2 triggerlog and vemslog at the same time because of baudrate limitation)