DrayTek UK Users' Community Forum
Help, Advice and Solutions from DrayTek Users
2862 CRC/ES/SES Errors on BT VDSL2 Line
- iceman
- Topic Author
- User
-
- edinburgh
- Offline
- Member
-
05 Feb 2022 17:20 #8
by edinburgh
Replied by edinburgh on topic Re: 2862 CRC/ES/SES Errors on BT VDSL2 Line
So, they say if you're connected to a Broadcom cabinet, which you are (and, incidentally, I am, too), then there may be combability issues with Infineon (now Lantiq) based routers, which Draytek is. I don't know if that is. I just think Draytek routers are bad on poor lines, although not sure if this applies to you, too. However, it looks like the same pattern of disconnections and behaviour as I have had: nothing, then flurry, disconnection. Our ADSL connection was a bit noisy, too, but my previous Drayteks handled it perfectly. My VDSL 2762 now sits in its cardboard box. You could try MDM3 firmware (77C717 Modem Code), as it's most conservative. See my and Hornbyp's discussion on firmwares on here, too.
Which version of BT Hub do you have? Some are made with Broadcom chipsets (Type A) others with Infineon (Type B). If yours is the former, then this might explain why you're getting a better sync without disconnections. However, my Fritz has Infineon, too, and seems to be ok, so maybe it's all down to DSL coding. I simply don't know. If you have Type A Hub, but don't like it, and if you're unable to find the cause of your problems, then you might want to find something else Broadcom based to try out. Here's a list of other routers organised by chipset types:https://forum.kitz.co.uk/index.php/topic,14436.0.html
My pattern of disconnections was at 12:57am every night. We also had more of them in the evening, to the point where I was unable to teach my evening class preparing students for national exams. Openreach blamed the router right from the start, but Plusnet Hub had a similar pattern (also Infineon chipset). Evening disconnections could also be due to noise or congestion, especially if most go with BT or Plusnet or John Lewis broadband packages, leading to oversubscription.
Plusnet sent us a Zyxel 8924, which is Broadcom based and which seemingly is very good with Huawei cabinets and also on poor lines if you go with advice on the Kitz forum, but I didn't like the looks of it - it looks like a shiny tile - and the interface as well as a lack of updates defo put me off using it:shock: 
Because of their inability to identify the cause, Plusnet capped our connection at 50/10 and said several times that we could leave without penalty, as I presume, they've now had enough of my complaints. Andrews and Arnold are always happy to take on connections that are problematic, but because they have a metred broadband, we can't go with them.
Which version of BT Hub do you have? Some are made with Broadcom chipsets (Type A) others with Infineon (Type B). If yours is the former, then this might explain why you're getting a better sync without disconnections. However, my Fritz has Infineon, too, and seems to be ok, so maybe it's all down to DSL coding. I simply don't know. If you have Type A Hub, but don't like it, and if you're unable to find the cause of your problems, then you might want to find something else Broadcom based to try out. Here's a list of other routers organised by chipset types:
My pattern of disconnections was at 12:57am every night. We also had more of them in the evening, to the point where I was unable to teach my evening class preparing students for national exams. Openreach blamed the router right from the start, but Plusnet Hub had a similar pattern (also Infineon chipset). Evening disconnections could also be due to noise or congestion, especially if most go with BT or Plusnet or John Lewis broadband packages, leading to oversubscription.
Plusnet sent us a Zyxel 8924, which is Broadcom based and which seemingly is very good with Huawei cabinets and also on poor lines if you go with advice on the Kitz forum, but I didn't like the looks of it - it looks like a shiny tile - and the interface as well as a lack of updates defo put me off using it
Because of their inability to identify the cause, Plusnet capped our connection at 50/10 and said several times that we could leave without penalty, as I presume, they've now had enough of my complaints. Andrews and Arnold are always happy to take on connections that are problematic, but because they have a metred broadband, we can't go with them.
Please Log in or Create an account to join the conversation.
- piste basher
- Offline
- New Member
-
- iceman
- Topic Author
- User
-
06 Feb 2022 11:54 #10
by iceman
Replied by iceman on topic Re: 2862 CRC/ES/SES Errors on BT VDSL2 Line
Thanks for the feedback and suggestions.
I have already tried the MDM3 variant and that seemed ok for about 3 days before the line synch was lost the first time then it lost synch again within 24 hours.
I'll take a look at the discussion regarding the chipsets, I have a BT Smart Hub 2 which is the one holding synch.
I hadn't really thought about the obvious option of plugging the BT hub into WAN2 - I was too focussed on looking at the Draytek. I was assuming that it was not possible to connect the Draytek to the BT hub since I'd read in various places that it needed to be in bridge mode which was only available on BT business hubs. Oh, I just realised configuration will be needed on the BT hub to allow VoIP traffic through. I've seen the various posts about connecting the Draytek to BT Hub so I will give that a whirl after a few days of calm to avoid being further banded down.
Other things I've seen around suggest possibly resetting to factory and reconfiguring manually (not reloading the saved configuration files) - what do you think of that? Some people report successfully getting a stable router - I'm tempted since it costs nothing to do it, just the time to sit down record and reenter the setup.
Thanks again everyone!
Cheers!
Andy
I have already tried the MDM3 variant and that seemed ok for about 3 days before the line synch was lost the first time then it lost synch again within 24 hours.
I'll take a look at the discussion regarding the chipsets, I have a BT Smart Hub 2 which is the one holding synch.
I hadn't really thought about the obvious option of plugging the BT hub into WAN2 - I was too focussed on looking at the Draytek. I was assuming that it was not possible to connect the Draytek to the BT hub since I'd read in various places that it needed to be in bridge mode which was only available on BT business hubs. Oh, I just realised configuration will be needed on the BT hub to allow VoIP traffic through. I've seen the various posts about connecting the Draytek to BT Hub so I will give that a whirl after a few days of calm to avoid being further banded down.
Other things I've seen around suggest possibly resetting to factory and reconfiguring manually (not reloading the saved configuration files) - what do you think of that? Some people report successfully getting a stable router - I'm tempted since it costs nothing to do it, just the time to sit down record and reenter the setup.
Thanks again everyone!
Cheers!
Andy
Please Log in or Create an account to join the conversation.
- edinburgh
- Offline
- Member
-
- iceman
- Topic Author
- User
-
07 Feb 2022 16:59 #12
by iceman
Replied by iceman on topic Re: 2862 CRC/ES/SES Errors on BT VDSL2 Line
Got it - thanks for the feedback and information.
I've now got the BT Hub hooked up to WAN2 and all seems ok.
I've been looking around to see if I've made an obvious mistake in setup, but the only thing I've noticed is that in the Modem Code selection dropdown I have the options of Default, AnnexA_779517_773F01 and AnnexA_77B507_775401.
In the release notes for 3.9.6.2 it suggests that these are the modem codes for the BT and the MDM2 variant (well, almost... release notes shows 77B506 for MDM2 not 77B507 - maybe slightly different or a typo in the release notes).
I think I saw a similar question asked about the two modem code variants and I wondered if it is always the case that there are two variants in each MDM release type. I suppose I could just load up MDM2 and MDM3 and see what happens, but I thought I'd ask first
Cheers!
Andy
I've now got the BT Hub hooked up to WAN2 and all seems ok.
I've been looking around to see if I've made an obvious mistake in setup, but the only thing I've noticed is that in the Modem Code selection dropdown I have the options of Default, AnnexA_779517_773F01 and AnnexA_77B507_775401.
In the release notes for 3.9.6.2 it suggests that these are the modem codes for the BT and the MDM2 variant (well, almost... release notes shows 77B506 for MDM2 not 77B507 - maybe slightly different or a typo in the release notes).
I think I saw a similar question asked about the two modem code variants and I wondered if it is always the case that there are two variants in each MDM release type. I suppose I could just load up MDM2 and MDM3 and see what happens, but I thought I'd ask first
Cheers!
Andy
Please Log in or Create an account to join the conversation.