Social Feed

After having "real life" get in the way for the past day or so and also deciding I'd back away from this problem before I took a hammer to that box, I got back on it last night and found out what the problem is/was!

Post #16 and 18 and a couple of others have the source of this problem listed but no one picked it up and pwrsurge, if you did indeed try to duplicate my problem then you didn't do exactly as I did when doing those scans.

But first, let me set the stage for how I got into trouble to begin with. As Stargaze mentioned, he uses a TP frequency of 3600 for his "dummy" TP. Years ago when I first did my channel list I did the same, ie, had 3600 and 11700 for my "dummies" and that has worked well for me over the past few years in both boxes. Each time I did a rescan of a satellite I always delete all but the "dummy" TP and that operation required me to press 3 buttons on the remote to delete each TP, ie, AZBox defaults to lowest TP number (which was also my dummy) so I have to arrow over, then press delete, then press OK. Smart and lazy me, (insert the word dumbass here also) I decided that I'd move my "dummy" TP numbers out to the upper end of the frequency just to do away with ONE arrow button push when deleting TPs and since there are some TPs up near the end of that frequency range I just decided to use 4205 and 12205. WRONG!! I finally figured out that these numbers being outside the normal range of the default scan settings is what the problem was. I went back and changed those "dummy" TP numbers back to 3600 and 11700 and all is well now!

The reason the scans didn't work with fresh firmware installs and default channel list is because each time I created 78w, the one TP number I always put in was 4205 and or 12205! Did the same thing too with other sats that I scanned??

So, I broke one of my own rules I use where my race car is concerned, ie, NEVER CHANGE BUT ONE THING AT A TIME, and it bit me in the ass big time!! In my case I decided to change my dummy TP numbers at the same time I changed firmware! Note, insert dumbass comment from above here again!

Ennywho, thanks to all for trying to help with this and I guess the up side is we all now know about another of the AZBox quirks!

That is really strange, I would not have thought that it would be the cause of it, especially when you consider that the default Ku band I always have to change from 12900 down to 12200 to avoid scanning unused frequencies! You would think that it would only consider it a selective scan. Guess it doesn't like it for a first scan! Anyhow, glad you figured out what was causing the quirk!

UPDATE!!!

Ok, so I resurrected this post today because I found out what the problem is/was and thought I'd put info in here so others could see if my fix works with their AZ Ultra.

We all know that EVERY satellite has to have at least ONE TP/SR listed or you're in deep do do. So when I first got my AZ I was careful to always put in 3650/29270 and 11700/29270 for "dummy" TPs in their respective satellites.

Over the years I got to a point where I was doing more blind scans, which required deleting all existing TPs before that was done. What I found was having that "dummy" TP at the beginning and skipping over it, ie, 3650/11700" added one more key stroke to delete all the other TPs? So, smart ass that I am, I went to the opposite end for the "dummy" TPs creating one at 4199 and another at 12199 instead. This allowed me to delete TPs with only 2 keystrokes instead of 3. Good idea, right? WRONG ANSWER because as it turns out THAT was what caused the blind scan issue I was having!!!

Early this week I took an old channel list dated back in 2012 and loaded that one with a clean install of bin 5020 and noticed on the first scan without deleting any TPs that AZ scanned normally?? WTF?? So I looked at that pre scan and post scan satellite list and didn't see anything different other than the 3650 "dummy" TP from the old days?? So just to verify this I went back to that same satellite TP list and moved the "dummy" back to the end at 4199, then deleted all TPs and did a rescan and the problem was back?? Double WTF? So I went back to the 3650 TP "dummy", did a TP delete and rescan and all came out fine, ie, normal!!

So I spent 3 days this week completely redoing that old 2012 channel list and now I've scanned EVERYTHING in and had zero problems as long as the "dummy" TP was at the beginning of that list on each satellite.

This ain't rocket science, but it does take some attention to detail at times. Hope this helps someone else!!

I've given up on the Azbox. I retired both the Ultra and the Elite. More trouble than it's worth to keep them working. I'm now using my GeoSatPro (which has been collecting dust since I bought it a year or 2 ago). Good luck in getting your Azbox units working.

I use my AZ Ultra every day and rarely have any trouble with it.Still running 5020 since what,5 years ago?,never put any of the newer updates in it.