11 replies to this topic

[ims]

I am using Satellite Configuration "non-standard user defined configuration..." I have 2 LNB + rotor as is on picture. LNB0 1.2 A/A, LNB1 1.1 A/B
How difficulty can be add into firmware optionaly function ? If this function is enabled(ref_move=1): Zap works as:

if ( ref_move == 1) rotor_ab(RP,x)
else standard(P,x)

where:
RP = referenc. position - set f.eg. in GotoXY or in PLi panel.
P position for LNB
x = (A/A,A/B,B/A,B/B)


rotor_ab(RP,x)
{
switch to A/A
if ( RP != actual position) then motor to RP position
switch to x
}

Now it works some as:
standard (P,x)
{
switch to x
if ( P != actual position ) then motor to P position
}

In case, when are 2LNBs on one dish with rotor, it is user unfriendly. F.eg. when is rotor on 30E (LNB0) and I want zap to program on LNB1 (23,5E), I must at first switch into some program on 19,2E (LNB0) and then program on 23,5E (LNB1). For Timer it is unusable too...
=> this modification switch to A/A, then move into RP (in my case 19,2E) and then switch into A/B.
IMHO, this can be usable for more users and it can then works for 2,3,4 LNBs on one Dish with rotor. Rotor would be always on A/A.
All routines in firmware exist. I think, it spend no much time for this realisation...

/ 2LNBs are used, because very often is switched between 19.2E - 23,5E => in standard position: LNB0 - 19,2E, LNB1 for 23,5E /

Attached Files

•  dm.jpg   12.03KB   0 downloads

[Roodkapke]

Hi,

I would configure this in another way.
Put the diseqc-switch behind the rotor.
So, 1 cable to the rotor.
From the rotor to the diseqc-switch.
Then connect both lnb's.
This way a standard diseqc switch can do the job.
Normal diseqc switches do not like the current needed to turn a rotor.

[ims]

Hi,

I would configure this in another way.
Put the diseqc-switch behind the rotor.
So, 1 cable to the rotor.
From the rotor to the diseqc-switch.
Then connect both lnb's.
This way a standard diseqc switch can do the job.
Normal diseqc switches do not like the current needed to turn a rotor.

No, it cannot works. Your connection works on IPBOX200, where is possible set for LNB1 references position. I need for LNB1 (23,5E) set Dish to 19.2E.

[Roodkapke]

I know that it will work, tried it myself.
The dreambox is able to get these diseqc settings to work.

But if you want to be totally shure, buy a uncomitted switch or diseqc relais from Spaun.
That will work always and can handle the current for the rotor.

[ims]

No, dreambox is not able it. I tried it, when I sold IPBOX and bought Dreambox.
Yes - rotor will be work always, but how You tell to dream, that for LNB1 (Astral 23,5) must rotor go only to 19,2E ?

[Roodkapke]

So, resume.

You want LNB 0 to be the "rotor lnb".
LNB 1 should be 23.5E and the rotor should automatically turn to a prefix position ?

[ims]

Yes, as I write on begin.
And both LNBs are on same Dish.

[Roodkapke]

Then i would simply buy a small dish.
For 25 euro you got exactly what you want.
Instant access to 23.5E and a full rotor setup.

A rewrite should be done by DMM i'm affraid.
The diseqc controls and so on are most likely inside the drivers, but that i don't know for shure.

[ims]

But I may not add next Dish :-(

[ims]

I think, it can be accessible, because SF image know f.eg. disable message about moving dish.

[Roodkapke]

Disabling that message is also possible in PLi.
However, that won't solve your problem.
Maybe it's time for a wavefrontier

[ims]

Disabling that message is also possible in PLi.
However, that won't solve your problem.
Maybe it's time for a wavefrontier

I know, that Disabling message doesnt solve my problem, but when it is possible change it => function for calling rotor must be accessibilited too.

I think, it must be easy. When will be Diseq rele behind rotor, them it is more easy:

ref_move ... enable/disable this modification (f.eg. stored in some file)
lnb ... number of LNB ... it is known
RP ... ref. position, stored in some file

if ( ref_move == 1 and lnb!=0) rotor(RP)
else rotor(P)

=> no new function for rotor, no modification of window... only one test