Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Bald_Eagle1]

i remember putting the gas boiler on for the hot water around that time, i thought of that , but no change after i knocked it off.
...shame becouse it was holding at 6.8 for the last 2 days 

Maybe a neighbour switched some electrical equipment on or switched their modem/router back on?


Your connection sees more US OHFErr (CRC) errors & Errored seconds (ES) than DS.

Indirectly, they MIGHT be impacting on your DS Interleaving depth.


Attainable rates always seem artificially high when Interleaving is applied.



Unlike updated versions, the firmware version your modem is currently using doesn't show any differences in pbParams data between DS Line Attenuation & Signal Attenuation for each band.


That COULD actually be the case, but here's mine for reference (roughly 1050 m line length):-

Code: [Select]

xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 4429 Kbps, Downstream rate = 20576 Kbps
Bearer: 0, Upstream rate = 4516 Kbps, Downstream rate = 22271 Kbps

Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1198)
DS: (33,859) (1216,1852)
  VDSL Port Details   Upstream   Downstream
Attainable Net Data Rate:      4429 kbps     20576 kbps
Actual Aggregate Tx Power:        6.8 dBm      12.6 dBm
====================================================================================
  VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
  Line Attenuation(dB): 8.2 54.1   N/A   N/A   N/A 21.8 66.4   N/A
Signal Attenuation(dB): 8.2 53.4   N/A   N/A   N/A 30.7 66.2   N/A
SNR Margin(dB): 6.1 6.0   N/A   N/A   N/A 5.2 5.2   N/A
TX Power(dBm): -0.4 5.9   N/A   N/A   N/A 11.6 6.0   N/A




Interestingly, after many months of DS Interleaving depth of around 400, my connection was switched to fastpath, with a slightly higher sync speed when the connection resynced just over a week ago.

[NewtronStar]

Interestingly, after many months of DS Interleaving depth of around 400, my connection was switched to fastpath, with a slightly higher sync speed when the connection resynced just over a week ago.

Thats good BE1, I have been waiting just over 2 years to be switched to fastpath on FTTC  (but if you've never had it you won't miss it ) thats what I try to tell myself when I see 51ms pings when gaming online with my Interleaving Depth of 587.

[perry081064]

  Oops, b*cat has committed a folly. 

I should have asked you for the Connection Stats, from under the Telnet Data tab in DSLstats and not the pbParams.

(Now where is that Analytical Eagle? Methinks it is best to keep my tail tucked inside this brown paper bag, to avoid any spurious tail pecks.)

no probs , here you go

... just before posting this there was a massive drop in down SNRM from 6.8 to 5.9 , also a drop in max downstream rate to 57552.
..not sure whats caused that 

Code: [Select]

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 21906 Kbps, Downstream rate = 57788 Kbps
Path: 0, Upstream rate = 20000 Kbps, Downstream rate = 50851 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): 5.9 6.3
Attn(dB): 0.0 0.0
Pwr(dBm): 12.9 6.4
VDSL2 framing
Path 0
B: 51 236
M: 1 1
T: 64 5
R: 12 16
S: 0.0325 0.3771
L: 15736 5410
D: 995 1
I: 64 255
N: 64 255
Counters
Path 0
OHF: 209823215 398268
OHFErr: 121 876
RS: 2175014138 1279253
RSCorr: 1726808 10947
RSUnCorr: 2030 0

Path 0
HEC: 353 0
OCD: 14 0
LCD: 14 0
Total Cells: 4232872255 0
Data Cells: 785660426 0
Drop Cells: 0
Bit Errors: 0 0

ES: 42 676
SES: 0 0
UAS: 18 18
AS: 438646

Path 0
INP: 3.00 0.00
PER: 2.08 6.12
delay: 8.00 0.00
OR: 92.20 203.67

Bitswap: 112359 23204

Total time = 1 days 1 hours 51 min 14 sec
FEC: 1726808 10947
CRC: 121 876
ES: 42 676
SES: 0 0
UAS: 18 18
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 6 min 14 sec
FEC: 5302 3
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 2401 1
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 1 hours 51 min 14 sec
FEC: 29018 89
CRC: 5 15
ES: 1 14
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 483533 3332
CRC: 19 190
ES: 7 153
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Since Link time = 5 days 1 hours 50 min 47 sec
FEC: 1726808 10947
CRC: 121 876
ES: 42 676
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#

todays DSLSTATS for comparison.

