TBSDTV Community Forum

Posted: **Wed May 11, 2011 5:29 am**

My qbox3 doesn't work well on transponder which have low SR.
Maybe it is not related to SR but it can not tune them most of the time.

Code: Select All Code: ./scan-s2 -o zap tptest.tpconf >> testresult.conf API major 5, minor 1 ERROR: Cannot open rotor configuration file 'rotor.conf'. scanning tptest.tpconf using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder DVB-S 12601000 V 2960000 AUTO AUTO QPSK initial transponder DVB-S 11049000 V 2400000 AUTO AUTO QPSK initial transponder DVB-S 10955000 H 2960000 AUTO AUTO QPSK initial transponder DVB-S 11964000 H 5925000 AUTO AUTO QPSK initial transponder DVB-S 12650000 H 4250000 AUTO AUTO QPSK ----------------------------------> Using DVB-S >>> tune to: 12601:v:0:2960 DVB-S IF freq is 2001000 >>> parse_section, section number 0 out of 0...! service_id = 0x0 service_id = 0x1 pmt_pid = 0x64 >>> parse_section, section number 0 out of 0...! VIDEO : PID 0x0065 AUDIO : PID 0x0066 AUDIO : PID 0x03FC >>> parse_section, section number 0 out of 0...! 0x0066 0x0001: pmt_pid 0x0064 Scopus -- 1 TV GEORGIA (running) >>> parse_section, section number 0 out of 0...! Network Name 'Scopus' ----------------------------------> Using DVB-S >>> tune to: 11049:v:0:2400 DVB-S IF freq is 1299000 WARNING: >>> tuning failed!!! >>> tune to: 11049:v:0:2400 (tuning failed) DVB-S IF freq is 1299000 WARNING: >>> tuning failed!!! ----------------------------------> Using DVB-S >>> tune to: 10955:h:0:2960 DVB-S IF freq is 1205000 WARNING: >>> tuning failed!!! >>> tune to: 10955:h:0:2960 (tuning failed) DVB-S IF freq is 1205000 WARNING: >>> tuning failed!!! ----------------------------------> Using DVB-S >>> tune to: 11964:h:0:5925 DVB-S IF freq is 1364000 WARNING: >>> tuning failed!!! >>> tune to: 11964:h:0:5925 (tuning failed) DVB-S IF freq is 1364000 WARNING: >>> tuning failed!!! ----------------------------------> Using DVB-S >>> tune to: 12650:h:0:4250 DVB-S IF freq is 2050000 WARNING: >>> tuning failed!!! >>> tune to: 12650:h:0:4250 (tuning failed) DVB-S IF freq is 2050000 WARNING: >>> tuning failed!!! dumping lists (1 services) Done.

Code: Select All Code: ./scan-s2 -o zap tptest.tpconf >> testresult.conf API major 5, minor 1 ERROR: Cannot open rotor configuration file 'rotor.conf'. scanning tptest.tpconf using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder DVB-S 12601000 V 2960000 AUTO AUTO QPSK initial transponder DVB-S 11049000 V 2400000 AUTO AUTO QPSK initial transponder DVB-S 10955000 H 2960000 AUTO AUTO QPSK initial transponder DVB-S 11964000 H 5925000 AUTO AUTO QPSK initial transponder DVB-S 12650000 H 4250000 AUTO AUTO QPSK ----------------------------------> Using DVB-S >>> tune to: 12601:v:0:2960 DVB-S IF freq is 2001000 WARNING: >>> tuning failed!!! >>> tune to: 12601:v:0:2960 (tuning failed) DVB-S IF freq is 2001000 WARNING: >>> tuning failed!!! ----------------------------------> Using DVB-S >>> tune to: 11049:v:0:2400 DVB-S IF freq is 1299000 WARNING: >>> tuning failed!!! >>> tune to: 11049:v:0:2400 (tuning failed) DVB-S IF freq is 1299000 WARNING: >>> tuning failed!!! ----------------------------------> Using DVB-S >>> tune to: 10955:h:0:2960 DVB-S IF freq is 1205000 WARNING: >>> tuning failed!!! >>> tune to: 10955:h:0:2960 (tuning failed) DVB-S IF freq is 1205000 WARNING: >>> tuning failed!!! ----------------------------------> Using DVB-S >>> tune to: 11964:h:0:5925 DVB-S IF freq is 1364000 WARNING: >>> tuning failed!!! >>> tune to: 11964:h:0:5925 (tuning failed) DVB-S IF freq is 1364000 WARNING: >>> tuning failed!!! ----------------------------------> Using DVB-S >>> tune to: 12650:h:0:4250 DVB-S IF freq is 2050000 WARNING: >>> tuning failed!!! >>> tune to: 12650:h:0:4250 (tuning failed) DVB-S IF freq is 2050000 WARNING: >>> tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done.

