Hobbyist Open Source Satellite Receiver - Raspberry Pi 2???

[jmc98]

It is the program that comes with the TEvii S662, called tevii player. I put in 10750,10750,10750. It is uses a standard Ku lnbf. I also tried 10750, blank, blank.

try this program smartDVB i had real good luck with it when i had my s662 and you can set it up like the pictures shown it is attached below
tevii player doesnt look as easy to setup and use as mytheater that they use to package with those tuners

 

[fred555]

Thanks I will try that too. Since when does Windows media player do this? That's nuts!

Its Windows, they have the Sat names wrong, I could have guessed that. haha

 

[jmc98]

Thanks I will try that too. Since when does Windows media player do this? That's nuts!

View attachment 105538

Its Windows, they have the Sat names wrong, I could have guessed that. haha

i dont know the when but i could only get it to scan a single sat when i tried it before

 

[fred555]

UPDATE:
TBS-5922 is now working on the Raspberrry Pi2! I will post the recipe soon. Had to fix a little code too.

Tbs attached clean as a whistle:

[  988.536875] usb 1-1.5: new high-speed USB device number 6 using dwc_otg
[  988.637658] usb 1-1.5: New USB device found, idVendor=734c, idProduct=5922
[  988.637683] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  988.637701] usb 1-1.5: Product: TBS 5922
[  988.637717] usb 1-1.5: Manufacturer: TBS-Tech
[  988.638772] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in cold state, will try to load a firmware
[  988.638800] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5922.fw'
[  988.638815] tbsqbox22: start downloading TBSQBOX firmware
[  988.766810] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in warm state.
[  988.767053] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  988.767295] DVB: registering new adapter (TBS QBOX22 DVBS2 USB2.0)
[  988.878871] dvb-usb: MAC address: 00:22:ab:c0:28:a3
[  988.880791] i2c i2c-2: Added multiplexed i2c bus 3
[  988.880961] i2c i2c-2: Added multiplexed i2c bus 4
[  989.022642] i2c i2c-4: av201x: Airoha Technology AV201x successfully attached
[  989.022671] QBOX22: TBS5922 attached.
[  989.023172] QBOX22: frontend attached
[  989.023207] usb 1-1.5: DVB: registering adapter 0 frontend 0 (Tmax TAS2101)...
[  989.024244] input: IR-receiver inside an USB DVB receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.5/input/input1
[  989.024520] dvb-usb: schedule remote query interval to 150 msecs.
[  989.024547] dvb-usb: TBS QBOX22 DVBS2 USB2.0 successfully initialized and connected.

From mumudvb, there are a few errors to figure out here but it is streaming to my Android tablet:

