Print

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

[roseway]

Has reliance on that package been added since v5.2?

No, I was grasping at straws, trying to work out how the program is apparently running while not displaying its GUI. I'll have to sleep on it.

[burakkucat]

I'll have to sleep on it.

A wise move. I still have v5.2 available for use, so there is no great urgency.

[NewtronStar]

Just started running Version 5.3 on Raspberry Pi, would have had it up an running hours ago but the boot-config just vanished after a reboot and zero display but putty was fine so just re-built the config.txt file and it's all good again 

[renluop]

My probably naive question is, does the HLOg graph have any value in assessing ADSL/ADSL2+ connections?

[roseway]

It might have some value if it has a really unusual shape (indicating something badly wrong), but it's much more useful over the wider frequency range of VDSL2.

[renluop]

Thanks! As it happens I reckon mine would be OK with being pretty horizontal at lower down then ~30 deg slope.

[roseway]

I'll have to sleep on it.

A wise move. I still have v5.2 available for use, so there is no great urgency.

Having slept on it and a bit more, I'm still unable to explain this. Either the program is hanging during initialisation, or something else is causing it not to display its window. All of the changes since V5.2 relate to things which happen during recording, not during initialisation, but there have been no significant changes in the initialisation.

My best idea at present is to make a diagnostic version which logs everything which happens during initialisation and saves it to a file. Would you be willing to give this a test?

[burakkucat]

My best idea at present is to make a diagnostic version which logs everything which happens during initialisation and saves it to a file. Would you be willing to give this a test?

Why, yes. Most certainly. But please do not make it a priority. 

[les-70]

  Thanks for the work improving things it is generally working well here on XP and will try raspberry pi soon.     but: -

Just one issue spotted -- the 24 hours now reset correctly - with the exception of the SES.  e.g. the modem uptime correctly  shows
SES   Up   0      0      0      0   
   Down   0      0      0.08      2.01
but the 24 hour right from the first start show strange large values including upstream ones e.g.
SES   Up   0      0.17      10.0      241   
   Down   0.02      1.34      80.2      1925   
On reset the 24 hour SES values don't go to zero but jump to much larger values suggesting some incorrect number that is not reset is being used. 

[roseway]

Thanks for the report. I think that the SES issue will sort itself out, although I will check again.

[broadstairs]

Eric I am unable to understand the average values for SES when compared to the graph. The averages has values but scrolling the graph shows no SESs at all a straight line of zero since starting DSLStats.

Stuart

[roseway]

Stuart, I recognise this issue, which is the result of loading previously saved data into the new enlarged array which holds it. If you reset the values the issue will go away after a period. Alternatively if you shut down DSLstats, delete the file errors.dat from the directory where the configuration files are saved, then restart DSLstats, you should find that correct averages are shown from then on.

[les-70]

Restarting after deleting errors.dat seemed to have fixed the SES issue.  But after one new SES a reset of the 24 hours does not reset the new 24 hour SES back to zero.  The previous SES is continuing to be counted.  I seem to always need to delete errors.dat and restart to get the correct response.

   The SES in the 24 hours are behaving like the ES did in the previous version.

[broadstairs]

Eric the SES thing is not a huge issue for me as I dont seem to have any  but I do understand now why I see what I see....

Stuart

[les-70]

Eric the SES thing is not a huge issue for me a

   Agreed, I am only trying to be helpful in reporting issues.  To prove I now have the pi on 5.3.  On the pi I never use the 24 hour reset.  I find the reset is mainly handy when testing and after a resync.