Sundtek Support Forum
English => Sundtek MediaTV Pro (Europe) => Thema gestartet von: Sundtek am August 11, 2010, 04:20:08 Nachmittag
-
In order to set install the driver on Settopboxes we provide some easy tools for Windows and Mac.
All you need is the ip address and the password (if set) of your settopbox.
(http://sundtek.de/images/settopbox_installer_feb2014.jpg)
Documentation:
http://sundtek.de/support/Sundtek_MediaTV_setting_guide.pdf
Windows:
http://sundtek.de/media/ssi.zip
Mac:
http://sundtek.de/media/ssi_mac.zip
-
This howto is for people who want to use more than 1 USB DVB Sticks
In order to set up more than 1 USB DVB-C Stick please use following commands:
root@bm750:~# /opt/bin/mediaclient -e
**** List of Media Hardware Devices ****
device 0: [Sundtek SkyTV Ultimate] DVB-S/S2
[DVB-S/S2]:
FRONTEND: /dev/dvb/adapter1/frontend0
DVR: /dev/dvb/adapter1/dvr0
DMX: /dev/dvb/adapter1/demux0
device 1: [ Sundtek MediaTV Pro] DVB-C, DVB-T, ANALOG-TV, FM-RADIO, REMOTE-CONTROL, OSS-AUDIO, RDS
[DVB-C]:
FRONTEND: /dev/dvb/adapter2/frontend0
DVR: /dev/dvb/adapter2/dvr0
DMX: /dev/dvb/adapter2/demux0
[DVB-T]:
FRONTEND: /dev/dvb/adapter2/frontend0
DVR: /dev/dvb/adapter2/dvr0
DMX: /dev/dvb/adapter2/demux0
[ANALOG-TV]:
VIDEO0: /dev/video0
VBI0: /dev/vbi0
[FM-RADIO]:
RADIO0: /dev/radio0
RDS: /dev/rds0
[REMOTECONTROL]:
INPUT0: /dev/mediainput0
[OSS]:
OSS0: /dev/dsp0
$ /opt/bin/mediaclient --enabledreambox=/dev/dvb/adapter1/frontend0
$ /opt/bin/mediaclient --enabledreambox=/dev/dvb/adapter2/frontend0
verify if the tuners are loaded:
$ cat /proc/bus/nim_sockets
cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2
Name: BCM7335 DVB-S2 NIM (internal)
NIM Socket 1:
Type: DVB-S2
Name: BCM7335 DVB-S2 NIM (internal)
NIM Socket 2:
Type: DVB-S2
Name: Sundtek SkyTV Ultimate (USB)
NIM Socket 3:
Type: DVB-C
Name: Sundtek MediaTV Pro (USB)
restart enigma:
$ killall enigma2
please not that not all Dreambox systems support multiple USB DVB-C devices, some VU+ systems also don't support DVB-C yet -- in case of VU+ the PLi Firmware Image is currently known to support USB DVB-C tuners, VTI is in progress but this is out of our hands
-
when installing i get a failure,
segmentation fault
/usr/sundtek/mediaclient
error while loading shared libraries : unexpected reloc type 0x7E
is there a solution for this problem, the dm800 can't find the usb C tuner at this moment
-
Are you using openPLI on a dreambox?
Please follow up in following thread:
http://support.sundtek.com/index.php/topic,348.msg2125.html#new
-
Does this work with both the MediaTV Pro and MediaTV Digital Home tuners? What about the SkyTV Ultimate tuner if one would like an extra satellite tuner?
-
SkyTV is upcoming soon, it is supposed to work with the Dreambox System. A software engineer from Dream Multimedia is also cooperating with this.
MediaTV Pro and MediaTV Digital Home tuners are supported.
Latest Reports:
* DM800 works (good support depends on the reencoding of the TV channels of your provider, the old DM800 is picky about that).
* DM8000 works again with the latest drivers
* DM500HD works with network mode
* DM800SE the dream Multimedia Software engineer reported it works another customer reported that it doesn't (so this software engineer is checking it again with the customer).
-
Hi
I have tried to install a DVB_S2 on a DM800HD-S and have som problems.
The installation proceeds as the instruction but it don't create the catalog /dev/dvb/adapter1
When I try to start the Suntek DVB_S2_Tuner Enigma craches :'(
Here are some screenshots:
root@dm800:/tmp# ./sundtek_installer_development.sh
Busybox installation
Welcome to the Sundtek linux driver setup
Legal notice:
This software comes without any warranty, use it at your own risk
Do you want to continue [Y/N]:
Nutzungsbedingungen:
Sundtek übernimmt keinerlei Haftung für Schäden welche eventuell durch
das System oder die angebotenen Dateien entstehen k├Ânnen.
Wollen Sie fortfahren [J/N]:
j
stopping old driver instance...
unpacking...
checking system... testing libc OK 2.3.90
MIPSel (old libc) System detected
installing...
Using /dev/misc/vtuner0 interface
Starting driver...
done.
root@dm800:/tmp#
root@dm800:/usr/script# ./DVB_S2_Tuner_starten.sh
--------------------------------------
DVB-S/S2 Tuner start
--------------------------------------
switching off loglevel
unable to open /dev/dvb/adapter1/frontend0
--------------------------------------
Enigma restart
--------------------------------------
root@dm800:/usr/script# ./DVB_Tuner_Info.sh
--------------------------------------
DVB Tuner info
--------------------------------------
**** List of Media Hardware Devices ****
NIM Socket 0:
Type: DVB-S2
Name: Alps BSBE2
Has_Outputs: yes
root@dm800:/usr/script# /opt/bin/mediaclient -e
**** List of Media Hardware Devices ****
root@dm800:/usr/script#
Could it be that you have any idea why?
-
One more thing...
I'm using Gemini 4.7 on this DM800
Thanks in advance!
-
that's strange, what does "lsusb" show up, or "/usr/sundtek/mediaclient --lsusb"
-
-sh: /usr/sundtek/mediaclient: not found
root@dm800:/usr/sundtek# ls
khelper-src.tar.gz kpatch sun_dvb.sh
I will upgrade the box to Gemini 5.10 tomorrow and try to install the USB tuner again after that.
It could be that some drivers are upgraded in the latest release...
I will let you know the result.
-
Our engineers are currently in Taiwan again for one month to verify new devices. So the answer will be a little be delayed for such questions.
-
I have now upgraded my DM800 from Gemini 4.7 to 5.1 (second stage loader 75 to 76).
I'm very pleased to tell you that my DVB_S2_Tuner now works :D
During the installation detected that it was a Dreambox 800/800se.
When I tried beforde the upgrade it said "MIPSel (old libc) System detected"
Thanks for your support!
-
It was probably too old and missing the dualtuner support so it used the generic drivers. But good to know maybe we should add a version-check and tell the user about that in the future.
-
Hello, tried to install the driver. I can tune all DVB-C channels, but I can see the free channels only. Does this tuner works with CI module with smart card to decrypt channels?
I have ClarkTech ET9000, PLI firmware, SMiT Conax chipset pairing CAM, UPC smart card (Czech). Thank you. Ales
-
Hello,
this works with some settopboxes (VU+ was working on this some time ago), if possible can you post this in the clarketech forum?
Technically it should be possible to use it of course.
This is a little bit out of our hands since this is done in the proprietary clarketech drivers.
-
Hi,
I have DM800HD se. I use the newest firmware from Newnigma2.
If I buy DVB-S card, will that work that I can record one channel and watch another one?
The How-To is for DVB-C and DVB-T, but I can see someone tried to run DVB-S too...?
-
We tested DVB-S/S2 it works with the Dreambox and various other settopboxes.
It can be used to extend the settopboxes to dual or triple DVB-S/S2 tuners
-
Hello all,
dreambox DM800Se with usb pro stick is very slow with zapping, with every channel spinner in the screen of the television :-\
Flashed the receiver with the latest Pli and drivers for my sundtek stick
Any idea what i can do to let it work how it did before ?
-
Did you replug the USB device after installing the latest driver?
-
replug ? no i did not.....
so if i understand - unplug the usb device and then install the latest driver with the sundtek plugin before replug the device ?
i will try this, thanx ;)
-
With the latest driver there was a firmware update introduced, this requires to replug the device after installing the driver.
-
did not work for me here
unplug the device and installed the driver -> reboot de dreambox and plugged the Sundtek stick back in.
the stick works but very slow .....
-
If you can contact us via Skype (sundtek) we might figure out what's wrong with your setup.
-
I will try that at the end of next week :)
thanx for your reply ;)
-
Last weekend I've tried to install the "Sundtek MediaTV Pro (DVB-CT, Radio, AnalogTV)" on a VU+Duo with OpenPli 2.1 with the last updates. I've used your installation manual (see link (http://support.sundtek.com/index.php/topic,348.0.html)). The VU+Duo sees the tuner, but thinks it's a DVB-T tuner. But I need the DVB-C tuner.
What am I doing wrong?
-
Did you run the DVB_C_Tuner_starten.sh script?
-
Did you run the DVB_C_Tuner_starten.sh script?
I'm starting to doubt wether I ran the DVB_T_Tuner by mistake. I've run the DVB_Tuner_kein_autostart.sh now, followed by DVB_C_Tuner_autostart.sh
I'm not at home at the moment (Just could make an ssh shell to the box from work). I'll give it a try when I'm back home, and let you know.
Thanks for the quick support!
-
I've run the DVB_Tuner_kein_autostart.sh to clear the DVB-T tuner autostart. Then I ran the DVB_C_Tuner_autostart.sh to enable the DVB-C tuner. But after a reboot the box still says it has: TunerC: Sundtek MediaTV Digital Home (USDVB-T (DVB-T)
And not DVB-C ... :(
Do I really have to powercycle the box to get it right?
-
It works now. I also had a thread on the OpenPli forum and there they adviced me to make a sundtek.conf in the /etc folder. And the sundtek.conf looks like this:
[serial_sundtek]
initial_dvb_mode=DVBC
dreambox_support_fe1=on
The serial can be retrieved by: /opt/bin/mediaclient -e
And now the VU+Duo sees the tuner as a DVB-C tuner!
-
DVB_C_Tuner_autostart.sh
only means to autostart the tuner after the reboot
DVB_C_Tuner_starten.sh
means immediately start E2 with DVB-C tuner support
In case you started the first script only it's understandable that nothing happened since it just deploys the autostart scripts
-
Ok...
Is it wise to run the DVB_C_Tuner_starten.sh?
Or can I leave it this way with the Sundtek.conf file?
DVB_C_Tuner_autostart.sh
only means to autostart the tuner after the reboot
DVB_C_Tuner_starten.sh
means immediately start E2 with DVB-C tuner support
In case you started the first script only it's understandable that nothing happened since it just deploys the autostart scripts
-
first of all you need to ensure that the driver is started automatically when you reboot your settopbox
-> you already did this by running DVB_C_Tuner_autostart.sh
The configurationfile (sundtek.conf) is usually only useful for setups which use 2 USB tuners, but it can also be used for single tuners.
The configurationfile has a higher priority than the *_starten.sh scripts.
In the background both things, the configfile or the scripts do the same (the scripts DVB_*_starten.sh is usually easier for customers)
So either way is correct, the configfile is just more difficult for the enduser.
-
Very clear :)
Thanks for all your quick support, wish all people were like this!
-
As I said, everything is working now.
But there is one fault with the Sundtek in combination with OpenPli. I can switch from DVB-T to DVB-C and back to DVB-T whithout any problems. But if I want to go back to DVB-C once more, it stops working. Only DVB-T will work from then on. The Sundtek doesn't do anything anymore, and says it has 0% signal.
Only a powercycle will resolve that issue, untill you switch from DVB-T to DVB-C for the second time. I guess it's a driver problem. I hope you can reproduce this problem, and resolve this. (it's a common problem with Sundtek if you search the internet)
-
As I said, everything is working now.
But there is one fault with the Sundtek in combination with OpenPli. I can switch from DVB-T to DVB-C and back to DVB-T whithout any problems. But if I want to go back to DVB-C once more, it stops working. Only DVB-T will work from then on. The Sundtek doesn't do anything anymore, and says it has 0% signal.
Only a powercycle will resolve that issue, untill you switch from DVB-T to DVB-C for the second time. I guess it's a driver problem. I hope you can reproduce this problem, and resolve this. (it's a common problem with Sundtek if you search the internet)
DVB-T should be DVB-S?
The problem is occurring when switching between DVB-S and DVB-C :)
I started a new topic: http://support.sundtek.com/index.php/topic,844.0.html because this problem is with several types of E2 boxes.
-
Hi,
Here is my problem:
I installed properly the dongle with the right script as explained in the beginning of this topic. Everything went fine but it doesn't want to work...
- In the end of the installation, if i chose the dvb-c start-script, the dreambox freezes and it's impossible to reboot it but manually. So, I don't have choice but to chose the "autostart-script". There is no problem. After a reboot, the Dreambox sees the device and i can enter the menu to set it up. BUT--->
-> If I go in the menu to scan services, I get this failure : "ERREUR - échec lors de l'analyse (error starting..."
-> I read that I shouldn't do an automatic scan but I did it previously (some months ago) and I worked fine. Anyway, I decide to scan manually but once again, it doesn't work and I have to reboot the Dreambox manually one more time.
I'm totally stacked with that problem. I can't get any channel. Would anybody help me ? :'(
Information:
-------------
Dreambox 8000 HD PVR
Latest LT Image
Boot Loader #84
Cable Operator : VOO
Country : Belgium
-
Which image do you use?
-
Hi,
This one : LT.Eight.1-dm8000.nfi
http://www.lt-forums.org/forum/showthread.php?7935-quot-LT8-Atlantis-The-Lost-Image-quot-for-DM8000HD-(LT-revision-3611)
-
we massively updated the drivers recently, however we need to do some fine-tuning still
Advantages are:
* faster zapping
* better stability
* overall better to improve for us
Disadvantage for the short term:
* we need to check the driver with all the STB systems again
* for short term some compatibility problems can arise of course.
-
We updated the driver for Merlin, we also tested LT now and it also works?
However we tested it with a DM800SE, in case you still have an issue with it please contact us via chat (Skype - sundtek) or http://chat.sundtek.de (we prefer Skype Chat)
-
Thank you for your active support.
May I contact you any day ?
-
Sure.
-
Driver is updated and should fix that problem now.
-
Hi Markus,
It has been a while ago, but now I've purchased a second adapter. I've followed the instructions, and my VU+Duo sees the 2 adapters, very good! But...
When I reboot, I only see one tuner, and have to do the lines:
/opt/bin/mediaclient --enabledreambox=/dev/dvb/adapter1/frontend0
/opt/bin/mediaclient --enabledreambox=/dev/dvb/adapter2/frontend0
Again, manually.
How do I force this will happen automatically every reboot?
-
For the dreambox please use the "sundtek control center" Plugin, it should be available in the feed.
-
What does that do? Can you give a bit more information?
I already installed a sundtek stick, and that's working fine, so all drivers are installed and working fine. It's only with this second stick that after every reboot, I have to activate the second adopter as you can read on the first page.
-
it's an enigma2 plugin which allows you to perform the driver installation and configuration with the remote control
-
Just edited my former post: The Sundtek stick was already installed and working, it's only the second stick which I have to activate every time after a reboot.
-
the sundtek control center also helps you with that
-
Is this Markus? I'm not familiar that you answer so short. :(
I've read the complete thread, and I don't find anything about the sundtek control center.
I just want a command to start it automatically, is that so hard?
Your installation manual in this thread is so complete, but only this thing is missing.
-
Try this one on a telnet console:
cd /tmp
wget http://www.sundtek.de/support/multituner.sh
chmod 755 multituner.sh
./multituner.sh
-
Hi, sorry for my late reply, had 'some' troubles with my receiver.
Thanks for the script, it works now.
There's just one typo, the last line has to start with ./ :)
-
Hi, sorry for my late reply, had 'some' troubles with my receiver.
Thanks for the script, it works now.
There's just one typo, the last line has to start with ./ :)
you're right .. I updated it thanks!
-
Hi,
2 days ago I bought Sundtek MediaTV Digital Home (DVB-C/T/T2) for my Dreambox 8000.
I installed the drivers I found here (I installed via IP address ... cool feature!).
This is the situation: the device works... but only for DVB-T channels.
I bought it to receive DVB-T2 channels, but when I search for them, they don't arrive!
In last 2 days I spent a lot of time to understand where is the problem?
I live in Finland, and here the DVB-T2 standard is a reality. I have the antenna ready for that kind of frequencies, but the Dreambox "sees" only DVB-T frequencies.
Why?
What I'm doing wrong?
I searched in the terrestrial.xml it seems alright... I see Suomi (Finland) DVB-T/DVB-T2 list, but I'm wondering if those frequencies are updated... Are they?
Of course I checked also in the options of my Dreambox that the Sundtek MediaTV Digital Home is set as DVB-T2 and frequencies are for Finland.
What else should I do?
Does it (maybe) works only with certain Dreambox images?
And by the way, does the remote control I received with the Sundtek MediaTV Digital Home, works with the Dreambox (do I need it?).
Thank you in advance! I hope you can help me!
Because I would be very disappointed. My Dreambox had already the receiver for DVB-T channels, and I didn't need to buy another one...
Pino
-
Dreamboxes officially do not support DVB-T2, however you can use the device and tunnel DVB-T2 through DVB-T (also only select DVB-T in the Windows installer, DVB-T2 is also supported through DVB-T mode!)
The problem here is that you need to scan those channels manually, because they will not be scanned with the default DVB-T frequency tables.
Do you know the DVB-T2 frequencies in your area?
-
Dreamboxes officially do not support DVB-T2, however you can use the device and tunnel DVB-T2 through DVB-T (also only select DVB-T in the Windows installer, DVB-T2 is also supported through DVB-T mode!)
The problem here is that you need to scan those channels manually, because they will not be scanned with the default DVB-T frequency tables.
Do you know the DVB-T2 frequencies in your area?
Hi and thank you very much for you answer!
Well, it was as I thought: the terrestrial.xml was wrong or not updated.
Does it come with your drivers?
Anyway searching and searching (it was difficult...) I found an updated terrestrial.xml file. Now I receive all the DVB-T2 channels!
I'm happy about that, but... the HD channels are really slow to open!
Some times the Dreambox stucks on the channel for 10 or 20 seconds... nothing happens...
there is only a freezed picture, so if I try to change the channel and come back, then maybe in 5 seconds I see the channel...
It's quite annoying...
Are there some option to choose, to change to have a better reception of the HD channels?
Thanks in advance!
Pino
-
Hi,
try to change the position of the antenna, I guess that should be the reason.
If you log in with Telnet you can run following command:
/opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter1/frontend0
to monitor the signal strength on the console (abort with ctrl-c)
-
Hi,
I have received my Sundtek MediaTV Pro USB tuner today. It was installed in genuine DM8000 receiver. Having a problem with reception of DVB-T2 channels. They were found and are on my list. Very often when I go to HD version (that uses T2) there is a message "Tune failed" and the only way is to go one channel up or down (SD on DVB T). I live in England and the same antenna is used for my DVB-T2 TV and works fine. Also EPG on DVB-T2 MUX is corrupted. The corruption also shows on normal T channels when I view EPG list, but as soon as I go to SD channel EPG shows fine. But EPG on T2 (for both SD and HD) channels is not good. One more problem. Normally when I reboot DM8000 (with DM terrestrial tuner) terrestrial EPG is always blank and populates on reception. With Sundek tuner the corrupted EPG shows immediately after reboot. It seems that Sundtek Plugin is responsible for EPG generation rather that DM8000.
Hope this makes sense. Thanks!
-
Does this affect all your HD channels? Or just one Mux?
EPG is parsed by the Dreambox filters. Normally there shouldn't be an issue, what does the signal strength command say?
And which channel parameters did you set? Setting the wrong ones can definitely also be the root cause for a bad picture.
Usually there should not be a problem, since all tuners have been tested before leaving our factory.
-
Does this affect all your HD channels? Or just one Mux?
EPG is parsed by the Dreambox filters. Normally there shouldn't be an issue, what does the signal strength command say?
And which channel parameters did you set? Setting the wrong ones can definitely also be the root cause for a bad picture.
Usually there should not be a problem, since all tuners have been tested before leaving our factory.
There are two DVB T2 muxes and they have a mixture of SD and HD channels. The issues with reception, that I am having, are only if I go from DVB T to DVB T2 MUX. Once T2 shows I can go between different channels on the same MUX without problems. The picture never freezes or misbehaves. 50% of time, if I go from DVB T to DVB T2 it shows "Tune failed".
I am unable to upload Screenshots!
-
Can you contact us via Skype-chat (sundtek), or if you have another instant messenger we can also set that up)?
We won't be able to deal with that today, but possibly tomorrow.
-
Thanks! Will Skype you tomorrow.
-
I tried to contact Sundtek Support via Skype, a few minutes ago, but there was no answer.
-
As discussed in Skype we will increase the tuning delay a little bit on T2 (plus 0.15 sek) that seems to solve the "Tune failed" for the EPG issue try another Dreambox image, this is not really related to our tuner (we don't have access to the EPG parser). But it's possible that the DM8000 cannot handle T2 EPG and that this garbles the EPG on your side.
-
I already own a Sundteck MediaTV Pro II which I use on my VU+duo very happily.
As I want to add a cabel tuner, I was looking at buying a Sundteck MediaTV Pro III, as the II is no longer available.
My question is: can I expect the two USB tuners to work together, just as if there were 2 version II's? And in the manner of just following this thread to get them to work?
Thanks
-
Hi,
yes the driver package supports all of our products (including those which are already EOL).
So yes you can use both versions at the same time.
The 3rd generation is even better than the second one (faster zapping and it supports DVB-T2) and the temperature is low.
The power consumption is nearly half of the old device.
-
Hi,
I bought my second stick and after I used the Sundtek Control center, it is visible in the Vu+Duo. Somehow, the second stick refused to come out of stand-by:
when I select one channel on the TV it gives:
root@bm750:~# /opt/bin/mediaclient -e
**** List of Media Hardware Devices ****
device 0: [Sundtek MediaTV Pro (USB 2.0)] DVB-C, DVB-T, ANALOG-TV, FM-RADIO, RE
MOTE-CONTROL, OSS-AUDIO, RDS
[INFO]:
STATUS: ACTIVE
[BUS]:
ID: 1-1
[SERIAL]:
ID: U111215160423
[DVB-C]:
FRONTEND: /dev/dvb/adapter1/frontend0
DVR: /dev/dvb/adapter1/dvr0
DMX: /dev/dvb/adapter1/demux0
[DVB-T]:
FRONTEND: /dev/dvb/adapter1/frontend0
DVR: /dev/dvb/adapter1/dvr0
DMX: /dev/dvb/adapter1/demux0
[ANALOG-TV]:
VIDEO0: /dev/video0
VBI0: /dev/vbi0
[FM-RADIO]:
RADIO0: /dev/radio0
RDS: /dev/rds0
[REMOTECONTROL]:
INPUT0: /dev/mediainput0
[OSS]:
OSS0: /dev/dsp0
device 1: [MediaTV Pro III USB (EU)] DVB-C, DVB-T, DVB-T2, ANALOG-TV, FM-RADIO,
REMOTE-CONTROL, OSS-AUDIO, RDS
[INFO]:
STATUS: STANDBY
[BUS]:
ID: 2-1
[SERIAL]:
ID: U150310172957
[DVB-C]:
FRONTEND: /dev/dvb/adapter2/frontend0
DVR: /dev/dvb/adapter2/dvr0
DMX: /dev/dvb/adapter2/demux0
[DVB-T]:
FRONTEND: /dev/dvb/adapter2/frontend0
DVR: /dev/dvb/adapter2/dvr0
DMX: /dev/dvb/adapter2/demux0
[DVB-T2]:
FRONTEND: /dev/dvb/adapter2/frontend0
DVR: /dev/dvb/adapter2/dvr0
DMX: /dev/dvb/adapter2/demux0
[ANALOG-TV]:
VIDEO0: /dev/video1
VBI0: /dev/vbi1
[FM-RADIO]:
RADIO0: /dev/radio1
RDS: /dev/rds1
[REMOTECONTROL]:
INPUT0: /dev/mediainput1
[OSS]:
OSS0: /dev/dsp1
When I select another TV connected and therefore want the second stick to start working. I get this readout:
root@bm750:~# /opt/bin/mediaclient -e
**** List of Media Hardware Devices ****
device 0: [Sundtek MediaTV Pro (USB 2.0)] DVB-C, DVB-T, ANALOG-TV, FM-RADIO, RE
MOTE-CONTROL, OSS-AUDIO, RDS
[INFO]:
STATUS: ACTIVE
[BUS]:
ID: 1-1
[SERIAL]:
ID: U111215160423
[DVB-C]:
FRONTEND: /dev/dvb/adapter1/frontend0
DVR: /dev/dvb/adapter1/dvr0
DMX: /dev/dvb/adapter1/demux0
[DVB-T]:
FRONTEND: /dev/dvb/adapter1/frontend0
DVR: /dev/dvb/adapter1/dvr0
DMX: /dev/dvb/adapter1/demux0
[ANALOG-TV]:
VIDEO0: /dev/video0
VBI0: /dev/vbi0
[FM-RADIO]:
RADIO0: /dev/radio0
RDS: /dev/rds0
[REMOTECONTROL]:
INPUT0: /dev/mediainput0
[OSS]:
OSS0: /dev/dsp0
device 1: [MediaTV Pro III USB (EU)] DVB-C, DVB-T, DVB-T2, ANALOG-TV, FM-RADIO,
REMOTE-CONTROL, OSS-AUDIO, RDS
[INFO]:
STATUS: STANDBY
[BUS]:
ID: 2-1
[SERIAL]:
ID: U150310172957
[DVB-C]:
FRONTEND: /dev/dvb/adapter2/frontend0
DVR: /dev/dvb/adapter2/dvr0
DMX: /dev/dvb/adapter2/demux0
[DVB-T]:
FRONTEND: /dev/dvb/adapter2/frontend0
DVR: /dev/dvb/adapter2/dvr0
DMX: /dev/dvb/adapter2/demux0
[DVB-T2]:
FRONTEND: /dev/dvb/adapter2/frontend0
DVR: /dev/dvb/adapter2/dvr0
DMX: /dev/dvb/adapter2/demux0
[ANALOG-TV]:
VIDEO0: /dev/video1
VBI0: /dev/vbi1
[FM-RADIO]:
RADIO0: /dev/radio1
RDS: /dev/rds1
[REMOTECONTROL]:
INPUT0: /dev/mediainput1
[OSS]:
OSS0: /dev/dsp1
Just to make sure all tuners are loaded:
root@bm750:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2
Name: BCM7335 DVB-S2 NIM (internal)
Frontend_Device: 0
NIM Socket 1:
Type: DVB-S2
Name: BCM7335 DVB-S2 NIM (internal)
Frontend_Device: 1
NIM Socket 2:
Type: DVB-C
Name: Sundtek DVB-C (0/0) (USB)
Frontend_Device: 2
NIM Socket 3:
Type: DVB-C
Name: Sundtek DVB-C (III) (1/0) (USB)
Frontend_Device: 3
root@bm750:~#
-
Did you set it up in the sundtek control center?
Did you install it using the Sundtek Settopbox Installer?
-
both yes, I installed through the programm on page 1 (ssi.exe) and then
configured in the Sundtek Control Center on the Vu+Duo. I put a yes at the 'second tuner' option.
-
both yes, I installed through the programm on page 1 (ssi.exe) and then
configured in the Sundtek Control Center on the Vu+Duo. I put a yes at the 'second tuner' option.
I tried uploading a picture of SCC as proof but the board won't let me.
-
After that did you configure and enable the tuner in the tuner selection?
-
Yes I did, as I deactiviated the S tuners, both C tuners are active
Both tuners are setup exactly the same, just confirmed that again
-
2 Tuners definitely work and it has been tested.
You might try to disable all tuners -- ok that
And enable them again in order to write a new tuner configuration.
Did you set up the tuner configuration properly in the tuner selection?
Eg. Tuner D same as Tuner E?
All the information you posted so far look correct on the driver installation.
So it seems like a configuration issue inside Enigma which is related either to the tuner configuration or possibly to the channel list.
-
I tried disabling both tuners and then re-enabling them.
That didn’t work.
In the order of old stick as tuner C and new stick as tuner D, I get picture through tuner C but tuner D does not work.
Then I attached only the new stick and that did not give me any picture. I did notice that the responsiveness of the system became terrible, about 5 seconds to process each remote control push.
Then I installed the old stick as tuner D and the new one as tuner C. Responsiveness is the same as without the old tuner.
This leads me to believe the cause should be found in the new tuner. Somehow it seems to cause enormous overhead resulting in poor responsiveness of the system.
What I also noted, even though the code I posted seems to show the stick is available, the SCC claims ‘no stick found’ for the second stick. Perhaps that could be the cause.
-
Which Settopbox Image do you use?
And did you try another Settopbox image already?
According to the serial number seems like the unit was tested on our side on 10th of March / 5:04pm without any issues
-
I'm using VTI6 which has given me much beter results in the past the e.g. OpenPli.
I did update the drivers to the version of 10 March 2015 but that didn't help.
Good to hear the unit worked at your end, therefore it must be a software/driver issue.
I'll put on VTI8 and OpenPli and see whether that will work
-
I'm using VTI6 which has given me much beter results in the past the e.g. OpenPli.
I did update the drivers to the version of 10 March 2015 but that didn't help.
Good to hear the unit worked at your end, therefore it must be a software/driver issue.
I'll put on VTI8 and OpenPli and see whether that will work
A clean install of VTI8 seems to have been the solution. Perhaps old residual install information was in the way.
Important part is that is works now. So what I did was:
- clean install VTI8
- install latest updates
- install Sundtek drivers through ssi.exe
- install channel list though dreamboxedit
- install cccam 2.3.0 to access Ziggo decodercard
Works now.
Thanks for your help
After some playing around a little nuance is needed: watching one channel directly and streaming another is ok.
Trying to stream 2 channels does not work, second channel will not start.
-
I guess that's all related to the image; I think I remember there might have been some issues with VTI6 which has been solved with VTI7 again.
Luckily since the driver is independent the only bug that can be around could be the broadcom drivers of the image.
-
Unfortunatly I was happy to early. Seems when I had two streams, they were comming from the same transponder, most likely through one tuner.
The new tuner will not function, not even when I remove the old tuner and it is the only configured tuner. I do not seem to be able to get a working picture out of this new tuner.
The Sundtek control center shows both sticks, OPenPli tuner configuration shows both sticks (I have a picture to proof that: www.bajor.nl/scc.jpg )
Changing the 'transmission way' does not change a thing
When I stream with the old stick and try to watch TV with the new stick it claims that it cannot find the channel (afstemmen mislukt in Dutch). As if the stick is working fine from the Linux side but is not able to convert the cable signal into a TV signal.
Tonight I will connect the new tuner to my windows computer and see whether or not it works.
-
OK, so the new stick is functioning, at least under Windows7.
Which on one side is good, as it is not deffective, but it is still not working.
Somehow I feel it could be a driver problem. I saw that for windows the current driver is from 2015 and the one on my Vu+Duo is from 10 March 2015, so I have the most current drivers.
-
The idea that it is a driver problem seems more and more plauasible.
I hooked the two tuners up to a Vu+Solo2, with a much faster processor.
Whenever the system tries to access the new tuner, it keeps saying 'loading'
The blue led on the tuner is on, it is visible in both VTI and OpenPli.
It feels like the driver is not working with the 3rd generation tuner.
As it is brand new: it is possible to swap it for a 2nd generation tuner?
-
We usually port the Linux drivers to windows you can contact us via Skype-chat (sundtek) to double check the issues on your settopbox directly.
-
Ok, sounds good, how about on Tuesday the 24th. Do I contact you, and how?
-
just contact us via Skype (sundtek) and we will see your request.
Or you might also try http://chat.sundtek.de (but we're not always monitoring the webchat).
It is very weird that the tuner doesn't work with your box, are you sure this is a genuine tuner from us? We even sold similar tuners to US and they also work - none of them causing boot up issues.
-
Ok, in your case if you mix an old and a new tuner; use the new tuner for scanning that will get you the correct frequencies into the channel list.
The old tuner will also have no problem with that.
This is a little bit related about the Ziggo frequency list submitted via their network, a very special case.
-
Thanks to the wonderful work of the Sundtek Support, who spend over an hour digging into the problem, the solution was found.
It appears the new MediaTV Pro III has a somewhat smaller bandwith to lock a channel then the old MediaTV Pro II.
As I scanned my channels using the old MediaTV Pro II, the found freqencies were out of the lock-bandwith needed by the MediaTV Pro III.
Scanning the freqencies with MediaTV Pro III solved that problem.
Ziggo is also a little to blame as e.g. transponder on 578MHz is actually centered on 578.75MHz.