WARN:  Unicast :  You have enabled the support for HTTP Unicast. This feature is quite youg, please report any bug/comment
Info:  Main:  Full autoconfiguration, we activate PAT rewritting. if you want to deactivate it see the README.
Info:  Main:  Full autoconfiguration, we activate SDT rewritting. if you want to deactivate it see the README.
Info:  Main:  Full autoconfiguration, we activate sorting of the EIT PID. if you want to deactivate it see the README.
Info:  Main:  ========== End of configuration, MuMuDVB version 1.7.1 is starting ==========
Info:  Autoconf:  The autoconfiguration auto update is enabled. If you want to disable it put "autoconf_pid_update=0" in your config file.
WARN:  Logs:  saving_filename /var/run/mumudvb/mumudvb_generated_conf_card0_tuner0: No such file or directory
WARN:  Main:  Can't create /var/run/mumudvb/channels_streamed_adapter0_tuner0: No such file or directory
WARN:  Main:  Can't create /var/run/mumudvb/channels_unstreamed_adapter0_tuner0: No such file or directory
Info:  Main:  Streaming. Freq 12115000
Info:  Tune:  Using DVB card "Tmax TAS2101" tuner 0
Info:  Tune:  Tuning DVB-S to Freq: 1365000 kHz, LO frequency 10750000 kHz Pol:V Srate=22425000, LNB number: 0
Info:  Tune:  LNB voltage 13V
Info:  Tune:  DISEQC SETTING SUCCEDED
Info:  Tune:  FE_STATUS:
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:       FE_HAS_CARRIER : found a DVB signal
Info:  Tune:       FE_HAS_VITERBI : FEC is stable
Info:  Tune:       FE_HAS_SYNC : found sync bytes
Info:  Tune:       FE_HAS_LOCK : everything's working...
Info:  Tune:  Event:  Frequency: 12115000 (or 9385000)
Info:  Tune:          SymbolRate: 22420000
Info:  Tune:          FEC_inner:  3
Info:  Tune:  Bit error rate: 3
Info:  Tune:  Signal strength: 42118
Info:  Tune:  SNR: 70
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:       FE_HAS_CARRIER : found a DVB signal
Info:  Tune:       FE_HAS_VITERBI : FEC is stable
Info:  Tune:       FE_HAS_SYNC : found sync bytes
Info:  Tune:       FE_HAS_LOCK : everything's working...
Info:  Main:  Card 0, tuner 0 tuned
Info:  Unicast:  We open the Master http socket for address 192.168.0.117:5000
Info:  Autoconf:  Autoconfiguration Start
Info:  Autoconf:  Autoconfiguration done
Info:  Autoconf:  Diffusion 17 channels
Info:  Autoconf:  Channel number :   0, name : "Impact TV"  service id 1010
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :   1, name : "RTA AFGHANISTAN"  service id 1020
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :   2, name : "BETHEL TV"  service id 1030
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :   3, name : "ITC"  service id 1040
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :   4, name : "MEA TV"  service id 1050
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :   5, name : "Rang A Rang"  service id 1051
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :   6, name : "ASSYRIASAT TV"  service id 1060
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :   7, name : "RTVN"  service id 1070
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :   8, name : "TASVIR IRAN"  service id 1080
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :   9, name : "ASRE EMROOZ TV"  service id 1090
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :  10, name : "ETV CHANNEL"  service id 2000
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :  11, name : "Iran E Aryaee TV"  service id 2010
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :  12, name : "NEWS1"  service id 2020
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :  13, name : "THE UNIV. NETWORK"  service id 2040
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :  14, name : "CTVN"  service id 2050
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :  15, name : "REVN"  service id 2060
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000
Info:  Autoconf:  Channel number :  16, name : "EBS"  service id 2080
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 192.168.0.117:5000

 

[SatPhreak]

Thanks, fred555 for the hard work that's over my head. Time for me to order a pi2.

 

[fred555]

try this program smartDVB i had real good luck with it when i had my s662 and you can set it up like the pictures shown it is attached below
tevii player doesnt look as easy to setup and use as mytheater that they use to package with those tuners

Thanks,

I have the Tevii working in Windows now with your help, so I know its good and I just have more work to do on the Pi2.

 

[fred555]

Thanks, fred555 for the hard work that's over my head. Time for me to order a pi2.

You wont say that one you see the instructions!

 

[fred555]

Part I. Addendum
Additions to Part I. If you have already completed Part I, don't worry do these now.

Next time, Instead of make, run make -j4, it uses all cores and compiles much faster. I went from 4+ hours down to 1.5.
I forgot to make header files, you won't go far on the next steps without these:
cd /usr/src/linux-rpi-3.18.y
make headers_install
after rebooting into the new kernel type this to back up Kernel config:
cp /usr/src/linux-rpi-3.18.y/.config /usr/src/linux-rpi-3.18.y/.config.bak

 

[fred555]

Part II.
Installing TBS-5922 Drivers on the Pi2

I logon as root to avoid su and sudo.
Pi must have an Internet connection too.

# Add a few dependencies
apt-get install patchutils
cpan Proc::ProcessTable

#Tell the system where the Kernel source code is
export KERNEL_SRC=/usr/src/linux-rpi-3.18.y
Or
add to /root/.bashrc to make permanent across reboots (or to your user home directory if not root):
export KERNEL_SRC='/usr/src/linux-rpi-3.18.y'

reboot and check with command:
printenv
result:
...
KERNEL_SRC=/usr/src/linux-rpi-3.18.y
...

#Get the open source drivers
cd /root
git clone --depth=1 https://github.com/ljalves/linux_media.git -b latest ./media

#Fix some code so compile does not fail, although it still spits out a nonsensical warning about something else.
nano /root/media/drivers/media/dvb-frontends/tas2101.c

Comment the folowing as shown below (*/):
/*#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 7, 0)*/
#define TAS2101_USE_I2C_MUX
/*#endif*/

