Drivers for Sundtek Media TV Pro

cristo4

Vu+ Newbie
Yes please....we are all waiting for support and implementation for these Sundtek drivers amongst all the other devices already supported! Please...is it that hard?
 
Would be nice to support our driver with BH, new devices are upcoming.

Is there any problem we can help to solve?

DVB-S2 is ready to go now, (our HW engineers finally did a very good job for this).

angelofsky1980 should have received a Version 3.x Tuner, we're at Version 4.0 (with improved sensitivity and support for several active multiswitches without AC adapters) right now.
 
Would be nice to support our driver with BH, new devices are upcoming.

Is there any problem we can help to solve?

DVB-S2 is ready to go now, (our HW engineers finally did a very good job for this).

angelofsky1980 should have received a Version 3.x Tuner, we're at Version 4.0 (with improved sensitivity and support for several active multiswitches without AC adapters) right now.

There's a driver update from our side which should work with the BH image now.
 

whatster

Vu+ Newbie
Oke I downloaded latest BH for Solo and the driver from 8 september, but it doesnt work for me.

Installed it on the same ways like on a VTI image, so I hope I get some help with this before switching back to VTI....

The light from the stick lights up but picture is black and after couple seconds it gives a pat timeout error.
 
Oke I downloaded latest BH for Solo and the driver from 8 september, but it doesnt work for me.

Installed it on the same ways like on a VTI image, so I hope I get some help with this before switching back to VTI....

The light from the stick lights up but picture is black and after couple seconds it gives a pat timeout error.

If you still have some issues try to contact us via skype (username sundtek) or chat (http://chat.sundtek.de)
We are currently not aware of any unresolved issues.
 

whatster

Vu+ Newbie
Oke just for information.

I installed the latest BH for Solo and then ofcourse manuel installed the Sundtek driver from 5 november 2011 and tadaa it worked like a charm.

For the people who still need answers if it works or not just do it it right way and you're good to go :)
 

rassi

Vu+ User
Oke just for information.

I installed the latest BH for Solo and then ofcourse manuel installed the Sundtek driver from 5 november 2011 and tadaa it worked like a charm.

For the people who still need answers if it works or not just do it it right way and you're good to go :)


Yeah it does work, personally i need "native" support to get Sundtek + another brand stick to work same time.
Tried twice without success, no issues with other images. It could be user error :)

It was June when i did start to wait implementation, still holding my breath :)
There is gladly other images which to use.
 
Yeah it does work, personally i need "native" support to get Sundtek + another brand stick to work same time.
Tried twice without success, no issues with other images. It could be user error :)

It was June when i did start to wait implementation, still holding my breath :)
There is gladly other images which to use.

you can use

echo vtuner_skip0=vtuner0 > /etc/sundtek.conf

(0 = zero)

this will cause that our driver attaches to vtuner1 instead of vtuner0, leaving vtuner0 to your alternative device.
 

rassi

Vu+ User
you can use



(0 = zero)

this will cause that our driver attaches to vtuner1 instead of vtuner0, leaving vtuner0 to your alternative device.

Yes, Last time i did have some issues with this, it did work with other images, but didn´t got working with BH, but i think it was some user error by me, now im back with BH and i´ll test
it again.
 

Seku

BH Lover
It´s works on BH perfect, but dvb-c can´t do search, error starting scanning...
Can you fix it?

Regards from Spain
 

rassi

Vu+ User
you need to scan 1 frequency manually and set network scan to yes.

It does not all ways work (I think it depends about cable network), so if it does not work, you have to create proper cables.xml and place it to /etc/tuxbox

I did this for my cable provider:
Code:
<?xml version="1.0" encoding="iso-8859-1"?>
<cables>


    <cable name="My cable bruteforce" satfeed="true" flags="9">

