Welcome to GOFASTMOTORSPORTS.com ... ... ... Green Flag - Green Flag - Go Go Go ... ... Brought to you by Ricks Satellite - Where the Big Dish Rules!

Ricks Satellite Wildfeed and Backhaul Forum
Register Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 2      1   2   Next
Herb

Registered:
Posts: 30
Reply with quote  #1 
A few months ago, the Ku side of the AZBox Premium + that I got from Rick several years ago died. After some detective work, I discovered that both tuners inside the box would not tune Ku, but were fine on C. Other boxes wouldn't tune Ku either, so I replaced the LNB. The Az still wouldn't tune Ku, but the other boxes would. I tried the Az on another dish, and it would still not tune Ku. Since I never used the second tuner inside the Az, the problem is probably on the board and not with the tuners. Being of limited resources, I decided to use the Az only for C and plug the Pansat 9200 HD into the Ku side of the BUD. Since the Az was already jacked up with just about every problem ever mentioned on this forum, I did a data reset. Next, I deleted all sats that I will never use, including the Ku ones in my arc. All of a sudden, the Az runs like it is supposed to. It's been a month and I have yet to see a single problem, and this box had just about all of them. I suspect that the box is short of memory and clearing out unused data made it run as designed. Even the multiple problems I was having with recording and playback went away. I don't know if the box took out the LNB, or the LNB took out the box, or if the AZ and LNB experienced simultaneous failures, but the reason I bought an AZ is that it does the most. Now that I've discovered that insufficient memory appears to be the problem, I'll get a second AZ to use exclusively for Ku. I wish there was a way to add capacity to the AZ, but the second best option is to use two of them and clear out unused data.
BillinIndy

Avatar / Picture

Registered:
Posts: 1,244
Reply with quote  #2 
I would try a full reload. Meaning format the application area and load a known stable version such as 5020.

These issues sound like a switch or L.O. setting in the AZ is incorrect for some or all Ku sats. L band is what the tuner actually sees so it s strange C would be fine and Ku would have issues. I have just about all C and Ku sats loaded from 139 to 55 and loaded with channels.

__________________
The Big Dish since 1984!
WineGard CK1088 10ft; Corotor II; Norsat 8515/4206a; Venture 24"; DSR920; AzBox Elite 0.9.5020; LinkBox 8000 HD Local; QS1080IR V3.16

wejones

Avatar / Picture

Registered:
Posts: 5,644
Reply with quote  #3 
First, what billinindy said is probably a good idea.  Plus pick up a copy of one of the satellite data files that various people here have created.

However, no tuner from any consumer receiver tunes Ku or C-band frequencies.  They only tune the IF band, usually 950-2100 or a bit wider than that in some cases.  So if your receiver is capable of tuning C-band, it is capable of tuning Ku band.

Now, it is possible that the problem was as described, ie related to overloading the memory capacity of the receiver, and/or corruption of the data in the receiver, however I really wonder if it could have been a problem with the satellite parameters.  Too late now to find out, but I'm curious whether you were trying to use satellites for both C and Ku frequencies?  Ie for example if you have G-19 defined with both C and Ku freqs listed in the it's transponder list, you won't be able to tune both C and Ku transponders without changing the LOF in the satellite parameters.  Same thing applies to switch parameters if you are using a 22KHz or diseqC switch to select between C and Ku.  You cannot define a satellite which will allow you to play both C and Ku from the channel lists.  You CAN, however create 2 satellites, one for C and one for Ku, such as G-19-C and G-19-KU, one set up with C band parameters and the other set up for Ku.   I'm guessing that you must have known this, but that perhaps your satellite/transponder data got corrupted, wiping out the band specific satellites, replacing them with incorrect parameters.
  
  I know that there have been a lot of "problems" reported for the Azbox, however I have found it to be a very stable receiver as long as you refrain from doing certain things associated with each problem.

Herb

Registered:
Posts: 30
Reply with quote  #4 
Thanks for the advice, guys. I blind scanned some xpdrs today and four of the stored sats went gray with the longitudes missing. Guess I spoke too soon about the problems going away. I'm going to research the procedures you both recommended and give them a try. I've always input everything with the remote, so I have some learning to do. I usually use the sats as the software has them and just change the parameters for the LO freq and such. Sat G-19/C would have 5150 and sat G-19/Ku would have 10750, so I think that's what you mean by using two sats. Since I've deleted all the Ku sats, I should have eliminated that possibility, right? I When I scanned these last ones, I did the sat switch/reboot trick, but I must have done it wrong. 

I need to put together a checklist of all the things I should and shouldn't do with the AZ. I like it when it works because it receives most of the FTA stuff that I want to watch. I think reformatting with ver 5020 is the best place to start, then loading the latest data files. Thanks again, guys.
Herb

Registered:
Posts: 30
Reply with quote  #5 
That didn't go so well. I downloaded the 5020 FW from the AZ.ca site onto a FAT32 USB. All appeared normal during install until we got to the STB initiated reboot. It said the Menu screen would come up when it finished, but all I got was a blank TV screen. I tried a hard boot and the STB said, "Welcome" "Booting" "Checking" "Checking" "Loading" then went blank except for the blue light above the display. The TV screen never showed the Azbox logo, just looked like an active xpdr with no video. Might be time for me to find another hobby.
jdcpa

Avatar / Picture

Registered:
Posts: 868
Reply with quote  #6 
This sounds a lot like what happened to me in March that I wrote about here. Don't give up. Once its quirks are understood well enough to work around, it's a great receiver. Try flashing again.

