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

Ricks Satellite Forum Header Ad
This Forum is Brought to you by "Ricks Satellite"
www.RicksSatelliteUSA.com or www.GoFastMotorsports.com or call 816-228-1801
Your US Supplier for Free To Air Digital Receivers, Feed Horns, LNB's & LNBF's, Venture Made in the USA Actuator Arms and many other products!

"Coming Soon... The NEW SX88 Octagon H.265 HEVC HD DVB-S2 Multistream Satellite Receiver!"
Ricks Satellite Wildfeed and Backhaul Forum
Register Latest Topics
 
 
 


Reply
  Author   Comment  
Mounir

Registered:
Posts: 117
Reply with quote  #1 
hi all
i would like to report an issue : 
i have installed v4l-updatelee  and dvbnoop-1.4.50 

dvbsnoop configuration :
sudo ./configure CPPFLAGS=-I/usr/src/v4l-updatelee/include/uapi/linux/dvb/


output of dvbsnoop :

sudo /usr/local/bin/dvbsnoop -s feinfo -frontend /dev/dvb/adapter0/frontend0
dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/

---------------------------------------------------------
FrontEnd Info...
---------------------------------------------------------

Device: /dev/dvb/adapter0/frontend0

Basic capabilities:
Name: "STV090x Skystar 2 Express HD"
Frontend-type: QPSK (DVB-S)
Frequency (min): 950.000 MHz
Frequency (max): 2150.000 MHz
Frequency stepsiz: 0.000 MHz
Frequency tolerance: 0.000 MHz
Symbol rate (min): 1.000000 MSym/s
Symbol rate (max): 45.000000 MSym/s
Symbol rate tolerance: 0 ppm
Notifier delay: 0 ms
Frontend capabilities:
auto inversion
FEC AUTO
QPSK

Current parameters:
Frequency: 0.000 MHz
Inversion: OFF
Symbol rate: 0.000000 MSym/s
FEC: none

dvbsnoop does not recognize dvb-s2 and multistrean capabilities ...
is sometthing wrong ?

Thank You


Mounir


__________________
Special Thanks to Mr Rick Caylor
DarkSky

Avatar / Picture

Registered:
Posts: 2,398
Reply with quote  #2 
I know nothing about dvbsnoop but I tuned my prof 7301 and my Geniatech HDStar with tune-s2 and replicated your command and I get varied results between the 2 devices. The Geniatech HDStar seems to show more info but as you not all info is reported on either device under "Frontend capabilities" and the prof 7301 does not report any "Current parameters". The 7301 does not report any "Frequency tolerance" and the Geniatech HDStar does:

Prof 7301:

Code:

[ray@arch ~]$ dvbsnoop -s feinfo -frontend /dev/dvb/adapter1/frontend0
dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/ 
---------------------------------------------------------
FrontEnd Info...
---------------------------------------------------------
Device: /dev/dvb/adapter1/frontend0
Basic capabilities:
    Name: "STV090x Prof 7301"
    Frontend-type:       QPSK (DVB-S)
    Frequency (min):     950.000 MHz
    Frequency (max):     2150.000 MHz
    Frequency stepsiz:   0.000 MHz
    Frequency tolerance: 0.000 MHz
    Symbol rate (min):     1.000000 MSym/s
    Symbol rate (max):     45.000000 MSym/s
    Symbol rate tolerance: 0 ppm
    Notifier delay: 0 ms
    Frontend capabilities:
        auto inversion
        FEC AUTO
        QPSK
Current parameters:
    Frequency:  0.000 MHz
    Inversion:  OFF
    Symbol rate:  0.000000 MSym/s
    FEC:  none

Geniatech HDStar:

Code:

