Intense rain for well over a week, and squally winds. Janet said she saw some of the heaviest rain in her experience the day before yesterday. I slept through that, missed it. We have some happy visitors staying in one of Janet’s shepherd huts. They were warned in advance about the utterly vile forthcoming weather and don’t care, they have their books and have done a bit of cooking and been plying my wife with drink. We have a lounge / kitchen / bathroom for guests’ use in a very big shed that we built originally as an equipment store room.
My line #2 has once again developed a case of ‘SNRM hollow curve’ syndrome, which has knocked the highest downstream tones 49-95 down by four bits, from 11 bits to 7, so that’s something like 300k out of 2.7 Mbps, so now down to 2.4 Mbps after a forced resynch. The d/s SNRM started falling at 1800 UTC yesterday evening and continued falling until midnight. In the early hours I discovered the d/s SNRM was only at 0.5 dB, down from 3dB, with a vast error count downstream, so I forced a resync, back up to 3dB d/s SNRM, and all was again well. This hasn’t happened for a while now. Could it be due to intense rain, water getting in somewhere?
I’m talking to A&A about it, yet again. It’s the same old story. Send for OR engineer; he/she does tests, does nothing that ought by rights to be effective, but the problem is always fixed, by magic. And is fixed somehow either before engineer arrives, or during initial procedures, before test results come in. A visit has never failed to fix it. I can’t remember clearly, but I have some vague notion that A&A may have once fixed it remotely, presumably by the effect of firing up whatever remote tests they can initiate.
The CRC count is still really quite bad this afternoon, so I’ve had to raise the d/s target SNRM up to 6dB to fix it. So even more speed lost.