fusion hdtv dual express 2

fusion hdtv dual express 2

[James Harper]

After confirming that it was supported I just bought a fusion hdtv dual express PCI adapter, only to find that I'd bought the 'dual express 2' version, which isn't supported (not the first time I've made such a mistake).

This page http://www.linuxtv.org/wiki/index.php/DViCO_FusionHDTV_DVB-T_Dual_Express2 says that the new v2 card is still using CX23885 chipset but also uses DIB7070 (dib7000 + dib0070) which appears to be supported already but only via a few USB adapters.

With a bit of cut and paste I have added some support for the card, to the point that dvbtune now says:

# dvbtune -f 550500000 -bw 7 -c 2 -cr 3_4 -gi 16 -tm 8 -I 1 -m -i

Using DVB card "DiBcom 7000PC"
tuning DVB-T (in United Kingdom) to 550500000 Hz
polling....
Getting frontend event
FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC
Bit error rate: 0
Signal strength: 49390
SNR: 233
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC
<transponder type="T" freq="550500000">
Nothing to read from fd_pat
Nothing to read from fd_sdt
</transponder>
Signal=49402, Verror=0, SNR=228dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=49397, Verror=0, SNR=226dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=49377, Verror=0, SNR=235dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=49336, Verror=0, SNR=230dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=49345, Verror=0, SNR=235dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=49374, Verror=0, SNR=232dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=49352, Verror=0, SNR=254dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=49396, Verror=0, SNR=241dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=49344, Verror=0, SNR=243dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=49353, Verror=0, SNR=258dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=49309, Verror=0, SNR=248dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=49334, Verror=0, SNR=243dB, BlockErrors=0, (S|L|C|V|SY|)
^C

Which all looks correct at the start, but obviously not as it can't actually read the information in the dvb streams.

Is it likely that getting it working only requires a small amount of further tinkering, or am I likely wasting my time? I know next to nothing about dvb and how it all hangs together.

Thanks

James

RE: fusion hdtv dual express 2

[James Harper]

> Hi James,
> 
> The first basic thing you should look at is if the dvb device has got all
> its pieces.
> A dvb adapter has, sort of, 4 sub-devices:
> [me@home ~]$ ll /dev/dvb/adapter2
> total 0
> crw-rw----+ 1 root video 212, 12 Jun  5 12:31 demux0
> crw-rw----+ 1 root video 212, 13 Jun  5 12:31 dvr0
> crw-rw----+ 1 root video 212, 15 Jun  5 12:31 frontend0
> crw-rw----+ 1 root video 212, 14 Jun  5 12:31 net0
> 
> From your post you might miss the demux while the front-end is working.
> 

ls -al /dev/dvb/adapter1/
total 0
drwxr-xr-x 2 root root     120 Jun  7 10:08 .
drwxr-xr-x 5 root root     100 Jun  7 10:08 ..
crw-rw---T 1 root video 212, 5 Jun  7 10:08 demux0
crw-rw---T 1 root video 212, 6 Jun  7 10:08 dvr0
crw-rw---T 1 root video 212, 4 Jun  7 10:08 frontend0
crw-rw---T 1 root video 212, 7 Jun  7 10:08 net0

same for adapter2 (adapter0 is an existing usb dvb-t adapter)

I think all the pieces are there, they just aren't connected up internally correctly. If I deliberately put in a wrong i2c address for the tuner (starts of at 0x12 and is reprogrammed to 0x80 in the usb version, which is what I've copied) then I get an error, so it can definitely see the tuner. And if I tune an incorrect frequency I never get lock or anything so I think that much is working. And my original post shows it can see a stream with no errors, and if I put the incorrect code rate in (eg 2_3 instead of 3_4) then it sees lots of errors.

So suppose that the demux is what's wrong, how could I debug that further?

Is there a block diagram somewhere that explains how the various dvb components feed into each other?

Thanks

James