TBSDTV Community Forum

did it and started to test. one of the sticks still failes to load, the "test" message doesn´t show up there. i am now testing the workig stick for a while..
here is the log:

Code: Select All Code

[ 2714.877955] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[ 2714.921125] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[ 2714.929180] tbs5220: start downloading TBS5220 firmware
[ 2715.068549] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[ 2715.075434] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 2715.084416] DVB: registering new adapter (TBS 5220 USB2.0)
[ 2715.377511] dvb-usb: MAC address: 00:00:00:00:00:00
[ 2716.989412] TurboSight TBS 5220 Frontend:
[ 2716.989418]  tbs5220fe - tuner command is not responding
[ 2718.614802] TurboSight TBS 5220 Frontend:
[ 2718.614808]  tbs5220fe - tuner command is not responding
[ 2718.624085] tbs5220fe: tuner attach failed
[ 2718.628217] dvb-usb: no frontend was attached by 'TBS 5220 USB2.0'
[ 2718.635242] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/usb4/4-2/4-2.1/input/input0
[ 2718.647602] dvb-usb: schedule remote query interval to 150 msecs.
[ 2718.653726] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.
[ 2718.660796] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[ 2718.692425] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[ 2718.699800] tbs5220: start downloading TBS5220 firmware
[ 2718.838533] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[ 2718.845061] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 2718.854084] DVB: registering new adapter (TBS 5220 USB2.0)
[ 2719.147305] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
[ 2719.241528] tbs5220: Attached TBS5220FE!
[ 2719.241534]
[ 2719.247144] tbs5220 test driver
[ 2719.250284] DVB: registering adapter 1 frontend 0 (TurboSight TBS 5220 DVBC frontend)...
[ 2719.259500] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/usb4/4-2/4-2.3/input/input1
[ 2719.271657] dvb-usb: schedule remote query interval to 150 msecs.
[ 2719.277773] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.
[ 2719.285115] usbcore: registered new interface driver tbs5220


Here comes an update. For me the Stick still does not work. I don´t get the error message anymore but TV fails after a while. VDR tells me:

Code: Select All Code

Jun  1 15:01:29 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 512, tp 818
Jun  1 15:01:50 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 10, tp 113
Jun  1 15:02:11 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 333, tp 121
Jun  1 15:02:32 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 28, tp 129
Jun  1 15:02:53 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 255, tp 346
Jun  1 15:03:15 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 174, tp 354
Jun  1 15:03:36 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 199, tp 362
Jun  1 15:03:57 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 274, tp 370
Jun  1 15:04:17 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 177, tp 378
Jun  1 15:04:38 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 178, tp 386
Jun  1 15:04:59 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 2, tp 394
Jun  1 15:05:20 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 30, tp 402
Jun  1 15:05:41 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 13, tp 410
Jun  1 15:06:02 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 1, tp 418
Jun  1 15:06:23 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 14, tp 426
Jun  1 15:06:45 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 102, tp 434
Jun  1 15:07:06 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 3, tp 442
Jun  1 15:07:16 DiskStation vdr: [21592] Streamdev: Accepted new client (HTTP) 192.168.0.101:7272
Jun  1 15:07:22 DiskStation vdr: [21592] client (HTTP) 192.168.0.101:7272 has closed connection
Jun  1 15:07:22 DiskStation vdr: [21592] streamdev-server: closing HTTP connection to 192.168.0.101:7272
Jun  1 15:07:24 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 3, tp 442
Jun  1 15:07:48 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 10, tp 113
Jun  1 15:08:08 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 333, tp 121
Jun  1 15:08:29 DiskStation vdr: [21580] frontend 0/0 timed out while tuning to channel 28, tp 129


For one of the other guys it seems to work for a longer time now


Update #2 on USB2 Port Error occurs again (and you can see how long it was working fine):

Code: Select All Code

[ 1518.511432] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[ 1518.554834] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[ 1518.562150] tbs5220: start downloading TBS5220 firmware
[ 1518.684756] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[ 1518.691304] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 1518.700578] DVB: registering new adapter (TBS 5220 USB2.0)
[ 1518.914496] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
[ 1519.031436] tbs5220: Attached TBS5220FE!
[ 1519.031442]
[ 1519.037559] tbs5220 test driver
[ 1519.041305] DVB: registering adapter 0 frontend 0 (TurboSight TBS 5220 DVBC frontend)...
[ 1519.050590] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:01.0/0000:01:0d.0/usb1/1-1/input/input1
[ 1519.062188] dvb-usb: schedule remote query interval to 150 msecs.
[ 1519.068283] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.
[ 1519.075689] usbcore: registered new interface driver tbs5220
[ 1532.626539] TurboSight TBS 5220 Frontend:
[ 1532.626545]  tbs5220fe - software version is 1.0.0.0
[ 1532.796019] TurboSight TBS 5220 Frontend:
[ 1532.796025]  tbs5220fe - Successfully Initialized
[ 9158.183233] TurboSight TBS 5220 Frontend:
[ 9158.183239]  tbs5220fe - tuner command is not responding
[ 9159.772760] TurboSight TBS 5220 Frontend:
[ 9159.772767]  tbs5220fe - tuner command is not responding
[ 9161.386094] TurboSight TBS 5220 Frontend:


