Print

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

[custard]

Actually i am using the this version already - bcm96368MVWG_fs_kernel_HG612V100R001C01B028SP10_no-btagent which gives me a log showing firmware A2pv6C035m.d22g

I did try the experimental firmware that you linked to over the weekend but i found my errors shot up and there was an increase in signal attenuation and no increase in sync.


Here are the logs from using the experimental firmware

At resync

Code: [Select]

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 24295 Kbps, Downstream rate = 66164 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 66164 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.8
Attn(dB): 15.2 0.0
Pwr(dBm): 13.4 4.7
VDSL2 framing
Bearer 0
MSGc: 18 150
B: 239 236
M: 1 1
T: 21 5
R: 0 16
S: 0.1154 0.3771
L: 16632 5410
D: 1 1
I: 240 255
N: 240 255
Counters
Bearer 0
OHF: 645926 192545
OHFErr: 22 0
RS: 0 3919324
RSCorr: 0 16
RSUnCorr: 0 0

Bearer 0
HEC: 9 0
OCD: 0 0
LCD: 0 0
Total Cells: 149909993 0
Data Cells: 35945 0
Drop Cells: 0
Bit Errors: 0 0

ES: 7 0
SES: 0 0
UAS: 26 26
AS: 1179

Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.82 6.15
OR: 105.18 202.87
AgR: 66269.13 20203.27

Bitswap: 27/27 0/0

Total time = 20 min 5 sec
FEC: 0 16
CRC: 22 0
ES: 7 0
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 5 min 5 sec
FEC: 0 8
CRC: 9 0
ES: 3 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 0 8
CRC: 13 0
ES: 4 0
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 20 min 5 sec
FEC: 0 16
CRC: 22 0
ES: 7 0
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 = 19 min 39 sec
FEC: 0 16
CRC: 22 0
ES: 7 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 24295 Kbps, Downstream rate = 66164 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 66164 Kbps

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:     24295 kbps     66164 kbps
Actual Aggregate Tx Power:        4.7 dBm      13.4 dBm
====================================================================================
  VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
  Line Attenuation(dB): 0.1 17.8 27.1   N/A   N/A 10.0 23.4 36.3
Signal Attenuation(dB): 0.1 17.7 27.0   N/A   N/A 13.1 23.2 36.3
SNR Margin(dB): 7.2 6.6 6.8   N/A   N/A 6.3 6.3 6.3
TX Power(dBm): -5.1 -29.0 4.2   N/A   N/A 10.1 7.6 7.2


xdslcmd info --Bits
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 24295 Kbps, Downstream rate = 66164 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 66164 Kbps

xdslcmd info --show
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 24291 Kbps, Downstream rate = 66164 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 66164 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.7
Attn(dB): 15.2 0.0
Pwr(dBm): 13.4 4.7
VDSL2 framing
Bearer 0
MSGc: 18 150
B: 239 236
M: 1 1
T: 21 5
R: 0 16
S: 0.1154 0.3771
L: 16632 5410
D: 1 1
I: 240 255
N: 240 255
Counters
Bearer 0
OHF: 647022 192873
OHFErr: 22 0
RS: 0 3940644
RSCorr: 0 16
RSUnCorr: 0 0

Bearer 0
HEC: 9 0
OCD: 0 0
LCD: 0 0
Total Cells: 150164353 0
Data Cells: 35980 0
Drop Cells: 0
Bit Errors: 0 0

ES: 7 0
SES: 0 0
UAS: 26 26
AS: 1181

Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.82 6.15
OR: 105.18 202.87
AgR: 66269.13 20203.27

Bitswap: 27/27 0/0



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

And 12 hours later. At this point my max attainable had dropped below my sync rate.

Code: [Select]

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 24281 Kbps, Downstream rate = 65692 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 66164 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.1 6.7
Attn(dB): 15.2 0.0
Pwr(dBm): 13.4 4.7
VDSL2 framing
Bearer 0
MSGc: 18 150
B: 239 236
M: 1 1
T: 21 5
R: 0 16
S: 0.1154 0.3771
L: 16632 5410
D: 1 1
I: 240 255
N: 240 255
Counters
Bearer 0
OHF: 24354564 1779393
OHFErr: 3349 4
RS: 0 3363816
RSCorr: 0 69
RSUnCorr: 0 0

