Changes by last author:
Added:
|
Update 09.23.2008
Audi is my favorite field. Almost half of my units run on Audis. Last weekend my first VEMS equipped Audi brings Crew to champions!!! in Rally-sprint 4WD n/a class. It was very tight fight: both main pretenders starts this event with equal standings and gives very close SS times. Finally only 3.2s separate both. Here is results: http://autosport.lv/ofiles/5522/docs/results-official/4WD.pdf All my 5cyl Audis run on Auditrigger. One with strange 7A flywheel with Hall signal inverted. Maximal Rpms I ever try is little under 8000. Without errors. Almost all use 1.1.27 firmware. What I like year later: *Still responsive WBO2 control *Boost control strategy with W-gate map (waiting for TPS scaling). Bulletproof strategy!!! *Easy to tune using analyzing software. *true VE map and separate map for lambda. *Idle control close to perfect (looking forward to new IAT compensation) *EGT logging. *LCD for customer diagnostics. No need every time for me with laptop. *soft rev limiter. *What I miss: * limp-home for MAT, CLT sensors. WBO2 damage/open circuit did not switch off ego correction. *CLT range higher than 102C. *relative retard for launch control cause imprecise boost. *support Update 09.05.2007 Put 1.1.23 firmware. Looks it works. Yes without Hall sender is possible to start/drive! I make fine tuning on this old engine. Must say I like to tune VEMS. Configuration in nightmare, tuning is almost pleasure! Old engine produce good power. Somewhat 15-20Hp higher than stock 170Hp. Only modifications is loud exhaust and now restrictive AFM is in the garbage! What I like: *responsiveness of WBO2 closed loop operation. Looks great! *idle control using ignition advance! *VE learning (note below) Cons: *It is almost impossible to find description of some configuration values. So I stay w/o knock control and self learning is a bit on slow side. Renaming of many Megatunes value names would be very welcome. To be value name plain describe what it affect. *no visualization of VE self learning. Every time need to hit Ctrl-F in Megatune. *Idle control try to manage IAC PWM before revs becomes close to idle. I think there must be some Rpm margin for IAC ON. *maximal temperature value is 102C in Megatune and 101C on LCD. Is it bug? Or have I something misconfigurated? Questions: *how to adjust/configure VE learning process? Wideband operation looks much faster and stable allowing learning process act faster. *What is "scaling factors"? *What is "Min. weight for modifying VE Entry"? *What is "Speed of changes"? *Is somewhere description of LCD pages? Looks very promising. But w/o knowledge much of this info is unusable ---- Flyback problem Update: here is my solution for flyback: http://www.vems.hu/wiki/index.php?page=MembersPage%2FGintsK%2FFlybackForLowZ 7A engine use 2 Ohm injectors. ~315ccm. With resistors from factory. My mistake is install without resistors. With flyback wire only it was completely impossible to tune. Injectors as soon as opened stays opened loooong time. Highest lambda possible 0.7 I install flyback board inside. And hope fix this problem completely. In reality things goes better, but stays far from good. This engine is for competition - no need for super-clean idle. Lambda 1.0, rough Ego control. But without flyback (yes my mistake - two fried FETs at redline) control over injectors at idle is far far better. Idling even at lamda 1.10...1.15 !!! |
| Here is board modificatons for cramhome signal (crankhome + Hall on camshaft) |
| Here is board modifications for cramhome signal (crankhome + Hall on camshaft) |
| It seems thigs goes even worther with new 1.1.11 firmware. |
| It seems things goes even worthier with new 1.1.11 firmware. |
| Use 96000 samples/sec wavfiles for this 135 tooth pattern (at least if you go high RPM), not 44100 samples/sec. |
| Use 96000 samples/sec wav files for this 135 tooth pattern (at least if you go high RPM), not 44100 samples/sec. |
| 18 usec is less than 55 usec/2, and even with a 27 usec timeconstant, the signal would reach the LM1815 input, just slightly lower amplitude (still much higher than needed to trigger). So this will not prevent reaching 8000 RPM. |
| 18 usec is less than 55 usec/2, and even with a 27 usec time constant, the signal would reach the LM1815 input, just slightly lower amplitude (still much higher than needed to trigger). So this will not prevent reaching 8000 RPM. |
|
++++++++++
Update early 09.02.2007 Remove c30 and able rev up to 9200 on my bench test on sound. I use Audi_270&1_4690Rpm.wav. Trigger errors is still present: more than 16/sec@7100. It becomes actual little over 6000 and most serious is ~@7000. Strange: @~8000 W counter on LCD became slower. Here is datalog:
Cursor is at 6528 Max peak is 9375 With new 1.1.11 firmware is unable rev up higher than 6500 and counter jumps like messed! This relative success achieved with 1.0.53 and http://www.vems.hu/files/GintsK/Trigger%20test_1.0.53_01.msq msq for new firmware: http://www.vems.hu/files/GintsK/Trigger%20test_1.1.11_01.msq Q: Plese help me with any sugestions! |
| This situation I got using balance buutton on allready "started engine": it works on 135(270)tooth signal only! No trigger errors. But reality - no second trigger signal at all. |
| This situation I got using balance button on already "started engine": it works on 135(270)tooth signal only! No trigger errors. But reality - no second trigger signal at all. |
|
* Synchronisation at cranking is fast enough
* Resynhronization at working engine is fast enough (ingnition switch off/on) |
|
* Synchronization at cranking is fast enough
* Resynchronization at working engine is fast enough (ingnition switch off/on) |
|
+++++++++++++++++ |