T4700

Season is over now... had no time to do further testing. Engine will be converted from Auditrigger to 60-2 this winter, so no more investigations necessary. Thanks again for fast support here.

Yesterday I reversed the polarity on the crank sensor and aligned the trigger cal. The significant 10 deg jump to the right is gone now. When I rev up, I can see very very short (short like a flash) jumps of the mark to approx. 20 deg after TDC. Except that, the mark is rock stable without a shift. Only short blips to the right. I'm not sure if they are really present or if there is something wrong with the strobe signal. Will test this again with my old ECU. I can confirm, that the arming voltage has no influence to anything, I can change the values from 1 to 3 V without anny difference and without any trigger errors. I only reved up to 4000 rpm... will test the full range soon - didnt want to provoke my neighbours yesterday ;-)

I'm wondering about the LINK help file. They say Arming Voltage should be half of the peak voltage. If I follow this, arming voltage would be 10V

I can see the cambelt stretch on Trigger mark, when reving the engine up. The Trigger mark is shifting smooth a very small amount around the TDC mark. Very very small and smooth. But when you go over 3000rpm it is jumping to the yellow mark in one step. If you hold the RPM at the angular point, the mark is jumping forward and backward between those two points. No, I dont tried to switch polarity or edge. Will try soon. I heard of some 135th cars, running LINK without issues - I hope this will be possible for me too. Seems to be the same issue member "150" described in the top of this topic

Was not able to take a video. Above 3000 UPM the white mark on the damper is jumping to the right (yellow) Changing aming voltage up and down or changing delay does not change anything.

Yes - will do this... OT (oberer Totpunkt) = TDC UT (unterer Totpunkt) = BDC

Thanks for fast reply. I will update software and firmware. (I'm running 5.5.7.3059/3062/FW1.9R6) But I guess, thats not the reason for my trigger issue. I will also take a video of the behaviour.

After a long break, I got back to my LINK Thunder. The car was firing up with the first keyturn and has stable idle. After warming up, I was calibrating the trigger with a timing light. The OT trigger Offset is -70 deg. Reference timing was set to 0 deg. Timing is stable until 3000 rpm. Above that, trigger starts to jump significant degrees after OT. Trigger 1 Type Reluctor Trigger 1 Filtering Level 1 (LOW) Trigger 1 Aiming Threshold 0 - 0.5 1000- 1 2000- 1.5 3000- 1.5 4000- 0.5 5000- 0.2 6000- 0.2 Trigger 2 Type Optical/Hall Trigger 2 Filtering Level 4 (High) Trigger 2 Pullup ON Trigger 2 Edge Falling Sync Mode Cam Pulse 1 x Any Ideas? Wiring and Polarity are checked. Picture below are on idle.

So finally my good old 5 cylinder 20VT is running with my new Link Thunder. OT Trigger is indeed around -70. Maybe ist because of a shift between hall window on cam sprocket and the flywheel pin. After doing lots of study and workbench pre-mapping the Link ECU, the engine started up with the first keyturn after 3 seconds. For now, I am happy with the first 20min of engine runtime :-)

I use Retard Absolute. If I type in a value it will allways be -1 lower. -45 results in -44, -20 results in -19 and so on. I also tested percentage. If I type in 12 it will be 12, if I type in 11 it will be also 12. So I think this is not an issue like you said. But the other two modes have the known "allways -1 issue"

I tested the newest LINK Software (3012) I wrote results into my postings above. Issues still present -> max 500 kPa in Lambda, Engine Protection and IC Spray. New issue in ALS Ignition Table. Now you type -45 and get -44. This was not an issue before software update. best regards

Ok I see the link to the bottom of the page is no longer present and there is a third new version of the V5.5.7.3012 Software on the top (first was 42,2, second 57,2 and now 58,3 MB) So I will install the new version on the top of the download page now.

opps... nasty Still no 3012 Firmware Updater shows V5.5.7 Firmware 5.5.7.2969

But the problems are still present in this version...

Hi Scott, perfect - thanks