Jump to content


Photo

Choice of tuner for search function


  • Please log in to reply
39 replies to this topic

#1 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 11 February 2015 - 11:46

I have a question.

Shouldn't it always possible to select tuner A or B when doing a channel search?

I have no way of selecting Tuner B. Does my setup prevent it?

 

My setup:

ET9000,

OpenPLi 4.0 from 3-4 months ago

Tuner A: positioner

Tuner B: second cable of a motorized dish


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Choice of tuner for search function #2 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 12 February 2015 - 09:38

Hi, is this such a rare setup that noone can confirm this behaviour?

Is it a feature or a bug?


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Choice of tuner for search function #3 WanWizard

  • PLi® Core member
  • 70,396 posts

+1,807
Excellent

Posted 12 February 2015 - 09:48

What is the difference between a positioner and a motorized dish? Do you mean both tuners are connected to the same rotor? Or that you have one with a twin LNB?

 

I think it is unclear exactly what setup you have, and how your tuners are configured. In general you should be able to select any tuner that is active, I can select all four on my 10K.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Choice of tuner for search function #4 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 12 February 2015 - 10:02

I have one dish and one rotor that moves the dish. I also have a twin LNB so both tuners, A and B, in my ET9000 can receive different transponders from the same satellite. In tuner configuration menu I have the following setup, which should be correct for my system:

Tuner A: positioner

Tuner B: second cable of a motorized dish

However, in channel search menu it is impossible to choose tuner B.

 

Anyone with a rotor and a twin LNB could check? Probably, there are not too many of us. ;)


Edited by Robinson, 12 February 2015 - 10:02.

ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Choice of tuner for search function #5 Dimitrij

  • PLi® Core member
  • 10,299 posts

+347
Excellent

Posted 12 February 2015 - 12:19

It's not a bug.

So it should be.
When you start Enigma, we do not always know the position of the motor.

Therefore, 'second cable of a motorized dish' ignored for manual scan.


Edited by Dimitrij, 12 February 2015 - 12:22.

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


Re: Choice of tuner for search function #6 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 12 February 2015 - 12:34

OK, but I'm still not convinced.

When you turn on the box a certain channel on a certain satellite is then switched on, so Enigma should already know where it is. Anyway, if I were able to choose tuner B for channel search on a certain satellite then tuner A should use the rotor to move the dish to the satellite I want in order to do a search.

Besides, if a channel is being recoreded, there is no way for me to do a manual channel search (neither tuner A nor tuner B) on the same satellite.

For me this is wrong and I'm pretty sure it might be corrected but of course I realize it would require some (or even a lot of) work.


Edited by Robinson, 12 February 2015 - 12:35.

ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Choice of tuner for search function #7 Stan

  • Senior Member
  • 380 posts

0
Neutral

Posted 12 February 2015 - 13:16

So what you are saying is, that it's not possible to do a channel search while Tuner A is busy with recording? What happens when you try it?



Re: Choice of tuner for search function #8 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 12 February 2015 - 13:33

I'm not at home now but I will check that later today.

As far as I can remember, I get some sort of pop-up information "no tuner available" or something.

I'll confirm that when I get back home.

So I hope you guys can now see it is not a desirable behaviour not to be able to choose tuner B for a motorized system with a twin LNB.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Choice of tuner for search function #9 Dimitrij

  • PLi® Core member
  • 10,299 posts

+347
Excellent

Posted 12 February 2015 - 13:48

Sorry, I think this one will not do.
Since when configuring 'second cable of a motorized dish' no satellite list.


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


Re: Choice of tuner for search function #10 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 12 February 2015 - 13:50

Dimitrij, are you perhaps the author of the part of the code responsible for channel search?


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Choice of tuner for search function #11 Dimitrij

  • PLi® Core member
  • 10,299 posts

+347
Excellent

Posted 12 February 2015 - 14:11

Dimitrij, are you perhaps the author of the part of the code responsible for channel search?

No.
This is done in a very long time.


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


Re: Choice of tuner for search function #12 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 12 February 2015 - 17:26

