Kitz Forum

Broadband Related => ADSL Issues => Topic started by: Weaver on January 20, 2019, 06:41:35 AM

Title: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 20, 2019, 06:41:35 AM
I’m still having problems with line #3 after the engineer’s visit this week, but lesser ones. Big noise spikes mean that connections are being broken and sync rates need to be reduced to allow for this.

I have captured an SNRM-vs-time graph - see https://ibb.co/zPkZ4vZ.

But in addition, the upstream of line 3 continues to be a big problem, with more than 9dB [!] of noise variation through the day, in the same pattern that is now becoming familiar: flat noise-vs-time graphs, with vertical cliffs between levels. The upstream high SNRM level over the last 24 hrs was 10.5dB and the low level was 1.6dB, with a target SNRM set at 6dB.

There is one difference from the earlier picture though: the appearance of spikes overlaid on the ‘plateaux’ graph.

On the SNRM-vs-time graph there are huge upward-going spikes - ie. noise disappearing for very short periods. These are the opposite of a problem of course. A new feature. Just an oddity. God only knows why such ultra-quiet brief moments are happening.

More importantly, there are also downward spikes in the upstream, ~2.5 dB high, and these are wrecking upstream reliability, since during part of the day the upstream SNRM is only 1.6dB, for many hours, until the noise level drops and the graph goes up to the next plateau. The modem chooses to hang on in there and does not drop the link, despite the downward-going spikes bring high enough to make the upstream SNRM go negative for a very short period.

Regarding the graph, unfortunately the y-axis scale is very unhelpful, as the y-axis max is far too high making it difficult to read y-values off accurately. The big upward-going spikes are creating crazy all-time high values and so stretching the y-axis range.

My main requests though:

I got the following stats from the modem and I would be very grateful if (i) someone would read them for me and comment. I would like to know what you think in general and (ii) specifically just how bad you think the error counts are. Also, I’m ashamed to say that, due to the once more increased pain drugs, I have forgotten the meaning of some of the fields in these reports, and (iii) I would be very grateful if some kind folks would go through the exact definitions of the various fields relating to errors. (I can look up the framing-related variables in G.992.3.) Here’s line #3:

Code: [Select]
VMG1312-B10A
Login: admin
Password:
 > xdslctl info --show
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    8000
Last initialization procedure status:   0
Max:    Upstream rate = 280 Kbps, Downstream rate = 2940 Kbps
Bearer: 0, Upstream rate = 344 Kbps, Downstream rate = 2606 Kbps

Link Power State:       L0
Mode:                   ADSL2 Annex A
TPS-TC:                 ATM Mode(0x0)
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        6.0             6.1
Attn(dB):        64.5            40.7
Pwr(dBm):        17.8            12.4

                        ADSL2 framing
                        Bearer 0
MSGc:           63              12
B:              76              4
M:              2               16
T:              1               8
R:              16              16
S:              1.8554          7.2453
L:              733             106
D:              1               4

                        Counters
                        Bearer 0
SF:             36390           35897
SFErr:          0               0
RS:             1255461         323009
RSCorr:         2               0
RSUnCorr:       0               0

ReXmt:          0               0
ReXmtCorr:      0               0
ReXmtUnCorr:    0               0

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    3600553         473763
Data Cells:     18185           5381
Drop Cells:     0
Bit Errors:     0               0

ES:             4181            5031
SES:            2543            709
UAS:            24374           22609
AS:             587

                        Bearer 0
INP:            29.00           2.00
INPRein:        0.00            0.00
delay:          8               7
PER:            16.00           16.30
OR:             34.49           8.83
AgR:            2628.53 351.95

Bitswap:        99/106          12/12
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: johnson on January 20, 2019, 08:13:12 AM
Clearly some erroneous values on those graphs, could you post the output of the log file from routerip:8000/data/logfile?
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: johnson on January 20, 2019, 08:43:52 AM
The spikes up to ~100db SNRM are some kind of artifact that should not be present in the graphs, a copy of the logfile would help with figuring out why. If no obvious way of ignoring them becomes apparent I can add clipping to the graph.

The negative downstream in red values are indicative of noise bursts that sometimes the modem copes with, others causing a resync.

