Social Feed

AcWxRadar said:

Pittsville,

This is a problem that I have observed, too.

I can only guess as to the reason why, but I think that when it completes the blind scan and logs the TPs, it goes immediately to the channel scan but doesn't wait for the tuner to lock in to the TP signals. Sometimes it does and sometimes it misses that first TP lock. I think that if it misses the first TP lock, it misses all the TPs for the entire scan duration and just zips through with nothing found.

When this happens, I select "SAVE ALL CHANNELS" even though none were shown as being logged in and then perform a "SATELLITE SCAN" which picks up the channels.

I think that the system gets "slow" or busy with what it was initially doing with the blind scan and doesn't wait for the tuner to LOCK onto the first TP signal, so then it just breezes through the scan for channels before it can ever lock onto a signal. i.e. "Didn't detect a signal, move on to the next TP, didn't see any signal, move on to the next and so on and so forth."

Since it doesn't always respond this way, I have tried to determine what might be different from one blind scan to the next. I think it might have something to do with the first TP found during the blind scan. If it is a weak signal because it is a fringe beam or because the dish/motor isn't optimally aligned or if it is an S2 signal that demands a strong signal quality for the tuner to lock it may just foul the whole scan process.

I have also observed that even when doing a TP scan or even when fooling around with my motor alignment, it takes a few seconds for the signal to lock. If the delay to LOCK onto a signal is too long, then it will pass it by. So this could be another reason why it does not pick up the channels.

I do believe that the above reasons, if they are indeed the root of the problem, can be overcome with firmware upgrades. Of course, that is if OpenSat would address them.

Since the firmware is open source, anyone with the Linux programming knowledge can write codes for these boxes (one of the advantages that brought me to the AZBox). Possibly, in the future, someone will write a better firmware that befits our use and resolves some of these conflicts.

RADAR

Click to expand...

AcWxRadar said:

Pittsville,

This is a problem that I have observed, too.

I can only guess as to the reason why, but I think that when it completes the blind scan and logs the TPs, it goes immediately to the channel scan but doesn't wait for the tuner to lock in to the TP signals. Sometimes it does and sometimes it misses that first TP lock. I think that if it misses the first TP lock, it misses all the TPs for the entire scan duration and just zips through with nothing found.

When this happens, I select "SAVE ALL CHANNELS" even though none were shown as being logged in and then perform a "SATELLITE SCAN" which picks up the channels.

I think that the system gets "slow" or busy with what it was initially doing with the blind scan and doesn't wait for the tuner to LOCK onto the first TP signal, so then it just breezes through the scan for channels before it can ever lock onto a signal. i.e. "Didn't detect a signal, move on to the next TP, didn't see any signal, move on to the next and so on and so forth."

Since it doesn't always respond this way, I have tried to determine what might be different from one blind scan to the next. I think it might have something to do with the first TP found during the blind scan. If it is a weak signal because it is a fringe beam or because the dish/motor isn't optimally aligned or if it is an S2 signal that demands a strong signal quality for the tuner to lock it may just foul the whole scan process.

I have also observed that even when doing a TP scan or even when fooling around with my motor alignment, it takes a few seconds for the signal to lock. If the delay to LOCK onto a signal is too long, then it will pass it by. So this could be another reason why it does not pick up the channels.

I do believe that the above reasons, if they are indeed the root of the problem, can be overcome with firmware upgrades. Of course, that is if OpenSat would address them.

Since the firmware is open source, anyone with the Linux programming knowledge can write codes for these boxes (one of the advantages that brought me to the AZBox). Possibly, in the future, someone will write a better firmware that befits our use and resolves some of these conflicts.

RADAR

Click to expand...

• OpenRSi - OpenPLI for AZBox​