[ray@arch dvbsnoop-1.4.50]$ dvbsnoop -s feinfo -frontend /dev/dvb/adapter2/frontend0 
dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/ 
---------------------------------------------------------
FrontEnd Info...
---------------------------------------------------------
Device: /dev/dvb/adapter2/frontend0
Basic capabilities:
    Name: "Montage Technology M88DS3103"
    Frontend-type:       QPSK (DVB-S)
    Frequency (min):     950.000 MHz
    Frequency (max):     2150.000 MHz
    Frequency stepsiz:   0.000 MHz
    Frequency tolerance: 5.000 MHz
    Symbol rate (min):     1.000000 MSym/s
    Symbol rate (max):     45.000000 MSym/s
    Symbol rate tolerance: 0 ppm
    Notifier delay: 0 ms
    Frontend capabilities:
        auto inversion
        FEC 1/2
        FEC 2/3
        FEC 3/4
        FEC 4/5
        FEC 5/6
        FEC 6/7
        FEC 7/8
        FEC AUTO
        QPSK
Current parameters:
    Frequency:  969.000 MHz
    Inversion:  ON
    Symbol rate:  30.000000 MSym/s
    FEC:  FEC 5/6


The extra C++ flags were not necessary and if they were I would have pointed it to /usr/include/linux/dvb/ for a user space app. A program like majortom's dvb-apps would have errored out compiling because kernel space headers are not sanitized for user space apps. Some do not need sanitizing like frontend.h but some do. Example when I try to compile dvb-apps and it is trying to use the unsantized kernel space header file video.h (I copied over the kernel space headers to /usr/include/linux/dvb/) :

error.png
midwestmac

Registered:
Posts: 2,294
Reply with quote  #3 
I don't know mounir you could try crazycats  dvbsnoop from his bitbucket. It was working with v4l-updatelee a while ago with TBS 5925 and 6925.

https://bitbucket.org/CrazyCat/dvbsnoop

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

Avatar / Picture

Registered:
Posts: 5,169
Reply with quote  #4 
Quote:
Originally Posted by Mounir
dvbsnoop does not recognize dvb-s2 and multistrean capabilities ...

is sometthing wrong ?



No, nothing is wrong. dvbsnoop is an old application...
To test that hypothesis, boot in to a stock kernel.
Recompile dvbsnoop or install it from a package manager.

rerun dvbsnoop and you'll likely see the same or similar output from the feinfo
command. Let us know your result when you have done that.



__________________
Perfect 10 7.5' mesh Chapparal C/Ku Co-Rotor feed, Norsat 8115 CBAND, Norsat 4106A Ku Thomson Saginaw Actuator, Vbox positioner,
Home Brew Polarotor683 Servo circuit. Openbox S9, Prof7500, v4l-updatelee linux drivers installed.
ricardo's geo-orbit archive: https://web.archive.org/web/20071202191450/http://www.geo-orbit.org:80/sizepgs/tuningp2.html
majortom

Avatar / Picture

Registered:
Posts: 5,169
Reply with quote  #5 
Any program that is using the  fe_get_info  ioctl is merely reporting what the frontend driver
author has defined in the .info array / struct (not a programmer, so whatever...) of the corresponding driver. Usually found near the end
of the corresponding frontend source code. The application using the fe_get_info ioctl may or may not want to utilise everything
that is in the .info struct. Depends what the application author wanted to use the information for in the first place. And that may vary from one application to the next.

https://www.linuxtv.org/docs/dvbapi/DVB_Frontend_API.html#SECTION003211000000000000000
snippets:
Code:
stv0900_core.c
        .info = {
                .name                   = "STV0900 frontend",
                .frequency_min          = 950000,
                .frequency_max          = 2150000,
                .frequency_stepsize     = 125,
                .frequency_tolerance    = 0,
                .symbol_rate_min        = 1000000,
                .symbol_rate_max        = 45000000,
                .symbol_rate_tolerance  = 500,
                .caps                   = FE_CAN_FEC_1_2 | FE_CAN_FEC_2_3 |
                                          FE_CAN_FEC_3_4 | FE_CAN_FEC_5_6 |
                                          FE_CAN_FEC_7_8 | FE_CAN_QPSK    |
                                          FE_CAN_2G_MODULATION |
                                          FE_CAN_FEC_AUTO
        },


