Oscam-emu zgemma h9s setup

There are 8 replies in this Thread which was already clicked 2,984 times. The last Post () by s3n0.

    HI,


    I live in Portugal so can not receive the standard UK freeview channels through satellite.

    I have discovered that I can receive a backup of some of these channels through a satellite dish pointing to 27.5w so I now have a dish that points to this satellite.

    I have done lots of reading and testingbut I still can not watch ny of the channels as all I see is a black screen.


    I have enclosed all of the file in the scam-emu folder below and would appreciate if if anyone could help me fix the problem (or problems).


    This is the scam-emu log:-


    • 2020/01/09 22:53:47 00000000 s (main) System name = Linux
    • 2020/01/09 22:53:47 00000000 s (main) Host name = zgemmah9s
    • 2020/01/09 22:53:47 00000000 s (main) Release = 4.4.35
    • 2020/01/09 22:53:47 00000000 s (main) Version = #1 SMP Tue Aug 27 02:08:49 UTC 2019
    • 2020/01/09 22:53:47 00000000 s (main) Machine = armv7l
    • 2020/01/09 22:53:47 00000000 s (main) Stb model = h9
    • 2020/01/09 22:53:47 00000000 s (main) Stb boxtype = h9
    • 2020/01/09 22:53:47 00000000 s (main) creating pidfile /var/tmp/oscam-emu.pid with pid 1677
    • 2020/01/09 22:53:47 00000000 s (emu) OSCam-Emu version 798
    • 2020/01/09 22:53:47 00000000 s (config) userdb reloaded: 1 accounts loaded, 0 expired, 0 disabled
    • 2020/01/09 22:53:47 00000000 s (main) signal handling initialized
    • 2020/01/09 22:53:47 00000000 s (led) LED support is not active. Can't detect machine type.
    • 2020/01/09 22:53:47 00000000 s (net) cccam: initialized (fd=4, port=12000)
    • 2020/01/09 22:53:47 00000000 s (reader) emulator [emu] creating thread for device emulator
    • 2020/01/09 22:53:47 00000000 s (main) waiting for local card init
    • 2020/01/09 22:53:47 4F176669 h (webif) webif: decompressed 172581 bytes back into 416640 bytes
    • 2020/01/09 22:53:47 4F176669 h (webif) HTTP Server running. ip=:: port=83
    • 2020/01/09 22:53:47 2FBCC85D r (reader) emulator [emu] Reader initialized (device=emulator, detect=cd, mhz=357, cardmhz=357)
    • 2020/01/09 22:53:48 2FBCC85D r (reader) emulator [emu] card detected
    • 2020/01/09 22:53:49 2FBCC85D r (reader) emulator [emu] found card system emu
    • 2020/01/09 22:53:49 2FBCC85D r (reader) emulator [emu] THIS WAS A SUCCESSFUL START ATTEMPT No 1 out of max allotted of 1
    • 2020/01/09 22:53:49 2FBCC85D r (emu) Reading key file: /etc/tuxbox/config/oscam-emu/SoftCam.Key
    • 2020/01/09 22:53:49 2FBCC85D r (emu) Total keys in memory: W:0 V:0 N:0 I:0 F:28 G:0 P:0 T:0 A:0
    • 2020/01/09 22:53:50 00000000 s (main) init for all local cards done
    • 2020/01/09 22:53:50 39B70393 c (client) plain dvbapi-client granted (dvbapi, au=auto (24 reader))
    • 2020/01/09 22:53:50 39B70393 c (dvbapi) dvbapi channelcache loaded from /etc/tuxbox/config/oscam-emu/oscam.ccache
    • 2020/01/09 22:53:50 39B70393 c (dvbapi) Detected /dev/dvb/adapter0/demux0 Api: 0, userconfig boxtype: 0 maximum number of filters is 64 (oscam limit is 64)
    • 2020/01/09 22:53:50 39B70393 c (dvbapi) ERROR: ioctl(CA_GET_DESCR_INFO): Invalid argument

    One final question I have is that I read that I had to copy a lamedb file with the correct entries to /etc/enigma2/lamedb after of course stopping enigma2 with the init 4 command.

    I copied the file into /etc/enigma2/lamedb then checked the contents, which were what I had copied but once I start enigma2 again with the init 3 command the contents of the lamedb file are as follows


    zgemmah9s login: root

    root@zgemmah9s:~# ce /etc/

    -bash: ce: command not found

    root@zgemmah9s:~# cd /etc/enigma2

    root@zgemmah9s:/etc/enigma2# more lamedb

    eDVB services /4/

    transponders

    0cfdace7:1000:0001

    s 11495000:44100000:1:9:-275:2:0:1:1:0:2

    /

    end

    services

    end

    Have a lot of bugs!


    Thanks.

  • master G

    Added the Label Arm 4K UHD Oscam-emu Support

    Hi.

    Which Enigma do you use exactly (name and version) ?

    Try verifying the following config entries (open and read the spoiler - source from here: https://github.com/oscam-emu/o…api-on-compatible-devices ):


    Try also delete or change the following line (in "oscam.conf" file):

    boxtype = zgemma h9s to boxtype = zgemma_h9s

    Delete the line... or try change it to the following:

    boxtype = dreambox

    More info about boxtype: http://www.streamboard.tv/wiki…Config/oscam.conf#boxtype

    Hi,


    thank you or your reply.


    The box is an enigma2 box but I don't know how to check the the version of enigma2.

    The software installed is Openatv 6.3 and Wooshbuild infinity.


    When I installed Oscem-emu it automatically created the oscam.conf and set boxtype to zgemma h9s.

    I tried setting boxtype to zgemma_h9s and dreambox and deleting the line.

    After restarting scam-emu each time I still could not see any channels and the log was just the same as before.

    Always the same mistake after changing boxtype? Or some new mistake?


    I don't know OscamEmu very well with a reader emulator. Try to study this:

    https://github.com/oscam-emu/o…i/OSCam-Emu-configuration


    It looks like OscamEmu is also trying to write / send packets to the hardware CI+ built-in interface on your device, but there is no CAM module plugged in, and therefore reports a communication error "(dvbapi) ERROR: ioctl (CA_GET_DESCR_INFO): Invalid argument". Maybe the "dvbapi" user should be disabled (oscam.conf, enabled = 0).


    I know almost nothing of OscamEmu configurations with emulator, for so many coding systems, sorry. It is also important to have a working SoftCam.key file, although the error in the LOG is probably related to an incorrect dvbapi setting. Because not all devices data is supported by dvbapi for OscamEmu (for PowerVU crypto): https://github.com/oscam-emu/o…api-on-compatible-devices


    For OpenATV, what is a Enigma2 based on the OE 2.0 Enigma core, you need use the value (file oscam.conf):

    extended_cw_api = 2

    ...and not this one:

    extended_cw_api = 1

    Select the correct extended CW API:

    Webif -> Config -> DVB-Api -> API for extended CWs :

    1 = OE 2.2

    2 = OE 2.0 (OpenATV, OpenPLi, etc.)

    Please refer to the link above for the encoding you use in your emulator.

    Hi,


    I have solved the problem, it had nothing to do with scam-emu, the problem was that Filezilla was corrupting the lamedb file when I transferred it from my PC to the zgemma.


    It is working now.


    Regards.

    In my whole life, I've written hundreds of thousands of files over a FTP connection of various types (passive, active, FTPS, ...), but it never happened that a CRC error occurred during data transfer. We live in the 21st century, when these problems have been solved long ago. It may have been 20 years ago that there were transmission errors on the old IPX, but it is not happening today. There are no longer problems with the CRC checksum. Data is transmitted with 100% reliability.


    The problem can only occur when using data compression, using the FTP protocol (a different data compression algorithm on both sides).


    I think there will be a problem with your internal flash memory on the device. The ext-format flash drive may be damaged. Uhm ...

    I have also ftp'd hundreds os thousand of files, I worked in IT for 36 years and have never seen such a problem before.

    Let me tell you the sequence of events and you can judge for yourself.

    Every time I used filezilla to copy lamedb (after issuing init 4) the file seemed to be copied correctly as I used the more command to inspect the contents but after issuing the init 3 command the file was corrupted.

    Last night I connected the dish pointing to 28.2e to try to watch some of the free channels as my internet was playing up and I could not watch IPTV.


    Once I had scanned the Astra channels in I checked the contents of lamedb and it was fine. I restarted the box and the file was still OK.

    Then I issued init 4 and copied the file to my MacBook Pro, the file seemed fine.

    I then copied it back using filezilla and using the more command it seemed fine but after I issued the init 3 command the file was corrupt.


    So this morning I copied the 27.5w lamedb from this forum using the macOS Finder app after issuing the init 4 command of course.

    When I issued the init 3 command I used the more command to check the file and it was perfect.

    Since then I able to watch the channels on 27.5w.


    Regards.

    I think the lamedb database file is linked to another files with a list of user favorite channels (userbouquets files) and a file with available transponders (satellites.xml, cable.xml, terrestrial.xml - depending on the type of DVB service / tuner being used). A new lamedb is created at each restart. Thus, if you upload your lamedb, it would also be useful to upload the appropriate channel lists (userbouquet files) and the corresponding transponder lists (satellites.xml) for Enigma, according to which lamedb "syncs". You can try deleting this lamedb file and then a new file will be created automatically after restart.


    However, the error does not occur as you wrote "when copying a file using the FTP protocol", but occurs when the Enigma is restarted and is not an error, but only an automatic update of the lamedb file. You can try to stop the Enigma, then completely delete the lamedb file and restart the set top box. Sometimes it helps.

OSCam-EMU Support Forum

Configs, discussion, downloads and guides for OSCam-EMU Softcam.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login