Its hard to read much from the current stats without knowing the uptime. For instance the 24374 UAS mean nearly 7 hours with no connectivity, either unplugged from the line or with the modem unable to gain sync.

Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: jelv on January 20, 2019, 09:45:16 AM
It seems OpenReach are incapable of keeping your four lines working properly for any significant period so I wonder if AAISP could arrange for you to have booked weekly engineer visits? This would be without you having to raise a new fault each time - engineer just turns up and asks what needs looking at this week.  :P
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: j0hn on January 20, 2019, 11:28:30 AM
lol....
as Johnson says there's no way you could possibly have 100dB SNRM on the upstream (or downstream), if only.

The downstream looks shaky though, but I'd send the log to Johnson to have a look over before doing anything else.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 20, 2019, 04:12:16 PM
There is a real problem though, it’s not just the graphs. Downstream sync rate is now down to 265k from 3055k [!] with huge packet loss and frequent disconnects. Will swap modem out as a rule-out. AA notified.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: johnson on January 20, 2019, 04:35:13 PM
I do not doubt there is problem with the line.

I just want to find a way of fixing the graphs so they are more readable and can maybe give you a better view of whats going on.

Also, as I mentioned previously, uptime is needed when posting ES, SES UAS etc. Its hard to make sense of them without it.

Edit:clarity
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 21, 2019, 07:00:00 AM
I thought one of the stats’ reports does give time intervals - is that correct? Apologies for posting the wrong report then, as indeed it’s useless without durations.

The uptime was 1d 16h 28m. Luckily I recorded that figure separately.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: aesmith on January 21, 2019, 09:31:56 AM
Could the 100dB spikes be mis-reporting of negative values?  I had that once when collecting via SNMP from (I think) Linksys, presumably some signed/unsigned mismatch in the MIB.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 21, 2019, 01:56:08 PM
I was just thinking the same thing. The Netgear DG834v1 used to display garbage when SNRM values went below zero, a sign bit problem. Was fixed later on.

However I think there are visible downward-going spikes which do reach negative values, so if the basic idea is correct, then the sign bit problem would have to be elsewhere in the arithmetic, somewhere earlier. That’s the only thing that I can think of to save the idea.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Chrysalis on January 21, 2019, 02:55:01 PM
yeah it either means negative value or loss of sync with those crazy readings.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 21, 2019, 02:59:35 PM
And nightmare: line 2 has also gone bad again, so it appears, although I ought to reserve judgment until it has been retested at 6dB target SNRM downstream instead of the current 3dB, which is potentially asking a lot (although 3dB is normally fine in these lines with no problems over many many months).

Line 2 now losing sync, huge packet loss etc.

And this weird message

BT Test xDSL Copper Test:Pass Standalone sub test passed successfully.Pass Max product, DCN, in synch, tests OK DS06:The system cannot carry out the test because it appears that a call is in progress on the line.Please ensure that there are no calls on the line and retry the test.Otherwise raise a fault report
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 21, 2019, 03:17:01 PM
Ah, now something sensible

BT Test xDSL Copper Test:Fail Line test failed report fault to OR, appointment advised.Fail Line test failed report fault to OR, appointment advised. T024:FAULT - Loop (Rectified)
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: burakkucat on January 21, 2019, 05:16:42 PM
BT Test xDSL Copper Test:Pass Standalone sub test passed successfully.Pass Max product, DCN, in synch, tests OK DS06:The system cannot carry out the test because it appears that a call is in progress on the line.Please ensure that there are no calls on the line and retry the test.Otherwise raise a fault report

Low insulation, A- to B-wire, will appear to the automated test-head as a telephony call in progress. I.e. the circuit appears to be looped.

BT Test xDSL Copper Test:Fail Line test failed report fault to OR, appointment advised.Fail Line test failed report fault to OR, appointment advised. T024:FAULT - Loop (Rectified)

The observed rectified loop confirms my earlier, above, suspicion.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 21, 2019, 05:55:24 PM
Ah, makes sense. Low insulation, could be abrasion? Something running over the cable lying on the ground at the side of the road maybe? Or huge hairy cows stamping on it? (There are actually a lot of highland - hairy orange - cows on the lower part of the northern slopes of the road, by the Harrapul fank, where repairs were carried out a couple of years ago.)
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: burakkucat on January 21, 2019, 06:01:40 PM
Yes, yes and yes.  :)

. . . by the Harrapul fank, . . .

