That was odd. Almost as though some cap had been put on the ADSL2+. But the cause, we hope, is history.

Regarding the noise margin, that is set sync time at the cabinet on FTTC, and at the exchange on ADSLx. From that point on the noise over the copper between you and the cabinet on FTTC varies with whatever noise level turns up near enough to the line. On ADSLx it is over the whole line to the exchange.

As noise goes up, the noise margin falls. See this page for a fuller explanation. The difference about SNRM between ADSLx and FTTC is that to stabilise the line one of the methods on ADSLx is to raise the sync-time noise margin to slow down the line, whereas on FTTC a speed cap is put directly on the line sync instead. They call it "banding". (I need to update the page about that). Let's hope the line between you and the cabinet is good. If you need to know more about banding, kitz.co.uk is a good site.

Thanks for that info.

Checking today shows:

Line state: Connected
Connection time: 0 days, 10:06:39
Downstream: 64.73 Mbps
Upstream: 16.36 Mbps

Dropped 10Mb down.

Also, both today and yesterday when I have gotten home from work, it has shown that connection time has reset in the morning. Is this normal for a new connection?

Sort of normal, but not what you wish for.

2.2.1 Dynamic Line Management

Dynamic Line Management (DLM) is employed in GEA-FTTC. DLM constantly manages lines to maintain a target link quality (speed and stability). It does this for as long as the product exists.

At provision, the line is put on �wide open� VDSL2 line profiles allowing the upstream and downstream line speeds to run at the upper limit of the product option selected.

On the first day of operation, DLM will intervene if severe instability is detected. Otherwise, DLM will wait until the day after provision before deciding if it must intervene, provided that the line has been trained up for at least 15 minutes during the preceding day.

(BT SIN 498). By that it means in your case after midnight on Thursday night. The early hours of Friday.

Whereas on ADSLx DLM messes around whenever it decides, on FTTC it is normally some time during the night after it has analysed the line's error statistics.

That size of drop in sync suggests interleaving has been turned on, and on the upstream too which is unusual. Can you see any more stats, or just what you have given us? This sort of thing is ideal:-

# xdslcmd info --show
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 14866 Kbps, Downstream rate = 57908 Kbps
Bearer: 0, Upstream rate = 14989 Kbps, Downstream rate = 59500 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 5.6 5.7
Attn(dB): 19.7 0.0
Pwr(dBm): 13.6 7.4
VDSL2 framing
Bearer 0
MSGc: -6 25
B: 243 237
M: 1 1
T: 0 64
R: 10 16
S: 0.1306 0.5051
L: 15561 4023
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 48 0
TxQueue: 16 0
G.INP Framing: 18 0
G.INP lookback: 16 0
RRC bits: 0 24
Bearer 1
MSGc: 122 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 8.0000 0.0000
L: 32 0
D: 1 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 1794243
OHFErr: 304 389
RS: 1429279640 1515982
RSCorr: 4870768 4434
RSUnCorr: 0 0
Bearer 1
OHF: 116838785 0
OHFErr: 0 0
RS: 934709789 0
RSCorr: 667 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 51370 0
rtx_c: 41571 0
rtx_uc: 49279 0

G.INP Counters
LEFTRS: 479 0
minEFTR: 59478 0
errFreeBits: 3192940116 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 4284342443 0
Data Cells: 237033393 0
Drop Cells: 0
Bit Errors: 0 0

Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0

ES: 76 367
SES: 11 0
UAS: 532 522
AS: 1876766

Bearer 0
INP: 49.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 8.11
OR: 0.01 30.56
AgR: 59560.78 15019.66

Bearer 1
INP: 2.00 0.00
INPRein: 2.00 0.00
delay: 0 0
PER: 16.06 0.01
OR: 63.75 0.01
AgR: 63.75 0.01

Bitswap: 1418653/1418653 41449/41591

#

Do you know what type of FTTC cabinet you are connected to? Huawei or ECI? What modem/router do you have?

I don't appear to have access to stats like that, using the Home Hub 5.

Connection dropping again this morning.. Seems like every 12 hours.