I have the same problem on Windows : viewtopic.php?f=15&t=8789 .
More precisely, I have 2 problems :
1) The picture freezes and I can't receive any sender anymore.
2) I can receive a sender but I can't tune to sender of another frequence.

I use DVB-C, Windows 7 Pro 64 Bit, TBSViewer ,SmartDVB, Windows Media Center, driver versions 1.0.0.5 (virtual DVB-S) , 1.0.0.5 DVB-C, 1.0.0.6 DVB-C.
My provider is Kabel Deutschland.
Same problem on openSuse 12.3 (64-Bit) and openSuse 13.1 (64-Bit).

i got the response from the other guy. same thing seems to work longer but error still occurs. any further ideas?

ps. german vdr forum thread over here: http://www.vdr-portal.de/index.php?page ... ID=1201767

i cannot comment for Windows - please, the Windows users to contact the support emails, if they didn't - that way they can get drivers with similar changes i suggested here.

so, for the Linux users: if i understand correct there are 2 users with the problem and reducing the access speed seems to increase the time until the stick fails. that suggest to me some hardware problem. so, did get those sticks replaced and have the same issues with new ones? i'm just trying to identify is those are isolated case, i.e. individual defective sticks or something more mass like batch of sticks that demonstrates the problem.

cody Wrote:so, for the Linux users: if i understand correct there are 2 users with the problem and reducing the access speed seems to increase the time until the stick fails. that suggest to me some hardware problem. so, did get those sticks replaced and have the same issues with new ones? i'm just trying to identify is those are isolated case, i.e. individual defective sticks or something more mass like batch of sticks that demonstrates the problem.

I try to sum up: I own 2 sticks and the issue with both of them. One of them was completely broken so i got it replaced and i sent the "working" one, too. I don´t know if both hav been replaced but at least one. The new one had the same problem. So i had 3 (4?) sticks with the issue. In the vdr forum there are 2 more guys with that problem, but i don´t know how many sticks they own and if/or they had replacements.

I received the Stick on January 09, 2014 and I informed the euro_support of TBS about the problem.
I got a test-version of a windows-driver from the support but it didn't help.

we're running some tests and we believe the IR receiver of the device (in some environments when it picks up other signals) can cause those problems. we will release update firmware that should fix the IR problem we found. in the mean time (that's for the Linux users, but there will be Windows driver update too), please, try modification as the one i described here:

viewtopic.php?f=145&t=8980#p31275

but this time remove the following additional lines:

Code: Select All Code

         buf[0] = 7;
         buf[1] = 1;
         tbs5220_op_rw(d->dev->udev, 0x8a, 0, 0,
               buf, 2, TBS5220_WRITE_MSG);

please, post your results or email us on euro_support@tbsdtv.com. thanks

This is in line 189, correct? I did that change and will test now.
One of the guys in the other forum mentioned it may be related to the I2C bus and that a short sleep between 2 access can help there. I have no knownledge of this but i thought i should share that idea.

This happend compiling but should be harmless

Code: Select All Code

  CC [M]  /usr/local/src/tbs/linux-tbs-drivers/v4l/tbs5880.o
/usr/local/src/tbs/linux-tbs-drivers/v4l/tbs5220.c: In function 'tbs5220_frontend_attach':
/usr/local/src/tbs/linux-tbs-drivers/v4l/tbs5220.c:181:5: warning: unused variable 'buf' [-Wunused-variable]
  CC [M]  /usr/local/src/tbs/linux-tbs-drivers/v4l/tbs5881.o


yes, exactly starts on line 189. the warning you get is harmless, just when you delete those lines the "buf" is not longer used, which is fine. however, i don't understand how that change can affect what you said on the message you sent me, i.e. the change makes the stick not working at all. i tested that modification myself and it's to disable the IR received. anyway, if those changes i suggested don't help then we need to wait for the new "dvb-usb-tbsqbox-id5220.fw", which i mentioned is under development.