Welcome to GOFASTMOTORSPORTS.com ... ... ... Green Flag - Green Flag - Go Go Go ... ... Brought to you by Ricks Satellite - Where the Big Dish Rules!

Ricks Satellite Wildfeed and Backhaul Forum
Register Latest Topics
 
 
 


Reply
  Author   Comment   Page 2 of 3      Prev   1   2   3   Next
pendragon

Registered:
Posts: 1,003
Reply with quote  #16 

Midwestmac - in post #1 the out of range error is occurring because the driver is getting a tuning request for 106.390 MHz, instead of something in the range of 940-2150 MHz. The reason you are having problems with blindscan-s2 is it wants to send frequencies to the driver in KHz, but my drivers are expecting Hz. There is also the complicating factor that a 32-bit signed integer cannot handle the full RF and L-band ranges in Hz. Wraparounds caused by adding the "extra zeros" may sort of get frequencies into a meaningful range for the driver, but they are unlikely what you intended.

Taking a quick look at blindscan-s2.c, you can probably solve this particular problem by changing:

{ .cmd = DTV_FREQUENCY, .u.data = tpfreq },

to:

{ .cmd = DTV_FREQUENCY, .u.data64 = tpfreq * 1000L },

and recompiling it. This should convert the 32-bit integer frequency in KHz to a 64-bit integer frequency in Hz. Then you can specify the LOF to blindscan-s2 as 10600, and the start and stop frequencies as 11700 and 12200. You may need to change other code to properly report what it finds, but this should at least solve the initial out of range problem.

midwestmac

Registered:
Posts: 2,239
Reply with quote  #17 
Thankyou Pendragon, that worked! Problem solved. You're right there's more fixing to do to the App.
I was trying to fix it another way but, you got me on track.
Thanks!

__________________
Azbox Ultra, Pansat 2500, Prof7301,Tbs 6925,5980, Genpix 8psk card, Dektec 2137c, Hauppauge 950q
Richard

Registered:
Posts: 40
Reply with quote  #18 
Quote:
Originally Posted by pendragon

....Features such as the spectrum capture are also presented through this interface, and I even added a capability to command the FlexPorts present on some of the DirecTV-compatible multiswitches. 

....Some of these changes are also present in the stv0910 driver I wrote, but I haven't uploaded a more completed version.


@Pendragon,

Am I right in thinking that you haven't added spectrum capture to the stv0910 driver, due to using your stv0900 based cards for this task, rather than any hardware related shortcoming with the stv0910 chip?

Regards,

Richard
pendragon

Registered:
Posts: 1,003
Reply with quote  #19 
Richard - you're precisely correct. All of my STV0910 cards are busy receiving signals, because of the somewhat more finished nature of their hardware. I still also use my STV0900 cards for that purpose, but they are less busy and some are always available for high-speed blindscanning, spectrum captures, etc. I have found nothing inherent in the STV0910 hardware that would preclude them from also serving these functions, and in fact I have pretty much all of these capabilities working in a prototype fashion. There simply hasn't been a pressing need to finish that project, and many others are time critical.

I don't have a "to do" list for what is missing with STV0910, but I believe the explanded DiSEqC support, which would include the ability to command FlexPort inputs, should already be there.

One thing that irks me about the STV0910 cards, which are all TBS, is the crystals are horrible. This makes the precision measurements I sometimes perform using STV0900 cards not very practical with the STV0910 cards. I suppose I could replace the crystals, or at least calibrate them, but I need to first find the time to characterize their phase noise and stability. I have no hard evidence that either is a problem, but my gut feeling isn't particularly comfortable.
Richard

Registered:
Posts: 40
Reply with quote  #20 
Quote:
Originally Posted by pendragon

One thing that irks me about the STV0910 cards, which are all TBS, is the crystals are horrible. This makes the precision measurements I sometimes perform using STV0900 cards not very practical with the STV0910 cards. I suppose I could replace the crystals, or at least calibrate them, but I need to first find the time to characterize their phase noise and stability. I have no hard evidence that either is a problem, but my gut feeling isn't particularly comfortable.


Thanks for the reply.

If you haven't already seen them and wanted to check out other stv0910 based cards, you might like to check out:

https://digitaldevices.de/products/dvb_components/cine_s2_v7/

and their quad/octo siblings.

I have just bought the Cine S2 V7A and it seems a nicely made card and somewhat cheaper than it's TBS 6903 equivalent. It also has the bonus of being able to add extra dual tuner DVB-S/T/C modules as required.