Forgive my forgetfulness but is that location just past the cattle-grid, on the right-hand side of the road, when leaving the village?
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 22, 2019, 02:00:54 AM
There are two fanks, it is confusing. Apart from the one right by my house (which is next to the cattle grid below me at the northern boundary of Heasta), there’s another one, the ‘Harrapul Fank’ (https://goo.gl/maps/xHXPfdqp6bq), a few miles north of me. That fank is near the northern end of the road a few hundred metres from the main road at a suburb called Harrapul. There was damage to the copper lines somewhere around there a few years ago, mentioned in a thread. It perhaps a bit further south than the Harrapul fank and there was more damage further south still, south of where the stream Allt a’ Choire goes under the road at a tiny bridge, where the road begins to climb. The aforementioned highland cattle hang out there and never venture up over the hill as far south as Heasta. Their grub is there, maybe that’s why. The lines at the Harrapul fank must be buried now because lorries and other vehicles pull off the road there and park up and would be running right over the cable all the time but the damage is very infrequent. A couple of years ago a huge lorry full of tree trunks was there and there was a problem with the copper so no prizes for guessing.

That was the ridiculous situation twenty years ago at the Heasta fank, with vehicles running right over the cable bundle and parking on top of it. Obviously caused repeated catastrophic damage until BT sobered up and buried the cable. Which makes you wonder why in the name of all that’s holy they had not just done the right thing in the first place.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: burakkucat on January 22, 2019, 03:41:01 PM
Ah, now I see it. (And it doesn't help that the heathens of Goggle spell Harrapul as "Harrapool".) Thank you for pointing my view onto the correct location.  :)
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 23, 2019, 12:08:00 AM
I managed to get it to come up in street view. The phone line presumable]y has to criss the road from the west side to the east side at some point along the southwards run, as it is visible on the east side of the road at the stream by the tiny bridge over the Allt a’ Choire south of the aforementioned Harrapul fank. So at the fank, I don’t know which side of the road the line is on. It is buried underneath either all the loose stone or the mud by one side of the road or the other.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: burakkucat on January 23, 2019, 12:51:45 AM
Upon taking an as close a look as possible at the location of the bridge, there are two ducts that cross over the stream to the east of the bridge. As the road also turns to the south-east, directly south of the bridge, a straight-line projection of the two ducts would then take them to the western side of the road. But who knows, for sure?  :-\
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 23, 2019, 02:03:05 AM
@Burrakucat -  I’m just not sure exactly what happens around the bridge, although I’m seeing what you’re seeing. On the higher ground further up the hill, further to the south than the bridge, the cable can be seen lying on the rocks on the east side of the road and it is visible on the east side all the way to me and down into Heasta itself for at least some of the way.

At the Heasta cattle grid if memory serves the cable should be visible going over the stream immediately south of the Heasta fank. South of the Heasta cattle grid, ie right by my house, the cable is east of the road and west of the stream (Allt an Daraich - trans ‘stream of the oak’; traditionally an ‘allt’ was supposed to be required to have two steep sides, or so I was told. This does qualify as such, where it goes over two impressive waterfalls, one by my house and one below it. In some places you see a ‘leth-allt’ ([ˈʎe(h) aʊɫ̪t̪]), which has one steep side.)
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: burakkucat on January 23, 2019, 07:03:39 PM
With those extra details, I can confirm the presence of the cable exactly as you describe.

The two ducts crossing the stream, south of the bridge, must be some other service . . . may be to the (farm?) buildings, accessed through the gate to the west of the road.

Once south of the Heasta fank and over the cattle grid, the cable is a little more hidden. But knowing that it is there (the pole from which your two aerial drops emanate is a good give away!), it can be spotted further down the road, into the village.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: johnson on January 23, 2019, 08:21:47 PM
Sorry to ask again Weaver, but if you could capture a log file (routerip:8000/data/logfile) containing one of the jumps to 100+db it would be great if you could save and send it to me. If it is as simple as negative values starting at 100 then it will be trivial to fix that in the next firmware, but really need some data to make sure.  :)

