Zitat von arki

aufnahmesperre noch aktiv

bei DM900?

kann ich bestätigen
bei mir ver 1.2r1-r0.1

Sep 18 19:59:11 dm7080 enigma2[190]: [InfoBar] quickSelectGlobal key:  red
Sep 18 19:59:11 dm7080 enigma2[190]: [InfoBar] exec InfoBar.startHbbtv(InfoBar.instance)
Sep 18 19:59:11 dm7080 enigma2[190]: [HbbTV].HbbTV.showRedButtonApplication
Sep 18 19:59:11 dm7080 enigma2[190]: [eHbbtv] Resolving Application Locator: dvb://current.ait/210.c
Sep 18 19:59:11 dm7080 enigma2[190]: [eHbbtv] We have 1 app(s) for service 3.3209.13202
Sep 18 19:59:11 dm7080 enigma2[190]: [eHbbtv] 'dvb://current.ait/210.c' resolved to 'http://dispatcher.hybridtv.cra.cz/tv/5784edc668ec31797e096524/index.html'
Sep 18 19:59:11 dm7080 enigma2[190]: allocating new converter!
Sep 18 19:59:11 dm7080 enigma2[190]: allocating new converter!
Sep 18 19:59:11 dm7080 enigma2[190]: allocating new converter!
Sep 18 19:59:11 dm7080 enigma2[190]: QtWebKit v5.6.2
Sep 18 19:59:11 dm7080 enigma2[190]: warning, skin is missing element green in <class 'Plugins.Extensions.Browser.Browser.Browser'>
Sep 18 19:59:11 dm7080 enigma2[190]: [Browser].__registerCallbacks
Sep 18 19:59:11 dm7080 enigma2[190]: [Browser].__restoreCookies ::: restoring 23 cookies
Sep 18 19:59:11 dm7080 enigma2[190]: event: event=6 data=(nil) data2=(nil)
Sep 18 19:59:11 dm7080 enigma2[190]: create buffer for widget 1920 x 1080
Sep 18 19:59:11 dm7080 enigma2[190]: event: event=1 data=0x7fd3c160 data2=(nil)
Sep 18 19:59:11 dm7080 enigma2[190]: [Browser].__onLoadProgress 100
Sep 18 19:59:11 dm7080 enigma2[190]: [eWebView::Private] delayedRepaint()
Sep 18 19:59:11 dm7080 enigma2[190]: [Browser].__onLoadFinished 1
Sep 18 19:59:11 dm7080 enigma2[190]: pageLoadFinished
Sep 18 19:59:11 dm7080 enigma2[190]: event: event=1 data=0x7fd3c160 data2=(nil)
Sep 18 19:59:12 dm7080 enigma2[190]: event: event=1 data=0x7fd3c160 data2=(nil)
Sep 18 19:59:12 dm7080 enigma2[190]: [Hbbtv].setVideoWindow x=0, y=0, w=1280, h=720
Sep 18 19:59:12 dm7080 enigma2[190]: [Hbbtv]._doSetVideoWindow x=0, y=0, w=1920, h=1080
Sep 18 19:59:12 dm7080 enigma2[190]: Looking for embedded skin
Sep 18 19:59:12 dm7080 enigma2[190]: not creating buffer for transparent widget 1920 x 1080
Sep 18 19:59:12 dm7080 enigma2[190]: [Hbbtv].setVideoWindow x=0, y=0, w=1280, h=720
Sep 18 19:59:12 dm7080 enigma2[190]: [Hbbtv]._doSetVideoWindow x=0, y=0, w=1920, h=1080
Sep 18 19:59:12 dm7080 enigma2[190]: event: event=1 data=0x7fd3c160 data2=(nil)
Sep 18 19:59:13 dm7080 enigma2[190]: event: event=1 data=0x7fd3c160 data2=(nil)
Sep 18 19:59:15 dm7080 enigma2[190]: no ancillary data in audio stream... abort radiotext pes parser
Sep 18 19:59:19 dm7080 enigma2[190]: [EPGC] cleanupOutdated
Sep 18 19:59:27 dm7080 enigma2[190]: action ->  ColorActions red
Sep 18 19:59:27 dm7080 enigma2[190]: navigate: 11
Sep 18 19:59:34 dm7080 enigma2[190]: nr_read 145068 nr_write 45052
Sep 18 19:59:34 dm7080 enigma2[190]: sum 190120 prev_sum 190120
Sep 18 19:59:34 dm7080 enigma2[190]: hdd IDLE!
Sep 18 19:59:34 dm7080 enigma2[190]: [IDLE] 31859.9416442 600 True
Sep 18 19:59:34 dm7080 enigma2[190]: action ->  BrowserActions exit

