318 replies to this topic

[littlesat]

The formuler does not have the proc... but cannot hotswitch...

[littlesat]

The formuler does not have the proc... but cannot hotswitch...
I also did not fully understand the requirement of that empty slot stuff... when your patch does work we can consider to use this ‘cleanup’

[athoik]

The formuler does not have the proc... but cannot hotswitch...

Please provide the ouput using "info" on e2 tuner list (or from dvb-fe-tool -f x).

Also explain the steps you tried and concluded that tuner is not able to change type on the fly!

Did you also try with my NimManager previously attached here?

[athoik]

And then is there again problem, that if is standard tuner detected as "hotswitchable", disable it is easy, but when I want workable tuner again, I must enable it and then restart gui.

Can you try this NimManager.py?

Can you try NimManager attached on #134?

[zeros]

Restart necessity test for my Triple with #134 NimManager.py, I did it in tomorrow morning and I'm not sure, if that helpful info.
All my lately tests, it's been done so, that the second Triple is disabled (Tuner C and D both disabled). Also many users have only one Triple.

Test1:
Configured:
Tuner A:
Configure DVB-S No
Configure DVB-C No
Configure DVB-T No
Tuner B:
Configure DVB-S No
Configure DVB-C No
Configure DVB-T No
+ box restarted (just in case)

Now I can add change configuration DVB-S No->Yes and DVB-S at once without restart activated.

Test2:
Configured:
Tuner A:
Configure DVB-S No
Configure DVB-C No
Configure DVB-T No
Tuner B:
Configure DVB-S No
Configure DVB-C No
Configure DVB-T No
+ box restarted (just in case)

Now when I add Configure DVB-T No->Yes it not activated. Only after restart DVB-T is Active.

Test3:
Configured:
Tuner A:
Configure DVB-S No
Configure DVB-C No
Configure DVB-T No
Tuner B:
Configure DVB-S No
Configure DVB-C No
Configure DVB-T No
+ box restarted (just in case)

Now when I add Configure DVB-T No->Yes it not activated. Next I activate also DVB-C No->Yes. The same, still can't access my DVB-T channels.
Next I activate DVB-S No->Yes and it's done without restart. I can access DVB-T channels.