stv090x.c
        .info = {
                .name                   = "STV090x Multistandard",
                .frequency_min          = 950000,
                .frequency_max          = 2150000,
                .frequency_stepsize     = 0,
                .frequency_tolerance    = 0,
                .symbol_rate_min        = 1000000,
                .symbol_rate_max        = 45000000,
                .caps                   = FE_CAN_INVERSION_AUTO |
                                          FE_CAN_FEC_AUTO       |
                                          FE_CAN_QPSK           |
                                          FE_CAN_2G_MODULATION  |
                                          FE_HAS_EXTENDED_CAPS
        },

m88ds3013.c
        .info = {
                .name = "Montage Technology M88DS3103",
                .frequency_min =  950000,
                .frequency_max = 2150000,
                .frequency_tolerance = 5000,
                .symbol_rate_min =  1000000,
                .symbol_rate_max = 45000000,
                .caps = FE_CAN_INVERSION_AUTO |
                        FE_CAN_FEC_1_2 |
                        FE_CAN_FEC_2_3 |
                        FE_CAN_FEC_3_4 |
                        FE_CAN_FEC_4_5 |
                        FE_CAN_FEC_5_6 |
                        FE_CAN_FEC_6_7 |
                        FE_CAN_FEC_7_8 |
                        FE_CAN_FEC_8_9 |
                        FE_CAN_FEC_AUTO |
                        FE_CAN_QPSK |
                        FE_CAN_RECOVER |
                        FE_CAN_2G_MODULATION |
                        FE_HAS_EXTENDED_CAPS
        },


__________________
Perfect 10 7.5' mesh Chapparal C/Ku Co-Rotor feed, Norsat 8115 CBAND, Norsat 4106A Ku Thomson Saginaw Actuator, Vbox positioner,
Home Brew Polarotor683 Servo circuit. Openbox S9, Prof7500, v4l-updatelee linux drivers installed.
ricardo's geo-orbit archive: https://web.archive.org/web/20071202191450/http://www.geo-orbit.org:80/sizepgs/tuningp2.html
Mounir

Registered:
Posts: 117
Reply with quote  #6 
thank u gentelmen ...now it is solved with dvbnoop from https://bitbucket.org/CrazyCat/dvbsnoop
 it reports :


Device: /dev/dvb/adapter0/frontend0

Basic capabilities:
Name: "STV090x Skystar 2 Express HD"
Frontend-type: QPSK (DVB-S)
Frequency (min): 950.000 MHz
Frequency (max): 2150.000 MHz
Frequency stepsiz: 0.000 MHz
Frequency tolerance: 0.000 MHz
Symbol rate (min): 1.000000 MSym/s
Symbol rate (max): 45.000000 MSym/s
Symbol rate tolerance: 0 ppm
Notifier delay: 0 ms
Frontend capabilities:
auto inversion
FEC AUTO
QPSK
multistream

Current parameters:
Frequency: 0.000 MHz
Inversion: OFF
Symbol rate: 0.000000 MSym/s
FEC: none


__________________
Special Thanks to Mr Rick Caylor
DarkSky

Avatar / Picture

Registered:
Posts: 2,398
Reply with quote  #7 
All stayed the exact same here on my devices as the original git version reports.
crazycat

Avatar / Picture

Registered:
Posts: 1,054
Reply with quote  #8 
Multistream capability report
__________________
Strong offset dish 0.95m on Powertech DG240 motor + ALPS BSTE8-751B Ku-Universal LNB. Variant CA-902 0.95 offset dish with 3xDreamSat DS-8 Ku-Universal LNBs (13E+4.8E+4W) + Variant CA-600 Ku-Circular LNB 36E + DiseqC 1.0. STB: GI8120 Lite. PC DVB: Omicom S2 PCI; TBS 6983 PCI; TBS QBox-CI USB(5980), 5927.
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.

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!