Autor Thema: Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM  (Gelesen 35532 mal)

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8272
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #15 am: November 07, 2012, 10:08:18 Nachmittag »
There are 3 Options availabe:
1. Software PID Filter (default on PCs)
Zitat
/opt/bin/mediaclient -P off -d /dev/dvb/adapter1/frontend0
2. Hardware PID Filter (default on eg. dreambox and other boxes)
Zitat
/opt/bin/mediaclient -P on -d /dev/dvb/adapter1/frontend0
3. Passthrough, ignore all filters
Zitat
/opt/bin/mediaclient -P passthrough -d /dev/dvb/adapter1/frontend0

Aside of that you can always read what is passed to the settopbox by running
Zitat
/opt/bin/mediaclient --cat /dev/dvb/adapter1/dvr0 > /media/hdd/stream.ts
Failure is a good thing! I'll fix it

StAlex

  • Newbie
  • *
  • Beiträge: 22
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #16 am: November 08, 2012, 12:53:49 Nachmittag »
There are 3 Options availabe:
Zitat
/opt/bin/mediaclient -P off -d /dev/dvb/adapter1/frontend0
/opt/bin/mediaclient -P on -d /dev/dvb/adapter1/frontend0
Oops. How your device remember chosen options? config file/flash cell? Or It option automatic ajusted by the driver's intellect?
Before I am start using this stick with the VU+ STB, I performed a some tests on PC (with the set of different softwares). May be it is the point of problems? Some PC software enables HW/SW PID filtering and this config is deep stored into the device ?

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8272
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #17 am: November 08, 2012, 01:14:42 Nachmittag »
You can read through the driver configuration file

http://wiki.sundtek.de/index.php/TreiberKonfiguration

the commands are instant options, as soon as you run them they will be active immediately
Failure is a good thing! I'll fix it

