This is a long standing bug affecting FBC tuners and Universal LNBs. There isn't an issue with FBC tuners and Unicable/Jess devices. It was originally reported as a bug on 19th November 2018 on another image from where OpenAAF forked from. As OpenATV uses different FBC code, other aspects of Enigma2 might be at play, not the FBC . OpenPLI does not have the issue.
Describe the bug / Actual behaviour:
If you have an FBC tuner with two wires from universal LNBs pointing at the same satellite, you should be able to access all the services on four transponders. For the attached video/log, I scanned following transponders.
282.e Vert Low 10818
282.e Vert High 12363
282.e Hor High 12226
282.e Hor Low 11053
To ensure that I did not accidentally scan any other services, I modified the satellites xml so it only had those.
[[A clear and concise description of what the bug is.]]
Sorry, not able to be concise as it is complicated. A user is not able to use/access the transponders that should be available when using an FBC tuner with a universal LNB. Yes, we can say get a Unicable/Jess device, but what about people using universal LNBs on fixed dishes or those using a motorised dish (which should be universal LNB) and one of the tuners is set to FBC automatic which in essence is just internal loop through.
Expected behaviour:
I should be able to record/access all the four transponders, but somewhere it is getting locked out.
Has this issue started to happen just recently?
No, this was first noticed in 2018.
To reproduce:
Universal LNB hooked up to top socket of FBC matrix/tuner. Universal LNB hooked up to bottom socket of FBC matrix/tuner. Tuners A & B set as simple, single, 28.2.
As you go through the services, you get some services greyed out when they should not be. You are also not able to select current transponder in the video I will link to.
Image/Box Model (please complete the following information):
Issue is long standing. But I have just tested 7.2 and issue is still present.
Experienced on a Vu Solo 4K. Vu Duo 4K, Gigablue UE 4K, Gigablue Quad 4K
Another user (mitchellin) had the issue on a Duo 4K SE, i.e. same chip as Ultimo 4K, so safe to assume bug affects all FBC receivers on ATV and the other image.
Video showing issue. This is 485MB
https://www.mediafire.com/file/y2uog35zolte4d0/openatv_7.2_fbc_universal.ts/file
On PLI, I could get up to 40 services, however they suffer with the efilepush issue. Video showing it below (47MB). This was some months ago, so transponders are different.
https://www.mediafire.com/file/ggdhllq1dnkukqo/Fbc-_Twin_Universal_2022-07_02.m4v/file
The issue also partly affects non-FBC tuners where there is internal loopthrough. I tested with one signal wire on a TM Nano 3T which has the same SOC as a Vu Solo2 . I should be able to access two transponders provided there is no further switching of LNB involved.
I have flashed 11/04/2023 7.2 image.
This is a long standing bug affecting FBC tuners and Universal LNBs. There isn't an issue with FBC tuners and Unicable/Jess devices. It was originally reported as a bug on 19th November 2018 on another image from where OpenAAF forked from. As OpenATV uses different FBC code, other aspects of Enigma2 might be at play, not the FBC . OpenPLI does not have the issue.
Describe the bug / Actual behaviour: If you have an FBC tuner with two wires from universal LNBs pointing at the same satellite, you should be able to access all the services on four transponders. For the attached video/log, I scanned following transponders.
To ensure that I did not accidentally scan any other services, I modified the satellites xml so it only had those.
[[A clear and concise description of what the bug is.]] Sorry, not able to be concise as it is complicated. A user is not able to use/access the transponders that should be available when using an FBC tuner with a universal LNB. Yes, we can say get a Unicable/Jess device, but what about people using universal LNBs on fixed dishes or those using a motorised dish (which should be universal LNB) and one of the tuners is set to
FBC automatic
which in essence is just internal loop through.Expected behaviour: I should be able to record/access all the four transponders, but somewhere it is getting locked out.
Has this issue started to happen just recently? No, this was first noticed in 2018.
To reproduce: Universal LNB hooked up to top socket of FBC matrix/tuner. Universal LNB hooked up to bottom socket of FBC matrix/tuner. Tuners A & B set as simple, single, 28.2.
As you go through the services, you get some services greyed out when they should not be. You are also not able to select current transponder in the video I will link to.
Image/Box Model (please complete the following information): Issue is long standing. But I have just tested 7.2 and issue is still present. Experienced on a Vu Solo 4K. Vu Duo 4K, Gigablue UE 4K, Gigablue Quad 4K Another user (mitchellin) had the issue on a Duo 4K SE, i.e. same chip as Ultimo 4K, so safe to assume bug affects all FBC receivers on ATV and the other image.
Test xml/bouquets attached here: test bouquets fbc universal bug.zip
Debug log: 20230411-074411-enigma2-debug.zip
Video showing issue. This is 485MB
https://www.mediafire.com/file/y2uog35zolte4d0/openatv_7.2_fbc_universal.ts/file
On PLI, I could get up to 40 services, however they suffer with the efilepush issue. Video showing it below (47MB). This was some months ago, so transponders are different.
https://www.mediafire.com/file/ggdhllq1dnkukqo/Fbc-_Twin_Universal_2022-07_02.m4v/file
The issue also partly affects non-FBC tuners where there is internal loopthrough. I tested with one signal wire on a TM Nano 3T which has the same SOC as a Vu Solo2 . I should be able to access two transponders provided there is no further switching of LNB involved.
Pity the skin does not show transponder details.