The official DD driver is here:

https://github.com/DigitalDevices

with Crazycat fork here:

https://github.com/crazycat69/dddvb

Neither of these drivers play well with other DVB cards though, so if this is required, there are modified versions of these drivers that do here:

https://github.com/herrnst/dddvb-linux-kernel

I've been testing this last driver for Daniel and he will shortly be submitting it for official Linux media blessing to go into the kernel.

I realise this driver info is redundant in your situation, but include it for anyone else interested.

Regards,

Richard
midwestmac

Registered:
Posts: 2,239
Reply with quote  #21 
with the blindscan-s2 app
Here's what I've done so far fixed the SNR.
I can't figure this out YET! had to commit this out otherwise it post an error "FE_READ_STATUS failed" in between each step scanning each transponder
Code:

//        if (ioctl(fefd, FE_READ_STATUS, &status) == -1) {
//        perror("FE_READ_STATUS failed");
//    }


So now I get this when blindscanning ses3 ku not bad. Thought I'd show off [smile]
jim@jim-System-Pendragon ~/oldblindscan-s2 $ blindscan-s2 -b -l 10600 -2 -s 11700 -H -d 6 -t 5
11762 H 30000 SIG 82.9 % SNR 17.1 dB DVB-S2 8PSK FEC_AUTO INV_ON  PIL_ON  ROL_20
11845 H 4600  SIG 79.7 % SNR 11.8 dB DVB-S2 8PSK FEC_7_8  INV_ON  PIL_ON  ROL_25
11851 H 5600  SIG 80.3 % SNR 9.6 dB DVB-S2 QPSK FEC_NONE INV_ON  PIL_OFF ROL_35
11882 H 30000 SIG 83.0 % SNR 16.0 dB DVB-S2 8PSK FEC_AUTO INV_ON  PIL_ON  ROL_20
11845 H 4600  SIG 79.7 % SNR 12.0 dB DVB-S2 8PSK FEC_7_8  INV_ON  PIL_ON  ROL_25
11851 H 5600  SIG 80.4 % SNR 9.9 dB DVB-S2 QPSK FEC_NONE INV_ON  PIL_OFF ROL_35
11882 H 30000 SIG 83.0 % SNR 15.9 dB DVB-S2 8PSK FEC_AUTO INV_ON  PIL_ON  ROL_20
11857 H 4599  SIG 79.8 % SNR 9.6 dB DVB-S2 8PSK FEC_7_8  INV_ON  PIL_ON  ROL_25
11882 H 30000 SIG 83.0 % SNR 15.7 dB DVB-S2 8PSK FEC_AUTO INV_ON  PIL_ON  ROL_20
11999 H 4600  SIG 80.2 % SNR 15.4 dB DVB-S2 8PSK FEC_7_8  INV_ON  PIL_ON  ROL_25
12005 H 4600  SIG 80.2 % SNR 12.5 dB DVB-S2 8PSK FEC_7_8  INV_ON  PIL_ON  ROL_25
11999 H 4600  SIG 80.2 % SNR 15.6 dB DVB-S2 8PSK FEC_7_8  INV_ON  PIL_ON  ROL_25
12005 H 4600  SIG 80.2 % SNR 11.9 dB DVB-S2 8PSK FEC_7_8  INV_ON  PIL_ON  ROL_25
12011 H 4599  SIG 79.7 % SNR 12.1 dB DVB-S2 8PSK FEC_7_8  INV_ON  PIL_ON  ROL_25
12017 H 4600  SIG 79.4 % SNR 10.2 dB DVB-S2 8PSK FEC_7_8  INV_ON  PIL_ON  ROL_25
12005 H 4600  SIG 80.2 % SNR 11.7 dB DVB-S2 8PSK FEC_7_8  INV_ON  PIL_ON  ROL_25
12051 H 4600  SIG 79.2 % SNR 8.4 dB DVB-S2 8PSK FEC_7_8  INV_ON  PIL_ON  ROL_25

I think I need to fix the FEC_7_8, too I don't think thats right
Oh and fix the transponders found twice

__________________
Azbox Ultra, Pansat 2500, Prof7301,Tbs 6925,5980, Genpix 8psk card, Dektec 2137c, Hauppauge 950q
pendragon

Registered:
Posts: 1,003
Reply with quote  #22 

Look's like you're making good progress. A few suggestions:

