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 2 [3] 4

Author Topic: Billion 8800NL and G.INP  (Read 17553 times)

tommy45

  • Reg Member
  • ***
  • Posts: 605
Re: Billion 8800NL and G.INP
« Reply #30 on: March 18, 2015, 03:09:15 PM »

 when  i compared stats from what i had on Fast path there's a slight increase in attainable rates and a low FEC rate, other errors have been zero , latency is around the same as fast path on G.inp  It's certainly so far a hell of a lot better than the legacy interleave,delay and inp  combo used by DLM
Logged

Mark800

  • Just arrived
  • *
  • Posts: 8
Re: Billion 8800NL and G.INP
« Reply #31 on: March 18, 2015, 06:53:38 PM »

I notice someone on the Billion forum is reporting an increase in downstream connection rate from 54 to 59 Mbps with G.INP, and an increase in upstream connection rate from 16 Mbps to 19 Mbps.
Logged

WWWombat

  • Kitizen
  • ****
  • Posts: 1674
Re: Billion 8800NL and G.INP
« Reply #32 on: March 20, 2015, 08:59:25 AM »

also possible he was previously interleaved. not fast path.
If you see an improvement in sync speed, it seems more likely to have come from a reduction in the volume of FEC overhead, rather than *just* the turning off of interleaving.

I can see that Mark's line now shows a FEC overhead of 8 bytes out of 139 bytes - which is around 6%. I wonder what the FEC settings were before?

Definitely fast path, with ping of 7 ms.

The new interleaving settings are for a depth of 16 and a width of 139 - so the overall volume is only 2,200. In  the old days (INP=3 and delay=8ms), the interleaving setup could be depth=1463 and width=64, so the volume would be 95,000. It is the volume of interleaving that corresponds to the delay of 8ms; having a volume 43x smaller makes for a delay of only 0.2ms - quite hard to measure.
Logged

vic0239

  • Reg Member
  • ***
  • Posts: 436
Re: Billion 8800NL and G.INP
« Reply #33 on: March 24, 2015, 07:40:18 AM »

I had my first resync post G.INP last night at around 02:48. Since G.INP was enabled I had noticed that my SNRM and attainable rate appeared to be behaving differently as before Iím sure they both rose/fell in sync, but lately they appeared to be going up and down independently and all over the place. At the weekend I took advantage of a higher attain rate and forced a resync to see what would happen and got a slightly higher sync rate. However the attain rate fell slightly and was sometimes below the actual sync rate. The FEC rate looked ok, some bursts, so I wonder what caused the DLM intervention? Iím using a Billion 8800NL at the moment (thanks to some Amazon vouchers from my bank) and wonder if there is a difference of opinion between it and the DLM given Billion are releasing a further firmware update?
Logged

WWWombat

  • Kitizen
  • ****
  • Posts: 1674
Re: Billion 8800NL and G.INP
« Reply #34 on: March 24, 2015, 04:19:45 PM »

I had my first resync post G.INP last night at around 02:48.

Judging from MDWS, you've had 4 new syncs since G.INP has become active, with slight alterations to the INP settings on 3 of them.

I suspect that the changes to the INP setting are making subtle internal adjustments to the speed vs SNRM calculation. I just don't know what yet, nor why the INP values have been changing.
Logged

vic0239

  • Reg Member
  • ***
  • Posts: 436
Re: Billion 8800NL and G.INP
« Reply #35 on: March 25, 2015, 09:29:13 AM »

Judging from MDWS, you've had 4 new syncs since G.INP has become active
Thanks for the reply. Mea culpa, can't stop plowtering with it! Interestingly this morning US SNRM has shot up, but DS has dropped.
Logged

Xup

  • Member
  • **
  • Posts: 32
Re: Billion 8800NL and G.INP
« Reply #36 on: March 25, 2015, 01:57:26 PM »

