Print

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

[roseway]

Changes since v2.73:

- fixed bug which left gaps in SNR per tone graph when included with bitloading in compressed form
- fixed issue which resulted in large peaks in displayed CRC and FEC levels after emerging from standby
- changed method of determining CRC/FEC errors so as to work with all compatible modem/routers
- added summary of average error rates over various periods
- added "Copy to clipboard" button to the above, and also to the basic stats page
- minor cosmetic changes to accommodate larger fonts

http://rsux.plainroad.me.uk

[ColinS]

  Thanks for all the hard work!

[broadstairs]

Eric would it be possible to have the program maximise itself if there is a new version. My problem is that I start and run and exit from minimised now and dont see the new version warning which only shows if I maximise it. I only saw the new version once I'd been here on the forum.

Stuart

[roseway]

Thank you Colin.

Stuart, yes that would certainly be possible. I'll add it to the next version.

[burakkucat]

Downloaded and now undergoing tests . . . 

[rhohne]

Is anyone else seeing negative CRC changes per min?

As a side note which fields are used to determine the max attainable values as they are appearing as zero.

[DG834GT using DGTeam Rev 1018 firmware]

[roseway]

The max attainable speeds are obtained from one of the early lines in the output of the --stats command:

Code: [Select]

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:   8000
Max:   Upstream rate = 1060 Kbps, Downstream rate = 8776 Kbps
Path:   0, Upstream rate = 1020 Kbps, Downstream rate = 7618 Kbps 
I guess that the DG834GT doesn't include this information.

The bitswaps CRC data also comes from the --stats command, so if you would be good enough to copy the 'Connection stats' data to me I can see where it goes wrong. Thanks in advance.

[Edit - corrected error]

[rhohne]

The DG834GT does have the max speed, however it's in a different field

Code: [Select]

adslctl info --stats
adslctl: ADSL driver and PHY status
Status: ShowtimeRetrain Reason: 8000
Channel: FAST, Upstream rate = 1155 Kbps, Downstream rate = 13207 Kbps
Link Power State: L0
Mode:                   ADSL2+
Channel:                Fast
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):       3.7             6.1
Attn(dB):       30.5            17.8
Pwr(dBm):       0.0             12.4
Max(Kbps):      15568           1160
Rate (Kbps):    13207           1155

....

                        Counters
SF:             197152834               188583066
SFErr(CRCErr):  150528          0

One thing I have noticed is that the Upstream CRC occasionally  has values and then drops back to zero.

[roseway]

Thanks. I can deal with the Max values now.

The CRC totals wouldn't normally return to zero unless there was a re-sync, so maybe there's a error in the reported values. I can trap out any reduction in the totals between samples and treat them as a re-sync, but it may not deliver a useful result. I'll give it some attention.

[rhohne]

I wouldn't call them returning to zero, more like false error reporting where a low value is reported for a couple of minutes. Independent logging indicates that about 3% of upstream CRC values contain a none zero value. None of my logging indicates that a re-sync has taken place.

[roseway]

Maybe I'm misunderstanding, but in the routers I've been able to test, the reported CRC and FEC values are cumulative, i.e. they never go down except as a result of a resync (which resets them to zero).

[rhohne]

I think its a bug in the firmware. On all other routers I have used the errors are cumulative. Its not worth doing special for these values. My concern was the values used on the y-axis, if the base value was zero then the graph looks OK.

[roseway]

Ok, thanks, I'll sort it out. The graph shouldn't display negative values, so there's a bug in rs-ux/w as well.

[roseway]

As we're not entirely sure what the router is reporting, I'm going to offer two alternative ways of dealing with the situation of the reported CRC total in a sample being less than in the previous sample:

1. Zero values will be plotted instead of negative values (the default option)
2. Negative values will be converted to positive values

There will be an extra option on the Graphs configuration page to make this choice.

[c6em]

Another idea for the future.
On the status lines at the bottom of the screen where you list DS and US sync & margin maybe at the end you can put if the Channel path is "Fast" or "Interleaved"
This can be taken from D the interleaver depth on the G.dmt & ADSL2+ framing stats where D=1 is fast path.
I note that several routers get it wrong on their own summary
My ADSL info stats reports the channel as FAST when actually it is D=64 downstream and D=8 upstream ie both interleaved.


I did get a one-off crash event when I swaped the view to the FEC's graph.
It said as I recall floating point error and gave me the option to accept or cancel to end program
I accepted and it exited anyway
Haven't yet repeated it so ignore/store away for future if it rears its head again.
If it happens again I'll be better forwarned to record the exact sequence which led to the occurance.
(This is using the lastest edition)

Keep up the good work - its great.