1. As you discovered, the ioctl(fefd, FE_READ_STATUS, &status) call in the getinfo routine serves no purpose and is ambiguous because you might get a status back while the driver is still looking for a signal. But see #2 and #3.

2. I would suggest adding a DTV_SCAN_WAIT to the start of the getinfo property list. This will wait for the driver to complete looking for a signal before returning any properties it has discovered. As soon as the driver locks a signal or gives up, it will return, but not before. That way you can remove all but one of the calls to getinfo in the blindscan routine, and all of the usleep(s) after the call to tune. This should speed up your scanning.

3. You might want to add a DTV_STATUS property to your getinfo list. That way you can check if the signal was partially or completely locked. See "enum fe_status" in the system frontend.h include file for the bit masks for each of the possibilities. There are more than in the vanilla interface.

4. Remove the two calls to:

ioctl(fefd, FE_READ_SIGNAL_STRENGTH, &signal);
ioctl(fefd, FE_READ_SNR, &snr);

and add two new properties to your getinfo list: DTV_SIGNAL_LEVEL and DTV_CNR. The return values are in units of dB * 1024, so you'll probably do something like:

float level = cmdseq.props[x].u.data / 1024.0;
float cnr = cmdseq.props[y].u.data / 1024.0;

where x & y are the appropriate indices in the restructured cmdseq list.

As you see, one can get all of the parameters back in a single system call, rather than having to make multiple ioctls for individual parameters.

5. To get the correct FEC ratios, change the "switch (dtv_inner_fec_prop)" to use the symbolic names in "enum fe_code_rate" in the frontend.h system include. For example:

case FEC_NONE: printf("FEC_NONE "); break;
case FEC_1_4: printf("FEC_1_4 "); break;

6. If you get a lock on a signal, you should step the next scanned frequency to go beyond its bandwidth, or otherwise you will likely get the repeats you saw. For example, let's say you are stepping every x MHz when no signal is found. If the blindscan detects a signal at frequency f and a SR of sr, the next scanned frequency should be something like f + (sr * (1.0 + rolloff)) / 2.0 + x, where rolloff is either 0.2, 0.25, or 0.35 (see "enum fe_rolloff" for property DTV_ROLLOFF). That way the next scan should be much less likely to lock the same signal, and run faster. It may still be a good idea to check the frequency/sr values against the previous detect, within some error margin.

midwestmac

Registered:
Posts: 2,239
Reply with quote  #23 
Thanks pendragon, that will help and should be easy to add.
I have to say, I think your driver is going to work very well just from what I've seen so far on some of the signals it finds.

I saw your post earlier and just got home to add this in.
Thankyou!

__________________
Azbox Ultra, Pansat 2500, Prof7301,Tbs 6925,5980, Genpix 8psk card, Dektec 2137c, Hauppauge 950q
midwestmac

Registered:
Posts: 2,239
Reply with quote  #24 
I'm still playing around with the blindscan-s2 app getting a little closer. I think?


Thanks Majortom here's the the link.
 
https://bitbucket.org/Midwestmac/v4l-pendragon

__________________
Azbox Ultra, Pansat 2500, Prof7301,Tbs 6925,5980, Genpix 8psk card, Dektec 2137c, Hauppauge 950q
midwestmac

Registered:
Posts: 2,239
Reply with quote  #25 
Here's the blinscan-s2.c I've been playing with I tried some of pendragons suggestions. I borrowed some of UDL/Majortoms code also as far as the "float lvl scale". Tried adding 1024.0
Still can't figure out how to report signal in dbm or what I'm doing wrong.
I'm still playing with it. I'm not a programmer so...
It works pretty good if someone wants to try it, just copy raw and paste to a text file and name the file blindscan-s2.c
https://pastebin.com/HJ8d2v99

Code:

