The Plusnet curse?....On & On 1 Year On!
Morning TicnTac,
Yes, I'd say get the home hub reconnected for now. Let me know when you do.
Checking your connection logs this morning I can see two drops that happened since my last post, one at 23:22 and one at 08:45 this morning, let me know if either of those were you swapping your hardware around or rebooting .
Thanks for the superb level of detail you've gone into re the Thomson, in being honest with you we would not give support to such a degree as to understand the technicalities of what may be causing issues within the hardware. However we do know of overheating issues with the Thomson so it's good to be able to understand that issue a little better now.
Yes, I'd say get the home hub reconnected for now. Let me know when you do.
Checking your connection logs this morning I can see two drops that happened since my last post, one at 23:22 and one at 08:45 this morning, let me know if either of those were you swapping your hardware around or rebooting .
Thanks for the superb level of detail you've gone into re the Thomson, in being honest with you we would not give support to such a degree as to understand the technicalities of what may be causing issues within the hardware. However we do know of overheating issues with the Thomson so it's good to be able to understand that issue a little better now.
Just spotted that the disconnection at 8:45 was actually us updating your speed profile (as you resynched which caused this to be updated to 3000 at BT's side of things).
So with that in mind its probably more stable than we thought, I'll continue to keep an eye on things from this side but do let us know how things go with the home hub back in place and what the speeds are like.
So with that in mind its probably more stable than we thought, I'll continue to keep an eye on things from this side but do let us know how things go with the home hub back in place and what the speeds are like.
Webdude
Here's hoping
Good idea though, proper stat logs like that would be nice, and maybe Plusnet could think about introducing a Fault Diary rather than let the feedback forum do it for them? 
Just a thought!
Quote In my case it would be handy when rain stops everything (BB, incoming voice calls, dial-tone)... so I could put together a diary for BT to some year fix my line!
Here's hoping
Good idea though, proper stat logs like that would be nice, and maybe Plusnet could think about introducing a Fault Diary rather than let the feedback forum do it for them? Just a thought!
Quote Morning TicnTac,
Afternoon Mr Adam
Quote Yes, I'd say get the home hub reconnected for now. Let me know when you do.
23:22
Quote Checking your connection logs this morning I can see two drops that happened since my last post, one at 23:22 and one at 08:45 this morning, let me know if either of those were you swapping your hardware around or rebooting .
The 08:45 would be the profile resync
Quote Thanks for the superb level of detail you've gone into re the Thomson, in being honest with you we would not give support to such a degree as to understand the technicalities of what may be causing issues within the hardware. However we do know of overheating issues with the Thomson so it's good to be able to understand that issue a little better now.
To keep it simple, if the PSU throws more power that means more heat, those Caps will get hot if the Amperage goes up, it also means if it is the PSU, it is cheaper replacing one of them than a whole new hub, you maybe able to get lots of overheating hubs working now?
Quote Just spotted that the disconnection at 8:45 was actually us updating your speed profile (as you resynched which caused this to be updated to 3000 at BT's side of things).
Yes, it wasn't me, I didn't do it!
Quote So with that in mind its probably more stable than we thought, I'll continue to keep an eye on things from this side but do let us know how things go with the home hub back in place and what the speeds are like.
Okay:
So all in all, it was a) BT at Fault b) BT at Fault c) BT at Fault - so we can blame BT now can we?
If you think about it, PN only held us as a customer because:a) We have friends and family on PN
b) Didn't want to go to an LLU with a fault - and Squalk Stalk sucks almost as much as BT & PN put together
c) We do actually like PN - sort of, not a lot anymore........
d) Better the devil you know the devil you don't
Typical but true!So.........wonder how many folk have read this little Diary and been a) Put off being a customer b) Decided to jump ship at the end of their contract.
Who's to blame? BT? Plusnet too in a way, because PN=BT-ish - so I think PN needs to claim much compensation from BT over this, send me a nice posh router and a few months free broadband
Yeah I know, never going to happen, too much paper work involved and they'd rather lose a customer than keep one 
Well on that note, here are the evil hub stats
Quote ADSL line status
Connection information
Line state Connected
Connection time 0 days, 13:09:15 (14 hours - wow a first)
Downstream 3,424 Kbps
Upstream 443 Kbps
ADSL settings
VPI/VCI 0/38
Type PPPoA
Modulation ITU-T G.992.3
Latency type Interleaved
Noise margin (Down/Up) 6.9 dB / 15.2 dB
Line attenuation (Down/Up) 57.5 dB / 35.6 dB
Output power (Down/Up) 0.0 dBm / 13.0 dBm
Loss of Framing (Local) 0
Loss of Signal (Local) 0
Loss of Power (Local) 0
FEC Errors (Down/Up) 0 / 0
CRC Errors (Down/Up) 616 / 2147480000
HEC Errors (Down/Up) nil / 0
Error Seconds (Local) 372 (not sure what to make of this figure at this point in time - might put it down to the hub)
So in 60 hours or less we could be up to 8Mb then?
Chat's to you later!
Hey TicnTac,
23:22, Was hoping you'd say that
Cheers for the suggestion, I can't say much but we are reassessing our hardware provision at the moment and weighing up how we want to go about this in the future. But I will present that solution to the people here that can make a difference.
We'll have to see, as I tell everyone what's seen on this site isn't an accurate representation of the wider experience of our customer base and its worth bearing in mind that people do tend to use this site as a channel for complaining more than anything else.
Being realistic issues will come up with services like this no matter who your provider is, its how we can help from a customer support point of view that can be the make or break factor here. We do thank you for your patience and as such your patience will be rewarded.
We like to be the open and honest ISP so in line with that ethos I'm going to say blame us, we are your provider and you pay us for the service. Yes, BT Wholesale are our suppliers here and it's our job to feed back to them any failures from their side of providing the service to you via ourselves. If there's any specific points you want me to pick up with them then by all means fire away.
As for the speeds, things should be back to what they we're within the next 48 hours. I'll give you a call before close of play to day (5.30 for me) to see how things are going.
Adam.
23:22, Was hoping you'd say that
Quote To keep it simple, if the PSU throws more power that means more heat, those Caps will get hot if the Amperage goes up, it also means if it is the PSU, it is cheaper replacing one of them than a whole new hub, you maybe able to get lots of overheating hubs working now? Smiley
Cheers for the suggestion, I can't say much but we are reassessing our hardware provision at the moment and weighing up how we want to go about this in the future. But I will present that solution to the people here that can make a difference.
Quote So.........wonder how many folk have read this little Diary and been a) Put off being a customer b) Decided to jump ship at the end of their contract.
We'll have to see, as I tell everyone what's seen on this site isn't an accurate representation of the wider experience of our customer base and its worth bearing in mind that people do tend to use this site as a channel for complaining more than anything else.
Quote c) We do actually like PN - sort of, not a lot anymore........ Roll Eyes
Being realistic issues will come up with services like this no matter who your provider is, its how we can help from a customer support point of view that can be the make or break factor here. We do thank you for your patience and as such your patience will be rewarded.
Quote Who's to blame? BT? Plusnet too in a way, because PN=BT-ish
We like to be the open and honest ISP so in line with that ethos I'm going to say blame us, we are your provider and you pay us for the service. Yes, BT Wholesale are our suppliers here and it's our job to feed back to them any failures from their side of providing the service to you via ourselves. If there's any specific points you want me to pick up with them then by all means fire away.
As for the speeds, things should be back to what they we're within the next 48 hours. I'll give you a call before close of play to day (5.30 for me) to see how things are going.
Adam.
Quote Hey TicnTac,
23:22, Was hoping you'd say that
So was I
Quote Cheers for the suggestion, I can't say much but we are reassessing our hardware provision at the moment and weighing up how we want to go about this in the future. But I will present that solution to the people here that can make a difference.
To be honest, it is a good little router, although the 2200V has still got to have been the best we've had service wise, we no longer have that one though, the Evil Hub V2 is better at attenuation and power than the Thomson, but the Thomson does prove to be good, but only good, nothing special put it that way!
Quote We'll have to see, as I tell everyone what's seen on this site isn't an accurate representation of the wider experience of our customer base and its worth bearing in mind that people do tend to use this site as a channel for complaining more than anything else.
That is true, what comes on to this forum is a tiny percentage of the wider percentage of customers who get a service and who, either don't know there is a fault, wouldn't know a fault unless it took them offline, or those who've had a perfect service without any issues.
Quote Being realistic issues will come up with services like this no matter who your provider is, its how we can help from a customer support point of view that can be the make or break factor here. We do thank you for your patience and as such your patience will be rewarded.
True again, but when I was with NTHell (Before Virgin took over) apart from roadworks, vandals and car crashes into green boxes, they were pretty much the only faults we ever got, there was never noise, or line issues, you either had the service or didn't
I understand there are traffic issues with Virgin these days, but it has been a while and the family I have still on Virgin, they do not seem to have had problems.
Quote We like to be the open and honest ISP so in line with that ethos I'm going to say blame us, we are your provider and you pay us for the service. Yes, BT Wholesale are our suppliers here and it's our job to feed back to them any failures from their side of providing the service to you via ourselves. If there's any specific points you want me to pick up with them then by all means fire away.
We'll blame BT then, that is very good of you to accept that BT are to blame
Quote As for the speeds, things should be back to what they we're within the next 48 hours. I'll give you a call before close of play to day (5.30 for me) to see how things are going.
Yeah well, here comes to bad news
Quote ADSL line status
Connection information
Line state Connected
Connection time 0 days, 5:51:45
Downstream 1,152 Kbps
Upstream 443 Kbps
ADSL settings
VPI/VCI 0/38
Type PPPoA
Modulation ITU-T G.992.3
Latency type Interleaved
Noise margin (Down/Up) 21.3 dB / 15.1 dB (and before: Noise margin (Down/Up) 6.9 dB / 15.2 dB )
Line attenuation (Down/Up) 57.5 dB / 35.5 dB
Output power (Down/Up) 0.0 dBm / 13.1 dBm
Loss of Framing (Local) 11
Loss of Signal (Local) 1 (ooo dear)
Loss of Power (Local) 0
FEC Errors (Down/Up) 0 / 4294967295
CRC Errors (Down/Up) 69 / 2147480000
HEC Errors (Down/Up) nil / 0
Error Seconds (Local) 425 (this has gone up a lot)
We were doing so well too
I'm going to do a warm sync: 18:48 - connecting now, as I am offline as I type this little bit, should be up and running when the blue light stays on - and we're up. Doh! Doesn't work does it? Got to lose PPP to resync, a disconnect doesn't work - darn it - do I, do I not? Going to leave it for now and see actually, can't be dealing with it - well there you have it - we'll see what it is like tomorrow
Could that have been BT? As they've been working around this area, and at the green box, and underground j/boxes One step forward, a billion back - gonna blame you this time Adam lol 
Quote Line state Connected
Connection time 0 days, 0:40:29
Downstream 1,152 Kbps
Upstream 444 Kbps
ADSL settings
VPI/VCI 0/38
Type PPPoA
Modulation ITU-T G.992.3
Latency type Interleaved
Noise margin (Down/Up) 19.9 dB / 16.3 dB
Line attenuation (Down/Up) 57.5 dB / 35.6 dB
Output power (Down/Up) 0.0 dBm / 13.0 dBm
Loss of Framing (Local) 22
Loss of Signal (Local) 2
Loss of Power (Local) 0
FEC Errors (Down/Up) 43 / 4
CRC Errors (Down/Up) 0 / 2147480000
HEC Errors (Down/Up) nil / 1
Error Seconds (Local) 521
Thinks we have a problem?
How are the pretty pictures looking?
Speak to you soon !
Hey TicnTac,
I'm just running some diagnostics from here to see what the exchange is reporting your sync speed at. However something about those router stats is bothering me, its the output power (Output power (Down/Up) 0.0 dBm / 13.1 dBm) this should really be set between 15 and 21dBm. By far the most common cause of this being low comes back chipset compatibility, although we were able to source that D-link for you we don't have access to any non-broadcom chipset routers so it may be worth seeing if you are able to get your hands on such a device. If you decide to go down that route have a look at this support library article by myself and Mand :
http://community.plus.net/library/hardware/adsl2-hardware/
EDIT: the dianostics I've run have just come back and show a sync speed of 1152kbps, in case there are any other factors at play here the fault report is going back to BT but we do think the router chipset may be part of the issue in hand here, I don't want to leave you high and dry on that front but can't make any promises on the other hand so I'll do what I can to try and find something suitable to send out.
Adam
I'm just running some diagnostics from here to see what the exchange is reporting your sync speed at. However something about those router stats is bothering me, its the output power (Output power (Down/Up) 0.0 dBm / 13.1 dBm) this should really be set between 15 and 21dBm. By far the most common cause of this being low comes back chipset compatibility, although we were able to source that D-link for you we don't have access to any non-broadcom chipset routers so it may be worth seeing if you are able to get your hands on such a device. If you decide to go down that route have a look at this support library article by myself and Mand :
http://community.plus.net/library/hardware/adsl2-hardware/
EDIT: the dianostics I've run have just come back and show a sync speed of 1152kbps, in case there are any other factors at play here the fault report is going back to BT but we do think the router chipset may be part of the issue in hand here, I don't want to leave you high and dry on that front but can't make any promises on the other hand so I'll do what I can to try and find something suitable to send out.
Adam
If you hunt back a few months in the ticket, you'll see that the 0db output was mentioned by me, also that I was connected to the TSTC rather than the IFTN - now if what you say about yours, then if it is 21CN Annex A 992.3 (or would that be 992.5 ADSL2+?) on IFTN then there is a factor there that this new one should solve, we'll just have to wait and see really.
It just bugged me, because again if you look back at the original ticket #34259494, then you will see posted and quoted data and proof that this could be one major factor in solving the issue? However I thought the D-Link was going to play the part of testing for this?
Apparently this is how LLU providers get much better service and sync. router matches chipset in exchange, again some ISP's are going down the same route, router chipset to match exchange setup.
It is odd, but then unless it is very new technology, then anything that "supports" ADSL2/2+ isn't going to support it well, it has have direct support nothing else.
I still don't understand how I went from TSTC to IFTN if no L&S took place - here are some original router stats: (taken when things were going downhill)
Spot the output power - explain that one?
BT have been fluffing about with something or other?
We'll wait for the router change and see how it goes from there.....................but there is some fishing to be done here do you not agree?
Ok, I see 992.1 and now 992.3 - so is me or did we start off on ADSL1? then went up to ADSL2, since we're not on 992.5 ADSL2+ then something is odd, surely there has to be history of this?
Might also explain why we got stable syncs during the voice fault of 4004
I dunno, this needs a fine comb to go through the BT history and logging of everything? Put it this way I've managed to confuse myself well enough!
so do I, and so did I on 7:58pm, Thursday 12 Aug 2010 read from there down on the ticket! Proof and questions and one of the reasons why Ben sent out the D-link although that could be down to the OH Thomson
Ah well, we'll wait and see what the next 7 days bring - hope we can get this done before Christmas
Chat to you later - after a very confuzzling post lol
It just bugged me, because again if you look back at the original ticket #34259494, then you will see posted and quoted data and proof that this could be one major factor in solving the issue? However I thought the D-Link was going to play the part of testing for this?
Apparently this is how LLU providers get much better service and sync. router matches chipset in exchange, again some ISP's are going down the same route, router chipset to match exchange setup.
It is odd, but then unless it is very new technology, then anything that "supports" ADSL2/2+ isn't going to support it well, it has have direct support nothing else.
I still don't understand how I went from TSTC to IFTN if no L&S took place - here are some original router stats: (taken when things were going downhill)
Quote Uptime: 0 days, 0:00:56 (just reconnected)
DSL Type: G.992.1 annex A
Bandwidth (Up/Down) [kbps/kbps]: 448 / 3,104
Data Transferred (Sent/Received) [kB/kB]: 0.00 / 0.00
Output Power (Up/Down) [dBm]: 12.0 / 18.5
Line Attenuation (Up/Down) [dB]: 31.5 / 59.0
SN Margin (Up/Down) [dB]: 15.0 / 6.5
Vendor ID (Local/Remote): TMMB / TSTC
Loss of Framing (Local/Remote): 12 / 0
Loss of Signal (Local/Remote): 1 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): 0
Error Seconds (Local/Remote): 16 / 0
FEC Errors (Up/Down): 0 / 1,181
CRC Errors (Up/Down): 0 / 0
HEC Errors (Up/Down): 0 / 0
Spot the output power - explain that one?
BT have been fluffing about with something or other?
We'll wait for the router change and see how it goes from there.....................but there is some fishing to be done here do you not agree?
Ok, I see
992.1 and now 992.3 - so is me or did we start off on ADSL1? then went up to ADSL2, since we're not on 992.5 ADSL2+ then something is odd, surely there has to be history of this?Might also explain why we got stable syncs during the voice fault of 4004
I dunno, this needs a fine comb to go through the BT history and logging of everything?
Put it this way I've managed to confuse myself well enough!
Quote we do think the router chipset may be part of the issue in hand here,
so do I, and so did I on 7:58pm, Thursday 12 Aug 2010 read from there down on the ticket! Proof and questions and one of the reasons why Ben sent out the D-link although that could be down to the OH Thomson
Ah well, we'll wait and see what the next 7 days bring - hope we can get this done before Christmas
Chat to you later - after a very confuzzling post lol
Hi TicnTac,
Sorry, going to have to ask you to explain that please, we're not familiar with those acronyms, google doesn't seem to find anything appropriate either.
I will do some digging for you here as other than you changing hardware at your side of things the only thing that could affect output power is either a change of line card at the exchange or a lift and shift has occurred out of the blue. Just to belay an concerns though the tie pair codes did change when I last noted that the lift and shift had gone ahead so we have reassurance that this was done on the 8th as planned.
Re the D-link router we sent this does have the same chipset as the original Thomson router, however at that stage I believe we just wanted to eliminate the hardware in general rather than delve into the specific issue with chipset compatibility. With that in mind though the Speedtouch 585 V8 is in the post and should be on its way to you now.
Adam
Quote TSTC rather than the IFTN
Sorry, going to have to ask you to explain that please, we're not familiar with those acronyms, google doesn't seem to find anything appropriate either.
I will do some digging for you here as other than you changing hardware at your side of things the only thing that could affect output power is either a change of line card at the exchange or a lift and shift has occurred out of the blue. Just to belay an concerns though the tie pair codes did change when I last noted that the lift and shift had gone ahead so we have reassurance that this was done on the 8th as planned.
Re the D-link router we sent this does have the same chipset as the original Thomson router, however at that stage I believe we just wanted to eliminate the hardware in general rather than delve into the specific issue with chipset compatibility. With that in mind though the Speedtouch 585 V8 is in the post and should be on its way to you now.
Adam
Cheers itsme,
Our level of understanding we believe does go as far as it needs to in terms of things like this but it's always good to increase the level of knowledge beyond what we just need to know.
Our level of understanding we believe does go as far as it needs to in terms of things like this but it's always good to increase the level of knowledge beyond what we just need to know.
Quote Vendor ID (Local/Remote): TMMB / TSTC
So you never wondered what the above meant when looking at users modem/route stats?