#Copy driver sources into kernel source directories
cp /root/media/drivers/media/dvb-frontends/tas2101.h /usr/src/linux-rpi-3.18.y/drivers/media/dvb-frontends
cp /root/media/drivers/media/dvb-frontends/tas2101.c /usr/src/linux-rpi-3.18.y/drivers/media/dvb-frontends
cp /root/media/drivers/media/dvb-frontends/tas2101_priv.h /usr/src/linux-rpi-3.18.y/drivers/media/dvb-frontends
cp /root/media/drivers/media/usb/dvb-usb/tbs-qbox22.c /usr/src/linux-rpi-3.18.y/drivers/media/usb/dvb-usb
cp /root/media/drivers/media/usb/dvb-usb/tbs-qbox22.h /usr/src/linux-rpi-3.18.y/drivers/media/usb/dvb-usb
cp /root/media/drivers/media/tuners/av201x.h /usr/src/linux-rpi-3.18.y/drivers/media/tuners
cp /root/media/drivers/media/tuners/av201x.c /usr/src/linux-rpi-3.18.y/drivers/media/tuners
cp /root/media/drivers/media/tuners/av201x_priv.h /usr/src/linux-rpi-3.18.y/drivers/media/tuners

#Make additions to Makefiles and Kconfigs so system will process the code

Add to /usr/src/linux-rpi-3.18.y/drivers/media/dvb-frontends/Makefile
obj-$(CONFIG_DVB_TAS2101) += tas2101.o

Add to /usr/src/linux-rpi-3.18.y/drivers/media/dvb-frontends/Kconfig
config DVB_TAS2101
        tristate "Tmax TAS2101 based"
        depends on DVB_CORE && I2C
        default m if !MEDIA_SUBDRV_AUTOSELECT
        help
          A DVB-S demod and tuner module.
          Say Y when you want to support this frontend.


Add to /usr/src/linux-rpi-3.18.y/drivers/media/usb/dvb-usb/Makefile
dvb-usb-tbsqbox22-objs = tbs-qbox22.o
obj-$(CONFIG_DVB_USB_TBSQBOX22) += dvb-usb-tbsqbox22.o

Add to /usr/src/linux-rpi-3.18.y/drivers/media/usb/dvb-usb/Kconfig
config DVB_USB_TBSQBOX22
        tristate "TurboSight QBOX22 DVB-S2 USB2.0 support"
        depends on DVB_USB
        select DVB_PLL if MEDIA_SUBDRV_AUTOSELECT
        select DVB_TAS2101 if MEDIA_SUBDRV_AUTOSELECT
        select MEDIA_TUNER_AV201X if MEDIA_SUBDRV_AUTOSELECT
        help
          Say Y here to support the TurboSight QBOX22 DVB-S USB2.0 receivers

Add to /usr/src/linux-rpi-3.18.y/drivers/media/tuners/Makefile
obj-$(CONFIG_MEDIA_TUNER_AV201X) += av201x.o

Add to /usr/src/linux-rpi-3.18.y/drivers/media/tuners/Kconfig
config MEDIA_TUNER_AV201X
        tristate "Airoha Technology AV201x silicon tuner"
        depends on MEDIA_SUPPORT && I2C
        default m if !MEDIA_SUBDRV_AUTOSELECT
        help
          Airoha Technology AV201x silicon tuner driver.

#Here is where the fun begins, make sure /usr/src/linux-rpi-3.18.y/.config is backed up
#Compile time with -j4 about 1.5 hrs, 4 or 5 without it.

cd /usr/src/linux-rpi-3.18.y
make -j4
mv /lib/modules/3.18.9-v7 /lib/modules/3.18.9-v7.bak
make modules
make modules_install
make headers_install

#Make sure you backup your old /boot/kernel.img
cp arch/arm/boot/zImage /boot/kerneltbs.img
nano /boot/config.txt
#add the following:
kernel=kerneltbs.img

#If you don't have the firmware file I will attach, take off the .txt and copy to /lib/firmware.
shutdown -r now

You should get the following results:

