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.
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 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.
echo vtuner_skip0=vtuner0 > /etc/sundtek.conf
you can use
(0 = zero)
this will cause that our driver attaches to vtuner1 instead of vtuner0, leaving vtuner0 to your alternative device.
It´s works on BH perfect, but dvb-c can´t do search, error starting scanning...
Can you fix it?
Regards from Spain
you need to scan 1 frequency manually and set network scan to yes.
<?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>
Is there are common issue with the code on the side of Vu+ drivers, which binaries distributed via vu+ website ?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.