Enigma 2 and diseqc 2.0 switches.

[mountaineer]

Have a diseqc 2.0 multiswitch/diseqc switch combo. 17 inputs and 8 outputs . Control by each receiver by diseqc 1.0 commands and 22 on/off.
So 1-4 ports are diseqc committed switch 1 and either 22 on or off to use all 4 ports.....5-8 use diseqc commited command 2 etc.

My problem is that I have 4 E2 receivers that have trouble with the switch..it is in the 22 on and off ONLY. So some of the inputs arent usable by the E2 receivers. The other 4 receivers that are openbox s10, azbox bravissimo, TBS computer card, and genpix computer card do not have any issues with the switch.

So the issue is in the E2. In this case all ports on #1 (1-4 inputs)work for all receivers. But # 2 (5-8 inputs) the H 22 on does not work...the E2 receivers sees it as always off and therefore sees H 22 off port only. On #3 (9 - 12 inputs) V off is always 22 on and cant see the port...and H 22 on is always seen as off and the port cant be used . On #4 (13-16 inputs) the 22 are always seen as on therefore both 22 off ports are useless to E2.


14366


There is nothing wrong with the switch...works perfectly with all other receivers.

Here is the kicker::::
i have a prof 7500 that is a 2nd tuner for AZME... It has the same issues when trying to tune in E2......HOWEVER if I take it and plug it into a computer and use smartdvb...it operates the switch perfectly..SO it is in E2. Can anyone see or help me with this?

Thanks!!!!!!!!!

[el bandido]

What E2 receivers and images have you tried?

[mountaineer]

Azme 3.92 Kernel.....openspa image

2 Edison OS minis openpli latest kernel

Zgemma H5AC have to check when get home. I think Openpli

[mountaineer]

i think I will try the optibox anaconda E2 when I get home and see if it is in the SH4 images as well.

[mountaineer]

Also these E2 boxes had no issues controlling stand alone 1.1 and 1.0 diseqc switches or in combination with zinwell multiswitches.
I think it is in the 2.0 bidirectional communication.

[el bandido]

Please Do this:
On one OS Mini,
Configure ALL your switch settings like they are supposed to be, OR what you think they are supposed to be. Reboot the receiver, then post your settings file in "etc/enigma2". Make sure you have not logged in to Facebook or anywhere else like that which requires a password. Some passwords are stored in the settings file. You may view the settings file if you wish using notepad or notepad++

[mountaineer]

Will do that this evening when I get home. Thanks!!!!

[el bandido]

Probably need to provide the make/model of switch too. That information may help.

[mountaineer]

[Only registered and activated users can see links]


Digital Satellite EMP-Centauri multiswitch 17/8 P 170 CP 8

[mountaineer]

settings file: thanks!!!

[el bandido]

What are the l.o. frequencies of the lnbs? You have several different ones listed in your settings. There should be only 3 lnb types for our fta:
C Band = 5150
Universal = 9750/10600
Circular = 10750

[el bandido]

I also need the satellites.xml file that you are using with these settings. Please send it.

[mountaineer]

I have several stacked lnb's. One I use I set it for 13850 so the H freq are correct and the V are off...use it for SES3 NBC...I actually fixed that one just now by changing it to 10750 and adjusting the freq of the H tps. Now that slot works!

i think it is in the communication between receiver and switch by 2.0. I think in that communication the switch sees the LO and the TPs from the database..it then calculates if that is correct or not and turns the 22 on or off to compensate.
seems it is all on the stacked lnbs....so it is the switch compensating somehow...

[el bandido]

I guess what we need is this:
A settings file with all satellites deleted except for the satellites used by the problem switch.
A list of lnbs that are used with this switch and the proper l.o. frequencies (please include lnb make/model).
The exact satellites.xml file that is being used with this switch.

I think we can get it to work properly. Am just having a very hard time understanding the settings file without knowing what is supposed to be controlled by it.

[mountaineer]

xml

[el bandido]

Your settings file breaks down like this:


lnb=1 lnb.1.lof=c_band
2230.tonemode=off
2250.tonemode=off
2270.tonemode=off
2290.tonemode=off
2330.tonemode=off
2350.tonemode=off
2370.tonemode=off
2390.tonemode=off
2410.tonemode=off
2432.tonemode=off
2470.tonemode=off
2489.tonemode=off
2550.tonemode=off
2590.tonemode=off
2630.tonemode=off
2650.tonemode=off
2669.tonemode=off
2690.tonemode=off
2710.tonemode=off
2730.tonemode=off
2770.tonemode=off
2820.tonemode=off
2880.tonemode=off
2990.tonemode=off
3019.tonemode=off
3030.tonemode=off



