What a difference a sync makes

Started by Rik, May 13, 2008, 11:55:37

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Lance

Rik is running the SBC firmware on the 2wire 2700HGV, which for some reason initiates a reboot or resync every 300 hours :)

I run my router 24/7.

Over the last half hour or so, my noise margin has been going between 5 and 6, and now seems settled on 5.
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

Update on my line...

Noise margin dropped to 4db at 8:35pm and to 3db at 9:13pm. It dropped to 2db at 9:49pm and that is where it is quite happily sitting at the moment. On my line, at the current sync, that is amazing!
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

It looks like it's all sorted then, Lance. :thumb:

If you want, you could force a re-sync at night so that your SNRM is 6dB at worse, but if there are no problems, you could equally leave it alone.

With regards to the 12 day/300 hour thing, it's something that Rik and I (and undoubtedly others) experience with the single SSID 2700HG running SBC firmware. There doesn't seem to be any real reason for it. I've now got myself a dual SSID with BT firmware, and it doesn't reboot. :)

Rik

The 2700 with SBC firmware re-boots itself every 300 hours (12.5 days), Baz, which means it often picks up poor speeds on alternative re-boots due to time of day.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

Further update, my line kept sync all night, and is now happily back to the usual 6db. Fantastic!

Shame it's not quite high enough for a 5mb profile!

edit: I've had 3,570,373 FECs and 2,245 CRCs since 15:10 yesterday.
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

You can usually try for the next profile, but stability is more important! ;)

Lance

Indeed. I don't think I could sync any higher and be stable. I'll just make do  ;D
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

Again, last night my line kept sync all night at the high sync. The noise margin dropped as low as 1db at around 10:30pm for about 10 mins but then went back up to 2db.

It does seem that getting my exchange side cable swapped has done the world of good!
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

madasahatter

Quote from: Rik on May 16, 2008, 08:06:18
The 2700 with SBC firmware re-boots itself every 300 hours (12.5 days), Baz, which means it often picks up poor speeds on alternative re-boots due to time of day.

Does anyone know exactly why it does that, or is it just one of lifes great modern mysteries?  ;)

Rik

Quote from: Lance on May 17, 2008, 09:41:13
It does seem that getting my exchange side cable swapped has done the world of good!

:yes:  :thumb:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Quote from: madasahatter on May 17, 2008, 10:13:28
Does anyone know exactly why it does that, or is it just one of lifes great modern mysteries?  ;)

We don't know why, Mad, it just seems to be something in the code. Possibly deliberate, probably accidental. It does trigger a full re-boot, though, not just a re-sync, so it's possible it was done for a reason.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

Damn. At 10:22 this morning, my line dropped sync to 4832, but it seems I now have a 9db noise margin target  :mad: :rant2:
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

BT working anywhere nearby, Lance?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

It's possible, but I'm not going out today so won't be able to see. Too much revision to do!
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

Quote from: Lance on May 17, 2008, 09:41:13
It does seem that getting my exchange side cable swapped has done the world of good!

Brilliant. :thumb:

Sebby

Quote from: Lance on May 17, 2008, 11:10:15
Damn. At 10:22 this morning, my line dropped sync to 4832, but it seems I now have a 9db noise margin target  :mad: :rant2:

I don't think that's necessarily a bad thing. Once you're used to a slightly lower sync, you'll find that you worry a lot less with a target of 9dB as there's so much more margin. Rik and I both have 9dB margins and wouldn't have it any other way. ;)

Rik

Yes I would. I'd like to sync at 8128 with a margin of 15db or more. ;)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby


Lance

To be honest, a sync of 4832 is more than I used to get before I had the 2wire and as it's solidly in the middle of the 4Mb profile, I'm happy :)
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

I get a very similar sync to you, Lanc (usually between 4.6 and 4.8Mb). What's your attenuation, out of interest?

Lance

Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

So it sounds like you're actually doing better than me, given that my attenuation is 47.5dB. :thumb:

I also had problems with a target SNRM of 6dB and it kept shooting up to 15dB, so I had it set manually at 9dB and it's solid as a rock; the SNRM moves only about 1dB at night. :)

Rik

Same here, at 6db the line was flaky. At 9db, the most variation I see normally is -2db, but generally it's only -1db. Of course, the Netgear was a different story...
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.