[  988.536875] usb 1-1.5: new high-speed USB device number 6 using dwc_otg
[  988.637658] usb 1-1.5: New USB device found, idVendor=734c, idProduct=5922
[  988.637683] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  988.637701] usb 1-1.5: Product: TBS 5922
[  988.637717] usb 1-1.5: Manufacturer: TBS-Tech
[  988.638772] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in cold state, will try to load a firmware
[  988.638800] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5922.fw'
[  988.638815] tbsqbox22: start downloading TBSQBOX firmware
[  988.766810] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in warm state.
[  988.767053] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  988.767295] DVB: registering new adapter (TBS QBOX22 DVBS2 USB2.0)
[  988.878871] dvb-usb: MAC address: 00:22:ab:c0:28:a3
[  988.880791] i2c i2c-2: Added multiplexed i2c bus 3
[  988.880961] i2c i2c-2: Added multiplexed i2c bus 4
[  989.022642] i2c i2c-4: av201x: Airoha Technology AV201x successfully attached
[  989.022671] QBOX22: TBS5922 attached.
[  989.023172] QBOX22: frontend attached
[  989.023207] usb 1-1.5: DVB: registering adapter 0 frontend 0 (Tmax TAS2101)...
[  989.024244] input: IR-receiver inside an USB DVB receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.5/input/input1
[  989.024520] dvb-usb: schedule remote query interval to 150 msecs.
[  989.024547] dvb-usb: TBS QBOX22 DVBS2 USB2.0 successfully initialized and connected.

 

[Titanium]

Typical setting for a Standard LNB:
LO1 - 0
LO2 - 10750
LOF - 11700

Universal LNB:
LO1 - 9750
LO2 - 10600
LOF - 11700

LOF is the switching frequency between low LO and high LO.

 

[fred555]

Moving on...

With many straight days of compiling I have been brushing up on my PHP. I figure to not run mumudvb as a service on the headend and let php
control mumudvb. I'm thinking ahead about when switching between channels that are on different transponders and how to control stopping mumudvb and restarting with different parameters. PHP can get the channel lists from the mumudvb webserver and process them.
Just a thought on how to build a master controller process on the headend.I figure http is an easy way for a client to talk to a separate headend box.
An all in one STB would be easier to code I would think. I'm open to other ideas, but I'm not a professional coder.

 

[fred555]

Update on Progress with Tevii S662 Drivers
Getting closer but may take a break for a few days and write some PHP. Thanks to jcm98 who helped me prove that my Tevii was working properly.
Here is how the driver acts from cold boot or if you reboot it after connecting it:

[    3.720207] usb 1-1.4: New USB device found, idVendor=9022, idProduct=d662
[    3.720221] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.720230] usb 1-1.4: Product: DVB-S/S2 Box
[    3.720239] usb 1-1.4: Manufacturer: Jactek
[    3.720248] usb 1-1.4: SerialNumber: 000000031
[    4.168305] dw2102: su3000_identify_state
[    4.168305]
[    4.168311] dvb-usb: found a 'TeVii S662' in warm state.
[    4.168340] dw2102: su3000_power_ctrl: 1, initialized 0
[    4.169926] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    4.171733] DVB: registering new adapter (TeVii S662)
[    4.182996] dvb-usb: MAC address: 00:18:bd:5b:b8:1d
[    4.554589]  Chip ID != [DS300X]! Not supported by this module
[    4.627010]  Chip ID = [DS3103]!
[    4.639570] DS3103 chip version: 0.208 attached.
[    4.698787] dw2102: Attached DS3103/TS2022!
[    4.709144] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Montage Technology DS3103/TS2022)...
[    4.729795] input: IR-receiver inside an USB DVB receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.4/input/input0
[    4.729826] dvb-usb: schedule remote query interval to 250 msecs.
[    4.729848] dw2102: su3000_power_ctrl: 0, initialized 1
[    4.729848]
[    4.729860] dvb-usb: TeVii S662 successfully initialized and connected.
[    4.730084] usbcore: registered new interface driver dw2102
[    6.979171] dvb-usb: recv bulk message failed: -110
[    6.985955] dw2102: i2c transfer failed.

You can see the two errors on the last lines.

Here is the dmesg result when you hotplug it:

[  216.739118] usb 1-1.4: new high-speed USB device number 5 using dwc_otg
[  216.840122] usb 1-1.4: New USB device found, idVendor=9022, idProduct=d662
[  216.840147] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  216.840164] usb 1-1.4: Product: DVB-S/S2 Box
[  216.840181] usb 1-1.4: Manufacturer: Jactek
[  216.840197] usb 1-1.4: SerialNumber: 000000031
[  216.850285] dw2102: su3000_identify_state
[  216.850285]
[  216.850314] dvb-usb: found a 'TeVii S662' in warm state.
[  216.850341] dw2102: su3000_power_ctrl: 1, initialized 0
[  216.850341]
[  216.850715] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  216.852062] DVB: registering new adapter (TeVii S662)
[  216.856590] dvb-usb: MAC address: 00:18:bd:5b:b8:1d
[  217.169814] Invalid probe, probably not a DS3000
[  217.170091] Invalid probe, probably not a DS3x0x
[  217.170116] dw2102: Failed to attach DS310x/TS202x!
[  217.170116]
[  217.170136] dvb-usb: no frontend was attached by 'TeVii S662'
[  217.170823] input: IR-receiver inside an USB DVB receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.4/input/input1
[  217.171132] dvb-usb: schedule remote query interval to 250 msecs.
[  217.171157] dw2102: su3000_power_ctrl: 0, initialized 1
[  217.171157]
[  217.171174] dvb-usb: TeVii S662 successfully initialized and connected.
[  219.419028] dvb-usb: recv bulk message failed: -110
[  219.419052] dw2102: i2c transfer failed.

