Print

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

[roseway]

I have this running nicely with a Zoom X4 5751. The only issue I have is a lack of bit loading information. The modem returns

adsl info --Bits
adsl: ADSL driver and PHY status
Status: Showtime  Retrain Reason:       4
Channel: INTR, Upstream rate = 448 Kbps, Downstream rate = 4928 Kbps
Tone number      Bit Allocation
>

Sadly I can't do anything about that, because the --Bits command is what DSLstats uses as its source of bitloading information. It seems odd that the data is missing though.

[kitz]

I think I've fixed this. The band detection logic was confused by an unusual value in the SNR margin section of your pbParams output - the U0 value is shown as 'NR' (what does that mean?). The result was that it believed that band U0 wasn't being used. I've corrected this, and you can download the corrected version at http://www.s446074245.websitehome.co.uk/files/dslstats32W-4.50.2.zip . This is the full archive, but you only need to replace the executable dslstats.exe.

By the way, this version also fixes the other issue you reported. It's now not possible to edit the login details while recording is in process; you have to stop or pause recording first.

Please test this version and (hopefully) confirm that the band colours are now correct.

Thanks vm eric, I somehow missed your post the other day. 

I can confirm that the band colouring is now correct.   
Ive also tested the config changes only work when paused and that seems good too.

FYI Im using the settings from the VMG1312 in the drop-down box, but you may also like to add the VMG8324-B10A to your page here confirming that it works with dslstats. 

Thank you for all the work put into dslstats

[roseway]

Thanks for confirming that.

I'll add the model to the compatibility list.

[kitz]

I seem to have hit a slight hiccup that may be worth mentioning.  I had to change the router password last night, & Ive been unable to get dslstats to work since.

The error I get is "Second stage login failure".

Ive tried renaming the .ini to force a new one, but I still get the same error when I try to change the password from the default which is set in dslstats.
 


---

Ive just tried downloading a fresh copy of 4.50.1 (pre-fix) which works fine - but obviously has the graph colour error....
so next I dropped in your fix just like I did the other day.. and it works, but obviously I've lost all my preferences.

[roseway]

That's an odd one. That error message should never be seen unless you have the login option "Requires command to enter shell" ticked. Presumably you haven't? If you still have the renamed dslstats.ini which didn't work, could you check if the value "Usesecondstage" in the Login section is set.

In the meantime I'll try to reproduce the error.

[kitz]

Is this what you need?

Code: [Select]

Encrypted=1
Router=Zyxel VMG1312-B
IPaddress=192.168.1.1
Telnetname=admin
Telnetpassword={removed}==
Usesecondstage=1
Shelltext=
TelnetPort=23
Annex M=0
Thomson=0
Synchronise=0

[kitz]

oh... just looked at the current working one

Code: [Select]

Encrypted=1
Router=Zyxel VMG1312-B
IPaddress=192.168.1.1
Telnetname=admin
Telnetpassword={removed]==
Usesecondstage=0
Shelltext=
TelnetPort=23
Annex M=0
Thomson=0
Synchronise=0

So somehow I must have accidentally ticked 'requires command to enter shell' whilst changing the password?
I dont recall doing so, but if Im reading the config correctly, then I must have .

[roseway]

That's it. The option "Usesecondstage" is set. I wonder how that happened? If you change that value to zero, DSLstats should work with that version of dslstats.ini (assuming that the password is now correct).

I do still need to look at this more closely, to see if the unintended setting of that option was the result of a bug, and also to see if I can improve on how the program handles this situation.

[kitz]

Oh well glad mystery is sorted.   sorry to have bothered you.. 
i did try fix it myself before mentioning it..  Guess I never spotted I may have got a bit trigger happy when changing the password.

Wasnt having a good night last night, so I must have done something stupid.   
Bit sick of PCs & routers atm - should be elsewhere, but waiting a call back from Zyxel.   

[roseway]

Even if it was an accidental mistake, I can still learn something from it and try to give better feedback to the user.