General OpenPLi Questions

[Alan Rovner]

Hi all, I have a VU+ Zero 4K and so far have been very satisfied with it. A few questions......

Why do I have to run circular polarity on Ku band? I have the standard Geosat 90 LNBF.

Does blind scan work on Ku band? It produces odd results such as not seeing channels I have manually entered, and listing channels not present, possibly from somewhere else in my bouquet list.

Are there release notes for firmware updates?

Tnx
Al, K7AR

Sent from my moto x4 using the SatelliteGuys app!

 

[comfortably_numb]

Hi all, I have a VU+ Zero 4K and so far have been very satisfied with it. A few questions......

Why do I have to run circular polarity on Ku band? I have the standard Geosat 90 LNBF.

Does blind scan work on Ku band? It produces odd results such as not seeing channels I have manually entered, and listing channels not present, possibly from somewhere else in my bouquet list.

Are there release notes for firmware updates?

Tnx
Al, K7AR

Sent from my moto x4 using the SatelliteGuys app!

You have to switch to "vertical and horizontal" on the blind scan menu

The blind scan plug-in is not foolproof and I would consider it "in beta" as I have experienced similar results.

 

[raydio]

Hi Alan the blind scan plugin has gone through an overhaul lately and some images do use it and some don't use it yet. For instance, I am using OpenPli RC7.0 and it has the new blind scan plugin and the lnb selection is "user" and then you enter in your LO frequency. The new plugin is better as far as accuracy is concerned, but as CN noted it is a work in progress...no blind scan is perfect or fool proof.

I only have Ku so that's all know as far as blind scan performance. I really don't have an issue with it as I know if there is a transponder that it won't scan I can always do it manually. There is always one on 103W that on blind scan it finds the transponder and then I tell it do scan and find the channels and it always misses them. I always have to manually scan that transponder.

As far as I know, there is not release notes on changes in images. However for OpenPli images, if you go to their forum, they usually have a thread regarding the changes they are making to a specific release.

 

[Chewie]

Hello raydio
What are you settings when you select User for:
LOF/L
LOF/H
Threshold

 

[comfortably_numb]

Hello raydio
What are you settings when you select User for:
LOF/L
LOF/H
Threshold

10750 for LOF/L and LOF/H

Can't remember threshold at the moment (not in front of my TV)

 

[raydio]

10750 for LOF/L and LOF/H

Can't remember threshold at the moment (not in front of my TV)

I don't do anything with threshold, just leave it as is -

 

[Titanium]

Circular LNB selection had been previously used to provide single scan of both polarities by default. The KU LNB selection seemed to expect that the system used a universal dual LO LNB even if a single LO was selected. The OpenVIX team has been releasing the recent changes to scanning and LNB selection and slowing being incorporated into other images as raydio posted. Glad to see that this problem is being addressed. It was very confusing for first-time E2 users. LOF/L is the 22KHz OFF LO selection and LOF/H is 22KHz ON LO selection typically used for a dual LO Universal type LNB.

Threshold is the frequency switchpoint for the 22KHz control signal activation. For example: If the threshold is 11700, transponder frequencies below 11700 use LOF/L (with 22KHz tone signal OFF. TP frequencies at and above 11700 activate a 22KHz signal and LOF/H is active.

Depending how it is coded, leaving the Threshold setting blank with identical both high and low LO settings, this may cause transponders to be scanned twice, analyzed twice or even logged twice. This often doubles the scan time.

Try setting the Threshold at 11700 and report if this affects the blind scan either in a positive or negative way.

 

[comfortably_numb]

Circular LNB selection had been previously used to provide single scan of both polarities by default. The KU LNB selection seemed to expect that the system used a universal dual LO LNB even if a single LO was selected. The OpenVIX team has been releasing the recent changes to scanning and LNB selection and slowing being incorporated into other images as raydio posted. Glad to see that this problem is being addressed. It was very confusing for first-time E2 users. LOF/L is the 22KHz OFF LO selection and LOF/H is 22KHz ON LO selection typically used for a dual LO Universal type LNB.

Threshold is the frequency switchpoint for the 22KHz control signal activation. For example: If the threshold is 11700, transponder frequencies below 11700 use LOF/L (with 22KHz tone signal OFF. TP frequencies at and above 11700 activate a 22KHz signal and LOF/H is active.

Depending how it is coded, leaving the Threshold setting blank with identical both high and low LO settings, this may cause transponders to be scanned twice, analyzed twice or even logged twice. This often doubles the scan time.

Try setting the Threshold at 11700 and report if this affects the blind scan either in a positive or negative way.

I can report that the latest OpenPLi RC blind scan menu changes the polarity to Vertical and Horizontal when standard LNB is used. You no longer have to manually change it.

 

[Chewie]

Hello Brian
I have Ortho feeds for my C and Ku bands, and always had problems with the Ku having duplicates channels, tonight I follow your suggestions to set the threshold to 11700.
This is my setup now and I do not get any more duplicates so far on Ku.
Thanks this work for me.
Regards.
Tunder