Posts by diyjeb

    Hey supwiddiss, thanks for your input here.


    I've had my eye on the OsMio 4K for a while now but was hoping to get the H7 working. As you know it has the dual S2 tuners and an ATSC tuner. The OsMio has one S2 tuner and a T2 tuner which doesn't work here. I guess I could get a USB ATSC tuner for terrestrial reception. I've heard a lot of good things about the OsMio scanning and the TNAP image.


    I'll try a bit more with the H7.AC and see if DiSEqC settings make a difference before buying an OsMio. Where would you recommend buying a OsMio4K?

    Yes, all my hardware is working perfectly with the TBS tuner, SmartDVB on a Windows10 computer. Today I scanned the entire arc from 129.0W to 87.1W with the universal LNB.


    Before, I was using an Invacom QPH-031 https://www.amazon.ca/Invacom-…lar-Outputs/dp/B000RLAK7A and had no problem with tuner settings Advanced, "Selecting satellites 1 (USALS)" and "User defined" L.O. settings of LOF/L=10750, LOF/H=10750, Threshold=11700. It would manual scan and move the dish.


    I may just try the DiSEqC settings and see if that works. Quite surprising. I thought this universal LNB would be drop in with a change of user defined LOF settings.

    Sorry, Pure2 does support satellites on this side of the pond for known active transponders. I overwrite with an xml file that has only satellites for this area and which includes channels that are deemed not active with the hope that I'll be able to scan in more channels. Blind scan doesn't work 100% for me with LOF frequency of 10750 which is why I replaced the LNB with a universal LNB. I thought all I'd have to do is change the user defined LOF frequencies and all would be golden.


    So I just updated my satellites.xml with the xml update plugin and I'm still not able to scan or move the USALS dish. The lamedb file has the satellites for this area.

    Hello, first and foremost, thank your taking an interest to help me with this. I'm in Canada on the west coast. The LNB is an Avenger Ku band single LNBF, part number PLL321S-2. Here is the link to the specification page http://www.dmsiusa.com/docs/pll321s-2-specs1.pdf


    I'm wondering if the satellites.xml or the lamedb files are causing the problem. A new installation of Pure2 does not support satellites on this side of the pond. I need to go to http://satellites-xml.org/ to get a file that supports this area and overwrite the satellites.xml located in etc/tuxbox. My understanding is that the lamedb file will be updated with each scan.


    My dish is not moving with the simple configuration and manual or blind scan.

    Yes, I tried simple configuration modes with single, positioner (selecting satellites) and positioner mode. I tried advanced configuration mode with Selecting satellites 1 (USALS), All satellites (USALS), selected individual satellite, assigned LNB1 and tried with LOF set to Universal LNB and User defined.


    I tried pretty much everything I could see would be worth while trying. I have not tried any DiSEqC settings since I don't use a switch.


    I'm currently scanning the entire arc successfully using SmartDVB on a Windows10 computer so the hardware is fine.

    Hello, I had a standard linear 10750Mhz L.O. LNB working on my Zgemma H7 using "Selecting satellites 1 (USALS)" and "User defined" L.O. settings but couldn't blind scan properly. I replaced the LNB with a universal LNB and changed the user defined L.O. settings to 9750Mhz and 10600Mhz but it will not scan manually or blind scan. The new universal LNB works just as it should when I have it connected to my TBS-5922 USB tuner using SmartDVB software on a Windows 10 computer. It doesn't work for some reason with my Enigma2 receiver. I have tried numerous variations of tuner config settings with no luck.


    Can someone post a tuner configuration that works with a universal LNB with no DiSEqC switch and Pure2 6.5? My setup is receiver to Stab HH motor to LNB.


    Thank you

    Yes, I did try without restoring settings. Basically started with a blank slate and didn't get too far before the reboot loop. Here is what I did.


    I originally saw the problem after installing a plugin so I reflashed and just restarted the GUI while at the home screen to replicate the reboot problem after a plugin is installed, no problems. I then scanned terrestrial channels and watched for a few minutes, everything fine at this point. I then restarted the GUI while tuned to a terrestrial channel and the reboot loop started. I also tested OpenATV on my ZGemma H7.AC and had the same results described in this post. Front display shows 2537 after reboot.


    So that test minimized the possible variables.


    The log file I provided was generated after I tuned to a terrestrial channel inducing the reboot loop.

    Thank you .atari. I'll give that a try on the weekend. Since the receiver doesn't reboot when tuned to satellite or IPTV, I was able to enter my email address in the log settings. I should be able to provide a copy of the log next time. Enigma2 has many features I still need to learn about.

    Well. I gave the Pure2 team feedback on a continuous reboot situation I have with the pure2 image. I waited patiently and things looked promising after downloading and installing "zgemmah7-PurE2-6.5-20200719_recovery_emmc.zip". I just did an update on my zgemma h7.ac and I'm back into the continuous 2 second reboot loop again. I have to go back to OpenPli again now. Hope this issue can be solved. Can't provide a log file because 2 seconds of reboot tine does not allow me to do that.

    Hello, here's a problem I noticed while installing plugins. "openatv-6.4-zgemmah7-20200712_recovery_emmc.zip" began to reboot in a repeating loop. A couple seconds after it boots up on my Zgeamma H7.AC, it reboots again, and again...


    I re-flashed with the idea of making one change at a time to see if anything I did caused the rebooting. This time I flashed and just restarted the GUI while at the home screen to replicate the restart after a plugin is installed, no problems. I then scanned terrestrial channels and watched for a few minutes, everything fine at this point. I then restarted the GUI while tuned to a terrestrial channel and the reboot loop started. I also tested Pure2 on my ZGemma H7.AC and had the same results described in this post. This reboot loop does not happen with Open PLI.


    Front display shows 2537 after reboot, possibly an error code.

    OK, here's some good feedback for you. I noticed this problem happens while I was installing plugins. I flashed again with the idea of making one change at a time to see if anything I did caused the rebooting. This time I flashed and just restarted the GUI while at the home screen to replicate the restart after a plugin is installed, no problems. I then scanned terrestrial channels and watched for a few minutes, everything fine at this point. I then restarted the GUI while tuned to a terrestrial channel and the reboot loop started. I also tested OpenATV on my ZGemma H7.AC and had the same results described in this post.


    Front display shows 2537 after reboot, possibly an error code since it is 12:15pm here.

    I had an update message saying to update using flash method. I downloaded "zgemmah7-PurE2-6.5-20200711_usb.zip" and the USB front panel button/power switch method would not give me "BOOT > USB > FLASH". I tried "zgemmah7-PurE2-6.5-20200711_recovery_emmc.zip" and it did flash but my ZGemma H7.AC receiver was in a reboot loop. Every two seconds after boot up, it would reboot. I flashed with OpenPLI and the reboot problem went away. I tried Pure2 again, same reboot problem so back to OpenPLI for now.

    Any chance someone could PM me too? I've tried but no luck. I only have ku reception at this time. If I could just see one channel work, I could then look at the files and understand what is required to maintain my own file and help others in the future.

    Thanks

    Hey supwiddiss, any chance I could get a copy of your .conf, .user, .server and softcam.key files? any other files that you think would be helpful as well. It's been a while since there has been discussion on this in this thread and I'll bet your files are a little more refined/updated now. At the moment I have a ku only setup. I can't determine if I have a working configuration because most activity is on c-band. If I could see something work, I'd be able to understand the relationship between the files and know what needs to be in them to make things work. If your files don't support ku band channels, at least I'll have the confidence that I have working files to learn from. Thanks

    I managed to get blindscan working on my Zgemma H7.AC with openpli-7.1-rc-h7-20190617_usb.zip and zgemmah7-PurE2-6.3-20190619_usb.zip.


    Event though my Invacom QPH-031 Quad Polar Circular Linear Ku Band LNB that requires a local oscillator Frequency: Lo = 10.75 GHz, High = 11.25 GHz, I decided to leave my tuner configuration LOF setting in OpenPLi and PurE2 set to universal. In the blindscan plugin, I left the scan start and stop frequencies as default (10700 and 12750).


    This resulted in successful ku blindscan on satellites 87.1W to 125.0W. It doesn't matter to me that the frequencies shown in the blind scan state window are wrong. I'm just happy all transponders are found and all channels are found.


    I have been using this QPH-031 because it has circular capability which is useful in North America but maybe its time to get a universal LNB.


    Thanks to everyone involved with developing these firmware options and plugins.

    I just noticed this forum and would like to post a problem I noticed with the Zgemma H7.AC ATSC tuner. Watching DVB-S channels, the picture is good. When I switch to an ATSC channel, the picture is glitchy. There are intermittent interruptions in the picture in the form of pixelation. I reboot the receiver and / or restart enigma and the pixelation minimizes and sometimes stops. I have good signal strength 20dB, AGC 99%, so that's not the issue. Not sure why it does that. Here is a link to a YouTube video that shows the problem.


    I use Pure2 v6.2 and the problem seems to be less with recent updates. The problem is the same with other images.