Code: [Select]

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 21903 Kbps, Downstream rate = 58720 Kbps
Path: 0, Upstream rate = 20000 Kbps, Downstream rate = 50851 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.3
Attn(dB): 0.0 0.0
Pwr(dBm): 12.9 6.4
VDSL2 framing
Path 0
B: 51 236
M: 1 1
T: 64 5
R: 12 16
S: 0.0325 0.3771
L: 15736 5410
D: 995 1
I: 64 255
N: 64 255
Counters
Path 0
OHF: 284819395 1343480
OHFErr: 176 1171
RS: 4194167088 2138669
RSCorr: 2402064 13159
RSUnCorr: 3849 0

Path 0
HEC: 736 0
OCD: 23 0
LCD: 23 0
Total Cells: 2382125142 0
Data Cells: 967471803 0
Drop Cells: 0
Bit Errors: 0 0

ES: 58 888
SES: 0 0
UAS: 18 18
AS: 595429

Path 0
INP: 3.00 0.00
PER: 2.08 6.12
delay: 8.00 0.00
OR: 92.20 203.67

Bitswap: 155240 32361

Total time = 1 days 21 hours 24 min 17 sec
FEC: 2402064 13159
CRC: 176 1171
ES: 58 888
SES: 0 0
UAS: 18 18
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 9 min 17 sec
FEC: 1080 9
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 1222 11
CRC: 5 1
ES: 1 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 21 hours 24 min 17 sec
FEC: 434091 1218
CRC: 42 124
ES: 12 93
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 270183 1083
CRC: 18 186
ES: 5 133
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Since Link time = 6 days 21 hours 23 min 51 sec
FEC: 2402064 13159
CRC: 176 1171
ES: 58 888
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#

[burakkucat]

You really need an Analytical Eagle to comment . . . 

[Bald_Eagle1]

My 'suspicion' is that you have been affected by increased crosstalk as the error counts don't look too bad.

If you are still using both programs, could you post the ongoing montage from HG612 Modem Stats from the period before your SNRM reduced until the present time?


You could manually run graphpd.exe or run it from the GUI & specify 6 d (6 days), assuming you have at least 6 days worth of data in modem_stats.log.

[perry081064]

My 'suspicion' is that you have been affected by increased crosstalk as the error counts don't look too bad.

If you are still using both programs, could you post the ongoing montage from HG612 Modem Stats from the period before your SNRM reduced until the present time?


You could manually run graphpd.exe or run it from the GUI & specify 6 d (6 days), assuming you have at least 6 days worth of data in modem_stats.log.

many thanks for the feedback 
i was hoping it was the HH5 that was originally connected that was causing the issues as theres been so much bad press about them constantly rebooting.

im in quite a large town that although has virgin media, ive noted a lot of people having problems with their service and moving to FTTC so im inclined to believe that your prognosis is indeed correct.

unfortunately i hadnt bothered using the other program, prefering just to use DSLstats , i dont know if running it now would be any use to you, if so , its not a problem to organise that .

if i am to use HG612 modem stats , i take it i would need to keep the pc running 24/7 for the next 6 days ?

again, thanks for your support 

[Bald_Eagle1]

if i am to use HG612 modem stats , i take it i would need to keep the pc running 24/7 for the next 6 days ?

For the stats to be truly meaningful, then yes, 24/7 monitoring is essential in order to detect patterns of issues/fluctuations etc.

Not everyone wishes to do that.

If the speed reduction/application of a fairly high Interleaving depth was actually due to the HH5'a issues, there is every chance that the connection will recover in due course (maybe 14 days or more of stability, low error counts, minimal resyncs etc.)

I always leave my PC running 24/7 & I originally developed my programs in FTTC's early days to 'prove' my connection's instability & 'faults' to my ISP who initially stated my connection was fine.
Having many months of stats eventually convinced them to pursue BTOR until the main fault was tracked down & cured.

Following 7 months of my repaired trouble free & relatively high speed connection, I started to see gradual increases in crosstalk that reduced my connection's DS sync speed from around 30 Mbps to around 20 Mbps.

BTOR remotely updated HG612 modems' firmware back in October, which appears to have slightly improved matters on my roughly 1050m long line, so much so that Interleaving was removed a short while ago.

From the format of your stats, I can see your HG612's firmware hasn't been updated (yet).
It may be remotely updated during the next week or so, but it's possible that whoever unlocked it decided to block BTOR's remote access.
Updated firmware versions (blocked & unblocked) can be downloaded via this link, should you wish to try them out:-

https://mega.co.nz/#F!LdJFDIJL!e_E1twsIg2kTet8mPjrb4w



You may wish to continue using DSLStas on an ad-hoc basis until when/if you see a further deterioration before electing to use HG612 Modem Stats.
As mentioned above, it may well improve.

An updated HG612 Modem Stats package is on its way, probably being realeased within the next couple of weeks.
It might be worth waiting for that anyway.

