QAM woes, again.

[Icantcrabhere]

Hi, this may be a somewhat lengthy post,
I'll have to split hub readings from the other day / after a restart today.

The basics out of the way first:

Superhub 3, modem mode. - wired
I have made sure all connections are finger tight.
I have checked both the online fault checker and the phone one

The following first set of logs I post will be from then (Before rebooting the hub).

The other night, 7th July - I noticed a huge latency spike, this turned out to be a Partial service error.

Obviously along with that comes a flood of post-RS errors, as expected.


The following first set of logs I post will be from then (Before rebooting the hub).
I am sorry for the formatting on this particular section:

Time Priority Description
07/07/2022 00:07:15 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:07:14 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:07:14 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:06:16 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:06:15 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:05:14 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:05:14 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:03:28 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.3 3057 6731
2 Locked 40.9 1858 7104
3 Locked 40.9 1836 7435
4 Locked 40.9 1828 5666
5 Locked 40.3 1621 5757
6 Locked 40.3 1627 5633
7 Locked 40.3 1811 5775
8 Locked 40.3 1808 5749
9 Locked 40.3 1573 5101
10 Locked 40.3 1876 5284
11 Locked 40.3 1689 5669
12 Locked 40.3 1896 5574
13 Locked 40.3 2822 6718
14 Locked 40.3 1878 6648
15 Locked 40.9 1831 6211
16 Locked 40.3 1893 6552
17 Locked 40.3 2115 6110
18 Locked 38.9 2531 7290
19 Locked 40.3 2399 7146
20 Locked 38.6 3513 7108
21 Locked 38.9 3432 7220
22 Locked 38.9 3493 6851
23 Locked 38.9 3308 6668
24 Locked 38.6 3401 6886

Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 10 0
2 ATDMA 0 0 12 0
3 ATDMA 0 0 6 0
4 ATDMA 0 0 12 0


Even through this, all my upstream QAM were locked to 64,
Until today, that is.
The following posts will show todays logs AFTER a reboot.

[Icantcrabhere]

Another update,

Still no fixed power levels,
Now I'm getting packet loss
and a channel has dropped back to 16QAM.

Going to have to split this post into two, due to text limits.

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	411000000	-6.5	38	256 qam	1
2	419000000	-6.7	38	256 qam	2
3	427000000	-6.9	38	256 qam	3
4	435000000	-7.2	38	256 qam	4
5	443000000	-7.5	38	256 qam	5
6	451000000	-7.5	38	256 qam	6
7	459000000	-7.5	38	256 qam	7
8	467000000	-7.5	38	256 qam	8
9	475000000	-7.7	38	256 qam	9
10	483000000	-7.7	38	256 qam	10
11	491000000	-7.9	38	256 qam	11
12	499000000	-8.2	38	256 qam	12
13	507000000	-8.2	38	256 qam	13
14	515000000	-8.4	38	256 qam	14
15	523000000	-8.5	37	256 qam	15
16	531000000	-8.7	37	256 qam	16
17	539000000	-9	37	256 qam	17
18	547000000	-9.2	37	256 qam	18
19	555000000	-9.4	37	256 qam	19
20	563000000	-9.5	37	256 qam	20
21	571000000	-9.9	37	256 qam	21
22	579000000	-10	37	256 qam	22
23	587000000	-10	37	256 qam	23
24	595000000	-10	37	256 qam	24

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	38.9	155	0
2	Locked	38.9	94	0
3	Locked	38.9	170	0
4	Locked	38.9	75	0
5	Locked	38.9	131	0
6	Locked	38.9	113	0
7	Locked	38.6	168	0
8	Locked	38.6	90	0
9	Locked	38.9	103	0
10	Locked	38.6	110	0
11	Locked	38.9	123	0
12	Locked	38.9	134	0
13	Locked	38.6	155	0
14	Locked	38.9	101	0
15	Locked	37.6	222	0
16	Locked	37.6	144	0
17	Locked	37.3	216	0
18	Locked	37.6	275	0
19	Locked	37.6	166	0
20	Locked	37.6	367	0
21	Locked	37.6	775	0
22	Locked	37.6	511	0
23	Locked	37.6	512	0
24	Locked	37.6	469	0

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	49600249	49.3	5120	64 qam	1
2	36600025	48.5	5120	64 qam	3
3	30100157	48	5120	64 qam	4
4	43100239	48.8	5120	64 qam	2
5	23599902	47.7	5120	16 qam	5

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	2	0
2	ATDMA	0	0	1	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	2	0
5	ATDMA	0	0	0	0

[Icantcrabhere]

https://www.thinkbroadband.com/broadband/monitoring/quality/share/99d0211a42b0af7eea816fe43594835dbd...

Link to my live BQM where the packet loss is visible on 30th September, just before and after 7PM.

Hoping this is just a power level/SNR issue and that the whole repull wasn't a waste of time.

[Icantcrabhere]

Okay, T3's are climbing on Channel 5

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	2	0
2	ATDMA	0	0	1	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	2	0
5	ATDMA	0	0	7	0

SNR issue inc!

[Comradebo]

When I had this issue about 18 months ago, it was a problem that was at the head end that no one was monitoring.  After multiple engineers, a repull etc it was some dodgy fibre cable.  Took 2 months to fix and now I have different issues. Anyone in your area you can do a BQM on?

