Top Tip T2-MI reception on E2 STB with SDG image - A complete step by step guide

MCelliotG

MCelliotG

Specialist Contributor
Messages
682
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
T2-MI on SatDreamGr images detailed guide/tutorial

1. Introduction

T2-MI is a special transmission method where a whole DVB-T2 stream is capped inside a data pid of a satellite transponder that is used to feed a terrestrial DVB-T2 transmitter. Until now, only some selected software was able to decapsulate these streams, notably for PC.

The SatDreamGr team made possible to implement this decapsulation to its supported Enigma2 receivers. So far this is done via the astra-sm project which works parallel to Enigma2 as a process, with the difference that it can now be done completely by the receiver without the need of an external device like a PC. The channels are being decapsulated internally as a stream favourites bouquet and can be viewed as regular channels with everything that there is inside the transponder stream such as EPG, teletext, audio streams etc.

The philosophy includes the data channel, which can be tuned with the receiver’s tuner (unless it’s also a multistream transmission, which requires a USB tuner like TBS) and acts as a feed for the T2-MI stream. This stream becomes an input for the astra-sm process, and with the help of a special script and a configuration file can be output as a stream package via internal stream relay. Note that this is the same way Powervu works for E2 STBs that don’t support direct emulation. The stream relay can then be stripped to separate channels that will compile a favourites bouquet which will work as a regular ready-to-view channel bouquet in the E2 receiver.

In this tutorial, I will show a complete step-by-step guide that will help you tune to these T2-MI streams and configure them to use on your E2 STB using the SatDreamGr image.


2. What you will need

a) your E2 STB :)

b) the SatDreamGr experimental image which can be downloaded here

c) Dreamboxedit on your PC for editing the streams and bouquets as required

d) a UNIX editor (like Notepad++ or UltraEdit).

e) an FTP client to connect to your STB (like Filezilla or FlashFXP)

f) a telnet client for certain commands (like Putty)


3. Getting the feed channel

Every Enigma2 receiver when it gets tuned to a T2-MI transponder will not download the channels directly (although this automation has to be implemented in the near future). Instead the tuner will lock and download a data channel. In the following example we used a T2-MI transponder on the C band of Express AM7 satellite on 40E.

In this image you can see that this frequency (3685L) is tuned normally with the internal tuner.


Now, scanning the frequency downloads the data service (it might take a while).


This data channel will act as our feed, as it contains the T2-MI stream. In 99% of these transmissions, this stream is contained in pid 4096. In order for the E2 STB to have it directly visible to the user in their channel list, it must be edited in the lamedb. There are two options; either direct lamedb editing (hard way) or editing via Dreamboxedit (easier).

With Dreamboxedit, the data service will be edited to look as a “fake” TV service (visible in the list). The pid 4096 has to be added manually too, as a cached pid.

After downloading the data service, FTP the channels to Dreamboxedit on your PC and locate the data service you just downloaded.

Click on the service and you will see a screen like this one:

Now change these parameters:

Name: input a descriptive name for the fake service. This is important as it will affect the configuration later on. In this example I give the name 3685L T2-MI.

Service Type: 1 (TV)

Check the K (Keep). This is also very important, so that the service will not be reverted to data on a future satellite scanning.

Extra parameters: add c:151000, where 15 is the cached index and 1000 is the hex value for 4096. This will cache this pid in the lamedb, and will provide all T2-MI data.

Click Save.

After this editing, the data service reference will change to 1:0:1:320:32A:0:1910E65:0:0:0:

Keep this service ref in mind, as it will be used in the configuration too.

After editing you can send the entries back to your STB. Make sure to completely reboot the STB after sending, and not just reload the commands, in order for lamedb changes to stick.

Now we are ready for Part 2 of this guide.
 
MCelliotG

MCelliotG

Specialist Contributor
Messages
682
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
4. Analyzing the stream

After rebooting, first make sure the fake service appears on your channel list with the given name. If everything went right it will tune normally with no error messages, and of course with no picture/sound.

Now, we are ready to preview what’s “inside” this fake service. In order to do that, we will have to analyze the stream using the astra commands.

First off we need to have astra-sm installed. For this we need a telnet tool to connect to our STB. In this example I used putty.

