51 replies to this topic

[Dimitrij]

 

BTW: restarting enigma can make a big difference for the tuner abilities. Often I could only record in parallel form one transponder (not even a sat pos.)

Simple.

Not need restart enigma.

Zap another transponder/sat after edit tuner setup.

 

 

 

While I was testing I realized that restarting Enigma automatically disables terrestrial tuner J (no big deal for me fortunately) so that only tuner I works after a restart... what the hell is going on there?

Please answer in telnet after restart enigma when tuner J is disabled.

cat /proc/bus/nim_sockets

 

Edited by Dimitrij, 20 June 2023 - 11:04.

[WanWizard]

 

So, it seems that I understood something.

This Unicable II IDLU-UWT110-CUO1O-32P 5/32 allows you to use 2 wideband LNBs with different satellites at the same time.

Then it's my mistake.

Needs to be sec.cpp fixed

 

Why is that? What does this fix?

 

There is no diseqc in use when you use Unicable, and multiple sat positions works fine, I have 4 of them on one cable.

[Dimitrij]

Why is that? What does this fix?

As far as I can see in the code, and I checked it virtually myself, it is impossible to select another satellite (gray channels in the list) if the first satellite is busy.

Edited by Dimitrij, 20 June 2023 - 13:55.

[WanWizard]

Not sure I understand what you mean.

 

I have two Unicable switches in use, each with multiple LNB's. Never had any issue, not in configuration, not in daily use.

 

From what I read the TS has two IDLU-UWT110-CUO1O-32P switches, each with two wideband LNBs (so each switch provides 2 positions), and a combiner to connect the two switches to the same cable.

 

This requires correct switch programming where either the first switch uses UB 1-16, and the second uses UB 17-32,  or the second switch needs to be explicitly programmed to respond only to position 3 and 4.

 

If this hasn't been done (properly), the setup will not work.

 

The programmers manual states:

 

It is also possible connect (chain) the outputs of two switches together with a RF combiner and
setup one switch to provide the signal from satellite A and B and the seconds one from satellite
C and D. It means that if a STB request a channel from satellite A or B, the first switch will enable
the user band and the seconds switch will disable the user band. If the STB then request a channel
from satellite C or D, the first switch will deactivate the user band and the seconds switch will
provide the user band.

 

It doesn't look like done using manual switches (like Jultec does), but through programming.

[Dimitrij]

We are talking about the FBC, where one cable is used(tuner A), the rest of the tuners(tuner B/C/D etc..) is connected via an internal loop.

Watch TV on one satellite, record on another satellite at the same time.

Edited by Dimitrij, 20 June 2023 - 16:03.

[WanWizard]

Yes.

 

And I do that on a daily basis, quite often 6 or more parallel recordings.

 

My Duo 4K has two FBC tuners, each only having a cable on the first input, connected to 2 Unicable switches having 4 LNB's. Setup exacly like you posted in #16, only for different positions (13/19/23/28). See also my screenshots in #3.

 

No issues whatsoever.

Edited by WanWizard, 20 June 2023 - 18:02.

[Dimitrij]

WanWizard

 

There was one small mistake, here it(post №20) is confirmed:

 

So I thought what about the Preferred Tuner configuration in System>Customize. I changed Preferred tuner DVB-S to A. No difference.

 

Then I changed Preferred tuner DVB-S to tuner B, AND BANG!!!! Recording from all sats with all tuners works perfectly!!!

 

 

 

[sec] fixed linked compare tuner data if used unicable multiswitch

 

 

 

 

Now we need to fix some kind of mistake with DVB-T

 

 

While I was testing I realized that restarting Enigma automatically disables terrestrial tuner J (no big deal for me fortunately) so that only tuner I works after a restart... what the hell is going on there?

Edited by Dimitrij, 20 June 2023 - 18:27.

[WanWizard]

Why would you set a preferred tuner if you have 8 (or 16)? And why would there be a problem if A is preferred, but not if B is preferred? Is the fix related to that?

 

And I'm just trying to understand what this does, because "is_unicable" and "diseqc" are mutually exclusive, it is one or the other, never both?

[Dimitrij]

 

And I'm just trying to understand what this does, because "is_unicable" and "diseqc" are mutually exclusive, it is one or the other, never both?

Example:
Tuner A --> FBC DVB-S root
DiSEqC 1.0 --> port A --> sat 19.2E /port B  --> sat 13E Unicable

Tuner C --> FBC DVB-S list
advanced mode --> sat 13E Unicable --> port B --> connected tuner A

Tuner D --> FBC DVB-S list
advanced mode --> sat 13E Unicable --> port B --> connected tuner A

Situation:
Zap to service 13E --> use tuner A
Play as PiP other service 13E -->use tuner C
Zap to service 19.2E --> use tuner A

A unique sight!
PiP(13E) and live tv(19.2E)  work one second at a time.

Same DiSEqC!

Edited by Dimitrij, 20 June 2023 - 20:33.