jim@jim-System-Pendragon ~/blindscan-s2 $ blindscan-s2 -b -l 10600 -2 -s 11700 -e 12200 -V -t 10
11726 V 2170  SIG 78.7 % SNR 9.7 dB DVB-S2 8PSK FEC_3_4  INV_ON  PIL_ON  ROL_25
11732 V 6700  SIG 79.0 % SNR 10.1 dB DVB-S2 8PSK FEC_3_4  INV_ON  PIL_ON  ROL_25
11832 V 2999  SIG 79.0 % SNR 8.5 dB DVB-S2 8PSK FEC_3_4  INV_ON  PIL_ON  ROL_25
11837 V 4350  SIG 79.1 % SNR 12.2 dB DVB-S2 8PSK FEC_3_4  INV_ON  PIL_ON  ROL_25
11857 V 5000  SIG 79.4 % SNR 14.5 dB DVB-S  QPSK FEC_1_2  INV_ON  PIL_OFF ROL_35
11877 V 5000  SIG 79.6 % SNR 14.0 dB DVB-S  QPSK FEC_1_2  INV_ON  PIL_OFF ROL_35
11956 V 6923  SIG 80.4 % SNR 13.2 dB DVB-S  QPSK FEC_5_6  INV_ON  PIL_OFF ROL_35
12013 V 13333 SIG 80.8 % SNR 13.9 dB DVB-S  QPSK FEC_3_4  INV_ON  PIL_OFF ROL_35




Also almost have tune-s2 working here's G17 ku ver
Code:

Tuning specs: 
System:     DVB-S 
Frequency:  12013 V 13333 
22khz:      ON 
Modulation: QPSK 
FEC:        AUTO 
Inversion:  AUTO 
Rolloff:    AUTO 
Pilot:      AUTO 
MIS:        -1 
Tuned specs: 
System:     DVB-S 5 
Frequency:  12013 V 13333 
22khz:      ON 
Modulation: QPSK 0 
FEC:        3/4 7 
Inversion:  ON 1 
Rolloff:    35 0 
Pilot:      ON 1 
MIS:        -1 
Bandwidth:  17.9996 MHz 
Data Rate:  18.4309 Mbps 
CN Failure: 7.2 dB 
status Locked | signal 78.3 % | snr 13.8 dB | ber 0 | FE_HAS_LOCK 
status Unlocked | signal 78.3 % | snr 13.8 dB | ber 0 | 


__________________
Azbox Ultra, Pansat 2500, Prof7301,Tbs 6925,5980, Genpix 8psk card, Dektec 2137c, Hauppauge 950q
pendragon

Registered:
Posts: 1,003
Reply with quote  #26 
Lines 452-476 should be:
Code:

        signal = sp_status.props[1].u.sdata / 1024.0;
        snr = sp_status.props[2].u.sdata / 1024.0;


Lines 577-578 should be:
Code:

        printf("SIG %5.1f dBm ", signal);
        printf("SNR %5.1f dB ", snr) ;
midwestmac

Registered:
Posts: 2,239
Reply with quote  #27 
Quote:
Originally Posted by pendragon
Lines 452-476 should be:
Code:
 signal = sp_status.props[1].u.sdata / 1024.0; snr = sp_status.props[2].u.sdata / 1024.0; 

Aha Thankyou!! thats just what I needed. I can't believe I deleted all of that and it works
better and faster. perfect.

One thing I like to do is if I open a terminal and do "tail -f 200 /var/log/kern.log"
then run the blindscan in another terminal I can watch the log as the driver finds signals
and determines if the modulation is known or unknown or sometimes I can see it stop at an rf level
to try and figure out the signal.
Of course it also finds some ACM signals that are switching modulation too and reports the MODCOD, if I slow down the step size it finds more of those types. I know I can't lock them with the prof 7301 but the driver is finding them.

Quote:
Lines 577-578 should be:
Code:
 printf("SIG %5.1f dBm ", signal); printf("SNR %5.1f dB ", snr) ; 

This worked!! and should help me with tune-s2 also.
Thanks again Pendragon everything you've posted has helped me and I'm learning more and more

__________________
Azbox Ultra, Pansat 2500, Prof7301,Tbs 6925,5980, Genpix 8psk card, Dektec 2137c, Hauppauge 950q
midwestmac

Registered:
Posts: 2,239
Reply with quote  #28 
I went ahead and pushed the changes to the blindscan-s2 app that I have here to Bitbucket.
also I edited the Makefile 'includes' for my setup.. so you might want to check the Makefile includes
There were some warnings about ' Diseqc.c. So in the Makefile I commited out the flag #CFLG=-O -g -W
https://bitbucket.org/Midwestmac/blindscan-s2/overview

I'm sure it could use some more tweaking but it works well I think.
If anyone wants to try it out.

I usually use the blindscan-s2 then if I see a feed I use Bluzee's dvbstream, and Tsreader w/wine installed to look at the signal

__________________
Azbox Ultra, Pansat 2500, Prof7301,Tbs 6925,5980, Genpix 8psk card, Dektec 2137c, Hauppauge 950q
Richard

