View Full Version : [VU+ Duo] Drivers for DVB USB Avermedia Volar A835 (9035) in Vix 2.3
Hi,
Can I install my Avermedia Volar DVB in Vix 2.3?
Thanks
Hi,
Can I install my Avermedia Volar DVB in Vix 2.3?
Thanks
On build 204 (kernel 3.1.1), the release notes advise that the af9035 drivers have been put into the feed:)
However, there is no plugin or single package to install the drivers from the menus...
So, this advice from the OpenPLi forum should work equally with the latest ViX build:
I just checked and there is no metapackage yet for the af9035 driver.
So you have to telnet into the box and run:
opkg install kernel-module-dvb-usb-af9035
to get the driver and then:
cd /lib/firmware/
wget http://xgazza.altervista.org/Linux/DVB/dvb-usb-af9035-01.fw
to get the firmware. Reboot and you are ready to go.
I'm currently running the Avermedia Twinstar (A825) based on the af9035 on this ViX image. As with all Vuduo images (not unique to ViX) there can be some stability issues with dtt which usually don't manifest themselves until you've been running for a while. I recommend increasing the <recording data sync size> from <off> to say <512k> and the <recording demux buffer size> to say <1M>. These parameters are to be found under menu->setup->system->recording. This has had a marginal improvement in my system... YMMV.
Cheers
I've followed your instructions on the latest VIX (3.1.1) image but the DVB-Tuner by avermedia is not displayed on the Tuner list, just the A & B ones.
What should I do next?
P.S.
Once rebooted the Vuduo tunes on the last sat channel but the display continue to show "Starting".
So I have to shut it down and restart from the back switch.
Okay, did the telnet opkg install succeed?
Well, since my advice above I've re-installed evrything and I found that I got one (so called fatal) error related to an undefined label. Perhaps because of this undefined label, the initial restart failed to detect the usb tuner(s). After a second restart, the tuners were detected; but recording from terrestrial tuners was limited to tuner C. After a third restart, I was able to record off tuner C and tuner D simultaneously. Your a835 device may need more than a single reboot to complete the initialisation process. Despite my initial advice, maybe I did several restarts the first time as well(?)
I guess this is all a bit crusty but I'm sure things will be more regular in the future when such gremlins are sorted. I know the OpenPli / Vix teams will get on top of all this stuff in the next image or two.
Hope a coupla reboots fixes things!
The driver seems to be installed fine. Here's what i get issuing the following command via telnet:
dmesg | grep dvb
dvb_bcm7335: module license 'Proprietary' taints kernel.
dvb-usb: found a 'Avermedia AverTV Volar HD & HD PRO (A835)' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9035-01.fw'
dvb-usb: found a 'Avermedia AverTV Volar HD & HD PRO (A835)' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: Avermedia AverTV Volar HD & HD PRO (A835) successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9035
dvb_pll: version magic '2.6.18-7.4-dm800 mod_unload MIPS32_R1 32BIT gcc-4.4' should be '3.1.1 SMP mod_unload MIPS32_R1 32BIT '
dvb_core: version magic '2.6.18-7.4-dm800 mod_unload MIPS32_R1 32BIT gcc-4.4' should be '3.1.1 SMP mod_unload MIPS32_R1 32BIT '
dvb_usb: version magic '2.6.18-7.4-dm800 mod_unload MIPS32_R1 32BIT gcc-4.4' should be '3.1.1 SMP mod_unload MIPS32_R1 32BIT '
dvb_usb_af9035: version magic '2.6.18-7.4-dm800 mod_unload MIPS32_R1 32BIT gcc-4.4' should be '3.1.1 SMP mod_unload MIPS32_R1 32BIT '
lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 07ca:a835 AVerMedia Technologies, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 07d1:3c0f D-Link System
Bus 001 Device 002: ID 18a5:0302
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lsmod
Module Size Used by
nfsd 99931 11
zd1211rw 55901 0
8192cu 542837 0
rtl8187 54063 0
rt73usb 24424 0
rt2800usb 13089 0
rt2800lib 44771 1 rt2800usb
rt2500usb 18185 0
rt2x00usb 10921 3 rt73usb,rt2800usb,rt2500usb
rt2x00lib 40442 5 rt73usb,rt2800usb,rt2800lib,rt2500usb,rt2x00usb
r8712u 169530 0
pl2303 12486 0
keyspan 32756 0
ipv6 342374 14
ftdi_sio 30425 0
exportfs 3994 1 nfsd
dvb_usb_af9035 11403 0
mxl5007t 7531 1 dvb_usb_af9035
af9033 15600 1 dvb_usb_af9035
tda18218 3573 1 dvb_usb_af9035
tua9001 2263 1 dvb_usb_af9035
carl9170 83694 0
belkin_sa 6809 0
usbserial 30919 4 pl2303,keyspan,ftdi_sio,belkin_sa
ath9k_htc 63975 0
mac80211 211445 7 zd1211rw,rtl8187,rt2800lib,rt2x00usb,rt2x00lib,car l9170,ath9k_htc
ath9k_common 1442 1 ath9k_htc
ath9k_hw 310668 2 ath9k_htc,ath9k_common
ath 16979 3 carl9170,ath9k_htc,ath9k_hw
appletalk 28439 0
psnap 1836 1 appletalk
llc 3665 1 psnap
brcmfb 1127 2
dvb_bcm7335 4932608 31 brcmfb
procmk 1397 1 dvb_bcm7335
as you can see it states that the Volar should be installed ok but it's not showed in the configuration\channel search\tuner configuration
Is thera some other GUI tool to check USB devices connected? And why it's not showing up among the other tuners?
just tried to uninstall and follow again your instructions. Here's what happens on first command:
opkg install kernel-module-dvb-usb-af9035
Package kernel-module-dvb-usb-af9035 (3.1.1-r15.3) installed in root is up to date.
Configuring picon-hd-hotbird-13e-flash-by-licher.
* *
* plugin installed successfully *
* *
* E2 restart is required *
* *
//usr/lib/opkg/info/picon-hd-hotbird-13e-flash-by-licher.postinst: line 7: ipkgupgrade.log: not found
//usr/lib/opkg/info/picon-hd-hotbird-13e-flash-by-licher.postinst: line 8: ipkgupgrade.log: not found
//usr/lib/opkg/info/picon-hd-hotbird-13e-flash-by-licher.postinst: line 9: ipkgupgrade.log: not found
//usr/lib/opkg/info/picon-hd-hotbird-13e-flash-by-licher.postinst: line 10: ipkgupgrade.log: not found
//usr/lib/opkg/info/picon-hd-hotbird-13e-flash-by-licher.postinst: line 11: ipkgupgrade.log: not found
Collected errors:
* pkg_run_script: package "picon-hd-hotbird-13e-flash-by-licher" postinst script returned status 127.
* opkg_configure: picon-hd-hotbird-13e-flash-by-licher.postinst returned 127.
I agree that it seems to have installed all the modules!
All I can suggest is that you remove all usb devices, then reboot (power switch).
Then plug in usb tuner only and reboot again. (There may be some conflict with registration of other usb devices)
/var/volatile/log/messages.0
dvb-usb: found a 'Avermedia TwinStar' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9035-01.fw'
dvb-usb: found a 'Avermedia TwinStar' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Avermedia TwinStar)
af9033: firmware version: LINK:11.15.10.0 OFDM:5.48.10.0
DVB: registering adapter 1 frontend 0 (Afatech AF9033 DVB-T)...
mxl5007t 0-00c0: creating new instance
mxl5007t_get_chip_id: unknown rev (3f)
mxl5007t_get_chip_id: MxL5007T detected @ 0-00c0
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Avermedia TwinStar)
af9033: firmware version: LINK:11.15.10.0 OFDM:5.48.10.0
DVB: registering adapter 2 frontend 0 (Afatech AF9033 DVB-T)...
mxl5007t 0-00c1: creating new instance
mxl5007t_get_chip_id: unknown rev (3f)
mxl5007t_get_chip_id: MxL5007T detected @ 0-00c1
dvb-usb: Avermedia TwinStar successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9035
Additional adapter instance because my device is a dual tuner
lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 07ca:0825 AVerMedia Technologies, Inc.
Bus 001 Device 002: ID 1a40:0101 TERMINUS TECHNOLOGY INC.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
From above you see that I have a usb hub with Avermedia 825 (TwinStar) on Bus 001
Using Vix 2.3.204 on VuDuo...
No other ideas I'm afraid.
dmesg | grep dvb
dvb_bcm7335: module license 'Proprietary' taints kernel.
dvb-usb: found a 'Avermedia TwinStar' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9035-01.fw'
dvb-usb: found a 'Avermedia TwinStar' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: Avermedia TwinStar successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9035
I'm wondering why you got all that version magic '2.6.18-7.4' stuff!!
wow, I didn't notice that!
Any clue on what could have caused that? And how to fix it?
I've got no idea... maybe you need to start with a clean image.
mmm don't like the idea. :D
tryed on my second Vuduo with VIXimage. The usb tuner is not showed aswell.
and here are the results:
dmesg | grep dvb
dvb_bcm7335: module license 'Proprietary' taints kernel.
dvb-usb: found a 'Avermedia AverTV Volar HD & HD PRO (A835)' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9035-01.fw'
dvb-usb: found a 'Avermedia AverTV Volar HD & HD PRO (A835)' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: Avermedia AverTV Volar HD & HD PRO (A835) successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9035
lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 07ca:a835 AVerMedia Technologies, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 13fd:0540 Initio Corporation
Bus 001 Device 002: ID 18a5:0302
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lsmod
Module Size Used by
nfsd 99931 11
zd1211rw 55901 0
8192cu 542837 0
rtl8187 54063 0
rt73usb 24424 0
rt2800usb 13089 0
rt2800lib 44771 1 rt2800usb
rt2500usb 18185 0
rt2x00usb 10921 3 rt73usb,rt2800usb,rt2500usb
rt2x00lib 40442 5 rt73usb,rt2800usb,rt2800lib,rt2500usb,rt2x00usb
r8712u 169530 0
pl2303 12486 0
keyspan 32756 0
ipv6 342374 17
ftdi_sio 30425 0
exportfs 3994 1 nfsd
dvb_usb_af9035 11403 0
mxl5007t 7531 1 dvb_usb_af9035
af9033 15600 1 dvb_usb_af9035
tda18218 3573 1 dvb_usb_af9035
tua9001 2263 1 dvb_usb_af9035
carl9170 83694 0
belkin_sa 6809 0
usbserial 30919 4 pl2303,keyspan,ftdi_sio,belkin_sa
ath9k_htc 63975 0
mac80211 211445 7 zd1211rw,rtl8187,rt2800lib,rt2x00usb,rt2x00lib,car l9170,ath9k_htc
ath9k_common 1442 1 ath9k_htc
ath9k_hw 310668 2 ath9k_htc,ath9k_common
ath 16979 3 carl9170,ath9k_htc,ath9k_hw
appletalk 28439 0
psnap 1836 1 appletalk
llc 3665 1 psnap
brcmfb 1127 2
dvb_bcm7335 4932608 32 brcmfb
procmk 1397 1 dvb_bcm7335
tryed on my second Vuduo with VIXimage. The usb tuner is not showed aswell.
No sign of version magic on the second box. I can only imagine you need to start with a fresh image and then just install the minimum that you require. Just backup your image if you have some special things in case the dvb-t still doesn't work. However, I can't see why you wouldn't have success as you're almost there!
what is "version magic" supposed to do?
what is "version magic" supposed to do?
I don't know for sure. However, my guess is that it is some trickery used to run old plugins on the new kernel or vice versa. With your first box, I thought you might have installed old stuff onto the current 3.1.1 build. Plugins are notorious for causing unexplained problems because they come from many uncoordinated sources. I guess plugins may not require any 'version magic' to work if they run at the 'top' levels.
Well that was rather a lot of guessing from me... hope I'm not misleading you!
here we go, freshly reinstalled ViX-2.3.153-vuduo_usb, and updated to this day updates.
(had to first instal the USB WIFI pen)
The tuner is not listed at all.
Just to clarify, I've tested and the USB DVB-T pen works (used on my Macbook pro, running Windows XP on Parallel desktop virtualmachine!!!)
dmesg | grep dvb
dvb_bcm7335: module license 'Proprietary' taints kernel.
dvb-usb: found a 'Avermedia AverTV Volar HD & HD PRO (A835)' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9035-01.fw'
dvb-usb: found a 'Avermedia AverTV Volar HD & HD PRO (A835)' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: Avermedia AverTV Volar HD & HD PRO (A835) successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9035
lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 07ca:a835 AVerMedia Technologies, Inc.
Bus 001 Device 002: ID 07d1:3c0f D-Link System
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lsmod
Module Size Used by
nfsd 99931 11
zd1211rw 55901 0
8192cu 542837 0
rtl8187 54063 0
rt73usb 24424 0
rt2800usb 13089 0
rt2800lib 44771 1 rt2800usb
rt2500usb 18185 0
rt2x00usb 10921 3 rt73usb,rt2800usb,rt2500usb
rt2x00lib 40442 5 rt73usb,rt2800usb,rt2800lib,rt2500usb,rt2x00usb
r8712u 169530 0
pl2303 12486 0
keyspan 32756 0
ipv6 342374 14
ftdi_sio 30425 0
exportfs 3994 1 nfsd
dvb_usb_af9035 11403 0
mxl5007t 7531 1 dvb_usb_af9035
af9033 15600 1 dvb_usb_af9035
tda18218 3573 1 dvb_usb_af9035
tua9001 2263 1 dvb_usb_af9035
carl9170 83694 0
belkin_sa 6809 0
usbserial 30919 4 pl2303,keyspan,ftdi_sio,belkin_sa
ath9k_htc 63975 0
mac80211 211445 7 zd1211rw,rtl8187,rt2800lib,rt2x00usb,rt2x00lib,car l9170,ath9k_htc
ath9k_common 1442 1 ath9k_htc
ath9k_hw 310668 2 ath9k_htc,ath9k_common
ath 16979 3 carl9170,ath9k_htc,ath9k_hw
appletalk 28439 0
psnap 1836 1 appletalk
llc 3665 1 psnap
brcmfb 1127 2
dvb_bcm7335 4932608 1 brcmfb
procmk 1397 1 dvb_bcm7335
was reading a post on the OpenPli forum about A835 installation.
http://openpli.org/forums/topic/20111-avermedia-a835-avertv-volar-hd-pro-installation-guide/
Did u get your steps from that post?
Gotcha!!!
dear stick50jr
in this thread you missed to describe some crucial steps that you posted here:
http://www.world-of-satellite.com/showthread.php?14242-Vu-Duo-ViX-2-3-(Linux-3-1-1)-25-12-2011&p=110771&viewfull=1#post110771
Infact as soon as I installed the dib0700 right from the plugin panel, restarted Enigma, the Tuner for DVB-T finally appeared!
Now I've to check if it works. (@ present my wife IS whatching TV)...
Gotcha!!!
dear stick50jr
in this thread you missed to describe some crucial steps that you posted here:
http://www.world-of-satellite.com/showthread.php?14242-Vu-Duo-ViX-2-3-(Linux-3-1-1)-25-12-2011&p=110771&viewfull=1#post110771
Infact as soon as I installed the dib0700 right from the plugin panel, restarted Enigma, the Tuner for DVB-T finally appeared!
Now I've to check if it works. (@ present my wife IS whatching TV)...
Okay... that post was before AndyBlac put the af9035 drivers in the Vix feeds (build 204)... so yes I had to do more with the old builds to get things going... I thought I'd outlined what was needed, but it seems not! I'm glad you have succeeded eventually. You need to be fairly dogged with these things sometimes:)
I'm hoping that the next release (must be getting closer) will include a complete 'meta package' so you can download an '.ipk' file for af9035 devices that will install drivers, firmware and usbtunerhelper in one simple operation. However, in the future if the kernel version is upgraded again (eg xtrend boxes) then usbtunerhelper may be superceded and we may experience some further 'adjustments' to keep our af9035 devices supported.
cheers
@stick50jr
few questions:
A-
I had a scan for frequencies and found channels. At this point when I try to tune I got a "tune lock fail" error (forgive me but I'm using italian as main language so I'm not sure this is ther actual english message, but I hope you understand what I mean.).
In which port of your decoder are you using the DVB pen connected? Or ar you using a power plugged USB-HUB?
Have you made any other tweak?
B-
once the decoder finishes the DVBT scan the channel are listed among sat ones. Is that right?
Am I thinking wrong if I say that to arrange them we need an external setting editor?
here is an extended list of usb DVB tuners and linux drivers:
http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices/Full
some few notes.
I've tried on my second DUO as well.
And I succeded in finding few channels, about 30. The main DVBT tuner has more than 400 channels stored, many doubled. But in these days of switch off this is a fact.
Anyway, even finding channels the DUO was unable to tune. As mentioned in previous post.
Than I tried to use a powered USB-HUB plugged in the DUO. And this time the stored channels were tuned fine.
But rescanning did not result in any new channel. Expecially national RAI and Mediaset channels were not found.
The weird thing is that with my Macbook running windowsXP on the virtual machine, the Avermedia software did found lots of channel including RAI and Mediaset ones. And I was using the antenna provided with the A835!
Back on the first DUO, no luck at all. Always 0 channels found.
I've tried default terrestrial.xml, and many other found on italian boards but always the same result. ZERO
some few notes.
I've tried on my second DUO as well.
And I succeded in finding few channels, about 30. The main DVBT tuner has more than 400 channels stored, many doubled. But in these days of switch off this is a fact.
Anyway, even finding channels the DUO was unable to tune. As mentioned in previous post.
Than I tried to use a powered USB-HUB plugged in the DUO. And this time the stored channels were tuned fine.
But rescanning did not result in any new channel. Expecially national RAI and Mediaset channels were not found.
The weird thing is that with my Macbook running windowsXP on the virtual machine, the Avermedia software did found lots of channel including RAI and Mediaset ones. And I was using the antenna provided with the A835!
Back on the first DUO, no luck at all. Always 0 channels found.
I've tried default terrestrial.xml, and many other found on italian boards but always the same result. ZERO
Dear MarsArtis,
I wish I could speak a language other than English (or the Oz version thereof)... but my schooling was fairly narrow.
I'm glad you appear to have the basic functionality of your dvbt stick working. For tuning my system uses the Australian dvbt system which is limited to a grand total of 20 fta channels using only five separate transponders. I use a different terrestrial.xml than you would use and all the Australian channels use a bandwidth of 7MHz (I imagine europe uses 8MHz mostly).
Despite these differences, a common problem is that the portable antennas provided with the dvbt usb stick are rubbish at picking up signals. I rely on a fixed roof mounted uhf yagi antenna with quad shielded rg6 cabling to my dvbt input. The ability of the various dvbt sticks to pull in a signal will vary with make and model. I note that we are using different models (though both are Avermedia). With Vix build 204, you should also get dvbt signal strength and SNR. With my external antenna I get 99% signal strength and more importantly 99% SNR. (This might sound a bit suspicious, but I have confirmed that these values can be made to reduce with attenuators etc.)
I was using my stick plugged into one of the rear usb ports but have changed this to now use a hub in the same location. I've heard that some people have had more success with a powered hub than relying on the Vu Duo usb power. This could vary with different Vu Duo's and also with different usb sticks... however, I'm currently happy using an unpowered hub which also has a memory stick attached!
That was probably the questions you asked me? Oh yes, all the channels scanned into my VuDuo showed up in a separate 'terrestrial' group. If you look at services by 'satellite' you should see each service grouped under each satellite that you scanned with your dvbs, dvbs2 tuners and another group under 'terrestrial' for your dvbt tuners. There should not be any terrestrial services listed under any of your satellite groups... however, if you look at services under provider then you may well have a mixture and or course, under your favourites you will most likely choose to a have mixture of satellite and terrestrial.
cheers
hi stick.
Abou the portable antenna mentioned by me, I was pointing that the Avermedia software was able to scan e tune channels that duo could not.
So I'm wondering if there's something wrong on the duo.
Infact, neither using my roof antenna both for UHF anf VHF channels I was able to get more channels.
I'm teil concerned about one of the DUO which was not able to find anything a all (and it's the freshly reinstalled one).
hi stick.
Abou the portable antenna mentioned by me, I was pointing that the Avermedia software was able to scan e tune channels that duo could not.
So I'm wondering if there's something wrong on the duo.
Infact, neither using my roof antenna both for UHF anf VHF channels I was able to get more channels.
Well if it's not the antenna, then it is probably the scan details in the terrestrial.xml file. I suggest you check to see what parameters are being used by the successful scanning (Windows PC?) and also what parameters are being used by the VuDuo during a scan. See if they match. In my case, the Avermedia PC software couldn't find any channels because the Australian TV parameters used were wrong... a subsequent update by Avermedia fixed this. So you may have the opposite situation (terrestrial.xml parameters may need changing).
Also you could strip out any parameter blocks in the terrestrial.xml file that are not relevant to your locale... just to ensure that the Vix doesn't get your locale confused with another one.
You could also check the parameters against any formal specification you can find for terrestrial broadcasts in your locale.
I'm teil concerned about one of the DUO which was not able to find anything a all (and it's the freshly reinstalled one).
I guess you need to re-check your installation procedure... it certainly is a pain and hopefully will be more straight forward after the next Vix release (I hope).
mmm, The A835 I was using is the Avermecia AverTv Volar Green Hd.
It's a energy safe model. And I think this may be the issue that makes it in need for more power from USB.
Anyhow, today I decided to send it back to Amazon.
Can you tell us which brand and model is your A835?
Can you tell us which brand and model is your A835?
Mine is also an Avermedia ... TwinStar model A825. This is a twin tuner model which also uses the af9035 chipset. Because it is a twin tuner it will probably cost more but allows you to view/record on separate transponders simultaneously.
Another option is the Hauppauge Nova TD or T stick which is based on the dib0700 chiipset. The TD is a dual tuner (or twin tuner) whereas the T is a single tuner. These used to be available from the site sponsor? The Nova T sticks (and other dib0700 sticks) have been supported earlier than the af9035 sticks in most images.
I would not have thought that the 'energy safe model' would have been a problem. Indeed, my dual tuner should use more power than the single tuner versions like yours.
Better luck with your next terrestrial stick.
Cheers
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.