search

zgemma-star / meta-zgemma

6 stars 10 forks source link

Blindscan "C band" Zgemma h9s #85

Open frankviana opened 4 years ago

frankviana commented 4 years ago

Hi. We have a problem using dmm binary for blindscan. It's necessary new bin file.

Here, a lot of problems related, then, I have some logs:

For more details, see this post:

https://forums.openpli.org/topic/75722-zgemma-h9s-blindscan/

Tests using a lot of images: OpenATV, PurE2, OpenPli, etc.... same problems.

Loop mode and wrong ranges (example: start frequency: 3600; stop frequency: 4200).

1_0_19_F0_66_138B_BCB0000_0_0_0_19700101000149 screenshot_19700101000230 1_0_19_F0_66_138B_BCB0000_0_0_0_19700101000137

[ActionMap] Keymap 'OkCancelActions' -> Action = 'ok'.
ID:  0
[Skin] Parsing embedded skin '<embedded-in-DmmBlindscan>'.
[Skin] Processing screen '<embedded-in-DmmBlindscan>', position=(650, 325), size=(620 x 430) for module 'DmmBlindscan'.
[Skin] Processing screen 'SetupSummary', position=(0, 0), size=(-1 x -1) for module 'SetupSummary'.
[eConsoleAppContainer] Starting /usr/bin/grab
[ActionMap] Keymap 'SetupActions' -> Action = 'ok'.
tunername Si2166D
[eDVBCAService] free slot 0 demux 0 for service 1:0:19:F0:66:138B:BCB0000:0:0:0:
[eDVBCAService] free service 1:0:19:F0:66:138B:BCB0000:0:0:0:
[eTSMPEGDecoder] decoder state: play, vpid=ffffffff, apid=ffffffff
[eDVBPCR0] DEMUX_STOP ok
[eDVBPCR0] destroy
[eDVBVideo0] DEMUX_STOP  ok
[eDVBVideo0] VIDEO_STOP ok
[eDVBVideo0] destroy
[eDVBAudio0] AUDIO_STOP ok
[eDVBAudio0] DEMUX_STOP ok
[eDVBAudio0] AUDIO_CONTINUE ok
[eDVBAudio0] destroy
cleaning up
TuxTxt cache cleared
[eDVBLocalTimerHandler] remove channel 0x23f7170
[eEPGCache] remove channel 0x23f7170
Sat Blindscan current range (10700000, 11700001, 0)
[eDVBFrontend0] tune
[eDVBSatelliteEquipmentControl] direct_connected 1
[eDVBSatelliteEquipmentControl] canTune 1
[eDVBSatelliteEquipmentControl] lnb 0 found
[eDVBSatelliteEquipmentControl] sat 3019 found
[eDVBSatelliteEquipmentControl] ret1 10000
[eDVBSatelliteEquipmentControl] ret5 10000
[eDVBSatelliteEquipmentControl] ret 0, score old 0
[eDVBSatelliteEquipmentControl] score new 0
[eDVBSatelliteEquipmentControl] final score 0
[eDVBSatelliteEquipmentControl] found no useable satellite configuration for DVB-S2 freq 10700000H QPSK on orbital position (3019)
[Skin] Parsing embedded skin '<embedded-in-SatBlindscanState>'.
[Skin] Processing screen '<embedded-in-SatBlindscanState>', position=(550, 280), size=(820 x 520) for module 'SatBlindscanState'.
[Skin] Attribute 'correct_aspect' (with value of 'width') in object of type 'eCanvas' is not implemented!
[Skin] Processing screen 'SimpleSummary' from list 'SatBlindscanState_summary, SimpleSummary', position=(0, 0), size=(-1 x -1) for module 'SimpleSummary'.
LOCKED at 4080000
CURRENT freq 4080000 -6620/4098
[eDVBFrontend0] tune
[eDVBSatelliteEquipmentControl] direct_connected 1
[eDVBSatelliteEquipmentControl] canTune 1
[eDVBSatelliteEquipmentControl] lnb 0 found
[eDVBSatelliteEquipmentControl] sat 3019 found
[eDVBSatelliteEquipmentControl] ret1 10000
[eDVBSatelliteEquipmentControl] ret5 10000
[eDVBSatelliteEquipmentControl] ret 0, score old 0
[eDVBSatelliteEquipmentControl] score new 0
[eDVBSatelliteEquipmentControl] final score 0
[eDVBSatelliteEquipmentControl] found no useable satellite configuration for DVB-S2 freq 10700000H QPSK on orbital position (3019)
LOCKED at 4080000
CURRENT freq 4080000 -6620/4098
[eDVBFrontend0] tune
[eDVBSatelliteEquipmentControl] direct_connected 1
[eDVBSatelliteEquipmentControl] canTune 1
[eDVBSatelliteEquipmentControl] lnb 0 found
[eDVBSatelliteEquipmentControl] sat 3019 found
[eDVBSatelliteEquipmentControl] ret1 10000
[eDVBSatelliteEquipmentControl] ret5 10000
[eDVBSatelliteEquipmentControl] ret 0, score old 0
[eDVBSatelliteEquipmentControl] score new 0
[eDVBSatelliteEquipmentControl] final score 0
[eDVBSatelliteEquipmentControl] found no useable satellite configuration for DVB-S2 freq 10700000H QPSK on orbital position (3019)
[DVBCAHandler] no more services
LOCKED at 4080000
CURRENT freq 4080000 -6620/4098
[eDVBFrontend0] tune
[eDVBSatelliteEquipmentControl] direct_connected 1
[eDVBSatelliteEquipmentControl] canTune 1
[eDVBSatelliteEquipmentControl] lnb 0 found
[eDVBSatelliteEquipmentControl] sat 3019 found
[eDVBSatelliteEquipmentControl] ret1 10000
[eDVBSatelliteEquipmentControl] ret5 10000
[eDVBSatelliteEquipmentControl] ret 0, score old 0
[eDVBSatelliteEquipmentControl] score new 0
[eDVBSatelliteEquipmentControl] final score 0
[eDVBSatelliteEquipmentControl] found no useable satellite configuration for DVB-S2 freq 10700000H QPSK on orbital position (3019)
LOCKED at 4080000
CURRENT freq 4080000 -6620/4098
[eDVBFrontend0] tune
[eDVBSatelliteEquipmentControl] direct_connected 1
[eDVBSatelliteEquipmentControl] canTune 1
[eDVBSatelliteEquipmentControl] lnb 0 found
[eDVBSatelliteEquipmentControl] sat 3019 found
[eDVBSatelliteEquipmentControl] ret1 10000
[eDVBSatelliteEquipmentControl] ret5 10000
[eDVBSatelliteEquipmentControl] ret 0, score old 0
[eDVBSatelliteEquipmentControl] score new 0
[eDVBSatelliteEquipmentControl] final score 0
[eDVBSatelliteEquipmentControl] found no useable satellite configuration for DVB-S2 freq 10700000H QPSK on orbital position (3019)
LOCKED at 4080000
CURRENT freq 4080000 -6620/4098
[eDVBFrontend0] tune
[eDVBSatelliteEquipmentControl] direct_connected 1
[eDVBSatelliteEquipmentControl] canTune 1
[eDVBSatelliteEquipmentControl] lnb 0 found
[eDVBSatelliteEquipmentControl] sat 3019 found
[eDVBSatelliteEquipmentControl] ret1 10000
[eDVBSatelliteEquipmentControl] ret5 10000
[eDVBSatelliteEquipmentControl] ret 0, score old 0
[eDVBSatelliteEquipmentControl] score new 0
[eDVBSatelliteEquipmentControl] final score 0
zgemma-star commented 4 years ago