Have made a fix for changing the time after boot via NTP, updating all the current log entries, also some nicer javascript with buttons for all available graphs etc, and updating each file under /data on access, but it doesnt seem worth putting out another version if the SNRM graphs are still messed up on your line.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 24, 2019, 04:21:28 AM
I’m sorry for that. I simply overlooked your original post at the time. Duh. Unfortunately just now none of the modems are exhibiting that phenomenon so I will have to wait until they do. :-(
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 24, 2019, 01:03:51 PM
Three OR vans here at the same time. One man has come all the way over the mountains from Fort William, so that’s a five hour round trip. Section of cable being mended at cabinet 10, many users affected apparently. Repairs might continue tomorrow. Also one or more colleagues are out in the field because all our guys here are waiting on him finishing.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: burakkucat on January 24, 2019, 05:40:17 PM
I wonder if it is at the PCP10, on the north side of the A87, or at the associated AIO, Huawei equipped cabinet, on the south side of the A87 that is undergoing the remedial cabling work?

(Currently being in the haggis hunting season, I wonder if the fault is a result of revenge action by those beasties . . .  :-\  ;)  )
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: j0hn on January 24, 2019, 07:57:42 PM
Can a PCP have an associated AIO cabinet?

Aren't all AIO cabinets given their own PCP number?
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: burakkucat on January 24, 2019, 09:47:33 PM
That is a very good point.

I know, thanks to Mrs Weaver's photography, that the AIO cabinet, south of the A87, is marked with a big 10. What I do not know, is the number of the PCP on the north side of the A87 and west of the Claymore Restaurant.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 24, 2019, 09:56:55 PM
About two cabs, an FTTC one and a PCP one that are on the main road by the Claymore restaurant, I can’t see these cabs in Magenta Codelook (https://www.telecom-tariffs.co.uk/codelook.htm?xid=356235&cabinets=10782) somehow. Am I using the site incorrectly? It says both ‘updated 2019’ and ‘updated 2017’, whatever that means.



Our gentlemen were offered refreshments, declined.

Here’s a pic taken by Mrs Weaver https://ibb.co/7vgRbnN


Line 4 BBEU20709519:
Today 15:32:50   BT Test xDSL Status Check:Pass Standalone sub test passed successfully.Pass OK. Circuit In Sync BRAS=2535kb/s FTR=2278kb/s MSR=2848kb/s ServOpt=1 I/L=I A SERVICE OPTION CHANGE ORDER IS IN PROGRESS ON THIS LINE Up Sync=550kb/s LoopLoss=39.9dB SNR=6.1dB ErrSec=0 HECErr=0 Cells=0 Down Sync=2865kb/s LoopLoss=63.5dB SNR=6.1dB ErrSec=0 HECErr=N/A Cells=0
Today 15:16:18   Today 15:17:20   BT Test xDSL Copper Test:Inconclusive More diagnostics required Line test failure. Algorithm unable to continue. Inconclusive More diagnostics required Line test failure. Algorithm unable to continue. DS05:Test Failure - Please Retry - if unsuccessful report problem to OR via a Trouble Report


Line 3 BBEU20700055:
Today 15:32:48   BT Test xDSL Status Check:Pass Standalone sub test passed successfully.Pass OK. Circuit In Sync BRAS=2912kb/s FTR=2278kb/s MSR=2848kb/s ServOpt=1 I/L=I A SERVICE OPTION CHANGE ORDER IS IN PROGRESS ON THIS LINE Up Sync=382kb/s LoopLoss=39.8dB SNR=6dB ErrSec=0 HECErr=0 Cells=0 Down Sync=3290kb/s LoopLoss=63.5dB SNR=2.9dB ErrSec=0 HECErr=N/A Cells=0
BT Fault 3-948750620269 SFI has been cancelled as line is not RWT
Right When Tested; End User Equipment;IP session terminates on RAS, check cust logon


Line 2 BBEU29735631:
Today 17:00:00   BT Fault 3-948741377434 SFI has been cancelled as line is not RWT
Right When Tested; End User Equipment;All BT tests completed ok, diagnostics show no fault condition
Today 15:32:25   Today 15:32:32   BT Test xDSL Status Check:Pass Standalone sub test passed successfully.Pass OK. Circuit In Sync BRAS=2385kb/s FTR=1817kb/s MSR=2272kb/s ServOpt=1 I/L=I Resysch A SERVICE OPTION CHANGE ORDER IS IN PROGRESS ON THIS LINE Up Sync=535kb/s LoopLoss=40.3dB SNR=6dB ErrSec=0 HECErr=0 Cells=0 Down Sync=2763kb/s LoopLoss=63.5dB SNR=6.1dB ErrSec=0 HECErr=N/A Cells=0
Today 11:05:02   Today 15:32:18   Management review TR 219AUX needs a review
Today 15:16:32   Today 15:17:26   BT Test xDSL Copper Test:Inconclusive More diagnostics required Line test failure. Algorithm unable to continue.Inconclusive More diagnostics required Line test failure. Algorithm unable to continue. DS05:Test Failure - Please Retry - if unsuccessful report problem to OR via a Trouble Report



Speeds are all back to normal.

Haggises will be subject to a mass slaughter in a week in the lowlands, maybe even up here in The Highlands to some extent, as a result of greatly increased mobility. It could be that haggises (‘taigeisean’, ‘prainnseagan’ or just ‘maragan(-gallda)’) are flooding north taking refuge, and gnawing on cables, as Burrakucat suggests.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: burakkucat on January 24, 2019, 10:20:35 PM
Almost a flock (or swarm) of Openreach vans!  :)