Bearer 0
HEC: 234 0
OCD: 4 0
LCD: 4 0
Total Cells: 1358540428 0
Data Cells: 4684114 0
Drop Cells: 0
Bit Errors: 0 0

ES: 1596 4
SES: 0 0
UAS: 26 26
AS: 44454

Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.82 6.15
OR: 105.18 202.87
AgR: 66269.13 20203.27

Bitswap: 18913/18913 22/22

Total time = 12 hours 21 min 20 sec
FEC: 0 69
CRC: 3349 4
ES: 1596 4
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 6 min 20 sec
FEC: 0 0
CRC: 501 0
ES: 159 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 0 3
CRC: 856 0
ES: 316 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 12 hours 21 min 20 sec
FEC: 0 69
CRC: 3349 4
ES: 1596 4
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 = 12 hours 20 min 53 sec
FEC: 0 69
CRC: 3349 4
ES: 1596 4
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 24281 Kbps, Downstream rate = 65692 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 66164 Kbps

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:     24281 kbps     65692 kbps
Actual Aggregate Tx Power:        4.7 dBm      13.4 dBm
====================================================================================
  VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
  Line Attenuation(dB): 0.1 17.8 27.1   N/A   N/A 10.0 23.4 36.3
Signal Attenuation(dB): 0.1 17.7 27.0   N/A   N/A 13.1 23.2 36.3
SNR Margin(dB): 7.2 6.7 6.8   N/A   N/A 6.1 6.1 6.1
TX Power(dBm): -5.1 -29.0 4.2   N/A   N/A 10.1 7.6 7.2


xdslcmd info --Bits
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 24281 Kbps, Downstream rate = 65692 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 66164 Kbps



xdslcmd info --show
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 24281 Kbps, Downstream rate = 65692 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 66164 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.1 6.7
Attn(dB): 15.2 0.0
Pwr(dBm): 13.4 4.7
VDSL2 framing
Bearer 0
MSGc: 18 150
B: 239 236
M: 1 1
T: 21 5
R: 0 16
S: 0.1154 0.3771
L: 16632 5410
D: 1 1
I: 240 255
N: 240 255
Counters
Bearer 0
OHF: 24355660 1779695
OHFErr: 3353 4
RS: 0 3383439
RSCorr: 0 69
RSUnCorr: 0 0

Bearer 0
HEC: 234 0
OCD: 4 0
LCD: 4 0
Total Cells: 1358794785 0
Data Cells: 4684166 0
Drop Cells: 0
Bit Errors: 0 0

ES: 1597 4
SES: 0 0
UAS: 26 26
AS: 44456

Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.82 6.15
OR: 105.18 202.87
AgR: 66269.13 20203.27

Bitswap: 18914/18914 22/22



xdslcmd --version
xdslcmd version 1.0
DSL PHY: AnnexA version - A2pv6C038m.d24j
Immedaitely after these stats I reverted back to the ECI at which point the line cap 0f 60Mbps occurred.

[Chrysalis]

On that basis my highest sync was with the ECI at 66.28/0.9679 = 68.48Mbps. That indicates a loss of approx 3mbps with the HG612 on a ECI DSLAM. I'd like to see if the hg612 attains that speed over the next month if i don't resync the modem.

On a sidenote my internet yesterday while i was on the lower sync was atrocious with frequent non-loading of pages. Today its back to normal.

Chrysalis - Sounds like i still have room for improvement! Does your SNRM vary much throughout the day and what do you estimate your line length to be? I think mine is approx 400m.

my actual distance to cabinet is 430 something if I remember right 436, was recently given to me by openreach.

my snrm barely budges at all during the day, especially as I now have a fixed nte5.

[NewtronStar]

Actually i am using the this version already - bcm96368MVWG_fs_kernel_HG612V100R001C01B028SP10_no-btagent which gives me a log showing firmware A2pv6C035m.d22g

I did try the experimental firmware that you linked to over the weekend but i found my errors shot up and there was an increase in signal attenuation and no increase in sync.

Custard I used the new firmware when it came out for two weeks and said no it's slower it has more error counts I dismissed it as bad and went back to the old firmware, then I gave it a second chance over a month of testing and guess what my BB connetion is better than when FTTC was first installed, yes it may work better on longer noisy lines and can't see why a shorter line would make this new firmware any worse than the old one.

