ISDB-T devices: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
(start new layout)
No edit summary
(5 intermediate revisions by 3 users not shown)
Line 5: Line 5:
*[[ISDB-T PCMCIA Cards]] (PC Card/CardBus, ExpressCard)
*[[ISDB-T PCMCIA Cards]] (PC Card/CardBus, ExpressCard)


== Support for Brazilian television ==


Linux now includes support for capturing Brazilian television, which uses the ISDB-T standard.
[[Category:Hardware|!ISDB-T devices]]
[[Category:ISDB-T|!ISDB-T devices]]


Mauro Carvalho Chehab wrote this about supported device availability on 29 December 2014:
Currently, There are one driver that support ISDB-T:


: One supported hardware that it seems it is still in sales in Brazil is this one:
== ISDB-T open source drivers ==
=== dibcom ===
The dib0700 implements the new DVBS2API to allow finer control at the ISDB-T parameters.


:: http://www.kabum.com.br/produto/6784/receptor-de-tv-digital-pixelview-playtv-usb-2-0-sbtvd-full-seg-pv-d231urn-f
====Devices====
- [http://www.linuxtv.org/wiki/index.php/ISDB-T_Devices#PixelView_PlayTV_USB_SBTVD PixelView PlayTV USB SBTVD]<br>
- [http://www.linuxtv.org/wiki/index.php/ISDB-T_Devices#Evolutepc_TVWay.2B Evolutepc TVWay+]


: It is based on a chipset that it is not manufactured anymore (mb86a20s), so it will eventually start to be harder to find it.
=== pt1 ===
Earthsoft PT1 Driver
==== Devices ====


: There are some devices based on Dibcom dib8096 and on Siano sms2270 that aren't deprecated, but I'm not sure what are the brand names for devices with those chipsets that are currently in the market.
=== em28xx ===
==== Devices ====
- [http://www.linuxtv.org/wiki/index.php/ISDB-T_Devices#Leadership_ISDB-T Leadership ISDB-T]
- [http://www.linuxtv.org/wiki/index.php/ISDB-T_Devices#Multilaser_ISDB-T Multilaser ISDB-T]


: The sms2270 is, IMHO, the best chipset for ISDB-T, but the last device I got has no brand on it (it is a "generic" tuner made in China).
== How to make it work with the current dvb-apps version? ==


:: sms2270 datasheet: http://www.siano-ms.com/cn/images/pdfs/siano_sms2270_pb_0311_web.pdf
Some changes are needed at dvb-apps in order to support the new DVBS2API parameters for ISDB-T. While those changes aren't implemented there and at the userspace apps, you need to use the DVB-T format.


: The thing with those devices is that the vendors change the hardware from time to time without notice, and sometimes, without even changing their brand name.
In the case of ISDB-T, the current implementations (Brazil and Japan) use 6 MHz bandwidth with the same [[ISDB-T Frequency Table]]. In the future, this is likely to change.


For the device to work, the first step is to seek for the existing channels. This is done by running the 'scan' application:
scan FrequencyTable >channels.conf


Here is a list of devices with its main features: https://www.linuxtv.org/wiki/index.php/Cards_and_dongles_for_ISDB-T
Then, a DVB-T userspace application can be used to play the stream. In the case of Brazil, the application needs to support H.264 for video, HE-AAC for audio, and PMT tables at the mpeg-ts. Currently, only vlc and the newest development versions of mplayer are known to support. However, some stream types are known to not work with none of those two applications, due to some existing bugs.


== ISDB-T Boards ==
== Outdated section ==
=== PixelView PlayTV USB SBTVD ===
[[File:box-pixelviewplaytv-isdb.jpg|300px]] [[File:pixelviewplaytv-isdb-device.jpg|300px]][[File:pixelviewplaytv-isdb-device01.jpg|300px]]
<br>
[[File:pixelviewplaytv-isdb-dibcom00.jpg|300px]] [[File:pixelviewplaytv-isdb-dibcom01.jpg|300px]]<br>
<br>
==== lsusb - vendor/product id ====
ID 1554:5010 Prolink Microsystems Corp.
==== Status ====
Sep 27 2009 - Working
==== Driver ====
dibcom


Support for ISDB-T devices is currently in its infancy under Linux, having only been added to the [[S2API|Linux DVB S2API]] in September 2009. The number of drivers and supported devices will surely grow in time.
=== Multilaser ISDB-T ===
[[File:box-multilaser-isdb.jpg|300px]] [[File:multilaser-isdb-device.jpg|300px]]<br>
[[File:multilaser-isdb-frontend.jpg|300px]] [[File:multilaser-isdb-empia.jpg|300px]]
<br>
==== lsusb - vendor/product id ====
1d19:3102
==== Status ====
Sep 27 2009 - Work in progress
==== Driver ====
em28xx


===How do I make ISDB-T devices work with the current dvb-apps version? ===
=== Leadership ISDB-T ===
[[File:box-leadership-isdb.jpg|300px]] [[File:leadership-isdb-device.jpg|300px]]<br>
[[File:leadership-isdb-frontend.jpg|300px]] [[File:leadership-isdb-empia.jpg|300px]]
<br>
==== lsusb - vendor/product id ====
eb1a:2875 eMPIA Technology, Inc.


Currently, some changes are needed within the [[LinuxTV dvb-apps|dvb-apps]] in order to support the new DVBS2API parameters for ISDB-T. Until those changes are implemented there, and within userspace apps, you will need to use the DVB-T format.
==== I2C devicelist hash table ====
0x6b800080
==== Status ====
Sep 27 2009 - Work in progress
==== Driver ====
em28xx


In the case of ISDB-T, the current implementations (Brazil and Japan) use 6 MHz bandwidth with the same [[ISDB-T Frequency Table]]. In the future, this is likely to change.
===Evolutepc TVWay+===
==== lsusb - vendor/product id ====
0x1e59 0x0002
==== Status ====
Sep 27 2009 - Work in progress
==== Driver ====
dibcom


For the device to work, the first step is to seek for the existing channels. This is done by running the 'scan' application:
=== Zaggy ISDB-T ===
scan FrequencyTable >channels.conf
[[File:box-zaggy-isdb.jpg|300px]] [[File:zaggy-isdb-device.jpg|300px]] [[File:zaggy-isdb-device01.jpg|300px]]<br>
[[File:zaggy-isdb-empia.jpg|300px]] [[File:zaggy-isdb-frontend.jpg|300px]] [[File:zaggy-isdb-frontend01.jpg|300px]]
<br>
==== lsusb - vendor/product id ====
eb1a:2861 eMPIA Technology, Inc.
==== Status ====
Sep 27 2009 - Work in progress
==== Driver ====
em28xx


Then, a DVB-T userspace application can be used to play the stream. In the case of Brazil, the application needs to support H.264 for video, HE-AAC for audio, and PMT tables at the mpeg-ts. Currently, only vlc and the newest development versions of mplayer are known to support. However, some stream types are known to not work with none of those two applications, due to some existing bugs.
=== AOC ISDB-T ===
==== ConnecTV Digital ====
[[File:box-aoc-conectv-isdb.jpg|300px]] [[File:aoc-conectv-isdb-device.jpg|300px]]
[[File:aoc-conectv-isdb-device01.jpg|300px]] [[File:aoc-conectv-isdb-device02.jpg|300px]]<br>
[[File:aoc-conectv-isdb-alps.jpg|300px]] [[File:aoc-conectv-isdb-lattice.jpg|300px]] [[File:aoc-conectv-isdb-cy.jpg|300px]]<br>

<br>
==== lsusb - vendor/product id ====
0x1170 0x0020

==== Status ====
Sep 27 2009 - Work in progress

<br>

=== JH Full HD Digital TV Receiver (A.K.A TBS USB ISDB-T Stick) ===
[[File:jh-box.jpg|300px]] [[File:jh-board-top.jpg|300px]] [[File:jh-board-botton.jpg|300px]]

==== dmesg ====
usb 1-6: new high speed USB device using ehci_hcd and address 4

==== lsusb - vendor/product id ====
734c:db08

==== lsusb detail information ====
lsusb -v -d 734c:db08
Bus 001 Device 004: ID 734c:db08
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x734c
idProduct 0xdb08
bcdDevice 0.01
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 171
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

==== Chipsets ====

*Tuner - NXP [http://www.nxp.com/pip/TDA18271HD_4.html TDA18271HD]
*Demodulator - [[Fujitsu_MB86A16]]
*USB interface - [http://www.cypress.com/ Cypress Semiconductor] EZ-USB FX2LP [http://www.cypress.com/?rID=14181 CY7C68013A]
*Other - [http://www.fs-rank.com/ Shenzen First-Rank Technology] [http://fsrank54.xm15.host.35.com/uploadfile/20090519140118389.pdf T24C02A] EEPROM 256 x 8 (2K bits)

==== Aditional Information ====
Device requires a specific firmware to operate.


==== Status ====
Sep 27 2009 - Unknow


[[Category:Hardware| ]]
==== Company Website ====
[[Category:ISDB-T| ]]
[http://www.tbsdtv.com/english/product/USBISDB-T.html TBS Media Expert]

Revision as of 19:17, 15 February 2016

Support for Brazilian television

Linux now includes support for capturing Brazilian television, which uses the ISDB-T standard.

Mauro Carvalho Chehab wrote this about supported device availability on 29 December 2014:

One supported hardware that it seems it is still in sales in Brazil is this one:
http://www.kabum.com.br/produto/6784/receptor-de-tv-digital-pixelview-playtv-usb-2-0-sbtvd-full-seg-pv-d231urn-f
It is based on a chipset that it is not manufactured anymore (mb86a20s), so it will eventually start to be harder to find it.
There are some devices based on Dibcom dib8096 and on Siano sms2270 that aren't deprecated, but I'm not sure what are the brand names for devices with those chipsets that are currently in the market.
The sms2270 is, IMHO, the best chipset for ISDB-T, but the last device I got has no brand on it (it is a "generic" tuner made in China).
sms2270 datasheet: http://www.siano-ms.com/cn/images/pdfs/siano_sms2270_pb_0311_web.pdf
The thing with those devices is that the vendors change the hardware from time to time without notice, and sometimes, without even changing their brand name.


Here is a list of devices with its main features: https://www.linuxtv.org/wiki/index.php/Cards_and_dongles_for_ISDB-T

Outdated section

Support for ISDB-T devices is currently in its infancy under Linux, having only been added to the Linux DVB S2API in September 2009. The number of drivers and supported devices will surely grow in time.

How do I make ISDB-T devices work with the current dvb-apps version?

Currently, some changes are needed within the dvb-apps in order to support the new DVBS2API parameters for ISDB-T. Until those changes are implemented there, and within userspace apps, you will need to use the DVB-T format.

In the case of ISDB-T, the current implementations (Brazil and Japan) use 6 MHz bandwidth with the same ISDB-T Frequency Table. In the future, this is likely to change.

For the device to work, the first step is to seek for the existing channels. This is done by running the 'scan' application: 

 scan FrequencyTable >channels.conf

Then, a DVB-T userspace application can be used to play the stream. In the case of Brazil, the application needs to support H.264 for video, HE-AAC for audio, and PMT tables at the mpeg-ts. Currently, only vlc and the newest development versions of mplayer are known to support. However, some stream types are known to not work with none of those two applications, due to some existing bugs.

Retrieved from "https://www.linuxtv.org/wiki/index.php?title=ISDB-T_devices&oldid=34679"