No I don't know how they calculate, but I can see values via e.g. webif at the same moment: I have connected both tuners to one converter with two outputs. 525 to B and Two to A and I earlier I had 525 connected to A and same result. My question is about displaying these values by Dreamboxes, not about calculating.

Ok, but it's the same converter so why older tuner has better precision. Even if it not exact signal, why there is a difference of displayed value?

I have DM 525 HD and now new DM Two UHD.

DM 525: 4.3.3r3-2021-10-29; image Experimental 2017-07-20

DM Two: 4.5.1r11-2021-10-29; image Experimental 2021-11-22

DM 525 has BCM73625 (G3) (DVB-S2) tuner where signal is displayed with 0.01 dB precision

DM Two has Si2166D (DVB-S2) where signal is displayed with 0.25 dB precision

e.g I have the same channel connected to both tuners (same dual converter) and first displays 14.17 dB (87%) and second 14.00 dB (87%)

I doubt older DM 525 tuner is better than new DM Two tuner

What is cause of such difference? Is this by design, software issue or my configuration issue?

Thanks for helping!

Thank you very much!

Hi

If I install new plugin it is always added under #1.

How can I change order of plugins under blue button menu?

Regards,

marrak

I will attach here: will Dreambox 520 HD, 525 HD, 900 HD and 920 HD get firmware updates yet or 4.3.2r5 is last?

Thank you everybody! I finally have written own python script with enigma2 web api requests, works as needed using cron. I can share it via PM.

Swiss-MAD HD channel has 8dB on 120cm, and SD version 15dB on 80cm Both are located on other position and I can't mount bigger dish.

dre Thanks I will try it

Anyway to be more clear - I'm looking for any software solution - writting own timer plugin or python script to check signal and deactivate/activate timer on demand. Help needed if this is possible?

I'm looking for any help how to do that.

I have cyclic timer scheduled on HD channel, but sometimes if bad weather there is no signal there.

I would like to record SD version then. Could anyone propose any solution?

Thank you

I have Dreambox 525HD with tuner BCM73625 (G3) (DVB-S2), OS 4.3.2r4-2019-02-19, Image: Experimental 2.5
I have DiSEqC 8/1 and receiving several satellites e.g 7E, 9E and 27.5W, etc.
I notice a issue I hope someone here reproduce and could fix

When I scan (or even switch in built-in signal checker) transponder on 9E:

<transponder frequency="12111000" symbol_rate="31400000" polarization="1" fec_inner="0" system="1" modulation="2" />

I immediately lost signal on some other transponders e.g.
7E:

<transponder frequency="10803750" symbol_rate="30000000" polarization="1" fec_inner="4" system="1" modulation="1" />

27.5W:

<transponder frequency="11495000" symbol_rate="44100000" polarization="1" fec_inner="9" system="1" modulation="1" />

I know this transponder on 9E is empty and completly useful for me but it is downloaded by auto update tool into satellites.xml before my weekly full rescan so it's really annoing as only solution then to restore signal is restart box

I can provide enigma logs or other data if necessarily.
Thank you for help.

@dhwz - no AFN does not use DES as you wrote. There are other services e.g on 4.8E and 15W using DES. I guess they are legal in dedicated boxes but not for public purposes. (hotels, markets promo etc.)
However you can buy occasional cards which decode stuff on ebay etc. just for DX hobby
Maybe was it deliberate to break non-commercial solution by Dreambox? Nevermind. I agree and accept you do not have to support it but it would be nice since it worked earlier on your boxex and familiar companies support it.

Zitat von djmastera2000

You only get support here for scrambled channels that work with a CI-Module(not CI+).

DM520 doesn't have a CI built-in...

Dear Dreambox support
the same issue on DM525 which have CI build-in... and the same firmware I guess
In fact it's not only PowerVu issue. The same is on legal card, which I have, using other DES encripted system.
It's your firmware issue as it works well on older Dreambox models which I have too.

@LookAtMe can you write what you expect from box for €150 ? And what exactly is below your expectations?
I have DM 525 HD which is identical plus CI slot and cannot catch that bad opinion. I have 10000+ channels from 12 satellites and do not see reliable issues works fast enough! Receiving feeds as well, no issue at all.
Every software issue I found was resolved (or at least workaround) here. Maybe one issue with black screen while switching from DES to AES on this box is annoying. Everything else works fantastic for me and I also had many others boxes in my hands. I did not see better box in that price.

Thank you, with that feature it realy fixed my time!

