Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: perry081064 on May 01, 2014, 10:55:47 AM
-
Hi guys, new to the forums so go gentle on me :-[.
over the last few months ( around the time I changed to a homehub 5 ) I noticed my download speed had dropped from my usual 60mbps to around 43 mbps.
im about 300 meters from my cab and had a brand new line from the pole on original install.
I managed to purchase a unlocked Hg612 from ebay , but im struggling to fully understand what the stats are telling me.
..could someone take a look over them for me and point out what I should be keeping an eye on or anything that stands out as a major problem.
many thanks in advance.
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 22119 Kbps, Downstream rate = 58020 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.0 6.4
Attn(dB): 0.0 0.0
Pwr(dBm): 13.0 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: 70599127 2183374
OHFErr: 36 283
RS: 893386049 2128527
RSCorr: 629493 4150
RSUnCorr: 823 0
Path 0
HEC: 163 0
OCD: 4 0
LCD: 4 0
Total Cells: 1545467255 0
Data Cells: 342528253 0
Drop Cells: 0
Bit Errors: 0 0
ES: 13 208
SES: 0 0
UAS: 18 18
AS: 147591
Path 0
INP: 3.00 0.00
PER: 2.08 6.12
delay: 8.00 0.00
OR: 92.20 203.67
Bitswap: 43168 8025
Total time = 1 days 17 hours 18 sec
FEC: 629493 4150
CRC: 36 283
ES: 13 208
SES: 0 0
UAS: 18 18
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 18 sec
FEC: 2 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 973 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 17 hours 18 sec
FEC: 355058 3070
CRC: 19 119
ES: 6 85
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 274435 1080
CRC: 17 164
ES: 7 123
SES: 0 0
UAS: 18 18
LOS: 0 0
LOF: 0 0
Since Link time = 1 days 16 hours 59 min 50 sec
FEC: 629493 4150
CRC: 36 283
ES: 13 208
SES: 0 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 = 22195 Kbps, Downstream rate = 58488 Kbps
Path: 0, Upstream rate = 20000 Kbps, Downstream rate = 50851 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: 22195 kbps 58488 kbps
Actual Aggregate Tx Power: 6.4 dBm 13.0 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 1.0 24.3 38.1 N/A 12.8 31.9 50.7
Signal Attenuation(dB): 1.0 24.1 38.0 N/A 12.8 31.9 50.7
SNR Margin(dB): 6.5 6.8 6.4 N/A 6.1 6.1 6.1
TX Power(dBm): -5.1 -20.7 6.0 N/A 9.5 7.4 7.3
#
-
Hi & welcome
There are some very good people on here that will no doubt take a look.
Also if you haven't already downloaded a stat program...
Either of these two are excellent at monitoring the line and can help give a better ideal of whats going on over a longer period of time.
Bald Eagle's
http://www.kitz.co.uk/routers/hg612stats.htm
roseway's
http://www.s446074245.websitehome.co.uk/
:)
-
Thanks for the welcome HighBeta :)
yes, ive already downloaded and am using both of those stat programs thanks.
the trouble im having is knowing what im looking for and a trained eye that could assess the stats provided , once ive got a few pointers on what to really look for , im sure ill be fine.
-
what I should be keeping an eye on or anything that stands out as a major problem.
Hi Perry081064 you will enjoy the Kitz forum
Well what I keep a close eye on in the stats is the SNRM as going below 6.0dB is not very welcome but going below 4.5dB is very bad, the next is the errors CRC and ES are a good guide if there is some kind of fault on the End User Line or an Internal issue with wiring.
Then comes the Tones and Bitloading and then Telnet data it's very complex to understand what your seeing on screen and convert it to how the line is performing it does take time and alot of help from BaldEagle1 ;D
-
Thanks for the info NewtronStar :)
i have some ES and CRC errors , im not too sure but they dont seem too high, but then again , im not sure what would be deemed as high anyway.
ive learned that my IMP of 3.00 and delay of 8.00 means ive been put on interleave (995) , so im learning something at least.
just need to find out whats caused it now ???
-
Phone line sound ok on the quiet line test ?
[Dial 17070 and select option 2 - best on a corded phone]
-
seems quiet , but its not corded so ill try and get one from town tomorrow.
managed to grab a screenshot of the QLN stats if thats any use ?
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi58.tinypic.com%2Fe80uar.png&hash=d23865f340540f9e5ecb30a8423bfab92fc2dea2)
-
Hello Perry081064 you need to know the QLN graph in the stats is not real time like CRC's errors and the SNRM.
The QLN Graph in the Stats is like a snapshot of your Line when the FTTC modem has been turned on it will not change again until you reboot the FTTC modem and I would avoid that for any testing purposes.
If you have noise creeping in and out during a 24 hour period then the best way to see this in the Graphs is to use SNR per tone this is real-time and will show massive large dips of SNR on your line if there is RFI and REIN noise.
-
hey thanks for all the info NewtronStar , need all the help i can get :-[
... what im beginning to notice is my SNRM is actually starting to rise tonight . i would normaly droop to around 5.8 around 9/10pm , however its gone up to 6.4.
....also ive noticed my attainable rate rise to 59424 so im hoping this is a good sign of my actual speed rising :-\
path downsteam doesnt want to move from 50851 though , making my actual download speed stay at around 47mbps .
could be worse though so i wont bitch about it.
thanks for all the info guys, im slowly making headway so keep it coming.
-
That QLN graph shows some noise spikes around tone 3200 and 3600 which I don't see on my line. I wonder whats causing that. Not crosstalk that's for sure so maybe some RFI/EMI in the vicinity...
Hows your internal phone wiring and extensions?
-
Hi Custard , and thanks for the input :)
new phoneline installed from pole to house when i moved here last year, new faceplate fitted by openreach at the same time.
HG612 connected directly to that running to my Billion 7800.
no other extentions for phone or broadband.
theres a couple of street lights near the house, other than that , not much else.
...also, i am running a couple of powerline adaptors , one for the IPcam and one for my daughters computer in her room.
ive disconnected the IPcam adaptor for now, but until i can run some ethernet cable into my daughters room , that one will have to carry on running.
downstream SNRM has risen today to 6.6 and attainable speed has risen to 60360 , however removing one of the powerlines hasnt improved anything as yet, however ill keep a check on it.
excellent advice here, think ill be staying a while :)
-
Good evening perry081064 I am sure quite a few members would love to see your Bitloading Graph, to me it seems you have a nice quiet line apart from the tones Custard has mentioned in the D3 band.
Regards NS
-
Good evening perry081064 I am sure quite a few members would love to see your Bitloading Graph, to me it seems you have a nice quiet line apart from the tones Custard has mentioned in the D3 band.
Regards NS
as requested, im hoping this is the graph required.
really struggling to understand all these graphs , feeling a bit of a noob and out of my depth with it all, but ill persevere as i find it really interesting.
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi58.tinypic.com%2F24g3mgz.png&hash=0b90b968e01a4ff9c0316ad6e12557bc072b5ffd)
-
It all look good to me, and I see you also have same SNRM dips on tones 1491 and 1665 to 1717 on the D2 Band plan as me and many others with FTTC across the UK there has to be some sort of explanation to this (is it RFI or is it just part of the normal MSAN noise) :-\
-
The bit loading looks good and as there is no deficit where the SNRM shows those downward spikes, I'll say that there is nothing to be concerned about.
Cross-referencing the dual-graph with that of the QLN, some posts above, reinforces that opinion. :)
-
Its abit difficult to see if bitloading has been reduced where SNRM drops in the compressed graph.
Can you take some more snapshots using the expand function around the SNRM drops in D2 and D3.
Examples of mine compressed and expanded in D1 are attached
Can you also provide the hlog for completeness.
-
Its abit difficult to see if bitloading has been reduced where SNRM drops in the compressed graph.
Can you take some more snapshots using the expand function around the SNRM drops in D2 and D3.
Examples of mine compressed and expanded in D1 are attached
Can you also provide the hlog for completeness.
Hi Custard , hope these are what you require, ive expanded the entire graph as best i can ..
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi62.tinypic.com%2F2u9idue.jpg&hash=bf839c40d31e3113657d819875cbaf7cc7f01e4b)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi59.tinypic.com%2F2nqhaf5.png&hash=f94e9101d6846239a7c8ebb10737810cefd34949)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi60.tinypic.com%2F2m4egqe.png&hash=240ab6cc9a1e1980866bfc8bdd0e544c80ddc3b7)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi60.tinypic.com%2F254yo77.png&hash=c9e58f671779b8c9a39d2d6bbc1586ba74350778)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi59.tinypic.com%2F2u9pnd5.png&hash=375402c5d1464c795a6968e521559a4bfd124d7f)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi59.tinypic.com%2Fvgjwn8.png&hash=34cd9aea1d10d2a0c4564f4ac149926e926ecc2c)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi60.tinypic.com%2F6dy5gj.png&hash=a2cfde872bab95ccebb862f77b4a6e06f0ecb748)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi59.tinypic.com%2F2ahwjva.png&hash=42c19d67086f22f1783eb225ff6c386b1f4e0a56)
-
The bit loading looks good and as there is no deficit where the SNRM shows those downward spikes, I'll say that there is nothing to be concerned about.
Cross-referencing the dual-graph with that of the QLN, some posts above, reinforces that opinion. :)
Hi Burakkucat :)
based on info and graphs supplied , would you say theres a possiblity that my interleave will be reduced or knocked off ?
...im hoping to regain my speed of 59 down 17 up that i used to have .
-
HI Perry.
Sorry you seem to have shown the wrong areas in the graphs. I Was looking for tones 3000-3900 in D3 and possibly tones 1300-1800 in D2.
Try to take these when your overall SNRM drops.
For the HLog leave the image collapsed so that all the tones show in the graph.
Once you have a few days of data you may be able to detect when the RFI/REIN occurs by checking your SNRM per band.
Lastly you might want to upgrade to the latest firmware. Peeps on here are reporting that it works better at bitswapping on noisy lines.
Nb: your line does not so much noise compared to some of the longer lines!
-
based on info and graphs supplied , would you say theres a possiblity that my interleave will be reduced or knocked off ?
That is the question, isn't it! ;)
Unfortunately I can't answer it. If the circuit is "well behaved" and stable, there is the possibility that the depth of the interleaving will be reduced, step-wise. It might be worthwhile posting the pbParams data for a number of successive days and then Bald Eagle1 may be able to offer an opinion . . . :-\
-
based on info and graphs supplied , would you say theres a possiblity that my interleave will be reduced or knocked off ?
That is the question, isn't it! ;)
Unfortunately I can't answer it. If the circuit is "well behaved" and stable, there is the possibility that the depth of the interleaving will be reduced, step-wise. It might be worthwhile posting the pbParams data for a number of successive days and then Bald Eagle1 may be able to offer an opinion . . . :-\
that would be great thanks
this is the first pbParams from 4 days ago..
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 22195 Kbps, Downstream rate = 58488 Kbps
Path: 0, Upstream rate = 20000 Kbps, Downstream rate = 50851 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: 22195 kbps 58488 kbps
Actual Aggregate Tx Power: 6.4 dBm 13.0 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 1.0 24.3 38.1 N/A 12.8 31.9 50.7
Signal Attenuation(dB): 1.0 24.1 38.0 N/A 12.8 31.9 50.7
SNR Margin(dB): 6.5 6.8 6.4 N/A 6.1 6.1 6.1
TX Power(dBm): -5.1 -20.7 6.0 N/A 9.5 7.4 7.3
#
and this one from almost 5 days on ( today)..
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 21920 Kbps, Downstream rate = 60360 Kbps
Path: 0, Upstream rate = 20000 Kbps, Downstream rate = 50851 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: 21920 kbps 60360 kbps
Actual Aggregate Tx Power: 6.4 dBm 13.0 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 1.0 24.3 38.1 N/A 12.8 31.9 50.7
Signal Attenuation(dB): 1.0 24.1 38.0 N/A 12.8 31.9 50.7
SNR Margin(dB): 6.1 6.4 6.3 N/A 6.6 6.7 6.6
TX Power(dBm): -5.1 -20.7 6.0 N/A 9.5 7.4 7.3
#
hope this helps
-
:paperbag: 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.)
-
Or a bank hoilday migrate to warmer climates away from troublesome kittens :)
Perry do you have any white extension cable (cw1308) into the NTE5 ?
Custards makes a great point on wiring.
Hows your internal phone wiring and extensions?
-
:paperbag: 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 :'(
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
#
-
Or a bank hoilday migrate to warmer climates away from troublesome kittens :)
Perry do you have any white extension cable (cw1308) into the NTE5 ?
Custards makes a great point on wiring.
Hows your internal phone wiring and extensions?
none whatsoever , phone and modem direct to the box
-
... 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 :'(
This would be the time to get that bitloading/SNRM data while the SNRM has dropped!
-
... 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 :'(
This would be the time to get that bitloading/SNRM data while the SNRM has dropped!
hope these are what you need...
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi62.tinypic.com%2F16m4z83.png&hash=efdbc0684b4f9a6a4ea361aacaaeb16145ab1579)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi62.tinypic.com%2F2ppaogz.png&hash=32d801fa3d069ab54647eb44d3ac7228cc8f8f2a)
-
:D I think I need some spectacles!!
Looking at that I don't think that those spikes would cause you to lose so much speed as you haven't lost bitloading on too many tones.
If your SNRM is dropping about 6pm and then rising again at 10pm everyday then this might just be normal variation. This will be apparent once you have stats over a few days.
Did any electrical appliances get switched on at the time when your SNRM reduced.
-
:D I think I need some spectacles!!
Looking at that I don't think that those spikes would cause you to lose so much speed as you haven't lost bitloading on too many tones.
If your SNRM is dropping about 6pm and then rising again at 10pm everyday then this might just be normal variation. This will be apparent once you have stats over a few days.
Did any electrical appliances get switched on at the time when your SNRM reduced.
shouldve gone to specsavers .... lol just kidding ;)
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 :(
-
Or a bank hoilday migrate to warmer climates away from troublesome kittens :)
Migrated to the garden today for the first time this year.
The grass was knee high.
Cutting through that lot certainly kept me warm (spurious tail pecking was the last thing on my mind) & there's still a lot more to cut tomorrow.
-
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):-
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.
-
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.
-
:paperbag: 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 :'(
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.
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
#
-
You really need an Analytical Eagle to comment . . . ;)
-
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.
-
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 :)
-
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.
-
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 :)
-
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 *********
-
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.
-
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
-
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.
-
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 :-\
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi60.tinypic.com%2F2uhsv3o.png&hash=f69dd99aee04ae5add17d2bdb2e74480ad71b6bd)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi62.tinypic.com%2Fjq2plg.png&hash=431a9d2e05fd40338373c841b98d7e388970a6a0)
-
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} ;)
-
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
-
at the same time the rain ( not heavy, just a general shower) started , my DS SNRM dropped and my US SNRM rose
That's interesting, i wonder whats causing that to happen. It not even a gradual decline/increase.
Almost as if the band plans have changed handing more to upload. Are you sure you did not have a resync?
I'm intrigued with this and look forward to hearing what the brainboxes on the forum think about it!
-
at the same time the rain ( not heavy, just a general shower) started , my DS SNRM dropped and my US SNRM rose
That's interesting, i wonder whats causing that to happen. It not even a gradual decline/increase.
Almost as if the band plans have changed handing more to upload. Are you sure you did not have a resync?
I'm intrigued with this and look forward to hearing what the brainboxes on the forum think about it!
no resync according to DSLstats or my router logs , its certainly something to do with that rainshower.
as my house sits and the area that the telephone line enters the building was fully sheltered from the shower , i can only conclude something happened at the cab or from the pole as shown in the photo link.
its got me stumped ( that doesnt take much though :-[ )
-
well its been pouring down for most of the morning and my DS SNRM has been stable at 6.3 so it wasnt the rain, must have been lots of houses putting the kettle on all at the same time ;D
-
This is an example how light rain affects my overhead line:
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fabload.de%2Fthumb%2Fsnrmargin-2014-04-05-idk53.png&hash=7595aa300e21c0461d1bf4bcbe921ace1c7e0225) (http://abload.de/img/snrmargin-2014-04-05-idk53.png)
On heavy rain and especially together with wind it sometimes gets even worse and random resyncs occur:
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fabload.de%2Fthumb%2Fsnrmargin-2014-05-01-r4jk8.png&hash=0c07355737edff9771a82735f79c93958a8fa957) (http://abload.de/img/snrmargin-2014-05-01-r4jk8.png)
-
Hi perry081064 I think this is a good time to download and start running HG612_Modem_stats and not because DSLstats is not any good, on the contrary the two software programs seems to complement each other, ones good for realtime and the other for in depth line monitoring over time.
What we would like to see is how your line stats is performing 24/7 for 4 weeks this will give BaldEagle1 a better understanding on on how your line is holding up.
-
Hi perry081064 I think this is a good time to download and start running HG612_Modem_stats and not because DSLstats is not any good, on the contrary the two software programs seems to complement each other, ones good for realtime and the other for in depth line monitoring over time.
What we would like to see is how your line stats is performing 24/7 for 4 weeks this will give BaldEagle1 a better understanding on on how your line is holding up.
Hi NewtronStar
because im running a pretty hungry gaming pc , i was wondering if it would be better to get my server running that as its going to be a lot less of a power drain and i can at least set it and forget it.
ill get it sorted to start graphing tonight ;)
-
Hi perry081064 I think this is a good time to download and start running HG612_Modem_stats and not because DSLstats is not any good, on the contrary the two software programs seems to complement each other, ones good for realtime and the other for in depth line monitoring over time.
What we would like to see is how your line stats is performing 24/7 for 4 weeks this will give BaldEagle1 a better understanding on on how your line is holding up.
Hi NewtronStar
because im running a pretty hungry gaming pc , i was wondering if it would be better to get my server running that as its going to be a lot less of a power drain and i can at least set it and forget it.
ill get it sorted to start graphing tonight ;)
:D yes a fully understand leaving a gaming PC on 24/7 those 200 watts start to become Kilowatts in 12 hours and thats just to get 24/7 stats, so yes setup your server to harvest the ongoing stats 24/7.
-
Hi perry081064 I think this is a good time to download and start running HG612_Modem_stats and not because DSLstats is not any good, on the contrary the two software programs seems to complement each other, ones good for realtime and the other for in depth line monitoring over time.
What we would like to see is how your line stats is performing 24/7 for 4 weeks this will give BaldEagle1 a better understanding on on how your line is holding up.
Hi NewtronStar
because im running a pretty hungry gaming pc , i was wondering if it would be better to get my server running that as its going to be a lot less of a power drain and i can at least set it and forget it.
ill get it sorted to start graphing tonight ;)
:D yes a fully understand leaving a gaming PC on 24/7 those 200 watts start to become Kilowatts in 12 hours and thats just to get 24/7 stats, so yes setup your server to harvest the ongoing stats 24/7.
actually , my server is an older dual core pc that isnt normally on 24/7 , its just for streaming as and when.
however i have and old laptop or i can use my daughters netbook if that will suffice ?
-
I completely agree with NS on the point of using HG612 modem stats to help provide the info for our resident boffin.
In the meantime would it be possible for you to provide the graphs from dslstats showing SNRM per band for upload and download around the time when the changes in SNRM occurred which resulted in your increase in upload and decrease in download. Also the point when this reverses aswell would be great.
-
actually , my server is an older dual core pc that isnt normally on 24/7 , its just for streaming as and when.
however i have and old laptop or i can use my daughters netbook if that will suffice ?
Anything XP Home version upward will suffice (manually editing the ini file), but dot net 4 upward does need to be installed to make full use of the programs' GUI element.
-
I completely agree with NS on the point of using HG612 modem stats to help provide the info for our resident boffin.
In the meantime would it be possible for you to provide the graphs from dslstats showing SNRM per band for upload and download around the time when the changes in SNRM occurred which resulted in your increase in upload and decrease in download. Also the point when this reverses aswell would be great.
hopefully these are what you require custard..
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi59.tinypic.com%2F23kyiz7.png&hash=e6a4e638404828a6d67a4dd4616a2866e035cef8)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi57.tinypic.com%2F208uwso.png&hash=45c979225b3e6cd445b42cb804baee01eac92f21)
-
actually , my server is an older dual core pc that isnt normally on 24/7 , its just for streaming as and when.
however i have and old laptop or i can use my daughters netbook if that will suffice ?
Anything XP Home version upward will suffice (manually editing the ini file), but dot net 4 upward does need to be installed to make full use of the programs' GUI element.
thanks for the heads up BE :)
ill get to work on setting up the laptop when i return home tomorrow afternoon.
... pretty sure it was running xp home version though.
-
another update...
seems my line resynced this morning around 8am
not much of a change , interleave depth has dropped just 2 points from 995 t0 993 on DS
....should i reboot anything yet ?
DSLAM/MSAN type: IFTN:0xb203 / v0xb203
Modem/router firmware: AnnexA version - A2pv6C035m.d22g
DSL mode: VDSL2
Status: Showtime
Uptime: 51 min 13 sec
Resyncs: 0 (since 09 May 2014 09:46:55)
Downstream Upstream
Attenuation (dB):
Connection speed (kbps): 50706 20000
SNR margin (dB): 6.1 6.2
Power (dBm): 12.9 6.4
Interleave depth: 993 1
INP: 3.00 0
RSCorr/RS (%): 0.0104 0.0790
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0.37 5.33
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 21782 Kbps, Downstream rate = 58324 Kbps
Path: 0, Upstream rate = 20000 Kbps, Downstream rate = 50706 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.8 6.4
VDSL2 framing
Path 0
B: 51 236
M: 1 1
T: 64 5
R: 12 16
S: 0.0326 0.3771
L: 15691 5410
D: 993 1
I: 64 255
N: 64 255
Counters
Path 0
OHF: 2897221 991594
OHFErr: 3 19
RS: 741567662 4292231
RSCorr: 41060 2012
RSUnCorr: 3 0
Path 0
HEC: 1 0
OCD: 0 0
LCD: 0 0
Total Cells: 592169768 0
Data Cells: 11931320 0
Drop Cells: 0
Bit Errors: 0 0
ES: 2 9
SES: 0 0
UAS: 18 18
AS: 6074
Path 0
INP: 3.00 0.00
PER: 2.08 6.12
delay: 8.00 0.00
OR: 91.93 203.67
Bitswap: 926 6
Total time = 1 hours 41 min 40 sec
FEC: 41060 2012
CRC: 3 19
ES: 2 9
SES: 0 0
UAS: 18 18
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 11 min 40 sec
FEC: 389 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 455 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 1 hours 41 min 40 sec
FEC: 41060 2012
CRC: 3 19
ES: 2 9
SES: 0 0
UAS: 18 18
LOS: 0 0
LOF: 0 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Since Link time = 1 hours 41 min 13 sec
FEC: 41060 2012
CRC: 3 19
ES: 2 9
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#
-
Looking at your snrm graphs it seems that the SNRM loss is across all download bands.
The increase in upload SNRM is for U2 only and does go back to its original level within minutes so I'm thinking it may just be the router misreporting that.
At quick glance of your current stats the resync was instigated on the router side rather than DSLAM (retrain reason=0). The router would not instigate a resync unless there was a loss of power or signal etc.
DLM resyncs have retrain reason 1 or 2.
Do you have any problems with the electrical supply to your house? i.e power outs.
I'd wait for BE1 to give the go ahead for any reboot...
Just a last question: does your hlog have a smooth decline?
-
Looking at your snrm graphs it seems that the SNRM loss is across all download bands.
The increase in upload SNRM is for U2 only and does go back to its original level within minutes so I'm thinking it may just be the router misreporting that.
At quick glance of your current stats the resync was instigated on the router side rather than DSLAM (retrain reason=0). The router would not instigate a resync unless there was a loss of power or signal etc.
DLM resyncs have retrain reason 1 or 2.
Do you have any problems with the electrical supply to your house? i.e power outs.
I'd wait for BE1 to give the go ahead for any reboot...
Just a last question: does your hlog have a smooth decline?
Hi Custard.
i think you may be right, it seems the router initiated a shutdown this morning and didnt gain internet access until 15 mins later.
the wife was around and didnt noticed any power outtage though and all clocks have kept the right time so i dont think it was a power cut , perhaps an outtage at the exchange or cab ?
... anyway , heres the Hlog as requested.
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi57.tinypic.com%2F2hek4rm.png&hash=067de93d91b6bea1f232c68c9198a1adca08f2fa)
-
The HLog looks fine.
Looking further at your stats it looks like you had a modem reboot not a resync as "Since Link time" is same as "Total time". If you had a resync then "Total time" would be higher than "Since Link time".
We don't normally see the modem reboot on its own unless a fault has occurred with the modem, or power has been lost or the firmware has been upgraded.
You haven't had a firmware upgrade as the version is still showing the same. An outage at the cab/exchange should not cause your modem to reboot.
BTagent in the firmware if installed can instigate a remote modem reboot i.e when automatically upgrading firmware.
-
BTagent in the firmware if installed can instigate a remote modem reboot i.e when automatically upgrading firmware.
i see where you are coming from , however this firmware has the btagent removed ( unless it can access some other way)
however , i found this in the router logs...
"Couldn't get channel number: Transport endpoint is not connected" , and on checking google it seems one customer had a short in the cable going to the pole causing the disconnects and was getting the same message.
if its of any value though, it seems he was using the same router as me , a billion 7800n with firmware 1.06h.
-
I would not be happy with an Hlog like that perry081064 there seems to be two large missing chunks of tones at -97dB, I will upload my Hlog as a guide.
-
I don't think that's a problem NS, He just does not seem to be showing upstream frequencies for hlog and QLN. Probably just needs to adjust a setting in dslstats to bring them up.
-
thanks, i can see the difference , however as im new to all this i wouldnt know what a hlog is even showing me let alone if its showing errors.
i think i seriously need to start learning fast :-[
... so whats it all mean, im clueless to be honest :(.
-
I don't think that's a problem NS, He just does not seem to be showing upstream frequencies for hlog and QLN. Probably just needs to adjust a setting in dslstats to bring them up.
Your spot on Custard ;D
-
I don't think that's a problem NS, He just does not seem to be showing upstream frequencies for hlog and QLN. Probably just needs to adjust a setting in dslstats to bring them up.
Your spot on Custard ;D
i had got everything ticked to be honest so i dont know why they arent showing :-[
-
i had got everything ticked to be honest so i dont know why they arent showing :-[
Me thinks this maybe due to the way older firmware is perceived by the stats software, I do have the latest HG612 firmware installed.
-
i had got everything ticked to be honest so i dont know why they arent showing :-[
probably because the DSLAM is configured not to report this values.
-
Me thinks this maybe due to the way older firmware is perceived by the stats software, I do have the latest HG612 firmware installed.
I plan to downgrade to the older firmware later tonight so i'll let you know if that's the case...
In the meantime Perry could you upload the QLN data or HLog data from the tabs under telnet data incase the modem is not reporting it to dslstats.
Otherwise if you are familiar with using hyperterminal or putty then telnet into the router and send these commands after logging in:
sh
xdslcmd info --QLN
xdslcmd info --Hlog
-
i had got everything ticked to be honest so i dont know why they arent showing :-[
probably because the DSLAM is configured not to report this values.
That could be the case! I was finding a similar issue for upload data with the ECI/r and ECI/I. They seem not to report the values from the MSAN.
-
Me thinks this maybe due to the way older firmware is perceived by the stats software, I do have the latest HG612 firmware installed.
I plan to downgrade to the older firmware later tonight so i'll let you know if that's the case...
In the meantime Perry could you upload the QLN data or HLog data from the tabs under telnet data incase the modem is not reporting it to dslstats.
Otherwise if you are familiar with using hyperterminal or putty then telnet into the router and send these commands after logging in:
sh
xdslcmd info --QLN
xdslcmd info --Hlog
im only allowed to send 2000 chars , no matter how i try i cant upload those to website or send them via pm :no:
...if you could pm me an email address, i will send them via that if thats acceptable?
-
How about saving it in notepad and attaching the txt file?
You asked about what HLog shows.
It can show signs of a bridge tap. This can be detected by a erratic decline in the HLOg. The bridge tap is extra cabling in the wiring between modem and the cabinet. An example would be an extension running from behind the master socket.
-
How about saving it in notepad and attaching the txt file?
oops sorry, i was having a blonde moment :-[
attachments enclosed .
-
I've had a glance at your hlog data and it does not show any upload tones. It does not look like an issue with dslstats so either what Morphium or NS said would be right.
-
I've had a glance at your hlog data and it does not show any upload tones. It does not look like an issue with dslstats so either what Morphium or NS said would be right.
thanks :)
-
The text data copied from DSLstats is just the raw data as received from the modem. As already said, all the upstream data is missing, so this is either a modem firmware issue or the DSLAM doesn't report those values. Most probably the latter.
-
The text data copied from DSLstats is just the raw data as received from the modem. As already said, all the upstream data is missing, so this is either a modem firmware issue or the DSLAM doesn't report those values. Most probably the latter.
thanks roseway :)
-
Ok I've just downgraded my firmware and lo and behold my upstream data is missing so it seems like a firmware issue as mentioned by NS.
Thanks for the great program Roseway BTW. :)
-
Ok I've just downgraded my firmware and lo and behold my upstream data is missing so it seems like a firmware issue as mentioned by NS.
Thanks for the great program Roseway BTW. :)
thanks for checking that out Custard ;)
...still undecided whether to upgrade to the latest firmware or leave it a while longer :-\
-
Ok I've just downgraded my firmware and lo and behold my upstream data is missing so it seems like a firmware issue as mentioned by NS.
Thanks for the great program Roseway BTW. :)
thanks for checking that out Custard ;)
...still undecided whether to upgrade to the latest firmware or leave it a while longer :-\
well lets go back to yout original post on this thread it was made on the 1st of may 2014 and its the 9th of may (8 days) so if your going to give the DLM time to adjust you need to wait a mininium of 14 days, so I would wait until the 14th of May before upgrading to the new Firmware it all depends when your HG612 last did a re-sync/retrain.
-
Ok I've just downgraded my firmware and lo and behold my upstream data is missing so it seems like a firmware issue as mentioned by NS.
Thanks for the great program Roseway BTW. :)
thanks for checking that out Custard ;)
...still undecided whether to upgrade to the latest firmware or leave it a while longer :-\
well lets go back to yout original post on this thread it was made on the 1st of may 2014 and its the 9th of may (8 days) so if your going to give the DLM time to adjust you need to wait a mininium of 14 days, so I would wait until the 14th of May before upgrading to the new Firmware it all depends when your HG612 last did a re-sync/retrain.
yes i think thats best, actually i may well give it all of may just to be sure ;)
-
yes i think thats best, actually i may well give it all of may just to be sure ;)
I am glad to here that. their is one thing about FTTC & monitering your line stats is you need the patients of a Saint :( others may dive in and then create a thread saying my download has droped in the last week after unlocking or updating my HG612 (I wonder why) ::)
-
seeing as im going to leave alone until at least the end of may , ive installed HG612_Modem_stats on my server to collect stats for the next 31 days.
... only problem im having is i cant run dslstats from my pc as it says it cant comunicate with the modem.
only happens when i running HG612_Modem_stats at the same time on the server though.
-
just a quick update..
having set up HG612_modem_stats on the server pc and collected data for the last day , i just want to test ive got everything set to gather correctly.
i will be collecting data until the end of may.
is this everything i need to collate ?
thanks
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi58.tinypic.com%2Ffepd8k.png&hash=69c7f3bc0d4e7a02b0883dc35fc0d3024ccd0656)
-
just a quick update..
having set up HG612_modem_stats on the server pc and collected data for the last day , i just want to test ive got everything set to gather correctly.
i will be collecting data until the end of may.
is this everything i need to collate ?
That looks right, but you can also obtain 'snapshot' graphs.
V 2.1 of HG612 Modem Stats is due to be released in the next few days.
V 2.1 includes a little more data & functionality & is (hopefully) more reliable than v 2.0.
BTW, for easier 'zoomed in' viewing by others, you can attach the Full__Monty Ongoing montage & the snapshot montage to posts in this forum.
EDIT:
I see you attached the Ongoing montage while I was typing.
-
... only problem im having is i cant run dslstats from my pc as it says it cant comunicate with the modem.
only happens when i running HG612_Modem_stats at the same time on the server though.
Hmmm.
I wonder if the clocks on your server & PC are slightly out of sync.
i.e. the 2 programs might actually be clashing with each other, despite using HG612 Modem Stats compatibility mode in DSLStats.
Either that or maybe they both need to run on the same machine to ensure clashes are avoided?
-
Your DS SNRM looks a bit 'spiky' on 3 occasions this morning.
Any idea what might have casused that?
-
Your DS SNRM looks a bit 'spiky' on 3 occasions this morning.
Any idea what might have casused that?
theres quite a few rain showers occuring here, some heavier than others. other than that ive no idea :-\.
-
I notice that your download output power is oscillating. I don't know whether this is normal or indicative of some fault in the modem or cabling.
I don't see this on my stats. Maybe the others can comment on this...
I also don't see anything oscillating on the individual bands though for download.
edit: I do see slight changes in my older graphs so maybe its nothing to worry about. :-\
-
just putting up a few stats from the past 5 days.
as already stated, im around 300 meters from my cab and the stats included are based on the weather for the last 3 out of five days being heavy showers.
my line is brand new from the pole, fitted 1 year ago, and is connected directly to the NTE5 with no extensions running, directly to the HG612 and from there to my billion 7800n router.
no powerline adaptors are fitted , everything is connected by ethernet cat 5e.
...although ive only got 5 days stats so far, ive had the HG612 connected and monitored for the past 14 days, and other than a reboot of the modem 5 days ago (unknown as to why as it wasnt a resync or any noticable power cut ) the stats have stayed stable other than a noticable rise in attainable speed and SNRM over the past 24 hours.
just wondering if anyone can see anything amiss that would have caused my interleaving ( other than running a HH5 previously that would like like to constantly resync) and could tell me if im likely to see interleaving reduced or taken off soon ?
of course, ill continue to collect the stats until the end of may , but would like to power down the server asap once anything is picked up to to electric costs of running the pc 24/7.
-
I can see relatively quite a lot of US Error seconds & US RSCorr/FEC errors, despite your connection achieving the full 20 Mbps US sync speed.
We don't often suuch such high US sync speeds with such relatively low DS sync speeds.
You do have a little spare DS SNRM, but not much to suggest massive improvements in sync speed.
Your QLN graph indicates a fairly steady, but highish level of background 'noise'.
-140 dBm is the 'ideal' quiet line level.
That on its own could be the reason for not having much in the way of spare DS SNRM and/or the lowish DS sync speed.
Can you hear any background hissing or humming on a quiet line phone test?
There's also quite a bit of bitswapping going on for a non-updated firmware version.
Line Attenuation isn't fantastic, but I have seen worse.
Unfortunately, the non-updated modem firmware doesn't show the 'real' DS Signal Attenuation values per band in the pbParams data, but I imagine they will actually be significantly higher than the levels shown.
I can also see smallish, but constant US SNRM fluctuations.
Do you have any ideas as to what might have caused the jumps in DS SNRM on 11th & 12th?
I'm hoping to release v 2.1 of my programs during this week.
Perhaps that might be a good time for you to try one of the updated firmware version?
FWIW, to keep the time shown along the x axis 'constant', plotting periods of 2, 3, 4, 6 12, 24 days/hours assists in determining patterns etc.
-
I can see relatively quite a lot of US Error seconds & US RSCorr/FEC errors, despite your connection achieving the full 20 Mbps US sync speed.
We don't often suuch such high US sync speeds with such relatively low DS sync speeds.
You do have a little spare DS SNRM, but not much to suggest massive improvements in sync speed.
Your QLN graph indicates a fairly steady, but highish level of background 'noise'.
-140 dBm is the 'ideal' quiet line level.
That on its own could be the reason for not having much in the way of spare DS SNRM and/or the lowish DS sync speed.
Can you hear any background hissing or humming on a quiet line phone test?
QLN phone test is quiet, even using a dect phone
There's also quite a bit of bitswapping going on for a non-updated firmware version.
Line Attenuation isn't fantastic, but I have seen worse.
Unfortunately, the non-updated modem firmware doesn't show the 'real' DS Signal Attenuation values per band in the pbParams data, but I imagine they will actually be significantly higher than the levels shown.
I can also see smallish, but constant US SNRM fluctuations.
Do you have any ideas as to what might have caused the jumps in DS SNRM on 11th & 12th?
only that it tended to rain heavier during those periods
I'm hoping to release v 2.1 of my programs during this week.
Perhaps that might be a good time for you to try one of the updated firmware version?
im willing to give that a try :)
FWIW, to keep the time shown along the x axis 'constant', plotting periods of 2, 3, 4, 6 12, 24 days/hours assists in determining patterns etc.
understood
Many thanks for taking the time to check things over BE1 , i shouldnt complain , theres a lot worse off than me. im hoping it just doesnt get any worse.
..... having said that , if it does, ill go with virgin media as im fully cabled for that and theres one of their green cabs outside my drive.
-
just to update:
17 days without a resync now ( so the HG612 is keeping BT out at least ) , i was resyncing 2 times a week on the HH5.
the router says 30 days, due to what i suspect was a power issue in the area causing the HG612 to reboot ( hence only 17 days uptime).
i havent been able to constantly monitor stats as leaving the pc on all this time would = a massive electric bill , however from my own observation, nothing much has changed from the stats already provided in this thread.
interleaving hasnt budged from IMP 3.0 / depth 993 downstream. upstream not interleaved.
speedtesting gives a download speed of 47 Mbps constant throughout the 17 days with no variation .
SNR margin never drops below 6.0 averaging around 6.4 on downstream.
so , whats the best way to go now ?..
should i leave well alone and continue to monitor and hope interleave relents ( if at all)
reboot the router or modem ( not sure if this would help to nudge something along or make it worse)
update to the latest firmware for the HG612.
-
Apparently, 14 days of a stable connection with low error counts is often the time when DLM decides to try removing Interleaving and/or increase sync speeds.
You don't have much in the way of spare SNRM, so a simple modem reboot is unlikely to deliver much.
I would suggest now trying an updated firmware version as that does apper to improve matters (on some connections).
e.g. increased bitswapping & so on, which in turn possibly results in fewer CRC/UnCorrected type errors.
Updating the firmware to a current version will obviously cause a modem reboot, but I reckon it's an experiment worth trying (nothing ventured, nothing gained eh?).
-
Hi perry081064 your DS & US Bitswaps Graph really caught my eye, see how during the morning your swaps are at it's lowest point at 9am and as the evening starts to arrive the swaps start to climb and by 22:30pm the swaps are at there highest point :-\
-
Thanks for your feedback guys :)
BE1 and NewtronStar , you have both made some very valid points , i didnt think a simple reboot would help either , but just wanted a second opinion.
also , as BE1 states, theres not much leeway in SNRM to make much of a difference anyway.
i wasnt sure how long to wait for a resync , but it seems as mentioned , i should have seen a possible resync within 14 days stable , its coming up to 18 days now, and not a sign of anything occuring.
NewtronStar , the bitswap graphs are something ive been mainly watching too, and they have been following the path you mention , however by 11pm seem to settle down again.
dont get me wrong guys, im happy to be getting the 47 Mbps downspeed , an increase back to 60 would be great too , however i dont want to do anything thats liable to make it any worse.
i think ill give it 20 days , then i will try the latest firmware ..can anyone point me in the right direction to the steps required as ive never done a firmware upgrade before as i bought the HG612 already unlocked.
thanks again for all the help guys :)
-
can anyone point me in the right direction to the steps required as ive never done a firmware upgrade before as i bought the HG612 already unlocked.
Hmmm perry I would would have thought you'd flashed that HG612 yourself, anyway it not a big deal but you need to follow the Instruction's by the book !
You will need to get latest firmware file and save it to you computer first.
and read through this tutorial http://www.kitz.co.uk/routers/hg612unlock.htm (http://www.kitz.co.uk/routers/hg612unlock.htm)
Regards
NS
-
can anyone point me in the right direction to the steps required as ive never done a firmware upgrade before as i bought the HG612 already unlocked.
Hmmm perry I would would have thought you'd flashed that HG612 yourself, anyway it not a big deal but you need to follow the Instruction's by the book !
You will need to get latest firmware file and save it to you computer first.
and read through this tutorial http://www.kitz.co.uk/routers/hg612unlock.htm (http://www.kitz.co.uk/routers/hg612unlock.htm)
Regards
NS
i prob would have if i could have got a cheap locked one at the time :)
thanks, that was the link i was looking for, cheers mate !
-
Apparently, 14 days of a stable connection with low error counts is often the time when DLM decides to try removing Interleaving and/or increase sync speeds.
You don't have much in the way of spare SNRM, so a simple modem reboot is unlikely to deliver much.
I would suggest now trying an updated firmware version as that does apper to improve matters (on some connections).
e.g. increased bitswapping & so on, which in turn possibly results in fewer CRC/UnCorrected type errors.
Updating the firmware to a current version will obviously cause a modem reboot, but I reckon it's an experiment worth trying (nothing ventured, nothing gained eh?).
i decided not to wait any longer :baby:
firmware is now updated as from this morning ( 27th May 2014).
server is being switched on in a minute or two to start collecting stats from HG612 Modem Stats , will try DSLstats on my main pc too but it usually crahes out if they are both going.
stats on day1
Stats recorded 27 May 2014 11:19:38
DSLAM/MSAN type: IFTN:0xb203 / v0xb203
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2
Status: Showtime
Uptime: 40 min 55 sec
Resyncs: 0 (since 27 May 2014 10:43:53)
Downstream Upstream
Attenuation (dB): 18.2 0.0
Connection speed (kbps): 51601 20000
SNR margin (dB): 6.3 6.3
Power (dBm): 13.1 6.4
Interleave depth: 1009 1
INP: 3.00 0
RSCorr/RS (%): 0.0004 0.0044
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0.29 4.60
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 21951 Kbps, Downstream rate = 59092 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 51601 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): 6.3 6.3
Attn(dB): 18.2 0.0
Pwr(dBm): 13.1 6.4
VDSL2 framing
Bearer 0
MSGc: 18 150
B: 51 236
M: 1 1
T: 64 5
R: 12 16
S: 0.0321 0.3771
L: 15968 5410
D: 1009 1
I: 64 255
N: 64 255
Counters
Bearer 0
OHF: 1192159 400855
OHFErr: 0 3
RS: 305069576 272926
RSCorr: 1224 12
RSUnCorr: 0 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 243646123 0
Data Cells: 2600353 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 3
SES: 0 0
UAS: 26 26
AS: 2456
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.06 6.15
OR: 93.19 202.87
AgR: 51694.07 20203.27
Bitswap: 1664/1664 0/0
Total time = 41 min 22 sec
FEC: 1224 12
CRC: 0 3
ES: 0 3
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 11 min 22 sec
FEC: 461 6
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 332 6
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 41 min 22 sec
FEC: 1224 12
CRC: 0 3
ES: 0 3
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 40 min 55 sec
FEC: 1224 12
CRC: 0 3
ES: 0 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
wish me luck :-\
-
i decided not to wait any longer :baby:
firmware is now updated as from this morning ( 27th May 2014).
server is being switched on in a minute or two to start collecting stats from HG612 Modem Stats , will try DSLstats on my main pc too but it usually crahes out if they are both going.
wish me luck :-\
See that was not so hard you don't need any luck you have successfully flashed a new firmware into the HG612 -> Modem/router firmware: AnnexA version - A2pv6C038m.d24j
Well done ;D
As for the crashes you will need the Help of Roseway and BaldEagle1 and I think if you have two DSLstats running together on same PC it causes it to crash when running it on a server, I am not well versed on this issue so they will help you ;)
-
See that was not so hard you don't need any luck you have successfully flashed a new firmware into the HG612 -> Modem/router firmware: AnnexA version - A2pv6C038m.d24j
Well done ;D
As for the crashes you will need the Help of Roseway and BaldEagle1 and I think if you have two DSLstats running together on same PC it causes it to crash when running it on a server, I am not well versed on this issue so they will help you ;)
nah , it wasnt hard , i was just lazy and just purchased one pre flashed .
didnt know at the time that it would prob need reflashing anyway as i thought it was the latest firmware at the time lol.
ive got both the stats programs running through the server now, and no crashes on any of them.
it only crashes DSLstats when i run it through any pc when modem stats is running on the server.
on a good note, for around 9 hours uptime , im not seeing as many errors....yet.
...will upload some graphs after 24 hours.
-
nah , it wasnt hard , i was just lazy and just purchased one pre flashed .
didnt know at the time that it would prob need reflashing anyway as i thought it was the latest firmware at the time lol.
Thats ok, now you know how to find which firmware is installed on the HG612, It looks like when you purchased the HG612 is was using the older firmware but it may have been updated by the BT agent soon after you powerd it up & connected the DSL cable.
There are some members here that block the firmware updates coming in and find the older firmware works better for them, for me on a longer line the A2pv6C038m.d24j feels better ;)
-
stats after 24 hours.
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi58.tinypic.com%2F2d11xyd.png&hash=86c21c033025ad9c5b0e13b003958e1ccc3084d4)
feel free to ask to see any other graphs guys :)
-
It might be interesting if you could zip & post the Plink logs from the 2 snapshot montages you have posted in this thread.
Also, ongoing graphs/modem_stats.logs over a few days may highlight any differences between the 2 different modem firmware versions.
From the version number (4.1) as shown in your graphs, it looks like you are still using an older version of the HG612 Modem Stats programs.
v 2.11 is on its way - as soon as I get the relevant debugging logs back from a couple of users currently testing it out & if it appears to be reliable (unless you want me to post the latest programs for you to try out).
-
It might be interesting if you could zip & post the Plink logs from the 2 snapshot montages you have posted in this thread.
Also, ongoing graphs/modem_stats.logs over a few days may highlight any differences between the 2 different modem firmware versions.
From the version number (4.1) as shown in your graphs, it looks like you are still using an older version of the HG612 Modem Stats programs.
v 2.11 is on its way - as soon as I get the relevant debugging logs back from a couple of users currently testing it out & if it appears to be reliable (unless you want me to post the latest programs for you to try out).
thats strange , i checked the updaters and they say they are up to date :-\ , however if you find the time to send them, i will be pleased to try out the latest version :)
attachment as requested
-
Just for fun Perry I'll upload my line stats and you can compare your line with my 850/1000m line still not 100% sure my of true distance to cabinet :blush:
-
Just for fun Perry I'll upload my line stats and you can compare your line with my 850/1000m line still not 100% sure my of true distance to cabinet :blush:
lol mate , its wasted on me as im still trying to get my head around what all the stats graphs mean myself ... i knew i should have behaved myself in school all those years ago :blush:
its hard to work yours out as you are still recovering from interleave , but from what i can make out, its not looking too bad for a line of that length .
as for mine , i can make out the cab in the distance at the far end of the field from my upstairs window. google maps says its around 300 meters if i take the road way to it.
-
lol mate , its wasted on me as im still trying to get my head around what all the stats graphs mean
Perry there is not a 100 page manual that I know for understanding the stats, and the best place to start is on the Kitz forum http://www.kitz.co.uk/adsl/linestats.htm (http://www.kitz.co.uk/adsl/linestats.htm) it's related to ADSL but most is still relevant to FTTC apart from attenuation.
-
thats strange , i checked the updaters and they say they are up to date :-\ , however if you find the time to send them, i will be pleased to try out the latest version :)
Ah. I think you are referring to the GUI version.
This is the version I'm using:-
V2.1 created 22/05/2014 20:06:12
Are you on the same version?
However, the updater only updates the GUI, not the logging/graphing programs.
I'll have a think about how best to automate the other program updates (unless Ronski beats me to it - hint, hint!!! ;)).
Your DS sync speeds & SNR/SNRM seem a shade low for the line length.
It could actually take a detour before it gets to your home.
Mine goes past my home to a footpath joint chamber before coming back to the pole mounted DP directly across the road from me.
Also, the full 20 Mbps US sync speed isn't too often achieved when DS sync speed is as low as yours.
However, the updated firmware tells us that DS Signal Attenuation is worse than Line Attenuation in the D1 band.
That could explain the low(ish) DS sync speed.
The older firmware incorrectly always reported identical DS Line & Signal attenuation levels:-
Old firmware:-
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: 21861 kbps 61364 kbps
Actual Aggregate Tx Power: 6.4 dBm 13.1 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 1.0 24.4 38.2 N/A 12.8 31.9 50.7
Signal Attenuation(dB): 1.0 24.2 38.0 N/A 12.8 31.9 50.7
SNR Margin(dB): 6.7 6.4 6.1 N/A 6.8 6.9 6.9
TX Power(dBm): -5.1 -20.7 6.1 N/A 9.7 7.4 7.2
New 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) (882,1193) (1984,2770)
DS: (41,857) (1218,1959) (2795,4083)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 22160 kbps 59564 kbps
Actual Aggregate Tx Power: 6.4 dBm 13.1 dBm
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 1.2 24.3 38.3 N/A N/A 12.9 32.0 50.9
Signal Attenuation(dB): 1.2 24.2 38.2 N/A N/A 17.5 31.8 50.9
SNR Margin(dB): 7.0 7.0 6.3 N/A N/A 6.4 6.4 6.4
TX Power(dBm): -5.1 -20.7 6.1 N/A N/A 9.7 7.7 7.2
The likeliest culprit for the increased signal attenuation in the D1 band is crosstalk from other VDSL2 or ADSL connections.
But, there could be other issues such as RFI etc.
You have no doubt spotted the band plan tone changes & removal of the 'shared' tones etc.
Other subtle differences have been noticed with the updated modem firmware such as increased bitswapping.
That was initially thought to indicate a problem.
But it does appear to have improved connection stability for most users, maybe because increased bitswapping to use previously unavailable tones (subject to 'noise' conditions etc.) now causes fewer errors?
A number of users have also seen a return to fatspath connections with the updated firmware following many months of Interleaving.
I saw that for a few weeks until what appears to have been another user being connected that reduced my SNRM & eventually the connection resynced with a low(ish) level of interleaving applied.
The best way to track any such changes is to leave the ongoing stats logging running 24/7 (if that is a viable option).
Anyway, could you post your HG612_stats.ini file to confirm whether or not it is fully ready for the newer programs & user relocated event/error log folders, choice of modem & so on?
If not, it can be manually edited or updated via the GUI (possibly needing the every minute task to be deleted & then recreated).
The latest versions of the programs are attached.
-
thats strange , i checked the updaters and they say they are up to date :-\ , however if you find the time to send them, i will be pleased to try out the latest version :)
Ah. I think you are referring to the GUI version.
This is the version I'm using:-
V2.1 created 22/05/2014 20:06:12
Are you on the same version?
HG612 Modem logs stats viewer & settings editor V2.1 created 20/05/2014 19:36:56
Version 2.1.5253.9955 running on Microsoft Windows 7 Home Premium
However, the updater only updates the GUI, not the logging/graphing programs.
I'll have a think about how best to automate the other program updates (unless Ronski beats me to it - hint, hint!!! ;)).
Your DS sync speeds & SNR/SNRM seem a shade low for the line length.
It could actually take a detour before it gets to your home.
Mine goes past my home to a footpath joint chamber before coming back to the pole mounted DP directly across the road from me.
i recall the BTO engineer showing me a handheld meter and recall him saying i was around 300 meters from the cab, that also tallies with my google maps ( give or take 50 meters or so)
Also, the full 20 Mbps US sync speed isn't too often achieved when DS sync speed is as low as yours.
However, the updated firmware tells us that DS Signal Attenuation is worse than Line Attenuation in the D1 band.
That could explain the low(ish) DS sync speed.
The older firmware incorrectly always reported identical DS Line & Signal attenuation levels:-
Old firmware:-
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: 21861 kbps 61364 kbps
Actual Aggregate Tx Power: 6.4 dBm 13.1 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 1.0 24.4 38.2 N/A 12.8 31.9 50.7
Signal Attenuation(dB): 1.0 24.2 38.0 N/A 12.8 31.9 50.7
SNR Margin(dB): 6.7 6.4 6.1 N/A 6.8 6.9 6.9
TX Power(dBm): -5.1 -20.7 6.1 N/A 9.7 7.4 7.2
New 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) (882,1193) (1984,2770)
DS: (41,857) (1218,1959) (2795,4083)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 22160 kbps 59564 kbps
Actual Aggregate Tx Power: 6.4 dBm 13.1 dBm
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 1.2 24.3 38.3 N/A N/A 12.9 32.0 50.9
Signal Attenuation(dB): 1.2 24.2 38.2 N/A N/A 17.5 31.8 50.9
SNR Margin(dB): 7.0 7.0 6.3 N/A N/A 6.4 6.4 6.4
TX Power(dBm): -5.1 -20.7 6.1 N/A N/A 9.7 7.7 7.2
The likeliest culprit for the increased signal attenuation in the D1 band is crosstalk from other VDSL2 or ADSL connections.
But, there could be other issues such as RFI etc.
i would imagine crosstalk is the main issue. on doing some research, it appears the cab is around 2 years old now and i moved here around this time last year. lots of people moving away from virgin media because of issues with slow speeds going to BT infinity so prob the cab is getting full.
You have no doubt spotted the band plan tone changes & removal of the 'shared' tones etc.
yes i saw the tone changes , not sure what 'shared' tones are yet , im still learning :-[
Other subtle differences have been noticed with the updated modem firmware such as increased bitswapping.
That was initially thought to indicate a problem.
But it does appear to have improved connection stability for most users, maybe because increased bitswapping to use previously unavailable tones (subject to 'noise' conditions etc.) now causes fewer errors?
its early days , but i think its giving less errors... also it appears in my logs that i had a resync yesterday that increased the Downstream rate to 51601 Kbps , it stored this in a stat folder called RESYNC and inside the folder is a plink file.
A number of users have also seen a return to fatspath connections with the updated firmware following many months of Interleaving.
I saw that for a few weeks until what appears to have been another user being connected that reduced my SNRM & eventually the connection resynced with a low(ish) level of interleaving applied.
The best way to track any such changes is to leave the ongoing stats logging running 24/7 (if that is a viable option).
yeah, to hell with it... ill leave the server on ;)
Anyway, could you post your HG612_stats.ini file to confirm whether or not it is fully ready for the newer programs & user relocated event/error log folders, choice of modem & so on?
attached
If not, it can be manually edited or updated via the GUI (possibly needing the every minute task to be deleted & then recreated).
The latest versions of the programs are attached.
thanks, i wont update anything until you have checked the ini :)
..... and cheers BE1 for all the help , im sure ill get there in the end .
-
HG612 Modem logs stats viewer & settings editor V2.1 created 20/05/2014 19:36:56
Version 2.1.5253.9955 running on Microsoft Windows 7 Home Premium
I have attached my version for you.
i recall the BTO engineer showing me a handheld meter and recall him saying i was around 300 meters from the cab, that also tallies with my google maps ( give or take 50 meters or so)
The likeliest culprit for the increased signal attenuation in the D1 band is crosstalk from other VDSL2 or ADSL connections.
But, there could be other issues such as RFI etc.
i would imagine crosstalk is the main issue. on doing some research, it appears the cab is around 2 years old now and i moved here around this time last year. lots of people moving away from virgin media because of issues with slow speeds going to BT infinity so prob the cab is getting full.
That could be the reason then.
I lost around 10 Mbps from my 30 Mbps connection over 1100m or so over a period of around 12 months.
You have no doubt spotted the band plan tone changes & removal of the 'shared' tones etc.
yes i saw the tone changes , not sure what 'shared' tones are yet , im still learning :-[
The 'shared' tones were when the U0 & D1 band plans overlapped with the older firmware:-
US: (0,95) (880,1195) (1984,2771)
DS: (32,859) (1216,1959) (2792,4083)
They are now completely separated:-
US: (6,31) (882,1193) (1984,2770)
DS: (33,857) (1218,1959) (2795,4083)
its early days , but i think its giving less errors... also it appears in my logs that i had a resync yesterday that increased the Downstream rate to 51601 Kbps , it stored this in a stat folder called RESYNC and inside the folder is a plink file.
Let's hope it remains that way.
yeah, to hell with it... ill leave the server on ;)
Even if you only do that for a few days, you'll then at least have a base line for future comparisons.
Anyway, could you post your HG612_stats.ini file to confirm whether or not it is fully ready for the newer programs & user relocated event/error log folders, choice of modem & so on?
attached
That looks fine.
I can't now recall what Ronski did for the newer GUI version, but I think it had something to do with an error in its reported stats that some users experienced
thanks, i wont update anything until you have checked the ini :)
..... and cheers BE1 for all the help , im sure ill get there in the end
It looks like all you need to do is switch to the latest attached GUI & then start using the programs I attached earlier on.
You will get there in the end.
I knew absolutely nothing about how broadband works, errors, SNRM until I got FTTC & saw speeds & stability deteriorate rapidly after the first month of up to 35 Mbps sync speed.
That's why I created the original graphing scripts, later becoming programs, in order to prove there actually was a line fault to Plusnet.
The fault was eventually fixed some 11 months later.
7 months later again was when I first dtarted seeing the effects of crosstalk.
-
updated :)
-
That's good.
There's also a new graph in the timestamped subfolder of the Current_Stats folder, named Bits_with_SNR-20140529-0700-HIGH_RES.png
Example attached.
-
That's good.
There's also a new graph in the timestamped subfolder of the Current_Stats folder, named Bits_with_SNR-20140529-0700-HIGH_RES.png
Example attached.
found it , heres mine :)
-
just an update regarding my stats over the last seven days using the latest firmware for the HG612.
cant see much difference if im honest , ive had just the 1 resync since changing firmware and that was later on in the afternoon. (shows itself in plink log but not on GUI though)
still doesnt want to let go of interleave or even reduce it it seems :(
most of the time its been raining if that makes any difference in what you see on the graphs, other than that ive nothing else to report.
ill be changing server over the next few days so i cannot continue to log using this one so these will be the last ones until im up and running on the new one.
any feedback is apreciated .
-
It's not to easy to say with a lot of confidence, but some of the stats appear to have changed a little since you updated the firmware e.g. DS bitswapping to mention just one of them.
Could you run graphpd for a longer period i.e to also include a few days of stats from the older fimware?
We might then find it easier to spot in a single montage if anything has changed significantly.
-
It's not to easy to say with a lot of confidence, but some of the stats appear to have changed a little since you updated the firmware e.g. DS bitswapping to mention just one of them.
Could you run graphpd for a longer period i.e to also include a few days of stats from the older fimware?
We might then find it easier to spot in a single montage if anything has changed significantly.
new server isnt coming til tomorrow, so booted the old one back up to get you these.
(updated HG612 firmware was installed on 27th may)
thanks for taking the time to look over them :)
-
DS bitswapping has increased, which is probably helping.
DS Signal attenuation has worsened, although I don't think it was actually reported correctly in the older firmware version.
US SNRM is stil fluctuating quite a bit & US errored seconds are relatively high(ish), probably as a consequence, although you are syncing at 20 Mbps.
DS Interleaving depth has increased slightly - probably due to the increased sync speed.
If a stable connection is maintained with quite low DS CRC, RSUncorr & DS HEC errors, DLM may relent a little & lower Interleaving depth, also increasing sync speed slightly.
DLM very quickly reduces sync speed & increases Interleaving depth when 'problems' are recorded to it (high error counts etc.), but it tends to take quite a while of stability before it deems that a connection is worthy of trying higher sync speeds etc.
14 days appears to be a typical waiting period (unless DLM has already decided your current sync speeds & Interleaving depth are permanently necessary in order to provide a stable, but fairly high sync speed).
Ifyou don't wish to continue logging 24/7, it may be worth manually running or scheduling the snapshot graphs at the same times every day or couple of days or so in order to detect any changes in performance over a period of time.
Personally, I couldn't cope without knowing my stats are being recorded 24/7 (just in case any issues are causing problems), but that's probably because of the 11 months of intermittent disconnections that I endured, which were initially denied by my ISP as they weren't showing in their own logs.
Thankfully, based on my graphical & raw data 'evidence' they eventually accepted that HG612s on VDSL2 connections can & do resync very quickly, often 'too' quickly to force a new PPPoE session & numerous BTOR Engineer vists were arranged accordingly (all at no cost to me).
Their own connection logs only show PPPoE sessions ending & restarting (or at least that's all they showed back in 2011/2012).
Fingers crossed for you that the updated firmware (in my humble opinion much 'better' firmware) will allow some improvements.
-
Thanks BE1 :)
It does take a trained eye to be able to work it all through and my lack of concentration doesnt help iether :-[.
im getting my head around the graphs , its just learning what and how the results shown show if something is loose, noise , rfi etc... thats going to take a little longer to learn :-[
initially, without even taking your assessment into account, i would say this firmware is treating me a lot better than the old one.
its still early days but i suspect interleave will relent eventually though.
rest assured though , im going to be running the stats 24/7 365 once my new (low wattage ;) ) server is up and running , its being setup as i type and should be online later tonight .
like yourself, i dont think i could go back to not be able to keep an eye on things ;)
one final point...
its you and the other peeps on this forum that make the whole journey worth while, and for that im extremely grateful.
thanks again.
-
initially, without even taking your assessment into account, i would say this firmware is treating me a lot better than the old one.
its still early days but i suspect interleave will relent eventually though.
Hi perry your Interleave Depth should decrease with the HG612 modem kept on 24/7, I had an issue in early may which caused my Interleaving to increase from 500 to 1200 and the INP: from 3 to 8, it took longer than expected 17 days but I did turn off the HG612 modem during the 14 days wait and it's all back to normal ;D
-
Hi perry your Interleave Depth should decrease with the HG612 modem kept on 24/7, I had an issue in early may which caused my Interleaving to increase from 500 to 1200 and the INP: from 3 to 8, it took longer than expected 17 days but I did turn off the HG612 modem during the 14 days wait and it's all back to normal ;D
hope so , coming up to 24 days now with no change as yet ( interleaved at 1009 imp 8 )
and no resync at all in that timeframe.
-
31 days and still no change >:(
..... may be best to update monthly methinks :(
all in all though , if nothing else, getting rid of the HH5 stopped all the drop outs , speeds havent flinched since getting rid of that :).
-
its been 34 days now and to be honest i cant see anything changing.
should i power down the modem for 30 mins and see if it improves things or leave well alone and be thankful for what ive got ?
heres my stats for the last 2 weeks...
-
I can't understand perry08106 when looking at your full monty it's doing much better than my 3 year old 40/10 895m line yet your interleave seems stuck it should have decreased by now.
MY interleave depth is at 595 and I have much more errors in a 24 hour period than yourself.
and yes I would turn off Modem and Router for 30 mins or overnight though it looks like the interleaving is stuck at 1000 :-\
EDIT: there is something not quite right with your upstream U1 band it should have more bits and snr than the U2 band ???
-
I can't understand perry08106 when looking at your full monty it's doing much better than my 3 year old 40/10 895m line yet your interleave seems stuck it should have decreased by now.
it is strange , and im pretty sure im less than 300m away from the cab , and thats adding around 50m for any detour
to be honest , i reckon ive been interleaved for over 3 months , although i didnt have an unlocked modem i checked my download results on speedtest and was getting 60 down just before i had the HH5 ,
MY interleave depth is at 595 and I have much more errors in a 24 hour period than yourself.
and yes I would turn off Modem and Router for 30 mins or overnight though it looks like the interleaving is stuck at 1000 :-\
its looking that way , just wondered if anyone else has the same view as yourself before i pull the plug
EDIT: there is something not quite right with your upstream U1 band it should have more bits and snr than the U2 band ???
not sure if thats related to crosstalk or not , hopefully BE1 could check that , pretty sure he mentioned crosstalk a few posts back
-
there is something not quite right with your upstream U1 band it should have more bits and snr than the U2 band
Power cut back & PSD masks. Mines the same.
----
Edit
Just seen your post above.. "im less than 300m away from the cab "
It will be power cut back.
-
thanks for that Kitz :)
i take it thats because i dont need the extra power and it helps to reduce xtalk for others on the cab ?
regarding the distance , im being pretty generous regarding distance , i could be standing by that cab in 3 mins ... and i dont walk fast ;)
-
Perry081064 there is something when your interleaved and it's this ->
when you sync higher the interleave will be higher for example
My Sync is 30484 kbps and interleaveing depth is 595
Your Sync is 51601 kbps and interleaving depth is 1000
now if I sync at 28000 kbps my interleaving depth will decrease to 450
but still even with the above information you should have had a lower interleaving or even been moved to fastpath in 14 days as long as you kept the modem on 24/7
-
Perry081064 there is something when your interleaved and it's this ->
when you sync higher the interleave will be higher for example
My Sync is 30484 kbps and interleaveing depth is 595
Your Sync is 51601 kbps and interleaving depth is 1000
now if I sync at 28000 kbps my interleaving depth will decrease to 450
but still even with the above information you should have had a lower interleaving or even been moved to fastpath in 14 days as long as you kept the modem on 24/7
i agree and yes the modem has been on ever since the firmware change 34 days ago.
before the latest firmware was installed , the interleave was at 950 iirc , on reboot the interleave was at 1009 and remained there since.
there was a resync in my plink log later on that afternoon at around 5pm , although it didnt show directly on the stats and also didnt change anything.
so where to go from here is the question, if i power down the modem i run the risk of an even higher interleave running from my history so far.
failing that , could it be possible for my interleave to be reduced in a few months time rather than a few weeks ?
-
i take it thats because i dont need the extra power and it helps to reduce xtalk for others on the cab
It depends on line length.. and since yours probably is in a similar length range to my own and classed as short(ish) then its to protect longer lines.
I havent read the whole thread as Ive just got back and am still catching up on posts, so apologies if Im covering old ground or something someone else has already said. But Ive just seen your QLN which to me doesnt look quite right in the first 400 tones. Your downstream is a tad lower than Id anticipate for a <300m line.
My immediate first impression would be crosstalk, but it could also be interference from other sources. With your line being interleaved that will be taking up some of the available speed... and also keeping your E/Secs count down. I think it may be a case of watching what happens with your SNRm and how much it fluctuates.
-
i take it thats because i dont need the extra power and it helps to reduce xtalk for others on the cab
It depends on line length.. and since yours probably is in a similar length range to my own and classed as short(ish) then its to protect longer lines.
I havent read the whole thread as Ive just got back and am still catching up on posts, so apologies if Im covering old ground or something someone else has already said. But Ive just seen your QLN which to me doesnt look quite right in the first 400 tones. Your downstream is a tad lower than Id anticipate for a <300m line.
My immediate first impression would be crosstalk, but it could also be interference from other sources. With your line being interleaved that will be taking up some of the available speed... and also keeping your E/Secs count down. I think it may be a case of watching what happens with your SNRm and how much it fluctuates.
crosstalk was BE1's thoughts as the cab is around 2 years old now , ive been here a year and was getting 67 down for around 3 months then it dropped to 60 .
after trying the HH5 and it constantly rebooting , it would appear that iether something happened to my line /cab or the HH5 was the problem.
as for monitoring the snrm , what youve seen already is consistant with the last few months, only spiking and dropping when its raining to pick up gradually over the coming days .
-
could it be possible for my interleave to be reduced in a few months time rather than a few weeks ?
I myself would just keep the modem on for as long as you can and if things change you will get a retrain/resync anyway at some stage, so follow what Kitz has posted and keep the stats running.
-
yes i think thats the way to go , im getting more than enough speed for what i need anyway :)
-
well , i noticed a big drop in SNRM last night around 10pm.
ive seen this happen on randomly before , it can happen at any time and usually drops my downstream SNRM down to 5.8 after climbing up to around 6.9 .
this happens roughly one a month and theres never a given reason as to why , the weather is fine , nothing inside the house had been powered up/down or changed .
no reboot or resync in over 40 days.
im just wondering if this is the reason my interleave wont drop ?.
ive included stats of the past 24 hours and can supply stats for the past 3 weeks if required.
-
It was preceded by quite an increase in SNRM.
Almost as though something had been switched off & back on again.
Maybe a neighbour rebooted their modem/router, relieving crosstalk for a short while, then causing it again with an increased vengeance due to a higher sync speed?
FWIW, the FULL__Monty montage provides a little more information that might be relevant.
-
It was preceded by quite an increase in SNRM.
Almost as though something had been switched off & back on again.
Maybe a neighbour rebooted their modem/router, relieving crosstalk for a short while, then causing it again with an increased vengeance due to a higher sync speed?
FWIW, the FULL__Monty montage provides a little more information that might be relevant.
my thoughts exactly , its as if something had been power cycled , there does seem to be more virgin media users on my street rather than FTTC but that doesnt mean much i suppose.
i recall the last time i noticed this type of event was just over a month ago, around 10am , again the weather wasnt bad and no machinery operating nearby.
anyway , i have included the full monty this time as advised and thanks again for taking the time to eye these over BE :)
-
my thoughts exactly , its as if something had been power cycled , there does seem to be more virgin media users on my street rather than FTTC but that doesnt mean much i suppose.
i recall the last time i noticed this type of event was just over a month ago, around 10am , again the weather wasnt bad and no machinery operating nearby.
anyway , i have included the full monty this time as advised and thanks again for taking the time to eye these over BE :)
Just a thought..............................
Do you or a nearby neighbour have smart meters that 'phone home' once a month?
Is the increased noise/bitswapping as shown in the graphs a daily occurrence or does that also only happen once a month?
You have my email address don't you?
If so, could you zip your complete modem_stats.log & email it to me for a closer look?
If not, send me a PM with your own email address & I'll respond accordingly.
-
my thoughts exactly , its as if something had been power cycled , there does seem to be more virgin media users on my street rather than FTTC but that doesnt mean much i suppose.
i recall the last time i noticed this type of event was just over a month ago, around 10am , again the weather wasnt bad and no machinery operating nearby.
anyway , i have included the full monty this time as advised and thanks again for taking the time to eye these over BE :)
Just a thought..............................
Do you or a nearby neighbour have smart meters that 'phone home' once a month?
Is the increased noise/bitswapping as shown in the graphs a daily occurrence or does that also only happen once a month?
You have my email address don't you?
If so, could you zip your complete modem_stats.log & email it to me for a closer look?
If not, send me a PM with your own email address & I'll respond accordingly.
im pretty sure no one in my near location has those meters and im attaching a full monty of the last 20 days regarding the bitswapping issue.
pm ing you now BE :)
-
Just a thought. The possible resync of another modem in the vicinity ties in with whats been reported by a few peeps on the forum recently? Modems resyncing due to firmware updates.... :hmm:
-
Just an update:
I had to have a full electrics test on the house today for legal reasons.
so obviously the modem , router , server etc needed to be powered down for a few hours rather than having several disconnects.
i was hoping after the modem being up for well over forty days that interleave wouldnt rise , however on reconnection im gutted to find its gone up again from 1009 to 1024 :'(
... seems my modem really doesnt like being powered down at all , the last time was when the modem firmware was updated , then it was 950 rising to 1009 and only powered down once.
it really doesnt seem to drop , only rise , and even then only 1 disconnect seems to do it :'(
im just hoping i never get a powercut now :baby:
-
just an update from my previous posts.
interleave has continued to stay at 1021 ( my last post stated 1024 but i meant to type 1021 ).
no resync , no dropouts .
however , my SNRM seems to be getting lower . it used to hover from 5.9 to 6.8 but has recently dropped to an all time low of 5.6 ( and thats in sunny weather so god help me when we get rain or storms)
looking at my stats , theres not much to see that you havent already seen before but will post if required.
-
UPDATE :
after using BT's line fault checker , it showed i had a line fault and asked me what the fault was.
i ticked noise.
2 days later i had a phone call from a BT tech to tell me he had fixed the fault and it was wet lines at the green cab.
i explained to him i had been suffering from interleave for a while that had reduced my speeds on infinity and he advised to wait a few days to see if speeds returned to normal.
As he was only a phone tech he couldnt arrange a DLM reset , but im hoping things may now turn around over the next few days.
wish me luck !
-
Good luck! :)