|
|
Has anyone on a FTTC connection been able to interrogate the VDSL model to find the SNR, attenuation and sync speed values?
TIA
|
|
|
Yes...
http://forums.thinkbroadband.com/btsupplier/t/401399...
But requires hardware modifications.
-==-
DougM
|
|
|
Yes...
http://forums.thinkbroadband.com/btsupplier/t/401399...
But requires hardware modifications.
0o0o interesting!
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
|
Its actually possible to produce a new firmware image that disables the block on the modem's web page by following the instructions posted by asbokid, I've done it to my modem. This doesn't need hardware modifications.
It gets you access to both the stats and terminal access to the underlying linux OS, which lets you get much more detailed stats (tones) and control settings on the modem such as VDSL profile and target SNR (although in my testing it either causes the modem to be unable to sync or the settings are ignored, I haven't actually managed to sync at anything other than the usual settings).
|
|
|
Could you give a complete step by step guide?
|
|
|
We would be interested in this also.
Edited by deleted (Thu 18-Aug-11 13:26:08)
|
|
|
Doing this sort of thing on an Openreach supplied modem of course carries risk of being charged for it, e.g. you destroy firmware and cannot get a working set back on by BOOTP and Openreach realise this rather than just believing it was a hardware failure.
They are likely to look the other way when using alternate hardware, but playing with their own hardware is asking for attention/trouble
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
|
Of course, but when it's a test line of our own that we use specifically for testing/diagnostic purposes, and have a number of spare VDSL2 modems we use for diagnostic purposes (e.g. to send to a customer having an issue on FTTC to determine whether it is their modem at fault), it's a difference scenario.
It would be *ideal* from an ISP point of view to be able to send out a configured VDSL2 device to a customer who is having issues, so they can simply plug it in to a single PC with DHCP enabled and it will simply work (as the modem can do PPPoE itself). The ability to also remotely connect to the modem interface from our office to view stats, CRC errors etc can be invaluable information when trying to diagnose a fault.
This is all for testing purposes, not for trying to mess Openreach about or expect them to replace any hardware we brick.
|
|
|
What you want will come once they roll out wires-only connections for FTTC product.
Took sometime with the original ADSL roll-out, once faults drop to low levels in terms of hardware working first time all the time when visiting a customer it will start. Though be aware that VDSL2 is VERY VERY sensitive to extension wiring, hence the SSFP
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
|
Absolutely. But there needs to be a better solution yesterday. As an ISP its near impossible to diagnose issues on FTTC due to the managed CPE.
|