Huevos

@Dimitrij, those are just Unicable 1 devices. Here I am testing with one of these.

https://www.hm-sat-s...teilnehmer?c=83

 

@bzlr, both the Vu Zero, and some of the ET's had driver issues, and needed additional safe time (about 100ms). The debug output would show this.

But still someone needs to offer us a JESS configuration -or- someone who has a JESS configuration needs to offer us a good patch that can be accepted...

The following code is working and has been briefly tested in OpenPLi.

 

Based on commits by "dvb-adenin" between March 2015 and January 2016

 

https://github.com/H...bfe5d37e428c156

 

 

Erik, here is my bug report.

Vu Solo 4K 20160119 driver bug.

Unicable picture break-up bug.

Tested in:
OpenViX, 
OpenATV,
OpenPLi,
Blackhole.

Setup:
Tuner A, Advanced, Unicable, SCR 1. Tuner A is the root tuner.
Tuner C, Advanced, Unicable, linked to tuner A, SCR 2.
Tuner D, Advanced, Unicable, linked to tuner A, SCR 3.
Tuner E, Advanced, Unicable, linked to tuner A, SCR 4.

Bug:
Picture is broken or there is no picture on tuners C/D/E if the root tuner is inactive.

Method 1:
View a service on tuner A.
Start recording that service.
Zap to a different service.
Stop the recording.
Viewed service is now broken.

Method 2:
View a service on tuner A.
Start recording a different service.
Put box in standby.
Recording is broken.

Method 3:
Set preferred tuner to tuner C.
Zap to a service.
Viewed service is now broken.

Method 4:
Anything else that causes the root tuner to become inactive.

Also, the drivers are generally unreliable even when the root tuner is in use.
Just zapping on tuner A the box often fails to get tuner lock however long you wait.

Symlinks and service references are a pain in the neck. How it is now picons are human readable. You can just transfer them from PC to FAT32 formatted stick and run them from there. Pull the stick out, put it in a different box, etc, with zero user knowhow.

 

These boxes have sufficient processing power to sacrifice some of it making them user friendly for everyone.

Have a look in OE-A ABM plugin. In tools.py for examples.

On the issue of alternatives the client box only has the principal service in its bouquet as the server box decides what alternative to stream. But the plugin still needed to understand alternative in order to be able to descend into the alternative bouquet and grab the principal service.

RCSC. OE-A version does handle alternatives. Check the GiT history and merge the last couple of commits. Should be easy as nothinghas changed in PLi version since my previous changes a few months ago.

Please don't make changes to break this.

Record indicator bug is aseparate issue. Recording channel and all its alteratives show as recording in the channel list even though it is just the principal service recording.

BTW, for anyone who wants to convert service ref picons to service name you can use this script.

 

Put it in /tmp

Telnet to the STB

cd /tmp

python rename-picons.py

 

Output will be a zip file: /tmp/picons.zip

Picons by 'Service name'.

 

Benefits:

Picon names are human readable.
If the service ref changes, the picon continues to work without intervention.
Picons can be shared between satellites, terrestrial and cable.
No symlinks are necessary for picon sharing. That means picons that previously needed symlinks can now work from a FAT32 formatted USB stick.
Service-ref picons take priority, so where a unique picon is needed, for example where regional channels all use the same service name, they are still available.

Filename format is as follows:

Lower case, bbconehd.png (this allows BBC One HD and BBC ONE HD to share a picon (Das Earst, 19.2E; DAS ERSTE, 13.0E; etc))
No spaces,
Excluded characters: ['/', '\\', '\'', '"', '`', '?', ' ', '(', ')', ':', '<', '>', '|', '.', '\n']
Special characters: '*', '+' and '&' are converted to 'star', 'plus' and 'and' respectively.

 

Enjoy!

1) Simple config should be simple. Never heard of any LNB that needs a DiSEqC instruction. DiSEqC commands are to control DiSEqC switches and motors. If the LNB needs this it is faulty.

 

2) What makes this particular circular LNB more important than my circular LNB that uses a different local oscillator frequency, or different from Australian LNBs that use a different LO frequency again, or different from a US circular LNB that uses a different LO frequency too. Or more important than a Ka band LNB? Or more important than a C-band LNB? This is a personal configuration and doesn't belong in the simple config screen. Simple config screen is for Universal LNBs only. If you want a special config for this LNB add it in 'Advanced' as Russian circular LNB. But it certainly doesn't go in the simple screen.

And terrestrial region selectable from 'Manual Scan'. Defaults to region selected in tuner setup.

 

 

Already in my lastest version.

 

 

Done that myself now. Also changed predefined list so it holds the index, rather than a list of tuner objects. This is how predefined list works for satellites (and in other plugins too, Sat finder for example). I can't see a need to re-invent the wheel (except to confuse people reading the code).

 

Code here,

https://github.com/O...b14db28ec3a7053

I can run an online update if necessary but from what I understand this option has been in the image for quite a while, so a 3-month's old image should definitely include it.

You need to do an update.

Well if the dish is set up as USALS you need to switch that off. Then go into positioner setup. Move the dish to the correct position (using the east/west controls via the coloured buttons). Then save.

 

BTW, if you write any future query in proper English and you will find more people will reply.