lnb=2
2329.tonemode=on
2369.tonemode=on
2431.tonemode=on
2451.tonemode=on
2469.tonemode=on
2488.tonemode=on
2526.tonemode=on
2549.tonemode=on
2589.tonemode=on
2610.tonemode=on
2668.tonemode=on
2709.tonemode=on
2750.tonemode=on
2769.tonemode=on
2879.tonemode=on
3300.tonemode=on




lnb=3 lnb.3.lof=c_band
2527.tonemode=off
2608.tonemode=off


lnb=4
2349.tonemode=on



lnb=5 lnb.5.lof=circular_lnb
2389.tonemode=off


lnb=6 lnb.6.lof=user_defined = 13850
2569.tonemode=on

lnb=7 lnb.7.lof=circular_lnb
2629.tonemode=on

lnb=8
2729.tonemode=on

lnb=9 lnb.9.lof=circular_lnb
2649.tonemode=on

lnb=10 lnb.10.lof=user_defined = 10750
2689.tonemode=off

lnb=11 lnb.11.lof=c_band
2570.tonemode=off

lnb=12 lnb.12.lof=circular_lnb
2409.tonemode=off






END

[el bandido]

Notice that lnbs 2,4, and 8 are not defined?
You have all of this running through one switch????

[el bandido]

