35 replies to this topic

[Huevos]

https://github.com/H...19b01ca78ede731

 

 satellite.jpg   57.47KB   14 downloads

 

 terrestrial.jpg   57.27KB   12 downloads

 

 cable.jpg   54.44KB   12 downloads

[Erik Slagter]

Nice.

 

I have started a list of patches we can include whenever we've branched Enigma for (stable) OpenPLi-4, which is going to be quite soon, because I've got a few other things that need to be merged as well. It's on the list!

[athoik]

Do you trust DVB API?

If yes then you do not afraid of the following patch.

diff --git a/lib/python/Components/NimManager.py b/lib/python/Components/NimManager.py
index 1600e61..7f6b15c 100644
--- a/lib/python/Components/NimManager.py
+++ b/lib/python/Components/NimManager.py
@@ -538,6 +538,8 @@ class NIM(object):
                                self.multi_type = {}
                                for type in types:
                                        self.multi_type[str(types.index(type))] = type
+                       else:
+                               self.multi_type = {}

        def isCompatible(self, what):
                if not self.isSupported():

Report failures (eg multitype DVB-C/T tuner now not reported as multitype with above patch)

Edited by athoik, 2 November 2016 - 21:58.

[Huevos]

What is the purpose of this? Just to show faulty DVB API?

[athoik]

To remove types reported from nim_sockets that do not match the DVB supported ones.

Eg nim_sockets says DTMB and DVB-T. Now we keep DTMB because that else is missing...

[Robinson]

I see there is some improvement going on for Satfinder.

I guess it is still too difficult to enable Satfinder for Tuner B if it is set to "second cable of a motorized dish"?

http://forums.openpl...earch-function/

[Huevos]

To remove types reported from nim_sockets that do not match the DVB supported ones.

Eg nim_sockets says DTMB and DVB-T. Now we keep DTMB because that else is missing...

Is that somehow related to this commit?

https://github.com/H...0ab55099cb4L639

[Huevos]

I see there is some improvement going on for Satfinder.

I guess it is still too difficult to enable Satfinder for Tuner B if it is set to "second cable of a motorized dish"?

Question is, why would you want to? What is the logic?

Edited by Huevos, 3 November 2016 - 09:47.

[Robinson]

I know you consider it a crippled setup but I am not the only one with it: motorized system with a twin LNB.

If Tuner A is busy with recording I cannot do a channel search or even check signal quality with tuner B.

I would assume tuner B should be free for it and I should be able to use any tuner to check signal quality.

By the way, I use an attenuator on Tuner A and no attenuator on Tuner B so it would be perfect to be able to compare signals between both tuners.

[Huevos]

I would assume tuner B should be free for it and I should be able to use any tuner to check signal quality.

No. If tuner A is in use it is impossible to getfrontend on tuner B in Python in this configuration.

Edited by Huevos, 3 November 2016 - 10:54.

[Robinson]

And this is what bothers me.

I realize the limitation is somewhere deep in Enigma and that is why plugins such as Satfinder are unable to use tuner B in this setup. Such limitation should not be there, it is unnecessary.

[MCelliotG]

With more tuner types and systems getting new support, don't you think it's also time to re-consider a name change for the Satfinder as well? It's been some time since it's not used only for dish alignments and satellite signal monitoring!

[Huevos]

With more tuner types and systems getting new support, don't you think it's also time to re-consider a name change for the Satfinder as well? It's been some time since it's not used only for dish alignments and satellite signal monitoring!

Name changed ages ago in OpenViX.

 

 signal-finder.jpg   122.01KB   6 downloads

[littlesat]

And even that name is incorrect (for multituner). Then rename it transponder finder.... Or signal finder....

Edited by littlesat, 4 November 2016 - 07:46.

[Dimitrij]

name signal finder busy

[MCelliotG]

I think the most accurate name would be Signal Monitoring, cause this is mainly what it does tbh! Now if someone wants to use this as a satfinder, or signal finder or dish helper it's up to them! Yes, signal finder is a bit of a stretch....

[Erik Slagter]

Yes I guess you're right, it does MONITOR the signal, it doesn't FIND it. Not the nicest name though.

[Erik Slagter]

Do you trust DVB API?

If yes then you do not afraid of the following patch.


 

diff --git a/lib/python/Components/NimManager.py b/lib/python/Components/NimManager.py
index 1600e61..7f6b15c 100644
--- a/lib/python/Components/NimManager.py
+++ b/lib/python/Components/NimManager.py
@@ -538,6 +538,8 @@ class NIM(object):
                                self.multi_type = {}
                                for type in types:
                                        self.multi_type[str(types.index(type))] = type
+                       else:
+                               self.multi_type = {}

        def isCompatible(self, what):
                if not self.isSupported():

Report failures (eg multitype DVB-C/T tuner now not reported as multitype with above patch)

I added it to the queue for 5.

[MCelliotG]

Yes I guess you're right, it does MONITOR the signal, it doesn't FIND it. Not the nicest name though.

Signal Information (signalinfo) sounds more legit, indeed!

[Rob van der Does]

Or 'TransponderInformation': it shows all details of a transponder and is even able to scan it.