Been working on my C Band system today... finally locking in some S2 signals on C Band which is great!
However I noticed an issue with the AZBox..
When I try to watch the CW on 97 west (4060MHz) I can watch for about 20 seconds, and then the LNB power keeps turning on and off (and it also keeps turning on and off my GBOX.)
If I switch to another channel then everything works fine... I switch it back to that channel again and again I can watch for a few seconds and then the lnb keeps turning on and off.
I have no switches inline.
Anyone see this one before?
Well, I read your post this morning, went to 97, tried to tune in 4060, nothing. Decided to go to the setup screen to see if settings were correct. Strangest thing I've seen yet on the Azbox...... went down to the TV option on the setup screen, hit OK, went to the right intending to click on Tuner-A...... There was no tuner option there, ONLY the IP option???!!!??? I thought, wow, that transponder must have done something weird to the Azbox.
However, I rebooted the thing, and it's working again, and locks that transponder (can't lock the DVB-S2 stuff today for some reason.).
Anyhow, I'm not sure it's the same feed on today that it was when you had trouble, as I think I've seen different types of feeds on that freq, but today at least, I'm not seeing any issues with that transponder.
I'm wondering though.... when you were viewing the channel, were you hearing audio? Ie, could you have scanned this in when there wasn't one of those Dolby-e audio channels on, but were having problems when trying to view when the receiver was trying to play the audio that it's not capable of playing. Ie there are 4 audio streams on that transponder right now, but the first one is that Dolby-e, but MY Azbox doesn't scan that in, and only shows the other 3 streams, but if somehow your Azbox scanned that in, perhaps it gets confused trying to play the audio, and reset everything when it can't do the audio???? No, I guess that doesn't make sense, but I don't have any other ideas, other than new firmware having additional bugs. I switched to firmware about 2 levels back from what it is now, a couple weeks ago, and the Azbox has been locking up, and doing strange things (like the above) about every couple hours of usage since I "upgraded" the firmware. So my guess is that whatever firmware version you're using isn't stable.
One thing though... you say you're not using a diseqC switch, but I'm wondering if in fact there is a switch of some kind in the GBOX? Ie I've read a few posts by people using recent firmware, saying that the Azbox (Elite and Plus) is resetting their GBOX limits, which means that perhaps the Azbox is sending diseqC commands to the GBOX even though it's not supposed to. It seems possible that perhaps the GBOX cuts power off to the LNBF whenever it's trying to move the dish or something? Again, not too likely, but I've seen some very wierd behavior with several receivers, that when they think they are losing lock they will try to send diseqC signals to switches (and perhaps to motors), trying to get channels back in tune, and the symptoms are that my signal completely dissappears for a second or so while it's doing this, then comes back, just like the lnbf power has gone off then back on. In my case this is almost certainly due to the switches I'm using, but I just thought that perhaps the GBOX might have a switch that just took the lnb out of the circuit when moving the dish or something. Just a wild guess.