After connecting with putty give this command:

Code:
opkg install astra-sm


Astra is finally installed. Now let’s analyze our stream. For that we need the serviceref of the fake service we created to be streamed within our STB. We will use 127.0.0.1:8001 which is our STB’s internal IP and relay port and the serviceref of our fake service.
Let's now see the analyze results.
 
MCelliotG

MCelliotG

Specialist Contributor
Messages
682
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
To analyze use the following command:
Code:
astra --analyze "t2mi://#t2mi_pid=4096&t2mi_input=http://127.0.0.1:8001/1:0:1:320:3A2:0:1910E65:0:0:0:"
This will give us a running output. Use Ctrl+C to stop the command.

The output in putty should look like this:
Code:
root@vusolo2:~# astra --analyze "t2mi://#t2mi_pid=4096&t2mi_input=http://127.0.0.1:8001/1:0:1:320:3A2:0:1910E65:0:0:0:"
    Nov 13 06:57:08: INFO: Starting Astra SM 0.2
    Nov 13 06:57:08: INFO: [t2mi/analyze] L1-current: PLP 0 (Data Type 1), group 1 (*)
    Nov 13 06:57:08: INFO: [t2mi/analyze] L1-current: PLP 1 (Data Type 1), group 1
    Nov 13 06:57:08: INFO: [t2mi/analyze] selected data PLP 0 (auto)
    Nov 13 06:57:08: INFO: PAT: tsid: 11
    Nov 13 06:57:08: INFO: PAT: pid: 16 NIT
    Nov 13 06:57:08: INFO: PAT: pid: 2010 PMT pnr: 2010
    Nov 13 06:57:08: INFO: PAT: pid: 2020 PMT pnr: 2020
    Nov 13 06:57:08: INFO: PAT: pid: 2030 PMT pnr: 2030
    Nov 13 06:57:08: INFO: PAT: pid: 2040 PMT pnr: 2040
    Nov 13 06:57:08: INFO: PAT: pid: 2050 PMT pnr: 2050
    Nov 13 06:57:08: INFO: PAT: pid: 2060 PMT pnr: 2060
    Nov 13 06:57:08: INFO: PAT: pid: 2070 PMT pnr: 2070
    Nov 13 06:57:08: INFO: PAT: pid: 2080 PMT pnr: 2080
    Nov 13 06:57:08: INFO: PAT: pid: 2090 PMT pnr: 2090
    Nov 13 06:57:08: INFO: PAT: pid: 2100 PMT pnr: 2100
    Nov 13 06:57:08: INFO: PAT: crc32: 0xD7A1B3F
    Nov 13 06:57:08: INFO: PMT: pnr: 2090
    Nov 13 06:57:08: INFO: PMT: pid: 2091 PCR
    Nov 13 06:57:08: INFO: PMT: descriptor: 0x050443554549
    Nov 13 06:57:08: INFO: VIDEO: pid: 2091 type: MPEG-4 AVC/H.264, ISO/IEC 14496-10 (0x1B)
    Nov 13 06:57:08: INFO: AUDIO: pid: 2092 type: MPEG-1 audio, ISO/IEC 11172-3 (0x03)
    Nov 13 06:57:08: INFO: DATA: pid: 2095 type: User private (0x86)
    Nov 13 06:57:08: INFO: PMT: crc32: 0x3461464C
    Nov 13 06:57:08: INFO: PMT: pnr: 2050
    Nov 13 06:57:08: INFO: PMT: pid: 2051 PCR
    Nov 13 06:57:08: INFO: PMT: descriptor: 0x050443554549
    Nov 13 06:57:08: INFO: VIDEO: pid: 2051 type: MPEG-4 AVC/H.264, ISO/IEC 14496-10 (0x1B)
    Nov 13 06:57:08: INFO: AUDIO: pid: 2052 type: MPEG-1 audio, ISO/IEC 11172-3 (0x03)
    Nov 13 06:57:08: INFO: DATA: pid: 2055 type: User private (0x86)
    Nov 13 06:57:08: INFO: PMT: crc32: 0xD50E9346
    Nov 13 06:57:08: INFO: PMT: pnr: 2030
    Nov 13 06:57:08: INFO: PMT: pid: 2031 PCR
    Nov 13 06:57:08: INFO: PMT: descriptor: 0x050443554549
    Nov 13 06:57:08: INFO: VIDEO: pid: 2031 type: MPEG-4 AVC/H.264, ISO/IEC 14496-10 (0x1B)
    Nov 13 06:57:08: INFO: AUDIO: pid: 2032 type: MPEG-1 audio, ISO/IEC 11172-3 (0x03)
    Nov 13 06:57:08: INFO: DATA: pid: 2035 type: User private (0x86)
    Nov 13 06:57:08: INFO: PMT: crc32: 0xE10BD564
    Nov 13 06:57:08: INFO: PMT: pnr: 2100
    Nov 13 06:57:08: INFO: PMT: pid: 2101 PCR
    Nov 13 06:57:08: INFO: VIDEO: pid: 2101 type: MPEG-4 AVC/H.264, ISO/IEC 14496-10 (0x1B)
    Nov 13 06:57:08: INFO: AUDIO: pid: 2102 type: MPEG-1 audio, ISO/IEC 11172-3 (0x03)
    Nov 13 06:57:08: INFO: PMT: crc32: 0x5D2C7C65
    Nov 13 06:57:08: INFO: PMT: pnr: 2040
    Nov 13 06:57:08: INFO: PMT: pid: 2041 PCR
    Nov 13 06:57:08: INFO: PMT: descriptor: 0x050443554549
    Nov 13 06:57:08: INFO: VIDEO: pid: 2041 type: MPEG-4 AVC/H.264, ISO/IEC 14496-10 (0x1B)
    Nov 13 06:57:08: INFO: AUDIO: pid: 2042 type: MPEG-1 audio, ISO/IEC 11172-3 (0x03)
    Nov 13 06:57:08: INFO: DATA: pid: 2045 type: User private (0x86)
    Nov 13 06:57:08: INFO: PMT: crc32: 0x81CF798A
    Nov 13 06:57:08: INFO: PMT: pnr: 2070
    Nov 13 06:57:08: INFO: PMT: pid: 2071 PCR
    Nov 13 06:57:08: INFO: PMT: descriptor: 0x050443554549
    Nov 13 06:57:08: INFO: VIDEO: pid: 2071 type: MPEG-4 AVC/H.264, ISO/IEC 14496-10 (0x1B)
    Nov 13 06:57:08: INFO: AUDIO: pid: 2072 type: MPEG-1 audio, ISO/IEC 11172-3 (0x03)
    Nov 13 06:57:08: INFO: DATA: pid: 2075 type: User private (0x86)
    Nov 13 06:57:08: INFO: PMT: crc32: 0x68E73575
    Nov 13 06:57:08: INFO: PMT: pnr: 2010
    Nov 13 06:57:08: INFO: PMT: pid: 2011 PCR
    Nov 13 06:57:08: INFO: PMT: descriptor: 0x050443554549
    Nov 13 06:57:08: INFO: VIDEO: pid: 2011 type: MPEG-4 AVC/H.264, ISO/IEC 14496-10 (0x1B)
    Nov 13 06:57:08: INFO: AUDIO: pid: 2012 type: MPEG-1 audio, ISO/IEC 11172-3 (0x03)
    Nov 13 06:57:08: INFO: DATA: pid: 2015 type: User private (0x86)
    Nov 13 06:57:08: INFO: PMT: crc32: 0x925EABE4
    Nov 13 06:57:08: INFO: PMT: pnr: 2060
    Nov 13 06:57:08: INFO: PMT: pid: 2061 PCR
    Nov 13 06:57:08: INFO: PMT: descriptor: 0x050443554549
    Nov 13 06:57:08: INFO: VIDEO: pid: 2061 type: MPEG-4 AVC/H.264, ISO/IEC 14496-10 (0x1B)
    Nov 13 06:57:08: INFO: AUDIO: pid: 2062 type: MPEG-1 audio, ISO/IEC 11172-3 (0x03)
    Nov 13 06:57:08: INFO: DATA: pid: 2065 type: User private (0x86)
    Nov 13 06:57:08: INFO: PMT: crc32: 0x5FAAE788
    Nov 13 06:57:08: INFO: PMT: pnr: 2080
    Nov 13 06:57:08: INFO: PMT: pid: 2081 PCR
    Nov 13 06:57:08: INFO: VIDEO: pid: 2081 type: MPEG-4 AVC/H.264, ISO/IEC 14496-10 (0x1B)
    Nov 13 06:57:08: INFO: AUDIO: pid: 2082 type: MPEG-1 audio, ISO/IEC 11172-3 (0x03)
    Nov 13 06:57:08: INFO: PMT: crc32: 0x9BE38B
    Nov 13 06:57:08: INFO: PMT: pnr: 2020
    Nov 13 06:57:08: INFO: PMT: pid: 2021 PCR
    Nov 13 06:57:08: INFO: VIDEO: pid: 2021 type: MPEG-4 AVC/H.264, ISO/IEC 14496-10 (0x1B)
    Nov 13 06:57:08: INFO: AUDIO: pid: 2022 type: MPEG-1 audio, ISO/IEC 11172-3 (0x03)
    Nov 13 06:57:08: INFO: PMT: crc32: 0x996F487D
    Nov 13 06:57:08: INFO: SDT: tsid: 11
    Nov 13 06:57:08: INFO: SDT: sid: 2010
    Nov 13 06:57:08: INFO: SDT:    Service: 11 РЕН ТВ
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2020
    Nov 13 06:57:08: INFO: SDT:    Service: 12 Спас
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2030
    Nov 13 06:57:08: INFO: SDT:    Service: 13 СТС
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2040
    Nov 13 06:57:08: INFO: SDT:    Service: 14 Домашний
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2050
    Nov 13 06:57:08: INFO: SDT:    Service: 15 ТВ3
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2060
    Nov 13 06:57:08: INFO: SDT:    Service: 16 Пятница
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2070
    Nov 13 06:57:08: INFO: SDT:    Service: 17 Звезда
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2080
    Nov 13 06:57:08: INFO: SDT:    Service: 18 МИР
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2090
    Nov 13 06:57:08: INFO: SDT:    Service: 19 ТНТ
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2100
    Nov 13 06:57:08: INFO: SDT:    Service: 20 МУЗ ТВ
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: crc32: 0xAED416EA
    Nov 13 06:57:09: INFO: Bitrate: 19674 Kbit/s
    Nov 13 06:57:10: INFO: Bitrate: 31234 Kbit/s
    Nov 13 06:57:11: INFO: Bitrate: 31278 Kbit/s
    Nov 13 06:57:12: INFO: Bitrate: 31237 Kbit/s
    Nov 13 06:57:13: INFO: Bitrate: 31280 Kbit/s
    Nov 13 06:57:14: INFO: Bitrate: 31236 Kbit/s
    Nov 13 06:57:15: INFO: Bitrate: 31277 Kbit/s
    Nov 13 06:57:16: INFO: Bitrate: 31234 Kbit/s
    Nov 13 06:57:17: INFO: Bitrate: 31281 Kbit/s
    Nov 13 06:57:18: INFO: Bitrate: 31231 Kbit/s
    Nov 13 06:57:19: INFO: Bitrate: 31233 Kbit/s
    Nov 13 06:57:20: INFO: Bitrate: 31227 Kbit/s
    Nov 13 06:57:21: INFO: Bitrate: 31235 Kbit/s
    ^CNov 13 06:57:22: INFO: [main] shutting down
