Page 1 of 2

Scan failures

PostPosted: Tue Sep 07, 2010 9:08 am
by jimlas53
Running Ubuntu 10.04, MythTV. Built and installed the latest drivers, V1.92.2. During Mythbackend setup, I try to scan a satellite, but the scan fails. I know the sat setup is OK, I have a working sat receiver and am pointed at the right sat, good signal and all.
Using scan-s2, it returns this:

doug@htpc:/shared/tbs6981$ scan-s2 ses1-101w
API major 5, minor 1
ERROR: Cannot open rotor configuration file 'rotor.conf'.
scanning ses1-101w
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
main:3021: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 16 Device or resource busy

Any ideas?

Re: Scan failures

PostPosted: Tue Sep 07, 2010 2:25 pm
by cody
hi, i saw your mail to the support e-mail address too. so, do you prefer to discuss here or via e-mails?

Re: Scan failures

PostPosted: Tue Sep 07, 2010 6:28 pm
by jimlas53
Posting here might be helpful to someone else.
Thanks for responding!

Re: Scan failures

PostPosted: Wed Sep 08, 2010 5:55 am
by jimlas53
With Mythtv-backend NOT running, this is the result of scan:

doug@htpc:/shared/tbs6981$ scan -5 -U -l 10750 ses1-101w
scanning ses1-101w
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 12060000 H 26700000 3
>>> tune to: 12060:h:0:26700
DVB-S IF freq is 1310000
WARNING: >>> tuning failed!!!
>>> tune to: 12060:h:0:26700 (tuning failed)
DVB-S IF freq is 1310000
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.

Trying scan-s2 next...

Re: Scan failures

PostPosted: Wed Sep 08, 2010 5:59 am
by cody
as you suggested in your mail, let's do it step-by-step and first rule out that the driver is working correctly and board hardware is functioning OK.

so, please, try 'szap-s2' with creating simple configuration file with only few lines as it's explained in 'README' file that is included in Linux driver package for TBS 6981. after you try to lock with 'szap-s2' no matter if you got successful lock or not check the output of 'dmesg | grep tbs6981fe' and post it here.

thanks,
cody

Re: Scan failures

PostPosted: Wed Sep 08, 2010 8:19 am
by jimlas53
I'm having trouble creating a usable file. The satellite is SES1 at 101W, or Galaxy19 at 97W.

Re: Scan failures

PostPosted: Wed Sep 08, 2010 3:15 pm
by cody
jimlas53 Wrote:I'm having trouble creating a usable file. The satellite is SES1 at 101W, or Galaxy19 at 97W.


ok, no problem, i will create one for you, but please tell me some channel there that you know for sure you can receive and it's with strong signal, otherwise we risk to introducing mistakes in the test and get false results.

Re: Scan failures

PostPosted: Wed Sep 08, 2010 7:39 pm
by jimlas53
From lyngsat website, ses1.html:

12060 V, TP18, "History East". I have a Geosatpro DSR200c receiver and this channel comes in with good signal (75) and quality (90).

Re: Scan failures

PostPosted: Thu Sep 09, 2010 3:35 pm
by cody
jimlas53 Wrote:From lyngsat website, ses1.html:

12060 V, TP18, "History East". I have a Geosatpro DSR200c receiver and this channel comes in with good signal (75) and quality (90).


thanks, now let's go to the actual test:

1. create text file "channels.conf" with the following line:

HEST:12060:h:0:26700:1210:1200:12

2. lock to the transponder with using 'szap-s2':

./szap-s2 -c channels.conf -p -r -S 0 "HEST"

please, let me know your LNB type, because the above command is for Universal LNB, which is with 9750/10600/11700MHz respectively for low-band LOF (Local Oscillator Frequency), high-band LOF and Switch frequency. so, if you use different type of LNB you maybe will need to use command line like this:

./szap-s2 -c channels.conf -p -r -S 0 "HEST" -l 10700,10700,11700

for exaple if you have LNB with only one Local Oscillator Frequency of 10700 MHz.

Re: Scan failures

PostPosted: Thu Sep 09, 2010 7:39 pm
by jimlas53
Single LNB, 10750 LO, no switches
Thanks for the information, I'll give it a run.