Still hope some Dreambox developer will look at my update in #post198652 and fix main issue

@gutemine Thank you once again - I've just switch to not use transponders time as you recomended, but I hope it's only workaround and someone can fix this issue Maybe @dhwz will look at it again with my latest update.

Back to ntp: it looks (in journal enigma2 log) that TimeHandler do not catch time from transponders now what it's better but I set ntp to auto, restart dreambox (not hard reset) and waiting about 1 hour now and time is not changed to correct (network is ok) - still 30 min ahead. How often ntp should update time? I do not see any messages related to ntp in jounal log too.

It takes me some time to find it but I've finally got it . DM time changed 30 min ahead but it shouldn't as it's wrong transponder time!

sie 26 20:15:05 dm520 enigma2[190]: [eDVBLocalTimeHandler] Receiver time is 'Sun Aug 26 20:15:05 2018'
sie 26 20:15:05 dm520 enigma2[190]: [eDVBLocalTimeHandler] Transponder time is 'Sun Aug 26 20:50:45 2018'
sie 26 20:15:05 dm520 enigma2[190]: [eDVBLocalTimeHandler] diff is 2140
sie 26 20:15:05 dm520 enigma2[190]: [eDVBLocalTimeHandler] we have correction -228
sie 26 20:15:05 dm520 enigma2[190]: [eDVBLocalTimeHandler] diff after add correction is 1912
sie 26 20:15:05 dm520 enigma2[190]: [eDVBLocalTimeHandler] use stored correction(<5 min)
sie 26 20:46:57 dm520 enigma2[190]: [eDVBLocalTimeHandler] update RTC
sie 26 20:46:57 dm520 enigma2[190]: [eDVBLocalTimeHandler] time_difference is 1912
sie 26 20:46:57 dm520 enigma2[190]: [eDVBLocalTimeHandler] update Linux Time

I think it's correction issue if there is no exception of earlier explanations for correction > 5 min. Please explain or fix it
I can provide full journal log if necessery, but I guess above code contains a clue.
Thaank you.

My problem is: when I search channels on my Dreambox 12 satellites there are many radio and data channels found as well. I would like to remove quick every new Radio and Data which are not interesting for me then.
Now I have to filter by Radio, delete and again filter by Data and delete. It's not a big issue but only useful feature, but I guess easy to implement

Tkank you for that tool
Is there possible to add in types filter - "Data & Radio" item? I would be very grateful
Regards

Zitat von gutemine

first the .value was just a cut and paste error from e2 python code and second you have to stop e2 with systemctl stop enigma2 before editing or e2 will overwrite it from his cache when restarting next and hence never use it.

Sure, thx I will try it next time

Zitat von dhwz

Ok seems you didn't understand. It doesn't sync time at all if the difference is larger than 5 minutes.Not to future and not to the past...
It's just not possible that it sync a time with 20min difference. Maybe you switched to different transponders which all had a offset <+5min. Which results in increasing again and again.

I can't provide log because it looks they fixed time on 9E transponder a moment ago but I will track this issue and try to catch E2 logs while time is changing since I notice this problem myself from time to time.
I'm pretty sure it's not true (about <5 min) or someting else caouses bigger resync because I had many time even bigger time resync e.g. about a day(!) so what I would have to do to achive that

So, for now thank you for your help. Please do not close this thread as I will looking for more details of this problem.

Thank you for response.

Zitat von dhwz

That's not a bug but expected behaviour. It's not accepting time sync if the diff is too high (>5min) to the current system time.
And E2 is not syncing time if it is 20min out of sync in future.

Ok, but why E2 allows to resync time > 5min?
So its a feature to have resync time and can't sync it? I hope not

Zitat von gutemine

If you want to use ONLY NTP then NTP on/off will be useless until you put use Transponder time Setting to false

config.misc.useTransponderTime.value=false

... Maybe ... somebody ... could produce a small patch so that you can choose there on/off/only and then both (!) Parameters are set correctly

This would be only 3 lines of Code and would save us a lot of time not to explain this all over again and again ...

Alles anzeigen

I was trying this earlier too
config.misc.useTransponderTime.value=false and config.misc.useTransponderTime=false

I thought the second one which was mention earlier here when I search is correct, but nevermind. I put both via shell vim editor (plus ntp on) and nothing happend, so how long I should wait? or maybe something else? I even restarted DM and sadly then in /etc/enigma2/settings both lines were removed The same if I sending it via DreamboxEdit, these lines never even can be see in setting file. Please corect me if I doing something wrong