From the above output we get the info that the stream contains two PLPs (0 and 1) and the channels of PLP 0 are these:

Code:
Nov 13 06:57:08: INFO: SDT: sid: 2010
    Nov 13 06:57:08: INFO: SDT:    Service: 11 РЕН ТВ
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2020
    Nov 13 06:57:08: INFO: SDT:    Service: 12 Спас
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2030
    Nov 13 06:57:08: INFO: SDT:    Service: 13 СТС
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2040
    Nov 13 06:57:08: INFO: SDT:    Service: 14 Домашний
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2050
    Nov 13 06:57:08: INFO: SDT:    Service: 15 ТВ3
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2060
    Nov 13 06:57:08: INFO: SDT:    Service: 16 Пятница
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2070
    Nov 13 06:57:08: INFO: SDT:    Service: 17 Звезда
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2080
    Nov 13 06:57:08: INFO: SDT:    Service: 18 МИР
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2090
    Nov 13 06:57:08: INFO: SDT:    Service: 19 ТНТ
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2100
    Nov 13 06:57:08: INFO: SDT:    Service: 20 МУЗ ТВ
This info will be useful when creating the bouquet list, so save it for later.
 
MCelliotG

MCelliotG

Specialist Contributor
Messages
682
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
5. Making the configuration

It’s time to make the astra configuration. Use an FTP manager to navigate to your STB’s file, and inside the /etc folder create a new folder called astra. The path should be /etc/astra

