11 replies to this topic

[MellisJ]

Hello!
I'm running OpenPLi 6.1 (latest).
Very often I get "Tuning failed" (translated from Swedish) when a recording is running and the box is switching tuner. Sometimes it works, but very often it fails.
I have tested Egami 8.0.6 and I can't get that tuner problem in Egami. It's switching of tuners is rocksolid! I have seen "tuning failed" blinking right after the switching, but the picture always starts in a few seconds.
Former I was using OpenMB 5 and the tuners is more stable in that distribution too. I have flashed that dist too for testing the last days.
 
I could use Egami to solve the problem, but I really like OpenPLi.
In system info I see 3 different drivers for the 3 distributions I have tested.
Is it possible that the drivers in 6.1 is the problem?

 

Box: Miraclebox Premium Twin+
Tuners: Si216x (DVB-T2)
Driver version (date):
- OpenMB: 2016-12-15
- OpenPLi 6.1: 2017-04-24
- Egami: 2017-06-12

[jort38]

That happened to me as wel on DVBT when I used transcoding and returned after that to DVBT.
Rescanning helped me.

[littlesat]

Mirakel needs to update their bsp...

[MellisJ]

Mirakel needs to update their bsp...

Where can I ask for that?

[mrvica]

I would say here http://www.miraclebox.se/

Support / Contact us

[MellisJ]

I do not really understand this.

Is Miraclebox responsible for that OpenPLi is using older drivers than Egami?
I thought that enigma drivers were universal to be used in all distribution?
Is it Miraclebox that provide these distributions with different drivers?

If Miraclebox actually is resposible for this: what exactly should I ask them?

[WanWizard]

The drivers are part of the BSP (Board Support Package), which is a layer that provides hardware abstraction or hardware compatibility to OpenEmbedded.

 

Some image builders create their own BSP layers, but we don't, we use the one the manufacturer supplies, as that is what the manufacturer supports. So yes, Micraclebox is responsable.

[MellisJ]

The drivers are part of the BSP (Board Support Package), which is a layer that provides hardware abstraction or hardware compatibility to OpenEmbedded.
 
Some image builders create their own BSP layers, but we don't, we use the one the manufacturer supplies, as that is what the manufacturer supports. So yes, Micraclebox is responsable.

Thanks everybody for answers.
Ok, I will contact Miraclebox!

For curiosity I would like to know if Miraclebox provide different BSP to each distribution?
(Otherwise OpenPLi and Egami would have same drivers)

[WanWizard]

No, as far as I most manufacturers publish new drivers, and have the image builders create the BSP.

 

We don't, we want the manufacturer to do that, they need to have a BSP anyway to be able to test their drivers. The Micraclebox BSP is here: https://github.com/m...meta-miraclebox

[marpal]

I got a very similar problem, with my miraclebox premium twin.

 

The error could be derived to a weak signal after long troubleshooting.

When I measured the signal with instruments, I had the contacts correctly, which did that the measurement showed a good signal :-(.

The solution was to put on new contacts and after that the problem was solved.

[MellisJ]

I got a very similar problem, with my miraclebox premium twin.
 
The error could be derived to a weak signal after long troubleshooting.
When I measured the signal with instruments, I had the contacts correctly, which did that the measurement showed a good signal :-(.
The solution was to put on new contacts and after that the problem was solved.

Thanks for answer..
But... It works with Egami. That’s why I do not think its harware/siglnal
I have SNR99% AGC 91 BER 0.

[MellisJ]

I want to close this topic by telling that the ”OpenPli-staff” has contacted Miraclebox and got an updated bsp with new drivers, which is implemented in OpenPli 7 rc. Now my prolems are gone.
Thank You OP-staff!!! You’re awsome!