Print

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

[WWWombat]

I should also add that sometimes I don't really want to zoom the timeline down either.

When I'm analysing these things, I usually have 2 or 3 frames in use, where the other frames keep track of changes to INP or resyncs, or ES's, CRC's, re-transmission counters, etc - so I can see the interplay between multiple graphs at the same time. Having correlated timelines makes this easy ... and getting matching zoomed timelines ends up quite awkward - especially if you have to fiddle to move a spike off one side.

[tbailey2]

I've been back and tried again. I was trying to replicate your image, and can only achieve the one attached below. I cannot zoom in a way that gets rid of both spikes.

Reduce the time period to 24 hours in that particular case which works... it may not always with Google in control

[NewtronStar]

I often have to zoom in on MDWS especially for FECS as large spikes just overpower the smaller ones and you have to use the cursor/mouse pointer on the X axis to see the smaller values.

 

[WWWombat]

Reduce the time period to 24 hours in that particular case which works... it may not always with Google in control

Ah, right. That works OK. So you can only zoom in so much (down to a 6 hr window) when the original view is set to "24 hours". If it is set to "2 days", the smallest window becomes 12 hr, and if set to "10 days", the smallest window becomes 60 hours.

Great if you only need to zoom into the last few hours, provided there is no spike within 6 hours, but less good when I want to zoom into the equivalent point 3 days ago. I guess we get whatever Google decides...

I often have to zoom in on MDWS especially for FECS as large spikes just overpower the smaller ones and you have to use the cursor/mouse pointer on the X axis to see the smaller values.

That's the alternative - to zoom in as much as you can, then hope that hovering the mouse can produce enough separate results in the pop-up.

[Bald_Eagle1]

FWIW, I have attached ongoing stats montages from skynewb's connection for the latest 1, 6 & 21 days.

[atkinsong]

Morning all. I have had G.INP applied overnight with some interesting results. Previously I had been comparing a Vigor 2760 (Lantiq VRX288) in VDSL mode with an HG612 as modem. Synch comparisons pre-G.INP were:

Vigor 2760     48680

HG612           53049

Following the application of G.INP the comparative synchs are:

Vigor 2760    52812

HG612          50320

So, following on from other reported figures regarding HH5a comparisons with HG612, a picture seems to be emerging where with G.INP applied, Lantiq chipsets have the edge over Broadcom on ECI cabs.

In my case there was no interleaving applied either before or after G.INP.     

[Dray]

I wonder if there's a way of monitoring the stats like DSLStats and MyDslWebStats.

[atkinsong]

I wonder if there's a way of monitoring the stats like DSLStats and MyDslWebStats.

Not that I'm aware. All that is available from the Draytek is shown below. ReTx shown as on at the far end means downstream!

[tbailey2]

Ah, right. That works OK. So you can only zoom in so much (down to a 6 hr window) when the original view is set to "24 hours". If it is set to "2 days", the smallest window becomes 12 hr, and if set to "10 days", the smallest window becomes 60 hours.

I had a look at the API as I haven't changed much for 18 months and there are some new settings... After a bit of fiddling, you can now zoom from 24 hours down to a just over an hour - and don't forget you can zoom several times consecutively until max is reached (== timespan x zoomfactor of 0.05 so 1.2 hours for 24 hours now) and right-click to reset.

I've set this up for SNRM and FEC at the moment and will add others later. The current default zoom is x 0.25 hence the 6 hours from 24 hours.
If you zoom a last hour range - it shows 3 minutes at max zoom i.e. 3 plots 

Example attached for ayeaye

Edit: I've subsequently changed it to .041 so it's exactly an hour's span for max zoom over 24 hours with a resolution of 10 minutes per division, Example attached for skyECI.

[ktz392837]

Have to say after waiting so long for Ginp why is it slowing sync speeds?

I do not have interleaving but was hoping for some improvement as reported by other users when it was rollout out last year for huawai. 

If I have to use my eci modem just to keep approx the same sync speed I will lose mdws unless support is added for eci modems.

[skyeci]

would there be any possibility of a re-sync upwards as my upstream has come down from 20mb to 17mb or is this the way dlm will leave it

All those errors that caused the bursts of CRCs and ES's (upstream) that triggered the DLM intervention have now become FEC's, leaving a zero ES rate. That means DLM has deployed a solution that successfully defeats the noise, but it doesn't mean the noise itself has gone.

I would imagine that DLM could choose to de-intervene if it only looks at the ES rate. However, my gut feeling is that it probably also checks the FEC rate, to see if that isn't too high; this would make sense to me, but has no official confirmation whatsoever.

Unfortunately, the MDWS graphs for FECs auto-scale themselves, and the sporadic, but large, spikes of downstream FECs make the behaviour of the upstream FECs almost invisible, so it is hard to tell.

My upstream does have delay,interleave and g.inp....

Your upstream now has had an old-style DLM intervention, setting an INP of 2.5 and a delay of 8ms; the modems have turned on FEC and interleaving. However, it doesn't look to have G.INP running upstream; I wouldn't expect it, either.

Thanks for your comments. I have just had BT OR engineer here to have a look. Showed him the data and as our estate DP is outside our house he has connected me on to a new pair. He also confirmed my line length of 320m. He said that at the cabinet there are no lines next to mine with broadband at the moment.

My line has been reset and g.inp is now showing as off. I have never seen my upstream snrm so high (now 9.5).US back to pre g.inp rate. Seen a slight increase in DS . Now at 57/20

Will be interesting to see what happens in the next few days. Thanks to the engineer for helping as he came before some months ago when I started this...

[rob]

Looks like G.INP is rolling out to ECI cabinets in full force now as my cabinet was enabled yesterday.  I'm not logging stats but my HG612 is showing this now:

Code: [Select]

# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 16897 Kbps, Downstream rate = 68028 Kbps
Bearer: 0, Upstream rate = 16797 Kbps, Downstream rate = 64845 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): 6.3 6.1
Attn(dB): 18.8 0.0
Pwr(dBm): 13.3 6.9
VDSL2 framing
Bearer 0
MSGc: -6 14
B: 243 238
M: 1 1
T: 0 61
R: 10 16
S: 0.1198 0.4529
L: 16959 4504
D: 1 1
I: 254 255
N: 254 255
Q: 8 0
V: 0 0
RxQueue: 51 0
TxQueue: 17 0
G.INP Framing: 18 0
G.INP lookback: 17 0
RRC bits: 0 24
Headline figures show an improved downstream sync (was ~59Mbps previously) but most of this increase is likely down to the modem switching back to fast path instead of interleaved (was approximately 1200 depth) and upload has increased marginally.

[daleski75]

Hopefully mine will switch over at some point as well

Sent from my MI PAD 2 using Tapatalk

[kitz]

Any chance of an updated sheet?

AyeAye and Jasonkruys have also been enabled today.   Ive updated the list to show the values for data that we have so far.

We'd need to see a lot more of the before and after raw framing data to figure that out.

Ive added in the R & N values for those that have provided it.  Using the R&N values Ive also shown the  % of RS overhead.  Unfortunately we only have that data for 3 people.


-----
PS

If any of the guys who dont use MDWS want to give me their data in the same format so I can add to the list - please do.

[Ronski]

Hopefully mine will switch over at some point as well

Neither of mine have switched over yet either