lnbs 2,4,8 are universal, and you are running them with 22KHz ON. Are the non-working satellites on these switches? (Subtract the orbit positions in the post#16 list from 3600 to get the correct orbit listing. I.E. 3600−2409 = 1191, Or 119.1 West)

Have you tried using Band for the 22KHz tone setting with the universal lnbs? The 22KHz tone will come on automatically for anything above 11700 MHz when Band is selected.

Have you tried using Diseqc 1.1 commands to control the 8 positions in this diseqc switch?

Have you tried using ToneBurst A and ToneBurst B in series with other Diseqc 1.0 settings?

[el bandido]

Looks like there are 3 lnbs assigned to each Diseqc 1.0 port.

lnb.1.commitedDiseqcCommand=AB (port 2)
lnb.2.commitedDiseqcCommand=AB (port 2)
lnb.3.commitedDiseqcCommand=AA (port 1)
lnb.4.commitedDiseqcCommand=AA (port 1)
lnb.5.commitedDiseqcCommand=BB (port 4)
lnb.6.commitedDiseqcCommand=BB (port 4)
lnb.7.commitedDiseqcCommand=BA (port 3)
lnb.8.commitedDiseqcCommand=AA (port 1)
lnb.9.commitedDiseqcCommand=AB (port 2)
lnb.10.commitedDiseqcCommand=BA (port 3)
lnb.11.commitedDiseqcCommand=BA (port 3)
lnb.12.commitedDiseqcCommand=BB (port 4)

E2 Diseqc Commands =
Sat1........A/A
Sat2........A/B
Sat3........B/A
Sat4........B/B

(Note: The switch is only designed for 8 lnbs Max.)

[mountaineer]

Yes I have tried toneburst to no effect.

i think the issue is that diseqc 3 and 4 containing inputs 9-16 is designed for quatro lnbs. I have stacked individual lnbs on those. I use H for one whole sat and V for another whole sat...in my dish farm. What is happeneing is that because the switch/multiswitch is Diseqc 2.0 it is testing signal and seeing range of lnbs and changing its own settings based on what it is "hearing" from the lnb's. What I mean is that it detects the wider range of the stacked lnb's and assumes they are universal and tries to adjust its 22 settings accordingly. This overrides the "normal" settings in the switch. SO it turns on 22 for certain ports and off based on what it thinks is the configuaration.

Now this does not happen with 1 and 2 and their ports 1-8...they are designed to be used with dual or quattro lnbs. So it seems to leave those alone with the stacked lnb's..I think :)

So my setup as of now is the following

Command V/H 22 sat
1 V off 107.3 Cband (V only) Regular Cband LNB STATIONARY CBAND DISH
1 H Off 99 W Cband H only reg Cband Lnb STATIONARY CBAND DISH
1 V ON 125 KU V Only UNiversal LNB set to universal setting
1 H ON 87 KU H only UNiversal LNB set to universal setting
NUMBER1 all work correctly

2 V Off 97 Cband Reg Cband LNB MOVEABLE CBAQND DISH
2 H Off 97 Cband Reg Cband LNB MOVEABLE CBAND DISH
2 V ON KU Moveable Dish V Only Universal LNB Set to universal MOVEABLE KU DISH
2 H ON 95 KU STACKED KU LNB 10750 LO

2 All work correctly

3 V OFF 91 KU STACKED KU LNB LO set 10750
3 H OFF 103 Cband STACKED CBAND LNB 5150 LO set
3 V ON 97 KU STACKED KU LNB LO set 10750
3 H ON EMPTY

91 ku AND eMPTY DO NOT WORK CORRECTLY 22 TONE IS WRONG AND DOESNT ALLOW ACCESS TO PORTS.


4 V off 119 KU 10750 LO (special 118 and 119 LNB)
4 H OFF 119 KU 10750 LO (special 118 and 119 LNB)
4 V ON 121 KU STACKED LNB Set 10750 LO
4 H ON 103 KU STACKED LNB Set 10750 LO


119 ku ports do not work as 22 is stuck ON on all ports.

I have one stationary Cband dish with 2 lnbs on it...I take the H from one and the V from the other because the channels I want are only on thos polarities (99 H 107.3 V)
I have a moveable Cband Dish

[el bandido]

You may be right about the Quattro side, but how would enigma2 automatically know about that side? Unless like you say, the switch is 22KHz automatically on that side.

I think this switch could be viewed in enigma2 as TWO multi-switches tied together.
Ports A thru H would be Switch One.
Ports I thru P would be Switch Two.

(Two Ports assigned for each satellite, 1 for vertical, 1 for horizontal)

If this line of thinking is correct, then try:
Assign switch One the proper diseqc switch number (1-4 or A-D), and also use ToneBurst A
Assign switch Two the proper diseqc switch number (1-4 or A-D), and also use ToneBurst B

Is it possible to test this configuration on a satellite or two?

[el bandido]

OR is it possible to move the three Universal lnbs to the quattro side If they are not there already.

[el bandido]

Are the stacked lnbs the only ones giving problems???
It might help to have the make/model of the stacked lnbs.

[mountaineer]

They are the dish network KU stacked lnbs...used for 121 on the old super dishes I think.
the one cband stacked lnb I have to look at tonight.

[mountaineer]

i think I will try the following...
1 your suggestion

2. Move all stacked lnb's to commands 1 and 2 ports 1-8 and all non stacked to 3 and 4 ports 9-16. If the switch (3 and 4 ports 9-16) doesn't detect an expanded range then maybe it will allow the receivers to control the 22.

I use stacked lnbs to receive both polarities on one polarity...thus I get all of Cband on 103, all of KU on 103, 95, 91, 121, and 97. ..... each with one single coax respectively.


This switch does not "PASS THROUGH" anything to lnbs......22 , diseqc and usals do not make it past this switch. The switch does have 4 DIP switches at the bottom of it to allow for a continuous transmission of 22 tone from switch to lnbs for ports 3,4,7,8...Each individually controlled by a dip switch. That is why the universal 125, 87, and moveable KU ...... ku lnbs have to stay on switch commands 1 and or 2 in the 22 on ports so they will have a LO of 10600. The commands 3 and 4 do not transmit 22 tone so I think that may be where the probelm is at..it thinks there are quatro lnbs there and is trying to collect all of the range that a quatro has and get it to the receivers.

Commands, tones, and voltages from receivers do nothing but operate the switches and select ports...nothing from the receivers makes it past the switch...it powers the lnbs as well.

Hope this all makes sense.

[el bandido]

The L frequency or Line frequency for the satellite receiver is about 950 MHz to 2150 MHz. A bandstacked lnb uses all of this frequency range while most other lnbs only use a segment of it. Enigma2 is not really designed to operate across the whole 950-2150 MHz range at one time. This tidbit is also probably part of your problem.

What is the make/model of your Ku band stacked lnb?

We may be able to make changes in the NimManager file and get something to work. Really dunno...The problem with this is you would then have a "Custom" enigma2 image, and you would need to install your custom NimManager file after an update. The NimManager file may also vary with different image groups. Still, I think it would be worth testing and see if we can get it to work correctly.

[mountaineer]

Dish Network KU band stacked FSS for use on super dishes to receive 105 or 121 ku

From : [Only registered and activated users can see links]


DP FSS

This is a bandstacked LNB which receives 11.7-12.2 GHz, the standard FSS frequency range. It was most commonly used with all types of Super Dishes, paired with a standard Ku band feedhorn attached via a standard 20mm flange fitting. When used with the type I Super Dish it received 105°, where it was attached to an unusual double feedhorn. The type II Super Dish used one for 121°, in the steel version it was connected to a standard round feedhorn, in the fiberglass version it was used with an elliptical feedhorn with a depolarizing collar that could be rotated to accept either circular or linear signals. The DP FSS is compatible with all Dish Pro and Dish Pro Plus switches, it shows up as "DP Feed" in a check switch. It can also be used in conjuction with a Super Dish or any other dish/feed with any non-Dish Network satellite receiver that supports bandstacked LNBs to receive any Ku band FSS satellite.


[Only registered and activated users can see links] 2FNDgwWDY0MA%3D%3D%2Fz%2FxrgAAOSwqu9VJEMf%2F%24_1. JPG%3Fset_id%3D880000500F&imgrefurl=[Only registered and activated users can see links] bViewItem%3FloggedInUsrName%3D%26itemid%3D39113729 9744&docid=O0LjFpzCOgl_nM&tbnid=Vc--nIHDiaTiNM%3A&vet=10ahUKEwjau4j36pXWAhWD64MKHWTxDiwQMwgmKAAwAA.. i&w=400&h=300&safe=strict&bih=526&biw=960&q=Dish%20Network%20FSS%20lnb%20121%2C%20105%20stac ked&ved=0ahUKEwjau4j36pXWAhWD64MKHWTxDiwQMwgmKAAwAA&iact=mrc&uact=8

[el bandido]

Looks to me like you are missing a l.o. frequency for the band stacked lnb.

DP FSS
This is a bandstacked LNB which receives 11.7-12.2 GHz, the standard FSS frequency range.
To do this would require two l.o. frequencies.
L.o. = 13850
L.o = 14350

[mountaineer]

I tried both of our suggestions and neither worked.

When I moved the stacked lnbs to switch 1 and 2 they deactivated 22 settings in the switch just like when they were on 3 and 4. 3 and 4 with no stacked lnbs worked fine then. So I changed everything back and tried the toneburst but nothing. So it is the stacked lnbs confusing the switch to change and alter the 22 settings it responds to.

Its ok...I have it pretty much like I want it...but it is interesting to say the least

[el bandido]

I do not see any way that a bandstacked lnb like yours will work Correctly with one l.o. frequency. It has got to have two l.o.'s

[mountaineer]

I use only 1 lo of 13850 and adjust the tps from the opposite polarity to that lo...only have one polarity available to each stacked lnb so they cant change.

Anyway I found a solution/workaround !!!!!

I change the ones that werent working to Cband LO. That apparently released the control of the 22. So even though they are KU lnb I set the LNB in E2 to be a cband LO. Then adjusted the tps frequencies to that of 5150 instead of 10750 and wala it worked. The bandstacked lnbs on only one polarity must mess with the 2.0 and cause it to tryand fit all the ranges from both polarities and 22 on/off onto the 4 ports....therfore messing everything up..when changed to cband lo then it removes that "thought" since one is ku and one is "cband"
Ha tricked it...knew there was a way!

Thanks for all of your help!!!!!!!!

[el bandido]

LOL

I guess you could use the Ka lnb setting the same way.

Glad you found a way to make it work!

[el bandido]

BTW,
That is a very nice switch! Found a Video of it.


[Only registered and activated users can see links]

[mountaineer]

Would you believe I got it for $40 shipped on ebay? I was shocked...it is an excellent switch...almost no insertion loss.

Thanks for all of your help!

[el bandido]

I think the NimManager file could be changed so the LOF changes automatically in the receiver when the polarity switches.
Here is an incomplete example:

if currSat.voltage.value == "polarization":
if config.Nims[slotid].diseqc13V.value:
sec.setVoltageMode(switchParam.HV_13)
else:
sec.setVoltageMode(switchParam.HV)
elif currSat.voltage.value == "13V":
sec.setVoltageMode(switchParam._14V)
sec.setLNBLOFL(10750000)
sec.setLNBLOFH(10750000)
elif currSat.voltage.value == "18V":
sec.setVoltageMode(switchParam._18V)

I guess something for me to look at in the future.