In reply to a post by MHC:

I have just installed an HG612 with SP10 and that makes it even worse - 60Mbps and 25ms latency!

Note that "SP10", whilst the highest SP number, is not the most recent firmware.

The history of public firmware for the HG612 seems to have been, in time order:
- B027SP06
- B028SP10
- B030SP06
- B030SP08

IIRC, I reflashed mine with B028SP10, but left it open for automatic firmware upgrades. BT have subsequently updated it to B030SP08 using the automatic upgrade mechanisms. In doing that, I lost the Web GUI on the modem, but kept telnet access - which was fine, as I didn't trust the GUI stats anyway.

It seems likely that the "SP10" variant on that list is not compatible with G.INP, but (unlike the ECI) will at least achieve a working sync, but with higher latency than normal.

Have been running an ECI at 72 Mbps with 8ms latency. Then two weeks back there was an overnight reset and I believe an upgrade to the cabinet with G.inp and my line dropped to 65Mbps and 15ms latency.

If the latency jumped like that, it is more likely that DLM intervened with standard FEC+interleaving, rather than G.INP.

In reply to a post by MHC:

Had a new user caused the problem I would have expected the reset to occur during the day soon after connection.

Unlikely. A new user connection would affect your line by anywhere from less than 0.5dB upwards, but not often more than 3dB.

Your line can easily survive one of these, perhaps two, three or four; it could continue surviving for months. It will, however, be running with reduced SNRM, and possibly ends up accumulating higher errors.

Without visible stats, you could not tell the difference.

Thanks for the comments from yourself and others!


I was suffering with a massive latency pulse every 40 minutes and it could not be solved - OR did find slight degradation of a joint which improved speeds by a small amount - had it been left it would really have degraded. However the pulses remained and changes of modem to other HG612s did not alter it. The intervals changed, speeds varied slightly however still problems,

I was seeing 62-64Mbps and 20ms. After a further few days changed to ECI which stopped the latency pulses, and speeds improved to around 65-66. Then speeds went up to 72-74 with sub 10ms latency and have been that way for months.

Then suddenly, the drop right back to 65 or so and 20ms latency along with a couple of drop outs at that time.

I installed an HG612 and that pushed latency up even further and a slight speed drop and te latency spike seemed to be back!

My link doe snot seem to like HG612s, even though the DSLAM is Huawei!.

I want to try the latest firmware to see if it has sorted the problem!

Yes, the information was a bit confusing at first, so it seems that the ECI modems will update correctly.

I think my line data on Zen's portal is not always updating, it doesn't make diagnosing things too easy. But I have not lost sync, although my backup ECI modem might not work.

If the current ECI firmware is adding in extra latency with G.Inp then I suppose that a future upgrade should improve it. If it is deemed necessary.

In reply to a post by rippedcotton:

I believe that the ECI modem should download a G.Inp friendly firmware upgrade if you can persuade your ISP to get your DLM reset.

No, The ISP will not going to reset DLM. Because it Openreach engineer need to attend at the cabinet but Openreach will not do this until a real fault on the line to fix it. In another word, Openreach will not reset DLM because of no fault on your line.

Any thoughts?

Connected PC, powered up modem with Reset pressed and held.

Went to 192.168.1.1 and had the upload page available.

Uploaded version ...30SP08 with WebGui

Allowed maybe 10 minutes and tried to access 192.168.1.1 again ... fails to connect.

In reply to a post by MHC:

Any thoughts?

Connected PC, powered up modem with Reset pressed and held.

Went to 192.168.1.1 and had the upload page available.

Uploaded version ...30SP08 with WebGui

Allowed maybe 10 minutes and tried to access 192.168.1.1 again ... fails to connect.

I had this issue, and realised I had previously changed the default ip address. Try using that address, or else try the process to factory reset the modem back to defaults - which the flashing process does not appear to do.

I think sometimes things need a cold reboot after flashing.

I don't think you can use the web gui to update the firmware, it doesn't work! You basically have to do the same steps as for unlocking the modem but load the latest (08) firmware.

Did not say I used the WebGui to update, I updated to the version with access to the WebGui.