Yes - that is indeed what you have (with identical INP & delay values to bald_eagle, so it suggests that DLM's first effort believes you need a fair degree of intervention).
As someone else's line on this forum, you've been given protection level of 16 parity bytes out of every block of 80 - so 20% of the line is being used as extra protection.
And it shows. The "Since Link" stats show near 20,000 FEC, 3 CRC and 1 ES in the 3.5 hours since the line was resynced. The parity protection has worked.
Hopefully the DLM will gradually reduce the interleaving depth over the next few days. I'll post an update in a weeks time, or if I get back on fastpath before then, whichever comes first.
Understand the nuances of setting interleaving is (as you can tell) quite a technical sport. I have no idea if you will see improvements, or if they'll happen in less than a month. But keeping us updated will be good
But be patient!
On the timings:
The guy first arrived at 8:10, but didn't stop, just drove straight back up the road again.
He then came back and parked on next doors driveway as I was leaving the house at 8:20
From here on out I'm relying on what I've been told with regards to timings.
He stayed for maybe 5 minutes (8:25) and then drove off again. At this point I'm assuming he went to the cab to connect the patch cables over to the FTTC cab?
He then came back, don't know what time but I'd imagine it would have been shortly before 8:35?
Don't know what time he left but I'd imagine that he finished the install and turned the modem on at 8:45, right when my attainable rate dropped. The CRC'd then must have started when he connected then in the cab.
Has he knocked something?
That's a bit more back-and-forth to the cabinet than I've seen in a previous "normal/working" installation. Normally the OR guy would attend the cabinet once only, and would go there first, to patch the line through to the FTTC cab.
So perhaps he did knock something, or took your line down in some way (IIRC the width of the red spike was a little wider than a plain resync; so it may have lasted a while), or perhaps he even took out the whole cabinet!
Perhaps your CRC errors started once the neighbour was patched into FTTC, even if he had no modem locally. And then your "attainable" numbers dropped only after the modem was plugged into the line too.