Print

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

[roseway]

This version has two changes relative to the previous v5.4.1/2:

- Upstream and downstream FEC values are correctly uploaded to MDWS
- The G.INP status of the connection is uploaded to MDWS

http://www.s446074245.websitehome.co.uk/downloads.html

[Edit] Raspberry Pi version is now included

[krypton]

Thank you.
Upstream FEC errors are now visible on MDWS.

[NewtronStar]

This version has two changes relative to the previous v5.4.1/2:

- Upstream and downstream FEC values are correctly uploaded to MDWS
- The G.INP status of the connection is uploaded to MDWS

I don't think my brain can handle seeing even more errors being displayed on MDWS the errored seconds are enough for me at the moment 

[roseway]

The FECs are the good guys.

[jid]

All up and running on the RPi here Eric, all looking good working brilliantly

As always, thanks for all of your hard work you put into DSLStats and for making in RPi compatible 

[NewtronStar]

The FECs are the good guys.

RPI and PC versions updated to 5.4.3 and as expected running very well indeed no errors to paste here yet 

[AArdvark]

Many Thanks, all up and running now.

Appreciate the excellent work you do for the greater good of all 'kitzen'.

[roseway]

Thanks all

[NewtronStar]

I have noticed since the 5.4.3 release the MAX/Attainable down stream rate in the telnet data connection stats becomes stuck this is happening daily only on the PC version the RPi is fine.

The only way to get the correct attainable is to turn off DSLstats and restart DSLstats on the PC

[roseway]

Nothing has changed in recent versions of DSLstats which would explain this. The Telnet Data --> Connection Stats information is the unprocessed data directly from the modem, and the way it's collected hasn't changed.

I presume other items such as SNR Margin still change by small amounts? If so, the data collection is working normally, and there's no reason for a single item within that data to get stuck.

Since G.INP was applied I notice that my attainable values hardly change at all, so I wonder if you're seeing some coincidental result of when you happened to restart DSLstats?

[NewtronStar]

I'll keep an eye on it as i say it happens randomly all other data is updating as normal.

[mhisani]

I have a problem which i've now seen on a friends linux box where typing in any of the input boxes puts double the input. it's most percuiiar..

[krypton]

Probably you can solve this if you quit IBus. If there is a keyboard layout icon on the taskbar select quit otherwise type killall ibus-daemon.

[roseway]

Thanks for that suggestion, morphium, which I agree with. One other possibility is that it relates to the use of Scim to support certain keyboard layouts.