ContributionsMost RecentMost LikesSolutionsRe: intermittent signal EH15 Thanks, that's all useful pointers, we're in a coastal area and been told anecdotally that local connections suffering from corrosion. Grateful if VM Mods/tech could get in touch when possible. Re: intermittent signal EH15 Let me know what else you need - please be specific and describe in plain english as this is the first time I have actully logged into the back end of the hub. Re: intermittent signal EH15 Router status Status Downstream Upstream Configuration Refresh data Upstream bonded channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 1 43100000 40.5 5120 64 qam 2 2 23600000 42 5120 64 qam 5 3 30100000 40.5 5120 64 qam 4 4 36600000 40.5 5120 64 qam 3 5 49600000 40.5 5120 64 qam 1 Upstream bonded channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 1 ATDMA 0 0 29 0 2 ATDMA 0 0 3 0 3 ATDMA 0 0 0 0 4 ATDMA 0 0 0 0 5 ATDMA 0 0 2 0 Downstream bonded channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 331000000 7.4 40 256 qam 25 2 203000000 8.5 43 256 qam 9 3 211000000 8.5 40 256 qam 10 4 219000000 8.1 40 256 qam 11 5 227000000 7.6 40 256 qam 12 6 235000000 7.5 40 256 qam 13 7 243000000 7.3 40 256 qam 14 8 251000000 7 40 256 qam 15 9 259000000 7 40 256 qam 16 10 267000000 7.8 40 256 qam 17 11 275000000 7.9 40 256 qam 18 12 283000000 7.6 40 256 qam 19 13 291000000 7.5 40 256 qam 20 14 299000000 7.9 40 256 qam 21 15 307000000 7.6 40 256 qam 22 16 315000000 7.4 40 256 qam 23 17 323000000 7.5 40 256 qam 24 18 339000000 7.4 40 256 qam 26 19 347000000 7.4 40 256 qam 27 20 355000000 7 40 256 qam 28 21 363000000 6.5 40 256 qam 29 22 371000000 6 40 256 qam 30 23 379000000 4.6 38 256 qam 31 24 387000000 5.5 40 256 qam 32 Downstream bonded channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 40.3 95 261 2 Locked 43.3 85 492 3 Locked 40.9 81 446 4 Locked 40.9 42 873 5 Locked 40.9 131 879 6 Locked 40.3 103 758 7 Locked 40.3 120 921 8 Locked 40.3 61 1080 9 Locked 40.9 42 951 10 Locked 40.9 47 1066 11 Locked 40.9 52 1086 12 Locked 40.9 70 1254 13 Locked 40.9 45 1349 14 Locked 40.3 97 1269 15 Locked 40.9 43 1194 16 Locked 40.9 80 1335 17 Locked 40.9 127 1528 18 Locked 40.9 89 1424 19 Locked 40.3 222 1381 20 Locked 40.3 70 1250 21 Locked 40.9 193 1472 22 Locked 40.3 99 1483 23 Locked 38.9 479 1587 24 Locked 40.9 79 177 Re: intermittent signal EH15 Hi, thanks for the response, I set up a BQM yesterday and it can accessed at https://www.thinkbroadband.com/broadband/monitoring/quality/share/a562c7629ea23e2a36a7c56ccf5766b813e75428-16-01-2024 SamKnows test says Network Log Network Log Time Priority Description 16/01/2024 18:06:28 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 16/01/2024 12:40:27 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 15/01/2024 22:14:19 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 15/01/2024 22:14:19 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 14/01/2024 06:27:41 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 12/01/2024 10:14:18 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 12/01/2024 10:14:18 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 10/01/2024 14:04:32 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 03:12:35 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 03:12:30 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 03:01:14 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 03:01:8 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 01:22:16 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 01:22:15 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 01:21:2 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 01:00:49 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 01:00:1 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 00:59:57 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 00:59:56 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/01/2024 00:59:56 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; intermittent signal EH15 Hi, having issues with frequent signal drop outs, affecting both laptops and phones, and causing our work VPNs to drop out and video calls to freeze. When I look at service status for our postcode it shows green - but when I go in and test the hub it says there are intermittent signal issues in our area, This has gone on for months. We're a couple of hundred metres from the cabinet. Please could someone advise whetherer there are plans to resolve this, as it seems to be a known issue? We've done frequent hub resets and it hasn't helped. Solved