340 replies to this topic

[BOSSEB]

Hi Guys,


I have compiled Openpli5/SatDreamGr experimental images for et10000, vuduo2, vuduo, vusolo4k
with TBS drivers and Enigma2 patched for MIS/PLS till now.

Here are the steps to get the card up and running

0. Use image in FLASH, not in multiboot, clear?

1. Place TBS firmware into /lib/firmware

you can download firmware from here: http://www.tbsdtv.com/download/

2. Use Proper MIS/PLS codes

eg for Mediaset, RAI multistreams @5W, 13E you can found in https://github.com/c.../satellites.xml

3. Install kernel module, reboot

opkg update
opkg install kernel-module-dvb-usb-tbsusb
reboot


Most probably a new tuner will show up on the list

Also if you have a sattelite with MIS/PLS report if those channels are scanned and you can tune to those channels.


Enjoy.


PS. Download links will be provided to you via PM, they are experimental images only for testing purposes.
So please don't ask for additional packages, cams, iptv or whatever.
The only purpose is to test that TBS tuner is recognized and MIS/PLS works.

 

HELLO i just install the new satdreamgr-images-experimental/vu/vusolo4k with VU+ patches

 

i put in telnet mod  :

 

1. Place TBS firmware into /lib/firmware

you can download firmware from here: http://www.tbsdtv.com/download/

2. Use Proper MIS/PLS codes

eg for Mediaset, RAI multistreams @5W, 13E you can found in https://github.com/c.../satellites.xml

3. Install kernel module, reboot

opkg update
opkg install kernel-module-dvb-usb-tbsusb
reboot

 

but no TBS tuner in tuners list !!!

 

if someone could help me

 

thank you

 

Edited by BOSSEB, 4 March 2016 - 19:14.

[athoik]

3. Install tbs drivers  from drivers menu or from console

opkg update
opkg install enigma2-plugin-drivers-dvb-usb-tbs
reboot

PS. 2 Is not fully implemented yet.

Edited by athoik, 4 March 2016 - 19:20.

[BOSSEB]

thanks

 

now i have the tuner in the list, but when i put satellites.xml I haven't any satellites in the scan system

[athoik]

MIS/PLS is not included yet. Soon.

But, with MIS/PLS included the lamedb will be version 5 so all known programs will not work...(eg dreamboxedit)

[athoik]

MIS/PLS patch included.

All vu boxes, et10000/et8000, osmini have the driver for TBS.

Lamedb will be version 5, dreamboxedit, channelizer etc should adapt.

Here are the Enigma2 changes:
https://github.com/O...oik:multistream

Please fill free to fix issues MIS/PLS related.

[BOSSEB]

thank you for your job

 

i just flash with your last update MIS/PLS patch is working but in the tuner advanced configuration there is just USALS ... Impossible to choose a satellite !

[athoik]

Can you post a screenshot?

Nobody mentioned that issue before.

[BOSSEB]

all screenshots

Attached Files

•  IMG_20160305_095617.jpg   93.01KB   13 downloads
•  IMG_20160305_095630.jpg   81.73KB   10 downloads
•  IMG_20160305_095635.jpg   99.55KB   10 downloads
•  IMG_20160305_095642.jpg   96.82KB   10 downloads
•  IMG_20160305_095649.jpg   100.58KB   10 downloads
•  IMG_20160305_095659.jpg   93.76KB   10 downloads

[athoik]

Please create screenshots from webif, they look much better.


Also I want to see screenshot from Tuner Configuration before selecting that tuner.

(I think you are selecting FBC link not the TBS card).

Edited by athoik, 5 March 2016 - 10:25.

[BOSSEB]

i put my old satellite.xml and it's works now !!! thank you for your help

[jpuigs]

On ET10000, when doing either manual scan or satfinder scan,  it doesn't appear PLS-MIS extra values.

It happens the same behaviour when we were privately testing OP5 images some weeks ago,

You told me then :

The problem is that FE_CAN_MULTISTREAM is not passed to vtuner!!!

We just find a ET10000 bug

 

 

Here is the tuner where I have TBS attached:

root@et10000:~# 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: "STV090x Multistandard"
    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
        FE_CAN_MULTISTREAM
        FE_CAN_2G_MODULATION

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

root@et10000:~#

Edited by jpuigs, 5 March 2016 - 14:29.

[athoik]

Yes, the bug is confirmed, although a workaround based on tuner name applied...
 

	def isMultistream(self):
		multistream = self.frontend_id and eDVBResourceManager.getInstance().frontendIsMultistream(self.frontend_id) or False
		# HACK due to poor support for VTUNER_SET_FE_INFO
		# When vtuner does not accept fe_info we have to fallback to detection using tuner name
		# More tuner names will be added when confirmed as multistream (FE_CAN_MULTISTREAM)
		if not multistream and "TBS" in self.description:
			multistream = True
		return multistream

What is the name of the tuner? Is TBS something or not?

PS. And what image are you using? MIS/PLS patches are not fully merged on Official OpenPLi yet.

Edited by athoik, 5 March 2016 - 14:34.

[jpuigs]

 tbs_5925_op4___.jpg   57.61KB   23 downloads

 

As you can see in the picture, name starts with TBS.

 

I'm testing it on current openpli 4 image, just because I've seen an earlier post which said: MIS/PLS patch included.

 

[athoik]

tbs_5925_op4___.jpg
 
As you can see in the picture, name starts with TBS.
 
I'm testing it on current openpli 4 image, just because I've seen an earlier post which said: MIS/PLS patch included.

Yes, MIS/PLS patch included on experimental SatDreamGR. There are some "prerequisites" in order to accepted to OpenPLi, currently it breaks lamedb and breaking something for only few users with TBS or Multistream enabled tuners is really bad...

Edited by athoik, 5 March 2016 - 14:44.

[jpuigs]

OK. Thanks. I thought those patches were on op4.

 

On your other experimental image, everything is fine.

[BOSSEB]

is it normal if zapping time is longer than the build-in tuner ??

[WanWizard]

Yes, USB tuners work in userspace, and send the entire transponder to be demuxed in software. A lot slower than a tuner the SoC can handle itself.

[el bandido]

Testing satdreamgr-images-experimental in Vu+Zero and having excellent results!

The TBS5925 channel zap time is almost as good a the internal tuners, just a tad bit slower than the internal tuner.

The Vu+Duo2 may activate the spinner and freeze for an instant when you land on a channel or a transponder with no signal. The Vu+ Zero Does Not have this issue using the TBS5925, and handles a loss of signal much better than the Duo2.

Here are screenshots of the Vu+Zero.




 Zero_About.jpg   63.38KB   10 downloads


 Zero_About.jpg   63.38KB   10 downloads

[BOSSEB]

Yes, USB tuners work in userspace, and send the entire transponder to be demuxed in software. A lot slower than a tuner the SoC can handle itself.

 

I have an other usb dvb-t tuner and zapping time is very fast but with the tbs5925 it's very long ...

[athoik]

Can you post an enigma2 log?

Every dvb-usb card uses the vtuner interface and it is known that vtuner implementation is not always so good..

Since you are the only one with solo4k and tbs card you can imagine how hard is..

Also support for TBS is not in official kernel.

So don't expect miracles.