Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: colly05 on May 04, 2013, 08:45:27 PM
-
had fibre now for few weeks and got a hg612 unlocked and on firmware A2pv6C030b.d22g
# xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 15563 Kbps, Downstream rate = 48340 Kbps
Path: 0, Upstream rate = 9995 Kbps, Downstream rate = 39997 Kbps
Discovery Phase (Initial) Band Plan
US: (0,95) (880,1195) (1984,2771)
DS: (32,859) (1216,1959) (2792,4083)
Medley Phase (Final) Band Plan
US: (0,95) (880,1195) (1984,2771)
DS: (32,859) (1216,1959) (2792,4083)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 15563 kbps 48340 kbps
Actual Aggregate Tx Power: 6.2 dBm 11.4 dBm
================================================== ==========================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 2.9 32.3 48.7 N/A 16.2 40.4 61.8
Signal Attenuation(dB): 2.9 32.2 48.5 N/A 16.2 40.4 61.8
SNR Margin(dB): 9.3 9.2 10.2 N/A 9.9 9.9 0.0
TX Power(dBm): -3.9 -10.5 5.6 N/A 9.5 7.3 -128.0
#
# xdslcmd info --show
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 15576 Kbps, Downstream rate = 48340 Kbps
Path: 0, Upstream rate = 9995 Kbps, Downstream rate = 39997 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 9.9 9.9
Attn(dB): 0.0 0.0
Pwr(dBm): 11.4 6.2
VDSL2 framing
Path 0
B: 239 235
M: 1 1
T: 64 7
R: 0 16
S: 0.1910 0.7508
L: 10054 2717
D: 1 1
I: 240 255
N: 240 255
Counters
Path 0
OHF: 1445506 375098
OHFErr: 76 0
RS: 0 2151740
RSCorr: 0 0
RSUnCorr: 0 0
Path 0
HEC: 209 0
OCD: 0 0
LCD: 0 0
Total Cells: 340778605 0
Data Cells: 3696494 0
Drop Cells: 0
Bit Errors: 0 0
ES: 50 0
SES: 0 0
UAS: 23 23
AS: 4436
Path 0
INP: 0.00 0.00
PER: 3.05 11.82
delay: 0.00 0.00
OR: 62.83 152.21
Bitswap: 305 0
what info can be seen by this and any tweaks modem sync speeds are 39997 down 9995 up
thanks
-
Welcome to the Kitz forum.
From the information you have posted, I can see that you are on a 40/10 Mbps package and are essentially obtaining the maximum sync speed that the line can provide. Which is good. :)
For a more detailed statement on your line's performance, I think it is best to wait for the Eagle (a.k.a. Baldy Bird) to cast his eye over the data. ;)
-
contacted plusnet order gone in for 80/20 as i am on the Unlimited Fibre Broadband.
"I can confirm that you were being supplied on a 40/10 service. Therefore I have placed an order to move you onto the 80/20 system.
This will take around 24 hours to complete and your speeds should increase within the next 10 working days."
also trying the new firmware which gives me a higher Attainable rate (kbit/s) 50112 down and 13385 up but it does look like i getting CRC errors should i go back tot he earlier firmware
-
"I can confirm that you were being supplied on a 40/10 service. Therefore I have placed an order to move you onto the 80/20 system.
This will take around 24 hours to complete and your speeds should increase within the next 10 working days."
So PlusNet still have not fixed their systems. :doh: D'oh!.
also trying the new firmware which gives me a higher Attainable rate (kbit/s) 50112 down and 13385 up but it does look like i getting CRC errors should i go back tot he earlier firmware
Having upgraded to the newer image, I would recommend that you now leave it be for the next 10 - 14 days. Wait for PlusNet to put you onto the 80/20 Mbps service and then see how it behaves, once the line has stabilised.
You might like to deploy a copy of Bald_Eagle1's utility software and start collecting line performance statistics . . .
Now where is that Eagle? Perhaps performing a penance, under the watchful eye of SHMBO?
-
thanks for the reply ill leave it as it is looking forward to the little speed boost
ill try the software and monitor it and let you know
thanks
-
Hi colly05 & welcome to the Kitz forum.
There are very few tweaks available to end users on FTTC/VDSL2 connections as almost everything is controlled by BT's DLM.
The only tweak that I am aware of via the HG612 modem is QoS.
You may see a slight increase in upload speed via this one (once you are transferred to the 80/20 service):-
In the modem's GUI, click Advanced, QoS & untick the Enable box if it's ticked by default, then click the Apply button.
I think that may cause a resync for the change to become effective.
It's pointless until you are transferred to the 80/20 service though as your connection's sync speeds are currently capped at 40/10.
I'd agree with burakkucat's advice to leave the connection alone for a couple of weeks, using the 24/7 monitoring program(s) to view any changes in performance etc.
They can be freely downloaded here:-
http://www.freewarefiles.com/HG612-Modem-Stats_program_84567.html
These should now be used in preference to the older batch file scripts that are linked to in the HG612 Hacking blog.
From the stats you posted we can see the following:-
Retrain Reason: 0 which suggests you either rebooted the modem via its GUI or power cycled it.
Typical DLM initiated resyncs tend to have Retrain Reason 2.
You are connected to an ECI DSLAM as shown by these Discovery Phase band plans:-
Discovery Phase (Initial) Band Plan
US: (0,95) (880,1195) (1984,2771)
DS: (32,859) (1216,1959) (2792,4083)
You do currently have some spare SNRM which does confirm that you should see a sync speed boost when the services are switched:-
SNR Margin(dB): 9.3 9.2 10.2 N/A 9.9 9.9 0.0
Your connection is currently operating on Fastpath for both DS & US (D: 1 1) i.e. DLM hasn't yet decided to apply Interleaving, Impulse Noise Protection (INP) or delay in order to favour stability over speed.
We have, however, seen these applied on some connections that use a HG612 modem connected to an ECI DSLAM after a few days.
Once you are switched to the 80/20 service, the higher sync speeds are likely to induce an increase in various errors & sync at the target 6dB SNRM, in which case DLM may decide tho apply Interleaving etc. - probably at a reasonably low depth.
Contining to monitor 24/7 for a couple of weeks should highlight any such changes & any patterns to error counts etc..
Your connection hadn't been up for long when you grabbed the stats that you posted (AS: 4436) i.e. 4436 seconds or approximately 1.23 hours, so it's a little hard to comment on various error counts.
Note: The error counts as displayed in the modem's GUI are mixed up & not to be relied upon.
-
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 2
Max: Upstream rate = 12711 Kbps, Downstream rate = 50884 Kbps
Path: 0, Upstream rate = 12523 Kbps, Downstream rate = 50062 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.3 6.2
Attn(dB): 0.0 0.0
Pwr(dBm): 11.9 6.9
VDSL2 framing
Path 0
B: 239 238
M: 1 1
T: 64 32
R: 0 16
S: 0.1526 0.6073
L: 12584 3359
D: 1 1
I: 240 255
N: 240 255
Counters
Path 0
OHF: 7649145 202569
OHFErr: 832 0
RS: 0 3196440
RSCorr: 0 1
RSUnCorr: 0 0
Path 0
HEC: 1249 0
OCD: 55 0
LCD: 55 0
Total Cells: 1803625602 0
Data Cells: 24775665 0
Drop Cells: 0
Bit Errors: 0 0
ES: 1730 3
SES: 9 0
UAS: 35 35
AS: 18746
Path 0
INP: 0.00 0.00
PER: 2.44 9.71
delay: 0.00 0.00
OR: 78.65 21.40
Bitswap: 4601 21
Total time = 1 days 19 hours 50 min 31 sec
FEC: 67992 0
CRC: 5347 0
ES: 1730 3
SES: 9 0
UAS: 35 35
LOS: 7 0
LOF: 6 0
Latest 15 minutes time = 5 min 31 sec
FEC: 0 0
CRC: 8 0
ES: 6 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 0 0
CRC: 21 0
ES: 18 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 19 hours 50 min 31 sec
FEC: 7643 0
CRC: 3666 0
ES: 618 0
SES: 8 0
UAS: 17 17
LOS: 7 0
LOF: 6 0
Previous 1 day time = 24 hours 0 sec
FEC: 37705 0
CRC: 682 0
ES: 542 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Since Link time = 5 hours 12 min 25 sec
FEC: 0 1
CRC: 832 0
ES: 229 0
SES: 1 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 13479 Kbps, Downstream rate = 50112 Kbps
Path: 0, Upstream rate = 9995 Kbps, Downstream rate = 39998 Kbps
Discovery Phase (Initial) Band Plan
US: (0,95) (880,1195) (1984,2771)
DS: (32,859) (1216,1959) (2792,4083)
Medley Phase (Final) Band Plan
US: (0,95) (880,1195) (1984,2771)
DS: (32,859) (1216,1959) (2792,4083)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 13479 kbps 50112 kbps
Actual Aggregate Tx Power: 6.9 dBm 11.6 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 2.9 32.4 49.0 N/A 16.2 40.4 63.2
Signal Attenuation(dB): 2.9 32.2 48.8 N/A 16.2 40.4 63.2
SNR Margin(dB): 9.0 8.8 8.5 N/A 14.9 15.7 15.4
TX Power(dBm): -3.6 -10.4 6.4 N/A 9.2 7.2 0.9
#
-
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 2
Max: Upstream rate = 12711 Kbps, Downstream rate = 50884 Kbps
Path: 0, Upstream rate = 12523 Kbps, Downstream rate = 50062 Kbps
<snip>
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 13479 Kbps, Downstream rate = 50112 Kbps
Path: 0, Upstream rate = 9995 Kbps, Downstream rate = 39998 Kbps
:hmm: Hmm, something doesn't correctly 'add up'. The line that I've highlighted in red implies that you are now on an 80/20 Mbps product, yet the line highlighted in blue shows the service is capped at 40/10 Mbps.
Were those two results, output from xdslcmd info --stats and output from xdslcmd info --pbParams, obtained on different days?
I think I'd better call for the Analytical Eagle . . .
-
:hmm: Hmm, something doesn't correctly 'add up'. The line that I've highlighted in red implies that you are now on an 80/20 Mbps product, yet the line highlighted in blue shows the service is capped at 40/10 Mbps.
Were those two results, output from xdslcmd info --stats and output from xdslcmd info --pbParams, obtained on different days?
Those were my thoughts too when I first read the post.
Perhaps colly05 will confirm matters in due course.
-
ok just got home from work emailed plusnet during the day and its now sorted this is the email i got back
"I have checked and can see that the order to upgrade to 80/20 has completed today and your sync speed has picked up to 50.1Mbps.
Therefore, I have amended your speed profiles on our systems to match this which can take up to 4 hours to take effect automatically. If you find your speeds still haven't risen after this time, please reboot your router just once."
here is latest stats
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 2
Max: Upstream rate = 12522 Kbps, Downstream rate = 50552 Kbps
Path: 0, Upstream rate = 12523 Kbps, Downstream rate = 50062 Kbps
Discovery Phase (Initial) Band Plan
US: (0,95) (880,1195) (1984,2771)
DS: (32,859) (1216,1959) (2792,4083)
Medley Phase (Final) Band Plan
US: (0,95) (880,1195) (1984,2771)
DS: (32,859) (1216,1959) (2792,4083)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 12522 kbps 50552 kbps
Actual Aggregate Tx Power: 6.9 dBm 11.9 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 2.9 32.5 49.2 N/A 16.2 40.6 63.5
Signal Attenuation(dB): 2.9 32.4 49.0 N/A 16.2 40.6 63.5
SNR Margin(dB): 6.3 6.0 6.0 N/A 6.3 6.2 6.2
TX Power(dBm): -3.6 -10.2 6.5 N/A 9.3 7.4 2.6
#
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 2
Max: Upstream rate = 12525 Kbps, Downstream rate = 50552 Kbps
Path: 0, Upstream rate = 12523 Kbps, Downstream rate = 50062 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.2 6.0
Attn(dB): 0.0 0.0
Pwr(dBm): 11.9 6.9
VDSL2 framing
Path 0
B: 239 238
M: 1 1
T: 64 32
R: 0 16
S: 0.1526 0.6073
L: 12584 3359
D: 1 1
I: 240 255
N: 240 255
Counters
Path 0
OHF: 27189437 1678011
OHFErr: 3717 99
RS: 0 760052
RSCorr: 0 1075
RSUnCorr: 0 0
Path 0
HEC: 6873 0
OCD: 265 0
LCD: 265 0
Total Cells: 2116211855 0
Data Cells: 81362084 0
Drop Cells: 0
Bit Errors: 0 0
ES: 2871 26
SES: 10 0
UAS: 35 35
AS: 66634
Path 0
INP: 0.00 0.00
PER: 2.44 9.71
delay: 0.00 0.00
OR: 78.65 21.40
Bitswap: 10916 31
Total time = 1 days 9 hours 8 min 39 sec
FEC: 67992 0
CRC: 8232 0
ES: 2871 26
SES: 10 0
UAS: 35 35
LOS: 7 0
LOF: 6 0
Latest 15 minutes time = 8 min 39 sec
FEC: 0 0
CRC: 15 0
ES: 12 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 0 0
CRC: 523 0
ES: 109 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 9 hours 8 min 39 sec
FEC: 0 0
CRC: 1660 0
ES: 741 23
SES: 1 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 7643 0
CRC: 4891 0
ES: 1018 0
SES: 8 0
UAS: 17 17
LOS: 7 0
LOF: 6 0
Since Link time = 18 hours 30 min 33 sec
FEC: 0 1075
CRC: 3717 99
ES: 1370 23
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#
-
i used rs-w32-2.91 for the modem logging and it was early this morning so i quickly posted.
so i have got a bit better than my estimate of 33. and having got the hg612 i found i was on the 40/10 profile andi could get a bit more. so i havnet rebooted the modem yet and i am on the A2pv6C035m.d22g firmware. do i need to do anything else or just leave it now and see how it settles
thanks
-
I would advise allowing the service 'time to settle' and just monitor the line statistics, for now.
-
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 12199 Kbps, Downstream rate = 55060 Kbps
Path: 0, Upstream rate = 11810 Kbps, Downstream rate = 47658 Kbps
Discovery Phase (Initial) Band Plan
US: (0,95) (880,1195) (1984,2771)
DS: (32,859) (1216,1959) (2792,4083)
Medley Phase (Final) Band Plan
US: (0,95) (880,1195) (1984,2771)
DS: (32,859) (1216,1959) (2792,4083)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 12199 kbps 55060 kbps
Actual Aggregate Tx Power: 6.9 dBm 12.3 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 2.9 32.5 49.1 N/A 16.2 40.5 63.4
Signal Attenuation(dB): 2.9 32.3 48.9 N/A 16.2 40.5 63.4
SNR Margin(dB): 6.2 6.3 6.3 N/A 6.1 6.1 6.1
TX Power(dBm): -3.6 -10.4 6.5 N/A 9.3 7.6 4.3
#
-
just thought i would post where it is now download has dropped but all working well
better than the 37 which i was on before the hg612
-
noticed that interleaving on now i guess this is why the speed has dropped a bit. any thoughts on the stats do you think its the most i can get. looks like its settled to ....
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 12042 Kbps, Downstream rate = 55432 Kbps
Path: 0, Upstream rate = 11787 Kbps, Downstream rate = 47826 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.1 6.2
Attn(dB): 0.0 0.0
Pwr(dBm): 12.4 7.0
-
With SNR at around the target 6dB, it does appear that is the max your connection can currently achieve.
Have you managed to get any graphs running that might give a 'picture' of how your connection is/has been performing?
What level(s) of interleaving, INP & delay have now been set by DLM & how long has that taken from original installation?
I do notice that Retrain Reason in your stats has been 0 a few times.
That suggests you have been rebooting/disconnecting the power to your modem.
Do you do that quite often?
(DLM isn't really a big fan of that sort of thing & quite often reacts rather aggressively by applying high levels of interleaving & thus lower speed levels).
-
Sorry to steal on the topic but when the Retrain reason is 0 it means you disconnect the modem a lot?
What does 1 mean?
I'm assuming 2 mean it's in training?
-
:hmm: Good questions and worthy of a thread of their own.
Perhaps Eric or Kitz could please perform a cut / paste?
Once done, then the Eagle can expound on the topic (from his extensive notes).
-
I'll open a separate thread on the subject.
See http://forum.kitz.co.uk/index.php/topic,12504.msg236038.html#msg236038
-
I have rebooted a few times just positioning where the modem is and 1 time when the speed dropped ill leave it again for week ? Or so and report back ?
Thanks for any help tho ;-)
-
stats from just now been stable for nearly 4 days
whats your thoughts ??
-
well its still the same speed.
so do you guys think that's the final speed or is there a way to reset the interleave and leave it be again ?
any info would be great thanks
-
Let me see if I can 'whistle up' an Eagle to review your last few posts . . . :D
-
The Relative Capacity Occupation (RCO) - that is sync rate over max attainable rate - is quite low at 86% [1]
That might suggest the effect of banding.
However, the nearest profile with a max downstream rate exceeding 47,607Kbps (your sync rate) but less than 54,792Kbps (your attainable rate) is a profile with a max downstream rate of 54,000Kbps.
So it doesn't appear that your sync rate of 47,607Kbps is chasing that max rate of 54,000Kbps. Your line appears to have found its natural, organic transmission rate.
You also have moderate error counts, which the DLM algorithm has sought to overcome through interleaving and INP.
Based on those observations and the other parameters including your downstream minimum INP level (3 symbols) and your Max Interleaving Delay (8ms), we can probably identify the profile (or at least define a suitable one):
MA5616(config)#display vdsl channel-profile 997
------------------------------------------------------------------------------
Profile index: 997 Name: colly05_channel_profile
Data path mode : PTM
Minimum impulse noise protection downstream : ThreeSymbols
Minimum impulse noise protection upstream : NoProtection
Maximum interleaving delay downstream(ms) : 8
Maximum interleaving delay upstream(ms) : 0
Minimum transmit rate downstream(Kbps) : 27000
Minimum reserved transmit rate downstream(Kbps) : 27000
Maximum transmit rate downstream(Kbps) : 54000
Minimum transmit rate upstream(Kbps) : 10000
Minimum reserved transmit rate upstream(Kbps) : 10000
Maximum transmit rate upstream(Kbps) : 20000
Rate threshold downshift downstream(Kbps) : 0
Rate threshold upshift downstream(Kbps) : 0
Rate threshold downshift upstream(Kbps) : 0
Rate threshold upshift upstream(Kbps) : 0
PHY-R control in downstream : Disable
PHY-R control in upstream : Disable
Erasure decoding switch : Disable
Minimum SOS bit rate downstream(8Kbps) : 8
Minimum SOS bit rate upstream(8Kbps) : 8
Minimum expected throughput downstream(Kbps) : 32
Maximum expected throughput downstream(Kbps) : 200000
Maximum net data rate downstream(Kbps) : 200000
Minimum delay downstream(ms) : 0
Maximum delay downstream(ms) : 63
Minimum impulse noise protection against single
high impulse noise event downstream(DMT symbol) : 0
Minimum impulse noise protection against single
high impulse noise event transported over DMT
symbols with a subcarrier spacing of 8.625kHz
downstream(DMT symbol) : 0
Single high impulse noise event ratio
downstream(0.001) : 0
Minimum impulse noise protection against
repetitive electrical impulse noise
downstream(DMT symbol) : 0
Minimum impulse noise protection against
repetitive electrical impulse noise transported
over DMT symbols with a subcarrier spacing of
8.625kHz downstream(DMT symbol) : 0
Repetitive electrical impulse noise
inter-arrival time downstream
0-100Hz 1-120Hz(0~1) : 0
Minimum expected throughput upstream(Kbps) : 32
Maximum expected throughput upstream(Kbps) : 200000
Maximum net data rate upstream(Kbps) : 200000
Minimum delay upstream(ms) : 0
Maximum delay upstream(ms) : 63
Minimum impulse noise protection against single
high impulse noise event upstream(DMT symbol) : 0
Minimum impulse noise protection against single
high impulse noise event transported over DMT
symbols with a subcarrier spacing of 8.625kHz
upstream(DMT symbol) : 0
Single high impulse noise event ratio
upstream(0.001) : 0
Minimum impulse noise protection against
repetitive electrical impulse noise
upstream(DMT symbol) : 0
Minimum impulse noise protection against
repetitive electrical impulse noise transported
over DMT symbols with a subcarrier spacing of
8.625kHz upstream(DMT symbol) : 0
Repetitive electrical impulse noise
inter-arrival time upstream
0-100Hz 1-120Hz(0~1) : 0
Channel initialization policy selection : 0
------------------------------------------------------------------------------
Have they told you the distance from your cabinet?
cheers, a
[1] http://www.kitz.co.uk/adsl/linestats_explanation.htm
-
No. Only the estimated distance I worked out.
So far I'm pleased but would always like more.
Thanks.
-
estimate of 750m distance
-
Looks about right then. In fact it's pretty good if the loop length is 750m. On thinkbroadband there's a speed prediction table for gauging a rough rule of thumb:
http://www.thinkbroadband.com/guide/fibre-broadband.html
Lots of variables to consider though. The quality of the pair is important, and of course there's crosstalk to consider.
Any idea of the demographics to your area? Just to try and judge the take-up of FTTC.
I would expect (albeit with no proof) that areas where older people tend to live generally enjoy higher sync speeds. Because take-up of FTTC tends to be lower (ageist assumption!) and, consequently, crosstalk is less of an issue in those areas.
Then again, perhaps that assumption is false because in the current climate, older people tend to have higher levels of disposable income to spend on broadband upgrades, and other non-essentials.
cheers, a
EDIT: Maybe to discover the quality of your pair, and the impairments on it, you could study the data gathered and graphed by tools developed by Eric (Roseway) and Paul (Bald Eagle). In particular, the QLN (background noise) and the Hlog (attenuation) graphs.
-
Is there a way to reset interleave or dslam ?
-
Is there a way to reset interleave or dslam ?
Your interleaving depth seems quite high.
If DLM doesn't adjust it or automatically or return your connection to fastpath, the only way is to request a DLM reset/recalc via your ISP.
However, ISPs can't actually physically do this as it is fully controlled by Openreach.
There is every likelihood the request would be rejected as it is usually only granted following physical line repairs & even then it is sometimes rejected.
Visibility of a few days worth of 24/7 monitoring graphs along with the usual snapshot graphs at different times of day/night may just highlight a pattern to noise interference and/or physical line issues.
Overall though, at a quick glance, it seems fairly good for a 750m or so line length.
-
ok final post
so is it worth asking plusnet to see if it can be reset or should i leave it be
if any more info is needed let me know. didn't realise turning off modem while getting sorted where to put it would alter anything
(if it did ) just want to say thanks again for all advice and help