In general you should be able to select any tuner that is active, I can select all four on my 10K.

I agree with you. That is why I started this thread.

 

So what you are saying is, that it's not possible to do a channel search while Tuner A is busy with recording? What happens when you try it?

Screenshot attached.

 

Attached Files


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Choice of tuner for search function #13 Stan

  • Senior Member
  • 380 posts

0
Neutral

Posted 12 February 2015 - 17:42

What kind of channel search did you start?



Re: Choice of tuner for search function #14 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 12 February 2015 - 18:04

manual scan

pre-defined transponder

a transponder with a different polarity than the one being recorded

 

I assume any sort of scan would be impossible but I can try some more at night.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Choice of tuner for search function #15 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 14 February 2015 - 19:26

I even tried a manual scan on the same transponder as the one being recorded.

No luck either!

This is the setting for my tuner B. I'm pretty sure it is responsible for not being able to choose tuner B for channel scan.

So do you guys think it is too complex to try and correct that?

 

Attached Files


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Choice of tuner for search function #16 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 15 February 2015 - 21:28

I just wanted to add that for Menu - Setup - Service searching - Signal Meter, it is also impossible for me to select tuner B so even checking signal strength on a tuner set to "second cable of a motorized dish" is impossible. For me there must be something wrong deep in Enigma code.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Choice of tuner for search function #17 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 17 February 2015 - 20:39

What is the difference between a positioner and a motorized dish?

None, as far as the receiver is concerned. Whether using a V-box and positioner, or a DiSEqC 1.2 motor, what gets output by the receiver is the same.


Edited by Huevos, 17 February 2015 - 20:40.


Re: Choice of tuner for search function #18 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 17 February 2015 - 20:55

For me there must be something wrong deep in Enigma code.

No. It's right there in the Python code. Maybe it was me who put it there in Satfinder when I updated several years ago so you could switch tuners in the main screen.

if n.config_mode  in ("loopthrough", "satposdepends", "nothing"):
            continue

Just remove "satposdepends" from that tuple, send the plugin to the box, and try some tests to see what happens.



Re: Choice of tuner for search function #19 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 17 February 2015 - 21:17

And in ScanSetup the slave tuner is skipped if it is the same type as the master. So if one was DVB-S and the other was DVB-S2 both would show.



Re: Choice of tuner for search function #20 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 17 February 2015 - 23:17

It's right there in the Python code. Maybe it was me who put it there in Satfinder when I updated several years ago so you could switch tuners in the main screen.

if n.config_mode  in ("loopthrough", "satposdepends", "nothing"):
            continue

Just remove "satposdepends" from that tuple, send the plugin to the box, and try some tests to see what happens.

 

Do you mean /usr/lib/enigma2/python/Plugins/Satfainder/plugin.py file?

 

Now it is:

		satfinder_nim_list = []
		for n in nimmanager.nim_slots:
			if not n.isCompatible("DVB-S"):
				continue
			if n.config_mode  in ("loopthrough", "satposdepends", "nothing"):
				continue
			if n.config_mode == "advanced" and len(nimmanager.getSatListForNim(n.slot)) < 1:
				continue
			satfinder_nim_list.append((str(n.slot), n.friendly_full_description))
		self.satfinder_scan_nims = ConfigSelection(choices = satfinder_nim_list)
		self.feid = int(self.satfinder_scan_nims.value)

It should be:

		satfinder_nim_list = []
		for n in nimmanager.nim_slots:
			if not n.isCompatible("DVB-S"):
				continue
			if n.config_mode  in ("loopthrough", "nothing"):
				continue
			if n.config_mode == "advanced" and len(nimmanager.getSatListForNim(n.slot)) < 1:
				continue
			satfinder_nim_list.append((str(n.slot), n.friendly_full_description))
		self.satfinder_scan_nims = ConfigSelection(choices = satfinder_nim_list)
		self.feid = int(self.satfinder_scan_nims.value)

By the way, I also have plugin.pyo file in the same directory. Shall I remove it?


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W



12 user(s) are reading this topic

0 members, 12 guests, 0 anonymous users