hast du exFAT probiert?
laut diese thread soll lengst funkzionieren
how i can use (OR INSTALL) exFAT FUSE Filesystem and Utils ?

probiermahl auch der disk label zum "hdd" (ohne klammern) ändern

schwer zu sagen in welche komponent es liegt
wenn es auch mit DMM image reproduzierbar ist dann wurde dem entwickler sicher ein log mit antwort helfen

kann sein es ist image bezogen
laut deine unterschrift ist auf deine box Merlin image.
Hast du es schon bei dem gemeldet?

I can recall him mentioning it in some reply, but I guess his setup was just one cable.
It might be that in the end it doesn't really matter if one or two cables.

The relations between the components must be possible to be entered and stored in the config and enigma needs to know how to work with it.

In my case I need to tell Enigma that on the cable 1 there is a rotor which needs to be used to move the dish to any satellite before all the tuners can tune to a channel on it.
It might even be that the config.Nims.x.sat.configMode=satposdepends option I tried would be the path to go.

I am aware of the vacation time, but I am checking this thread almost every day and am patiently waiting for Ghost stopping by and leave at least some comment.

enjoy the summer

Hi dhwz,
I would have used the GUI, but I am afraid the GUI is not ready for the kind of setup I am seeking for, that's why I did try to tweak the setting file manually.
As I explained this was just a desperate test, because nobody stopped by.
I do have a backup of vanilla setting file which I am using as a starting point and I have also a backup of via GUI completed tuner config.

Regarding the rotor config.
I maybe wasn't crystal clear in my previous descriptions, but I have bought just one new tuner, so my actual config is like this:
Tuner A1: BCM4506 (DVB-S2) - Positioner:USALS
Tuner A2: BCM4506 (DVB-S2) - advanced
Tuner B1: Si2169C (DVB-S2 / DVB-C / DVB-T2) - DVBS-2:advanced - DVB-T2:inactive - DVB-C:inactive
Tuner B2: Si2169C (DVB-S2 / DVB-C / DVB-T2) - DVBS-2:advanced - DVB-T2:inactive - DVB-C:inactive
Tuner C: (empty)

IMHO the new rotor speed setting don't apply when using the original tuner, or am I wrong?
There is even no GUI option for that on the old tuner.

thanks

PiGeon

Hi dhwz,
no reactions since 4 weeks so thanks for stopping by
I am doing desperate things to make my wife able to watch her favorite music channels

I guess the setting you have mentioned is there in the file, because I wasn't really brave enough to try to compile the file from scratch and just tried to modify it slightly.
If I am not wrong then it is this one:
config.Nims.0.turningSpeed=fast

Maybe you have been lost in the long posts, so here is the short version:

The dish moves quite fine, but only from 23.5 to 19.2 and resist to move back.
I guess because it thinks the 23.5 channels are still available on the other "unicable" tuners.
It isn't able to distinguish that there is just one LNB and that it moved together with the dish to 19.2.
So I am trying to find out how to teach it that the "unicable" tuners are connected to the same physical LNB as the first "positioner" tuner, just different output.

hope one of the devs will show up soon, I am ready to test their changes to the code

PiGeon

So I tried to add the following to the settings file

config.Nims.1.sat.configMode=satposdepends
config.Nims.2.sat.configMode=satposdepends
config.Nims.3.sat.configMode=satposdepends

it immediately fixed the issue with moving back to 23.5 while on 19.2, but I have lost the 3 unicable tuners
so it doesn't seem to be the right path, at least not without changes in the code, right?

I came also across following parameters

config.Nims.3.positionerExclusively=true
config.Nims.2.positionerExclusively=true

Can anybody please explain their purpose?

thanks

PiGeon

Zitat von juanito_perez

Happy Birthday edEIT!

edEIT wird heute zwei Jahre alt

