cancel
Showing results for 
Search instead for 
Did you mean: 

lag on streaming

kawsar11499
Joining in

my streaming services like iplayer and nowtv live sports lags every now and then, here is my broadband quality monitor 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/4ee616a5c83e3ded75665afd27be08a57e...

 

1 ACCEPTED SOLUTION

Accepted Solutions

Ethernet won't improve the very erratic latency visible on the BQM, since that's caused by a poor broadband connection.

Connect to the hub by clicking on this link http://192.168.0.1/  That should pull up the log in page for the hub.  But don't log in, just click on the link "Check router status"  That'll bring up a window with five tabs.  Open the Downstream tab.  Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots.  Post that, do the same for the Upstream and Network log.  You'll get an error message when you post the Network log, just click on "post" a second time.

Then we can check for any obvious problems with power, noise or error counts.

See where this Helpful Answer was posted

16 REPLIES 16

legacy1
Alessandro Volta
Are you streaming by wire or wireless?

---------------------------------------------------------------

By wifi

Try it with an ethernet connection. 

- jpeg1
My name is NOT Alessandro. That's just a tag Virginmedia sticks on some contributors. Please ignore it.

My tv is in a different room than my hub

Ethernet won't improve the very erratic latency visible on the BQM, since that's caused by a poor broadband connection.

Connect to the hub by clicking on this link http://192.168.0.1/  That should pull up the log in page for the hub.  But don't log in, just click on the link "Check router status"  That'll bring up a window with five tabs.  Open the Downstream tab.  Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots.  Post that, do the same for the Upstream and Network log.  You'll get an error message when you post the Network log, just click on "post" a second time.

Then we can check for any obvious problems with power, noise or error counts.

3.0 Downstream channels

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

253307500001.70000140.366287QAM25625
11387500003.00000038.983261QAM2561
21467500002.90000238.983261QAM2562
31547500002.59999838.605377QAM2563
41627500002.00000038.983261QAM2564
51707500001.59999838.983261QAM2565
61787500001.20000138.983261QAM2566
71867500001.09999838.605377QAM2567
81947500001.40000238.983261QAM2568
92027500001.50000038.983261QAM2569
102107500001.09999838.983261QAM25610
112187500001.00000040.366287QAM25611
122267500001.20000138.983261QAM25612
132347500000.90000238.983261QAM25613
142427500000.70000138.983261QAM25614
152507500000.90000240.366287QAM25615
162587500000.50000038.983261QAM25616
172667500000.09999838.983261QAM25617
182747500001.09999838.983261QAM25618
192827500001.50000040.366287QAM25619
202907500001.59999840.366287QAM25620
212987500002.00000038.983261QAM25621
223067500002.29999940.366287QAM25622
233147500001.79999938.983261QAM25623
243227500001.79999940.366287QAM25624
263387500001.70000140.366287QAM25626
273467500001.79999940.946209QAM25627
283547500001.79999940.366287QAM25628
293627500001.70000140.366287QAM25629
303707500001.50000040.366287QAM25630
313787500001.00000038.983261QAM25631



3.0 Downstream channels

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

25Locked40.36628700
1Locked38.98326100
2Locked38.98326100
3Locked38.60537700
4Locked38.98326100
5Locked38.98326100
6Locked38.98326100
7Locked38.60537700
8Locked38.98326100
9Locked38.98326100
10Locked38.98326100
11Locked40.36628700
12Locked38.98326100
13Locked38.98326100
14Locked38.98326100
15Locked40.36628700
16Locked38.98326100
17Locked38.98326100
18Locked38.98326100
19Locked40.36628700
20Locked40.36628700
21Locked38.98326100
22Locked40.36628700
23Locked38.98326100
24Locked40.36628700
26Locked40.36628700
27Locked40.94620900
28Locked40.36628700
29Locked40.36628700
30Locked40.36628700
31Locked38.98326100



3.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33944K1840QAM4096424


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
33Locked42-0.18134214722

3.0 Upstream channels

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

13260000047.0205995120 KSym/sec64QAM7
24620000047.0205995120 KSym/sec64QAM5
33940000047.0205995120 KSym/sec64QAM6
42580000046.7705995120 KSym/sec64QAM8



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0010
2US_TYPE_STDMA0000
3US_TYPE_STDMA0060
4US_TYPE_STDMA0000

Network Log

Time Priority Description

Thu Jan 1 00:01:20 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 17 12:30:16 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 17 12:33:22 20216SW Download INIT - Via Config file cmreg-vmdg640-bbt057+voc-b.cm
Tue Aug 17 12:34:48 20216SW download Successful - Via Config file
Tue Aug 17 12:37:46 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 17 13:03:35 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Aug 19 09:46:04 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 21 02:01:51 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 27 05:44:31 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 28 02:01:51 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 28 06:56:08 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 31 14:01:51 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 1 01:22:23 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Sep 4 02:01:51 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:20 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Sep 4 23:32:18 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 5 02:21:19 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 8 00:47:03 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:21 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 8 13:14:52 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Sep 11 14:08:20 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Sep 11 15:59:36 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 15 01:57:41 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 17 15:07:13 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Sep 18 13:57:41 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Unfortunately there's nothing I can see in the status data to indicate a problem, although BQM continues to show there is one.  My best guess is noise ingress on downstream channels, but I can't be certain because thanks to poor quality firmware the Hub 4 shows downstream error counts of zero which is incorrect: All DOCSIS connections have some errors, usually the insignificant pre-RS type, but my suspicion is yours may have an excess of the serious post-RS errors.  All you can do is wait for the staff to pick this up and advise - they may be able to interrogate the hub remotely and see a correct error count.