Project

General

Profile

Forums » General »

Tvheadend: "scan, no data" - mumudvb: no problem

Added by Michael B. almost 9 years ago

I have a Sundtek Media Pro III USB receiver for DVBC. When I use mumudbv, I can get perfect streams. I tested this with two different muxes.

Using the same muxes on Tvheadend (4.0.8), however, I get only "scan, no data".

Dec 28 14:25:46 omnibox2 tvheadend[2189]: mpegts: 506MHz in Cablecom - tuning on Sundtek DVB-C (III) : DVB-C #0
Dec 28 14:25:51 omnibox2 tvheadend[2189]: subscription: 0073: "scan" subscribing to mux "506MHz", weight: 2, adapter: "Sundtek DVB-C (III) : DVB-C #0", network: "Cablecom", service: "Raw PID Subscription" 
Dec 28 14:25:51 omnibox2 tvheadend[2189]: mpegts: 506MHz in Cablecom - scan no data, failed
Dec 28 14:25:51 omnibox2 tvheadend[2189]: subscription: 0073: "scan" unsubscribing
Dec 28 14:26:01 omnibox2 tvheadend[2189]: mpegts: 306MHz in Cablecom - tuning on Sundtek DVB-C (III) : DVB-C #0
Dec 28 14:26:06 omnibox2 tvheadend[2189]: subscription: 0075: "scan" subscribing to mux "306MHz", weight: 2, adapter: "Sundtek DVB-C (III) : DVB-C #0", network: "Cablecom", service: "Raw PID Subscription" 
Dec 28 14:26:06 omnibox2 tvheadend[2189]: mpegts: 306MHz in Cablecom - scan no data, failed
Dec 28 14:26:06 omnibox2 tvheadend[2189]: subscription: 0075: "scan" unsubscribing

I really have no idea, what the problem could be. I have the card enabled on the right network. All data on the muxes are 100% identical to mumudvb. Why don't I get any data on tvheadend?


Replies (12)

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by Mark Clarkstone almost 9 years ago

You're not using AUTO at all for any values?

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by Markus Rechberger (Sundtek) almost 9 years ago

you can check the transponder parameters with following command:

/opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0

I guess the modulation or symbol rate differs between your mumudvb and tvheadend setup

(in case you are using openelec you might strip /opt/bin and only use mediaclient)

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by saen acro almost 9 years ago

@ Markus Rechberger

mediaclient is from witch application ?

usualy FEMON do information

sudo femon -H -a 3 -f 0
FE: TurboSight TBS 6981 DVBS/S2 frontend (DVBS)
status SCVYL | signal  74% | snr  99% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  74% | snr  99% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  74% | snr  99% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  74% | snr  99% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  74% | snr  99% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  74% | snr  98% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  74% | snr  99% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  74% | snr  99% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  74% | snr  99% | ber 0 | unc 0 | FE_HAS_LOCK

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by Markus Rechberger (Sundtek) almost 9 years ago

mediaclient is part of the sundtek driver package, a swiss army knife for handling sundtek dvb tuners.

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by Michael B. almost 9 years ago

Sorry guys for the late answer. Strangely, all the email notifications for your answers went into my SPAM folder, while the original one (from my own posting) did not.

Thanks a lot for helping. I would really like to get tvheadend working as I like it alot.

I will see, if I can get any more debug information (e.g. from mediaclient or femon. So far, I can only say that mumudvb gives very good video and audio, while tvheadend does not find any muxes. It would be great to find out, what the problem is...

I will also list all settings that I am using. Maybe something is wrong here.

Thanks

Michael

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by Michael B. almost 9 years ago

So, here is the configuration attached

4.0.8.tar.bz2 (3.57 KB) 4.0.8.tar.bz2

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by Michael B. almost 9 years ago

here is the output of mediaclient while tvheadend is scanning:

/opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [.............................    ] ( 88%)  BER:      0 FREQ: 306000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM64
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256

The signal on the two muxes seems to be good, right?

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by Michael B. almost 9 years ago

Some more experiments with mediaclient.

If I stop mediaclient and configure manually with mediaclient, I get:

# /opt/bin/mediaclient -m DVBC -f 506000000 -S 6900000 -M Q256
Using device: /dev/dvb/adapter0/frontend0
Checking for lock:
. [LOCKED]

# /opt/bin/mediaclient --readsignal=10 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256

# /opt/bin/mediaclient --tsscan /dev/dvb/adapter0/dvr0
PMT PID: 0x0064
  Program Number: 0x234c
  TransportstreamID: 90
  Encrypted: No
  Service running: Yes
  Provider Name: upc
  Service Name: ORF eins HD
    --> 0x0050 (27)
    --> 0x0052 (ISO/IEC 13818-3 Audio)
    --> 0x005b (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x006e (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x0070 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
PMT PID: 0x00a4
  Program Number: 0x234d
  TransportstreamID: 90
  Encrypted: No
  Service running: Yes
  Provider Name: upc
  Service Name: ORF 2 HD
    --> 0x0090 (27)
    --> 0x009b (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x00ae (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x00b0 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
PMT PID: 0x00e4
  Program Number: 0x2354
  TransportstreamID: 90
  Encrypted: No
  Service running: Yes
  Provider Name: upc
  Service Name: BR Sd HD
    --> 0x00d0 (27)
    --> 0x00d1 (ISO/IEC 11172 Audio)
    --> 0x00d2 (ISO/IEC 11172 Audio)
    --> 0x00db (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x00ee (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x00f0 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
Total found: 3 PMTs (incl. unknown 0x0000)
Scan finished after 1501 packets (282188 bytes)

When tvheadend is running, there is always "LOCKED: NO" and mediaclient does not get any scan data:

/opt/bin/mediaclient --readsignal=10 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256
SIGNAL: [...............................  ] ( 93%)  BER:      0 FREQ: 506000000  Hz LOCKED:  NO SYM: 6900 MOD: QAM256

/opt/bin/mediaclient --tsscan /dev/dvb/adapter0/dvr0
Timed out after 10 seconds
Total found: 0 PMTs (incl. unknown 0x0000)
Scan finished after 0 packets (0 bytes)

Not sure, if that means anything important. It is clear, however, that there are channels on these frequencies and the signal strength is not bad either. So why don't I get anything in tvheadend?

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by Markus Rechberger (Sundtek) almost 9 years ago

You can see that the symbolrate is wrong 6900 it should be 6900000. Update your tvheadend transponder setting and it should work.

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by saen acro almost 9 years ago

I tested with old Toshiba Qosmio DVB-T tuner and TVH Not connect
in same time with mumudvb 68% and no problems.
Also test with DVB-S2 tunner behind multiswith and diseq on my stb to satelites same signal level,
only one of sattelites tuned with TVH image with Neutrino no problem Enigma also.
Maby TVH read some values not from correct place!

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by Markus Rechberger (Sundtek) almost 9 years ago

saen acro:
please write a new post, your issue is completely unrelated to the initial issue here. Also you are using DVB-S/S2 and a totally different tuner (not Sundtek Brand, so I can't support that)
This Bugreport is about DVB-C and using the wrong symbolrate.

RE: Tvheadend: "scan, no data" - mumudvb: no problem - Added by Michael B. almost 9 years ago

Thanks Markus!

Indeed, such a stupid mistake. And I haven't even noticed that at all, although I typed all that in.

It's working now. Good. Hope to be able to get some TV streaming over new year.

Have a Happy New Year!!!!

Michael

    (1-12/12)