Using a UNIX editor (in the example I used Notepad ++) create a new file called astra.conf and add the following code:
Code:
f3685rtrn0 = make_t2mi_decap({
        name = "3685L T2-MI",
        input = "http://127.0.0.1:8001/1:0:1:320:3A2:0:1910E65:0:0:0:",
        plp = 0,
        pnr = 0,
        pid = 4096,
})
In the above code:

f3685rtrn0 is the name of the capped input. Make sure to start with a letter and not a number. In this example we used f 3685 rtrn and 0 (frequency, provider, and plp number).

the input is the serviceref of the “fake” service we created earlier, and 127.0.0.1:8001 is the internal STB ip and stream port.

"name" is the exact name of the feed channel we gave earlier

plp is the number of the PLP which was shown in the analyze part. For 3685 we used plp 0 which contains the channels we need.

"pid" is the 4096 we cached in our lamedb entry.

After this piece of code let’s make the stream output using this code:
Code:
make_channel({                                                         
        name = "3685plp0", input = { "t2mi://f3685rtrn0", },           
        output = { "http://0.0.0.0:9999/rtrn/3685plp0", },             
})
The output is the internal output relay for our STB

rtrn is a given path name to segregate the different packages, we give a name of our choice

3685plp0 is the output name for this T2-MI stream. This will be used in Dreamboxedit too.