In the report for BBEU20700055 --

Quote
BT Fault 3-948750620269 SFI has been cancelled as line is not RWT

I read that as "the Special Faults Investigation appointment has been cancelled as the line is not Right When Tested." I am baffled by the logic.  ???
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 24, 2019, 11:40:56 PM
Janet related a message from the OR workers that there was a damaged section of cable between the NSBFD exchange and cabinet 10 so the whole section is being replaced this week. That’s why many users were or are expected to be affected. I asked my beloved if she would be good enough to survey neighbours / grapevine.

Sync rates on all lines back to normal today after I forced downstream SNRMs back to 6dB.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: aesmith on January 28, 2019, 09:54:08 AM
I read that as "the Special Faults Investigation appointment has been cancelled as the line is not Right When Tested." I am baffled by the logic.  ???

Broadband fault/appointment cancelled until copper line fixed?
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: burakkucat on January 28, 2019, 04:49:52 PM
Broadband fault/appointment cancelled until copper line fixed?

That could certainly be an interpretation but it only becomes possible with the knowledge of the cable status, as relayed by word of mouth. 
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on January 28, 2019, 08:02:34 PM
I never saw any OR engineers’ notes this time round.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on February 11, 2019, 05:39:23 PM
@johnson

I finally managed to catch an example of high positive spikes, during a day of chaos today. Here’s /data/logfile - see attached.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: johnson on February 11, 2019, 05:55:25 PM
@johnson

I finally managed to catch an example of high positive spikes, during a day of chaos today. Here’s /data/logfile - see attached.

Thanks for thinking of capturing it! The attachment doesnt seem to have worked though, could you maybe try dropbox or some other way of sharing it?
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: j0hn on February 11, 2019, 06:04:35 PM
Thanks for thinking of capturing it! The attachment doesnt seem to have worked though, could you maybe try dropbox or some other way of sharing it?

I thought it was just me. Gives me a failed to download error.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Ronski on February 11, 2019, 07:10:08 PM
The txt file attachment is showing a size of 0kB, perhaps that's why it's giving an error.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: burakkucat on February 11, 2019, 09:38:23 PM
The txt file attachment is showing a size of 0kB, . . .

The result of a revenge attack by the haggis, I believe.  ;)
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on February 23, 2019, 02:40:51 AM
Attached /data/logfile and this time I am not seeing an attachment size of 0. This has happened to me several times before with the forum software, getting zero-sized attachments. I don’t know what I am doing wrong or what is going wrong -
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on February 23, 2019, 02:51:57 AM
Can anyone else see that attachment now? If not, what’s the easiest alternative?
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: johnson on February 23, 2019, 03:33:21 AM
No it works fine, have a copy. I shall ponder over it!  :D
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: burakkucat on February 23, 2019, 06:36:36 PM
Can anyone else see that attachment now?

Yes, that's fine. I have a copy of the file . . . but I do not know what to make of it. I see a total of 1030 lines, 437 of which record a "NOSYNC" state.
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: johnson on March 02, 2019, 08:35:03 PM
So yes it appears the assumption that negative upstream values rolled over to 101, 102 etc was correct.

From:
(https://i.imgur.com/XB1SRyY.png)

To:
(https://i.imgur.com/ESdqZa8.png)

By subtracting all upstream values > 100 from 100.

Shall add it to the next version, thanks for the data Weaver!
Title: Re: Continuing lesser line #3 problems - noise - Request for read of stats
Post by: Weaver on March 03, 2019, 02:48:17 AM
I think you mentioned adding other data. Points for attn upstream+downstream would be useful to me, as the root of my problem is I believe due to both the attn figures jumping up.