Congratulations!
enjoy the party

PiGeon

So is this a dead end street when I am using the DM original image?

thanks for any comment

PiGeon

Any comment from the devs appreciated.

thanks

PiGeon

@antrabe
I am wondering if you have been able to achieve what you wanted and how.

I would like to achieve a similar thing.
I have one cable connected through a positioner to an Inverto LNB (normal output) and another cable leading to an unicable output of the very same LNB.
The positioner cable is connected to A1 tuner, the unicable cable is split into 2 cables and connected to A2 and B1 tuner.
B2 tuner is configured as "Connected to tuner B1"

Currently everything works as expected except one scenario. I am mainly watching channels on the 23.5E.
When I switch to a channel on 19.2E the dish moves there, but it resists to move back when changing to a channel on 23.5E satellite.

thanks

PiGeon

Today I chose a different approach.
I thought about teaching the unicable tuners that it should use rotor to move the dish by changing DiseqC mode to 1.2 on A2,B1 and B3 tuner.
But it didn't help either.

I am assuming telling the unicable tuner to use the diseqc 1.2 means that the diseqc command is sent through the unicable cable, which is not my case.

Anybody any idea?

thanks

PiGeon

Hi, just reporting that I moved further in my tests

Actual configuration:
Rotor cable - Tuner A1 – Positioner
Split. cable - Tuner A2 – Unicable 23.5E LNB1 SatCR 28 (2040MHz)
Split. cable - Tuner B1 – Unicable 23.5E LNB1 SCR1
w/o cable - Tuner B2 – Unicable 23.5E LNB1 SCR2 Connected to Tuner B1

There were no other satellites configured on the for Unicable configured tuners.

All the tuners are working fine, but I still was not able to convince the box to move back to 23.5
When I switch to some channel on 19.2 the dish moves OK.
But it resists to move to 23.5 when I switch to some 23.5 channel, it just says "Tune failed"
I have to make inactive all except the first tuner, to be able to move the dish back.

I did try to understand the behavior by comparing the settings file from various configurations. (see the excel file in the zip archive)
But there seems something to be still hidden to me.

I was assuming following:
nims.0 is equal to Tuner A1
nims.1 is equal to Tuner A2
nims.2 is equal to Tuner B1
nims.3 is equal to Tuner B2

Strangely all the .advanced.sat. lines were assigned to Nims.3 so I have replaced all the "config.Nims.3.advanced.sat." with "config.Nims.0.advanced.sat." thinking this is the thing which makes the box think that it doesn't need to move the dish.
But it didn't help either

I have also thought about configuring all the unicable LNBs as second cable of motorized LNB by adding
config.Nims.1.sat.configMode=satposdepends
config.Nims.2.sat.configMode=satposdepends
config.Nims.3.sat.configMode=satposdepends
but I am not sure if this would be enough.

Or are my thoughts totally wrong and I am in a dead end street, because it isn't possible to combine USALS with Unicable even on two different cables and the actual state of logic in the Enigma2 code doesn't allow this?

I am also wondering why there is still some unused garbage even after reboot.
For example following lines:
config.Nims.3.diseqcA=192
config.Nims.1.diseqcB=130
config.Nims.2.diseqcB=130
config.Nims.3.diseqcB=130
config.Nims.2.diseqcC=3601
config.Nims.3.diseqcC=3601
config.Nims.2.diseqcD=3601
config.Nims.3.diseqcD=3601
config.Nims.1.diseqcMode=diseqc_a_b
config.Nims.2.diseqcMode=diseqc_a_b
config.Nims.3.diseqcMode=diseqc_a_b

I think at least some of them are not used, I understand they might have been left there to be able to reuse them.
It would be great if they could have some prefix to be able to differentiate them from those which are really used.

Can somebody please help me to clean my last settings file? (settings.motor+3unicableOK_nims0.sat.txt)
I still think there could be some lines which block the dish movement.
I am afraid to delete it in a batch and it would take years to me to try remove one line after another.

thanks

PiGeon

I have just made a progress.
I have accidentally found the Unicable User defined option, and was able to configure it like this:
Split. cable - Tuner A1 – Unicable 23.5E LNB1 SatCR 19 (1680MHz)
w/o cable - Tuner A2 – Unicable 23.5E LNB1 SatCR 28 (2040MHz) Connected to Tuner A1
Split. cable - Tuner B1 – Unicable 23.5E LNB1 SCR1
w/o cable - Tuner B2 – Unicable 23.5E LNB1 SCR2 Connected to Tuner B1