My Billion 8800nl in the last hour has gone to G.INP enabled,  down stream up from 44mb to 50, upstream 9.5 to 10mb, 800m to my cab.

 :)

The old and new.

21-03-2105

Mode VDSL2
Traffic Type PTM
Status Up
Link Power State L0
 
 Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 6.0 5.9
Attenuation (dB) 21.5 0.0
Output Power (dBm) 13.3 5.0
Attainable Rate (Kbps) 52907 9413
 
Rate (Kbps) 44750 9413
 
B (# of bytes in Mux Data Frame) 51 237
M (# of Mux Data Frames in an RS codeword) 1 1
T (# of Mux Data Frames in an OH sub-frame) 64 44
R (# of redundancy bytes in the RS codeword) 12 16
S (# of data symbols over which the RS code word spans) 0.0370 0.8035
L (# of bits transmitted in each data symbol) 13848 2529
D (interleaver depth) 875 1
I (interleaver block size in bytes) 64 127
N (RS codeword size) 64 254
Delay (msec) 8 0
INP (DMT symbol) 3.00 0.00
 
OH Frames 953526230 248960483
OH Frame Errors 76394 2890
RS Words 2746407341 3172874
RS Correctable Errors 2373268 329
RS Uncorrectable Errors 31670 0
 
HEC Errors 107875 0
OCD Errors 3 0
LCD Errors 3 0
Total Cells 1297079051 0
Data Cells 297755596 0
Bit Errors 0 0
 
Total ES 2400 2526
Total SES 211 0
Total UAS 423 390

--------------------------------------------------

G.INP 25-03-2015

Mode VDSL2
Traffic Type PTM
Status Up
Link Power State L0
 
 Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 6.2 5.8
Attenuation (dB) 21.6 0.0
Output Power (dBm) 13.1 5.6
Attainable Rate (Kbps) 50907 10158
 
Rate (Kbps) 50740 10158
 
B (# of bytes in Mux Data Frame) 243 227
M (# of Mux Data Frames in an RS codeword) 1 1
T (# of Mux Data Frames in an OH sub-frame) 0 0
R (# of redundancy bytes in the RS codeword) 10 14
S (# of data symbols over which the RS code word spans) 0.1531 0.7139
L (# of bits transmitted in each data symbol) 13270 2712
D (interleaver depth) 8 4
I (interleaver block size in bytes) 254 242
N (RS codeword size) 254 242
Delay (msec) 0 0
INP (DMT symbol) 46.00 42.00
 
OH Frames 0 0
OH Frame Errors 0 0
RS Words 12723976 2739945
RS Correctable Errors 65 0
RS Uncorrectable Errors 0 0
 
HEC Errors 0 0
OCD Errors 0 0
LCD Errors 0 0
Total Cells 47714640 0
Data Cells 179266 0
Bit Errors 0 0
 
Total ES 0 0
Total SES 0 0
Total UAS 0 0
« Last Edit: March 25, 2015, 02:03:41 PM by Xup »
Logged

WWWombat

  • Kitizen
  • ****
  • Posts: 1674
Re: Billion 8800NL and G.INP
« Reply #37 on: March 27, 2015, 12:06:01 PM »

My line was G.INP'd this morning - more details on that contained in this thread.

My Billion 8800NL coped well with this, even though I haven't updated the firmware since purchase. It is currently running 2.32d.dh14 and A2pv6F039g1.d24m

However, the "HG612 modem stats" program fails to harvest stats from the modem. DSLstats v5.3 does harvest data, but there's a slight hint that it isn't collecting CRC values correctly.
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: Billion 8800NL and G.INP
« Reply #38 on: March 27, 2015, 04:43:10 PM »

Just to confirm, the latest version of HG612 Modem Stats does now correctly harvest ongoing stats from Billion (& ZyXel modems).
This does include all the new G.INP raw stats & the various new graphs (quite a few new ones). 

I'm just awaiting a little more feedback from a couple of users before it is released for everyone.



Logged

WWWombat

  • Kitizen
  • ****
  • Posts: 1674
Re: Billion 8800NL and G.INP
« Reply #39 on: March 29, 2015, 01:14:04 PM »

It looks like it worked fine for me. Harvesting is running, and a full monty graph is available on the other thread. It is pretty boring though...
Logged

Xup

  • Member
  • **
  • Posts: 32
Re: Billion 8800NL and G.INP
« Reply #40 on: March 30, 2015, 03:57:28 PM »

G.INP been on my line now for 5 days, very happy with it.

Billion 8800NL First 5 full day stats with G.INP. 30-03-20015

Mode VDSL2
Traffic Type PTM
Status Up
Link Power State L0
 
 Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 6.1 5.6
Attenuation (dB) 21.6 0.0
Output Power (dBm) 13.1 5.6
Attainable Rate (Kbps) 50892 10155
 
Rate (Kbps) 50740 10158
 
B (# of bytes in Mux Data Frame) 243 227
M (# of Mux Data Frames in an RS codeword) 1 1
T (# of Mux Data Frames in an OH sub-frame) 0 0
R (# of redundancy bytes in the RS codeword) 10 14
S (# of data symbols over which the RS code word spans) 0.1531 0.7139
L (# of bits transmitted in each data symbol) 13270 2712
D (interleaver depth) 8 4
I (interleaver block size in bytes) 254 242
N (RS codeword size) 254 242
Delay (msec) 0 0
INP (DMT symbol) 46.00 42.00
 
OH Frames 0 0
OH Frame Errors 14 1
RS Words 2745698736 1724924
RS Correctable Errors 1685141 27177
RS Uncorrectable Errors 0 0
 
HEC Errors 0 0
OCD Errors 0 0
LCD Errors 0 0
Total Cells 3853386937 0
Data Cells 564739582 0
Bit Errors 0 0
 
Total ES 3 1
Total SES 0 0
Total UAS 0 0
Logged

vic0239

  • Reg Member
  • ***
  • Posts: 436
Re: Billion 8800NL and G.INP
« Reply #41 on: March 31, 2015, 04:57:08 PM »

Interesting stats this afternoon. During a brief power cut in the village when presumably all competing X talkers went down (I have a UPS) my DS SNRM shot up to 14.9 and the attainable speed up to ~82Mbps from ~60Mbps.  ;D It only lasted a few minutes however and returned to previous levels.  :( Roll on vectoring if this is what might be possible on my line! and fingers crossed the 8800NL actually will support it.

Corrected.
« Last Edit: March 31, 2015, 07:50:34 PM by vic0239 »
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 31617
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Billion 8800NL and G.INP
« Reply #42 on: March 31, 2015, 06:05:47 PM »

. . . the attainable speed up to ~82Kbps from ~60Kbps.

I suspect that those upper case Ks should really be Ms!  ;)
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.

vic0239

  • Reg Member
  • ***
  • Posts: 436
Re: Billion 8800NL and G.INP
« Reply #43 on: March 31, 2015, 06:48:50 PM »

. . . the attainable speed up to ~82Kbps from ~60Kbps.

I suspect that those upper case Ks should really be Ms!  ;)
Or I've missed out some zeros. ;)
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 31617
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Billion 8800NL and G.INP
« Reply #44 on: March 31, 2015, 08:14:21 PM »

. . . the attainable speed up to ~82Kbps from ~60Kbps.

I suspect that those upper case Ks should really be Ms!  ;)
Or I've missed out some zeros. ;)

Ah, ha!  ;D

The scientist within me feels that he should point out one other fact (and hopes that Vic will understand that I am just using his earlier posting as an example of a frequently occurring mishap). The upper case K refers to units on the Kelvin temperature scale whereas the lower case k is the kilo multiplier.
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.
Pages: 1 2 [3] 4