Ah, thank you, my friend, I forgot.
My memory is completely shot, my friend, all the drugs I’m afraid. It’s a very big problem for me, and a regular source of embarrassment in the forum,
, although Burrakucat help to keep me straight. The DSLstats alarm feature is excellent then.
My existing main ‘wellness summary’ program gives one three-valued, global single summary result across all modems: all good, minor problem(s) or major problem(s). It integrates the whole of the data for all four modems. It also knows ‘expected value ranges’ too - that is, allowed ranges of values of things such as SNRM down/up per line and min sync rate up/down. The program only shows detailed stats if there’s a problem. I have a different program, stats overview, which combines reasonably detailed stats reports on all four modems, without making any judgements.
So my wellness summary tool’s main purpose is perhaps not the same as that of DSLstats; it’s aim is to make judgements, not to display all the data, and it means that I don’t have to carefully read all the stats for each modem. DSLstats may well be able to do the same, given what you told me about alarms. Mr Johnson’s custom firmware already does approximately what DSLstats does in terms of stats reporting, mind you DSLstats could very well be more comprehensive - I’d need to leave others to judge that.
My wellness summary tool also has HCD detection in it, which of course DSLstats will never have heard of. That’s a valuable test for me as its detection gives a very early warning of impending serious failure, as the HCD severity will build, downstream speed will droop ever lower, eventually to unusable speeds, and then finally the link will start to fail altogether. So with HCD detection, my code is attuned to this particular well-known disease that afflicts me.
So does the rationale make sense ? DSLstats’ ability to run all the time is very important and I need to take a look at it.
However my existing code is very well tuned to what I need and so is Mr Johnson’s custom ZyXEL code. And I need specialist things such as the HCD detection too.
Another point, if I do decide to go for the port, is that writing the code would be a big learning opportunity for me.
