Registered: 1199982923 Posts: 5,695
Reply with quote #1
Well.... I previously posted about a couple lightning storms with very close strikes having killed my Azbox Elite, my Prof 7500, my TBS 6925, and the last remaining port on my TBS-6983 (previous strorms knocked out my other 6925 and the first port on my 6983). Some of these receivers came back partially, in that the 6925 would power the LNB and slave to another receiver, the Prof-7500 came back so that it would work on vertical if set on horizontal (ie voltage very low), and one of the ports on the 6983 would work if slaved to my 6925. So I was kind of limping along , waiting for the availability of the new 4K receiver to replace the Azbox.
The Azbox had symptoms similar to what other people have been reporting, ie it was stuck in continuous booting. Anyway, today I decided that I was going to pull the Azbox out, and put in my old Coolsat 8100, to use until I get a better receiver. So I moved all the cables over to the Coolsat. I was about to take the Azbox away, but decided to give it one more chance at life......plugged it in.....and of course, it booted right up! I thought that maybe it just needed a rest for some reason, so I replaced the LNB and HDMI cables, and plugged it in. BOOTING, BOOTING, BOOTING....etc. So I pulled the LNB cable thinking there might be a partial short in the coax. Still stuck in BOOTING. Fooey I thought, but decided to also pull the HDMI cable....... booted right up.?!?! Reconnected the HDMI cable while it was running, and it stayed working. Tuned in a satellite channel, and the channel came up fine. Anyway, it seems like the HDMI cable was somehow keeping the Azbox from booting, but once booted, it worked fine. Strange. Now, if I could just figure out how to fix my two TBS-6925 cards. Both of them work fine on DVB-S, and will lock DVB-S2, however they don't decode the DVB-S2. Ie TSREADER is full of all sorts of errors, and even though the SNR might be high like 15, the BER will be like 0.3 or something like that, instead of zero. I think someone posted a while back that this meant that the demod chip was bad or something. But I'm not capable of replacing a surface mounted chip. I was hoping that somehow the EEPROM got corrupted, however I compared it to what I had downloaded from the card a year or two ago, and they files were identical. So I guess I'm out of luck on the two 6925 cards. But at least I got my Azbox back.
Registered: 1191673979 Posts: 1,247
Reply with quote #2
You may also want to re-seat the connector harness that connects the front display board to the main board. I have seen it cause the same symptom on a friend's AzBox Elite. Half of the connector was actually up. You could actually tell by looking at it that it wasn't seated properly.
If it is booting ok at this point you may want to consider reload of firmware from USB after formatting the application area. Some say reformat at least three times, not sure why though. __________________ 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
Registered: 1199982923 Posts: 5,695
Reply with quote #3
Originally Posted by
BillinIndy You may also want to re-seat the connector harness that connects the front display board to the main board. I have seen it cause the same symptom on a friend's AzBox Elite. Half of the connector was actually up. You could actually tell by looking at it that it wasn't seated properly. If it is booting ok at this point you may want to consider reload of firmware from USB after formatting the application area. Some say reformat at least three times, not sure why though. Thanks, I did re-seat the MOM device, but didn't think of the display connector you mention. If the problem returns, I will give that a try. I'm not sure I understand the reason for the multiple formatting of application area either. It was necessary for me once, when I upgraded to a significantly different firmware version, but has never been necessary when I reloaded the same version. On the other hand, I guess it can't hurt to do that. One thing I noticed though. I had the cover off, and decided to blow the dust off with an air nozzle off my compressor. The dust didn't blow off, because it seemed to be "oily" and stuck to the motherboard, so I kind of wiped the dust/oil off with a paper towel. It seemed to me that this might be an indication of an electrolytic capacitor leaking, but I looked at all the caps, and didn't see anything bulging or cracked or otherwise unusual. So I'm not sure where the oil came from, unless it came from my air compressor the last time I blew the dust off the motherboard.