When I test on windows, It seems that everything works better:

Posted: **Wed May 11, 2011 5:31 am**

Posted: **Wed May 11, 2011 5:33 am**

Posted: **Wed May 11, 2011 5:37 am**

Is there anybody who use qbox3 in linux. At least he can test and I can be sure If my qbox is damaged or not.

Thanks

Posted: **Thu May 12, 2011 9:41 pm**

I just bought a Qbox3 specifically to use under Linux, I may (or may not) be seeing something similar to you. While I've not tested on Windows I have basically replaced a Sky+HD box with this system - so can compare it with the performance of that. In this regard the Qbox seems to struggle to tune in to channels the Sky box has no issues with (I'm obviously talking free to air here and not encrypted). Under TVHeadend a large number of multiplexes are listed as faint signal/bad signal. Stranger still it sometimes takes my "wiggling" the coax cable at the qbox end in order to tune it at all to a number of channels. It'll then be fine for several hours but again at some point the picture will freeze and a wiggling is needed once more. I have replaced the plug (following a very good video guide to fitting Type-F connectors) in case it was the issue but the problems remain.

Again the Sky box never required this, sure it had issues with bad weather conditions but again this is not the situation here. It's actually getting somewhat annoying now - I can't be wiggling cables about everytime I switch on the linux box and wish to watch a certain TV channel.

Posted: **Thu May 12, 2011 11:39 pm**

Drae Wrote:I just bought a Qbox3 specifically to use under Linux, I may (or may not) be seeing something similar to you. While I've not tested on Windows I have basically replaced a Sky+HD box with this system - so can compare it with the performance of that. In this regard the Qbox seems to struggle to tune in to channels the Sky box has no issues with (I'm obviously talking free to air here and not encrypted). Under TVHeadend a large number of multiplexes are listed as faint signal/bad signal. Stranger still it sometimes takes my "wiggling" the coax cable at the qbox end in order to tune it at all to a number of channels. It'll then be fine for several hours but again at some point the picture will freeze and a wiggling is needed once more. I have replaced the plug (following a very good video guide to fitting Type-F connectors) in case it was the issue but the problems remain.

Again the Sky box never required this, sure it had issues with bad weather conditions but again this is not the situation here. It's actually getting somewhat annoying now - I can't be wiggling cables about everytime I switch on the linux box and wish to watch a certain TV channel.

Definitely same problem.
Maybe I couldn't describe it well, but You did