[kwax]

cat /proc/bus/nim_sockets

NIM Socket 0:

        Type: DVB-S2X

        Name: Vuplus DVB-S NIM(45308X FBC)

        Frontend_Device: 0

NIM Socket 1:

        Type: DVB-S2X

        Name: Vuplus DVB-S NIM(45308X FBC)

        Frontend_Device: 1

NIM Socket 2:

        Type: DVB-S2X

        Name: Vuplus DVB-S NIM(45308X FBC)

        Frontend_Device: 2

NIM Socket 3:

        Type: DVB-S2X

        Name: Vuplus DVB-S NIM(45308X FBC)

        Frontend_Device: 3

NIM Socket 4:

        Type: DVB-S2X

        Name: Vuplus DVB-S NIM(45308X FBC)

        Frontend_Device: 4

NIM Socket 5:

        Type: DVB-S2X

        Name: Vuplus DVB-S NIM(45308X FBC)

        Frontend_Device: 5

NIM Socket 6:

        Type: DVB-S2X

        Name: Vuplus DVB-S NIM(45308X FBC)

        Frontend_Device: 6

NIM Socket 7:

        Type: DVB-S2X

        Name: Vuplus DVB-S NIM(45308X FBC)

        Frontend_Device: 7

NIM Socket 8:

        Type: DVB-T2

        Name: Vuplus DVB-T NIM(BCM3466)

        Mode 0: DVB-T2

        Mode 1: DVB-C

        Frontend_Device: 8

        I2C_Device: 4

NIM Socket 9:

        Type: DVB-T2

        Name: Vuplus DVB-T NIM(BCM3466)

        Mode 0: DVB-T2

        Mode 1: DVB-C

        Frontend_Device: 9

        I2C_Device: 4

[WanWizard]

Tuner A --> FBC DVB-S root
DiSEqC 1.0 --> port A --> sat 19.2E /port B --> sat 13E Unicable

 

Ah, off course.

 

Didn't enter my mind that someone with Unicable could have a second dish with a DiseqC switch...

[Dimitrij]

kwax

Can you post screenshots of the I/J tuners settings before and after restarting Enigma?

and https://wiki.openpli...ebugging_Enigma

 

I have the same tuner, I'll check it out tonight.

 

 

P.S.

And your problem with the required priority of Tuner B should now be fixed.

It will be necessary to update the software (image develop) after the new build.

 

Edited by Dimitrij, 21 June 2023 - 05:54.

[Dimitrij]

kwax

please show file /etc/enigma2/settings

[kwax]

 

kwax

Can you post screenshots of the I/J tuners settings before and after restarting Enigma?

and https://wiki.openpli...ebugging_Enigma

 

I have the same tuner, I'll check it out tonight.

 

 

P.S.

And your problem with the required priority of Tuner B should now be fixed.

It will be necessary to update the software (image develop) after the new build.

 

 

 

Really weird: Terrestrial tuner J shows as disabled as you can see in the screenshot (and cannot be used for tuning). BUT: If I click on the tuner it shows as active (see other screenshot).

 

If I exit tuner J (WITH EXIT, NOT SAVE!) from there, it shows upp as active in the list and can be used for tuning. Until next restart...

Attached Files

•  Vu5.jpg   61.98KB   0 downloads
•  Vu6.jpg   33.12KB   0 downloads

[kwax]

kwax

please show file /etc/enigma2/settings

 

Error You aren't permitted to upload this kind of file 

 

Added txt extension...

Attached Files

•  settings.txt   14.45KB   4 downloads

[kwax]

BTW: I have an older VU+ Duo4k (non SE) in another location with the same internal terrestrial tuner and identical sat positions (but DiseqC dish setup) and tuner I and J always show up.

[Dimitrij]

init 4

remove line

config.Nims.8.diseqcA=282
config.Nims.8.diseqcB=3592
config.Nims.8.diseqcC=130
config.Nims.8.diseqcD=192
config.Nims.8.diseqcMode=diseqc_a_b_c_d
config.Nims.8.terrestrial=Scandinavia (Europe DVB-T/T2)
config.Nims.9.configMode=equal
config.Nims.9.connectedTo=8
config.Nims.9.terrestrial=Scandinavia (Europe DVB-T/T2)

init 3

reconfigure the DVB-T tuners

Edited by Dimitrij, 22 June 2023 - 05:39.

[Dimitrij]

Problem in old sat config  when use DVB-S tuner

config.Nims.9.configMode=equal

Edited by Dimitrij, 22 June 2023 - 05:41.

[kwax]

Problem in old sat config  when use DVB-S tuner

config.Nims.9.configMode=equal

 

Ok, thanks! Will try.

[kwax]

Ok, guys everything seems to work great now. Thanks for sorting all the issues out pretty quickly!

 

Tuner J stays active and it is possibly to record/PIP from all sats and tuners in parallel.

Edited by kwax, 24 June 2023 - 21:49.