So, to summarize the code in the astra.conf file in order to stream relay the channels of 3685L is going to look like this:
Code:
log.set({ stdout = false, debug = false, syslog = "astra", })
f3685rtrn0 = make_t2mi_decap({
        name = "3685L T2-MI",
        input = "http://127.0.0.1:8001/1:0:1:320:3A2:0:1910E65:0:0:0:",
        plp = 0,
        pnr = 0,
        pid = 4096,
})
make_channel({                                                         
        name = "3685plp0", input = { "t2mi://f3685rtrn0", },           
        output = { "http://0.0.0.0:9999/rtrn/3685plp0", },             
})
6. Making our favourites stream bouquet

This is the final part in our tutorial. We have already analyzed the stream and got its content via telnet.
Code:
Nov 13 06:57:08: INFO: SDT: sid: 2010
    Nov 13 06:57:08: INFO: SDT:    Service: 11 РЕН ТВ
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2020
    Nov 13 06:57:08: INFO: SDT:    Service: 12 Спас
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2030
    Nov 13 06:57:08: INFO: SDT:    Service: 13 СТС
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2040
    Nov 13 06:57:08: INFO: SDT:    Service: 14 Домашний
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2050
    Nov 13 06:57:08: INFO: SDT:    Service: 15 ТВ3
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2060
    Nov 13 06:57:08: INFO: SDT:    Service: 16 Пятница
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2070
    Nov 13 06:57:08: INFO: SDT:    Service: 17 Звезда
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2080
    Nov 13 06:57:08: INFO: SDT:    Service: 18 МИР
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2090
    Nov 13 06:57:08: INFO: SDT:    Service: 19 ТНТ
    Nov 13 06:57:08: INFO: SDT:    Provider: РТРС
    Nov 13 06:57:08: INFO: SDT: sid: 2100
    Nov 13 06:57:08: INFO: SDT:    Service: 20 МУЗ ТВ
Now we need to add each one of the above channels to our list

We go back to Dreamboxedit and on the bouquets column we right click and select “Insert new bouquet”. Let’s name it “RTRN T2-MI (40E)”

Now let’s add the channels. On the newly created bouquet column right-click and select “IPTV and other streaming services” and Add. It will lead to this screen:


