Volkswagen Polo 1.2, 3 cylinder SI engine valve timing issue 2012 model year

Hello and thank you for accepting my membership to the forum, this is my first post.

The main reason for registering and posting on this forum is because a number of years ago Scanner Danner produced a video (detailed) explaining how to evaluate igntion timing before and after a timing chain engine repair. I never forgot that. Recently I was asked to put a new timing chain kit on the above engine because the valve timing had jumped. First I did not diagnose that so I pinned up the crankshaft to TDC and removed the blanking plugs in the rear of the cylinder head to gain access to the slots of the camshafts. Both camshafts were out of alignment, which visually appeared about 1 tooth each! Now there is only one camshaft position sensor fitted to the inlet camshaft, so the exhaust camshaft to me anyway can't be assessed without the use of a WPS, hence I used on for this job.

So after pinning up the crankshaft and seeing the camshaft slots out of alignment, and the tools not locating as they should, I knew the timing was incorrect.

Putting the scope on and reading the camshaft, crankshaft and WPS in cylinder waveforms together, I followed the logic of Scanner Danner from his video when he evaluated the ignition timing due to a slipped timing chain.

Here in brief are my conclusions...

Engine before repair...

Using the scope and ruler legend results...

The three waveforms are recorded over 720 degrees minimum. 

Ruler 1 is located at TDC compression from the WPS waveform.
Ruler 2 is located at the camshaft sensor switch off point, i.e. the falling edge. The result from the ruler legend is 15.1 ms
Ruler 2 is then moved to position 3 which becomes ruler 3 at 720 degrees rotation.
The distance between ruler 1 and ruler 3 is 37.34 ms
720 divided by 37.34 = 19.28 degrees per ms

Now ruler 1 records 15.1 ms and ruler 2 at the camshaft switch off point recorded 16.47 ms, this equates to a change of 1.374 ms

If you now multiply 1.374 by 19.28 = 26.50 degrees

If then this is advising that the ignition timing is occurring 26.50 degrees after TDC, which indicates incorrect ignition timing, then after engine repair, and there is no fault with the engine now, how come I get these results for ignition timing...

Doing exactly the same as above but this time with the new scope traces, I gain the following...

13.57 ms, and 5.52 degrees per ms, hence 13.57 x 5.52 = 75 degrees after TDC?

Surely I can't have ignition timing occurring after TDC? 

Your BEFORE capture numbers indicate an RPM of 3198. Were the AFTER capture numbers recorded at the same RPM? If not, the comparison of ignition timing is not valid.

Can you share the waveform files?

If you have a question about ignition timing, it would be best to use the WPS along with an ignition strike, (whether it is Primary, Secondary, or a control signal), from that same cylinder.
Then, you can see the timing of ignition, directly, against the compression peak.
 

I looks like your second capture was take at about 920 RPM. Such a significant difference in RPM's will make comparing Ignition timing like apples to oranges.

I've checked the rpm's and yes they are both different, but I'd of expected that to be so given the engine timing was incorrect in the first capture at idle, and then corrected in the second capture. 
 I'll upload as soon as I can after work tomorrow. Thanks 

I've spoken to the Pico engineers today and we've discussed in some detail what I was trying to achieve and what was occurring with the latest SW download. The engineers agree that the graph and phase rulers when used together are not consistently providing the correct results, hence this afternoon I sent them a file where the crank and cam points of trigger were shown as 60 degrees, but the legend recorded a little over 7 degrees rotation. 

So I'l' conclude this thread by saying that I'm happy to have seen an issue that Pico can now resolve which will help others in their diagnostic investigations. 

Thank you for letting me join your community. When the Pico is fixed and I'm confident, I'll share more experiences with the members.

Thanks