Beiträge von 2pat

    When I try to unpack it on my dm8000 I only get some error messages, what is I doing wrong?


    root@dm8000:/tmp# unzip skin_essential72_\ e2\ CVS.zip
    Archive: skin_essential72_ e2 CVS.zip
    unzip: Unsupported compression method 0


    root@dm8000:/tmp# unzip skin_essential72_\ e2\ CVS.zip
    Archive: skin_essential72_ e2 CVS.zip
    unzip: Unsupported compression method 0


    root@dm8000:/tmp#

    I have a rev. J tuner module.
    I have one SUR420 DiseqC 1.1 switch connected to my DM800, and one 4x1 DiseqC 1.0 (2.0) switch on each of the 1.1 switch inputs.
    My settings:
    config.sec.delay_between_diseqc_repeats=150
    config.Nims.0.configMode=advanced
    config.Nims.0.advanced.sats=48
    config.Nims.0.advanced.sat.3592.lnb=8
    config.Nims.0.advanced.sat.192.lnb=2
    config.Nims.0.advanced.sat.130.lnb=4
    config.Nims.0.advanced.sat.3170.lnb=12
    config.Nims.0.advanced.sat.235.lnb=1
    config.Nims.0.advanced.sat.100.lnb=5
    config.Nims.0.advanced.sat.48.lnb=7
    config.Nims.0.advanced.sat.3550.lnb=9
    config.Nims.0.advanced.sat.282.lnb=13
    config.Nims.0.advanced.sat.3520.lnb=10
    config.Nims.0.advanced.sat.70.lnb=6
    config.Nims.0.advanced.sat.90.lnb=5
    config.Nims.0.advanced.sat.160.lnb=3
    config.Nims.0.advanced.lnb.1.diseqcMode=1_1
    config.Nims.0.advanced.lnb.1.uncommittedDiseqcCommand=1
    config.Nims.0.advanced.lnb.1.commandOrder=uct
    config.Nims.0.advanced.lnb.1.commitedDiseqcCommand=AA
    config.Nims.0.advanced.lnb.3.diseqcMode=1_1
    config.Nims.0.advanced.lnb.3.uncommittedDiseqcCommand=1
    config.Nims.0.advanced.lnb.3.commitedDiseqcCommand=BA
    config.Nims.0.advanced.lnb.3.commandOrder=uct
    config.Nims.0.advanced.lnb.2.diseqcMode=1_1
    config.Nims.0.advanced.lnb.2.uncommittedDiseqcCommand=1
    config.Nims.0.advanced.lnb.2.commitedDiseqcCommand=AB
    config.Nims.0.advanced.lnb.2.commandOrder=uct
    config.Nims.0.advanced.lnb.5.diseqcMode=1_1
    config.Nims.0.advanced.lnb.5.uncommittedDiseqcCommand=2
    config.Nims.0.advanced.lnb.5.commitedDiseqcCommand=AA
    config.Nims.0.advanced.lnb.5.commandOrder=uct
    config.Nims.0.advanced.lnb.4.diseqcMode=1_1
    config.Nims.0.advanced.lnb.4.uncommittedDiseqcCommand=1
    config.Nims.0.advanced.lnb.4.commitedDiseqcCommand=BB
    config.Nims.0.advanced.lnb.4.commandOrder=uct
    config.Nims.0.advanced.lnb.7.diseqcMode=1_1
    config.Nims.0.advanced.lnb.7.uncommittedDiseqcCommand=2
    config.Nims.0.advanced.lnb.7.commitedDiseqcCommand=BA
    config.Nims.0.advanced.lnb.7.commandOrder=uct
    config.Nims.0.advanced.lnb.6.diseqcMode=1_1
    config.Nims.0.advanced.lnb.6.uncommittedDiseqcCommand=2
    config.Nims.0.advanced.lnb.6.commitedDiseqcCommand=AB
    config.Nims.0.advanced.lnb.6.commandOrder=uct
    config.Nims.0.advanced.lnb.9.diseqcMode=1_1
    config.Nims.0.advanced.lnb.9.uncommittedDiseqcCommand=3
    config.Nims.0.advanced.lnb.9.commitedDiseqcCommand=AA
    config.Nims.0.advanced.lnb.9.commandOrder=uct
    config.Nims.0.advanced.lnb.8.diseqcMode=1_1
    config.Nims.0.advanced.lnb.8.uncommittedDiseqcCommand=2
    config.Nims.0.advanced.lnb.8.commitedDiseqcCommand=BB
    config.Nims.0.advanced.lnb.8.commandOrder=uct
    config.Nims.0.advanced.lnb.10.diseqcMode=1_1
    config.Nims.0.advanced.lnb.10.uncommittedDiseqcCommand=3
    config.Nims.0.advanced.lnb.10.commitedDiseqcCommand=AB
    config.Nims.0.advanced.lnb.10.commandOrder=uct
    config.Nims.0.advanced.lnb.13.diseqcMode=1_1
    config.Nims.0.advanced.lnb.13.uncommittedDiseqcCommand=4
    config.Nims.0.advanced.lnb.13.commitedDiseqcCommand=AA
    config.Nims.0.advanced.lnb.13.commandOrder=uct
    config.Nims.0.advanced.lnb.12.diseqcMode=1_1
    config.Nims.0.advanced.lnb.12.uncommittedDiseqcCommand=3
    config.Nims.0.advanced.lnb.12.commitedDiseqcCommand=BB
    config.Nims.0.advanced.lnb.12.commandOrder=uct

    I think we can rule out bugs in the Enigma2, but instead focus on the DVB-S2 tuner. As I have been testing my DM800 during the weekend, using a tuner module from a DM600. And with that tuner module the DM800 searches and tunes without any trouble at all!!! (no S2 channels of course)


    So I hope DM and it's developers can take an extra look at why the DVB-S2 tuner module is having this big problem with DiseqC 1.1 swithing. (my theory is that it sometimes fails to deliver voltage out and then the switch resets...)

    Could someone clearify how the "blind scan" function is supposed to work? As far as I am able to observe it only scans the already known transponders??? Not very "blind" that if you ask me!

    Yes, is using "uncommited, commited, toneburst". And have tried different "repeats" without any big difference. Have a bad feeling that there is something in the tuner module that is unstable. As I can zap between different satellites for hours one day without trouble, and the other day it looses the signal after just a few zaps. Its when zapping to an HD channel using 8PSK it mostly looses the signal and the box has to be rebooted. Checking the "dmesg" when this happens, it is filled with "pilot on pilot off" messages.


    Because very often when scanning a satellite I suddenly get channels from my first satellite (Uncommited input 1 / Commited AA). And a bit to often "tuning errors" when zapping and the only way to get picture back is to reboot the DM800. So I have a feeling my uncommited switch (Spaun SUR420) sometimes looses it position, and thats why I feel it would be practical to resend the uncommited commands. It would anyway be nice to have tried if resending the uncommited commands makes any difference on this "bug".


    My Enigma1 boxes (DM600 and DM7000) does work smootly without any such hickups when connected to the same switch system!

    Firmware: latest cvs.


    Hi, been scrating my head over this problem with "tuning error" since I started using the DM800. And after looking into what the "dmesg" tells me, I'm hoping someone of you DiseqC gurus could take an extra look at this. It seems that the Uncommitted commands

    Code
    DISEQC: e0 DISEQC: 10 DISEQC: 39

    is only sent once each time we select a new satellite position, and then not again as long as we zap on the same satellite. Why not send it each time we zap? (if fast DiseqC is off at least)




    Hans Jørgen

    Zitat

    Originally posted by mrabcx
    I think it is quite horrible that there are so many people here who are having similar types of problems and DM are doing nothing to solve them!! When you email they simply respond that new software is coming out soon.


    As for yesterday, I can now no longer view some other HD channels which used to come up just fine. I don't know what suddendly happened but now I get 'Tuning failed' or 'No PAT' type of errors on
    Thor: 11341.00V, dvb-s2.


    Why would this happen all of a sudden ?! Manual searching does not help (no services are found whatsoever) on this transponder!!!


    Well that has nothing to do with the Dreambox at all, you can't blame Telenor's change on Dream(?):


    http://www.telenorsbc.com/uplo…ry%20HD%20move_240608.pdf


    http://www.telenorsbc.com/templates/Page.aspx?id=401

    The Diseqc and DM800 seems to be very troblesome when cascading switches, I have a SPAUN SUR 420 F first as the uncommited and then some Chess 4x1 behind it. Very often when scanning a satellite, it starts OK but suddenly it loses the signal, and then it seems to have fallen back to the "input 1" satellite (input 1 on both the uncommited and commited). So in my mind this seems to be the DM800 not sending all the commands for each transponder when scanning.


    (http://www.spaun.de/files/b01c2_de_ske11s135.pdf)

    root@dm800:~> cat /etc/fstab
    rootfs / auto defaults 1 1
    proc /proc proc defaults 0 0
    devpts /dev/pts devpts mode=0620,gid=5 0 0
    usbdevfs /proc/bus/usb usbfs defaults 0 0
    /dev/mtdblock/2 /boot jffs2 ro 0 0
    tmpfs /var tmpfs defaults 0 0
    tmpfs /tmp tmpfs defaults 0 0
    #/dev/ide/host0/bus0/target0/lun0/part1 /media/hdd auto defaults 0 0
    10.0.251.11:/var/pub /media/hdd nfs rw,rsize=8192,wsize=8192,soft,tcp,nolock 2 0
    root@dm800:~>