Select Stream type: DVB/TS

Name: the name of the channel preferably as given by the analyze

URL: the output url of the PLP (it will be the same for all the channels of the same PLP)

Service Type: 1 for TV and 2 for Radio

Service ID: The sid of the channel

The rest three entries can be edited freely of even not at all. However they are useful to edit smartly in order to keep all channels to the same bouquet and give them a serviceref for easier classification. In this case I have input:

Transponder ID: I like to put the frequency of the transponder

Network ID: I usually input the satellite orbital position or PLP number

Namespace can be left blank.

So, the edited screen should look like this:


After editing click Add.

Repeat the same procedure for the rest of the SIDS, prefering to keep the same Transponder ID and Network ID for the same frequency and PLP.

Our stream bouquet is ready to go. Save everything and FTP back to your STB.

You are now ready to watch the T2-MI channels.

Important note: Streaming occupies the tuner, so essentially is the same as recording. You can change directly from a regular channel to your stream bouquet but not the other way round. To return to the regular channels list you need to retune to the feed channel (all others will be greyed out). For facilitation, you can also add the feed service to your stream list.
Also note that currently these stream services cannot be recorded to your HDD, hoping this will be fixed in the near future.

Here’s a video example (c/o Captain Jack):

7. Conclusion
In the above tutorial, I showed you how to add a new set of T2-MI channels as a stream relay favourites bouquet in your SDG image supported E2 STB. The process is long and difficult, but definitely worth it. Channel zapping is seamless and very fast and the channels transmit all their data like EPG, teletext etc.
We encourage the users to make configurations for all available T2-MI streams. You can send me these conf files to add to SDG feed for future users facilitation. In the near future we hope for a more automated T2-MI implementation into the Enigma2 core, so that these channels can be downloaded as normal channels, able to be recorded directly. This will take extensive changes and patching and good coding, so if there is more interest, good coders will make this possible for all Enigma2 and other images as well.
For the moment this is the best implementation there is.
I hope I made this documentation and guide as detailed as possible!
Enjoy!!!
 
Captain Jack

Captain Jack

Модератор
Staff member
Messages
10,601
My Satellite Setup
See signature
My Location
North Somerset
Excellent how to! Stickied.
 
A

Archive-8

Guest
Will there be a plugin available to add the multi stream straight in, just like you can get for other packages?

Or do we have to do this for all channels?

Or is there an available sat xml/lame db?
 
MCelliotG

MCelliotG

Specialist Contributor
Messages
682
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
The idea is to gather everything that there is T2-MI on satellite, make configurations and then add them ready to the SDG feed. So far we have only Zeonbud on 4.8E and RTRN on 40E, but there's lots of others as well. This guide will help anyone who is willing to try decapping T2-MI streams we haven't got ready yet and post them for the rest! Of course it's a lot of effort, but always the first ones have to do the dirty work!
 
Captain Jack

Captain Jack

Модератор
Staff member
Messages
10,601
My Satellite Setup
See signature
My Location
North Somerset
Other than 55e, are there any other satellites and frequencies that you know of that carry TI2 MI? I have a spot at the front of my house where I can get 55e - perhaps lash up a temporary dish to scan it...
 
P

Pierangelo

Regular Member
Messages
183
My Satellite Setup
150 cm from 80 east to 40 west + C lnb
My Location
Italy
Dear,
do you think It could be implemented on a standard pc card?
Regards
 
CrazyCat

CrazyCat

Regular Member
Messages
86
My Satellite Setup
13E 4.8E 4W: Dish Variant CA-902 0.95m + 3xLNB Ku-Universal DreamSat DS8 + DiseqC 1.0
30W-95E: Dish Strong 0.95m + LNB Ku-Universal ALPS BSTE8-751B + Motor PowerTech DG240
OpenBox X-800
TT S-1401 PCI
Omicom S2 PCI
TBS 5980 USB2.0
My Location
Ukraine, Kharkov
But this was implemented first-time on PC with any suitable PC DVB device :)
 
P

Pierangelo

