Sundtek Support Forum
English => {Single, Dual, Quad} Sundtek SkyTV Ultimate => Thema gestartet von: Dima73 am Dezember 15, 2020, 09:28:14 Nachmittag
-
openPli 8.0 or VTI image/
Vu+solo4k/duo4k.
Visible only one tuner(not dual tuners).
openpli develop vusolo4k
vusolo4k login: root
Last login: Tue Dec 15 21:16:41 EET 2020 on pts/0
root@vusolo4k:~# /usr/sundtek/sun_dvb.sh info
--------------------------------------
DVB Tuner info
--------------------------------------
**** List of Media Hardware Devices ****
device 0: [MediaTV Digital Home III (EU)] DVB-C, DVB-T, DVB-T2
[INFO]:
STATUS: STANDBY
[BUS]:
ID: 3-1.2
[SERIAL]:
ID: U150511201402
[DVB-C,DVB-T,DVB-T2]:
FRONTEND: /dev/dvb/adapter1/frontend0
DVR: /dev/dvb/adapter1/dvr0
DMX: /dev/dvb/adapter1/demux0
device 1: [ Dual S2] DVB-S/S2, REMOTE-CONTROL, DVB-S/S2
[INFO]:
STATUS: STANDBY
[BUS]:
ID: 3-1.4
[SERIAL]:
ID: U201009191237
[DVB-S/S2]:
FESTATUS: ACTIVE
LNBVOLTAGE: DISABLED
LNBSUPPLY: USBPOWER
LNBSTATUS: OK
FRONTEND: /dev/dvb/adapter2/frontend0
DVR: /dev/dvb/adapter2/dvr0
DMX: /dev/dvb/adapter2/demux0
[REMOTECONTROL]:
INPUT0: /dev/mediainput0
[DVB-S/S2]:
FESTATUS: STANDBY
FRONTEND: /dev/dvb/adapter3/frontend0
DVR: /dev/dvb/adapter3/dvr0
DMX: /dev/dvb/adapter3/demux0
NIM Socket 0:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 0
NIM Socket 1:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 1
NIM Socket 2:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 2
NIM Socket 3:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 3
NIM Socket 4:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 4
NIM Socket 5:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 5
NIM Socket 6:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 6
NIM Socket 7:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 7
NIM Socket 8:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 8
I2C_Device: 4
NIM Socket 9:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 9
I2C_Device: 4
NIM Socket 10:
Type: DVB-T
Name: Sundtek DVB-T (III) (1/0) (USB):VTUNER
Frontend_Device: 10
NIM Socket 11:
Type: DVB-S2
Name: Sundtek DVB-S/S2 (VIII) (2/0) (USB):VTUNER
Frontend_Device: 11root@vusolo4k:~#
-
Does that single Tuner work?
/opt/bin/mediaclient --enabledreambox=/dev/dvb/adapterX/frontend0
I think the "Auto-registering" mode only recognises one tuner automatically, we'll change that shouldn't be hard to add support for multiple tuners there - thanks for spotting this.
-
Single tuner work fine.
openpli develop vusolo4k
vusolo4k login: root
root@vusolo4k:~# /opt/bin/mediaclient --enabledreambox=/dev/dvb/adapter2/frontend0
sending enable dreambox request for /dev/dvb/adapter2/frontend0
root@vusolo4k:~# /opt/bin/mediaclient --enabledreambox=/dev/dvb/adapter3/frontend0
sending enable dreambox request for /dev/dvb/adapter3/frontend0
root@vusolo4k:~# /usr/sundtek/sun_dvb.sh info
--------------------------------------
DVB Tuner info
--------------------------------------
**** List of Media Hardware Devices ****
device 0: [MediaTV Digital Home III (EU)] DVB-C, DVB-T, DVB-T2
[INFO]:
STATUS: STANDBY
[BUS]:
ID: 3-1.2
[SERIAL]:
ID: U150511201402
[DVB-C,DVB-T,DVB-T2]:
FRONTEND: /dev/dvb/adapter1/frontend0
DVR: /dev/dvb/adapter1/dvr0
DMX: /dev/dvb/adapter1/demux0
device 1: [ Dual S2] DVB-S/S2, REMOTE-CONTROL, DVB-S/S2
[INFO]:
STATUS: STANDBY
[BUS]:
ID: 3-1.4
[SERIAL]:
ID: U201009191237
[DVB-S/S2]:
FESTATUS: ACTIVE
LNBVOLTAGE: DISABLED
LNBSUPPLY: USBPOWER
LNBSTATUS: OK
FRONTEND: /dev/dvb/adapter2/frontend0
DVR: /dev/dvb/adapter2/dvr0
DMX: /dev/dvb/adapter2/demux0
[REMOTECONTROL]:
INPUT0: /dev/mediainput0
[DVB-S/S2]:
FESTATUS: STANDBY
FRONTEND: /dev/dvb/adapter3/frontend0
DVR: /dev/dvb/adapter3/dvr0
DMX: /dev/dvb/adapter3/demux0
NIM Socket 0:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 0
NIM Socket 1:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 1
NIM Socket 2:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 2
NIM Socket 3:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 3
NIM Socket 4:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 4
NIM Socket 5:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 5
NIM Socket 6:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 6
NIM Socket 7:
Type: DVB-S2
Name: Vuplus DVB-S NIM(7376 FBC)
Frontend_Device: 7
NIM Socket 8:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 8
I2C_Device: 4
NIM Socket 9:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 9
I2C_Device: 4
NIM Socket 10:
Type: DVB-T
Name: Sundtek DVB-T (III) (1/0) (USB):VTUNER
Frontend_Device: 10
NIM Socket 11:
Type: DVB-S2
Name: Sundtek DVB-S/S2 (VIII) (2/0) (USB):VTUNER
Frontend_Device: 11
NIM Socket 12:
Type: DVB-S2
Name: Sundtek DVB-S/S2 (VIII) (3/0) (USB):VTUNER
Frontend_Device: 12root@vusolo4k:~#
Now both work(visually, further tests needed).
-
Tested(sorry, a lot of work at the end of the year).
Second tuner - work fine same as first tuner.
/usr/sundtek/sun_dvb.sh add
case "$1" in
start_c)
....
if [ -e /etc/sundtek.conf ] && [ "`grep -c dreambox_support_fe1 /etc/sundtek.conf`" != "0" ]; then
echo `date +"%Y-%m-%d %H:%M:%S [$$]"`" Using /etc/sundtek.conf for deviceconfiguration" >> /var/log/mediasrv.log
+ $DRIVERPATH/mediaclient --enabledreambox=/dev/dvb/adapter3/frontend0
else
-
openpli develop vusolo4k
vusolo4k login: root
Last login: Sun Jan 3 18:53:42 EET 2021 on pts/0
root@vusolo4k:~# /opt/bin/mediaclient --build
Build date: 2020-12-29 12:32:30
I checked the new version, the same problems.
The second tuner is not recognized.
Need manual fix
case "$1" in
start_c)
....
if [ -e /etc/sundtek.conf ] && [ "`grep -c dreambox_support_fe1 /etc/sundtek.conf`" != "0" ]; then
echo `date +"%Y-%m-%d %H:%M:%S [$$]"`" Using /etc/sundtek.conf for deviceconfiguration" >> /var/log/mediasrv.log
+ $DRIVERPATH/mediaclient --enabledreambox=/dev/dvb/adapter3/frontend0
else
-
As far as I know that's just a workaround we will update the driver source for it soon.
-
Ok.Wait.
-
Hi Sundtek
Install new drivers
root@vusolo4k:~# /opt/bin/mediaclient --build
Build date: 2021-02-14 03:28:50
The second tuner is not auto recognized.
-
There is a problem.
SNR value always 91%.
Is it possible to make dynamic values, at least a little closer to reality?
-
The unit is not % it's in dB
By my experience if you have 91 it's pretty good.
There is no real range given in the Linux DVB API (and the value is returned by the chipset),
I'd prefer to keep it that way since various clients are using it that way for years already (the receiver part is the same as with the current single tuners which are available since 2018).
Also the values cannot be returned in a more accurate way than what the hardware returns (they might be transformed, but might loose accuracy by doing so).
So the application should better do that transformation.
-
It not dynamic values.
If this were the case, then I wrote the recalculation code in the enigma itself.
-
There are two options in enigma2.
"Force legacy signal stats"-->"If set to 'yes' signal values (SNR, etc) will be calculated from API V3. This is an old API version that has now been superseded." yes/no
1) https://github.com/OpenPLi/enigma2/blob/5af9063bdb4254368315f8969378b95b720aeaa3/lib/dvb/frontend.cpp#L1350
2)Manual recalculation https://github.com/OpenPLi/enigma2/blob/5af9063bdb4254368315f8969378b95b720aeaa3/lib/dvb/frontend.cpp#L940
-
it is a dynamic value, there's no hardcoded value in it. For good systems I usually see 89-91, but there are also worse 70.
You could probably crosscheck by adjusting the attenuation. The outcome can just alter the value given by the chipsets, it won't change anything else.
"Sundtek DVB-S/S2 (IV)" seems to do some recalculation.
-
Ok, I'll check everything again.
-
I checked that dynamic values work very badly.
I used was the VU+DVB-S dual tuner, so the calculation of the values is very accurate.
1)
VU+DVB-S dual tuner -->SNR 94%
Sundtek-->SNR 91%
2)
VU+DVB-S dual tuner -->SNR 64%
Sundtek-->SNR 90%
The value was very low and the picture on the HD channel began to freeze.
-
There are also other factors, you wrote the picture froze, on both tuners or what? Don't even take VU+ as a reference, things very much depend on the chipsets. Everything has its advantages and disadvantages.
SNR is only one factor, things are chipset and device dependent
-
There are also other factors, you wrote the picture froze, on both tuners or what?
yes
-
Is it possible to make dynamic values, at least a little closer to reality?
I checked that dynamic values work very badly.
I used was the VU+DVB-S dual tuner, so the calculation of the values is very accurate.
1)
VU+DVB-S dual tuner -->SNR 94%
Sundtek-->SNR 91%
2)
VU+DVB-S dual tuner -->SNR 64%
Sundtek-->SNR 90%
The value was very low and the picture on the HD channel began to freeze.
Any tuner should not report such high values in poor signal conditions(which can be simulated by misaligned dish or during the heavy rain)...
It also seems that yellow warning is present only when replying to topic:
Loading mixed (insecure) display content “http://support.sundtek.com/Smileys/default/smiley.gif” on a secure page ???
EDIT: or on any topic when such gifs are used!
-
Loop through
Is internal loopback("Loop through") possible between the two tuners A<->B?
-
dvbloopback:
--createadapter create dvb loopback device
--remove=[n] delete dvb loopback device
-
Solo 4K
Last drivers.
Connected together tuner SkyTV VIII dual / tuner Sundtek SkyTV Ultimate IV.
No signal on both tuners.
Remove Sundtek SkyTV Ultimate IV, reboot solo4K, SkyTV VIII dual no signal.
Unplug the power adapter SkyTV VIII dual temporarily,load solo4K, SkyTV VIII dual work fine.
---
Sundtek I just add the answer here, it must have been fixed for a long time already.