As you said Qbox3 can tune channels under tvheadend, but after sometime (I couldn't find the reason) Qbox3 starts not tuning to transponders and tvheadend lists a large of transponders as faint signal/bad signal. At first I thought that, this happens because of a bug in tvheadend, but later when I test qbox3 with scan-s2 tool, I got same results. It seems that we need a corrected linux driver.

Maybe windows driver also has same bug, I didn't test in windows as long as in linux.

Posted: **Tue May 17, 2011 1:24 am**

diglam Wrote: tvheadend lists a large of transponders as faint signal/bad signal. At first I thought that, this happens because of a bug in tvheadend, but later when I test qbox3 with scan-s2 tool, I got same results. It seems that we need a corrected linux driver.

please, give me details how you assess that the signal is faint/bad especially without 'szap-s2' tool? in my opinion you can asses that only with activating dB and dBm reporting in the driver as it's described in the README file and check with 'szap-s2'. other than that i agree it could be some bug in the Linux driver regarding low symbol rate and i will look at it, but if the same happens in Windows and in Linux it's highly unlikely to be bug in the Linux driver, because there is no shared source code between Windows and Linux drivers. anyway, i want to look at those issues as part of the work for updating the drivers for the new kernel versions (2.6.37/2.6.38), e.g. before releasing the new versions, which is planned to happen soon.

Posted: **Tue May 17, 2011 2:25 am**

cody Wrote:
diglam Wrote: tvheadend lists a large of transponders as faint signal/bad signal. At first I thought that, this happens because of a bug in tvheadend, but later when I test qbox3 with scan-s2 tool, I got same results. It seems that we need a corrected linux driver.

please, give me details how you assess that the signal is faint/bad especially without 'szap-s2' tool? in my opinion you can asses that only with activating dB and dBm reporting in the driver as it's described in the README file and check with 'szap-s2'. other than that i agree it could be some bug in the Linux driver regarding low symbol rate and i will look at it, but if the same happens in Windows and in Linux it's highly unlikely to be bug in the Linux driver, because there is no shared source code between Windows and Linux drivers. anyway, i want to look at those issues as part of the work for updating the drivers for the new kernel versions (2.6.37/2.6.38), e.g. before releasing the new versions, which is planned to happen soon.

Please check first post that I sent.

Qbox3 can not tune to transponders with scan-s2 tool in linux although It can tune to same transponders in windows.
If you need more information, I can do what I can.

Thanks

Posted: **Tue May 24, 2011 3:19 am**

I downloaded and compiled new driver, but problem still continue.

These are kernel messages with dmesg :

[ 1309.473049] usb 1-4: new high speed USB device using ehci_hcd and address 3
[ 1309.588370] usb 1-4: New USB device found, idVendor=734c, idProduct=5921
[ 1309.588382] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1309.588868] dvb-usb: found a 'TBS QBOXS3 DVBS2 USB2.0' in cold state, will try to load a firmware
[ 1309.647628] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5921.fw'
[ 1309.654621] tbsqboxs3: start downloading TBSQBOX firmware
[ 1309.776039] dvb-usb: found a 'TBS QBOXS3 DVBS2 USB2.0' in warm state.
[ 1309.776162] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 1309.807174] DVB: registering new adapter (TBS QBOXS3 DVBS2 USB2.0)
[ 1309.871118] tbsqboxs3: read eeprom failed
[ 1309.871125] dvb-usb: MAC address reading failed.
[ 1309.872275] TurboSight TBS 5921 Frontend Attaching...
[ 1310.082123] TurboSight TBS 5921 Frontend:
[ 1310.082127] tbs5921fe: attach failed
[ 1310.082298] dvb-usb: no frontend was attached by 'TBS QBOXS3 DVBS2 USB2.0'
[ 1310.146312] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:04.1/usb1/1-4/input/input3
[ 1310.146441] dvb-usb: schedule remote query interval to 150 msecs.
[ 1310.146452] dvb-usb: TBS QBOXS3 DVBS2 USB2.0 successfully initialized and connected.
[ 1310.146576] usb 1-4: USB disconnect, address 3
[ 1310.159833] dvb-usb: TBS QBOXS3 DVBS2 USB2.0 successfully deinitialized and disconnected.
[ 1311.400043] usb 1-4: new high speed USB device using ehci_hcd and address 4
[ 1311.515366] usb 1-4: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
[ 1311.515730] usb 1-4: New USB device found, idVendor=734c, idProduct=5921
[ 1311.515737] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1311.515743] usb 1-4: Product: DVBS2BOX
[ 1311.515748] usb 1-4: Manufacturer: TBS-Tech
[ 1311.516201] dvb-usb: found a 'TBS QBOXS3 DVBS2 USB2.0' in cold state, will try to load a firmware
[ 1311.519901] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5921.fw'
[ 1311.525308] tbsqboxs3: start downloading TBSQBOX firmware
[ 1311.643053] dvb-usb: found a 'TBS QBOXS3 DVBS2 USB2.0' in warm state.
[ 1311.643218] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 1311.643425] DVB: registering new adapter (TBS QBOXS3 DVBS2 USB2.0)
[ 1311.744733] dvb-usb: MAC address: XX:XX:XX:XX:XX:XX (edited by me)
[ 1311.744737]
[ 1311.746638] TurboSight TBS 5921 Frontend Attaching...
[ 1311.786994] QBOXS3: TBS5921FE attached.
[ 1311.787243] DVB: registering adapter 0 frontend 0 (TurboSight TBS 5921 DVBS/S2 frontend)...
[ 1311.787903] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:04.1/usb1/1-4/input/input4
[ 1311.788046] dvb-usb: schedule remote query interval to 150 msecs.
[ 1311.788058] dvb-usb: TBS QBOXS3 DVBS2 USB2.0 successfully initialized and connected.

Posted: **Mon May 30, 2011 12:02 am**

Seo wants an excellent search engine optimizer plan. Simply one in all these methods could make a big distinction in your sites position and firm your website brings you.

TBSDTV Community Forum

Problem on low SR transponders

Problem on low SR transponders

Re: Problem on low SR transponders

Re: Problem on low SR transponders

Re: Problem on low SR transponders

Re: Problem on low SR transponders

Re: Problem on low SR transponders

Re: Problem on low SR transponders

Re: Problem on low SR transponders

Re: Problem on low SR transponders

regards to www.buydvb.net team