[perry081064]

if i am to use HG612 modem stats , i take it i would need to keep the pc running 24/7 for the next 6 days ?

For the stats to be truly meaningful, then yes, 24/7 monitoring is essential in order to detect patterns of issues/fluctuations etc.

Not everyone wishes to do that.

If the speed reduction/application of a fairly high Interleaving depth was actually due to the HH5'a issues, there is every chance that the connection will recover in due course (maybe 14 days or more of stability, low error counts, minimal resyncs etc.)



I always leave my PC running 24/7 & I originally developed my programs in FTTC's early days to 'prove' my connection's instability & 'faults' to my ISP who initially stated my connection was fine.
Having many months of stats eventually convinced them to pursue BTOR until the main fault was tracked down & cured.

Following 7 months of my repaired trouble free & relatively high speed connection, I started to see gradual increases in crosstalk that reduced my connection's DS sync speed from around 30 Mbps to around 20 Mbps.

BTOR remotely updated HG612 modems' firmware back in October, which appears to have slightly improved matters on my roughly 1050m long line, so much so that Interleaving was removed a short while ago.

From the format of your stats, I can see your HG612's firmware hasn't been updated (yet).
It may be remotely updated during the next week or so, but it's possible that whoever unlocked it decided to block BTOR's remote access.
Updated firmware versions (blocked & unblocked) can be downloaded via this link, should you wish to try them out:-

https://mega.co.nz/#F!LdJFDIJL!e_E1twsIg2kTet8mPjrb4w



You may wish to continue using DSLStas on an ad-hoc basis until when/if you see a further deterioration before electing to use HG612 Modem Stats.
As mentioned above, it may well improve.

An updated HG612 Modem Stats package is on its way, probably being realeased within the next couple of weeks.
It might be worth waiting for that anyway.

Hi Bald_Eagle1

thanks again for bearing with me as i slowly try to find me feet around all this , theres so much to learn 

yes after doing some homework and reading up a little, i understand why the pc would need to be on 24/7 over a period of time.
thats no problem , however i think ill wait as you advise, for the updated stats package to arrive. that "should" give the stats time to re-adjust if they was down to the HH5 reboots.

i purchased the unlocked HG612 from a auction site seller and i was under the impression that this was the latest version and it was supposedly a good thing that the option for bt to update was disabled .  the main reason i thought this was becouse of btor's constant checking was causing the reboots in the HH5 hence me purchasing the hg612 in the first place.

ive just downloaded the firmwares from the link you provided and i see theres an option to install the one with the snitch disabled so i may give that a shot once ive given this time to adjust back of its own accord.

thanks again for the input, its people like you that make this forum what it is ... awesome 

[Bald_Eagle1]

i purchased the unlocked HG612 from a auction site seller and i was under the impression that this was the latest version and it was supposedly a good thing that the option for bt to update was disabled .  the main reason i thought this was becouse of btor's constant checking was causing the reboots in the HH5 hence me purchasing the hg612 in the first place.

ive just downloaded the firmwares from the link you provided and i see theres an option to install the one with the snitch disabled so i may give that a shot once ive given this time to adjust back of its own accord.

thanks again for the input, its people like you that make this forum what it is ... awesome 

I agree that this forum really is awesome.

I knew next to nothing about any sort of broadband & I hadn't really written a meaningful program at all until I first registered here back in 2011.

I have received a tremendous amount of patient & polite assistance & advice from regular members since then.



Just in case you weren't aware, BTOR's remote firmware update disables the HG612's GUI, but Telnet access & access to the monitoring programs is still available.


If you check the firmware versions in the Experimental area of the download site I provided the link for, updated blocked & unblocked GUI versions are available.

They aren't really experimental versions any longer as many users (from this forum & others) have tried & tested both versions & they simply work reliably as intended.




You can confirm your current firmware version via telnet, using admin & admin for username & password, then sh to get into Busybox.

Once in Busybox, type the command xdslcmd --version.

This is mine:-

xdslcmd --version
xdslcmd version 1.0
DSL PHY: AnnexA version - A2pv6C038m.d24j
******* Pass *********

[perry081064]

i purchased the unlocked HG612 from a auction site seller and i was under the impression that this was the latest version and it was supposedly a good thing that the option for bt to update was disabled .  the main reason i thought this was becouse of btor's constant checking was causing the reboots in the HH5 hence me purchasing the hg612 in the first place.

ive just downloaded the firmwares from the link you provided and i see theres an option to install the one with the snitch disabled so i may give that a shot once ive given this time to adjust back of its own accord.

thanks again for the input, its people like you that make this forum what it is ... awesome 