Registered:
Posts: 40
Reply with quote  #29 
@Pendragon,

I wonder if you can offer some help? I'd very much like to use your stv0900 driver, but the only card I have based on this demod (TT S2 6400), uses the stv090x driver, so I need to change the saa716x_ff_main.c to suit your driver and having almost zero coding experience, I've come up with the following.

Apart from the obvious replacement of the stv090x header file at the top, there appears to be two functions that need modification, which I list below and I have added "-" and "+" on the left hand side for changes I believe need making, with "?" against original parts I'm unsure of.

-static struct stv090x_config tt6400_stv090x_config = {
+static struct stv0900_config tt6400_stv0900_config = {
?        .device                 = STV0900,
-        .demod_mode             = STV090x_DUAL,
+        .demod_mode             = 1,
-        .clk_mode               = STV090x_CLK_EXT,
+        .clkmode                = 2,

        .xtal                   = 13500000,
-        .address                = 0x68,
+        .demod_address          = 0x68,

?        .ts1_mode               = STV090x_TSMODE_SERIAL_CONTINUOUS,
?        .ts2_mode               = STV090x_TSMODE_SERIAL_CONTINUOUS,
?        .ts1_clk                = 135000000,
?        .ts2_clk                = 135000000,

?        .repeater_level         = STV090x_RPTLEVEL_16,

?        .tuner_init             = NULL,
?        .tuner_set_mode         = NULL,
?        .tuner_set_frequency    = NULL,
?        .tuner_get_frequency    = NULL,
?        .tuner_set_bandwidth    = NULL,
?        .tuner_get_bandwidth    = NULL,
?        .tuner_set_bbgain       = NULL,
?        .tuner_get_bbgain       = NULL,
?        .tuner_set_refclk       = NULL,
?        .tuner_get_status       = NULL,
};

Looking at your stv0900.h file, I suspect I also need to add at least:

tun1_auto = 1,
tun2_auto = 1,
tun1_type = STV0900_TUNER_STV6110,
tun2_type = STV0900_TUNER_STV6110,
tun1_clkdiv = 2,
tun2_clkdiv = 2,

The second function is:

static int saa716x_s26400_frontend_attach(struct saa716x_adapter *adapter, int c
ount)
{
        struct saa716x_dev *saa716x     = adapter->saa716x;
        struct saa716x_i2c *i2c         = saa716x->i2c;
        struct i2c_adapter *i2c_adapter = &i2c[SAA716x_I2C_BUS_A].i2c_adapter;

        dprintk(SAA716x_DEBUG, 1, "Adapter (%d) SAA716x frontend Init", count);
        dprintk(SAA716x_DEBUG, 1, "Adapter (%d) Device ID=%02x", count, saa716x-
>pdev->subsystem_device);

        if (count == 0 || count == 1) {
-                adapter->fe = dvb_attach(stv090x_attach,
+                adapter->fe = dvb_attach(stv0900_attach,
-                                         &tt6400_stv090x_config,
+                                         &tt6400_stv0900_config,
                                         i2c_adapter,
?                                         STV090x_DEMODULATOR_0 + count);

                if (adapter->fe) {
                        struct stv6110x_devctl *ctl;
                        ctl = dvb_attach(stv6110x_attach,
                                         adapter->fe,
                                         &tt6400_stv6110x_config,
                                         i2c_adapter);

?                        tt6400_stv090x_config.tuner_init          = ctl->tuner_init;
?                        tt6400_stv090x_config.tuner_sleep         = ctl->tuner_sleep;
?                        tt6400_stv090x_config.tuner_set_mode      = ctl->tuner_set_mode;
?                        tt6400_stv090x_config.tuner_set_frequency = ctl->tuner_set_frequency;
?                        tt6400_stv090x_config.tuner_get_frequency = ctl->tuner_get_frequency;
?                        tt6400_stv090x_config.tuner_set_bandwidth = ctl->tuner_set_bandwidth;
?                        tt6400_stv090x_config.tuner_get_bandwidth = ctl->tuner_get_bandwidth;
?                        tt6400_stv090x_config.tuner_set_bbgain    = ctl->tuner_set_bbgain;
?                        tt6400_stv090x_config.tuner_get_bbgain    = ctl->tuner_get_bbgain;
?                        tt6400_stv090x_config.tuner_set_refclk    = ctl->tuner_set_refclk;
?                        tt6400_stv090x_config.tuner_get_status    = ctl->tuner_get_status;

                        if (count == 1) {
                                /* call the init function once to initialize
                                   tuner's clock output divider and demod's
                                   master clock */
                                /* The second tuner drives the STV0900 so
                                   call it only for adapter 1 */
                                if (adapter->fe->ops.init)
                                        adapter->fe->ops.init(adapter->fe);
                        }

                        dvb_attach(isl6423_attach,
                                   adapter->fe,
                                   i2c_adapter,
                                   &tt6400_isl6423_config[count]);

                        if (adapter->fe->ops.sleep)
                                adapter->fe->ops.sleep(adapter->fe);
                }
        }
        return 0;
}


I  realise this is probably asking a bit much, but any assistence would be greatly appreciated, even if only pointing me at a suitable example of acheiving this elsewhere.

Kind regards (and apologies to the list for the length of this post),

Richard
pendragon

Registered:
Posts: 1,003
Reply with quote  #30 
Richard:

I'm very busy at the moment, so I'm sorry that I haven't been able to spend much time on this. However I did look through your notes and what follows are my best initial impressions. This may not be enough to get things to even compile, but I hope it gets you a little closer. We can always iterate on this along the way. One thing worth noting is I don't have any dual tuner STV090* cards, which means the dual tuner code has only been eyeball-tested.

(In saa716x_ff_main.c)

Fairly sure about these:
.demod_mode = STV0900_DUAL, // = 1
.clkmode = 2,
.xtal = 13500000,
.demod_address = 0x68,
.path1_mode = STV0900_SERIAL_CONT_CLOCK, // = 2
.path2_mode = STV0900_SERIAL_CONT_CLOCK, // = 2
tun1_auto = 1,
tun2_auto = 1,
tun1_type = STV0900_TUNER_STV6110,
tun2_type = STV0900_TUNER_STV6110,
.tuner_init = NULL,
.tuner_set_mode = NULL,
.tuner_set_frequency = NULL,
.tuner_get_frequency = NULL,
.tuner_set_bandwidth = NULL,
.tuner_get_bandwidth = NULL,
.tuner_set_bbgain = NULL,
.tuner_get_bbgain = NULL,
.tuner_set_refclk = NULL,
.tuner_get_status = NULL,

Wasn't able to verify these either way:
tun1_clkdiv = 2,
tun2_clkdiv = 2,

Others:
Don't set path1_clk or path2_clk, this provides auto speed control
I2C repeater is always off

(In saa716x_s26400_frontend_attach)

change:
STV090x_DEMODULATOR_0 + count);
to:
count);

