Print

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

[kitz]

Try this one (executable only): http://www.s446074245.websitehome.co.uk/files/dslstats.exe.zip

Lovely Jubbly thanks 

Code: [Select]

U0 U1 U2 U3 D1 D2 D3
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4

[roseway]

Can you copy the contents of Telnet data --> Connection stats to me please, so I can try to find what's going wrong.

It's okay now, it seems to display the wrong time for the first couple samples, then displays the correct time. Do you still want the info?

Yes please. I'm hoping it may help with diagnosing the access violations.

[roseway]

Lovely Jubbly thanks 

Code: [Select]

U0 U1 U2 U3 D1 D2 D3
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4

You're welcome. The only thing is that it's only supposed to copy that line when one of the values changes. Does it repeat every sample?

[kitz]

As it only records atten at startup and changes, theres only been that one sample so far.  I will let you know if it continues to duplicate.

[roseway]

Thanks

[kitz]

I was out last nite and only just had chance to see what was going on

It would appear that its adding a new line each time it gathers stats
I have lots and lots of rows like this

Code: [Select]

Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4

[ryant704]

I'm assuming you haven't currently changed the way errors are reported?

Also, telnet shows

Since Link time = 49 days 17 hours 2 min 46 sec

When actual Link Time is 58 Days 5 Hours and 24 Mins

[roseway]

I was out last nite and only just had chance to see what was going on

It would appear that its adding a new line each time it gathers stats
I have lots and lots of rows like this

I was afraid that might be the case, hence my question a few messages ago. It's clearly not extracting/recording the values correctly, so it thinks there's a change with every sample.

I'll get working on it.

[roseway]

I'm assuming you haven't currently changed the way errors are reported?

Also, telnet shows

Since Link time = 49 days 17 hours 2 min 46 sec

When actual Link Time is 58 Days 5 Hours and 24 Mins

I haven't changed the error reporting code since v3.6. When I see your telnet stats text I'll hopefully be able to make sense of the problems you've reported.

The link time issue is a bug in the Broadcom firmware - it stops incrementing the "Since link time" counter after 49 days and a few hours. What DSLstats does is, when the reported value gets over 49 days it switches over to reporting the AS (available seconds) value, which continues to increment properly.

[roseway]

I was out last nite and only just had chance to see what was going on

It would appear that its adding a new line each time it gathers stats
I have lots and lots of rows like this

Another one to try: http://www.s446074245.websitehome.co.uk/files/dslstats32W-3.73.zip

Don't just copy the executable. Copy all the files, because other things have changed. It would be best to start from a clean position, so either delete/rename dslstats.ini or copy this version to a different directory. You may even find that traffic monitoring works with this version if you select HG612 (VDSL2) in the traffic monitoring setup.

[ryant704]

They're on page 1 I believe?

[kitz]

Another one to try: http://www.s446074245.websitehome.co.uk/files/dslstats32W-3.73.zip

Don't just copy the executable. Copy all the files, because other things have changed. It would be best to start from a clean position, so either delete/rename dslstats.ini or copy this version to a different directory. You may even find that traffic monitoring works with this version if you select HG612 (VDSL2) in the traffic monitoring setup.

ty eric

I moved all the old files out (aside from my logs), then started afresh with the new version. 

Still getting this Im afraid

Code: [Select]

U0 U1 U2 U3 D1 D2 D3
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4
  Line Attenuation(dB): 0.8 17.8 28.9   N/A 11.1 24.4 38.4

Also should there be a timestamp recorded for any changes?

[roseway]

Still getting this Im afraid

Oh dear, sorry about that.

Also should there be a timestamp recorded for any changes?

There should be really, yes, but I haven't provided it. I'll add it to the next version (when I find out what's causing the endless repetition ).

[roseway]

They're on page 1 I believe?

Sorry, I've done it again, mixing you up with someone else. I blame the heat and humidity. I think I'm going to go and cool down.

[les-70]

  Eric,

   After a few days and more tests I can't get the past days traffic saved in file with either a PC shutdown or a modem power down.  However only a PC shutdown does not seem to matter as the full modem values pick up on PC startup and with only a modem shutdown the program seems clever enough to cope and not go to zero.   It seems to be the combined PC and modem shutdown that is the issue. 

  Might the save action which occurs on program exit be allowed to occur with each sample.  Perhaps via an option if it is a significant overhead.   I guess that would be one fix.