04-08-2022 15:12 - edited 04-08-2022 15:23
The VM resolve team tell me the area 3 high utilisation fault F009369438 has now been fixed well ahead of the scheduled fix date of 30/9/22. But we are still experiencing an unreliable connection. @Martin_N you advised yesterday that the issues would resolve when the area fault was fixed but they haven't - so it seems something else is going on with our Hub 4 connection.
We seem to have half hourly spikes on the BMQ and a poor SNR on several channels. Any suggestions gratefully received
4 | 163000000 | 3.500000 | 32.321487 | QAM256 | 4 |
1 | 139000000 | 3.599998 | 33.956509 | QAM256 | 1 |
2 | 147000000 | 3.400002 | 31.403784 | QAM256 | 2 |
3 | 155000000 | 3.400002 | 31.335388 | QAM256 | 3 |
5 | 171000000 | 3.000000 | 33.376591 | QAM256 | 5 |
6 | 179000000 | 2.299999 | 34.345688 | QAM256 | 6 |
7 | 187000000 | 1.400002 | 35.083549 | QAM256 | 7 |
8 | 195000000 | 0.900002 | 36.609653 | QAM256 | 8 |
9 | 203000000 | 0.900002 | 37.355988 | QAM256 | 9 |
10 | 211000000 | 1.500000 | 37.636276 | QAM256 | 10 |
11 | 219000000 | 1.700001 | 38.605377 | QAM256 | 11 |
12 | 227000000 | 1.799999 | 37.636276 | QAM256 | 12 |
13 | 235000000 | 1.700001 | 37.636276 | QAM256 | 13 |
14 | 243000000 | 1.299999 | 37.636276 | QAM256 | 14 |
15 | 251000000 | 1.299999 | 36.609653 | QAM256 | 15 |
16 | 259000000 | 1.799999 | 37.355988 | QAM256 | 16 |
17 | 267000000 | 2.099998 | 37.355988 | QAM256 | 17 |
18 | 275000000 | 2.700001 | 37.355988 | QAM256 | 18 |
19 | 283000000 | 3.200001 | 37.636276 | QAM256 | 19 |
20 | 291000000 | 3.599998 | 38.605377 | QAM256 | 20 |
21 | 299000000 | 3.500000 | 38.605377 | QAM256 | 21 |
22 | 307000000 | 2.500000 | 37.636276 | QAM256 | 22 |
23 | 315000000 | 1.799999 | 37.355988 | QAM256 | 23 |
24 | 323000000 | 1.599998 | 37.636276 | QAM256 | 24 |
25 | 331000000 | 1.599998 | 37.636276 | QAM256 | 25 |
26 | 339000000 | 1.500000 | 37.636276 | QAM256 | 26 |
27 | 347000000 | 1.599998 | 38.605377 | QAM256 | 27 |
28 | 355000000 | 1.700001 | 37.636276 | QAM256 | 28 |
29 | 363000000 | 1.799999 | 38.605377 | QAM256 | 29 |
30 | 371000000 | 2.099998 | 38.605377 | QAM256 | 30 |
31 | 379000000 | 2.299999 | 38.983261 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
4 | Locked | 32.321487 | 1022466 | 0 |
1 | Locked | 33.956509 | 331511 | 0 |
2 | Locked | 31.403784 | 3659342 | 0 |
3 | Locked | 31.335388 | 4751173 | 0 |
5 | Locked | 33.376591 | 156370 | 0 |
6 | Locked | 34.345688 | 39573 | 0 |
7 | Locked | 35.083549 | 16929 | 0 |
8 | Locked | 36.609653 | 13036 | 0 |
9 | Locked | 37.355988 | 14329 | 0 |
10 | Locked | 37.636276 | 13189 | 0 |
11 | Locked | 38.605377 | 13970 | 0 |
12 | Locked | 37.636276 | 16840 | 0 |
13 | Locked | 37.636276 | 25927 | 0 |
14 | Locked | 37.636276 | 41943 | 0 |
15 | Locked | 36.609653 | 52659 | 0 |
16 | Locked | 37.355988 | 45200 | 0 |
17 | Locked | 37.355988 | 37160 | 0 |
18 | Locked | 37.355988 | 25571 | 0 |
19 | Locked | 37.636276 | 18691 | 0 |
20 | Locked | 38.605377 | 16950 | 0 |
21 | Locked | 38.605377 | 20746 | 0 |
22 | Locked | 37.636276 | 33072 | 0 |
23 | Locked | 37.355988 | 53523 | 0 |
24 | Locked | 37.636276 | 78104 | 0 |
25 | Locked | 37.636276 | 102274 | 0 |
26 | Locked | 37.636276 | 106381 | 0 |
27 | Locked | 38.605377 | 113443 | 0 |
28 | Locked | 37.636276 | 125319 | 0 |
29 | Locked | 38.605377 | 123963 | 0 |
30 | Locked | 38.605377 | 126334 | 0 |
31 | Locked | 38.983261 | 121600 | 0 |
33 | 96 | 4K | 1880 | QAM2048 | 759 |
Answered! Go to Answer
19-08-2022 22:28 - edited 19-08-2022 22:31
No Zoie I am afraid we are not fixed after all sadly
I reposted the latest downstream router data and while the power levels and SNR are fine for the 3.0 channels for 3.1 -7.2 dBmV is out of spec for channel 33 and is behind the high number of uncorrectables
Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
33 | Locked | 38 | -7.2 | 2496975759 | 1216841 |
…so we have yet another engineer on Wednesday 24/8
One thing gets fixed but knocks another out…
22-08-2022 08:34 - edited 22-08-2022 08:36
OK - have things settled down now? The 3.1 downstream power is now - 5.9 dBmV and the lowest SNR is 36.6 dB. Upstream looks OK.
Thanks so much for help
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
4 | 163000000 | 5.500000 | 37.355988 | QAM256 | 4 |
1 | 139000000 | 6.199997 | 38.983261 | QAM256 | 1 |
2 | 147000000 | 5.800003 | 37.355988 | QAM256 | 2 |
3 | 155000000 | 5.699997 | 36.609653 | QAM256 | 3 |
5 | 171000000 | 4.900002 | 37.636276 | QAM256 | 5 |
6 | 179000000 | 3.900002 | 38.605377 | QAM256 | 6 |
7 | 187000000 | 3.099998 | 38.983261 | QAM256 | 7 |
8 | 195000000 | 2.700001 | 38.983261 | QAM256 | 8 |
9 | 203000000 | 2.400002 | 38.983261 | QAM256 | 9 |
10 | 211000000 | 2.599998 | 40.366287 | QAM256 | 10 |
11 | 219000000 | 2.700001 | 40.366287 | QAM256 | 11 |
12 | 227000000 | 2.599998 | 38.983261 | QAM256 | 12 |
13 | 235000000 | 2.400002 | 38.983261 | QAM256 | 13 |
14 | 243000000 | 2.200001 | 38.983261 | QAM256 | 14 |
15 | 251000000 | 2.500000 | 38.983261 | QAM256 | 15 |
16 | 259000000 | 3.099998 | 38.983261 | QAM256 | 16 |
17 | 267000000 | 2.900002 | 38.983261 | QAM256 | 17 |
18 | 275000000 | 3.200001 | 38.605377 | QAM256 | 18 |
19 | 283000000 | 3.299999 | 40.366287 | QAM256 | 19 |
20 | 291000000 | 3.299999 | 40.366287 | QAM256 | 20 |
21 | 299000000 | 2.900002 | 38.983261 | QAM256 | 21 |
22 | 307000000 | 1.900002 | 38.983261 | QAM256 | 22 |
23 | 315000000 | 1.200001 | 38.605377 | QAM256 | 23 |
24 | 323000000 | 0.799999 | 38.605377 | QAM256 | 24 |
25 | 331000000 | 0.599998 | 38.605377 | QAM256 | 25 |
26 | 339000000 | 0.500000 | 38.983261 | QAM256 | 26 |
27 | 347000000 | 0.400002 | 38.605377 | QAM256 | 27 |
28 | 355000000 | 0.200001 | 38.983261 | QAM256 | 28 |
29 | 363000000 | 0.000000 | 38.983261 | QAM256 | 29 |
30 | 371000000 | 0.000000 | 38.983261 | QAM256 | 30 |
31 | 379000000 | 0.200001 | 38.983261 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
4 | Locked | 37.355988 | 339 | 0 |
1 | Locked | 38.983261 | 275 | 0 |
2 | Locked | 37.355988 | 662 | 0 |
3 | Locked | 36.609653 | 729 | 0 |
5 | Locked | 37.636276 | 202 | 0 |
6 | Locked | 38.605377 | 204 | 0 |
7 | Locked | 38.983261 | 215 | 0 |
8 | Locked | 38.983261 | 210 | 0 |
9 | Locked | 38.983261 | 217 | 0 |
10 | Locked | 40.366287 | 144 | 0 |
11 | Locked | 40.366287 | 145 | 0 |
12 | Locked | 38.983261 | 162 | 0 |
13 | Locked | 38.983261 | 241 | 0 |
14 | Locked | 38.983261 | 349 | 0 |
15 | Locked | 38.983261 | 312 | 0 |
16 | Locked | 38.983261 | 189 | 0 |
17 | Locked | 38.983261 | 182 | 0 |
18 | Locked | 38.605377 | 189 | 0 |
19 | Locked | 40.366287 | 134 | 0 |
20 | Locked | 40.366287 | 175 | 0 |
21 | Locked | 38.983261 | 252 | 0 |
22 | Locked | 38.983261 | 461 | 0 |
23 | Locked | 38.605377 | 795 | 0 |
24 | Locked | 38.605377 | 1160 | 0 |
25 | Locked | 38.605377 | 1589 | 0 |
26 | Locked | 38.983261 | 1778 | 0 |
27 | Locked | 38.605377 | 2212 | 0 |
28 | Locked | 38.983261 | 2746 | 0 |
29 | Locked | 38.983261 | 3154 | 0 |
30 | Locked | 38.983261 | 3299 | 0 |
31 | Locked | 38.983261 | 2960 | 0 |
33 | 96 | 4K | 1880 | QAM4096 | 759 |
33 | Locked | 39 | -5.9 | 811987495 | 1039768 |
on 22-08-2022 09:13
Hi 2tw2,
Thank you for keeping us updated with regards to this issue.
I'm glad that this all seem to be working for you now.
Please do let us know if you need help in the future.
^Martin
on 22-08-2022 09:15
Hi Martin
so in your view is this all ok
now?
thx