Willkommen Gast. Bitte einloggen oder registrieren.

Einloggen mit Benutzername, Passwort und Sitzungslänge

 
Erweiterte Suche

17294 Beiträge in 2072 Themen- von 2950 Mitglieder - Neuestes Mitglied: Hannes

September 20, 2017, 06:39:50 pm
Sundtek Support ForumEnglishSundtek MediaTV Pro (Europe)DriversSundtek DVB-T and Wetek
Seiten: [1] 2
Drucken
Autor Thema: Sundtek DVB-T and Wetek  (Gelesen 5656 mal)
HWTest
Newbie
*
Beiträge: 23


Profil anzeigen
« am: März 26, 2016, 01:51:01 pm »

I have a problem with my Sundtek DVB-T stick on my Wetek play running PBnigma.
I've installed the driver using sundtek_netinst, then unpacked the stb.tar a started using the sun_dvb start_t.
The blue light on the stick comes on and after a couple of seconds it goes off and the tuner is not visible under E2.
I've found nothing relevant in the logs.
Has anybody an idea what to check and how to make it work?
Gespeichert
Sundtek
Administrator
Hero Member
*****
Beiträge: 7456


Profil anzeigen
« Antworten #1 am: März 28, 2016, 03:10:18 pm »

Enigma2 needs to be modified not to look in /proc/bus/nim_sockets because all the native settopbox environment is just not available on Wetek.
Gespeichert

Sundtek Ltd. Support Engineer
HWTest
Newbie
*
Beiträge: 23


Profil anzeigen
« Antworten #2 am: März 28, 2016, 03:49:35 pm »

Meaning it'll not work on the Wetek in E2?
Gespeichert
Sundtek
Administrator
Hero Member
*****
Beiträge: 7456


Profil anzeigen
« Antworten #3 am: März 28, 2016, 04:12:55 pm »

This means that the nim socket python script needs to be modified in order to recognize the tuner.

It's missing /dev/misc/vtuner*, this is not the same as a regular e2 settopbox image.
Instead of looking in /proc/bus/nim_sockets it should just look in /dev/dvb/ for adapterN (where N would be the adapter ID).


https://github.com/libo/Enigma2/blob/master/lib/python/Components/NimManager.py#L684
« Letzte Änderung: März 28, 2016, 04:22:18 pm von Sundtek » Gespeichert

Sundtek Ltd. Support Engineer
HWTest
Newbie
*
Beiträge: 23


Profil anzeigen
« Antworten #4 am: März 28, 2016, 06:23:10 pm »

Ok, thanks.
So it is possible but I'm not sure how.
I didn't find the NimManager.py only NimManager.pyo
I'm afraid simply replacing the /proc/bus/nim_sockets with /dev/dvb/adapter1 is not the solution ... ?
Gespeichert
Sundtek
Administrator
Hero Member
*****
Beiträge: 7456


Profil anzeigen
« Antworten #5 am: März 29, 2016, 04:11:17 am »

Here we need to go back to the OpenATV (I think that is the image in question) to the git repository

https://github.com/openatv/enigma2/blob/master/lib/python/Components/NimManager.py

you can rename the file NimManager.pyo to NimManager.pyobackup and copy the .py file from the git repository into that directory.

pyo is just the generated python object code, it's source is always the .py file.

I think the easiest way might be to copy the content of /proc/bus/nim_sockets to /tmp/nim_sockets
and add a second definition for the other tuner.
This nim_socket stuff comes from the settopbox world it's not a linux standard by itself. It's just used by enigma2 though.

You can see the comment in the code:
Zitat
      # the content of /proc/bus/nim_sockets looks like:
      # NIM Socket 0:
      #          Type: DVB-S
      #          Name: BCM4501 DVB-S2 NIM (internal)
      # NIM Socket 1:
      #          Type: DVB-S
      #          Name: BCM4501 DVB-S2 NIM (internal)
      # NIM Socket 2:
      #          Type: DVB-T
      #          Name: Philips TU1216
      # NIM Socket 3:
      #          Type: DVB-S
      #          Name: Alps BSBE1 702A

you have created a ticket, for now I can only give you some hints which you can try once there's some more time I can give you some more help about it.
Gespeichert

