Jump to content


Photo

Why are there only 32 LNB numbers?


  • Please log in to reply
136 replies to this topic

#1 Huevos

  • PLi® Contributor
  • 4,243 posts

+158
Excellent

Posted 17 April 2014 - 23:36

Why are there only 32 LNB numbers in tuner config when there are 64 DiSEqC switching combinations combinations? This is really frustrating as I want to add more LNBs to my setup but E2 (not hardware) is stopping me.



Re: Why are there only 32 LNB numbers? #2 malakudi

  • Senior Member
  • 1,449 posts

+69
Good

Posted 18 April 2014 - 07:53

Actually the combinations limit is 128 LNBs, for receivers that also support 0/12V switches (some non-BCM do support 0/12V). I guess someone thought that "32 LNBs ought to be enough for anybody" :-)


Edited by malakudi, 18 April 2014 - 07:54.


Re: Why are there only 32 LNB numbers? #3 littlesat

  • PLi® Core member
  • 56,244 posts

+691
Excellent

Posted 18 April 2014 - 11:23

Good question! But do you need more then 32?

I suggest it was due to too many left right selections in the config menu... But now you can select through the complete list via the video button this ins't a real limitation anymore.

Edited by littlesat, 18 April 2014 - 11:25.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Why are there only 32 LNB numbers? #4 Huevos

  • PLi® Contributor
  • 4,243 posts

+158
Excellent

Posted 18 April 2014 - 22:46

Good question! But do you need more then 32?

I suggest it was due to too many left right selections in the config menu... But now you can select through the complete list via the video button this ins't a real limitation anymore.

Littlesat I've no idea what you are talking about. I've got 32 physical LNBs and want to add more. DiSEqC switching allows this but it is not possible because E2 has this unnecessary limitation.


Edited by Huevos, 18 April 2014 - 22:48.


Re: Why are there only 32 LNB numbers? #5 littlesat

  • PLi® Core member
  • 56,244 posts

+691
Excellent

Posted 18 April 2014 - 22:54

I suppose you can fix it yourselve ;).... Or did you discover it also needs changes in the binary...

But what did you do you need 32 lnbs?.... What sats do you switch?

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Why are there only 32 LNB numbers? #6 Huevos

  • PLi® Contributor
  • 4,243 posts

+158
Excellent

Posted 18 April 2014 - 23:03

I suppose you can fix it yourselve ;).... Or did you discover it also needs changes in the binary...

But what did you do you need 32 lnbs?.... What sats do you switch?

Fast zapping needs an LNB on each satellite.

 

Numbers above 32 are used for something else, not sure what. I'm lost trying to read it.

 

if lnbnum < 33:


Re: Why are there only 32 LNB numbers? #7 littlesat

  • PLi® Core member
  • 56,244 posts

+691
Excellent

Posted 19 April 2014 - 07:43

Two lnbs per sat... How does this increase zapspeed??

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Why are there only 32 LNB numbers? #8 Dimitrij

  • PLi® Core member
  • 9,990 posts

+338
Excellent

Posted 19 April 2014 - 08:05

NimManager.py