Regular Member
Messages
183
My Satellite Setup
150 cm from 80 east to 40 west + C lnb
My Location
Italy
But this was implemented first-time on PC with any suitable PC DVB device :)
Thanks but it seems my skystar hd usb 2 is not suitable for crazyscan an 4t2, are there other ways?
Thanks
 
CrazyCat

CrazyCat

Regular Member
Messages
86
My Satellite Setup
13E 4.8E 4W: Dish Variant CA-902 0.95m + 3xLNB Ku-Universal DreamSat DS8 + DiseqC 1.0
30W-95E: Dish Strong 0.95m + LNB Ku-Universal ALPS BSTE8-751B + Motor PowerTech DG240
OpenBox X-800
TT S-1401 PCI
Omicom S2 PCI
TBS 5980 USB2.0
My Location
Ukraine, Kharkov
In linux you can use your device + astra-sm + any IPTV player :) Or same way with Enigma2PC + astra-sm.
 
P

Pierangelo

Regular Member
Messages
183
My Satellite Setup
150 cm from 80 east to 40 west + C lnb
My Location
Italy
Dear,
is it possibile that 9 db and a big ber is not enough to watch them?

During 10 minutes of watching, I found some data with russian name, but only for seconds....

Ciao
Regards


t2-mi.jpg
 
MCelliotG

MCelliotG

Specialist Contributor
Messages
682
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
Yes I see you have setup everything correctly but you receive about 4 mbps of data while normally it should be over 25. Besides these transmissions generally require at least 11db for stable picture!

Στάλθηκε από το LG G3 μου μέσω tapatalk.
 
CrazyCat

CrazyCat

Regular Member
Messages
86
My Satellite Setup
13E 4.8E 4W: Dish Variant CA-902 0.95m + 3xLNB Ku-Universal DreamSat DS8 + DiseqC 1.0
30W-95E: Dish Strong 0.95m + LNB Ku-Universal ALPS BSTE8-751B + Motor PowerTech DG240
OpenBox X-800
TT S-1401 PCI
Omicom S2 PCI
TBS 5980 USB2.0
My Location
Ukraine, Kharkov
is it possibile that 9 db and a big ber is not enough to watch them?
If your receiver report correct SNR in dB and have good sensitivity :)
If you have some Dreambox or VU+ with integrated Broadcom demod - this usual report incorrect SNR value and require more signal. So see BER. must be 0. I think you need +1-2dB for error-free reception with 0 dB link margin.
 
solly

solly

Specialist Contributor
Messages
4,319
My Location
Tel Aviv, Israel
any soport dreambox 900uhd ?
 
MCelliotG

MCelliotG

Specialist Contributor
Messages
682
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
You should have no problem at all with openatv 6!

Στάλθηκε από το LG G3 μου μέσω tapatalk.
 
ettore88

ettore88

Regular Member
Messages
51
My Satellite Setup
Gibertini 105cm 45E-42E-39E-36E,Gibertini 105cm 33E/31,5E-28,2E-26E/25.5E-23.5E,Gibertini 105cm 19,2E-16E-13E-10E/9E-7E-5E,Gibertini 105cm 15W-12,5W/11W-8W/7W-5W/4W-1W.Decoders:CT HD 5100C/CT2100+

Notebook HP Windows 7 Ultimate
My Location
Italy
Hi guys.I have a problem with the ZeonBud channels.(My box is Octagon SF4008.)On 12188 and 12341...I tried to do the manual scan on both transponder.(T2-MI at 4.8E)Unfortunately I haven't found anything!The signal is very good.(12 db) I tried a backup...on my Octagon and i can see the ZeonBud channels!I'm Not The Only One with this problem! How can this happen?THX in advance.
 
MCelliotG

MCelliotG

Specialist Contributor
Messages
682
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
You don't have to scan the channels for Zeonbud, we already have the service references posted!
And in case you miss them:
12188 MIS 10
1:0:1:1:48:10:30B022:0:0:0:

12188 MIS 20
1:0:1:1:48:20:30B022:0:0:0:

12341 MIS 30
1:0:1:1:48:30:30B022:0:0:0:
 
Captain Jack

Captain Jack

Модератор
Staff member
Messages
10,601
My Satellite Setup
See signature
My Location
North Somerset
Don't you need an external tuner for that as it's multistream?
 
Top