New Lnb changer

[RimaNTSS]

Disconnect the positioner and lead the coax cable directly to the diseqc motor

That is exactly how I am doing, bu somehow software does not allow to store positions of DiseqC motor.
Frequencies (C and Ku) are already separated in satellites.xml. OK, not so urgent, will figure out till next year

 

[Trust]

That is exactly how I am doing, bu somehow software does not allow to store positions of DiseqC motor.
Frequencies (C and Ku) are already separated in satellites.xml. OK, not so urgent, will figure out till next year

Dont know how the motor menu of your receiver looks or how it works .
Q1. Is there already a channel list stored in your receiver ?
Q2, did you searched the satellite positions and stored them in the positioner via the motor menu of the receiver ?

I made a 2 motor setup on the bench , using a V-box with a small actuator and a SG2100 .
Made a slider at the actuator to prefend twisting the eyebolt and have a option to mark the positions .
Connected the V-box , choose the Motorized Setting menu of the Maxdigital 220S , selected Astra 19.2º / diseqc 1.2 and with option 5 Move send the actuator to a random position .
Marked that position at the slider and stored it in option 7 Motor Control by selecting the </> button at SAVE
Did the same thing for HB 13º and Astra 23.5º with different positions at the slider .
Disconnected the coax cable from the V-box and connect it to to the SG2100 and made the same actions .
Then put the V-box and SG2100 inline and both turned to their marked positions when i choose each of the 3 stored satellites , also when the SG2100 is first inline .

The position of each motor is stored in the motor (SG2100) or for the actuator in the V-box .

But if you make a satellite position correction by the motor menu of the receiver , that also effected the position of the lnb changer .
Done by the remote in the V-box menu , has no effect to the lnb changer .

 

[RimaNTSS]

Thanks Wim!
I will try to explain my way of thinking and to show obstacles I am getting on the way. I have GB Quad Plus to play with (also DM8k available and it gives more or less same results, as they both Enigma2 receivers) , at other end I have actuator-driven antenna.
There is spreadsheet I made where all satellites I am able to receive from balcony. Which satellite given number from 1 to 31. Pozitioner is programmed to those 1-31 numbers and if I chose, lets say, channel from Astra4, than positioner clicks to memory #13 and antenna automatically turns to Astra 4. So, no problem with that, I did such a installations many times. But now DiseqC motor comes to play (something very new and strange for me ). I wish to program this motor same way as I am doing with positioner- but this time to turn proper LNB into antenna's focus. For example, motor's stored position 13 should turn Ku-band LNB . I was trying to program motor when positioner is excluded from the chain.
On receivers menu I get following controls: Tuner basic settings
And on Positioner control menu looks like this where green button "Store position" should remember position of the motor and tie it together with number 13. There also blue "Allocate" button which I can not understand what it should be doing. So, it is mess I have.

 

[Trust]

Rima , probably it can only store when there is a sat signal present , some receiver software works that way .
So fool the system by connecting a signal from a fixed dish (19.2 ?) and set a TP (10744 h ?) in the list .
That what i did at the Maxplus 2100 a few post up .

 

[Trust]

So guys , mine changer is ready (almost) , ordered a second X-1 C lnb for lineair reception .
Then the 4/1 switch have to be changed for a 8/1 type .
Now have the time for other changers , who's next ?
Made also adjustment at the EHM-100 H2H rotor , adding AZ scale and checking the ZERO position .

 

[MCelliotG]

Rima, are you planning to move both the dish and the changer with the same receiver? If you try to move the changer only using the E2 box, the solution is quite simple, you use a manual diseqc 1.2 setting and store the position of each lnb to the desired satellite, having signal or not is irrelevant in this case, but you need to set each position for each satellite separately! You can even use the same changer position for more than one satellite!
For instance if you need to use LNB 1 for 3.1, 4.8 and 19.2 East you will set the positioner for the first orbital (ie 3.1E) and give it a desired index (ie 2). Then without moving the changer you will go to 5E and use a different index (ie 3) and so on. When you need to change the LNB for another position you move that one as well manually (ie LNB2) and then store a different index for each orbital position you want regardless if they use the same lnb or not!
The disecq setting becomes more complex if you try to move both the dish and the changer using the same receiver as it involves a twin tuner setting and sequence repeat!

 

[RimaNTSS]

Of course, my goal is to move antenna and the changer with the same receiver. But by now I can not setup changer (even if there is no positioner between receiver and DiseqC motor). Somehow that DiseqC motor does not like me

 

[MCelliotG]

Yes, that would be very convenient, however the setting becomes very difficult due to lnb conflicts. The cable needs to go from diseqc switch to motor and then to the other motor and so on! Then each position should be set accordingly using a combination of diseqc 1.2 and 1.1 commands and sequence repeat! It should be possible but it's hard!
By the way, if it's possible could you please check if the Gigablue receiver can show db levels above 17db?

 

[RimaNTSS]

if the Gigablue receiver can show db levels above 17db?

I am not sure I ever seen levels above 17dB on any receiver.

 

[MCelliotG]

