Robinson

Perhaps it is worth copying the info here from Github:

 

Changes:
- The motor index field now allows numeric input instead of just a selection which
was cumbersome to use with indices going up to 50 or so.
- There was a performance issue with the tuning screen as it was using the scanner
screen. The required code is now isolated and tuning selection works much faster.
- The tune screen now correctly points to the satellite and transponder of the currently
playing service. The tuning screen now identifies the correct transponder as
predefined – if indeed it is.
- The motor index field is now correctly filled-in after selection of the satellite.
- Fields are added to specify an X coordinate for the gotoX command. This field is
automatically set according to the satellite tuned but can, of course, be filled in
manually as well.
- A gotoX command is added under the yellow button (USALS use).
- The auto-focus function is added under the red button.
- USALS calibration is added under the red button.
- Additional parameters are added in the advanced satellite section of the tuner setup
screen to specify the detailed characteristics of the rotor is use.
- A log function is added under the ‘info’ button to log the details of all steps and
measurement values, including the exact diseqc parameters. All actions are also
shown to the user in a status bar on the screen.
The rotor parameter defaults are reasonably universal but you should supply your rotor
parameter is known. The rotor speeds are in degrees/sec, one for horizontal and one for
vertical polarisation. These are only used to estimate the rotor movement time. The
‘step size’ is in degrees and is more critical as it determines the actual resolution used in
the position calculations.
The requirement for using auto-focus is that there must be a signal that the tuner locks
on. The auto-focus search range is artificially limited to +/- 5 degrees. The calculation
uses the weighted average, not the maximum signal position. All measured values are
logged. Use the ‘info’ button to access the log. There should not normally be more than
1 step between the center of the beam and the maximum signal position. The auto-focus
position can be stored in a motor index. The search directions are randomized to avoid
bias. The calculation of the auto-focus position should be reproducible. If not, the rotor
probably suffers from wear and tear and should be considered for replacement.
The USALS calibration is a way to determine a misalignment – if any – on your rotor
installation. Especially useful if the physical rotor setup is difficult to reach. At least
three measurements are needed, one on each opposite side of your rotor range and one
in the center. If the readings on the opposites e significantly different, there is something
wrong with the physical setup. If the deviation on each end of the rotor range is about
the same, an opposite shift could be applied to the site longitude to correct for a
longitude misalignment.
The requirement for using the calibration is that the target is within +/- 10 degrees. This
is an artificial limit to prevent inadvertent full-scale moves. The search directions are
unbiased.
There is something in Diseqc called Re-calculate. This is largely undocumented by
Eutelsat and does not seem to be implemented in most rotors. The usefulness is
questionable and is presently not supported.

There are no HD versions on this satellite. What you get is just "empty SID's", which has been mentioned many times in this thread.

There are no transport streams on these SID's on 27.5W.

These files are no longer necessary.

However, I do not have an Ultimo 4K or OpenPLi 7.0, so I cannot check.

Hmmmm, I like "Power Options" which is very accurate, but I'm afraid it won't translate well to other languages.

To me it does not really matter if names are kept or changed but I would say the atatched should translate into Greek quite well.

The values here are correct because the screenshots come from a different box.

MCelliotG is totally right, so I'm not sure why WTE is trying to ridicule him.

I also bought HD51 because it was widely recommended for its reliability and support.

The first thing was "rotor issue", which Huevos warned us against. Despite that, I decided to buy it only to experience a long waiting time before the picture appears after moving the dish. That was the main issue for me, apparently worked-around for a simple setup - with the powermeasurement set to off. OK.

Then there's service information in the menu. If blue buton is used to show frontend info, only 2 oscilaltor frequencies are shown, instead of service frequency. If lamedb values are displayed then everything is OK but I would really prefer the real frequency as reported correctly by the tuner.

And the third issue is signal strength. So far, my previous boxes have shown smooth values while HD51 reports signal strength with large increments but I have not investigated this issue very much.

This is an example entry for 27.5W:

44c8:0cfdace7:1000:0001:25:0:0
ITV1 HD
p:ITV,c:001839,c:031839,c:050001,c:09183d0101,c:12183a,c:161838,C:2600,f:400

Look for all the entries with 0cfdace7.

What is your box?

"A" entries in oscam.dvbapi?

Softcam keys?

What does oscam log say?

By the way, if you are using a genuine OpenPLi image, you do not need doublet's script any more, at least on PLi 6 but PLi 4 probably the same.

 

I am not a multiswitch expert and not even a user but I think you only need the following for a traditional and reliable setup:

- 3 x quatro LNB's

- 12+2 multiswitch,

- 2 cables running to your twin tuner.

As for Unicable and FBC, I do not have any experience with this either. They could possibly somehow simplify your setup but I think it is already simple enough.

 

 

Thanks. This is an interesting setup. But why would I need 3 quatro LNB's?
I’m only planning to have a TV in the living room not anywhere else.
Isn’t the Unicable solution the point of skipping such an intricate setup? With one cable only from the satellite dish?

 

If you need to receive 3 satellites at the same time, you must have 3 LNB's. They are quattro because they will be conncected to a multiswitch (3 x (H Low, V low, H high, V high)). That makes 12 short cables from LNB's to your multiswitch at the dish. Then you will only have 1 cable running at home to your box.

I'm still considering to post a how-to, how to install and configure OpenVPN on your box and how to create (as example) good keys a.....  and how te create a .opvn file for your iPad/iPhone... but as the preferable safety is to use the VPN of your server I did not post it yet...

The how-to would indeed be very useful.

Are they all UK beam?

opkg install dvbsnoop

OK, maybe Enigma2 indeed does not know ProvID so it would be great to have a script (which could be assigned to a key using HotKey) which could read this sort of information from a running Oscam or other cam.

Can you please restore the following Eurosport HD entry?

1_0_1_330E_190_13E_820000_0_0_0

It has a better bitrate than the one used by Ampersand.

Thank you.

is limitation in your streamproxy,? there is only 2 porfiles. Why do you soo? You are not helful man?

Erik is one of the most helpful men on this forum.

Read from this: http://openpli.org/f...sat#entry265948