delete:
struct stv6110x_devctl *ctl;
ctl = dvb_attach(stv6110x_attach,
adapter->fe,
&tt6400_stv6110x_config,
i2c_adapter);

tt6400_stv090x_config.tuner_init = ctl->tuner_init;
tt6400_stv090x_config.tuner_sleep = ctl->tuner_sleep;
tt6400_stv090x_config.tuner_set_mode = ctl->tuner_set_mode;
tt6400_stv090x_config.tuner_set_frequency = ctl->tuner_set_frequency;
tt6400_stv090x_config.tuner_get_frequency = ctl->tuner_get_frequency;
tt6400_stv090x_config.tuner_set_bandwidth = ctl->tuner_set_bandwidth;
tt6400_stv090x_config.tuner_get_bandwidth = ctl->tuner_get_bandwidth;
tt6400_stv090x_config.tuner_set_bbgain = ctl->tuner_set_bbgain;
tt6400_stv090x_config.tuner_get_bbgain = ctl->tuner_get_bbgain;
tt6400_stv090x_config.tuner_set_refclk = ctl->tuner_set_refclk;
tt6400_stv090x_config.tuner_get_status = ctl->tuner_get_status;

Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Fellow Members, your posts are welcome here! Do not worry about posting everything perfect. Different receivers and LNB's will give you different Frequencies and Symbol Rates. Some set top boxes, PCI cards and USB receivers, Do Not Require all of the same information that others may need. It is not Required to post everything that others may need to tune in a feed. It is just most important to share the find. We can always adjust the Frequency and Symbol Rates and try the various Modulations and FEC's on our own receivers until we get a lock and then give a polite reply with what works for your receiver, as that information might help others as well. We all appreciate the efforts and energy of the Posters!

Thank You for Visiting GOFASTMOTORSPORTS.com - Keep Your Eyes on the Sky and the Track!