I believe I'm connected to a Huawei cabinet, although my mum said that she seen an open reach guy tinkering with things at the old scabby cabinet the day of migration - when the internet dropped out to be switched. Also there is no white sticker indicating the cabinet number on the new FTTC one?

Currently chatting to BT Chat.

The guy has run some line tests. He believes the wiring at my property is correct but has discovered a fault in the Broadband line. An engineer is being sent out on Monday between 1pm-6pm.

Will update then with information.

It's probably detecting a bridged tap, which would be because you have 2 sets of extension wires coming off of the master socket.

That's awkward, because the fault detected may be a bridge tap, (a minor point by the way - it's called a bridge tap, not a bridged tap). If so the previous two posters who mentioned it may be right. I thought these only occurred before the incoming wires reached the master, not when two extensions are directly connected to the faceplate.

The correct fix is to get a Mk3 filter plate, which simply plugs into the test socket of the master, with the master faceplate plugged into that. You check which pair is going to the socket you wish to use for the router, and transfer it to the pair of unfiltered connectors marked A and B on the Mk3. That is what a engineer install would have involved, though he may also have preferred to upgrade the cable between there and the extension. That raises the question of whether the wires reach to it as they are.

You would still need a filter at the router extension because the signal from the A/B connectors is unfiltered. Your second extension is filtered by the Mk3 so wouldn't need one.

What worries me is that if this is the problem you may be charged for the engineer visit. Were you warned that there could be a charge if it was the house wiring at fault?

If the fault is anywhere before the master then you should be in the clear. Is it certain there are only the two extensions, and there isn't another run from a junction box between the cable reaching the house and the master?

A bridge tap (or bridged tap, you can use either/or) occurs if the cable pair is split off in multiple directions before the modem. Makes no difference whether this is before or after the master socket, as the DSL signal is still going to travel down both the extensions.

The easiest fix would be for the OP to lose one of the extension sockets, then the engineer would crimp the incoming pair through to the extension where the modem is placed, thus rendering the current master socket dead and fitting a new NTE and SSFP where the extension is.

Of course, this is assuming that each of the extension wires is connected through to a single extension socket.

The engineer would do exactly what I suggested unless asked to do something different. That is why the Mk3 and I think the Mk2 have the user-available A/B terminals.

You also forget that the non-router extension is the one where the phone is required. You would disconnect that.

Just in the door from work and can only go on the notes that my mother has quickly jotted down.

The engineer stated there were too many errors in the living room socket (extension), so swapped it around with the Master socket from the lobby - now we have the Master Openreach branded socket in the living room - with the lobby "master" socket and the extension in the kitchen now disconnected.

The engineer also stated he wasn't happy with the wiring from the lobby to the living room (not sure why - anyone have an idea?), but said if any problems persist he may have to come back and change the wiring from the small white box just inside the front door - rewiring from there around the living room to the router. Seems like too much hassle to me.

Also, I asked BT before hand if there would be a charge and they stated no, so we will see!

At the moment everything is running smoothly and will continue to monitor for 10 days.

I have included the stats I can find below, if they are any use to anyone.

1. Product name: BT Home Hub
2. Serial number: +068543+NQ61103283
3. Firmware version: Software version 4.7.5.1.83.8.204.1.11 (Type A) Last updated 17/06/16
4. Board version: BT Hub 5A
5. DSL uptime: 0 days, 00:44:11
6. Data rate: 19999 / 79995
7. Maximum data rate: 27744 / 83791
8. Noise margin: 15.2 / 7.8
9. Line attenuation: 11.3 / 10.2
10. Signal attenuation: 11.4 / 10.2
11. Data sent/received: 0.7 MB / 1.4 MB
12. Broadband username: [email protected]
13. BT Wi-fi: Yes

_____________________________

DSL Line Status

Connection Information

Line state: Connected
Connection time: 0 days, 01:05:37
Downstream: 78.12 Mbps
Upstream: 19.53 Mbps

_____________________________

Throughput speedtest from BTW showing:
Download speed (Mbps) = 74.22
Upload speed (Mbps) = 10.86
Ping Latency (ms) = 42.13

_____________________________

Thanks all for your sharing your knowledge.