rusefi.com

The unstandart teeth pattern causes first tooth to be too long on signal. Conséquences are not clear for me yet.

You may have some trouble with this trigger pattern and RUSEFI because of the abnormal long male tooth then the long gap. I work on a more modern Renault engine that has the same configuration in 60-2. The Renix trigger decoder is probably untested on real engine. Expect to have to mill the long mal...

Trigger non happy problems.

Unable to solve the software problem I finally chose to go for a hardware solution for dual ecu trigger wheel. Renault pattern in the inside of the wheel, 60 - 2 on the outside.

I have a warning "shaft event during trigger misconfigurated".

It's not a problem for me that you have no time now to go further since I have sync now a can continue RUSEFI work.
But this is a nice feature and I'm ready to play beta tester again...

My problem is that when I switch on tunerstudio to trigger gap override I loose sync. When I go back on the console engine sniffer and verbose trigger message displays nothing. Am I doing something wrong?

I gave the trigger gap override a number of trials. All tests failed to synchronise. In first trial, I set the gap "from" and "to" values to 2.00 - 3.00 for first gap and 0.50 - 1.50 for second gap (gap count set to 2). I tried also 0.50 - 1.50 for first gap 2.00 - 3.00 for secon...

"Use only rising edge" seems not to have an effect on detailed trigger messages.

With or without it, it reports 114 events (should be 116 for à 58 teeth wheel)

Thanks for that confirmation. Next : is gapindex=0 always related to a pulse beginning with a rising edge and ending with a falling edge? Is gapindex=1 always related to a pulse beginning with a falling edge and ending with a rising edge? PS : the purpose of all this questions is to get a correct un...

I do not understand the sync process : 2021-11-06_16_49_03_605: EngineState: TRG rpm=268 time=822 eventIndex=114 gapIndex=0: gap=2.517 expected from 2.250 to 3.750 error=No 2021-11-06_16_49_03_605: EngineState: TRG rpm=268 time=822 eventIndex=114 gapIndex=1: gap=1.000 expected from 0.750 to 1.250 e...

Here is verbose sync output file asked above.

I didn't succeed in installing the new software on my old win7 laptop and desktop computer. It seems that SSL certificate problems abort the install. I tried with console and device manager, same results.

Reverted to old firmware. Trigger errors came back.
Congratulations for finding the problem!

Should I reload old firmware to confirm the progress made?

Can you explain the relative position of 5 gaps please ?
I suppose they are the 5 previous gaps of the sync event?
The numbers are ratios?
The gap override count selects how much gaps we look back so the value must be between 0 and 5 ?

Has there been an improvement in trigger decoding since "snapshot_20210416_121019_mre_f4_rusefi" ? I'm unable to reproduce the problem. The trigger decoding is perfect up 5800 RPM (upper limit of my flywheel spinner) with 60-2 decoder ! The only sync losses are the normal ones when sync ca...

I tried to use cool new feature : 2021-10-31 16_05_44-Trigger Gap Override.png but need some help to use on this trigger shape : Trigger logger2.png to start with same parameters than standard 60-2 decoder what are the values to put in the fields ? Here is the .csv file from trigger high speed logge...

First Ruzki thanks for your knowledgeable help, I appreciate to have some interest for this topic. Using the falling edge of the big male tooth is OK but has the drawback this edge is caused by the decay of magnetism along the tooth and not the effect of a well defined edge. Just for sync purpose it...

How can you use the rising edge of the big tooth? When this edge is detected, the sync even has not yet arrived (the long time of the interval can only be treated at the end of the tooth) .

When experimenting on that problem, the use of the "use only rising edge" option never had an influence on the result.

Is this file OK ?

Andrey the 60-2 is just a more modern version of the RENIX 44-2-2 or 66-2-2. All have the big male tooth at the beginning of sync part. So you have solved the problem in the past.

Will post the trigger log as soon as possible.

Due to the sync problems, Rusefi work is stopped. 3 solutions for me : - having a working decoder programed by the devs - having the oem ecu working with a normal 60 - 2 flywheel and cut the Renix flywheel to that spec - add a 60-2 wheel on the crank pulley and a supplementary vr sensor. This has be...

I have some better diagrams but with Renault PnP will be a problem. They have very French (complicated) configuration management habits. Even OEM ECU are not PnP because of all the continuous changes in production. They trust on VIN to find the right part and even then it's not sure you get the righ...

I presume the long tooth is triggering the noise filtering code of trigger_central.cpp :

I have more documentation (my SECMA engine is also mounted in export LOGAN).

Ask what you need.

Bad news after today's tests : I triggered the scope with the "trigger error led" signal to investigate on high speed sync losses. The scope showed repeatedly that the error was thrown on the end of the abnormal first tooth. Crank signal and row vr signal were both absolutely normal. No sp...

Some more tests today.
As Matt predicted once the first anormal tooth is passed sync is OK.
Strangely the sync is not on the male part of the tooth but in the void.
Changing the "use only rising edge" option did nothing.

I have LOGAN wiring diagrams.

What are you interested in ?

PS : this ECU works with the Renault special 60 - 2 trigger wheel...

Do you agree that the timing gun is wrong at high rpm ?

Did you know that problem ?