Great!
This way I can use all the 4 tuners via 2 cables split from one unicable LNB output
So it seems there is something wrong in the Tuner config logic and/or the IDLB-QUDL42-UNI2L-1PP is not compatible with my IDLU-QUDL42-UNR2L-1PP LNB.

have a nice weekend

PiGeon

Hi to everyone!

My previous config
Tuner A1 – USALS – cable connected to motor from motor to first output of a twin LNB
Tuner A2 – second cable of motorized LNB – cable connected directly to second output of a twin LNB

My goal was to upgrade my box with the newest hybrid tuner and use unicable on the second cable split in to 3 cables to feed it.
We are watching mainly channels on 23.5E and 19.2, we rarely move the dish elsewhere, but I have decided to keep the first cable and motor to be able to move the dish to other satellites.

I have bought the following:
- Dreambox Triple 2x DVB-S2X / 1x DVB-C/T2 Tuner
- Inverto Unicable LNB IDLU-QUDL42-UNR2L-1PP http://www.inverto.tv/products/product.php?id=358
- 3way splitter

First I tried to connect it and configure it based only on intuition, but I failed, got GSD many times while in Satfinder trying if the tuners are able to tune.
I even had to restore once, because Enigma refused to start.

So, I went back to internet to gather some knowledge and finally have tried to achieve following config:
Tuner A1 – USALS – cable connected to motor from motor to first LNB output of the new Unicable LNB
Tuner A2 – Unicable 23.5E LNB1 SCR2 - one of the 3 split cables connected
Tuner B1 – Unicable 23.5E LNB1 SCR3 - one of the 3 split cables connected
Tuner B2 – Unicable 23.5E LNB1 SCR4 - one of the 3 split cables connected

But it seems not to be possible, the only SCR which could be stored is the SCR1 and 2. When I try to save SCR3 or 4 on it is reset back to SCR1.

So, I moved back to beginning and now I have just two of the unicable cables connected.
One is connected to the LNB1 input of the new hybrid tuner, which is configured the following way.
Tuner B1 – Unicable 23.5E LNB1 SCR1
Tuner B2 – Unicable 23.5E LNB1 SCR2 Connected to Tuner B1
The second cable is connected to the built-in tuner to the input A2, the tuners are configured as follows:
Tuner A1 – inactive (when enabled, I was able to move to 19.2, but it didn’t want to move back to 23.5)
Tuner A2 – Unicable 23.5E LNB1 SCR1 - one of the 3 split cables connected

But tuner A2 refuses to store SCR3 or 4 it always resets to SCR1 (see the Enigma log)

Note: I am using the IDLB-QUDL42-UNI2L-1PP in the config, it looks like a predecessor of the one I bought. Hopefully this is the right option.

I have also tried to understand the tuner config saved in the settings file, but it doesn’t make much sense to me, not in the current state. (see the attached file)

It would be great if someone can help me to achieve at least to configure astra 23.5 on all 4 tuners, so I can move forward and after that try to achieve my original goal.
Is my original goal USALS + Unicable possible at all?
Does anybody use such or similar config and wouldn’t mind to share his knowhow?

Thanks
PiGeon

It doesn't allow any rest to my mind.

First I thought the PGS subpicture is cropped from 1920:1080 to 1920:800 and so part of the subs is cut off.
However in the case of top placed subs I would expect the upper part of subs being cut of, but actually the bottom part of the subs is missing.

Additionally the sub height is squeezed so the whole PGS subpicture must have been squeezed from 1920:1080 to 1920:800.
But why then any parts of the subs is missing?

someone any idea how to explain it?

thanks

PiGeon

Hi Ghost,
can you please let me know if you had chance to look into it or at least if it is on your list?
I hope you could reproduce it.

Do you think the skin designers could help with it?

thanks and have a nice weekend

PiGeon

Zitat von mr_vica

oh sorry, I am using another image (Open* images), I didn´t mention it, thougt could be all the same in all images

never mind, It might be it would not help, the PGS subtitles may be handled differently.