Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 ... 3 4 [5] 6 7 8

Author Topic: Now up, but speed for now not what hoped for  (Read 21174 times)

NewtronStar

  • Kitizen
  • ****
  • Posts: 4898
Re: Now up, but speed for now not what hoped for
« Reply #60 on: May 03, 2018, 11:22:42 PM »

I've left the Billion router on while away. Before going the FECs were quite low, but yesterday's (no activity by me, DSLStats recorded  @ 14749443/hour, and today @ 49319738/hour.

Suspect that will be down to XdB being active the lower the SNRM decreases from target margin of 6dB those FEC counts will increase dramatically.
Logged

renluop

  • Kitizen
  • ****
  • Posts: 3326
Re: Now up, but speed for now not what hoped for
« Reply #61 on: May 04, 2018, 08:54:33 AM »

History of readings a little before midnight
Code: [Select]
Average error rates by day

03 May 2018
CRC errors per hour: 0 Down, 0.84 Up
FEC errors per hour: 49409271 Down, 1.81 Up
HEC errors per hour: 0 Down, 0 Up
ES per hour: 0 Down, 0.76 Up
SES per hour: 0.25 Down, 0 Up

02 May 2018
CRC errors per hour: 29.4 Down, 1.13 Up
FEC errors per hour: 14749443 Down, 2.17 Up
HEC errors per hour: 0 Down, 0 Up
ES per hour: 0.83 Down, 1.13 Up
SES per hour: 0.42 Down, 0 Up

01 May 2018
CRC errors per hour: 0 Down, 0.75 Up
FEC errors per hour: 2637 Down, 2.72 Up
HEC errors per hour: 0 Down, 0 Up
ES per hour: 0 Down, 0.75 Up
SES per hour: 0 Down, 0 Up

30 Apr 2018
CRC errors per hour: 0.09 Down, 0.88 Up
FEC errors per hour: 584 Down, 1.67 Up
HEC errors per hour: 0 Down, 0 Up
ES per hour: 0.04 Down, 0.88 Up
SES per hour: 0 Down, 0 Up

29 Apr 2018
CRC errors per hour: 0.06 Down, 0.76 Up
FEC errors per hour: 3169 Down, 3.38 Up
HEC errors per hour: 0 Down, 0 Up
ES per hour: 0.06 Down, 0.76 Up
SES per hour: 0 Down, 0 Up

28 Apr 2018
CRC errors per hour: 0 Down, 0.82 Up
FEC errors per hour: 309 Down, 4.32 Up
HEC errors per hour: 0 Down, 0 Up
ES per hour: 0 Down, 0.73 Up
SES per hour: 0 Down, 0 Up

27 Apr 2018
CRC errors per hour: 22.4 Down, 0.92 Up
FEC errors per hour: 1437 Down, 1.13 Up
HEC errors per hour: 0 Down, 0 Up
ES per hour: 0.42 Down, 0.92 Up
SES per hour: 0 Down, 0 Up

26 Apr 2018
CRC errors per hour: 0.13 Down, 1.23 Up
FEC errors per hour: 391 Down, 1.65 Up
HEC errors per hour: 0 Down, 0 Up
ES per hour: 0.13 Down, 1.19 Up
SES per hour: 0 Down, 0 Up

25 Apr 2018
CRC errors per hour: 74.9 Down, 1.34 Up
FEC errors per hour: 2244 Down, 5.20 Up
HEC errors per hour: 0.04 Down, 0 Up
ES per hour: 1.05 Down, 1.13 Up
SES per hour: 0.59 Down, 0 Up

24 Apr 2018
CRC errors per hour: 19.4 Down, 0.42 Up
FEC errors per hour: 4515 Down, 1.22 Up
HEC errors per hour: 484 Down, 0 Up
ES per hour: 1.37 Down, 0.38 Up
SES per hour: 0.71 Down, 0 Up

23 Apr 2018
CRC errors per hour: 103 Down, 4.18 Up
FEC errors per hour: 767 Down, 0.16 Up
HEC errors per hour: 249 Down, 8.29 Up
ES per hour: 41.1 Down, 4.50 Up
SES per hour: 8.68 Down, 0 Up

I'm not disputing what you say, but doesn't the sudden 559300% jump from 1-2 May even so seem excessive? And there's the 300+% lift since. Is the %age increase I am seeing common?
Logged

NewtronStar

  • Kitizen
  • ****
  • Posts: 4898
Re: Now up, but speed for now not what hoped for
« Reply #62 on: May 04, 2018, 11:27:39 AM »

It is a big jump when seeing it like that, are you going take up the offer for a engineer visit
Logged

renluop

  • Kitizen
  • ****
  • Posts: 3326
Re: Now up, but speed for now not what hoped for
« Reply #63 on: May 04, 2018, 03:04:47 PM »

We'll probably with less trepidation than before B'cat's reply.

From May 03, 2018, 06:26:36 PM
Quote
Does anyone know what Sagemcom the HubOne is based on, and if DSLStats will yield any stats at all, should I need change to it
Is anyone able to answer, please?
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 4103
Re: Now up, but speed for now not what hoped for
« Reply #64 on: May 04, 2018, 04:15:42 PM »

The Plusnet Hub One will not work at all with DslStats.

It will provide the same basic stats via its web interface as the BT HomeHub 5A does.
Logged
Talktalk FTTP 550/75 - Speedtest - BQM

renluop

  • Kitizen
  • ****
  • Posts: 3326
Re: Now up, but speed for now not what hoped for
« Reply #65 on: May 04, 2018, 05:06:04 PM »

I thought that was so, but had vague idea that Lantiq chipsets did sometimes work limitedly. Where from goodness knows! I wonder if I can persuade Lowen's Routerstats to yield SNRM live activity.
Logged

Browni

  • Reg Member
  • ***
  • Posts: 137
Re: Now up, but speed for now not what hoped for
« Reply #66 on: May 04, 2018, 05:48:14 PM »

There's basic monitoring of a Plusnet Hub One available on RouterStatsHub.

renluop

  • Kitizen
  • ****
  • Posts: 3326
Re: Now up, but speed for now not what hoped for
« Reply #67 on: May 05, 2018, 08:09:02 AM »

Thank you! :)
I've managed the set up. For anyone interested here's the summary.
Code: [Select]