[Megan_L]

Hi Icantcrabhere, 

Thanks for your post, I am sorry you're having this issue with your broadband services recently, thank you for taking the time to post your logs.

I have had a look at your services on my side and can see there is an area outage, which is regarding an SNR issue. 

This is due to be fixed  - 04 OCT 2022 09:00 - but please be aware this is just an estimate, it could change depending on what the engineers find. However, I am sure they will be working incredibly hard to get this fixed as soon as possible for you.

Thanks, 

Megan_L

[Icantcrabhere]

@Comradebro
Luckily this time it seems to be an SNR issue,

however sadly no, I don't have anyone else locally who has a BQM, or who is willing to discuss their levels etc.
I tried before with other locals in a FB group, but I don't think they were comfy with the idea.
and most of our neighbours are with different providers.

Thankfully a new FTTP provider is in town, so there's one positive through all this mess 🙂

and thank you for the update, Megan!

[Icantcrabhere]

Well this is neat.

Logs taken after a fresh restart.

Channels dropping from 64QAM again.
Nothing in the Modem log worth posting, except from previous T3's.

And yes my power levels are completely wrong, just like before and they didn't get anyone out to fix them 🙂

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	49600233	49.3	5120	64 qam	1
2	43100254	49	5120	64 qam	2
3	36600000	49.7	5120	16 qam	3
4	30100171	48	5120	32 qam	4
5	23599814	47.5	5120	16 qam	5

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	0	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0
5	ATDMA	0	0	0	0

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	411000000	-6.4	38	256 qam	1
2	419000000	-6.5	38	256 qam	2
3	427000000	-6.7	38	256 qam	3
4	435000000	-7.2	38	256 qam	4
5	443000000	-7.5	38	256 qam	5
6	451000000	-7.5	38	256 qam	6
7	459000000	-7.4	38	256 qam	7
8	467000000	-7.5	38	256 qam	8
9	475000000	-7.5	38	256 qam	9
10	483000000	-7.7	38	256 qam	10
11	491000000	-7.7	38	256 qam	11
12	499000000	-8.2	38	256 qam	12
13	507000000	-8.2	38	256 qam	13
14	515000000	-8.2	38	256 qam	14
15	523000000	-8.5	37	256 qam	15
16	531000000	-8.7	37	256 qam	16
17	539000000	-8.9	37	256 qam	17
18	547000000	-9.2	37	256 qam	18
19	555000000	-9.4	37	256 qam	19
20	563000000	-9.5	37	256 qam	20
21	571000000	-9.7	37	256 qam	21
22	579000000	-10	37	256 qam	22
23	587000000	-10	37	256 qam	23
24	595000000	-9.9	37	256 qam	24

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	38.9	0	0
2	Locked	38.9	4	0
3	Locked	38.9	5	0
4	Locked	38.9	0	0
5	Locked	38.6	5	0
6	Locked	38.9	5	0
7	Locked	38.6	5	0
8	Locked	38.9	6	0
9	Locked	38.9	5	0
10	Locked	38.6	6	0
11	Locked	38.6	5	0
12	Locked	38.6	0	0
13	Locked	38.6	0	0
14	Locked	38.6	7	0
15	Locked	37.6	5	0
16	Locked	37.3	5	0
17	Locked	37.3	12	0
18	Locked	37.6	0	0
19	Locked	37.6	5	0
20	Locked	37.3	6	0
21	Locked	37.3	5	0
22	Locked	37.3	5	0
23	Locked	37.6	0	0
24	Locked	37.6	5	0

Also according to the fault checker:
"Looks like there’s an intermittent signal issue in your areaTo make sure it's not the kit in your home that's causing the issue, follow our steps to check your cables. And don’t worry, if you need a technician we can set that up from here."


take that as you will.

.
Feels like I'm liviing in a cursed area right now:

Countless technicians,
A repull,
loads of SNR issues.

What an absolute headache

[Comradebo]

Are you running a Hub5 or 4? Any Attenuators on the line? I was told that only wideband ones work on the 4 and 5 otherwise they cause issues. Also what is your slope like? I have been having a similar issue and its driving me nuts with pulls (they put a RG11 thicker cable in as it is on the cusp of distance) and engineers etc. My slope isnt flat and it has hump in the middle.

I feel your pain, the headache is real!

[Icantcrabhere]

Hey there, Comeradebo!
Running a Hub3 🙂

If i were to take the attenuators off my power levels would actually be higher, scary right?

In regards to slope, It's actually low powered the closer we get to the cabinet (Or was before the repull, at least).
Unfortunately I wasn't here the day of the repull, so I have no idea which cable they actually replaced it with.

Sadly for the most part it has been generic responses from technicans, etc - i'm assuming it has been the same for you.
It's definitely an odd situation, sorry to hear you're having to deal with it too!

If VM were to compensate me for all these issues? - it still wouldn't cover the price of the paracetamol i've used 🙂
Hopefully we can get our issues resolved, fellow headache brother!

[jbrennand]

Your Down powers are all too low - so removing any attenuator would increase the - perhaps to back in range - worth a try and see what happens.

But if you are being informed that there is a "known intermittent signal issue" then that needs to be cleared before any tech visit could happen

Is it being reported on the local status line - 0800 561 0061 ?