<transponder frequency="154000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="162000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="162000" symbol_rate="6875000" fec_inner="0" modulation="5"/>
<transponder frequency="170000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="226000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="234000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="242000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="242000" symbol_rate="6875000" fec_inner="0" modulation="5"/>
<transponder frequency="250000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="250000" symbol_rate="6875000" fec_inner="0" modulation="5"/>
<transponder frequency="258000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="258000" symbol_rate="6875000" fec_inner="0" modulation="5"/>
<transponder frequency="266000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="266000" symbol_rate="6875000" fec_inner="0" modulation="5"/>
<transponder frequency="274000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="274000" symbol_rate="6875000" fec_inner="0" modulation="5"/>
<transponder frequency="282000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="282000" symbol_rate="6875000" fec_inner="0" modulation="5"/>
<transponder frequency="282000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="290000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="290000" symbol_rate="6875000" fec_inner="0" modulation="5"/>
<transponder frequency="298000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="298000" symbol_rate="6875000" fec_inner="0" modulation="5"/>
<transponder frequency="306000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="314000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="322000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="330000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="330000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="338000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="346000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="354000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="362000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="362000" symbol_rate="6875000" fec_inner="0" modulation="5"/>
<transponder frequency="370000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="378000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="386000" symbol_rate="6875000" fec_inner="0" modulation="4"/>
<transponder frequency="394000" symbol_rate="6875000" fec_inner="0" modulation="4"/>

    </cable>

</cables>

With this i can do autoscan as brute force. Correct values for Symbol_rate and frequency has to be set, cable company will know correct ones.


I got one issue, in normal situation I use Sundtek as C tuner only for one cable channel and many many times, recordings hasn't work properly, it has recorded maybe 10minutes or recording is just blank and it stops immediately after trying to play it. Channel is without encryption and I use maybe 2-3 weeks old experimental drivers with BH. Will powered USB hub give some advantages?
 

rassi

Vu+ User
Anyone using sundtek with BH 1.7.3?
And it does work fine?

Just tested it very quickly but it didn't work "no driver started" when test with mediaclient. Again it is propably user error, have to test it again with bettter time. First time was with personal backup recovery and manual installation for the sundtek drivers after that.
 

whatster

Vu+ Newbie
I am using it with BH 1.7.3 on a Solo without any problems, I am up to date with the latest driver by the way from april 23.
 

StAlex74

Vu+ Newbie
Hi.

I have Sundtek MediaTV Digital Home (DVB-CT) and Vu+ Uno with:
- latest BH Image (1.7.8 Light);
- latest drivers from VU+ (2012-08-24);
- drivers from Suntek (3. August 2012).

The stick used for watching DVB-C only. No problem with the scanning for channels, and no problem with watching of open (not encrypted) channels. But seems to I have the problems with watching of the encrypted channels. I am not sure, but when I am switch the STB to the any encrypted channel (Conax CI module with the smart card is inserted), I am not receive an any onscreen message about watching encrypted channel (like a box with "no access" message). And dmesg is empty too (only logging of VIDEO and AUDIO subsystems when they are stopping but no information about communication with CI-module). Binding CI-slot to the provider is done.

The question is:
How can I make sure, what hardware is working properly? Is there any way to obtain any logs for make sure about communications between STB <-> CI-module ?

PS.
Littlebit explanation:
My Cable provider (Russia, Moscow, "OnLime") have two channels to verify the customer's hardware:
- one channel absolutelly free;
- one channel is encrypted, but not require any subscription. Provider says: If You can watch this channel WITH module and WITHOUT inserted card - then you equipment is working properly, and you can call to the our callcenter for activation of full subscription. At this moment, the subscription is not activated: firstly, I want to make sure about my HW.
 

StAlex74

Vu+ Newbie
At Sundtek forum I found some information about issues with the some models of CONAX CAM's.
According to our information this is exactly what they (VU+) wanted to work on 1 year ago and we actually thought that they solved that problem already. Direct CAM support is something VU+ needs to offer within their infrastructure.
Is there are common issue with the code on the side of Vu+ drivers, which binaries distributed via vu+ website ?
That issue is still not fixed ?
 
Top