Quote:
Originally Posted by APE
I loaded in firmware v1.53 from Fortec before i looked to you's guys for
advise. Liked a few things that came about as a result of loading....but
didn't solve the dish moving problem. I switched over to Diseq on a few
sat's exreme east/west and stored this way. Seems to work ok......but
still curious why Usals wouldn't get me there.
|
I don't know why USALS wouldn't work on some sats, and not on others (although nothing surprises me anymore with this
Mercury).
One thing though, since you say that you're using DiseqC-1.2 on some sats, be aware that the Mercury's list of DiseqC-1.2 sat positions will get scrambled if you ever delete a satellite. Ie all satellite positions below the one deleted get moved down one position. Ie the list of positions doesn't change, but the list of satellites does. This can be corrected, but it's annoying. If you use the Fortec channel editor program for the Mercury, I'd advise saving a .bin file. I wrote a VB program, ie:
http://wejones.ftdata.com/bjbinview.zip
that will take that .bin file and tell you what DiseqC-1.2 sat position numbers were used by the Mercury for each sat, so if your positions ever get scrambled, you can recover without having to reprogram all the sats.
Right now the above program won't recover the sat list. I've been doing that manually with a binary editor, however I may change the program to do the recovery automatically if Fortec doesn't ever issue another firmware update. But if nothing else, the above program will tell you which numbers are being used, which comes in handy if you switch receivers. Ie you can just enter those numbers into the new (not Mercury) receiver, and won't have to program the satellites, since the positions are already stored in the motor.