Superhub 3 and asus ax86u issues

[kaz1402]

Hi, last week we put our superhub into modem mode and added an asus ax86u router. All worked well for a few days. Much improved connection. So fast. But now we seem to have issues. Speed is reduced again and yesterday we lost connection totally. I have rebooted the router. Im a bit of a novice and trying to do all this with lack of knowledge! My son has severe learning difficulties and i need a stable connection so he can watch his youtube videos. 

Is there anything i should be doing to make this work better. We seem to have gone back to the issues we had with our superhub regarding service. I have a think broadband monitor set up since we added the asus. I had one on the virgin router too but that went solid red once the new router was added. Funnily enough that started showing stats again the last few days, didnt think it would. I have disabled that one now.  

Any help would be gratefully received for someone who is clueless on how to sort this. Many thanks

[kaz1402]

Thank you. As soon as my son is in bed and i can take the wifi off i will try that

[kaz1402]

Have turned it off and switched back on. Do the pre rs errors need to be 0 too?     Downstream bonded channels

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

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

[sophist]

pre-rs aren't really a problem.. they indicate errors that the hub was able to correct.. it's the post-rs errors that you need to worry about.. which indicate errors that the hub was unable to correct.

[kaz1402]

Thank you for the explanation. I am a real novice at this! I will keep checking to see what they do and post back tomorrow for advice. Appreciate everyone's help. My son has no understanding if we have no wifi! 

[legacy1]

The hub being buggy that a given reboot to modem mode didn't going to plan so another reboot was needed.

[mus1991]

hi i was just wondering i keep getting post rs errors on some channels, what is the expected errors normally or should it not be doing any? and t3 time outs too that seems to happen. any advice on keeping these errors down?

[sophist]

---

@mus1991 wrote:

hi i was just wondering i keep getting post rs errors on some channels, what is the expected errors normally or should it not be doing any? and t3 time outs too that seems to happen. any advice on keeping these errors down?

---

It’s best to start your own thread with the detail of the problem and provide the information from the hub that was requested in this thread.

[kaz1402]

Ive checked this morning and they are still at 0 but the pre rs numbers have gone up. Last night the v6 box wouldnt connect to what we were watching on prime later on in the night. It does that most nights now. It was fine to start with. 

Do you need to see all stats again? We have always had issues with our connection despite many many calls to virgin. Connecting the asus worked amazingly for a few days only. Its still faster than before but maybe ive done something wrong?

The 5g connection seems to keep going off. My sons ipad was on it and then it kept asking for the password but telling me it was incorrect. I connected him to the 2.4 one fine. It doesnt automatically come up on the network list either. The v6 boxes are on the 2.4 one as the 5g one had a worse signal. 

[kaz1402]

These have appeared though 

Network Log

Time Priority Description

22/05/2021 12:26:34	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:26:33	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:22:46	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:22:45	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:22:32	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:22:32	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:21:31	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:21:31	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:20:1	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:19:57	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:19:33	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:19:32	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:19:5	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:19:5	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:18:46	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:18:45	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:18:27	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:18:26	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:18:11	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/05/2021 12:18:11	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[jbrennand]

BQM showing a clear disconnect around 10pm last night and 1.30pm today - did you switch off/reboot at those times?

Have you tried with the Asus disconnected for a period - although if no PostRs errors are appearing it may be irrelevant.