Thread: Diseqc 1.2

Originally Posted by hd fan

Mine sends the command ok for evry channel change but for instance for me to do a blind scan I have to disable DiseqC (OFF) otherwise it will "hunt" the signal and set the Lower Limit. Some sats if there is no signal it will start hunting for the signal as well instead of staying put on the predetermined position. I use 5220 fw. I use only DiseqC.

Right now, I'm using only diseqc.

That said jhonny , I have found that after resetting the VBOX (by pressing power while reconn plug at wall) then I can save all positions with Auto in Azbox and it works ok , I mean it sends the proper position command without confusing the VBOX.

I tried resetting the Gbox but still can't get things to work right. I even tried rebooting the Azbox but that didn't help. Only thing left is an Azbox factory reset which I don't want to do.

One other thing that I noticed is that sometimes the Azbox won't "wake up" the Gbox so the antenna doesn't move even though the Azbox display shows that the dish is moving.

johnny ? is this behaviour consistent between the elite and the ultra ? i would like to help but i dont have an ultra and i spent way too much on sat gear this year. from reading the posts of those with diseqc 1.2 issues i assume they are occuring on the ultras and premium pluses which i think have a different demodulator than the old premiums and elites. i think this is ware the problem lies but i dont have the hardware or the time to test my theories.

crackt out,.

Originally Posted by johnnynobody

With the Gbox remote I can tell the Gbox to go to P1 and it goes there. But, if I change "channels" on the same sat, the Gbox sometimes moves away from the programmed position. Sometimes, the Gbox appears to "hunt" (the Vbox did the same thing). Sometimes when I select a program, the Gbox goes past the programmed position and then comes back and stop on the programmed position. There has been a couple of times where everything worked OK. Anyway, the bottom line is that this stuff is erratic. If there is a receiver that properly controls a Gbox, I'd like to hear about it. I'd like to get something set up so that my wife can operate the system. I want to be able to select a program with the FTA remote and have an actuator controller (i.e. Gbox) move the dish the the proper position rather than having to move the dish with a separate remote control.

Just so you know, I've had all these problems from time to time. And they always seem to come and go with no rhyme or reason to them. It's happened maybe a handful of times. A couple of times just turning the receiver off for a minute or two fixed it.

Originally Posted by crackt

johnny ? is this behaviour consistent between the elite and the ultra ? i would like to help but i dont have an ultra and i spent way too much on sat gear this year. from reading the posts of those with diseqc 1.2 issues i assume they are occuring on the ultras and premium pluses which i think have a different demodulator than the old premiums and elites. i think this is ware the problem lies but i dont have the hardware or the time to test my theories.

crackt out,.

I haven't tried with the Ultra. Only the Elite.

Originally Posted by johnnynobody

Right now, I'm using only diseqc.

One other thing that I noticed is that sometimes the Azbox won't "wake up" the Gbox so the antenna doesn't move even though the Azbox display shows that the dish is moving.

I only have used Diseqc 1.2 here also. with a Elite, and a Ultra.

the only time that mine will not wake up the G-box is if it is on 1 of my fixed satellites that I do not have a Diseqc 1.2 turn on and boot the receiver, but if I call up a satellite that is with a motor location no problem at all, it will wake up and move to it.

are you sure that you do not have a corrupt satellite list that is causing this problem for you?? because I have seen this when the satellite list has gotten corrupted, the AZ will change it's position #'s in it's memory, but if you go into the installation it will have the same position # that that satellite has been program to in the past.

I have work Diseqc 1.2 for over a year, and have been using the 5020 FW for about a month now and do not see any of these problems that you are having, but I have seen it when I upgraded FW and my sat list got corrupted in the AZ.

Originally Posted by 1captain

I only have used Diseqc 1.2 here also. with a Elite, and a Ultra.

the only time that mine will not wake up the G-box is if it is on 1 of my fixed satellites that I do not have a Diseqc 1.2 turn on and boot the receiver, but if I call up a satellite that is with a motor location no problem at all, it will wake up and move to it.

are you sure that you do not have a corrupt satellite list that is causing this problem for you?? because I have seen this when the satellite list has gotten corrupted, the AZ will change it's position #'s in it's memory, but if you go into the installation it will have the same position # that that satellite has been program to in the past.

I have work Diseqc 1.2 for over a year, and have been using the 5020 FW for about a month now and do not see any of these problems that you are having, but I have seen it when I upgraded FW and my sat list got corrupted in the AZ.

I haven't checked every sat channel but I can get channels on every sat.

I played around with this and found that this process gets things working properly with the Azbox/Gbox:

1. Program the last satellite position.
2. Then select a previously programmed satellite position before leaving the setup submenu.
3. The dish will move to this position.
4. Exit the setup.
5. Dish will now move to all programmed dish positions when using the Azbox remote.

But, if I forget to do this, I just go back into the setup menu and select another satellite, the dish moves to that sat and then I exit the setup and everything works fine.

Otherwise, the dish won't move when you select a satellite channel with the Azbox remote.

Everything has been stable for 3 days now. I suspect the same thing happens with a Vbox but I'm testing out the Gbox for a couple of weeks.

Still, it's too bad that developers of the Gbox and Vbox don't test these units for compatibility with as many receivers as possible and alert potential buyers of the pitfalls.