Print

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

[AArdvark]

Yes, all up to date.

[kitz]

In the early days if you used both then there was a possibility that one or both programs could crash as they tried to collect stats at the same time..  and youd end up with one or both not recording, which you may notice for some time.  So times are staggered so that one runs on the minute and the other at 40seconds past.   DSLstats can also detect if HG612stats is still running

I'll leave the technical explanation to BE/Eric, but basically when you set cooperation mode, then the worst case situation if DSLstats detects that HG612modem stats is still harvesting data should be that DSLstats will miss a sample

for eg

Code: [Select]

10 Sep 2014 23:55:35 1 instance(s) of HG612_stats.exe running, sample missed
10 Sep 2014 23:55:35 Unable to login to modem/router
10 Sep 2014 23:56:35 1 instance(s) of HG612_stats.exe running, sample missed
10 Sep 2014 23:56:35 Unable to login to modem/router

I have now set the 'Not HG622' option in DSLstats.

You dont need to check that - selecting the correct model from the drop down list will be sufficient to identify your router.



If youre getting lots of unable to collect due to HG612 stats still running then something is perhaps wrong with the harvesting time.
HG612 modem stats should  be done by the time DSLstats starts at 40seconds past the minute.   However there may be still times when it isnt such as if say your processor is busy.. or conversely, if you have a high spec PC there may be times when your PC processor is much faster than the routers, so you end in a loop.  This used to happen for me with my i7 processor..  so BE kindly built in a setting to account for this.

The settings within HG612modemstats where you can adjust the speed for your processor type are

Settings > Additional settings > PCSpeed.

Although I have (what was at the time) a very fast PC - it will run fine at Medium setting.

[AArdvark]

Thanks kitz, I have all set as you have advised.

I will try the 'co-operation' setting again and leave it for an hour or so.
(The 'no stats' was as it should work 'Worse-case' according to your info.)

I have changed the PC setting from fast to medium.

Thanks everyone for the wonderful software and support which is SO helpful. 

[roseway]

Most of it has already been said, but I'll just say what happens in DSLstats when the 'co-operation' option is set (this all applies to Windows users only):

1. DSLstats delays the start of sampling (if necessary) so that it occurs between 35 and 40 seconds after the minute.

2. When a new sample is due, DSLstats checks if either HG612_stats.exe or HG612_current_stats.exe is running, and if it is, that sample is missed. This happens for a maximum of 5 samples, after which it stops the check for the next half an hour.

3. When sampling starts, a do-nothing process called dslstatssampling.exe is launched, and killed when sampling ends. HG612_Modem_Stats checks for this process before running, and delays running until the process aborts.

These measures should ensure that conflicts between the two programs are avoided.


A brief note about the HG622 messages: DSLstats attempts to detect the HG622 automatically, because it needs to modify its login behaviour slightly for this model. Sometimes, particularly under error conditions, DSLstats wrongly detects other models as the HG622, and login fails with the error messages mentioned above. If you see this behaviour you can avoid the error messages by setting the 'Not HG622' option.

[adslmax]

Nice work roseway. Here is DSLstats v5.0.2

Code: [Select]

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 36567 Kbps, Downstream rate = 102416 Kbps
Path: 0, Upstream rate = 19999 Kbps, Downstream rate = 79987 Kbps

Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 12.2 23.2
Attn(dB): 0.0 0.0
Pwr(dBm): 12.5 -0.2
VDSL2 framing
Path 0
B: 239 237
M: 1 1
T: 23 42
R: 0 16
S: 0.0955 0.3781
L: 20104 5374
D: 1 1
I: 240 127
N: 240 254
Counters
Path 0
OHF: 19101274 3732662
OHFErr: 26 10
RS: 0 3459443
RSCorr: 0 166
RSUnCorr: 0 0

Path 0
HEC: 13 0
OCD: 0 0
LCD: 0 0
Total Cells: 562169315 0
Data Cells: 26312143 0
Drop Cells: 0
Bit Errors: 0 0

ES: 12 6
SES: 0 0
UAS: 17 17
AS: 31592

Path 0
INP: 0.00 0.00
PER: 1.64 3.97
delay: 0.00 0.00
OR: 116.54 64.47

Bitswap: 11 26

Total time = 8 hours 46 min 51 sec
FEC: 0 0
CRC: 26 0
ES: 12 6
SES: 0 0
UAS: 17 17
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 1 min 51 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 8 hours 46 min 51 sec
FEC: 0 0
CRC: 26 0
ES: 12 6
SES: 0 0
UAS: 17 17
LOS: 0 0
LOF: 0 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Since Link time = 8 hours 46 min 31 sec
FEC: 0 166
CRC: 26 10
ES: 12 6
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#

The only one problem is Error processing signal attenuation in the event log but...the Telnet Data still ok below:

Code: [Select]

Signal attenuation (dB) U0 U1 U2 U3 D1 D2 D3
14 Sep 2014 23:47:19 2.3 12.4 18.8 N/A 6.9 16.0 24.8

Average error rates over 24 hour period:

Code: [Select]

Per second Per minute Per hour  Per day

CRC Up 0 0 0.11 2.74
Down 0 0 0.11 2.74

FEC Up 0 0.03 1.71 41.1
Down 0 0 0 0

HEC Up 0 0 0 0
Down 0 0 0.11 2.74

ES Up 0 0.01 0.68 16.4
Down 0 0.02 1.37 32.8


[AArdvark]

All appears to be working OK.

Many Thanks.

At least I will have a record of the 'Quality' of my FTTC line as it dissipates under the onslaught of Crosstalk & DLM 

[kitz]

The only one problem is Error processing signal attenuation in the event log but...the Telnet Data still ok below:

Turn off signal attenuation in Config > Items to Monitor.
It will still continue to report under Telnet Data > attenuation log.

I think its something to do with the fact that the HG612 and Zyxel dont report signal attenuation as one combined figure. The figure its expecting is total upstream and total downstream, but these routers only report 0.0

Code: [Select]

                Down            Up
SNR (dB):        8.4             11.7
Attn(dB):        0.0             0.0
Pwr(dBm):        14.3            4.4
Instead its split down into the 3 separate bands.

Code: [Select]

Signal Attenuation(dB):  0.4     17.6    26.8     N/A     N/A    10.4    23.4    37.0 
Turning off the first, doesnt stop the second set being logged under the Telnet data tab.