With an 1,80 dish? That's impossible, lol! I have 1.30 and see several above 18db especially on 23.5E and 0.8W! But not to go offtopic! I'm waiting impatiently for your progress, mr craftsman!!!

 

[a33]

If I try to allocate numbers they stick randomly.

Hi rimantss,

I'm trying to understand your problem. Do I understand right that you only have this problem with your lnb-changer motor?
And you wrote: the position-numbers stick randomly.
Is that only in the motor, and on the screen of your receiver you still see the correct, wanted number?
And does it mean that if you assign number 13 to a position, that it stores in motormemory position X (not being 13), and if you later try to store again at number 13, it does again store in number X? Or another random number Y?

Just trying to understand what you meant.

Greetz,
A33

 

[John]

Iv'e not got too much to add to my efforts really, added my extended Cband lump to the changer plate and can be seen as the one looking at focus consisting of the usual conical scaler / AV-Comm poloriser barrel /JRC 4.5 to 4.8Ghz lnb looking at circular 40.5West. I just spin the lnb within wave guide to get me from LHC or RHC or linear .... pretty simple but works. The weather has been absolutely appalling over the last week making it unfit to do any outside work

 

[RimaNTSS]

Do I understand right that you only have this problem with your lnb-changer motor?
And you wrote: the position-numbers stick randomly.
Is that only in the motor, and on the screen of your receiver you still see the correct, wanted number?
And does it mean that if you assign number 13 to a position, that it stores in motormemory position X (not being 13), and if you later try to store again at number 13, it does again store in number X? Or another random number Y?

Sorry for being not clear enough. Yes, I have difficulties with LNB-changer motor. On the screen of the receiver and also in receiver's memory all numbers are correct, like 13- which in my case represents 4,8*E Ku-band. But motor-memory does not memorize position of the rotor, but instead sends rotor to another position, sometimes this is somewhere about Zero but sometimes another (it is hard to say). If I turn rotor to needed position and push button "Assign" it says something like "Position assigned to #1 or #2 or.... # whatever."

 

[RimaNTSS]

I am starting to have suspicion that DiseqC motor is malfunctioning (even it is brand new). I have another motor (should be in working condition), so will connect it to receiver and will try to memorize some positions. Will do that, but not now

 

[MCelliotG]

Can you make a short description of your connectivity at the moment? How are the lnbs connected to the motor(s) and the receiver?
Edit: I found it, connectivity seems correct, with a small question, do you connect the disecq motor to the vbox powered motor?

 

[Channel Hopper]

I am starting to have suspicion that DiseqC motor is malfunctioning (even it is brand new). I have another motor (should be in working condition), so will connect it to receiver and will try to memorize some positions. Will do that, but not now

From your last two posts I think that it might be a mismatch of the receiver data to the motor rather than a fault. Many combinations of the two will have issues on certain satellite positions since the coding was AFAIK not written in the Eutelsat specification for DiSEqC, though there was mention of some 60 satellite position limit in many slave boards that found their way into motors.


It might be worth creating your own manual table of positions to orbital slots.

 

[MCelliotG]

The philosophy should be like: the receiver gives: 1) a command for the vbox to make the big motor move (this already happens as I see), 2) a second command parallel to the first for the small motor to move the corresponding lnb. 3) a parallel command to switch to the desired lnb via the switcher. I'll think about it and try to figure out the correct command combination. The one thing for sure is you need to use both 1.2 and 1.1 commands.

 

[RimaNTSS]

small question, do you connect the disecq motor to the vbox powered motor?

I connect DiseqC motor directly to the receiver, but can not get DiseqC motor start working properly.

 

[mcelliot_g]

That could be a problem, it would be easier to give priority to the big motor and then the moteck. Try this! Receiver > big motor > Moteck > Switcher > lnbs. Now Don't use the allocate function it completely ruins the stored positions! You have to reset the moteck now.

Στάλθηκε από το Xperia Z μου μέσω tapatalk.

 

[a33]

Sorry for being not clear enough. Yes, I have difficulties with LNB-changer motor. On the screen of the receiver and also in receiver's memory all numbers are correct, like 13- which in my case represents 4,8*E Ku-band. But motor-memory does not memorize position of the rotor, but instead sends rotor to another position, sometimes this is somewhere about Zero but sometimes another (it is hard to say). If I turn rotor to needed position and push button "Assign" it says something like "Position assigned to #1 or #2 or.... # whatever."

No sorry needed! You gave a hint of your problem, not knowing how difficult or incomprehensible this problem was; so we ask questions to investigate .

So it seems as if the motor doesn't store the right positions. Have you tried programming the positions with another receiver? That might do the trick for this motor.

Another way to investigate where the problem lies, or to tackle the problem:
As far as I know a motor recalls positions relative to the center-position. Does the storing go right for the LNB at the center position? In that case you can always store a LNB at center postion, and then use the function "recalculate" (though I didn't see that in your receiver-menu?). Assuming, of course, that your motor has no problem with the recalculate command .

Or maybe the motor expects movement before storing a new LNB-position, and you should do a "goto center" before storing a 'new' LNB position?

Greetz,
A33