For me I now can't install opkg install v4l-utils, probably for probably too new kernel, but on some old days (recently) it don't give me anything interesting output (see my post #49).

[littlesat]

I would say merge 134... as it also simplifies. I’m convinced that the empty slot is not really required.

[ricki]

From a Swedish forum Google translat

 

Now I have succeeded in getting the Tripeltun

ern Si2169D to find the DVB-T2 channels in Openpli and Openatv.
I had to manually set all parameters for each channel when searching.
Auto tuning did not work even on a separate channel.

If you do not have the transmission parameters, then start by installing an OE 2.5 image where the tuner works normally.
Then read out the channel parameters, via Menu / Info / Channel / Receiver status.
There is everything needed.

[athoik]

@littlesat, the check mode was re-reverted. Please give some time to make safe conclusions. Issue mention from @ims regarding tuner was about "enable" mode only after a restart.

So a tuner detected as hot, that requires restart of e2, means something needs fine-tune. Removing them as hotswitch we are not going to find the problem, right?

Currently the only "real" tester here is zeros, and he has no supported box! (although I am convinced that Dream use properly the delsys and mode change using DVB API).


@ims

    multituner: disable howtswitch on FBC tuners

    As reported from @ims, it seems there is an issue using FBC DVB-C/T tuner as hotswitch.

diff --git a/lib/python/Components/NimManager.py b/lib/python/Components/NimManager.py
index d36f062..7866388 100644
--- a/lib/python/Components/NimManager.py
+++ b/lib/python/Components/NimManager.py
@@ -517,7 +517,7 @@ class NIM(object):
                                types.remove("DVB-S")
                        if len(types) > 1:
                                self.multi_type = {}
-                               self.hotswitchable = not os.path.exists("/proc/stb/frontend/%d/mode" % self.frontend_id)
+                               self.hotswitchable = not (os.path.exists("/proc/stb/frontend/%d/mode" % self.frontend_id) or self.isFBCTuner())
                                for type in types:
                                        self.multi_type[str(types.index(type))] = type

@zeros, restarting e2 to make a type affective, means we still need to perform proper initialization on NimManager.

So we are close, but not fully done yet.


Changes previously attached here committed to develop branch (with an extra change that excludes FBC tuners marked as hot).

[ims]

Positive - now is not needed restart gui when going from Disable to Enable DVB-T tuner.

 

But I did not know, that I have so much hotswitchable tuners on boxes as:

 

osnino plus ... f.eg. /proc/stb/frontend/ is empty

osnino pro

osmio4k

formuler1

e4hd

...

...

 

hotswitchable tuner is for you each tuner, when is missing "mode" in "/proc/stb/frontend/%d" ? I thought, that this tuner type is on several few boxes only.

Edited by ims, 14 March 2019 - 21:58.

[littlesat]

Athoik the check on the proc did over detect hotswitchable tuners eg formuler1 was added. At least this did not happen with the AVL check. That was why I did revert it. It is not only the VU system that has hardswitchable tuners. In addition I have currently due to circomstances not many testtime.

Edited by littlesat, 14 March 2019 - 23:15.

[athoik]

All tuners with at least two modes (eg C and T) are able to switch via DVB API (aka hotswichable) since kernel 3.3

Before kernel 3.3 the solution was to use /proc/stb/frontend/X/mode in order to "switch" mode.

Today, some manufactures still use /proc/stb/frontend/X/mode, no idea why!


I can create a simple C program that switches to all available delsys and changes delivery system using DVB API, just to get it.

And I mean something like:

for ds in delsys:
   if not change_to(ds):
       print "failed to switch to delivery system %s via DVB API" % ds

Edited by athoik, 14 March 2019 - 23:36.

[littlesat]

So this means that it should be right now! Let’s wait (if more tuners are indeed hotswichable)...
Then for the ui we can simply name it multitype or so... and you see on the ui when it is hot or hard...
Btw Huevos also pushed an important fix on a typo by me

[athoik]

Well, there are more issue pending...

Eg. The issue mentioned by zero is totally reproducible on a tuner with S/T/C (like the one available on osmini+/osmega).

I was able to trace it down to this:

diff --git a/lib/python/Screens/Satconfig.py b/lib/python/Screens/Satconfig.py
index 83d0846..ef045e1 100644
--- a/lib/python/Screens/Satconfig.py
+++ b/lib/python/Screens/Satconfig.py
@@ -162,8 +162,8 @@ class NimSetup(Screen, ConfigListScreen, ServiceStopScreen):
                                self.nimConfig.configMode.choices.choices.pop("nothing", None)
                        if (not self.nim.isMultiType() or self.nimConfig.configMode.value != "nothing") and (not self.nim.isHotSwitchable() or self.nimConfig.configModeDVBS.value):
                                self.list.append(self.configMode)
-                       else:
-                               self.nimConfig.configMode.default = self.nimConfig.configMode.value = "nothing"
+                       #else:
+                       #       self.nimConfig.configMode.default = self.nimConfig.configMode.value = "nothing"
                        if self.nimConfig.configMode.value == "simple":                 #simple setup
                                self.diseqcModeEntry = getConfigListEntry(self.indent % pgettext("Satellite configuration mode", "Mode"), self.nimConfig.diseqcMode, _("Select how the satellite dish is set up. i.e. fixed dish, single LNB, DiSEqC switch, positioner, etc."))
                                self.list.append(self.diseqcModeEntry)

Once we enable the T on an S/T/C tuner, it doesn't get enabled because the above line executed.

Commenting above line tuner the T seems to work without reboot.


Also Huevos has spot some issues with motor, if I am not mistaken.


I think we still "need a lot of improvements" to make it fully stable.

[littlesat]

We need to perform that else only when we hard switchable multi tuner. So change it to
Elsif

Edited by littlesat, 15 March 2019 - 00:17.

[athoik]

BTW: Here is how VU+ is handling the delsys when mode changes.

root@vusolo4k:~# dvb-fe-tool -f 8
Device Vuplus FE (/dev/dvb/adapter0/frontend8) capabilities:
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_5_6
     CAN_FEC_7_8
     CAN_FEC_AUTO
     CAN_GUARD_INTERVAL_AUTO
     CAN_HIERARCHY_AUTO
     CAN_INVERSION_AUTO
     CAN_QAM_16
     CAN_QAM_64
     CAN_QAM_AUTO
     CAN_QPSK
     CAN_RECOVER
     CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.10, Current v5 delivery system: DVBT
Supported delivery systems:
    [DVBT]
     DVBT2
root@vusolo4k:~# init 4
root@vusolo4k:~# echo -n  0 > /proc/stb/frontend/8/mode
root@vusolo4k:~# dvb-fe-tool -f 8
Device Vuplus FE (/dev/dvb/adapter0/frontend8) capabilities:
     CAN_FEC_AUTO
     CAN_INVERSION_AUTO
     CAN_QAM_16
     CAN_QAM_32
     CAN_QAM_64
     CAN_QAM_128
     CAN_QAM_256
DVB API Version 5.10, Current v5 delivery system: DVBC/ANNEX_A
Supported delivery systems:
    [DVBC/ANNEX_A]
     DVBC/ANNEX_C

Here is a device that exposes all available delsys (a hotswitch one).

root@osmega:~# dvb-fe-tool -f 2
Device FTM-4862 (Availink AVL6862) (/dev/dvb/adapter0/frontend2) capabilities:
     CAN_2G_MODULATION
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_4_5
     CAN_FEC_5_6
     CAN_FEC_6_7
     CAN_FEC_7_8
     CAN_FEC_8_9
     CAN_FEC_AUTO
     CAN_GUARD_INTERVAL_AUTO
     CAN_HIERARCHY_AUTO
     CAN_INVERSION_AUTO
     CAN_MULTISTREAM
     CAN_MUTE_TS
     CAN_QAM_16
     CAN_QAM_32
     CAN_QAM_64
     CAN_QAM_128
     CAN_QAM_256
     CAN_QAM_AUTO
     CAN_QPSK
     CAN_RECOVER
     CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.10, Current v5 delivery system: DVBS
Supported delivery systems:
     DVBS2
    [DVBS]
     DVBT2
     DVBT
     DVBC/ANNEX_A
DiSEqC VOLTAGE: OFF
ERROR    FE_SET_VOLTAGE: Operation not permitted

Here is how to test it (change modes):

root@osmega:~# dvb-fe-tool -f 2 | grep Supported -A5
ERROR    FE_SET_VOLTAGE: Operation not permitted
Supported delivery systems:
    [DVBS2]
     DVBS
     DVBT2
     DVBT
     DVBC/ANNEX_A
root@osmega:~# dvb-fe-tool -f 2 | grep Supported -A5
ERROR    FE_SET_VOLTAGE: Operation not permitted
Supported delivery systems:
    [DVBS2]
     DVBS
     DVBT2
     DVBT
     DVBC/ANNEX_A
root@osmega:~# dvb-fe-tool -f 2 | grep Supported -A5
ERROR    FE_SET_VOLTAGE: Operation not permitted
Supported delivery systems:
    [DVBS2]
     DVBS
     DVBT2
     DVBT
     DVBC/ANNEX_A
root@osmega:~# dvb-fe-tool -f 2 -d DVBS
Changing delivery system to: DVBS
root@osmega:~# dvb-fe-tool -f 2 | grep Supported -A5
ERROR    FE_SET_VOLTAGE: Operation not permitted
Supported delivery systems:
     DVBS2
    [DVBS]
     DVBT2
     DVBT
     DVBC/ANNEX_A
root@osmega:~# dvb-fe-tool -f 2 -d DVBT2
Changing delivery system to: DVBT2
root@osmega:~# dvb-fe-tool -f 2 | grep Supported -A5
Supported delivery systems:
     DVBS2
     DVBS
    [DVBT2]
     DVBT
     DVBC/ANNEX_A
root@osmega:~# dvb-fe-tool -f 2 -d DVBT
Changing delivery system to: DVBT
root@osmega:~# dvb-fe-tool -f 2 | grep Supported -A5
Supported delivery systems:
     DVBS2
     DVBS
     DVBT2
    [DVBT]
     DVBC/ANNEX_A
root@osmega:~# dvb-fe-tool -f 2 -d DVBC/ANNEX_A
Changing delivery system to: DVBC/ANNEX_A
root@osmega:~# dvb-fe-tool -f 2 | grep Supported -A5
Supported delivery systems:
     DVBS2
     DVBS
     DVBT2
     DVBT
    [DVBC/ANNEX_A]
root@osmega:~#

[littlesat]

Mmmm then actually all tuners that find multiple system via delsys should be a multiple tuner... then we even do not need the proc check...

Edited by littlesat, 15 March 2019 - 00:26.

[WanWizard]

@Athoik,

 

I don't believe the C/T in the Solo4K is hotswitchable, i.e. C and T simultaneously available, so you can zap from a C to a T to a C channel and have them all work. And likewise for the Formuler 1 and a lot of other older C/T cards.

 

It would require enigma to change the delsys on every zap (on that tuner) to make that work, as there is only a single tuner available.

 

A multituner that is hotswitchable (in Littlesats context) is a tuner that has both delsys avaialable at the same time, like in your osmega example.

[littlesat]

Based on the information of WanWizard I did perform the AVL check... But when delsys says it can do multiple types (see post #155) there might be more tuners that can do it in an 'hotswitchable' way... and not 'coldswitchable'...

 

B.t.w. I tried to describe the difference that it can be switched 'on the run'...

 

And we still need to change some things regarding the naming.... (for the code itself I suggest HotSwitchable might be a good description)

 

MultiType (Tuner) are both tuners... but these one has as extra it can be done 'on the run' or -automatically- 

the other ones are 'fixed'....

 

Some Tries...

 

HotSwitchable (DVB-S2X + DVB-T2 + DVB-C + ATSC)

HotSwitchable (DVB-S2X-T2-C-ATSC)

Multi Type On the Run Multi (DVB-S2X-T2-C-ATSC)

Multi Modes Auto Switch (DVB-S2X-T2-C-ATSC)

Auto Switched (DVB-S2X-T2-C-ATSC)

AutoMode (DVB-S2X-T2-C-ATSC)

 

MultiType  (DVB-S2X + DVB-T2 + DVB-C + ATSC)

MultiType (DVB-S2X-T2-C-ATSC)

Fixed Switched (DVB-S2X-T2-C-ATSC)

FixedMode (DVB-S2X-T2-C-ATSC)

Edited by littlesat, 15 March 2019 - 11:49.

[athoik]

@Athoik,

 

I don't believe the C/T in the Solo4K is hotswitchable, i.e. C and T simultaneously available, so you can zap from a C to a T to a C channel and have them all work. And likewise for the Formuler 1 and a lot of other older C/T cards.

 

It would require enigma to change the delsys on every zap (on that tuner) to make that work, as there is only a single tuner available.

 

A multituner that is hotswitchable (in Littlesats context) is a tuner that has both delsys avaialable at the same time, like in your osmega example.

 

The osmega tuner can work in one mode at a time!

 

So if you are record on DVB-S and you try to switch to DVB-T, you should get channel unavailable (actually channels should be red, once you start using tuner).

 

The tuner of osmega can work in S or T or C but not in S+T or S+C or T+C.

 

It's a single tuner with multiple delsys.

 

I can't understand who ever said that this tuner is able to work in more than one modes.

 

If what I am explaining above is not clear, please let me know. I will give my best to explain it better.

Edited by athoik, 15 March 2019 - 13:55.

[WanWizard]

@littlesat,

 

No idea what you are on about.

 

Imho, you have three different types of tuner modules:

• Fixed tuner, only one delsys (like the traditional DVB-S or DVB-C modules)
• Fixed tuner, Multiple delsys (this is usually a DVB C/T modules, that an do either C or T but not both together, you need to switch the delsys, which is currently only done in tuner config)
• Dynamic tuner, multiple delsys (this can be a DVB C/T or DVB S/C/T, depending on the tuners on the module, all can be active simultaneously, no switch of delsys needed)

And only the last one I consider what you call hotswitchable.