Posts by gorski

    diyjeb


    "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."

    You keep pushing and pushing, regardless of what one tells you - I call that aggression and you? What do you call it?

    Try this and see...


    chewie


    "I got a tip on another forum on how to set up for blind scan, I have the Zgemma 9.2S and these settings also work on the Zgmma 7, here are the settings:


    For C band use user definied,

    Lo low 10000,

    Lo High 10000 and you need to

    scan from 10950 - 11750 mhz to cover all C Band.


    You can scan from 11000 - 11750 for best results.


    Cover all C band frequencies. 10950 is 4200 and 11750 is 3400.


    On the blind scan screen the start frequency is set to 11000 and the Stop frequency is set to 11700, I set the accuracy for 5.


    This receiver Blind Scans on C-BAND now, give it try on these settings.


    Regards.

    Chewie"

    tromo


    "Ah well, the meaning of 'blindscan' is a bit elusive/shady among manufacturers/users, especially in C band. A proper one (in a true sense of the def) should not care about predefined satellites.xml or other stuff, but do a 2 pass scan; 1st spectral analysis (get something strong and probably reasonable) and then do all the possible DVB parameters checks to see if it makes any sense. There are at least two more approaches to this problem, with less or more happy results (time vs quality)."


    "The problems are not BRCM related, but Front End/Tuner HW and SW , which are from another company. Sadly, at this moment, I'm not able to check C band stuff."

    Perhaps if you slow down a little and read with some understanding of the issues.... A few posts back I told you who writes drivers but oh no...


    Push, push, push regardless... Aggression doesn't solve any problems, only makes more of them...


    tromo has a post on the subject, he wrote in more technical detail...

    PurE2 has sorted out a number of issues, even in drivers, low level coding etc. However, dear eager beaver saragusa, how do you solve a problem if you do not have the equipment?!?


    Seriously, slow down, m8... Read carefully, methodically... Be a German in this regard... :rasta2bigsmoke0gf1:

    It's not a big problem for me... I don't go after those satellites and even if I did - one needs a big dish for it, too... How many people are affected?


    Of course, non-EU guys have a problem with that and they should GET TOGETHER AND WRITE TO THE MANUFACTURERS TO FIX IT IN DRIVERS AND SW!!!!


    I already did my part in this regard, even though it doesn't affect me - but this is obviously not enough, so you guys SHOULD DO WHATEVER YOU CAN DO!!!! After all, it's in YOUR interest.... And if you sheepishly sit on your hands and do nothing... oh, well...


    You can also write to the forum sponsor as well as all your suppliers and they should all also ask for it to be done, on your behalf, as you are their customers...


    Good luck!

    Just a small note: this skin has broken new Full HD ground in E2 hobby and it is giving users a lot of ways to configure it according to the users' needs!


    All you need to do is NOT BE RIGID/INFLEXIBLE/CLOSE MINDED/PREJUDICED/SPIRITUALLY LAZY - and you will be able to configure it for yourself...


    Don't be afraid, all the help you need is right here, just ask away if you are stuck or if you feel like you are out of your depth...


    Worry not, these things are NOT that complex - after all, even I have managed to get it going well for myself... :laugh1::mosking::rasta2bigsmoke0gf1::P:party-time:

    Cables up to 50m are OK, m8...


    I use various QUAD LNBs (3 types). never bothered with low power ones.


    Issue with low power was with PSU missing As (2 instead of 3A, AFAIR) and PurE2 fixed the settings issue long ago...


    I have a feeling more boxes are connected at the same time and wrong format list is being forced from one box to the other with wrong settings...


    AJ was seriously complicating things in a post above, mixing 2 different DiSEqC protocols needlessly, so from a distance I'd say it's a user, not a HW issue, quite frankly...

    Your post 11, for example - you will have to excuse my bluntness - speaks of your constant moving of the goalposts...


    One thing is clear: things are not done consistently there! One moment dishes galore, both tuners are used, the same setup for both tuners, then one tuner is not used...


    Post 7 motorised system is used, later on it is not used...


    You say 'no loop-through', then I am thinking that probably some of those other boxes you have may have a loop-through and you might be using it but not telling us you are, whatever the reason, and that MIGHT be affecting the setup, as in "clashing" would happen....


    Then, I am thinking that you should know not all lists have the same format, i.e. they are not to be pushed into all E2s regardless - but do you know this?


    I.e. DMM is not to be used in OE-A E2 etc., so don't push your DMM list into PurE2 because:

    1) DMM

    2) OE-A

    3) OpenPLi

    (is OpenViX different a bit, as well, so no. 4?)

    have a different format!


    So, you may be committing a grave error there, as well, rigidly trying to push something that works in one but can not work properly in another STB with a different E2...???


    One moment it is just one tuner, the next it is two used, one moment a box is working, the next it goes tits up, one moment it is just one STB on a cable, the next - we are not sure just how many boxes are connected to a single cable, in how many spaces, since you have quite a few STBs to play with... And we all know that loop-through can cause problems, especially when on different transponders... Problem solved, problem re-appeared... Problem here, problem solved, problem re-appears... How do you connect them, which lists go where, are you restoring settings or doing it all carefully from scratch, manually...???


    Where do you live? Is the electrical current steady? Do you have some kind of 'shock absorber' to shield the sensitive equipment from serious power fluctuations? Tuners and network cards usually go first when this is not OK...


    Are you reconfiguring your internal setup all the time (it seems to me you are)?

    I just see confusion there, sorry...

    If you get it on your box - it should be ON wherever you are casting... What's the problem?


    And what kind of "thinking" is this - no info re. your image, what you are doing, procedures you are using etc. etc.


    Shall we use our crystal ball to get all the relevant info?!?