it increases temporarily when it has to correct an error, which is better than permanent increase from normal interleaving.
I haven't yet managed to figure out what the new "huge" INP values are telling us.
However, I think the setup of G.INP is that the other parameter "INPrein" takes over the job of handling against REIN - the "repetitive electrically induced noise", which causes short, small levels of interference that re-occurs at 50Hz or 100Hz - from the old parameter "INP" that seemed to be used to do that job.
=~=~=~=~=~=~=~=~=~=~=~= Plink log 2015.03.18 10:28:15 =~=~=~=~=~=~=~=~=~=~=~=
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 32206 Kbps, Downstream rate = 85316 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 7.2 13.9
Attn(dB): 13.5 0.0
Pwr(dBm): 12.4 3.2
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 130 97
M: 1 1
T: 0 0
R: 8 8
S: 0.0518 0.1554
L: 21468 5457
D: 16 8
I: 139 106
N: 139 106
Q: 16 8
V: 14 2
RxQueue: 57 39
TxQueue: 19 13
G.INP Framing: 18 18
G.INP lookback: 19 13
RRC bits: 24 24
Bearer 1
MSGc: 186 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 5.3333 16.0000
L: 48 16
D: 3 1
I: 32 32
N: 32 32
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 0
OHFErr: 0 0
RS: 1485528144 3196410
RSCorr: 8790 671
RSUnCorr: 0 0
Bearer 1
OHF: 1202365 158489
OHFErr: 0 0
RS: 14427642 533292
RSCorr: 0 6
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 514 67
rtx_c: 397 67
rtx_uc: 0 0
G.INP Counters
LEFTRS: 7 1
minEFTR: 79982 19991
errFreeBits: 23564798 5890148
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2971153725 0
Data Cells: 6364912 0
Drop Cells: 0
Bit Errors: 0 0
Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0
ES: 11 1
SES: 10 0
UAS: 69 59
AS: 19314
Bearer 0
INP: 46.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 80614.82 20102.08
Bearer 1
INP: 4.00 4.00
INPRein: 4.00 4.00
delay: 3 0
PER: 16.06 16.06
OR: 95.62 31.87
AgR: 95.62 31.87
Bitswap: 1071/1071 2/2
Total time = 1 days 20 hours 30 min 46 sec
FEC: 80128 135410
CRC: 6848 2
ES: 11 1
SES: 10 0
UAS: 69 59
LOS: 1 0
LOF: 5 0
LOM: 0 0
Latest 15 minutes time = 46 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
Previous 15 minutes time = 15 min 0 sec
FEC: 101 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 20 hours 30 min 46 sec
FEC: 36684 44100
CRC: 6817 0
ES: 10 0
SES: 10 0
UAS: 32 22
LOS: 1 0
LOF: 5 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 43444 91310
CRC: 31 2
ES: 1 1
SES: 0 0
UAS: 37 37
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 5 hours 21 min 53 sec
FEC: 8790 671
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
HELLO HG612
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 32206 Kbps, Downstream rate = 85316 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 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,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 32206 kbps 85316 kbps
Actual Aggregate Tx Power: 3.2 dBm 12.4 dBm
=========================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 3.2 15.1 21.8 N/A N/A 8.7 19.1 29.2
Signal Attenuation(dB): 3.2 14.1 21.0 N/A N/A 11.5 18.9 29.2
SNR Margin(dB): 13.9 13.9 13.9 N/A N/A 7.2 7.2 7.2
TX Power(dBm): -11.8 -27.9 3.1 N/A N/A 8.0 7.9 7.0
As of 5am my connection went onto G inp, My IP profile is 77.35 instead of the normal 77.44 ? I'm also still using an older unlocked firmware Software version = V100R001C01B030SP06 Firmware version = A2pv6C038m.d24j which would appear to work with G.INP , no doubt some one will tell me if it isn't working as well as it should, I still have the ECI that i was issued with by by installing engineer, Which that was to fail to sync, the DLM would require a reset, ?Can someone on a G.inp enabled line do the following, possibly?
xdslcmd profile --show
xdslcmd info --cfg
ta :)
There may be something to be gleaned from vdslCfgFlagsValue: 00210400 but not sure!
G.INP feature bit
Bit 17 xdslAuxFeaturesMask—ON
Bit 17 xdslAuxFeaturesValue—ON
xdslAuxFeaturesMask—00040003
xdslAuxFeaturesValue—00040003
Bit 17 xdslAuxFeaturesMask—OFF
Bit 17 xdslAuxFeaturesValue—OFF
xdslAuxFeaturesMask—00060003
xdslAuxFeaturesValue—00060003
GinpUs support
Bits 18 kDslGinpUsSupported—OFF
xdslAuxFeaturesValue—00024003
Bits 18 kDslGinpUsSupported—ON
xdslAuxFeaturesValue—00064003
FireDS support
Bits 22 kDslFireDsSupported—OFF
adslDemodCap2Value—00900000
Bits 22 kDslFireDsSupported—ON
adslDemodCap2Value—00d00000
FireUS support
Bits 23 kDslFireUsSupported—Off
adslDemodCap2Value—00500000
Bits 23 kDslFireUsSupported—On
adslDemodCap2Value—00d00000
Has anyone on an ECI cabinet had G.INP yet or is it just Huawei cabs?
G.INP so far seems an all win for those who have it.
That said, it does look promising to those with a decent line.
I have two lines both running from the same Huawei cabinet, both are running on unlocked HG612's and both of these are using software version V100R001C01B030SP06
Are both using the exact same firmware V100R001C01B030SP06 comes in two flavours ?
1. unlockedgui
2. unlockedgui-nobtagent
the first one still updates to V100R001C01B030SP08 the second one will not update to V100R001C01B030SP08
In the last 14 hours the G.INP enabled line had recorded just 9500 FEC's and no other errors the other line is still clocking up errors at it's usual rate.
I'm not as technical as you guys here but I'm interested in getting improvements.
This G-IMP I take it is only for some people so is there a list on a website saying who has it ans hasn't?
Is it to be rolled out to us all and is there a completion date?
[off-topic]they are crap. funny thing is belkin sent them as a replacement for an ethernet wireless adapter that could not be upgraded to wpa Anne
Ah, ha! Home plugs. Just the same "problem creators" that N*Star had a while ago . . . :-X
[/off-topic]
I have some new Devolo's that I'm watching like a hawk ... and I haven't seen a dicky bird out of them. The line runs at about 40 ES per day.listen on your phoneline crackles like ice crispies Anne.
I have some new Devolo's that I'm watching like a hawk ... and I haven't seen a dicky bird out of them. The line runs at about 40 ES per day.
I'm using the 500 AV Wireless+ units, and don't get a peep from them either - in either audio or VDSL2. If they did *anything*, I'd be trying for something better.
Right now, I'm using the WiFi in 2.4GHz mode, but sometime soon I'll swap it to 5GHz.
I'm using the 500 AV Wireless+ units, and don't get a peep from them either - in either audio or VDSL2. If they did *anything*, I'd be trying for something better.
Right now, I'm using the WiFi in 2.4GHz mode, but sometime soon I'll swap it to 5GHz.
OK, this is off-topic I suppose but.....
What units exactly are they please?
I have Devolo 200s (dLan 200 AVeasy) here and also Solwise 500s (PL-500AV-SMT). Can't use either make though as they are both as bad as each other. Just running them for lan to other rooms, I get about 40-60,000+ extra FECs/Min as soon as I make a physical LAN connection and if I plug the Sony smart TV LAN connection in to one - it goes to Millions/min!!
These plugs are NOT WiFi though - using several normal repeaters around the property currently but speed is not good and chronic latency by the looks of it. So I wonder if a WiFi able Homeplug is much better than a wired one from the interference angle?
Gone to G.inp this morning! Seems after the mystery sync loss for ten minutes the other night, its pushed it to the cab.
Last night we had a power cut, and I had to resync the connection manually to get my snr back up - I'd resync before everyone else!
On G.inp I'm on full sync and increased snr, I'll PST some stats if anyone wants them?
Gone to G.inp this morning! Seems after the mystery sync loss for ten minutes the other night, its pushed it to the cab.
Last night we had a power cut, and I had to resync the connection manually to get my snr back up - I'd resync before everyone else!
On G.inp I'm on full sync and increased snr, I'll PST some stats if anyone wants them?
Yes!
What was synch before vs now? Plus any other before/afters if you can. Logging onto MDWS is a PITA :P
Interestingly my but loading has changed, some of the central tones are powered back and the far right tones are being used? Image attached
Ooh, that looks odd! ???
I'll check via MDWS to see the entire tone spectrum.
I just checked on MDWS now, and it all looks fine there?
newt must be begging for g.inp now.
I just checked on MDWS now, and it all looks fine there?
Agreed. :)
However there is something not right with your server that is displaying the images (apart from only showing up to tone 255 for the bit loading graph). :(
You need to drag zoom the start of the plot on MDWS as otherwise they are lost 8)
edit: fixed all the graphs on my webserver (http://www.jamieidavies.co.uk/dslstats/webserver/) 8)
edit: fixed all the graphs on my webserver (http://www.jamieidavies.co.uk/dslstats/webserver/) 8)
<Cough> Another fur-ball. ::)
Ah . . . ;)
This may do it (http://www.jamieidavies.co.uk/dslstats/webserver/allstats.html) :)
FWIW, I have been using Devolo dLAN 500 WiFi units for quite a long time now.
Whether they are switched on, switched off, plugged in or unplugged, they make absolutely no difference to my connection's performance & error stats.
If they had made any difference & with me being somewhat obsessed about connection stats, Mrs. Eagle would still be putting up with the much poorer wireless range (due to very thick walls between rooms) of my Netgear WNR1000 v 3 router for her Candy Crushing & so on ;)
Do you have a UTP modem cable?
STP rather than UTP then :)
STP rather than UTP then :)
Okay I give up - what's the difference?
If S=Single and D=Double then the spare I have has 4 wires....
I'm using the 500 AV Wireless+ units
What units exactly are they please?
STP rather than UTP then :)
Okay I give up - what's the difference?
If S=Single and D=Double then the spare I have has 4 wires....
STP = shielded twisted pair, UTP = unshielded twisted pair. There's also FTP, which is foil shielded twisted pair.
What units exactly are they please?
Ah! Thanks. I still find it difficult to believe that a homeplug just inserted into a ring mains 60 feet away from the modem would generate that sort of interference on even an unshielded flat 10 inch lead?
Ah! Thanks. I still find it difficult to believe that a homeplug just inserted into a ring mains 60 feet away from the modem would generate that sort of interference on even an unshielded flat 10 inch lead?
It may be being transferred through the mains, and into the PSU of the modem, and on into the power circuits.
Have you got the modem PSU plugged into the pass-through? This is supposed to be filtered.
Ah. That complicates things somewhat...
I agree that the homeplug ought to go onto an unfiltered connection to the ring main - and preferably without an extension lead.
However, I'd have thought your UPS would effectively filter the homeplug signal from the PSU anyway - and you wouldn't suffer from this problem.
But your UPS ought to make it easy to test whether the errors are mains-borne or RF; just have the modem run from UPS on battery while the homeplug remains in the mains. That way there would be no path from the ring main via the UPS to the modem.
Thinking further, though, perhaps you would need to run the test without even a network connection into the modem - just to be sure it isn't coming through the ethernet cable either.
Removed. Ideas please?
Removed. Ideas please?
Take them back and request a refund! ::)
...
...
ECI or Huawei cab?
excellent news newt :)
so far looks a decent improvement on your line :)
So is interleaving completely disabled once gimp kicks in? Delay 0 / 0 even though there still appears to be interleaving (and INP) on both bearers?
UPDATE:
Well finally I've had all my faults resolved after a month of new kit in the exchange/cab, a free HH5 and 2 cable repairs <snip>
This could be just a coincident I looked at Bald-Eagle1's uptime before his line was G.INP enabled and noticed a gap of 1 hour a power down of modem on the 17th so I turned my HG612 off for 1 hour on monday evening 23rd and G.INP was enabled on the 2nd day :-\
again probably a complete coincidence! ;D
again probably a complete coincidence! ;D
Your error rates are looking good there Newt!
It's just me looking to deeply into others stats and hopefully finding something in common to the event :blush:
Obviously I can't be precise but it looks like approximately tones 61 - 82 are affected. :-\
When converted to the corresponding frequencies, is there anything significant that might account for their attenuated bit-loading?
Hmm . . . That's puzzling. :-\
I am deffo seeing the same effects on the lower tones 65 to 85 as Jid noticed after G.INP was enabled see my Dslstats tone graphs.
Well I've been G.INPd today and if you look on MyDSLWebSite at my Bitloading graph the U0 band makes interesting reading...it appears to be ECI based ???
Well I've been G.INPd today and if you look on MyDSLWebSite at my Bitloading graph the U0 band makes interesting reading...it appears to be ECI based ???
The U0 band is not ECI based it's just your standard power cut back for your shorter line to stop you interfering with longer broadband lines ADSl ADSL2 and so on ;)
excellent news newt :)
so far looks a decent improvement on your line :)
Errored seconds and CRC's have magically disappeared and FEC's are much lower than i've ever seen on this FTTC line over the past three years, I'll give this G.INP technology a 10 out of 10 we should of had this years ago ;)
Well I've been G.INPd today and if you look on MyDSLWebSite at my Bitloading graph the U0 band makes interesting reading...it appears to be ECI based ???
The U0 band is not ECI based it's just your standard power cut back for your shorter line to stop you interfering with longer broadband lines ADSl ADSL2 and so on ;)
Stats recorded 26 Mar 2015 19:40:47
DSLAM/MSAN type: BDCM:0xa44f / v0xa44f
Modem/router firmware: AnnexA version - A2pv6F039g1.d24m
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 16 days 16 hours 43 min 4 sec
Resyncs: 0 (since 26 Mar 2015 19:32:43)
Downstream Upstream
Line attenuation (dB): 11.2 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 79987 19999
SNR margin (dB): 11.3 14.7
Power (dBm): 12.5 1.2
Interleave depth: 1 1
INP: 0 0
G.INP: Not enabled
RSCorr/RS (%): N/A 1.9891
RSUnCorr/RS (%): N/A 0.0000
ES/hour: 0 0
You probably don't want it Max :no:
(https://pbs.twimg.com/media/CBA9DSlWkAAv4OW.png)
http://aastatus.net/2115
Latency was never a top priority for me line stability was always foremost and with the help of G.INP i can now relax as CRC's and ES's are out of the equation unless something goes very wrong on this line.
There are quite a lot of users with very little errors on there current fastpath profile i doubt G.INP would make much difference to there line but a least it has the added protection from REIN and Shine that's always a good thing :)
You probably don't want it Max :no:
(https://pbs.twimg.com/media/CBA9DSlWkAAv4OW.png)
http://aastatus.net/2115
Seems that noise bursts do cause a spike in latency
Is it true that G.INP roll out for all Huawei cabinets roll out will be completed by end of this month then the next roll out for all the remaining ECI cabinets from April until end of June this year?
You probably don't want it Max :no:
(https://pbs.twimg.com/media/CBA9DSlWkAAv4OW.png)
http://aastatus.net/2115
Is there anywhere I can check to find out whether my cabinet is Huawei? Using Telnet it tells me the DSLAM chipset is Broadcom and the VDSL Firmware version is 05-04-08-00-00-06. I'm currently using a Draytek 2760, although I do have a locked Huawei.
The Broadcom chipset means that the cabinet is Huawei.
I was GINPed this morning at about 6:30am. Slight increase in SNRM (line is capped 80/20), no increase in latency. No non-FEC errors whatsoever since then. Stats are on MDWS.
so it is probably fair to say that G.INP is on its way for all lines.
But sadly, I think my line won't be G.INP enabled. I be very surprise if mine haven't done.
Can't generate BaldEagle's ongoing graphs, as there is no harvesting
Looks like G.INP was enabled on my line this morning.
If you want to take a look, I have my stats on MyDSLWebStats.
SNRM went from 5.3dB down, and 5.2dB up to 8.4dB down and 6.2dB up without any speed changes. It also reduced interleaving to 8 from around 860, and reduced delay from 8 to 0.
I'm a happy bunny!
Can I expect DLM to intervene and start raising my download speed now that my SNRM is so high?
Does G.INP reset DLM itself?
I just got G.INPed ;D
upstream speed went up by around 1.5mbps, downstream by around 4-5mbps. interleave dropped from 777 to 16. I seem to be banded downstream as there's still some SNR available.
I got G.INP enabled now this morning at 7:50am
Hi
This is to let you know that a resync/restart occurred on your line at 28-03-2015 07:50 local time (+/- 1 minute).
The MyDSLWebStats Team
That now works out at approximately 96.69% of sync speed compared to the previous (non-G.INP) 96.79%.
I have just tested this on my own connection, modem freshly rebooted.
Sync 22399/4999 & BT's IP Profile is 21.66/20
96.69% = 21.66% (rounded up).
Maybe the slight reduction in IP Profile is for the small 'overhead' required for G.INP?
I have read somewhere on kitz forum that G.INP has been removed off lines.
I have read somewhere on kitz forum that G.INP has been removed off lines.well looking at the my webstats all users page danbl would appear to of had G.inp enabled for some 37 days so i won't be holding my breath on getting de G.inp'd any-time soon,
Sorry, cannot remember where I have just read it.
G.INP is supposed to provide enhanced Impulse noise protection, it is possible that if you have a very good line you do not need it. :o
Supposedly it is possible to convince DLM you have a very good line ;D :o
I turned of the HG612 last night for 15 minutes and noticed the DS INP: changed from 46:00 to 49:00 what sort of change will that do to my line ?
May be that on resync the G.INP algorithm calculates the most suitable correction rates for the line.
Obviously all an assumption ???
i was g inped 5 hrs ago, funny time indeed. My ping is a lot better, knocked 8ms off to the bbc 16-17ms now , not bad for a long line
Before
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fimg537.imageshack.us%2Fimg537%2F6791%2F8LvkWu.jpg&hash=27c6092cff4f1b3a58d4806a255e8fa06c04dcd4)
After
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fimg661.imageshack.us%2Fimg661%2F3706%2FUsTtHc.jpg&hash=788eb22923f954440167a6834ac57d3986ed6534)
no idea, probably dropping as its night, my line is pretty poor to be fair, lots of ali cable and about 1200 metres.
I turned of the HG612 last night for 15 minutes and noticed the DS INP: changed from 46:00 to 49:00 what sort of change will that do to my line ?
no idea, probably dropping as its night, my line is pretty poor to be fair, lots of ali cable and about 1200 metres.
Before bbc.co.uk ping was 10ms and now 13ms (I have checked the billion router. It's haven't lost the sync or anything changed at all. Nothing)
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 35881 Kbps, Downstream rate = 105573 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 12.3 16.3
Attn(dB): 11.3 0.0
Pwr(dBm): 12.5 -1.3
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 130 97
M: 1 1
T: 0 0
R: 8 8
S: 0.0518 0.1554
L: 21468 5457
D: 16 8
I: 139 106
N: 139 106
Q: 16 8
V: 14 2
RxQueue: 57 39
TxQueue: 19 13
G.INP Framing: 18 18
G.INP lookback: 19 13
RRC bits: 24 24
Bearer 1
MSGc: 186 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 5.3333 16.0000
L: 48 16
D: 3 1
I: 32 32
N: 32 32
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 0
OHFErr: 0 0
RS: 2716152320 3038525
RSCorr: 96522 35037
RSUnCorr: 0 0
Bearer 1
OHF: 23054942 80053
OHFErr: 0 0
RS: 276659300 2400587
RSCorr: 57 140
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 1700 824
rtx_c: 1693 791
rtx_uc: 0 0
G.INP Counters
LEFTRS: 40 10
minEFTR: 79999 19991
errFreeBits: 451844219 114854581
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1137280766 0
Data Cells: 595978910 0
Drop Cells: 0
Bit Errors: 0 0
Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
AS: 370380
Bearer 0
INP: 46.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 80614.82 20102.08
Bearer 1
INP: 4.00 4.00
INPRein: 4.00 4.00
delay: 3 0
PER: 16.06 16.06
OR: 95.62 31.87
AgR: 95.62 31.87
Bitswap: 594/594 1046/1046
Total time = 4 days 6 hours 53 min 0 sec
FEC: 96522 35037
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 8 min 0 sec
FEC: 16 23
CRC: 0 0
ES: 0 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: 297 295
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 6 hours 53 min 0 sec
FEC: 7587 1748
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 50973 12702
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 4 days 6 hours 52 min 59 sec
FEC: 96522 35037
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
>
Before bbc.co.uk ping was 10ms and now 13ms (I have checked the billion router. It's haven't lost the sync or anything changed at all. Nothing)
I am not a ping expert but 13ms sounds quite good to me
Sorry for ranting :D
if the modem hasnt lost sync then likely its a routing change between tbb and plusnet. although I dont see it on my graph.
My latest billion stats:Code: [Select]adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 35881 Kbps, Downstream rate = 105573 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 12.3 16.3
Attn(dB): 11.3 0.0
Pwr(dBm): 12.5 -1.3
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 130 97
M: 1 1
T: 0 0
R: 8 8
S: 0.0518 0.1554
L: 21468 5457
D: 16 8
I: 139 106
N: 139 106
Q: 16 8
V: 14 2
RxQueue: 57 39
TxQueue: 19 13
G.INP Framing: 18 18
G.INP lookback: 19 13
RRC bits: 24 24
Bearer 1
MSGc: 186 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 5.3333 16.0000
L: 48 16
D: 3 1
I: 32 32
N: 32 32
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 0
OHFErr: 0 0
RS: 2716152320 3038525
RSCorr: 96522 35037
RSUnCorr: 0 0
Bearer 1
OHF: 23054942 80053
OHFErr: 0 0
RS: 276659300 2400587
RSCorr: 57 140
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 1700 824
rtx_c: 1693 791
rtx_uc: 0 0
G.INP Counters
LEFTRS: 40 10
minEFTR: 79999 19991
errFreeBits: 451844219 114854581
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1137280766 0
Data Cells: 595978910 0
Drop Cells: 0
Bit Errors: 0 0
Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
AS: 370380
Bearer 0
INP: 46.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 80614.82 20102.08
Bearer 1
INP: 4.00 4.00
INPRein: 4.00 4.00
delay: 3 0
PER: 16.06 16.06
OR: 95.62 31.87
AgR: 95.62 31.87
Bitswap: 594/594 1046/1046
Total time = 4 days 6 hours 53 min 0 sec
FEC: 96522 35037
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 8 min 0 sec
FEC: 16 23
CRC: 0 0
ES: 0 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: 297 295
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 6 hours 53 min 0 sec
FEC: 7587 1748
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 50973 12702
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 4 days 6 hours 52 min 59 sec
FEC: 96522 35037
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
>
Bearer 1
INP: 4.00 4.00
INPRein: 4.00 4.00
delay: 3 0
PER: 16.06 16.06
OR: 95.62 31.87
AgR: 95.62 31.87
Bear 1 (G.INP) side of things has put an extra 3ms on your line and it's done the exact same thing to my short error free line too..
Updated: Have BT starting to love me now?
Interesting BQM graph showing reduced in ping just after 11am this morning. (I notice between 12:30pm yesterday and before 11am today the ping was higher by 3ms extra. Graph below:
Speed test also reduced from 12ms to 9ms
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww.speedtest.net%2Fresult%2F4259877875.png&hash=9953c9f262d0adecf78c8586d94b46a4a1c63f0d) (http://www.speedtest.net/my-result/4259877875)
@lockeh my stats bearer 1 now showing 0 0
@boost my bbc co uk ping now 9ms
@lockeh my stats bearer 1 now showing 0 0
@boost my bbc co uk ping now 9ms
Level of INP do you have on bearer 1 now? My guess is 2.00
@lockeh my stats bearer 1 now showing 0 0
@boost my bbc co uk ping now 9ms
Level of INP do you have on bearer 1 now? My guess is 2.00
What's the lowest ping you see in the tracert? First/second hop etc? :)
Bearer 1
INP: 2.50 4.00
INPRein: 2.50 4.00
delay: 0 0
PER: 16.06 16.06
OR: 47.81 31.87
AgR: 47.81 31.87
xdslcmd info --stats
Bearer 1
INP: 2.50 4.00
INPRein: 2.50 4.00
delay: 0 0
PER: 16.06 16.06
OR: 47.81 31.87
AgR: 47.81 31.87
#
b*cat wonders if B*Eagle1 and N*Star have a time-share on the same circuit! ::)
very nice newt, I see you getting less than 15ES a day now.
All that hassle you had trying to fix things internally and all that was required was for BT to turn something on :)
Ah.
I had forgotten that you don't log 24/7.
I suppose if you generated 12 hour graphs they might give a rough indication of what changes over a 'real' 24 hours.
I do log 24/7 using Dslstats on the RPi it's just the HG612_Modem_stats uses MS windows OS for the program to work and the PC go's to sleep the same time as me ;)
Here are my equivalent graphs.
Hi all I used to get a ping of 4-5ms and just noticed its gone up quite alot to 15-16ms is this due to inp, and is there any way i can revert back to my old ping...as all this nonsense is annoying me!!
this is my connection statistic if that helps!
39952 kbps 10000 kbps
Which, if I have correctly understood the various articles I have read recently, along with your own comments, suggest/confirm that your connection is hardly affected by crosstalk (or other 'interference') at all.
I don't know if it really does show crosstalk, or just noise of any source.
I'm hoping g.inp will counter this low level interference when it arrives to my eci cabinet.
Can you post up your sets of graphs for, say, the last 10 days?
Anyone know why my line has interleave enabled?
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi474.photobucket.com%2Falbums%2Frr110%2Flock3h%2FCapturejhgk.jpg&hash=8211443043be193be3477448aa899d38b5ab1818)
Anyone know why my line has interleave enabled?
before the rubbish G.INP was forced on my line I had 3 years worth of full sync fast path trouble free line.
The line is only about 80 meters long of underground .5 copper.
Anyone know why my line has interleave enabled?
From my limited understanding interleaving as to be on for g.inp to work.
I know but I want my fast path ping back :(
I don't don't understand why my interleave depth is so high 16 down and 8 up.Do you know how much latency you are complaining about? Have you calculated it?
This is as bad as it can get with noise on the line as my cab is now full.
I don't know if it really does show crosstalk, or just noise of any source.
crosstalk will manifest itself as noise into the effected end-users line but the difference is it's another broadband signal thats interfering with the EU's line rather than the normal culprits like RFI and REIN this is were vectoring comes in it's able to mask out the crosstalk/noise from the disturbing broadband signal.
that you noticed boost UP has the biggest SNR, Attainable Rate but still not yet G.INP enabled on his Huawei cabinet?
Pretty sure boost is using the latest firmware on his HG after demoting the BH5a to auth n wireless only.
Good luck convincing gamers that interleaved is better than fastpath :P
When someone asks for help we should probably try and provide real help instead of convincing everyone there isn't really a problem :P
moved off fastpath and am now interleaved was due to end-users going above their daily errored second quota.
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 8169 Kbps, Downstream rate = 52832 Kbps
Bearer: 0, Upstream rate = 9997 Kbps, Downstream rate = 53998 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 5.9 4.1
Attn(dB): 22.3 0.0
Pwr(dBm): 12.2 5.9
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 243 227
M: 1 1
T: 0 0
R: 10 16
S: 0.1439 0.7254
L: 14122 2691
D: 8 4
I: 254 244
N: 254 244
Q: 8 4
V: 0 0
RxQueue: 42 16
TxQueue: 14 8
G.INP Framing: 18 18
G.INP lookback: 14 8
RRC bits: 24 24
Bearer 1
MSGc: 122 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 8.0000 16.0000
L: 32 16
D: 1 1
I: 32 32
N: 32 32
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 0
OHFErr: 2 0
RS: 375653472 2361207
RSCorr: 4275944 9905
RSUnCorr: 0 0
Bearer 1
OHF: 10500855 56429
OHFErr: 0 0
RS: 84006350 3514053
RSCorr: 85 25
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 40636 36
rtx_c: 4375 321
rtx_uc: 3 0
G.INP Counters
LEFTRS: 78 23
minEFTR: 53987 9994
errFreeBits: 138878331 106508342
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 334868363 0
Data Cells: 463237793 0
Drop Cells: 0
Bit Errors: 0 0
Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0
ES: 2 0
SES: 0 0
UAS: 44 44
AS: 168676
Bearer 0
INP: 47.00 43.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 54052.91 10019.02
Bearer 1
INP: 2.00 4.00
INPRein: 2.00 4.00
delay: 0 0
PER: 16.06 16.06
OR: 63.75 31.87
AgR: 63.75 31.87
Bitswap: 126122/126122 626/627
Total time = 1 days 22 hours 52 min 0 sec
FEC: 4275944 9905
CRC: 2 0
ES: 2 0
SES: 0 0
UAS: 44 44
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 7 min 0 sec
FEC: 148 9521
CRC: 0 0
ES: 0 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: 224 3
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 22 hours 52 min 0 sec
FEC: 3724437 9642
CRC: 2 0
ES: 2 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 551507 263
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 44 44
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 days 22 hours 51 min 15 sec
FEC: 4275944 9905
CRC: 2 0
ES: 2 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Stats recorded 05 Apr 2015 10:21:42
DSLAM/MSAN type: BDCM:0xa44f / v0xa44f
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 1 day 22 hours 52 min 15 sec
Resyncs: 0 (since 05 Apr 2015 09:06:35)
Downstream Upstream
Line attenuation (dB): 22.3 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 53998 9997
SNR margin (dB): 5.9 4.8
Power (dBm): 12.2 5.9
Interleave depth: 8 4
INP: 47.00 43.00
G.INP: Enabled
RSCorr/RS (%): 1.1333 0.4708
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour:
I'm not against g.inp :D
Is it starting to get a little silly here, though? It seems like no one can get away with posting their valid concerns about latency ramp without someone chiming in about how 10ms~ doesn't really matter or how wonderful error correction is :)
When longstanding members adopt a dismissive attitude on certain topics there is a risk that valid technical issues get lost in the mire of p00 we already have to put up with from BT, lol.
When someone asks for help we should probably try and provide real help instead of convincing everyone there isn't really a problem :P
Hopefully, I'm not too guilty of this myself but please pick me up on it if I'm being silly :)
It varied, when I first had G.inp enabled it increased by 3ms then it increase by about 12ms and reduced sync with ECI modem, I installed the HG612 and in deceased slightly. Had a BT engineer out had the port reset abut wouldn't stick and interleave wouldn't budge and needed someone at BT OR HQ to fix the interleave on up and down. I had 9ms ping to BBC again for a few days and then G.INP reapplied with and same again.
I wonder if having ECI connected when G.INP got applied caused a higher state of interleave?
Is it starting to get a little silly here, though? It seems like no one can get away with posting their valid concerns about latency ramp without someone chiming in about how 10ms~ doesn't really matter or how wonderful error correction is :)
When someone asks for help we should probably try and provide real help instead of convincing everyone there isn't really a problem :P
Bearer 1 does have a say in latency
Bearer 1
INP: 4.00 4.00
INPRein: 4.00 4.00
delay: 3 0
PER: 16.06 16.06
OR: 95.62 31.87
AgR: 95.62 31.87
Bearer 0
INP: 46.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 80614.82 20102.08
Read adslmax post as he had delay set to 3 and it was removed for some reason and is now set at 0 and his ping did drop by 3ms backed up by thinkBB graph.
Many things...
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 5374 Kbps, Downstream rate = 21920 Kbps
Bearer: 0, Upstream rate = 4999 Kbps, Downstream rate = 22399 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 5.9 6.2
Attn(dB): 24.5 0.0
Pwr(dBm): 12.8 6.6
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 166 73
M: 1 1
T: 0 0
R: 10 8
S: 0.2370 0.4662
L: 5974 1407
D: 16 8
I: 177 82
N: 177 82
Q: 16 8
V: 5 5
RxQueue: 12 12
TxQueue: 6 6
G.INP Framing: 18 18
G.INP lookback: 6 6
RRC bits: 24 24
Bearer 1
MSGc: 90 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 10.6667 16.0000
L: 24 16
D: 1 1
I: 32 32
N: 32 32
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 0
OHFErr: 103 0
RS: 2623506496 1957702
RSCorr: 693262 1286
RSUnCorr: 0 0
Bearer 1
OHF: 41529587 797852
OHFErr: 4 0
RS: 249177152 3560509
RSCorr: 1260 78
RSUnCorr: 8 0
Retransmit Counters
rtx_tx: 23470 126
rtx_c: 14531 182
rtx_uc: 666 0
G.INP Counters
LEFTRS: 778 23
minEFTR: 22405 4997
errFreeBits: 289054759 91140315
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2964033152 0
Data Cells: 1200718095 0
Drop Cells: 0
Bit Errors: 0 0
Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0
ES: 29 0
SES: 2 0
UAS: 55 55
AS: 667078
Bearer 0
INP: 41.00 41.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 22458.21 5059.16
Bearer 1
INP: 2.50 4.00
INPRein: 2.50 4.00
delay: 0 0
PER: 16.06 16.06
OR: 47.81 31.87
AgR: 47.81 31.87
Bitswap: 420725/420725 691/693
Total time = 1 days 18 hours 23 min 58 sec
FEC: 734540 1494
CRC: 109 0
ES: 29 0
SES: 2 0
UAS: 55 55
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 8 min 58 sec
FEC: 421 0
CRC: 0 0
ES: 0 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: 659 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 18 hours 23 min 58 sec
FEC: 44626 67
CRC: 2 0
ES: 2 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 78723 147
CRC: 2 0
ES: 2 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 7 days 17 hours 17 min 57 sec
FEC: 693262 1286
CRC: 103 0
ES: 28 0
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
HELLO HG612
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 5374 Kbps, Downstream rate = 21920 Kbps
Bearer: 0, Upstream rate = 4999 Kbps, Downstream rate = 22399 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 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,1200)
DS: (33,859) (1216,1783)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 5374 kbps 21920 kbps
Actual Aggregate Tx Power: 6.6 dBm 12.8 dBm
=========================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 8.1 53.2 N/A N/A N/A 21.7 65.3 N/A
Signal Attenuation(dB): 8.1 52.7 N/A N/A N/A 30.4 65.1 N/A
SNR Margin(dB): 6.0 6.2 N/A N/A N/A 5.9 5.9 N/A
TX Power(dBm): -1.0 5.9 N/A N/A N/A 11.6 6.3 N/A
Good Bye HG612
I hadn't even noticed the aggregate rate matched the synch speed!
I don't think it does
MSGc: 90 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 10.6667 16.0000
L: 24 16
D: 1 1
I: 32 32
N: 32 32
Q: 0 0
V: 0 0
I keep forgetting what all these mean too!
Any chance we could get a short list stickied in this forum, if anyone has the definitions? :)
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 34038 Kbps, Downstream rate = 97684 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 10.8 15.3
Attn(dB): 9.6 0.0
Pwr(dBm): 13.1 -6.2
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 130 97
M: 1 1
T: 0 0
R: 8 8
S: 0.0518 0.1554
L: 21468 5457
D: 16 8
I: 139 106
N: 139 106
Q: 16 8
V: 14 2
RxQueue: 57 39
TxQueue: 19 13
G.INP Framing: 18 18
G.INP lookback: 19 13
RRC bits: 24 24
Bearer 1
MSGc: 186 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 5.3333 16.0000
L: 48 16
D: 3 1
I: 32 32
N: 32 32
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 0
OHFErr: 0 0
RS: 947457840 1963300
RSCorr: 171 349
RSUnCorr: 0 0
Bearer 1
OHF: 4242988 65384
OHFErr: 0 0
RS: 50915113 4153850
RSCorr: 0 11
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 7105 37
rtx_c: 24 2922
rtx_uc: 0 3649
G.INP Counters
LEFTRS: 0 78
minEFTR: 79999 19997
errFreeBits: 83157548 156773334
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1895028733 0
Data Cells: 110592801 0
Drop Cells: 0
Bit Errors: 0 0
Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 0
SES: 0 0
UAS: 25 25
AS: 68155
Bearer 0
INP: 46.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 80614.82 20102.08
Bearer 1
INP: 4.00 4.00
INPRein: 4.00 4.00
delay: 3 0
PER: 16.06 16.06
OR: 95.62 31.87
AgR: 95.62 31.87
Bitswap: 27974/27974 144/144
Total time = 18 hours 56 min 20 sec
FEC: 171 349
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 25 25
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 11 min 20 sec
FEC: 0 8
CRC: 0 0
ES: 0 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 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 18 hours 56 min 20 sec
FEC: 171 349
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 25 25
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 = 18 hours 55 min 55 sec
FEC: 171 349
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
HELLO HG612
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 34038 Kbps, Downstream rate = 97684 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 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,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 34038 kbps 97684 kbps
Actual Aggregate Tx Power: - 6.2 dBm 13.1 dBm
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 2.3 9.1 12.2 N/A N/A 5.6 11.4 17.1
Signal Attenuation(dB): N/A 7.9 11.6 N/A N/A 7.0 11.3 17.1
SNR Margin(dB): N/A 15.3 15.3 N/A N/A 10.8 10.9 10.8
TX Power(dBm): -128.0 -33.8 -6.1 N/A N/A 9.7 8.0 6.8
Good Bye HG612
xdslcmd --version
xdslcmd version 1.0
DSL PHY: AnnexA version - A2pv6C038m.d24j
******* Pass *********
equipcmd swversion display
software version: V100R001C01B030SP08
xdsl firmware version: A2pv6C038m.d24j
cpu version: BCM6368
cfe version: 1.0.37-102.6
display version success
Max: Upstream rate = 33916 Kbps, Downstream rate = 89004 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 8.3 15.0
Attn(dB): 13.8 0.0
Pwr(dBm): 13.2 4.2
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 130 97
M: 1 1
T: 0 0
R: 8 8
S: 0.0518 0.1554
L: 21468 5457
D: 16 8
I: 139 106
N: 139 106
Q: 16 8
V: 14 2
RxQueue: 57 39
TxQueue: 19 13
G.INP Framing: 18 18
G.INP lookback: 19 13
RRC bits: 24 24
Bearer 1
MSGc: 186 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 5.3333 16.0000
L: 48 16
D: 3 1
I: 32 32
N: 32 32
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 0
OHFErr: 0 0
RS: 1914448256 694663
RSCorr: 728315 35
RSUnCorr: 0 0
Bearer 1
OHF: 1549509 506991
OHFErr: 0 0
RS: 18593370 1927301
RSCorr: 0 3
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 113628 2
rtx_c: 204 19287
rtx_uc: 0 0
G.INP Counters
LEFTRS: 3 61
minEFTR: 79999 19997
errFreeBits: 30368494 610697078
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 3829004125 0
Data Cells: 38663116 0
Drop Cells: 0
Bit Errors: 0 0
Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 0
SES: 0 0
UAS: 23 23
AS: 24890
Bearer 0
INP: 46.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 80614.82 20102.08
Bearer 1
INP: 4.00 4.00
INPRein: 4.00 4.00
delay: 3 0
PER: 16.06 16.06
OR: 95.62 31.87
AgR: 95.62 31.87
Bitswap: 7075/7075 0/0
Welcome Visiting Huawei Home Gateway
Copyright by Huawei Technologies Co., Ltd.
Login:admin
Password:
ATP>sh
BusyBox v1.9.1 (2014-01-21 16:44:38 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 32073 Kbps, Downstream rate = 90596 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 8.6 13.5
Attn(dB): 6.1 0.0
Pwr(dBm): 12.6 -11.5
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 130 97
M: 1 1
T: 0 0
R: 8 8
S: 0.0518 0.1554
L: 21468 5457
D: 16 8
I: 139 106
N: 139 106
Q: 16 8
V: 14 2
RxQueue: 57 39
TxQueue: 19 13
G.INP Framing: 18 18
G.INP lookback: 19 13
RRC bits: 24 24
Bearer 1
MSGc: 186 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 5.3333 16.0000
L: 48 16
D: 3 1
I: 32 32
N: 32 32
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 0
OHFErr: 0 0
RS: 1657526960 620864
RSCorr: 372 144
RSUnCorr: 0 0
Bearer 1
OHF: 1341571 298237
OHFErr: 0 0
RS: 16098117 1092286
RSCorr: 0 1
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 10943 16
rtx_c: 24 16
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 79999 19997
errFreeBits: 26293195 6572136
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 3315166653 0
Data Cells: 120923360 0
Drop Cells: 0
Bit Errors: 0 0
Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 0
SES: 0 0
UAS: 24 24
AS: 21550
Bearer 0
INP: 46.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 80614.82 20102.08
Bearer 1
INP: 4.00 4.00
INPRein: 4.00 4.00
delay: 3 0
PER: 16.06 16.06
OR: 95.62 31.87
AgR: 95.62 31.87
Bitswap: 10/10 0/0
Total time = 5 hours 59 min 34 sec
FEC: 372 144
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 24 24
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 14 min 34 sec
FEC: 21 9
CRC: 0 0
ES: 0 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: 8 17
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 5 hours 59 min 34 sec
FEC: 372 144
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 24 24
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 = 5 hours 59 min 9 sec
FEC: 372 144
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
#
How does my rtx_tx per min look like compared to yours ?
I'm not sure who the question was aimed at, but mine are attached.
Just one small point -- it is G.Inp (or G.INP) not G.Imp (or G.IMP)! ;)
On the subject of "weird spiky drops in SNR", do they tend to occur when the telephone is used? Assuming that there is a telephone connected to the circuit, of course. If yes, then perhaps you would please post a few example graphs that show the effect.
Freudian slips ?? ;)Very possibly.
It really isn't as easy to suss out good/poor connections and/or faults etc. on G.INP active connections.
Downstream Upstream
General
rtx_tx 293197 57
rtx_c 15355 1023
rtx_uc 235 122
LEFTRS 396 33
minEFTR 32898 7636
errFreeBits 124200589 376781790
Bearer 0
RxQueue 26 12
TxQueue 13 6
G.INP Framing 18 18
G.INP Lookback 13 6
RRC Bits 24 24
Interleave depth 8 4
INP 47.00 41.00
INPRein 0.00 0.00
Delay 0 0
Bearer 1
Interleave depth 1 1
INP 2.50 4.00
INPRein 2.50 4.00
Delay 0 0
As for the LEFTRS values you will need to ask Roseway to supply this value on his program, but still we are awaiting for these results to be implemented into tony's MDWS, use guys don't seemed to have found a common ground relating to the values that is important for your average G.INP line.
I've added a graph of LEFTRS to the G.INP section of DSLstats. It will be in the next release.