MembersPage/GintsK/AUDIS (2007-02-28 19:07:03)

AUDIS


08.02.2007

So reality is: my first Genboarded cars will be Audi 20V turbo and n/a.

Here is board modificatons for cramhome signal (crankhome + Hall on camshaft)

R487.jpg

question:

I imitate Audi Trigger using WAW file: 270 pulses on right, 1 pulse on left chanel. 1.0.53 firmware.

Everything works OK until ~6000Rpm. Then starts trigger errors. After 7000 - no sync at all.

It seems thigs goes even worther with new 1.1.11 firmware.

Q: How to sort out what is cause: sound card resolution or something with Genboard?

Disquiet is because 2 of 3 Audis must rev up higher than 7000!

  1. Audi have restricted turbo by rules ~300hp max. I think ~500Nm@~3500 and ~300Hp@~5000
  2. is project with big turbo and target power >500Hp
  3. is n/a engine with deep modificatons for rallying ~250Nm@~5200 ~230hp@~6900
All 5L 20V using InputTrigger/AudiTrigger

here is my waw files:

Audi http://www.vems.hu/files/GintsK/Audi_270&1_4690Rpm.wav

Audi http://www.vems.hu/files/GintsK/Audi_270&1_6840Rpm.wav

60-2 http://www.vems.hu/files/GintsK/60-2.wav

36-1 http://www.vems.hu/files/GintsK/36-1.wav

I use http://www.goldwave.com/ Goldwave sound software. They have evaluation version: free and very sutable: simly loop .waw say 8000 times. And under tools is easy to control playback speed evenly.

Use 96000 samples/sec wavfiles for this 135 tooth pattern (at least if you go high RPM), not 44100 samples/sec.

third question:

Q: C30 cap between primary 135tooth VR input and ground? Is't it too big??

C30.jpg

R56 * C30 = 18k * 1nF = 18 usec

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.

However, if you want to reach 8000 RPM very quickly, like from 4000 .. 8000 in 0.4 sec or faster, than the adaptive hysteresis arming threshold might not be reached and trigger errors might be the result. A 7..8000 RPM revlimit in neutral gear is not a bad idea anyway.

This document:

http://www.vems.hu/wiki/index.php?page=MembersPage%2FTonciLoncar%2FQuestionsAndAnswers beside of all is mentioned:

...if there is noise C30 (which helps shape the input signal) may be broken, try replacing it if you don't have a scope 1nF is will give you a 16kHz filter frequency, you could easily have a bit more here for most applications....

But 16kHz is 7111Rpm for audi 135 teeth Wheel!

++++++++++

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:

9200Rpm.jpg

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!

+++++++++++++++

Update mid 09.02.2007

Another observation:

R484.jpg

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.

---

and this is with normal mid balance and C30 soldered back

R4860.jpg

Both tests 1.0.53 and Audi_270&1_4690Rpm.wav

Keep an eye on MembersPage/MarcellGal/PowerAndTraction, we purchased a 5cyl audi (engine should jump to bay on 2007-03-09) to have all the details hammered out so installation and diagnostics becomes smooth (which it is not yet) on these nice engines.