Line 1208: 	advanced_lnb_choices = [("0", "not available")] + [(str(y), "LNB " + str(y)) for y in range(1, 33)]
Line 1394: 				lnb = ConfigSelection([("0", "not available"), (str(lnbnum), "LNB %d"%(lnbnum))], "0"

"not available" not gettext


GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Why are there only 32 LNB numbers? #9 littlesat

  • PLi® Core member
  • 56,244 posts

+691
Excellent

Posted 19 April 2014 - 08:33

As far I can see LNB 33, 34, 35 and 36 is used for unicable...

I do not have unicable... so I cannot check if I break this.....


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Why are there only 32 LNB numbers? #10 Dimitrij

  • PLi® Core member
  • 9,990 posts

+338
Excellent

Posted 19 April 2014 - 08:59

littlesat

http://sourceforge.n...af7606750ecd30/

ok,but...

-				lnb = ConfigSelection([("0", "not available"), (str(lnbnum), "LNB %d"%(lnbnum))], "0")
+				lnb = ConfigSelection([("0", _("not available")), (str(lnbnum), "LNB %d"%(lnbnum))], "0")
-	advanced_lnb_choices = [("0", "not available")] + [(str(y), "LNB " + str(y)) for y in range(1, 65)]
+	advanced_lnb_choices = [("0", _("not available"))] + [(str(y), "LNB " + str(y)) for y in range(1, 65)]

GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Why are there only 32 LNB numbers? #11 Dimitrij

  • PLi® Core member
  • 9,990 posts

+338
Excellent

Posted 19 April 2014 - 09:54

littlesat

Thanks.


GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Why are there only 32 LNB numbers? #12 Huevos

  • PLi® Contributor
  • 4,243 posts

+158
Excellent

Posted 19 April 2014 - 11:25

Lnb number is also used in tuner config screen so would need changing there too.

Littlesat, it is not 2 lnbs per sat. It is 1lnb per sat, and up to 64 satellites. I.e. combination of 16 uncommited x 4 committed = 64.

Re: Why are there only 32 LNB numbers? #13 littlesat

  • PLi® Core member
  • 56,244 posts

+691
Excellent

Posted 19 April 2014 - 11:36

Here in tuner config screen I see 64 sats now????


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Why are there only 32 LNB numbers? #14 Huevos

  • PLi® Contributor
  • 4,243 posts

+158
Excellent

Posted 19 April 2014 - 12:50

Then there is a problem. Number of sats should be around 200. Same as in satellites.xml.

Re: Why are there only 32 LNB numbers? #15 littlesat

  • PLi® Core member
  • 56,244 posts

+691
Excellent

Posted 19 April 2014 - 16:27

mmmm lnb is different then sats....???


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Why are there only 32 LNB numbers? #16 Huevos

  • PLi® Contributor
  • 4,243 posts

+158
Excellent

Posted 19 April 2014 - 17:05

mmmm lnb is different then sats....???

Of course it is different. One LNB on a motor can get you 70 satellites.



Re: Why are there only 32 LNB numbers? #17 littlesat

  • PLi® Core member
  • 56,244 posts

+691
Excellent

Posted 19 April 2014 - 17:29

Here I have two times one LNB for two sats without a rotor... (10E/9E + 4W/5W)


Edited by littlesat, 19 April 2014 - 17:31.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Why are there only 32 LNB numbers? #18 Rick Hunter

  • PLi® Core member
  • 9,051 posts

+56
Good

Posted 19 April 2014 - 17:34

Good question! But do you need more then 32?

I suggest it was due to too many left right selections in the config menu... But now you can select through the complete list via the video button this ins't a real limitation anymore.

Littlesat I've no idea what you are talking about. I've got 32 physical LNBs and want to add more. DiSEqC switching allows this but it is not possible because E2 has this unnecessary limitation.

Do you have 32 LNB's on one tuner? Or are the LNB's spread over multiple tuners?


Plinux member We have a.. (ehmm.. morgage) house.

Re: Why are there only 32 LNB numbers? #19 gerard0610

  • Senior Member
  • 939 posts

+41
Good

Posted 20 April 2014 - 09:50

I get a green screen in my situation.

Application:

16 LNB’s combined with a ‘USALS’ rotating dish and a VU+Duo sat-receiver in combination with OpenPLi 4.0.

Most people set the rotating adjustments for each satellite position.
However I have all set in once. This is already running this way for the last 5 years. I have set ‘All satellite 1’set as in figure “DiSEqC adjustments All satellites 1.jpg”. By use of only this all the Satellite position are Using the USAL rotor dish except the 16 LNB’s which I separate defined. This is working excellent.

 

After the change of last night I have put ‘All Satellite 1”on LNB 64 and adjust the parameters equal to the old situation.

After the conformation by clicking OK I get a green screen. See my crash log.

After this a reboot is not functioning any more.

 

I hope that you can follow my description (English is not my native language).

Attached Files



Re: Why are there only 32 LNB numbers? #20 littlesat

  • PLi® Core member
  • 56,244 posts

+691
Excellent

Posted 20 April 2014 - 10:12

FYI:

Likely this should fix this....

http://sourceforge.n...031309d6a404ec/

 

But in the commit log I made a mistake, I meant LNBs instead of Satellites... sorry...


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users