What is the highest firmware version anyone is running on a 5 cyl Audi?
Im running 1.2.9 on mine. Im using 60-2 trigger though.
Any particular reason why asking?
Hi, yes, I'm having trouble with an S2 running 1.1.81 with misfires above a bout 4500rpm, under vacuum and boost, and I can't figure out why. Nothing I do to the timing or fuel seems to sort it out. I'm using new coils (034 motorsport) ht leads, and plugs. 3ms on the charge time but no change. Thought maybe it was firmware.
What kind of misfires?
"034" coils are noisy. May be you have some triggering issues are caused by this noise?
more like backfiring. How do I check for noise issues?
First check your datalog for trigger error presence.
I had two problematic cases on those coils. Capacitor at each coil supply to ground solved the problem.
IMHO coils are overrated. It gives high energy of spark. But in prolonged in time. What we need for high boosted applications is high energy right at beginning of spark event.
What size capacitor should I use?
first you want to view your log to see if that is your problem and if infact it is trigger error due to noise
I used the "record trigger log" button but not sure how to read it. I did see though that the blue dot in the VE map table starts tk jump between 4500 and 5500 rpm when it happens. So I thi nk I do have issues. What size cap should I use or how do I calc it?
No no, you have to review .vemslog file for "trigger error" flag presence at backfiring moment. Open the log in VT and hit Shift+8. It is possible to configure what flags are showed.
@GintsK, I am the owner of this car that Bambi is struggling with :-[
I just had a look at a .vemslog file I recorded a while ago and I now see that there is a Trigger Error when rpm goes over 4000. The log is at https://dl.dropbox.com/u/38296055/v3.3_n002006-2012.08.13-20.28.09.vemslog
Yes, you have really serious problems with triggering!
It can be noise issues, it can be something with starter gear.
Regarding caps. I used 4.7uF 63V polymer ones. It is not so strict.
Ford do the same for ages.
Quote from: GintsK on December 21, 2012, 10:07:40 AM
Yes, you have really serious problems with triggering!
It can be noise issues, it can be something with starter gear.
Regarding caps. I used 4.7uF 63V polymer ones. It is not so strict.
Ford do the same for ages.
Thanks GintsK! - we will get caps and see if it helps. Worse case we can just go back to stock coils but since I spent the money on the 034 coils it would be better to get it to work.
Update!
Bambi installed the caps in the 12v lines to the coils and the trigger errors are still there >:(
Then I thought the one thing that also changed was I had a new fly wheel built.
Here are 2 trigger logs.
https://dl.dropbox.com/u/38296055/v3.3_n002006-2012-12-26-16.00.49.triggerlog
https://dl.dropbox.com/u/38296055/v3.3_n002006-2012-12-26-16.00.13.triggerlog
Can anybody help?
trigger logs are inappropriate, they are ok only for low rpm :)
but I think this is your problem: Then I thought the one thing that also changed was I had a new fly wheel built. too small flywheel pin or something. caps on coils don't cure this problem, they only help later to get less noisy signal when you fix that flywheel problem.
Your files is almost useless. We can guess from some regular log fragments that you have problems with 135-tooth sensing. Note regular missing signals after camsync. 96msec cam period - around 1250rpms. Just guess.
It is possible to get more usable trigger logs with highest communications baud rate.
Anyway first sign of errors is trigger error flag presence in .vemslog.
If you have this, most efficient tool for further diagnostics is oscilloscope.
Before deeper diagnostics you can try to move sesnor together with little modified bracket to rear. Sometimes it helps.
Gints
Thanks Guys!
I would like to confirm that the new flywheel and its timing pin is really the problem before taking out the gearbox which is quite a job.
I will try and get higher baud triggerlog tonight. Otherwise I will have a look at it on an oscilloscope.
Quote from: Gandalf on December 27, 2012, 12:19:10 PM
Thanks Guys!
I would like to confirm that the new flywheel and its timing pin is really the problem before taking out the gearbox which is quite a job.
I will try and get higher baud triggerlog tonight. Otherwise I will have a look at it on an oscilloscope.
log it on idle. + you dont need to remove gearbox, remove starter and then you can access it.
Update!
I drove the car and only got a trigger error at 6500 rpm. So the caps seemed to have helped a lot. The log file - Log (https://dl.dropbox.com/u/38296055/v3.3_n002006-2012.12.28-10.51.09.vemslog)
I also ran a trigger log @ 115k baud at idle - Triggerlog (https://dl.dropbox.com/u/38296055/v3.3_n002006-2012-12-28-11.00.59.triggerlog)
Do I need to go more aggressive on the capacitors? In the past the trigger errors appeared at 4000 rpm and now it seems clean to 6500 rpm?
Can you scope the actual trigger input signal to see what it looks like?
Quote from: gunni on December 28, 2012, 08:17:14 PM
Can you scope the actual trigger input signal to see what it looks like?
Bambi has access to a oscilloscope but the is 4x4ing in Lesotho currently. I will get the car through to him when he is back so we can check on the oscilloscope.
What about the 1.2.10? Is it in regards to Audi Trigger good as supposedly is the 1.2.2?
Quote from: billman on February 23, 2013, 07:28:45 PM
What about the 1.2.10? Is it in regards to Audi Trigger good as supposedly is the 1.2.2?
yes it's ok, today tried 1.2.11 no problems.
Does anyone else has issues with Audi Divby9 in 1.2.10?
When choosing the Divby9 settings from the dropdown menu on Primary Trigger settings something occurs I think and the config goes bad.
I did a manual Divby9 Setup and it works without issues. But the following occur: With 1.1.96 TDC before trigger was 59 (Divby3). with 1.2.10 and Divby3 I had to set it at 56 and now with Divby9 I had to set it at 53! Why is that?