Quote:
Originally Posted by Jose47
Hi guys,
I finally did it. I took off the east limits on my SG2100 and ever since then I have nothing but problems with the DiSEqC. The USALS works great with most of the Sats. However, there are a few that I have to tweak and that is when the diSEqC goes ape Sh...t. It doesn't matter how many times I set up a Sat with the DiSEqC it won't remember to go back to that position. What it does is it goes back to O or some were near it.
I have done a master reset, I have changed the cables, I even switched motors and the problem still there. Ok you may think is probably my receiver, Right? Here is the strange thing I also have two units and is doing the same thing on both of them. If it is a software problem I would be totally  .
Why did I removed the East Limits? I wanted to get Telstar 12 @ 15W and Atlantic Bird 1 @ 12.5W.
I would appreciate any inputs from you guys.
Thanks! |
Do I understand that you switched to DiseqC-1.2, found the sat in question, then saved the position, then you were unable to return to the sat?
Having disabled the limits shouldn't have made any difference if the position was saved properly. HOWEVER, I guess I should have asked.... WHAT RECEIVER ARE YOU USING??? If it's a
Mercury, then the Mercury really doesn't do DiseqC1.2 properly, and that is your problem right there. You can use the Mercury in DiseqC1.2 mode, but as Bill190 pointed out, if you ever add and remove sats, or don't save the sats in order, then it really mixes everything up. In all likelihood, the mercury is trying to send your dish to some sat that is out of range of your dish, in which case it just goes to zero. The only way to tell is to use the serial port to download a channel data file, and look at it with a binary editor. My Mercury got hopelessly mixed up, but I was able to edit this file, re-load it to the Mercury, and now it's taking the dish to the right sats.
Relative to it being the same on different receivers, that's the way it SHOULD be with receivers that do DiseqC properly, because all the position data is stored on the motor, not in the receiver. The problem is, that the Mercury doesn't give the user any capability of choosing what position number is used for each sat, so it's pretty hard to jump back and forth between different receivers. With other receivers, I was able to set up the sat positions with one receiver, then set up the 2nd receiver to use the same position numbers, and it would take you to the proper position without ever needing to search for the sat. But this can't be done with the Mercury, unless you use a binary editor on the data file.
ANyway, I'm guessing that you're using a Mercury. If so, you're in for some annoyances.
