Trigger setup for Audi S4, 5cyl Direct Fire engine
- Primary trigger is VR 60-2 multitooth
- Secondary trigger is a hall sensor, 10-20 Deg Slot fully adjustable (mockup distributor)
- What is the best way to configure this ?
- firmware modification, done in 1.0.25 (ready for testing)
- If we set another_trigger_tooth to 12 (5 per crankrot), and extend the h[2] table to 10 cells, and set dummy values every second cell, also for injectors, divider=02. I guess it would work?
- it would work, but with current stable firmware dwell-time would be limited at high RPM. In short, not a good solution.
- Config http://linkopingsmotorsport.se/config.txt
- make sure you publish actual config (output of mcd) also, not just the intended config. If you mess up global.h (eg. using an old version, forget to update config.mtt file, whatever) this reveals the truth.
- Tables http://linkopingsmotorsport.se/tables.txt
- Datalog: http://linkopingsmotorsport.se/datalog200511141121.xls
- if this is sure not captured with primary_trigger=coil-type config (which results in 24x higher RPM than actual, as in the log), than try http://www.vems.hu/files/Firmware/release/v3_firmware_1.0.25.zip we suspect a syntax thingie in 1.0.24 that could result in coil-type being activated
1.0.25 + MT r027
Config http://linkopingsmotorsport.se/config.txt
Tables http://linkopingsmotorsport.se/tables.txt
Datalog http://linkopingsmotorsport.se/datalog200511281817.xls
Datalog http://linkopingsmotorsport.se/datalog200511281819.xls
Notice drop in RPM, engine never catches up
TODO:
- find cases when RPM drops (trigger error), and find out if anything special happens there (like actuation of a misc output)
Possible causes
- VR waveform shape
- see InputTrigger/RunOut
- can you record (and publish) the measured VR waveform (at idle-RPM is OK), either with
- onboard circuit
- unlikely. But tell about ECM history. Board version, serial Nr, assembled by, ...
- ground
- other
- unlikely
See also