Elite boot issue

[rprenove]

If I happen to powerdown my Elite box to cause a reboot, then it boots back up with the LNB frequency having changed on AMC 21. Consequently, I always have to change it back to the correct value (universal to 10750). If I scroll through my satellite list I do not see any other corrupted values. Does anybody have an idea for a quick fix? The only thing that I can think of is to delete AMC 21 and re-enter all the data again to see if it sticks OK which is not a quick fix.

 

[B.J.]

If I happen to powerdown my Elite box to cause a reboot, then it boots back up with the LNB frequency having changed on AMC 21. Consequently, I always have to change it back to the correct value (universal to 10750). If I scroll through my satellite list I do not see any other corrupted values. Does anybody have an idea for a quick fix? The only thing that I can think of is to delete AMC 21 and re-enter all the data again to see if it sticks OK which is not a quick fix.

Shouldn't take you very long to try that, and it's probably the quickest fix you'll find. I really think that more than AMC-21 is corrupted. I'm curious whether you have the BIG sat list with both eastern and western sats, or have you been able to edit that list to get only the sats that you can see? Also, what firmware version are you using?
When I first got my Abox, the sat list was corrupted, and there was a sat at 1.0W that couldn't be deleted, and as long as that sat was there, strange things happened to other sats in the list, with parameters changing, etc. So if by chance you have an old firmware version with the sat list that is corrupted, you may be messed up with ALL your sats until you get that straightened out.
Anyway, if you DO have the BIG sat list, try deleting the 1.0W sat, and see what happens. If you can't delete it, I think your whole list is corrupted. I think with later firmware versions, you can delete that sat, so if you CAN delete it, then it may be easier to fix things.

Also, even if you CAN delete the 1.0W sat, I'm curious whether that sat re-appears upon the reboot. If that's the case, then it's possible that following the instructions in another thread for replacing the DVBS.dat backup file might solve your problem, however that could also cause even more problems, so if it were me, I think I'd get things working before doing that.

But basically, I think what is happening is that on reboot, the Azbox is sensing that something is corrupted, and it's replacing your DVBS.dat file with the backup file which does NOT have AMC21 in it's master list, so you then have the list of sats that you've saved channels to which DOES have AMC21, but it won't be able to retrieve LO and other parameters from the master list. Just my guess.

 

[rprenove]

I do not have the big sat list. Over time I pruned it down and had a lot of strange issues with the box changing satellite locations on me. It was very painfull.

I have updated firmware a few times. I am currently on 9.3877

 

[B.J.]

I do not have the big sat list. Over time I pruned it down and had a lot of strange issues with the box changing satellite locations on me. It was very painfull.

I have updated firmware a few times. I am currently on 9.3877

Were you able to get rid of the sat at 1.0W ? When I had the corrupted list, I could delete other sats, but not 1.0W, and until I managed to get rid of that (by using the .xml file into the AzboxEdit program method), I had strange things happening. the 3877 firmware worked fairly well with the 2880 AzboxEdit program, as long as you didn't try to change anything.
Anyway, the corrupted sat list is the only idea I have. If that's not it, I don't know.

 

[cracklincrotch]

I've had the same problem (except it was a different sat.) I haven't ever figured out the rhyme or reason to it. When it's happened I just fix it and save the settings again and I'm off and running again.

 

[rprenove]

B.J.

I did delete the 1.0E sat a long time ago.

I ended up fixing my AMC-21 issue with Maz 3.0