Sundtek Ltd. Support Engineer
HWTest
Newbie
*
Beiträge: 23


Profil anzeigen
« Antworten #6 am: März 29, 2016, 02:57:04 pm »

Sorry, I'm a bit lost...

It's a PBnigma image.

I've added this to the nim_sockets :

Code:
NIM Socket 1:
Type: DVB-T
Name: Sundtek DVB-T (1/0) (USB)
Frontend_Device: 1

But I'm not able to overwrite the original file with the modified one.

When I delete the pyo and copy the py file, it creates a new pyo file.

I was advised on your IRC support chat to create a ticket, when I posted my problem there.
Gespeichert
Sundtek
Administrator
Hero Member
*****
Beiträge: 7456


Profil anzeigen
« Antworten #7 am: März 29, 2016, 03:32:27 pm »

You can copy nim_sockets to /tmp/nim_sockets
there you can edit it (that's what I mean).

if you modify the .py file enigma2 will recreate the .pyo file automatically everytime you restart enigma2 (you don't have to worry about that, the .py is relevant for editing).
Gespeichert

Sundtek Ltd. Support Engineer
HWTest
Newbie
*
Beiträge: 23


Profil anzeigen
« Antworten #8 am: März 29, 2016, 04:02:43 pm »

That's what I did (edit nim_sockets in /tmp) but I thought it doesn't help sitting in /tmp, so what have I to do with the edited nim_sockets file? Leaving it in /tmp makes no sense, it gets deleted after a reboot.

According the py and pyo files, that's what I thought.
Gespeichert
Sundtek
Administrator
Hero Member
*****
Beiträge: 7456


Profil anzeigen
« Antworten #9 am: März 29, 2016, 04:06:27 pm »

you can modify the path to nim_sockets in NimManager.py

I would recommend to keep it in /tmp and just create that file before starting enigma2.
But for testing you can also try to copy it to "/" and reference the path in NimManager.py to "/nim_sockets"
Gespeichert

Sundtek Ltd. Support Engineer
HWTest
Newbie
*
Beiträge: 23


Profil anzeigen
« Antworten #10 am: März 29, 2016, 04:31:36 pm »

OK, now I got it :-)

The tuner is now visible in E2 but it still doesn't work, when I record something with the first (internal tuner) I cant switch to another mux, its grayed out. When I disable the first tuner, so only the USB tuner stays active, I get no signal.
The blue LED on the stick behaves the same, it goes on during the boot but after a couple of seconds it goes off and stays off.
Gespeichert
Sundtek
Administrator
Hero Member
*****
Beiträge: 7456


Profil anzeigen
« Antworten #11 am: März 29, 2016, 04:45:35 pm »

I think the tuner needs to be registered as /dev/dvb/adapter0/frontend1 (and the other tuner as frontend0) but currently they are registered the normal linux way /dev/dvb/adapter1/frontend0
I don't have insight how this system works on the wetek, we can check that in a few days via the ticket which you have created.
By creating the nim_sockets file manually you're definitely one step forward now.
Gespeichert

Sundtek Ltd. Support Engineer
HWTest
Newbie
*
Beiträge: 23


Profil anzeigen
« Antworten #12 am: März 29, 2016, 04:58:03 pm »

OK
Gespeichert
rassi
Newbie
*
Beiträge: 32


Profil anzeigen
« Antworten #13 am: April 02, 2016, 02:41:45 pm »

The tuner is now visible in E2 but it still doesn't work

Did you get it to work?
only tried to install drivers with SSI and then with Sundtek Control Center.
Using now newest OpenATV 5.1
« Letzte Änderung: April 02, 2016, 02:43:23 pm von rassi » Gespeichert
Sundtek
Administrator
Hero Member
*****
Beiträge: 7456


Profil anzeigen
« Antworten #14 am: April 02, 2016, 03:12:44 pm »

The WETEK is not like all the other Enigma2 systems, it needs some modifications you can contact us next week via chat so we can help to go through it. http://chat.sundtek.de
Gespeichert

Sundtek Ltd. Support Engineer
Seiten: [1] 2
Drucken
Gehe zu: