Morning B*cat and thanks for the graphs hope you had a pleasant catnap.
You're welcome. And yes, thank you. I'm now thinking about my next meal.
>> m quite surprised to see all of the CRC errors and significant SNRm changes are only happening on the upstream. Any initial hunch as to why that is?
Usually an indication of filters, internal wiring, or a physical line fault (HR).
I'm getting a preliminary sensation of frequency-dependent semi-conducting joint . . .
I'm also getting a feeling of deja-vu... its a shame HG612 modem stats wont work on linux.
I do have the new, revised version of a
HG6xx_stats utility tucked in my 'what-not'. It will harvest the data from
Huawei HG610,
HG612 &
HG622 devices and writes to a log file in the
Eagle-specified format. It is fully functioning for any Linux kernel based OS -- the user would be expected to compile the source code for her/his target system -- but I have not yet fully incorporated the
BGW compatibility code that my
Avian colleague has requested.
When I last used the
HG6xx_stats utility, I had it executing on a
Raspberry Pi. Once sufficient data had been harvested from my
HG622 modem/router (operating in ADSL2+ mode), I passed a copy of the log file to
No-Feathers and he processed it with his code, running on
BGW.
Below is an image of my
R-Pi, upon which
HG6xx_stats was executing. All communication to/from the
R-Pi was via the Ethernet cable and the log file was written to the USB memory stick.