Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[NewtronStar]

Well Sheepie I should be moving to a new ISP in a fortnight what will happen is G.INP will be removed and put onto fastpath if my errored seconds go's above 2880 as it looks like Vodafone uses the DLM profile of Speed then I'll be Interleaved for the duration until G.INP becomes active again on my line.

That's the theory 

The reason for going to Fastpath first is because there are still a lot of modem/routers that don't support G.INP

[myriad]

So I haven't caught any noise on the line yet but doing phone calls does affect the error rates. At the moment my US Margin is at 5.8 so not sure if that is the core reason, but the screenshots show CRC errors as soon as the call is up, you can see I made 3 calls.

It's annoying but I doubt I have anything I can report to BT and have a hope they will fix yet though, I presume it is not normal to get errors during a phone call or have errors on the line in general when presumably before there were none, but since I don't see a drop or hear noise and my sync is OK I guess they won't care about that?

[myriad]

I cap my line, it greatly reduces my es, I stay on fastpath for ages now. Here's a useful link http://forum.kitz.co.uk/index.php/topic,16427.0.html

Thanks forceware, that is helpful. I found out that on the D6400 the command is: adslctl configure --maxDataRate, I presume it is the same for the D7000

So I have tried to drastically reduce to 30000 and 5500 to see if I can get fully stable. As a side note it seems the third number in the command should be the total of the up and downstream rather than the 100000 figure used in the sticky:

adslctl configure/configure1 [--maxDataRate <maxDsDataRateKbps maxUsDataRateKbps maxAggrDataRateKbps>]

[j0hn]

Thanks forceware, that is helpful. I found out that on the D6400 the command is: adslctl configure --maxDataRate, I presume it is the same for the D7000

So I have tried to drastically reduce to 30000 and 5500 to see if I can get fully stable. As a side note it seems the third number in the command should be the total of the up and downstream rather than the 100000 figure used in the sticky:

adslctl configure/configure1 [--maxDataRate <maxDsDataRateKbps maxUsDataRateKbps maxAggrDataRateKbps>]

it must be at least the upload + download, but can be left at 100,000 in all cases

[NewtronStar]

That is what I found when capping the HG612 you add both the DS sync and US sync to get third number IE 30000 + 5000 = 35000 if I used as the third number 100000 IE  --maxDataRate 30000 5000 100000 it would not cap the HG612

[myriad]

OK so 24 hrs later here is the comparison between running at a 6db SNR and capping bitrate so I'm at about 9-10db DS and 15db US:

Latest 1 day time = 23 hours 21 min 33 sec
FEC:            1016632         60
CRC:            296             34
ES:             76              33
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0

Previous 1 day time = 24 hours 0 sec
FEC:            2137267         2
CRC:            1464            298
ES:             214             284
SES:            3               0
UAS:            32              32
LOS:            0               0
LOF:            0               0
LOM:            0               0

A big improvement but I would have hoped for even better, does this seem like it could be low enough for DLM to try fastpath?

[NewtronStar]

does this seem like it could be low enough for DLM to try fastpath?

No it would need to be well below 20 ES per day for a week or two if that DLM calculation is correct, you have only got it down to 76 per day and there is a limit to how far you can cap the sync on the modem could never get it to go below 25Mbps