MembersPage/YasecElise (2006-08-27 18:08:18)

The car got an 1.6L 4cyl NA engine because it is believed to better compete in that class, compared to the 1.8L engine.

Location: 3h drive West from Budapest (Sopron, at Austrian border).

Because of illness the project was delayed, but it should be completed

This engine has a special trigger, and the PlugAndPlay harness makes overview and debug hard.


IAC

Simple bipolar stepper - should be straightforward


MembersPage/YasecElise/Ignition


MAP / AlphaN

The engine has a MAP sensor. However, because of very aggressive cams, some loadsites might need to be tuned from TPS (AlphaN).


Trigger - Rover K-series wheel (we refer to it as "elise" trigger)

The engine has camsync, but because of wasted spark, only primary trigger will be used for now.

Is there a chance that something is fundamentally wrong with the trigger ?

Maybe the trigger is HALL ? can you measure ohm between trigger pins ? Both polarity.

Try to record the trigger signal with notebook soundcard.

Try 20k pullup on the trigger signal.

This crankwheel is very smart construction, because it can sync in half revolution (often even earlier!).

We made some modifications to signalgen to generate the wav sound files to test the trigger setup on the table. Firmware code was tested against this.

Lotus_crank_wheel_36-hell_counted_s.jpg

The trigger is supported from 1.0.38 with the following setting (multitooth, no camsync) MAKE SURE YOU TRY THESE TOO, there is a mismatch right at the very first (primary_trigger=00 is not 01 although it might work with both edges if the sensor is HALL for sure):

Take InputTrigger/TriggerLog to check the tooth pulsetrain correctness. (upload the binary too, and possibly the output after formatted with perl binary.pl < terminal.log > terminal.txt )

Because of the extremely fast acceleration (this engine has a special coating and lightweight structure) and the special trigger wheel, some modifications were necessary to the advanced multitooth filter.

Trying 1.0.48 experimental firmware ... http://cell.dyndns.ws/del/v3_firmware_1.0.48.zip


A describtion of the trigger (HU; just to confirm the direction and position seen on the image):\n

Mind1, itt küldöm a képet, immáron dedikált lendkerékkel.
A felsõ holtpont fizikailag ott van, ahol a lendkerék tövében a csap van.
(azaz van 6db felfogató csavar + 1 tájoló csap, na a csap van felül
holtponton)
A jeladó ehez képest lejjebb van, gondoltam azt a bordát jelölöm meg, amit
"lát" a szenzor felsõ holtpontban. Komikus mód ez úgy semmilyen rendszerben
nincs semmivel se.
Utána a forgásirány szerint még kettõ bordát "olvas" a szenzor, és kezdõdik
az elsõ kihagyás.


Udv Yas

Azt hittem soha nem fox feliratkozni.:) Lenne 1 kersem:) Ha lehetne akkor kommentalnad magyarul is a torteneseket? Lassan azert tanulok angolul:)

A_Feri/Saybor:)


Here are the configuration files:

[config]

[tables]

InputTrigger/TriggerLog

Seems very nice, signal and polarity is correct. Analysis of the file, missing teeth:

3,13,2,14, ... pattern seems correct for the wheel.

worst case: (note that the log is very-very short read below! There are likely to be worse cases)

The problem is, that the engine stroke kicks the engine at the 169 position, so the crank accelerates (I guess it has a lightweight flywheel).

Therefore the 1318 (*4 usec) difference is followed by 1869 difference, which is LESS THAN 1.5 * 1328. Normally a missing tooth is 2x normal tooth, and the standard code only consides it missing if >1.5 x

We must use multitooth advanced filter (checking toothrel_ ... on GenBoard/UnderDevelopment/FirmwareChanges), and set the treshold, so 1869 / 1318=1.41 is accepted as missing tooth.


Explanation - N,n,M,m are one hexa digit each:

OLD semantics - before 1.0.40

If the tg (time-gap) between 2 teeth compared to tg_prev (previous time-gap)

NEW semantics - since 1.0.41

If the tg (time-gap) between 2 teeth compared to tg_prev (previous time-gap)

As you see, for the missing-tooth condition, original 1.5+m/8 changed to 1.25+m/8 in http://www.vems.hu/files/Firmware/release/v3_firmware_1.0.41.zip

In our case, it's critical than N is 6 or less. Thresholds for different config:

Apparently it's problematic to define a good threshold for this engine. 1.5 was too high by any means, 1.375 didn't work either (we don't know exactly why, it didn't improve from 1.5).

The best is somewhere between 1.16 and 1.41, my vote is to try

If it really doesn't want to work - note: longer triggerlog needed to decide -maybe (but this is hard, requires nontrivial firmware mod)

Also upload the binary triggerlog (before formatting with binary.pl). Use zip if fileyhingy otherwise does not allow upload.

Analysis of new [log2]

This is a long log, with appr 33 perfect crank rotations.

With improved binary.pl (see http://www.vems.hu/files/MembersPage/YasecElise/trig2_all.zip ) it's easier to spot MISSINGTOOTH for certain threshold (default 1.5, but any other (like 1.31) can be specified on the command line.

The right side is interesting (left side is rabbish), the 3,13,2,14 pattern is also shown:\nÿ2ÿ

This means that the pattern is recognized with the original 1.5 threshold (without the advanced filter). There was one 1.51 in this long log, one 1.56 and the rest are 1.57 or above.

The * 1.41 that we've seen in the short log is not very typical.

It is clearly seen, that 1..2 tooth before the MISSINGTOOTH (after the long, 13 or 14 periods) the engine accelerates appr 10% every tooth. It is so consistent (0.93, 0.81 and 0.92, 0.82, but really very consistent throughout the whole long log!) that makes it suspect there is no combustion taking place AT ALL, we just see the compressed air acting in the cylinder accelerating the engine.

So what's wrong with this setup ?

The original loom (remember than plug-and-play install is always much more problematic than making a new loom) is somewhat brain-dead. The supply to the injectors, fuel-pump, ignition transformers (and ECU) is fed from the starter-motor, instead of the battery. This might mean 1..2V more voltage drop than necessary, which can make a big difference (starting or not), especially with a discharged battery

Engine started after the supply+ was connsected properly, from the battery. The trigger was fine from the start. There is still connection problem at the ignition transformer, and obviously tuning is needed.


The car does not work good again:

Here are the files:

[config]

[tables]

[Megatunelog]

Investigating ... trigger section