TBSDTV Community Forum

Hi,

I recently purchased a 5922 and have connected it to my Mythbuntu HTPC. Installing the drivers and scanning for channels was straightforward, and worked fine.

I can watch and record TV using MythTV, so the box is working ok. However, the signal seems to be quite unstable. I can sometimes record TV for over an hour at a time with no problem, but then sometimes the bit error rate rapidly rises and the signal lock is lost, terminating the recording. On average I think it manages about half an hour before losing lock.

Below is the output from femon showing the bit error rate rising, then losing lock. As an aside I think the drivers must be reporting the wrong data, because I've never seen 'unc', or uncorrected errors, go above zero. ber seems to be the number of uncorrected errors.

Code: Select All Code

status SCVYL | signal  82% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr  91% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr 100% | ber 777 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr 100% | ber 89 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr 100% | ber 59 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr 100% | ber 185 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr  97% | ber 333 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr  69% | ber 4939 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr 100% | ber 13656 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr  89% | ber 5186 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr 100% | ber 2380 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr  79% | ber 61 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr  87% | ber 2383 | unc 0 | FE_HAS_LOCK
status SCVYL | signal  82% | snr  69% | ber 5594 | unc 0 | FE_HAS_LOCK
status       | signal  82% | snr  95% | ber 20368 | unc 0 |
status SCVYL | signal  82% | snr  99% | ber 0 | unc 0 | FE_HAS_LOCK
status       | signal  82% | snr 100% | ber 20230 | unc 0 |
status       | signal  81% | snr  60% | ber 25344 | unc 0 |
status       | signal  82% | snr 100% | ber 30918 | unc 0 |
status       | signal  82% | snr  85% | ber 32074 | unc 0 |
status       | signal  82% | snr  57% | ber 31793 | unc 0 |
status       | signal  82% | snr  60% | ber 32000 | unc 0 |


My signal strength is good, so I'm not sure what the problem is. To check my dish and cabling I connected a FreeSat box to the other cable and recorded the same program on it and through the 5922. On a number of occasions the FreeSat box has recorded it fine, but the 5922 has lost lock and lost the recording.

What can I do to help diagnose this? Is it just the 5922 is not a forgiving as other tuners to noise, or is there an problem either with my 5922 or my pc?

Thanks for any help,
Andrew

Here are some extra details on my setup:

uname -a

Code: Select All Code

Linux tv 3.2.0-34-generic #53-Ubuntu SMP Thu Nov 15 10:49:02 UTC 2012 i686 i686 i386 GNU/Linux


dmesg

Code: Select All Code

