Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Signal problem
#1
Hello here,

i just bought a Sb5101 ( haxoware ) , i just plug in and nothing happened , can't find the signal , even when i put manually the signal (of the other model ) on the box , got this result

-------------------------------------------------------------------
CM> Attempting Downstream FEC lock @ freq= 162750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 170750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 178750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 186750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 194750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 202750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 210750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 218750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 226750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 234750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 242750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 250750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 258750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 266750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 274750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 282750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 290750000 Hz, QAM64/256
0x000196a4 [DHCP Server Thread] BcmDhcpServerThread::ThreadMain: (DHCP S
hread) Callback request expired:
timerDuration secs = 1
current time secs = 104
elapsed time secs = 1
Attempting Downstream FEC lock @ freq= 298750000 Hz, QAM64/256
CM> Attempting Downstream FEC lock @ freq= 306750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 314750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 322750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 330750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 338750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 346750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 354750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 362750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 370750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 378750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 386750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 394750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 402750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 410750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 418750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 426750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 434750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 442750000 Hz, QAM64/256
0x0001c1d8 [DHCP Server Thread] BcmDhcpServerThread::ThreadMain: (DHCP S
hread) Callback request expired:
timerDuration secs = 1
current time secs = 115
elapsed time secs = 1
CM> Attempting Downstream FEC lock @ freq= 450750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 458750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 466750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 474750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 482750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 490750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 498750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 506750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 514750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 522750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 530750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 538750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 546750000 Hz, QAM64/256
Favorite[0].freq = 346000000
Attempting Downstream FEC lock @ freq= 346000000 Hz, QAM64/256
Favorite[1].freq = 354000000
Attempting Downstream FEC lock @ freq= 354000000 Hz, QAM64/256
Favorite[2].freq = 657000000
Attempting Downstream FEC lock @ freq= 657000000 Hz, QAM64/256
Go back to 1st favorite
Attempting Downstream FEC lock @ freq= 554750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 562750000 Hz, QAM64/256
0x0001ed02 [DHCP Server Thread] BcmDhcpServerThread::ThreadMain: (DHCP S
hread) Callback request expired:
timerDuration secs = 1
current time secs = 126
elapsed time secs = 1
CM> Attempting Downstream FEC lock @ freq= 570750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 578750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 586750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 594750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 602750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 610750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 618750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 626750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 634750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 642750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 650750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 658750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 666750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 674750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 682750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 690750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 698750000 Hz, QAM64/256
0x0002182c [DHCP Server Thread] BcmDhcpServerThread::ThreadMain: (DHCP S
hread) Callback request expired:
timerDuration secs = 1
current time secs = 137
elapsed time secs = 1
Attempting Downstream FEC lock @ freq= 706750000 Hz, QAM64/256
CM> Attempting Downstream FEC lock @ freq= 714750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 722750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 730750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 738750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 746750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 754750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 762750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 770750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 778750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 786750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 794750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 802750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 810750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 818750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 826750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 834750000 Hz, QAM64/256
Attempting Downstream FEC lock @ freq= 842750000 Hz, QAM64/256
0x0002436a [DHCP Server Thread] BcmDhcpServerThread::ThreadMain: (DHCP S

-------------------------------------------------
Reply
#2
Are you in the USA or Europe?

Is BPI set to 1.0? Try BPI 1.1...

Change the frequency annex to where you are, save it, and reboot. Is it Diag or lite? In a few areas here it will not lock an upstream with Diag. It's in the frequency page i think.
Reply
#3
(28-03-2013, 09:43 AM)southernyankey1970 Wrote: Are you in the USA or Europe?

Is BPI set to 1.0? Try BPI 1.1...

Change the frequency annex to where you are, save it, and reboot. Is it Diag or lite? In a few areas here it will not lock an upstream with Diag. It's in the frequency page i think.


- what you mean by diag or lite ? please explain well

- it was bpi 1.1 ( but in my normal cable modem Bpi , on the main page , Bpi authentification is skipped )

Pics here

from my normal cable modem : Upstream Channel ID : 3
Frequency: 354000000

but when i put same infos on the haxoware , still not locking on the frequency
Reply
#4
up ...
Reply
#5
I just bought a new Motorola SB5101 modem and I'm having trouble setting it up. I plugged it in but it can't find the signal. I even tried entering a signal frequency manually (from another model I guess) but that didn't work either. The modem seems to be searching through a bunch of frequencies (between 162750000 Hz and 842750000 Hz) but isn't locking onto any of them. The fact that it's trying so many term paper writing service frequencies makes me wonder if the issue is with the modem itself or the signal from my internet service provider.
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)