StAlex

  • Newbie
  • *
  • Beiträge: 22
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #18 am: November 08, 2012, 01:35:48 Nachmittag »
http://wiki.sundtek.de/
BIG Thanks for the manpage! I am completely missed this page (installation/configuration steps I've got from forum messages only).

I'll checkup the my configs by this evening.

StAlex

  • Newbie
  • *
  • Beiträge: 22
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #19 am: November 08, 2012, 07:36:09 Nachmittag »
I'll checkup the my configs by this evening.
Something strange in that kingdom.
first: by default I am do not found the /etc/sundtek.conf file.
When I create it (even if it contains only commented lines), the tuner fails to start.
The example file I've take from wiki page.
second: if I pass the command
 /opt/bin/mediaclient --tsscan /dev/dvb/adapter1/dvr0
it does nothing. Just freezes. It unfreezes by Ctrl+C

If I pass one of that command:
/opt/bin/mediaclient -P off -d /dev/dvb/adapter1/frontend0
or
/opt/bin/mediaclient -P passthrough -d /dev/dvb/adapter1/frontend0
no changes at all:
--tsscan - still freezes;
- no success on encrypted channels;
- no success on firmware update

It is I am doing something wrong ?

PS.
I am check the -e output. It contains next:
root@vuuno:~# /opt/bin/mediaclient -e
**** List of Media Hardware Devices ****
device 0: [Sundtek MediaTV Digital Home (USB 2.0)]  DVB-C, DVB-T, REMOTE-CONTROL
  [SERIAL]:
     ID: U120622043728
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0
 
BUT!
I am do not see these devices in /dev/ folder:
root@vuuno:~# ls -l /dev/dvb
drwxr-xr-x    2 root     root           540 Jan  1  1970 adapter0
root@vuuno:~#
« Letzte Änderung: November 08, 2012, 08:01:44 Nachmittag von StAlex »

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8272
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #20 am: November 08, 2012, 09:40:58 Nachmittag »
The driver is started with the --no-nodes option that's why it doesn't work.


however you can try to use following mediaclient version until the next driver version will be avialable:

http://sundtek.de/support/mediaclient

This version will support the --no-nodes option of the driver (that means that the node itself is not existent in /dev/dvb)

Edit:
official driver is udpated for that to support drivers which are started with --no-nodes
« Letzte Änderung: November 09, 2012, 12:50:24 Vormittag von Sundtek »
Failure is a good thing! I'll fix it

StAlex

  • Newbie
  • *
  • Beiträge: 22
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #21 am: November 09, 2012, 07:48:30 Vormittag »
official driver is udpated for that to support drivers which are started with --no-nodes
Okay, I catch the new driver, and --tsscan is work for now. Thank you very much.
But, I want return to the on-topic problem.
I try to run once this command at this morning, and see the output starts with a lot of fake (zeroes) CAID's. Two or three dozen. I cant attach a log at this moment, but I can do this at this evening.
May be this is the point of unrecognized encryption by the driver of Marusys.
But anyway, at this evening I'll do some more tests with the mediaclient.

The last question: --no-nodes - it can be overridden to force nodes creation ? It can be useful to TS exploration with the dvbsnoop utility.
Or there are exists an another way to work with dvbsnoop (to perform comparing between different TS's from different tuners)?

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8272
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #22 am: November 09, 2012, 09:56:50 Vormittag »
Well you can check back with Marusys.

You can check it on a regular PC or start the driver manually on the settopbox.
The devicenodes are not created due bugs in some Enigma2 versions.

Shut down enigma2, and run /opt/bin/mediaclient --shutdown; /opt/bin/mediaclient --start


Before running dvbsnoop etc. run export LD_PRELOAD=/opt/lib/libmediaclient.so
Failure is a good thing! I'll fix it

StAlex

  • Newbie
  • *
  • Beiträge: 22
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #23 am: November 09, 2012, 09:11:12 Nachmittag »
Before running dvbsnoop etc. run export LD_PRELOAD=/opt/lib/libmediaclient.so
I am not reach the success with the dvbsnoop. Even I run command described in quotation.
It is required the devicenode, or I don't know how I can run dvbsnoop on the DVB-C tuner. Starting dvbsnoop without specifying the device - fails. With the targeting on "virtual" node - fails too

Output for mediaclient --tsscan - is (with "cuts"): it starts with a lot of (~80 times) messages like
CAT:
CA system: 0b00
CAT:
CA system: 0b00
CAT:
CA system: 0b00
CAT:
CA system: 0b00
then, follows the normal recognition
PMT PID: 0x0064
  Encrypted: Yes
  Service running: Yes
  Provider Name: OnLime
  Service Name: 
    --> 0x0065 (ITU-T Rec. H.262 | ISO/IEC 13818-2 Video or ISO/IEC 11172-2 constrained parameter video stream)
    --> 0x006e (ISO/IEC 13818-3 Audio)
    --> 0x0096 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
PMT PID: 0x00c8
  Encrypted: Yes
  Service running: Yes
  Provider Name: OnLime
  Service Name: c 1
    --> 0x00c9 (ITU-T Rec. H.262 | ISO/IEC 13818-2 Video or ISO/IEC 11172-2 constrained parameter video stream)
    --> 0x00d2 (ISO/IEC 13818-3 Audio)
    --> 0x00fa (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)


when I wrote the morning's message - I have been mistake by myself, because not paid enough of time.
What is the leading "stream" with the messages about "CAID" ? Is this normal for DVB ?
How can I understand a PID where the EMM/ECM transmission present ? It sould be a single PID for all channels. Do I am right?
And two comments on output of --tsscan command
#1 The first service - is not encrypted. It can be watched on totally FTA devices. And STB show this channel not marked as encrypted.
#2 The names of the services transmitted in cyrillic. Due to it correct displayed on STB, I think they are transmitted in UTF-8

The described quotation of --tsscan commnd taken  with the "-P off" option.

PS.
I would like you not tired?

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8272
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #24 am: November 09, 2012, 09:32:29 Nachmittag »
capture the TS stream to hard disk, dvbsnoop is not fast enough to do realtime analysis.

/opt/bin/mediaclient --cat /dev/dvb/adapter1/dvr0 > /media/hdd/test.ts


CAT/CA system is just printed whenever such packet comes in.

Service name is probably not printed because of the russian character set on the console (only ASCII is printed, it's just for informational purpose on the console)
Failure is a good thing! I'll fix it

StAlex

  • Newbie
  • *
  • Beiträge: 22
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #25 am: November 09, 2012, 10:42:33 Nachmittag »
interesting observation.

On the different channels, stick chooses different pid-space to HW filtering.
What is the algorhythm ?
For example, on the one cable-channel(I mean the frequency-holder; like "transponder" on DVB-S) PID-list is
root@vuuno:~# /opt/bin/mediaclient -w -d /dev/dvb/adapter1/dvr0
Using device: /dev/dvb/adapter1/dvr0
ID   | PID
----------
0000 | 0x0000 - 0
0001 | 0x0065 - 101
0002 | 0x006e - 110
0003 | 0x0096 - 150
0004 | 0x0064 - 100
0005 | 0x0012 - 18
root@vuuno:~#

on the second (where the all channels is encrypted) is the
root@vuuno:~# /opt/bin/mediaclient -w -d /dev/dvb/adapter1/dvr0
Using device: /dev/dvb/adapter1/dvr0
ID   | PID
----------
0000 | 0x01f4 - 500
0001 | 0x01f5 - 501
0002 | 0x01fe - 510
0003 | 0x0046 - 70
0004 | 0x0012 - 18
0005 | 0x0f02 - 3842
0006 | 0x0bbb - 3003
0007 | 0x1388 - 5000
0008 | 0x0039 - 57
root@vuuno:~#

And another observation.
When I try to remove some(even the one) PID from the list (via pass the "-x NNNN" command), STB starts to show a broken MPEG decoding, like a low-signal on DVB-S. As mentioned in wiki-documentation, it may be due low speed of USB connection?

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8272
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #26 am: November 09, 2012, 10:44:21 Nachmittag »
Enigma is setting up those IDs depending on the channel.
Failure is a good thing! I'll fix it

StAlex

  • Newbie
  • *
  • Beiträge: 22
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #27 am: November 09, 2012, 10:50:19 Nachmittag »
As I ask before - how can I understand on which PID present the CA messages ? This is to check the HW filtering list.

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8272
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #28 am: November 09, 2012, 10:52:23 Nachmittag »
you can capture the stream and look at it with dvbsnoop. All the logic is in Enigma here.
Failure is a good thing! I'll fix it

StAlex

  • Newbie
  • *
  • Beiträge: 22
    • Profil anzeigen
Re:Sundtek MediaTV Digital Home, VU+ UNO, SMiT Conax Chipset Pairing CAM
« Antwort #29 am: November 14, 2012, 07:38:47 Vormittag »
you can capture the stream and look at it with dvbsnoop. All the logic is in Enigma here.
Ok, I'm done with this. I am just take a couple of the days to learning myself about containment of the DVB-streams basics, and what I am found.
Your side take a set of pids from Enigma2 ? Or parse PAT && CAT && PMT itself ?
This is important, because resulting set of pids on encrypted channels is totally incomplete.
This is what using the your side on encrypted channel by default (just switch on to channel and dump the pid set):
Zitat
root@vuuno:~# /opt/bin/mediaclient -w -d /dev/dvb/adapter1/dvr0
Using device: /dev/dvb/adapter1/dvr0
ID   | PID
----------
0000 | 0x0000 - 0
0001 | 0x00C9 - 201
0002 | 0x00D2 - 210
0003 | 0x00FA - 250
0004 | 0x00C8 - 200
0005 | 0x0012 - 18
root@vuuno:~#

And this - is the dvbsnoop analysis(with cuts to reduce the message size), performed on TS, catched when HW pid filter is switched off (no matter where - on STB or on the PC with the ProgDVB). Missed pids marked as Bold.
CAT-table:
Zitat
------------------------------------------------------------
TS-Packet: 00000001   PID: 1 (0x0001), Length: 188 (0x00bc)
------------------------------------------------------------
{cut}
    TS sub-decoding (1 packet(s) stored for PID 0x0001):
    =====================================================
    TS contains Section...
    SI packet (length=18):
        PID:  1 (0x0001)  [= assigned for: ISO 13818-1 Conditional Access Table (CAT)]

        Guess table from table id...
        CAT-decoding....
        Table_ID: 1 (0x01)  [= Conditional Access Table (CAT)]
        section_syntax_indicator: 1 (0x01)
        (fixed): 0 (0x00)
        reserved_1: 3 (0x03)
        Section_length: 15 (0x000f)
        reserved_2: 262143 (0x3ffff)
        Version_number: 2 (0x02)
        current_next_indicator: 1 (0x01)  [= valid now]
        Section_number: 0 (0x00)
        Last_Section_number: 0 (0x00)

               MPEG-DescriptorTag: 9 (0x09)  [= CA_descriptor]
               descriptor_length: 4 (0x04)
               CA_system_ID: 2816 (0x0b00)  [= Norwegian Telekom]
               reserved: 7 (0x07)
               CA_PID: 90 (0x005a)
        CRC: 734917485 (0x2bcdf36d)

PMT-table:
Zitat
------------------------------------------------------------
TS-Packet: 00000001   PID: 200 (0x00c8), Length: 188 (0x00bc)
------------------------------------------------------------
{cut}
    TS sub-decoding (1 packet(s) stored for PID 0x00c8):
    =====================================================
    TS contains Section...
    SI packet (length=53):
        PID:  200 (0x00c8)

        Guess table from table id...
        PMT-decoding....
        Table_ID: 2 (0x02)  [= Program Map Table (PMT)]
        section_syntax_indicator: 1 (0x01)
        (fixed '0'): 0 (0x00)
        reserved_1: 3 (0x03)
        Section_length: 50 (0x0032)
        Program_number: 2 (0x0002)
        reserved_2: 3 (0x03)
        Version_number: 16 (0x10)
        current_next_indicator: 1 (0x01)  [= valid now]
        Section_number: 0 (0x00)
        Last_Section_number: 0 (0x00)
        reserved_3: 7 (0x07)
        PCR PID: 201 (0x00c9)
        reserved_4: 15 (0x0f)
        Program_info_length: 6 (0x0006)

               MPEG-DescriptorTag: 9 (0x09)  [= CA_descriptor]
               descriptor_length: 4 (0x04)
               CA_system_ID: 2816 (0x0b00)  [= Norwegian Telekom]
               reserved: 7 (0x07)
               CA_PID: 260 (0x0104)

        Stream_type loop:

            Stream_type: 2 (0x02)  [= ITU-T Rec. H.262 | ISO/IEC 13818-2 Video | ISO/IEC 11172-2 constr. parameter video stream]
{cut}
Summary, HW filter misses at least two Pids:
CA_PID: 90 (0x005a) - common TS for EMM/ECM transmission
CA_PID: 260 (0x0104) - per channel TS for EMM/ECM transmission

But.
I must to say, if I add this pids manually to pid set, nothing happens. Channels still encrypted.
This is may caused by one of two reasons. Or by both.
1) due to using pairing Conax cam - it needs some more information, than provided by standart pids (90 && 260). It may needs some additional pid. But I am not shure - it is a hypothesis.
2) due to incomplete handshake between smartcard and CAM, the CAM rejects all data incoming from this CA pids, and it affects to the pid set, which your side takes from enigma.

Described here - covers an encryption issue. Not an updating firmware. Firmware issue - is still not cleared for me - how it regulated by EBU standarts (where and how declared additional pids with the new firmware data).