Pretty grusome on hotplug.

After a cold start, mumudvb sees the frontend but there is no signal, there is more work to do:

WARN:  Unicast :  You have enabled the support for HTTP Unicast. This feature is quite youg, please report any bug/comment
Info:  Main:  Full autoconfiguration, we activate PAT rewritting. if you want to deactivate it see the README.
Info:  Main:  Full autoconfiguration, we activate SDT rewritting. if you want to deactivate it see the README.
Info:  Main:  Full autoconfiguration, we activate sorting of the EIT PID. if you want to deactivate it see the README.
Info:  Main:  ========== End of configuration, MuMuDVB version 1.7.1 is starting ==========
Info:  Autoconf:  The autoconfiguration auto update is enabled. If you want to disable it put "autoconf_pid_update=0" in your config file.
Info:  Main:  Streaming. Freq 12115000
Info:  Tune:  Using DVB card "Montage Technology DS3103/TS2022" tuner 0
Info:  Tune:  Tuning DVB-S to Freq: 1365000 kHz, LO frequency 10750000 kHz Pol:V Srate=22425000, LNB number: 0
Info:  Tune:  LNB voltage 13V
Info:  Tune:  DISEQC SETTING SUCCEDED
Info:  Tune:  FE_STATUS:
Info:  Main:  Card not tuned after timeout - exiting

 

[fred555]

Handy Tip for Linux Newbies

When you do the initial setup of the Pi enable ssh. Then use putty as your client from your laptop in the comfort of your easy-chair.

http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe

Then you can just copy and paste the statements given above. You paste into putty by just right clicking.
To copy from putty you simply select the text by holding down the left mouse button and highlighting.

Another handy feature with putty is logging. Right click on the top border, click on change settings. Under the session category, click logging.
Under session logging, select all session logging, browse to a suitable location, then click apply. You will now have a record of everything you
typed and everything the PI spit back out at you. /username/.bash_history only shows what you typed in not the results.
This feature is handy to go back and review your work if you made a mistake or to log compiling to be able to see what has left the viewing area.
To stop logging, go back in and select none under session logging. The logging will also stop automatically when you exit the session.

All of my work was done in this manner, sometimes my Pi was 40 miles away, connected to a fast internet connection so
I could download the many kernels and large source code packages that would have taken forever on my measily, slow connection.

 

[richyrich]

10600 blank blank worked the last time i had winkno's installed (windows). The boost is the debug on 22 khz on or off. 10600 however; will allow some lower frequencies of the whole pie is not programme matched per Country (match for/by the freq./sr/pol. entered) to come in when it is truly a universal lnbf circ. or linear it does not care (a piece of plastic in lnbf does this); just the task in getting a number of numbers to match where they are "a slice" of raspberry pie. Has anybody USB 2/3 typed network definitions into enough of them; to allow say a number of single-ended users with correct params to multi-output to multi-users say "any old pc" type installation; for companies with many cellphones?

 

[Titanium]

10600 would only be used with a universal type LNB. It also must be used in conjunction with 22KHz switching. The 10600 setting is not correct for use with a standard type LNB (LO of 10750).

A mismatch of the LO will not log additional frequencies. A mismatch only incorrectly identifies the downlink frequency.

 

[richyrich]

10600 would only be used with a universal type LNB. It also must be used in conjunction with 22KHz switching. The 10600 setting is not correct for use with a standard type LNB (LO of 10750).

A mismatch of the LO will not log additional frequencies. A mismatch only incorrectly identifies the downlink frequency.

