dm920 - FBC tuner issues

I try to explain.

In my DM920 2 tuners are installed: 1x satellite FBC Twin tuner (2 input), 1x terrestrial Twin tuner (2 input). So I have 2 F connectors and 2 IEC connectors on the back panel.

The terrestrial tuner works ok, I can use both tuners together for, say, wath a channel and record a different one.

Instead, the satellite tuner is not recognized correctly. I see 8 tuners in the Tuner Configuration menu (it's ok), but only the first one does work correctly.

Using the Openvix image I can freely configure the first 2 tuners as I want, leaving the remaining 6 unmodified, so the FBC feature is automatically configured. The same does occur with every OE2.5 images that I tested.

In other OE2.0 images (I tested Openatv, Satlodge, now this "customized" Openpli), when I configure the second tuner, the configuration is apparently accepted but it does not work: the box gets the satellite signal always from the first F connector, so the receiver can't be used with two different dishes.

As the Openvix works, how can I move the right files to a different image? Any cut/paste operation is enough maybe? If possible, could you please tell me how to proceeed? Thanks.

Just tested but no way. The box does recognize only one tuner (the first, listed as tuner A). The remaining 7, whatever the configuration, do not work, so it is like the second F connector do not exist.

So the "Equal to" option could be selected only for the first tuner, that's unuseful as I want to use the second one too.

What about the FBC tuner problem?

I mentioned this in another thread today. In many OE2.0 images (other than Openvix) the FBC tuners are not fully supported, and only the first input does work.

What about here? Anyone tested? As soon as I have a little bit of time I will surely make my test, but if this problem does occur again I can't use this image and it would be a pity.

Anybodyelse has the same FBC tuner like me in the DM920?

This limitation is very annoying, because all these OE2.0 images are not suitable. Bad luck.

Thank you very very much for your kindness, really appreciated.

Yes the Openatv image has the same tuner handling problem. The only OE2.0 image working well is the Openvix.

Could you please explain better this github link you posted?

Maybe the problem could be solved downloading files from there? Whih file? Thank you again.

So,if I understand correctly, I can't download any useful file from that Github link, right?

Visiting that web page, I find only source files, not a real patch.

So I must wait when the Openatv 7.6 will be officially released?

I try to tell you any possible information.

I have a DM920 with two tuners installed: 1x Twin FBC satellite tuner (2 inputs), 1x Twin terrestrial tuner (2 inputs).

The terrestrial tuner always works well without problems with ALL images.

The satellite tuner works well ONLY with Openvix, and with every OE2.5 images.

My dish setup:

Input 1: dual feed dish (Hotbird + Astra) with a diseqc switch;

Input 2: motorised dish with a standalone motor controller, so the receiver is configured as a common universal LNB.

I have different behaviours in the Tuner Configuration menu depending from the installed image.

Openvix: Tuner A and B are detected as FBC IN 1 and FBC IN 2, and configuring both them as needed (Tuner A: simple mode, dual feed; Tuner B: Advanced mode, Universal LNB for each satellite other than those in the Dual Feed tuner to avoid conflicts). The remaining six tuners are shown as Automatic Inactive, and I never changed them. It does work.

Every other OE2.0 image: all 8 tuners are identical, all shown as independent tuners like having eight single tuners installed in the box instead of one, so the FBC feature is not recognized. Only the first tuner does work properly. Attempting to configure every tuner other than the first, the configuration in the Menu is accepted and saved but it does not work. In other hands, the firmware does never recognize the second input. I largely tried to configure the remaining seven tuners one by one but no way.

I hope this helps. Please let me know if you need more information. Thanks.

Please note that the only working image is the Openvix 6.7.014, all other images work in the way I explained above.

I'm not interesting in the FBC feature as I have no Unicable LNBs, so I use only the first 2 tuners in the list.

As I specified above, the Openvix image does detect the first 2 tuners as FBC IN 1 and FBC IN 2, so I can smoothly configure them for my purpose. The remaining six tuners are shown as FBC Automatic and I don't change them.

In every other images all tuners are shown in the same way, so no differences between the first 2 and the remaining 6, and as I mentioned only the first one does work.

This is my situation. Hope this helps. Thanks.

Thank you for moving this thread in a more proper section. Now it is a thread on its own.

So, I understand your explanation. As I mentioned earlier, I have no Unicable LNBs, and I'm not interesting in any connection between tuners.

My only need is having the 2 satellite input connectors working like 2 fully independent tuners.

I confirm that the satellite card is in the slot 1: so Tuner A = input 1 = dual feed dish, Tuner B = input 2 = motorised dish (no motor movement from the receiver).

I repeat that the Openvix 6.7 (now 6.7.014) is the only image that works properly, so I keep it in my box now.

Hoping that the problem will be solved in more images like Openatv or custom build of Openpli.

Just a question: is it possible to transfer the proper files from an installed Openvix to different images? If so, how can I proceed?

Or is the problem fixable only modifying source files and recompiling the entire image?

Thank you so much for your great support.

Did you tested your tuner with different images other than Openvix?

If the Openvix developers was able to fix the problem, I presume (and hope) that it will be solved in more images. Let's see.