HW blindscan never needs an external bin file. So if you install a binairy please remove it. C-Band LNB has other LO value like 5150/5750 so the scan range which you want to scan should been adjust as well.

I think the blindscan is now made for KU band LNB's and need first some improvements. When it doesn't work then we can report it to Silabs as the box uses HW blindscan through the Silabs drivers.

frankviana commented 4 years ago

Yes... I know about C band (5150/5750) and I have all configuration OK.

Blindscan working fine for C band too, not only for Ku band. Example Vu's receivers. I have zero and zero4k working very very fine. For zero4k, including internal (same h9s si2166D) and external USB TBS card 5925 using a lot of parameters...

I think you need report to Silabs to solve this problems.

See Zero4k working fine C band (si2166D too):

screenshot_20200722174907

1_0_1_66_1_43_B530000_0_0_0_20200722174950

screenshot_20200722175222

screenshot_20200722180036

screenshot_20200722181125

screenshot_20200722181141

zgemma-star commented 4 years ago

Please test with same image and same plugins as this is not comparable. Probably the extra settings you see is given by a different plugin.

What is happing on the VU seems not right. The transponder is showing as V-H but this is L-R. Ku-band start 4 scans V-low/ V-high/ H-low/ H-high C-Band start 2 scans R-L

This is not arranged in the plugin and second the scan range is probably not good recalculate to the Enigma2 value.

frankviana commented 4 years ago

I don't understood, but I'll test using ATV too. I did several times and same result. Working only Ku band.

frankviana commented 4 years ago

All foruns and users reporting: don't work C band. A lot of images tested.

zgemma-star commented 4 years ago

ll test using ATV too. I did several times and same result. Working only Ku

Your testing now with different blindscan plugins and this is not comparable.

Please test zero and zero4K with same Openpli version and same blindscan plugin. I think you will get similar problems and that it don't work.

So first we need to been sure that the plugin from Openpli works with Cband transponders

frankviana commented 4 years ago

Sorry... zero don't have blindscan (confused, a lot of receivers), but zero4k and last OpenPli working fine C band.

I bought my zero4k for years and always test C blindscan, including TBS 5925 usb card. American users always need this feature.

