on 05-04-2022 13:38
Greetings,
I had my VM hub 3 router replaced by a hub 5 last week.
Since my hub 5 replacement I've started losing connection after about say 15 - 20 minutes of gaming 'F1 Mobile Racing' on my iPad via WIFI which results in me losing the game.
This didn't happen with the old hub 3 router.
Has anyone else hit this issue with the new hub 5 or does anyone have any advice how to solve it because I'm now plummeting down the in game league. The cable is screwed in nice and tight into back of new hub. I'm not sure what else to do.
Thanks
Nick
Answered! Go to Answer
on 12-04-2022 14:13
I've just tried gaming again from around 12.15pm and connection dropped mid game around 1pm. BQM below. I've no idea what to do now. Could it be a fault with the new hub 5? I wasn't dropping mid-game with my old hub 3.
on 14-04-2022 14:28
I am going to send you a private message to confirm some details.
Cheers,
Ryan.
on 20-04-2022 18:08
Hi Ryan,
It seems I didn't passed your verification check although I've just phoned Support and passed verification with same password. The support person (sounded offshore) told me to reset my hub 5 and then she kept me waiting for 10 minutes while she did her checks. Then she came back and told me she fixed it but I've no idea what she did. Anyway, I'll have a 45 minute online gaming session tomorrow lunch time and see if connection still hangs or not.
Regards
Nick
on 28-04-2022 14:40
The connection dropping off issue still persists unfortunately 😞
on 30-04-2022 16:12
Thanks for coming back to us @NickNotTheGreek.
I'm sorry that the issues haven't yet been resolved for you. The technician should be able to resolve these issues on their visit to you.
Please do let us know how the visit goes.
Regards,
Steven_L
on 17-05-2022 18:50
Hi Steven,
Technicians visited and has been helpful. Hub was replaced and power levels checked. Hoped that fixed it but just tried gaming now (after a bit of a break) and connection started dropping after around 45 minutes of gaming which is what was happening before so it seems the hub wasn't the issue. Unsure what to do now.
Nick
on 19-05-2022 18:53
Hi Nick,
Thanks for reaching back out, sorry to hear your gaming issue has returned, are you facing issues on other devices or just the iPad?
Regards
Paul.
on 26-05-2022 20:10
Hi Paul,
I only do online gaming on my ipad. It's an itunes app for IOS devices so I can't test it on my laptop which I don't have any games on.
I'm still getting this dropping out issue. No change at all.
I don't recall having this issue with my old hub 3 which was replaced by this hub 5 which itself has been replaced by another hub 5 but made no difference. I'm wondering if I can have my old hub 3 sent back to me to test if that fixes it?
I've pasted my downstream & upstream info. Does it look okay to you? The Pre and Post RS Errors look very high!
What do you think?
Thanks
Nick
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 1.8 | 39 | QAM 256 | 25 |
2 | 139000000 | 6.3 | 38 | QAM 256 | 1 |
3 | 147000000 | 6.1 | 38 | QAM 256 | 2 |
4 | 155000000 | 5.7 | 38 | QAM 256 | 3 |
5 | 163000000 | 5.4 | 38 | QAM 256 | 4 |
6 | 171000000 | 5.2 | 38 | QAM 256 | 5 |
7 | 179000000 | 5.3 | 38 | QAM 256 | 6 |
8 | 187000000 | 5.3 | 38 | QAM 256 | 7 |
9 | 195000000 | 5.4 | 38 | QAM 256 | 8 |
10 | 203000000 | 5.1 | 38 | QAM 256 | 9 |
11 | 211000000 | 4.8 | 38 | QAM 256 | 10 |
12 | 219000000 | 4.3 | 38 | QAM 256 | 11 |
13 | 227000000 | 3.9 | 38 | QAM 256 | 12 |
14 | 235000000 | 3.7 | 38 | QAM 256 | 13 |
15 | 243000000 | 3.6 | 38 | QAM 256 | 14 |
16 | 251000000 | 3.4 | 38 | QAM 256 | 15 |
17 | 259000000 | 3.2 | 38 | QAM 256 | 16 |
18 | 267000000 | 2.9 | 38 | QAM 256 | 17 |
19 | 275000000 | 2.7 | 38 | QAM 256 | 18 |
20 | 283000000 | 2.7 | 38 | QAM 256 | 19 |
21 | 291000000 | 2.7 | 38 | QAM 256 | 20 |
22 | 299000000 | 2.7 | 39 | QAM 256 | 21 |
23 | 307000000 | 2.7 | 39 | QAM 256 | 22 |
24 | 315000000 | 2.6 | 39 | QAM 256 | 23 |
25 | 323000000 | 2.2 | 39 | QAM 256 | 24 |
26 | 339000000 | 1.8 | 38 | QAM 256 | 26 |
27 | 347000000 | 1.7 | 39 | QAM 256 | 27 |
28 | 355000000 | 1.7 | 39 | QAM 256 | 28 |
29 | 363000000 | 1.6 | 39 | QAM 256 | 29 |
30 | 371000000 | 1.4 | 39 | QAM 256 | 30 |
31 | 379000000 | 1 | 39 | QAM 256 | 31 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 39 | 365 | 8212 |
2 | Locked | 38 | 0 | 0 |
3 | Locked | 38 | 5008 | 1880 |
4 | Locked | 38 | 51135 | 787 |
5 | Locked | 38 | 6200 | 11070 |
6 | Locked | 38 | 8993 | 257354 |
7 | Locked | 38 | 442 | 51403 |
8 | Locked | 38 | 1512 | 165083 |
9 | Locked | 38 | 1171 | 21400 |
10 | Locked | 38 | 2321 | 66627 |
11 | Locked | 38 | 1171 | 289 |
12 | Locked | 38 | 811 | 271 |
13 | Locked | 38 | 18554 | 10665 |
14 | Locked | 38 | 734 | 4238 |
15 | Locked | 38 | 708 | 4329 |
16 | Locked | 38 | 759 | 3468 |
17 | Locked | 38 | 719 | 3262 |
18 | Locked | 38 | 689 | 3297 |
19 | Locked | 38 | 578 | 4720 |
20 | Locked | 38 | 614 | 6034 |
21 | Locked | 38 | 538 | 3244 |
22 | Locked | 39 | 457 | 3086 |
23 | Locked | 39 | 361 | 2858 |
24 | Locked | 39 | 334 | 2672 |
25 | Locked | 39 | 304 | 3531 |
26 | Locked | 38 | 4046 | 4577 |
27 | Locked | 39 | 3436 | 7261 |
28 | Locked | 39 | 1040 | 8416 |
29 | Locked | 39 | 387 | 8346 |
30 | Locked | 39 | 3769 | 86225 |
31 | Locked | 39 | 3748 | 249883 |
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 48.5 | 5120 | QAM 64 | 2 |
2 | 46200000 | 48 | 5120 | QAM 64 | 3 |
3 | 39400000 | 47.5 | 5120 | QAM 64 | 4 |
4 | 32600000 | 47 | 5120 | QAM 64 | 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 |
on 26-05-2022 20:13
My Network Log looks like this.
Network Log
Time Priority Description
16-05-2022 07:03:21 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 19:38:08 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 19:03:20 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 18:55:44 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 10 11 12 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 18:55:37 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 10 11 12 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 18:55:36 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 18:03:20 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:44:35 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:44:27 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:44:11 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 10 11 12 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:43:55 | notice | CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:43:51 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 10 11 12 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:43:51 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:43:40 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:43:27 | notice | CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:43:26 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:43:09 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 10 11 12 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:42:48 | notice | CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:42:38 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 10 11 12 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:42:30 | notice | CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:42:21 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 10 11 12 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:42:21 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:42:08 | notice | CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:42:05 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:41:51 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 10 11 12 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:41:24 | notice | CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:41:16 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 10 11 12 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:40:48 | notice | CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:40:15 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 10 11 12 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:39:53 | notice | CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:39:39 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 10 11 12 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-05-2022 17:39:36 | notice | CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 29-05-2022 09:37
Hi @NickNotTheGreek,
Thank you for coming back to us about your ongoing connection issue. After running some internal checks on your power levels, I have to say that they are all within spec and look good on our end.
How has your connection been recently? Is this impacting more than one device at the moment?
Let us know how you're getting on and how we can help.
Thank you.