sO, if the program for the operating system (driver); has a 10600 parameter at the display; it tells the tuner to set-up the defined channel list from the frequencies; or if the defines are 10750; and just the displayed information that set's the LO? In some receiver's, the 10600 also forces 22 khz on (and the freq's. stay aligned for NA freq. listed) instead of showing 10750; it really aligns the tuners pre-defined center of a band (which is a 500 MHz. for NA) depending on the lnbf it needs to tune.

10750 seems only the force to tune each slice...what if the pc program i got was from Australia; where they talk in different language. Their channel list would have different defines for each typical australian lnbf would use 9750 3.4-3.9 and then the defined channels setup the tuner.

What I am saying is; the display is not lying; it just can lie to yout eyes by doing more than one thing with a display (because it does say 10600; but it really means center of band for tuner). Window's uses .bak; a problem is the child...

Darn if my dvb xxx does work 11789 V 28125; and the program needed 10600 to set the tuner up right on a NA listed; then the freq. lock worked correctly (equipment manufactured for ascertain any country).

Lucky for me i am old; do not have to know that is how it works. Update replaces old .bak's! As a spectrum analyzer and a oscope both on the same machine shows, what slice is locking! The trinket is that 2x500Mhz. is selected with 14/18vdc sw. Then the 10600 I entered into my card dvb really meant center of standard lnbf because the .bak told my tuner with a local oscillator to 14vdc lof1; and center tune a stabbard lnbf; because the .bak told it to do ALL OF IT!

 

[fred555]

PHP on The Pi2

Possibly for mumudvb control on separate headend system later.
Here is a very simple script that prints out some system information by running system commands.
"System" prints out the results immediately, "exec" will run the command silently, allowing calculations before printing.

http://www.raspberrypi.org/documentation/remote-access/web-server/apache.md

apt-get install apache2
apt-get install php5 libapache2-mod-php5
cd /var/www
rm index.html
nano index.php
<html>
<head>
  <title>PHP Test</title>
</head>
<body>
You are running kernel version  <?php system("uname -r"); ?>
<p>System has been running for <?php system("/usr/bin/uptime"); ?>
<p>System Temperature is
<?php $mc = exec("cat /sys/class/thermal/thermal_zone0/temp");
$c =  $mc/1000;
$f =  ($c * 1.8) + 32;
echo $f;
?> Degrees F
</body>
</html>

Here are the results:

You are running kernel version 3.18.9-v7

System has been running for 11:09:38 up 1:24, 1 user, load average: 0.00, 0.01, 0.05

System Temperature is 103.1828 Degrees F

Learn more here: http://php.net/manual/en/index.php

 

[Titanium]

If the user manually inputs a frequency parameter then the LO must be correct and matched for the calculation to tune the desired IF.

A defined LO frequency does not force a 22KHz signal. The LOF identifies the switch point if the function is enabled If the defined downlink frequency is below the LOF, no 22KHz signal is issued.

There isn't such a thing as a different language. LO frequencies and LOF switching operate the same internationally with any LNB type or LO frequency. A LNB either has one LO or two. If two bands, then a switch point is defined and issued to select the band.

Tuner frequencies are based on IF, not downlink frequencies. If the software allows and the user wishes to define frequencies as IF, then no LO frequency is necessary.

 

[richyrich]

And, the tuner selects the slice at the width; for instance in the tuner a vco gives the exact voltage for the tuner to tune a (11789 V 28125) of the whole band; just another slice of pie or any other is not tuned.

Now look at a wifi; any test says I am getting a full 4 Mb up and down with the link I am on. But really, I am only a slice of that band I run on (which goes up and down depending on how many others are slicing around me at the same time).

What I noticed in hdvr1200 the other day was it will not tune a stacked lnbf fss by DN fully. I don't care why it doesn't. It just won't relate; or allow, the 11840 to be the auto-updated "change a definition"; that frequency isn't my matched routine (cuz the freq. is a must match) typed in rhinking; it also needs a different LO for the middle to be hit correctly (and they stack both ends to the middle, which is blanker at the middle and wider than 1 gig) when aiming it at a fss satellite g-19.

 

[richyrich]

Let's look at tuners; then maybe i can understand it. The tuner in a 4DTV 922; it is marked and read as 950-2150. This should mean it can tune that band (fully 2 gig). Now I look at my microHD, the tuner is marked satellite in and 18vdc 500 milliamp. Lotta good that comparison did. The tuner is so small; it hasn't even got a label (must be new one though). These typed tuners can only tune a full 1 gig. So standardly, in fact; it can tune 2x500. And it does tune one 500 (H or V) fully at one time (or is that the loop out typed tuner?). It has usb2! And the dvb-s2 format; dvb-s hd!