See:

1_0_1_12C_12D_1_BCB8E88_0_0_0_20200723060437 1_0_1_12C_12D_1_BCB8E88_0_0_0_20200723060606 1_0_1_12C_12D_1_BCB8E88_0_0_0_20200723060612 1_0_1_12C_12D_1_BCB8E88_0_0_0_20200723060631 1_0_1_12C_12D_1_BCB8E88_0_0_0_20200723060646 screenshot_20200723060229 screenshot_20200723060245 screenshot_20200723060257 screenshot_20200723060416

For h9s, I'm using same version 7.3 OpenPli (fresh from today) to test and OpenATV too

frankviana commented 4 years ago

I think no need more tests...

First post: H9 (fresh same OpenPli) Last post: Zero4k (fresh same OpenPli)

Same Si2166D

Then different plugin (binary)

Screen for h9 OpenPli blindscan (original dmm "Dreambox" blindscan)

88216101-05bea500-cc33-11ea-953e-8e71e297ad06

Screen for Zero4k OpenPli blindscan ("own" modified vuplus blindscan)

1_0_1_12C_12D_1_BCB8E88_0_0_0_20200723060612

zgemma-star commented 4 years ago

Plugin is Python code and zgemma doesn't maintain the blindscan plugins. What can been done if there is a problem with C band Blindscan in the drivers then it can been look to it. However if the plugin your using only support uiversal LNB (KU) then first this should been improved.

First point is to compare the boxes with each other to see if there is any difference. First it need to have same image and same PLUGIN.

That you use a different plugin on the zero4k gives me the idea that the blindscan plugin in Openpli doesn't support Cband scanning on your zero4k as well. Right?

Further why do set you frequency on the Openpli plugin 10700/12750 and with your own modified plugin on 3700/4200 Your modified plugin is available as source so that probably parts can been copied from it?

frankviana commented 4 years ago

Plugin is Python code and zgemma doesn't maintain the blindscan plugins. What can been done if there is a problem with C band Blindscan in the drivers then it can been look to it. However if the plugin your using only support uiversal LNB (KU) then first this should been improved.

First point is to compare the boxes with each other to see if there is any difference. First it need to have same image and same PLUGIN.

That you use a different plugin on the zero4k gives me the idea that the blindscan plugin in Openpli doesn't support Cband scanning on your zero4k as well. Right?

Further why do set you frequency on the Openpli plugin 10700/12750 and with your own modified plugin on 3700/4200 Your modified plugin is available as source so that probably parts can been copied from it?

I don't know about difference between OpenPli plugins... I just downloaded the blindscan plugin in the same way, on systemplugins for both receivers... and we were unable to change to 3600/4200 for OpenPli, OpenAtv, Pure2 (tested). Only OpenVision change this parameter (3600/4200), but no channels found.

I don't understand about code lines (python). I'm only a tester...

Then, only OpenVision appear for h9 the correct ranges (3600/4200), need fix why no channels found.

zgemma-star commented 4 years ago

openpli 7.3 on VU zero4k you download blindscan plugin and all is fine? openpli 7.3 on Zgemma H9 you download blindscan plugin and you cannot change frequency to 3600/4200?

If so then it must install a different plugin, however I do not see as both seems to use the "DMM" blindscan plugin. So both canot adapt to 3600/4200.

frankviana commented 4 years ago

See my post from April 20, 2020

https://forum.openvision.tech/viewtopic.php?f=5&t=677&start=20#p8680

My old pictures

1_0_1_1FA_355F_DE_DBF0000_0_0_0_20200229080316 1_0_1_7E6_3560_3560_DBF0000_0_0_0_20200403091331 screenshot_20200403024256 screenshot_20200403024956 1_0_1_7E6_3560_3560_DBF0000_0_0_0_20200403091106 screenshot_20200403091128 screenshot_20200403091140

frankviana commented 4 years ago

openpli 7.3 on VU zero4k you download blindscan plugin and all is fine? openpli 7.3 on Zgemma H9 you download blindscan plugin and you cannot change frequency to 3600/4200?

If so then it must install a different plugin, however I do not see as both seems to use the "DMM" blindscan plugin. So both canot adapt to 3600/4200.

openpli 7.3 on VU zero4k you download blindscan plugin and all is fine?

YES

openpli 7.3 on Zgemma H9 you download blindscan plugin and you cannot change frequency to 3600/4200?

YES

But there is only this plugin available for OpenPli... And, for OE-Alliance (Pure2, OpenATV), don't change 3600/4200 too... only OpenVision (post above)

frankviana commented 4 years ago

OpenVision, OpenPli, Pure2, OpenATV.... all working fine Ku band (search and found all channels)

OpenVision appear correct 3600/4200, but no channels found (C band) All the rest, don't change for 3600/4200, and appear wrong frequencies (C band).

1_0_1_4_2_0_DF22B7E_0_0_0_20200420084033 screenshot_20200420083753 screenshot_20200420083830