[custard]

my actual distance to cabinet is 430 something if I remember right 436, was recently given to me by openreach.

my snrm barely budges at all during the day, especially as I now have a fixed nte5.

Sounds like you line is similar to mine in many ways. My SNRM variation reduced after moving from ADSL2 to FTTC. Have you had the mark 2 VDSL faceplate fitted to your NTE5?

I gave it a second chance over a month of testing and guess what my BB connetion is better than when FTTC was first installed, yes it may work better on longer noisy lines and can't see why a shorter line would make this new firmware any worse than the old one.

Thanks NewtronStar. I may eventually go back to the experimental firmware but don't want to do this few a few weeks incase the modem resync is detected as a line problem.
What made you give the experimental firmware a second chance?

[Chrysalis]

I have the MK2.

I will point out I swapped out the NTE5 myself, 4 visiting engineers all failed to diagnose it and left the broken one in place.  Also I swapped it before I reported my fault to plusnet I already knew it was the cause of the HR symptons (I told kitz in private before the event so she can back me up), I put the BT NTE5 back in place tho so when the engineers visited they wouldnt try to charge on the basis I swapped out the NTE5, but that of course meant the HR issue was back.  After the last visit I put my newer NTE back so the HR was fixed again.

So basically in short I have a new NTE5 fitted by myself (but only the front part not the fixed back part on the wall).  This solved my HR symptons and gave me an extra 3mbit of sync speed.  I also have the MK2 faceplate which I put on myself, this seems to have no effect on my line tho.

Notice the 0 SES on my upstream, on the broken NTE5 that used to tally up and be way higher than the downstream SES (even tho the upstream has a bigger snrm).

Although my downstream CRC error rate has creeped up again tho I think after a DLM reset which openreach carried out after I contacted them. (I didnt ask for DLM reset they just did it).

[NewtronStar]

Thanks NewtronStar. I may eventually go back to the experimental firmware but don't want to do this few a few weeks incase the modem resync is detected as a line problem.
What made you give the experimental firmware a second chance?

Yes thats definitely a good idea to leave the firmware alone for a few weeks and see how it performs on your line and also have HG612_stats running in the back ground to compare the difference between the firmware's.

The reason for the second chance was down to looking into my stats and noticed Wolfys firmware always seem to give a higher Max: attainable sync and Path: but with more error counts I was concerned about the higher error counts but after a month of usage no retrains it stay'd constant, Asbo's firmware was giving me a lot of retrains & variable Max Att: and Path: speeds which was lower than the new firmware.

Also I have ordered the MKII faceplate to see if it filters out some of my RFI it will be interesting to see the outcome 

[custard]

I will point out I swapped out the NTE5 myself, 4 visiting engineers all failed to diagnose it and left the broken one in place.  Also I swapped it before I reported my fault to plusnet I already knew it was the cause of the HR symptons (I told kitz in private before the event so she can back me up), I put the BT NTE5 back in place tho so when the engineers visited they wouldnt try to charge on the basis I swapped out the NTE5, but that of course meant the HR issue was back.  After the last visit I put my newer NTE back so the HR was fixed again.

The very back plate only holds the socket to the wall anyway so no need to change.

"If you want a job done right then do it yourself"

I did something similar to OR equipment. I relocated my master socket and connected it directly to the grey drop cable. The previous cabling ran into an old BT junction box.

Your stats on the experimental firmware are similar to my test although I had much more errors for a shorter period.

Yes thats definitely a good idea to leave the firmware alone for a few weeks and see how it performs on your line and also have HG612_stats running in the back ground to compare the difference between the firmware's.

The reason for the second chance was down to looking into my stats and noticed Wolfys firmware always seem to give a higher Max: attainable sync and Path: but with more error counts I was concerned about the higher error counts but after a month of usage no retrains it stay'd constant, Asbo's firmware was giving me a lot of retrains & variable Max Att: and Path: speeds which was lower than the new firmware.

I've had a read of the 16 page experimental firmware thread again. I can see the reports of higher errors but also higher syncs after a couple of retrains. I'm itching to change the software again!!