1. Product name:Plusnet Hub
2. Serial number
3. Firmware version:Software version 4.7.5.1.83.8.237.2.2 Last updated Unknown
4. Board version:Plusnet Hub One
5. DSL uptime:0 days, 13:08:09
6. Data rate:5358 / 22144
7. Maximum data rate:5358 / 23453
8. Noise margin:5.9 / 4.0
9. Line attenuation:29.2 / 26.0
10. Signal attenuation:29.0 / 22.0
11. Data sent/received:61.9 MB / 635.5 MB
12. Broadband username: @plusdsl.net
13. 2.4 GHz Wireless network/SSID:PLUSNET-****
14. 2.4 GHz Wireless connections:Enabled (802.11 b/g/n (up to 144 Mb/s))
15. 2.4 GHz Wireless security:WPA2
16. 2.4 GHz Wireless channel:11
17. 5 GHz Wireless network/SSID:PLUSNET-****
18. 5 GHz Wireless connections:Enabled (802.11 a/n/ac (up to 1300 Mb/s))
19. 5 GHz Wireless security:WPA2
20. 5 GHz Wireless channel:Automatic (Smart Wireless)
21. Firewall:Default
22. MAC Address:*
23. Modulation:G.993.2 Annex B
24. Software variant:AA
25. Boot loader:1.0.0
Plusnet Hub One | Software version 4.7.5.1.83.8.237.2.2 | Last updated Unknown
Logged

renluop

  • Kitizen
  • ****
  • Posts: 3326
Re: Now up, but speed for now not what hoped for
« Reply #68 on: May 06, 2018, 08:29:30 PM »

Engineer is booked for Wednesday p.m. :fingers:
I have changed to PN's Hub One to be "standard and innocent".
Hub connects lower, and with a near 3dB increase in attenuation. I know about how the calculation can vary, but does such a variation seem normal?
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 4103
Re: Now up, but speed for now not what hoped for
« Reply #69 on: May 06, 2018, 09:14:58 PM »

Since the last set of stats you posted your target snrm has dropped from 4dB to 3dB.
You're now above the 24Mb minimum Plusnet quoted.
The Plusnet Hub One syncs just under 24Mb, so leave that in place.

Hopefully the engineer can increase your speeds a little. Keep us updated.
Logged
Talktalk FTTP 550/75 - Speedtest - BQM

GaryW

  • Member
  • **
  • Posts: 96
Re: Now up, but speed for now not what hoped for
« Reply #70 on: May 07, 2018, 09:02:46 AM »

Engineer is booked for Wednesday p.m. :fingers:
I have changed to PN's Hub One to be "standard and innocent".
Hub connects lower, and with a near 3dB increase in attenuation. I know about how the calculation can vary, but does such a variation seem normal?

I get similar behaviour with a HH5A versus Broadcom-based modems on my line.  Billion 8900AX reports 27.6 db attenuation, Zyxel VMG8924 reports 28.2 dB, and HH5a reports 32.6 db!  And this is reflected by sync speeds: Billion and Zyxel both hit the 15000 cap, but HH5a never gets much above 11000. 
Logged
EE 4G - Huawei B618s-22d - BT WHWF

renluop

  • Kitizen
  • ****
  • Posts: 3326
Re: Now up, but speed for now not what hoped for
« Reply #71 on: May 07, 2018, 10:39:43 AM »

@j0hn

Actually PN suggested test as perf below the lower estimate rather than handback
Logged

renluop

  • Kitizen
  • ****
  • Posts: 3326
Re: Now up, but speed for now not what hoped for
« Reply #72 on: May 07, 2018, 07:26:50 PM »

Mind wandering/ mulling time! :: The ADSL rate was very good for distance, thought to be a little less than 3 km. The stated length from PCP to me is a little over 1 km. House was built c.1970, as part of an estate and phone cables are DIG. Could horrible ali in the line from PCP to house be the cause of my misfortune, but not cause such trouble with ADSL? Would complete or part of that length be needed to give result as is?.
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Now up, but speed for now not what hoped for
« Reply #73 on: May 07, 2018, 10:15:08 PM »

Could horrible ali in the line from PCP to house be the cause of my misfortune, but not cause such trouble with ADSL? Would complete or part of that length be needed to give result as is?.

I can't see how the problem depends upon the xDSL type.
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

renluop

  • Kitizen
  • ****
  • Posts: 3326
Re: Now up, but speed for now not what hoped for
« Reply #74 on: May 07, 2018, 10:53:37 PM »

I got idea from https://community.plus.net/t5/Fibre-Broadband/Aluminium-Telephone-Line/td-p/1409961 where in the first of the posts OP seems to put his low speed vs estimate on ali. Are you saying that ali makes no difference whatever to sync speeds VDSL or ADSL?
Logged
Pages: 1 ... 3 4 [5] 6 7 8