Make sure you haven't let Windows rename the bin file with two dots. Unhiding extensions is one of the very first things I do after every Windows installation, to avoid such foolish automatic misbehavior.

If you've never had it open for a good cleaning, take the opportunity now. Maybe heat coupled with two tuners has become an issue in its old age.

__________________
Hurricanes Hermine and Irma 28N paths. C Norsats: 8115 on Corotor II on 10' mesh; 5215G5 X2 on Bullseye I on 12' mesh.
Herb

Registered:
Posts: 30
Reply with quote  #7 
Thanks JD. This is the file that I tried to use: azbox-0.9.5020-patch   I'm trying to figure out how it knew it was a bin file without the extension. I think I should have renamed it before trying the install.
I'm not sure how to proceed from here because there is now no way for me to make an input to the STB as I have no video on the TV and no indication on the front of the STB except a blue light that I believe indicates the unit has power. I'm still researching past posts to find a possible answer. I may take a break and pop the cover off to see if it likes compressed air.
BillinIndy

Avatar / Picture

Registered:
Posts: 1,244
Reply with quote  #8 
Will the box still boot off of the .bin file on the usb stick?
__________________
The Big Dish since 1984!
WineGard CK1088 10ft; Corotor II; Norsat 8515/4206a; Venture 24"; DSR920; AzBox Elite 0.9.5020; LinkBox 8000 HD Local; QS1080IR V3.16

jdcpa

Avatar / Picture

Registered:
Posts: 868
Reply with quote  #9 
I suspect it did the erase first, then tried to flash a non-existent file. My USB stick has that 0.9.5020 file named

    patch.bin

47500K (48640056 bytes), 9 July 2012. I'm pretty sure the full instructions (wherever they are) require either that name or at least a .bin extension for flashing to succeed. Also either the instructions describe how to use the LED panel to perform a flash when there is no video output, or video should show up in some kind of safe mode for the purpose of flashing if it won't boot normally. Google found this, but emergency/rescue flashing seems to be missing.

__________________
Hurricanes Hermine and Irma 28N paths. C Norsats: 8115 on Corotor II on 10' mesh; 5215G5 X2 on Bullseye I on 12' mesh.
Herb

Registered:
Posts: 30
Reply with quote  #10 
Quote:
Originally Posted by BillinIndy
Will the box still boot off of the .bin file on the usb stick?


I tried renaming the file and it still will not boot from the stick. The front display also says "USB S . . " when I try, but nothing comes up at the end of the sequence. Blank TV screen, blank STB display.
jdcpa

Avatar / Picture

Registered:
Posts: 868
Reply with quote  #11 
Quote:
Originally Posted by Herb
I tried renaming the file...

What did you do to ensure the actual name on the stick is patch.bin ? Are there any other files on the stick? If there are, either delete them, or make a directory and move all others into it. The AZBox is limited in its filename understanding.

__________________
Hurricanes Hermine and Irma 28N paths. C Norsats: 8115 on Corotor II on 10' mesh; 5215G5 X2 on Bullseye I on 12' mesh.
BillinIndy

Avatar / Picture

Registered:
Posts: 1,244
Reply with quote  #12 
I have seen cases where renaming the file patch.bin ends up as patch.bin.bin
Try renaming it just patch with no extension

On the pc you are using turn off hide extensions for both known and unknown file types in windows Explorer you can then see the entire file name

__________________
The Big Dish since 1984!
WineGard CK1088 10ft; Corotor II; Norsat 8515/4206a; Venture 24"; DSR920; AzBox Elite 0.9.5020; LinkBox 8000 HD Local; QS1080IR V3.16

Herb

Registered:
Posts: 30
Reply with quote  #13 
O.K. guys, that sounds reasonable, so I'm going to go try both of those suggestions right now. When I renamed it, I right clicked the icon on the USB and selected properties. Then I renamed it. I may have an issue with the double bin thing.


Turned off the extension hide and the file is back to it's original name:  azbox-0.9.5020-patch.bin

Rebooted with stick inserted and above file the only item on the stick. Same results. Blank TV, blank STB display. I'll have to come back to this tomorrow. The wife wants the TV because it's Friday night. I guess I'll be out in the garage watching EBRU on the trusty Traxis and a 19 inch analog CRT Panasonic that came out of the motorhome when it got remodeled.
jdcpa

Avatar / Picture

Registered:
Posts: 868
Reply with quote  #14 
Quote:
Originally Posted by Herb
the file is back to it's original name:  azbox-0.9.5020-patch.bin

That's not the name the AZBox HD+ recognizes. It needs to be

Code:
patch.bin

__________________
Hurricanes Hermine and Irma 28N paths. C Norsats: 8115 on Corotor II on 10' mesh; 5215G5 X2 on Bullseye I on 12' mesh.
Herb

Registered:
Posts: 30
Reply with quote  #15 
Let me get rid of everything in front of patch.bin and see what happens. Thanks!
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.

Fellow Members, your posts are welcome here! Do not worry about posting everything perfect. Different receivers and LNB's will give you different Frequencies and Symbol Rates. Some set top boxes, PCI cards and USB receivers, Do Not Require all of the same information that others may need. It is not Required to post everything that others may need to tune in a feed. It is just most important to share the find. We can always adjust the Frequency and Symbol Rates and try the various Modulations and FEC's on our own receivers until we get a lock and then give a polite reply with what works for your receiver, as that information might help others as well. We all appreciate the efforts and energy of the Posters!

Thank You for Visiting GOFASTMOTORSPORTS.com - Keep Your Eyes on the Sky and the Track!