Sundtek Support Forum
English => VU+ - VU Duo Settopbox => Thema gestartet von: tappari am Februar 07, 2014, 10:20:35 Vormittag
-
I have tested this stick in VU+ Duo2, VU+ Ultimo, Dreambox 8000HD and DM800HD, but in none of these STB:s there is T2 function. Only T. So please stop advertising this model as suitable USB-T2 tuner for T2 use in STB:s.
-
We told you to contact us via Skype, those Models and the driver supports DVB-T2.
http://wiki.sundtek.de/index.php/Mediaclient#Tuning_DVB-T2
Other ones usually get back to us and we solve or at least analyze possible issues.
-
It was Sundtek that promised to come back with this issue when having enough of time. Normally it is on suppliers responsibility to guarantee the operation, not customers.
-
Well you have the choice:
Find another Manufacturer who will give you direct support (and I can guarantee that any other manufacturer is scared to touch such systems)
or
Try to work with us, and find a solution for your issue.
-
sO IS IT UP TO ME
So is it up to me to make Your product to do what You have promised?
-
Normally I see it is on suppliers responsibility to see if the product is operating as promised. Not customers.
-
We are not going to struggle with you, you have the choice either try to cowork with us or ship it back.
The time you are spending on writing those posts might be enough to fix your issue.
The entire Settopbox Support was made that way, customers asking if we could support their boxes and we tried to help them, and there was a lot experimenting involved. The same with supporting several routers and other systems.
-
It is not the question if I want to co-operate or not. I would like to co-operate, but I`m waiting for Your activivities to do something.
-
I think we tried to contact you through skype/chat earlier already, but also no response. Our Skype account always shows away that's normal.
We have several settopboxes here but eg no DM8000, no VU+ Ultimo and no DM800HD (we only have the DM800HD SE and VU+ duo 2)
We have prepared some updates, but would like to see the output on your side.
All those boxes which you have use slightly different Enigma versions.
So once you have some time get back to us via Skype chat and we can give it a go.
-
There are some Tuner Startscripts in /usr/script
DVB_T2_Tuner_autostart.sh <- autostart on reboot
DVB_T2_Tuner_starten.sh <- start immediately (should only be run from console)
-
Sundtek Control Center/Info-button says:
[DVB-T2]
FRONTEND: /dev/dvb/adapter1/frontend0
DVR: /dev/dvb/adapter1/dvr0
DMX: /dev/dvb/adapter1/demux0
But in Dreambox Control Center FTP /dev/dvb/adapter0
No adapter1
This is in VU+Ultimo, but same situation with other STB`s.
-
Start the DVB-T2 Script in /usr/script
The Sundtek Controlcenter still needs some update it doesn't include DVB-T2 yet.
Our driver does not register /dev/dvb/adapterN on Settopboxes because it is not needed.
cat /proc/bus/nim_sockets shows up the registered tuners.
-
There is no /cat directory in STB`s.
-
And /proc/bus/nim_sockets is empty
-
Seems like you need some howto with pictures, I'll do that a little bit later.
-
Welcome to OpenViX for vuultimo
openvix 3.0 vuultimo
root@vuultimo:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-T
Name: Vuplus DVB-T NIM(CXD1978)
Mode 0: DVB-C
Mode 1: DVB-T
Frontend_Device: 0
I2C_Device: 2
NIM Socket 1:
Type: DVB-T
Name: Vuplus DVB-T NIM(CXD1978)
Mode 0: DVB-C
Mode 1: DVB-T
Frontend_Device: 1
I2C_Device: 3
NIM Socket 2:
Type: DVB-T
Name: Vuplus DVB-T NIM(CXD1978)
Mode 0: DVB-C
Mode 1: DVB-T
Frontend_Device: 2
I2C_Device: 1
NIM Socket 3:
Type: DVB-T
Name: MediaTV Digital Home III (EU) (UDVB-T
Frontend_Device: 3root@vuultimo:~#
-
almost correct, but you need to run the DVB-T2 scripts.
I guess the Control Center will be updated tomorrow to support T2 as well to make it more comfortable.
-
After running scripts:
Welcome to OpenViX for vuultimo
openvix 3.0 vuultimo
root@vuultimo:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-T
Name: Vuplus DVB-T NIM(CXD1978)
Mode 0: DVB-C
Mode 1: DVB-T
Frontend_Device: 0
I2C_Device: 2
NIM Socket 1:
Type: DVB-T
Name: Vuplus DVB-T NIM(CXD1978)
Mode 0: DVB-C
Mode 1: DVB-T
Frontend_Device: 1
I2C_Device: 3
NIM Socket 2:
Type: DVB-T
Name: Vuplus DVB-T NIM(CXD1978)
Mode 0: DVB-C
Mode 1: DVB-T
Frontend_Device: 2
I2C_Device: 1
NIM Socket 3:
Type: DVB-T2
Name: MediaTV Digital Home III (EU) (UDVB-T2
Frontend_Device: 3root@vuultimo:~#
But no T2 function.
-
You are correct, seems like some images still need some updates (but this is not something we can update in our driver).
VTI does not support DVB-T2 via USB
OpenPLI also has some issue displaying it, OpenPLI allows to scan DVB-T2 transponders
Black Hole image allows to scan and watch DVB-T2 channels
-
I confirm that it does operate in T2 mode with BlackHole image.
-
OpenPLI also works now. They needed a driver workaround to get it work.
-
Also OpenViX operates with your latest drivers. Fantastic. Thank you Sundtek!
-
For me also shows T
openpli 4 et9x00
et9x00 login: root
root@et9x00:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2
Name: AVL2108
Has_Outputs: yes
Frontend_Device: 0
I2C_Device: 2
NIM Socket 1:
Type: DVB-S2
Name: AVL2108
Has_Outputs: yes
Frontend_Device: 1
I2C_Device: 3
NIM Socket 2:
Type: DVB-T
Name: MediaTV Digital Home III (EU) (USB)
Has_Outputs: no
Frontend_Device: 2
I2C_Device: -1
root@et9x00:~#
-
Can you try the new installer:
(http://sundtek.de/images/settopbox_installer_feb2014.jpg)
http://sundtek.de/media/ssi.rar
-
It shows correct now.
openpli 4 et9x00
et9x00 login: root
root@et9x00:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2
Name: AVL2108
Has_Outputs: yes
Frontend_Device: 0
I2C_Device: 2
NIM Socket 1:
Type: DVB-S2
Name: AVL2108
Has_Outputs: yes
Frontend_Device: 1
I2C_Device: 3
NIM Socket 2:
Type: DVB-T2
Name: MediaTV Digital Home III (EU) (USB)
Has_Outputs: no
Frontend_Device: 2
I2C_Device: -1
root@et9x00:~#
-
Does DVB-T2 work for you? You would be the first one using an XTrend STB with our device.
-
This stick operates very clever way in my Ultimo. If I set preferred tuner to auto, Ultimo uses A-tuner for DVB-T SD-channels, but when I go to T2 HD channels, it automatically switches to tuner D which is Sundtek. But in DUO2 this does not happen. I have to set Sundtek (tuner C) as preferred tuner. Both boxes have OpenViX version 808 and latest VU+ drivers.
-
I can't test that. In the netherlands broadcasting is only T
Does DVB-T2 work for you? You would be the first one using an XTrend STB with our device.
-
Hi.
I am trying to get DVB-T2 to work with my Vu+ Duo2 and a Sundtek MediaTV Digital Home III dvb-c/t/t2 usb tuner.
The duo2 is equipped with 4 internal DVB-S2 tuners (2 dual tuners) and one usb MediaTV Digital Home III tuner. I have BlackHole 2.1.5 installed. The usb drivers in the duo2 is installed with Sundtek Software Installer. The usb tuner is configured as dvb-t2 in Sundtek Control Center.
If I search for terrestrial channels which are dvb-t and choose dvb-t as search setting, the usb tuner discovers channels and I am able to watch those channels on the duo2. If I try to search for dvb-t2 channels and choose dvb-t2 or dvb-t as search settings, nothing is found on the dvb-t2 frequency.
If I list the available tuners in the duo2 I get this:
root@vuduo2:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 0
I2C_Device: 2
NIM Socket 1:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 1
I2C_Device: 2
NIM Socket 2:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 2
I2C_Device: 4
NIM Socket 3:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 3
I2C_Device: 4
NIM Socket 4:
Type: DVB-T2
Name: Sundtek DVB-T2 (III) (0/0) (USB)DVB-T2
Frontend_Device: 4root@vuduo2:~#
NIM Socket 4 has not complete information. Does this indicate problems with the usb tuner?
-
Use DVB-T and not DVB-T2 in the settings.
DVB-T2 is tunneled through DVB-T with those tuners, the DVB-T2 setting requires exact transponder informations - while in "DVB-T" Mode most transponder settings are discovered automatically.
The incomplete settings are ok -- this is not related to our driver but to the VU+ broadcom interface drivers (so we cannot change anything there anyway)
-
Thanks for your answer.
Don't know exactly which setting you mean but I have tried two things.
First attempt
Setting in Sundtek Control Center: dvb-t2
Manual search on frequency which contains dvb-t2 channels with dvb-t as search setting.
Result: Nothing found
Second attempt
Setting in Sundtek Control Center: dvb-t
Manual search on frequency which contains dvb-t2 channels with dvb-t as search setting.
Result: Nothing found
Any suggestions what's wrong?
-
Try following on the console:
/opt/bin/mediaclient -D DVBT -d /dev/dvb/adapter1/frontend0
/opt/bin/mediaclient --blindscan /dev/dvb/adapter1/frontend0
this should give you a list of transponder frequencies which you are able to receive.
If you are missing channels try to adjust the antenna.
-
I get 12 frequencies but not the frequency which is broadcasting in dvb-t2.
If I connect a new LCD TV which is DVB-T2 compatible to the antenna, I perfectly fine receive channels on the dvb-t2 frequency.
If I swap usb tuner and connect a PCTV nanostick 290e usb stick to the same vuduo2 I perfectly fine find the DVB-T2 channels if I search and I can also watch them with no problem.
If I then try to watch the dvb-t2 channels with the sundtek usb tuner on my duo2 (channel search done by pctv 290e), I can't get any picture.
(When I test I only have one usb tuner connected.)
Bug in drivers? Problem with hardware?
-
No there's no driver issue with those devices, try to adjust the antenna?
I'm not aware of any issue with DVB-T2.
You might doublecheck it with Windows, however Win&Linux are using the same drivers but maybe you'll get some different result who knows.
-
If I try to watch a dvb-t2 channel with the sundtek usb tuner on the duo2 I get 57 % in SNR level. So the tuner detects there something on the frequency, but I get black picture. 57 % don't seem much but if a watch a dvb-t channel I only have 37 % in SNR and no pixelation in picture. It seems that the sundtek tuner gives very low SNR values in Black Hole.
I have also tried the tuner in Windows/MediaPortal with same result. No picture on dvb-t2 channels but on dvb-t channels I get picture.
Can it be some tuning parameters that isn't handled correctly in the drivers?
-
No definitely not we have several customers all over Europe using DVB-T and T2 for quite some time already.
My guess is still that you might have to adjust the antenna or add an extra amplifier to it (usually that's not required, but possibly the frequencies really have a too low signal strength in your area).
T2 has been confirmed to work by our engineer in Germany, UK, Sweden, Finland, Norway, Ireland, Italy...
Also the sensitivity has been checked it is within a normal range, it can only be improved a little bit by adding some additional amplifier.
-
If the signal strength is to low, how come it works directly in my lcd tv and with the pctv nanostick 290e?
-
Maybe the LNA of the 290e helps you, TV sets are bigger and definitely have more space for additional amplifiers, who knows how stable everything will be over some time.
However the signal must be really low on your side the only way out would be a better Antenna then.
We do not experience any issue with DVB-T2 on our side.
You are really the first one having such an issue, I would focus on adjusting the Antenna, or using a better one then.
-
You might try to use this command to tune manually to DVB-T2:
/opt/bin/mediaclient -m DVBT2 -f 642000000 -b 8
Using device: /dev/dvb/adapter0/frontend0
Tuning to DVB-T2 channel
Checking for lock:
. [LOCKED]
(just tested with our old and our new units, this is the current test transponder in Berlin - and I usually do not have a good signal either at my place with any device nor with the TV)
or:
/opt/bin/mediaclient -D DVBT2
/opt/bin/mediaclient --blindscan /dev/dvb/adapter0/frontend0
This will be more intensive.
-
I have tried out the command to manually tune DVBT2 and the command to blindscan DVBT2. No luck on either commands.
If no one has any other suggestions what to try, I will move the vu+ to a friends house which is equipped with a newly bought roof antenna. If the usb tuner can't find DVB-T2 channels there either, my antenna can't be the source of the problem.
Thanks for your help so far. Will report back my results.
-
The problem with dvb-t2 and Sundtek MediaTV Digital Home III is related to the driver.
I had no luck with dvb-t2 at my friends house either, so then I tested the oldest driver from your download page. And with that driver both dvb-t and dvb-t2 worked as it should.
Then I tested a selection of linux drivers to figure out which work with dvb-t2 and which drivers don't work with dvb-t2.
All linux drivers, of those I tested, including sundtek_installer_150224.045219 and older work with dvb-t2.
All linux drivers, of those I tested, including sundtek_installer_150228.114609 and newer don't work with dvb-t2.
Can you please correct the code in the drivers so that a any new driver you release will work with both dvb-t and dvb-t2 frequencies.
-
Hi,
I don't see that there has been any change related to DVB-T2 during that time, according to our changelog we updated the ATSC driver during that time.
Also since DVB-T2 works for us this would be more than strange.
It would help if you could demonstrate the issue on your side while an engineer has a look at it via remote desktop.
Can you contact us via Skype (sundtek) or Chat (http://chat.sundtek.de)
Skype is preferred (the chat is not always occupied).