[   20.606902] dib0700: loaded with support for 21 different device-types
[   20.607351] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware
[   20.661061] type=1400 audit(1359406552.055:8): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=882 comm="apparmor_parser"
[   20.662131] type=1400 audit(1359406552.055:9): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=882 comm="apparmor_parser"
[   20.662313] type=1400 audit(1359406552.055:10): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=882 comm="apparmor_parser"
[   20.662840] init: failsafe main process (766) killed by TERM signal
[   20.663580] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[   20.663618] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
[   20.663638] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
[   20.664958] type=1400 audit(1359406552.059:11): apparmor="STATUS" operation="profile_load" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=881 comm="apparmor_parser"
[   20.728851] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5922.fw'
[   20.734353] tbsqbox22: start downloading TBSQBOX firmware
[   20.742972] HDMI status: Codec=3 Pin=3 Presence_Detect=1 ELD_Valid=1
[   20.744014] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
[   20.745789] HDMI: detected monitor SAMSUNG at connection type HDMI
[   20.745790] HDMI: available speakers: FL/FR
[   20.745793] HDMI: supports coding type LPCM: channels = 2, rates = 32000 44100 48000, bits = 16 20 24
[   20.745904] input: HDA Intel HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input4
[   20.763368] usb 1-4: USB disconnect, device number 2
[   20.864012] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in warm state.
[   20.864070] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   20.864087] DVB: registering new adapter (TBS QBOX22 DVBS2 USB2.0)
[   20.864090] tbsqbox22: read eeprom failed
[   20.864092] dvb-usb: MAC address reading failed.
[   20.866143] tbs5922fe: module license 'TurboSight Proprietary: www.tbsdtv.com' taints kernel.
[   20.866145] Disabling lock debugging due to kernel taint
[   20.976698] dib0700: firmware started successfully.
[   21.005643] sky2 0000:03:00.0: eth0: enabling interface
[   21.005807] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.032896] init: gdm main process (1028) killed by TERM signal
[   21.041423] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.168012] TurboSight TBS 5922 Frontend Attaching...
[   21.192023] TurboSight TBS 5922 Frontend:
[   21.192025]  tbs5922fe - attach failed
[   21.192037] dvb-usb: no frontend was attached by 'TBS QBOX22 DVBS2 USB2.0'
[   21.192042] dvb-usb: TBS QBOX22 DVBS2 USB2.0 successfully initialized and connected.
[   21.192095] usbcore: registered new interface driver tbsqbox22
[   21.194068] dvb-usb: TBS QBOX22 DVBS2 USB2.0 successfully deinitialized and disconnected.
[   21.480159] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state.
[   21.480221] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   21.480600] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
[   21.604656] DVB: registering adapter 0 frontend 0 (DiBcom 3000MC/P)...
[   21.610030] MT2060: successfully identified (IF1 = 1249)
[   21.989987] init: plymouth-stop pre-start process (1414) terminated with status 1
[   22.086854] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   22.086985] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
[   22.092856] DVB: registering adapter 1 frontend 0 (DiBcom 3000MC/P)...
[   22.097607] MT2060: successfully identified (IF1 = 1245)
[   22.516014] usb 1-4: new high-speed USB device number 4 using ehci_hcd
[   22.649057] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in cold state, will try to load a firmware
[   22.650400] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5922.fw'
[   22.651665] tbsqbox22: start downloading TBSQBOX firmware
[   22.652688] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected.
[   22.652835] usbcore: registered new interface driver dvb_usb_dib0700
[   22.772013] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in warm state.
[   22.772065] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   22.772174] DVB: registering new adapter (TBS QBOX22 DVBS2 USB2.0)
[   22.868286] dvb-usb: MAC address: 00:22:ab:c0:23:86
[   23.172009] TurboSight TBS 5922 Frontend Attaching...
[   23.216050] QBOX22: TBS5922FE attached.
[   23.217552] DVB: registering adapter 2 frontend 0 (TurboSight TBS 5922 DVBS/S2 frontend)...
[   23.217802] dvb-usb: TBS QBOX22 DVBS2 USB2.0 successfully initialized and connected.
[   23.217859] usbcore: registered new interface driver usbserial_generic
[   23.217861] usbserial: USB Serial Driver core
[   23.218089] USB Serial support registered for pl2303
[   23.218111] pl2303 8-2:1.0: pl2303 converter detected
[   23.232346] usb 8-2: pl2303 converter now attached to ttyUSB0
[   23.238428] usbcore: registered new interface driver pl2303
[   23.238430] pl2303: Prolific PL2303 USB to serial adaptor driver
[   23.501163] sky2 0000:03:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control both
[   23.513269] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   34.008005] eth0: no IPv6 routers present
[ 1156.584197] TurboSight TBS 5922 Frontend:
[ 1156.584200]  tbs5922fe - Current Delivery System and Mode are unknown
[ 1442.740191] TurboSight TBS 5922 Frontend:
[ 1442.740194]  tbs5922fe - Current Delivery System and Mode are unknown


lsusb

Code: Select All Code

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 2040:9950 Hauppauge WinTV Nova-T-500
Bus 006 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver
Bus 008 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 001 Device 004: ID 734c:5922 TBS Technologies China


Most linux dvb drivers report ber as the number of errors reported per second. Not the ratio of error's to total packets. Many linux dvb drivers dont have unc implemented so always report 0.

What transponder are you tuning? There are some funky systems/modulations out there, knowing the tp would help people reply.

UDL

Hi,

I'm trying to use the 5922 to record the BBC HD channels on Freesat. They transmit on 10832.00 H 49 on Astra 1N.

Andrew

Hi,

I think I've tracked down the source of my problem. I think it was caused by a nearby cordless phone. Moving the 5923 further away seems to have cured the issue as I'm now able to get stable, error free reliable recordings. Hurrah!

Andrew