I agree that this forum really is awesome.

I knew next to nothing about any sort of broadband & I hadn't really written a meaningful program at all until I first registered here back in 2011.

I have received a tremendous amount of patient & polite assistance & advice from regular members since then.



Just in case you weren't aware, BTOR's remote firmware update disables the HG612's GUI, but Telnet access & access to the monitoring programs is still available.


If you check the firmware versions in the Experimental area of the download site I provided the link for, updated blocked & unblocked GUI versions are available.

They aren't really experimental versions any longer as many users (from this forum & others) have tried & tested both versions & they simply work reliably as intended.




You can confirm your current firmware version via telnet, using admin & admin for username & password, then sh to get into Busybox.

Once in Busybox, type the command xdslcmd --version.

This is mine:-

xdslcmd --version
xdslcmd version 1.0
DSL PHY: AnnexA version - A2pv6C038m.d24j
******* Pass *********

... and this is mine.


# xdslcmd --version
xdslcmd version 1.0
DSL PHY: AnnexA version - A2pv6C035m.d22g
******* Pass *********
#

wonder why it was supplied with an older version , i only purchased it a week ago ?

..not to worry, as already stated , i will flash the provided version once ive given the modem time to settle.

[Bald_Eagle1]

This was Asbokid's original unlocked firmware version:-

xdslcmd --version
xdslcmd version 1.0
DSL PHY: AnnexA version - A2pv6C030b.d22g
******* Pass *********


The version you have seems to be the one with the 'new' BLOB.

That version did give me slightly higher sync speeds, but (from memory), the reported bitloading data does not change dynamically between resyncs & it doesn't use the updated band plans.


These are your current band plans (ECI DSLAM):-

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)


These are the ECI bandplans when using the October 2013 updated firmware:-

Discovery Phase (Initial) Band Plan
US: (6,31) (882,1193) (1984,2770)
DS: (33,857) (1218,1959) (2795,4083)
Medley Phase (Final) Band Plan
US: (6,31)
DS: (67,503)

The Medley Phase (Final) Band Plan shown in the example is from a very long distance connection that is unable to use all the lowest frequency band, never mind the higher frequency bands:-

Max:   Upstream rate = 443 Kbps, Downstream rate = 2760 Kbps
Bearer:   0, Upstream rate = 487 Kbps, Downstream rate = 2637 Kbps

[perry081064]

This was Asbokid's original unlocked firmware version:-

xdslcmd --version
xdslcmd version 1.0
DSL PHY: AnnexA version - A2pv6C030b.d22g
******* Pass *********


The version you have seems to be the one with the 'new' BLOB.

That version did give me slightly higher sync speeds, but (from memory), the reported bitloading data does not change dynamically between resyncs & it doesn't use the updated band plans.

i see , so its worth upgrading to the latest version then 

as my SNR  and max downstream rate have increased again to SNR 6.8 , downstream max 61064 , would it be worth waiting to change to the new firmware or flash it asap ?

thanks again.

[perry081064]

just a quick update...

as i am still learning, ingnore me if its normal behavior.
i was out in the garden until it started to rain this afternoon, i had left DSLstats running as i was getting a SNRM of 6.8 and my max speed had increased .

at the same time the rain ( not heavy, just a general shower) started , my DS SNRM dropped and my US SNRM rose .... its now stopped as it was only a 5 minute shower but my stats remain the same as shown below

is this normal, i ask becouse i notice the pole im attached to has my line connected and being fed to a grey box held on by a cable tie 

[HighBeta]

Hows the wiring behind the NTE5 perry ?

Is the wire run into a Block Terminal or any other points from when it comes into the property ?

Excellent guide on types of  sockets

http://www.kitz.co.uk/adsl/btsockets.htm

Also recommend having a quick look over les-70 thread on "findings with a new connection"
http://forum.kitz.co.uk/index.php?topic=13420.45

Some hidden gems in that thread - {thanks les-70}

[perry081064]

Hows the wiring behind the NTE5 perry ?

Is the wire run into a drop box or any other points from when it comes into the property ?

Excellent guide on types of  sockets

http://www.kitz.co.uk/adsl/btsockets.htm

Hi HighBeta.

wiring to the NTE5 is fine , i watched the whole process when the new line was installed last year.
i notice the wire coming from the pole attaches to the gable of the house , it loops then runs down to a comtell box thats situated at just the right position to match the NTE5 inside the house.
the box on the pole outside is the one thats got a grey box table tied together thats making me worry
..not a good pic, but the best i can do...

https://www.dropbox.com/s/0730m42ohjw4tos/2014-05-07%2016.28.23.jpg