Print

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

[burakkucat]

Two quick comments for Mr Eagle's attention:

* Posts 56 and 57 to this thread appear to be identical. 
* It was a certain resident of The Cattery who provided Kitz with a (pre-unlocked) Huawei HG612. 

And one for bossian (so that I can't be accused of feather-favouritism):

* A reset of the HG612 will not result in it needing to be 're-unlocked'. With the device being currently in use, I would recommend the following steps.

[1] Power down the router by disconnecting the PSU from the mains supply.
[2] Power down the HG612 modem by disconnecting the PSU from the mains supply.
[3] Disconnect the cable that links the modem to the telephone line.
[4] Power up the modem and wait for it to stabilise.
[5] Press and hold its reset button for 20 seconds. Release the button and allow the modem to re-stabilise.
[6] Power down the modem.
[7] Reconnect the cable that links the modem to the telephone line.
[8] Power up the modem and wait for it to stabilise.
[9] Power up the router.

[bossian]

Two quick comments for Mr Eagle's attention:

* Posts 56 and 57 to this thread appear to be identical. 
* It was a certain resident of The Cattery who provided Kitz with a (pre-locked) Huawei HG612. 

And one for bossian (so that I can't be accused of feather-favouritism):

* A reset of the HG612 will not result in it needing to be 're-unlocked'. With the device being currently in use, I would recommend the following steps.

[1] Power down the router by disconnecting the PSU from the mains supply.
[2] Power down the HG612 modem by disconnecting the PSU from the mains supply.
[3] Disconnect the cable that links the modem to the telephone line.
[4] Power up the modem and wait for it to stabilise.
[5] Press and hold its reset button for 20 seconds. Release the button and allow the modem to re-stabilise.
[6] Power down the modem.
[7] Reconnect the cable that links the modem to the telephone line.
[8] Power up the modem and wait for it to stabilise.
[9] Power up the router.

Done!

Thanks for the instructions  burakkucat, and interesting that since then my line has been up, with no re-syncs for 23 hours!! So maybe BE was right about my modem not being quite right!

But I'm not going to run outside and count chickens.....just yet 

@BE....not sure where Kitz lives, but I'm in Leicester

Here's some stats from the last 20 odd hours....

Question BE.......to get 2 hours stats I have to ask for 55mins?? This on is a 12 hour request? 

[burakkucat]

Thanks for the instructions  burakkucat, and interesting that since then my line has been up, with no re-syncs for 23 hours!! So maybe BE was right about my modem not being quite right!

But I'm not going to run outside and count chickens.....just yet 

That reads as if you have achieved a definite positive result! 

Excellent news. 

[Bald_Eagle1]

Thanks for the instructions  burakkucat, and interesting that since then my line has been up, with no re-syncs for 23 hours!! So maybe BE was right about my modem not being quite right!

But I'm not going to run outside and count chickens.....just yet 

I doubt that was the cause, but it was maybe worth a shot.

It does look more stable at the moment though.

@BE....not sure where Kitz lives, but I'm in Leicester

Not that either then. It's no secret that Kitz lives in the Blackpool area.

Here's some stats from the last 20 odd hours....

Question BE.......to get 2 hours stats I have to ask for 55mins?? This on is a 12 hour request? 

I notice that there are lots of gaps in your graphs.

It appears that for some reason, data isn't being collected every minute.

Maybe the PC you are using to harvest the data is running very, very slowly or it is very busy doing other things thus slowing down the data harvesting.

specifying 55 minutes actually means 55 data samples.
So, if roughly half of the expected samples are missing, 55 samples will actualy span a two hour period or so.

It might be worth checking Task Manager just in case a few instances of HG612_stats.exe are stuck there.
If they are, ending their processes should clear things up.

You should only see HG612_stats.exe appear in Task Manager for a couple of seconds each minute.

[bossian]

Hi guys, still here....just been working 4 days.

Lines still a tad messy, but PN have arranged another engineer for tomorrow.....so lets see if this one will remake all the joints between my house and the CAB

Here's my stats from this mornings run.....

[bossian]

Well another superb OR engineer! This ones been here for 4 hours!!

So today, remake of joint on pole and full remake of a very old and dodgy blue bullet style joint!

This one had the latest lappy with him and showed me all the info that they have available to them. The cable serving my house were installed in 1974 and there's only 2 UG joints along the way.

His manager stopped him doing the final one cause of time spent here, but it's now on the system that if my faults not sorted, the last joint will now also be remade.

And he was able to reset my DLM on the phone by an option!



Just waiting for PN to reset my profile now.

But there have been some good changes to my log file....so fingers crossed



xdslcmd info --stats

xdslcmd: ADSL driver and PHY status

Status: Showtime

Retrain Reason:   2

Max:   Upstream rate = 32047 Kbps, Downstream rate = 97888 Kbps

Path:   0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps



Link Power State:   L0

Mode:         VDSL2 Annex B

VDSL2 Profile:      Profile 17a

TPS-TC:         PTM Mode

Trellis:      U:ON /D:ON

Line Status:      No Defect

Training Status:   Showtime

      Down      Up

SNR (dB):    10.9       13.3

Attn(dB):    0.0       0.0

Pwr(dBm):    13.4       5.0

         VDSL2 framing

         Path 0

B:      239      236

M:      1      1

T:      23      5

R:      0      16

S:      0.0955      0.3771

L:      20107      5410

D:      1      1

I:      240      255

N:      240      255

         Counters

         Path 0

OHF:      991157      267928

OHFErr:      3432      0

RS:      0      226854

RSCorr:      0      4

RSUnCorr:   0      0



         Path 0

HEC:      996      0

OCD:      0      0

LCD:      0      0

Total Cells:   252035819      0

Data Cells:   1390068      0

Drop Cells:   0

Bit Errors:   0      0



ES:      44      0

SES:      11      0

UAS:      41      41

AS:      1642



         Path 0

INP:      0.00      0.00

PER:      1.64      6.12

delay:      0.00      0.00

OR:      116.56      203.67



Bitswap:   231      0



Total time = 36 min 18 sec

FEC:      0      0

CRC:      3432      0

ES:      44      0

SES:      11      0

UAS:      41      41

LOS:      5      0

LOF:      5      0

Latest 15 minutes time = 6 min 18 sec

FEC:      0      0

CRC:      20      0

ES:      10      0

SES:      0      0

UAS:      0      0

LOS:      0      0

LOF:      0      0

Previous 15 minutes time = 15 min 0 sec

FEC:      0      0

CRC:      3410      0

ES:      26      0

SES:      6      0

UAS:      0      0

LOS:      0      0

LOF:      0      0

Latest 1 day time = 36 min 18 sec

FEC:      0      0

CRC:      3432      0

ES:      44      0

SES:      11      0

UAS:      41      41

LOS:      5      0

LOF:      5      0

Previous 1 day time = 0 sec

FEC:      0      0

CRC:      0      0

ES:      0      0

SES:      0      0

UAS:      0      0

LOS:      0      0

LOF:      0      0

Since Link time = 27 min 21 sec

FEC:      0      4

CRC:      3432      0

ES:      38      0

SES:      6      0

UAS:      0      0

LOS:      0      0

LOF:      0      0



xdslcmd info --pbParams

xdslcmd: ADSL driver and PHY status

Status: Showtime

Retrain Reason:   2

Max:   Upstream rate = 32047 Kbps, Downstream rate = 97888 Kbps

Path:   0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps



Discovery Phase (Initial) Band Plan

US: (0,95) (880,1195) (1984,2771)

DS: (32,859) (1216,1959) (2792,4083)

Medley Phase (Final) Band Plan

US: (0,95) (880,1195) (1984,2771)

DS: (32,859) (1216,1959) (2792,4083)

       VDSL Port Details       Upstream        Downstream

Attainable Net Data Rate:      32047 kbps         97888 kbps

Actual Aggregate Tx Power:        5.0 dBm          13.4 dBm

============================================================================

  VDSL Band Status        U0      U1      U2      U3      D1      D2      D3

  Line Attenuation(dB):    0.1    18.2    28.5     N/A    9.9    23.5    39.1   

Signal Attenuation(dB):    0.1    18.1    28.4     N/A    9.9    23.5    39.1   

        SNR Margin(dB):    13.6    13.1    13.3     N/A    11.1    10.9    10.9   

         TX Power(dBm):   -4.9   -27.0    4.6     N/A    10.4    7.3    7.1   

[burakkucat]

Some good news, at last! 

. . . full remake of a very old and dodgy blue bullet style joint!

One of the old style 'blue beans'? (Examples in the image attached, below.) They should always be suspect, as a matter of course.

[bossian]

Some good news, at last! 

. . . full remake of a very old and dodgy blue bullet style joint!

One of the old style 'blue beans'? (Examples in the image attached, below.) They should always be suspect, as a matter of course.

Yeah that's it.....the engineer phoned me to tell me he was re-making a joint at the end of my road and did I want to have a nose......wild horses and all that......

Typical though, I forgot to take my phone for some pix.....DOH

But on a much better note.......my stats are looking great since this.....still waiting on PN to sort my profile.........

[ColinS]

.....still waiting on PN to sort my profile.........

You could try dropping the PPP connection for 8mins before reconnecting it.  Then the OR delta report may get transmitted and the IP profile updated.  Worth a shot?

[bossian]

.....still waiting on PN to sort my profile.........

You could try dropping the PPP connection for 8mins before reconnecting it.  Then the OR delta report may get transmitted and the IP profile updated.  Worth a shot?

Tried that, but didn't seem to do anything.....still waiting on PN to update, they can take there time sometimes grrrr

But on a brighter note, my stats for the last 13 hours look good! The 4 hour gap is whilst OR engineer was here and I was disconnected. I see there was a re-sync at 8pmish last nite, don't know why, but it hasn't made any difference.

[ColinS]

Did the resync appear in the resync.log file which you will find in the current_stats subs directory of hg612_stats?  If not, then it probably was some sort of parameter change rather than a speed (i.e. sync) change.  In the same directory there ought to be a current_stats_<date>_<time>-resync subdirectory for that time.  If you look in there at the plink_<D,T>.log file you should see the retrain reason, and you should be able to compare the parameters from that time, with a similar plink file from before the resync.

[bossian]

Did the resync appear in the resync.log file which you will find in the current_stats subs directory of hg612_stats?  If not, then it probably was some sort of parameter change rather than a speed (i.e. sync) change.  In the same directory there ought to be a current_stats_<date>_<time>-resync subdirectory for that time.  If you look in there at the plink_<D,T>.log file you should see the retrain reason, and you should be able to compare the parameters from that time, with a similar plink file from before the resync.

Mmmm interesting thought ColinS.....

The stats log shows the last re-sync at 13:19 yesterday, which is when the modem was re-connected at the end of my OR visit, but my router log shows it requested a PPPoE re-connect at around 8ish,  because it had sent 3 echo requests in a row and did not get any responses from PN. My router sends an echo request ever 2 mins....so it saw PN has not having replied in 6 mins so dropped then re-acquired a connection.

No resync file for that time saved, so 8pm was not a resync, but more down to PN?

[ColinS]

[so 8pm was not a resync, but more down to PN?

Yes, it seems so - a network level failure in PN, as this is a PPP timeout as you said.  I've posted elsewhere that PN intend to reduce its PPP timer from 2mins (x3 retries) to 30s(x3 retries).

[bossian]

[so 8pm was not a resync, but more down to PN?

Yes, it seems so - a network level failure in PN, as this is a PPP timeout as you said.  I've posted elsewhere that PN intend to reduce its PPP timer from 2mins (x3 retries) to 30s(x3 retries).

Yes, I have read your post on this, will have to see if it related to my issue.

Well my line conditions since Thursday have improved somewhat. Still a fair few drop outs, but DLM is strangely leaving me alone? I had at least 12 drops over a 2 hour period yesterday afternoon.....I would have expected DLM to return with a vengeance!!

PN have reset my profile today.... 0.128M-80M DS interleaving off, 0.128M-20M US interleaving off.

Attached, stats from