Well done Roseway I can see we can toggle on/off the SNRM in Bitloading in V5 without having to deselect other setting, and V5.0 :thumbs:Blind as well probably, but I cannot see that. Another Technicolor limitation, maybe?
when I click on the icon in the task bar to open DSLStats...
Blind as well probably, but I cannot see that. Another Technicolor limitation, maybe?
14 Jul 2014 10:39:49 Recording started
14 Jul 2014 10:39:54 Timeout while retrieving stats
14 Jul 2014 10:39:54 No stats received
14 Jul 2014 18:20:08 Unable to login to modem/router
14 Jul 2014 18:27:14 Recording started
14 Jul 2014 18:27:20 Timeout while retrieving stats
14 Jul 2014 18:27:20 No stats received
15 Jul 2014 05:28:08 Configuration files stored in C:\Users\Paul\AppData\Local\dslstats\
15 Jul 2014 05:28:11 Recording started
Download succeeded. File saved to C:\Users\Paul\Desktop\dslstats32W-5.0.1.zip
15 Jul 2014 05:28:41 Previous sample still being processed
15 Jul 2014 05:28:42 Updated version downloaded
15 Jul 2014 05:38:32 Configuration files stored in C:\Users\Paul\AppData\Local\dslstats\
15 Jul 2014 05:38:32 Snapshot folder is C:\DSL-Stats\
15 Jul 2014 05:38:35 Recording started
15 Jul 2014 05:38:37 No bitloading data received
15 Jul 2014 05:38:39 IP address is now xxx.xx.xxx.xx
15 Jul 2014 05:39:08 No bitloading data received
15 Jul 2014 05:39:37 No bitloading data received
15 Jul 2014 05:40:07 No bitloading data received
15 Jul 2014 05:40:37 No bitloading data received
15 Jul 2014 05:41:07 No bitloading data received
15 Jul 2014 05:41:37 No bitloading data received
15 Jul 2014 05:42:07 No bitloading data received
15 Jul 2014 05:42:38 No bitloading data received
15 Jul 2014 05:43:07 No bitloading data received
15 Jul 2014 05:43:37 No bitloading data received
15 Jul 2014 05:44:14 Timeout while collecting bitloading data
15 Jul 2014 05:44:14 No bitloading data received
15 Jul 2014 05:44:14 Telnet timeout
15 Jul 2014 05:44:37 No bitloading data received
15 Jul 2014 05:45:07 No bitloading data received
15 Jul 2014 05:45:37 No bitloading data received
15 Jul 2014 05:46:07 No bitloading data received
15 Jul 2014 05:46:37 No bitloading data received
15 Jul 2014 05:47:08 No bitloading data received
15 Jul 2014 05:47:37 No bitloading data received
15 Jul 2014 05:48:07 No bitloading data received
15 Jul 2014 05:48:37 No bitloading data received
15 Jul 2014 05:49:07 No bitloading data received
15 Jul 2014 05:49:38 No bitloading data received
15 Jul 2014 05:50:07 No bitloading data received
15 Jul 2014 05:50:37 No bitloading data received
15 Jul 2014 05:51:07 No bitloading data received
15 Jul 2014 05:51:37 No bitloading data received
15 Jul 2014 05:52:07 No bitloading data received
15 Jul 2014 05:52:38 No bitloading data received
15 Jul 2014 05:53:07 No bitloading data received
15 Jul 2014 05:53:37 No bitloading data received
15 Jul 2014 05:54:07 No bitloading data received
15 Jul 2014 05:54:37 No bitloading data received
15 Jul 2014 05:55:07 No bitloading data received
15 Jul 2014 05:55:37 No bitloading data received
15 Jul 2014 05:56:07 No bitloading data received
15 Jul 2014 05:56:37 No bitloading data received
15 Jul 2014 05:57:08 No bitloading data received
15 Jul 2014 05:57:38 No bitloading data received
15 Jul 2014 05:58:08 No bitloading data received
15 Jul 2014 05:58:37 No bitloading data received
15 Jul 2014 11:49:21 Recording started
15 Jul 2014 11:49:23 *** Second stage login failure. Did you enable the option "Requires command to enter shell" by mistake?
15 Jul 2014 11:49:23 Second stage login failed
sh
Thank you. v5.0.1 works like a charm since 5 hours.
Unfortunately the resyncs-counter seems not to work. It never displayed anything different than zero although I had some resyncs. How does the counter get triggered?
Eric might I make a suggestion about alerts.... would it be possible to have an alert when SNRM dropped by a number of db? Watching mine I suddenly get a spike drop from say 7db to 5 db (a drop of 2) I might also later in the evening see a drop of 2 db but from 5 to 3, so I think it might be a good thing if you could do this rather than just setting a drop to value.
Stuart
Quote15 Jul 2014 11:49:21 Recording started
15 Jul 2014 11:49:23 *** Second stage login failure. Did you enable the option "Requires command to enter shell" by mistake?
15 Jul 2014 11:49:23 Second stage login failed
sh
@snadge
Sorry, but at the moment I'm having trouble digesting all the information. I'll come back to you as soon as I can.
DSLAM/MSAN type: BDCM:0xa321 / v0xa321
Modem/router firmware: AnnexA version - A2pD037h.d24a
DSL mode: ADSL2+
Status: Showtime
Uptime:
Resyncs: 0 (since 16 Jul 2014 22:57:26)
Downstream Upstream
Line attenuation (dB): 25.5 14.6
Signal attenuation (dB): 29.3 14.3
Connection speed (kbps): 19488 1212
SNR margin (dB): 4.9 9.0
Power (dBm): 18.6 12.1
Interleave depth: 96 8
INP: 1.00 1.50
RSCorr/RS (%): 0.2657 1.0839
RSUnCorr/RS (%): 0.0304 0.0000
ES/hour: 8.01 0.01
@snadge: I've had a report from a Win 8 user that setting the compatibility mode to Win 7 seems to have solved some crashes he was experiencing. If you're on Win 8 too, this might possibly provide a fix for the time being.
I configure DSLstats to sample every 60 seconds. In the fullness of time, I stop recording and close down the GUI. At a later date, I re-invoke DSLstats and start recording . . . only to find that the utility is sampling every 30 seconds!
I hope you're not going mad. :)Well even if I use localhost it doesn't work. If I telnet to the port it accept a connection. But if I try to "get" anything the connection is terminated. The same in any browser,
Here is how it's currently configured on my system: http://www.s446074245.websitehome.co.uk/webserver.html (http://www.s446074245.websitehome.co.uk/webserver.html)
Unfortunately I can't reproduce this. After shutting down DSLstats, can you check ~/.dslstats/dslstats.ini, and look in the [graphs] section for the item "Samplerate=NNNNN". This is the sample timing in milliseconds. Does it show the correct value as it was set in the GUI?
For some reason it works now! I didn't touch anything!
I noticed my HG612 rebooted itself about 17 hours ago!
(Two minutes later . . . ) On checking the value via the configuration tab I see it is set to 60 seconds. [img alt=:-[]http://forum.kitz.co.uk/Smileys/kitzemotes/embarrassed.gif I've no idea what has happened, for the problem was apparent on four separate days. The moment I make a report, it mysteriously fixes itself.
Perhaps all the configuration options could be "greyed out" whilst the utility is in its recording state? Maybe the ability to change certain settings whilst the utility is in its active mode could be the source of weird results. For example, I can obtain (repeatedly and upon demand) an exception by going to the Configuration ---> Traffic Monitoring tab and changing the string in the "Modem/router model:" box by a manual process.
List index (0) out of bounds.
Press OK to ignore and risk data corruption.
Press Cancel to kill the program.
I can't explain the miraculous clearing of the sample rate issue, but I'm grateful for it. :)
Hi, I'm running the latest version on linux mint 64 bit. Its a fresh install, I have an older version (4.x) in another directory. Every 24 hours I get this message
List index (0) out of bounds.
Press OK to ignore and risk data corruption.
Press Cancel to kill the program.
It seems to coincide with when I first run the program. It stops recording at the same time each day with the same message. Closing the program and starting again clears the error. Not yet sure how to reproduce it, not being a real problem until now, I came back in and the program had stopped logging for nearly two hours until I paused recording and then started it again.
I wouldn't expect it to work by telnet, it's an http server.
Hi, I'm running the latest version on linux mint 64 bit. Its a fresh install, I have an older version (4.x) in another directory. Every 24 hours I get this message
List index (0) out of bounds.
Press OK to ignore and risk data corruption.
Press Cancel to kill the program.
It seems to coincide with when I first run the program. It stops recording at the same time each day with the same message. Closing the program and starting again clears the error. Not yet sure how to reproduce it, not being a real problem until now, I came back in and the program had stopped logging for nearly two hours until I paused recording and then started it again.
That's a very good clue, thank you. There are very few things which happen on that timescale, so I can concentrate on those. I'll do my best to fix it.
The description of the traffic monitoring feature is here: http://www.s446074245.websitehome.co.uk/trafficconfig.html
When the feature is enabled an new tab "Traffic" is revealed, and here you get the option to display monthly or daily traffic as a bar chart, or per-minute traffic as a scrolling graph.
It probably is me but I can't see how to configure automatic snapshots of the traffic graph as distinct to saving a textual file. :-\
It probably is me but I can't see how to configure automatic snapshots of the traffic graph as distinct to saving a textual file. :-\
It's missing from the "Autosave graphs" section.
Hi, I'm running the latest version on linux mint 64 bit. Its a fresh install, I have an older version (4.x) in another directory. Every 24 hours I get this message
List index (0) out of bounds.
Press OK to ignore and risk data corruption.
Press Cancel to kill the program.
It seems to coincide with when I first run the program. It stops recording at the same time each day with the same message. Closing the program and starting again clears the error. Not yet sure how to reproduce it, not being a real problem until now, I came back in and the program had stopped logging for nearly two hours until I paused recording and then started it again.
That's a very good clue, thank you. There are very few things which happen on that timescale, so I can concentrate on those. I'll do my best to fix it.
I don't know if it's easily done but what I think might be quite handy is the ability to overlay the previous synchs (1? 2? 3?) HLOG/QLN over the current one :)
26 Jul 2014 09:30:27 No bitloading data received
26 Jul 2014 09:30:57 No bitloading data received
26 Jul 2014 09:31:27 No bitloading data received
26 Jul 2014 09:31:57 No bitloading data received
26 Jul 2014 09:32:26 No bitloading data received
26 Jul 2014 09:32:57 No bitloading data received
26 Jul 2014 09:33:27 No bitloading data received
26 Jul 2014 09:33:57 No bitloading data received
26 Jul 2014 09:34:27 No bitloading data received
I stopped running stats yesterday afternoon. Today the first time I double-click dslstats file the error message appears immediately. Click Cancel and the error appears every time until I click OK. Click OK, close the program, run it again and no error. :)
I stopped running stats yesterday afternoon. Today the first time I double-click dslstats file the error message appears immediately. Click Cancel and the error appears every time until I click OK. Click OK, close the program, run it again and no error. :)
As I can't reproduce this error I've been going through the program line by line, looking for any code which could conceivably return this particular error message. I've found just one place where it could happen, and made some changes which will avoid it happening. I'll try to upload a test version some time this weekend.
I notice pbparams only seems to update on program start and not with re-syncs or other events.