Jump to content


Photo

vreemde tuner-pericelen

Started by BMWZ3, 03 Mar 2023 17:13

  • Please log in to reply
215 replies to this topic

Re: vreemde tuner-pericelen #101 hw9258

  • Senior Member
  • 33 posts

+3
Neutral

Posted 6 April 2023 - 07:29

For three weeks I studied the destination code of the FBC tuners.

Found one small problem.

example, not unicable:

 

tuner  A - sat 13E

tuner  B - sat 13E

 

Add more recording.

 

A/C/D/E/F record vertical polarization/different transponders

 

B/G record horizontal polarization/different transponders

 

Live TV tuner H vertical polarization

 

Services horizontal polarization is gray color.

When zap this services Live TV work.

 

But when selecting a record, the timer conflict.
I can fix it if anyone needs it.
 
8 recording same time...

A million thanks to the OpenPLi team for all their hard work in FBC code and especially to Dimitrij for all his work including the latest FBC and motor patch.

 

It would be great if you could also fix the problem above with 8 recordings and timer conflict.

 

Thank you again OpenPLi team and Dimitrij!

 

 

google translate

Een miljoen dankzij het Openpli-team voor al hun harde werk in FBC-code en vooral aan Dimitrij voor al zijn werk, inclusief de nieuwste FBC en Motor patch.

 

Het zou geweldig zijn als je het probleem hierboven ook zou kunnen oplossen met 8 opnames en timerconflicten.

 

Nogmaals bedankt Openpli-team en Dimitrij!


Re: vreemde tuner-pericelen #102 BMWZ3

  • Senior Member
  • 56 posts

0
Neutral

Posted 6 April 2023 - 09:55

I agree

Thanks Dimitrij!

mvg pjotter


Re: vreemde tuner-pericelen #103 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 10 April 2023 - 16:28

Wellicht gerelateerd; een reeds lang bestaand probleem.

 

VUDUO2 met twee dubbele tuners draait 8.3 (release).

Tuner A = gemotoriseerd, en heeft o.a. 19.2E

Tuners C&D hebben elk een eigen feed met DiSEqC 1.0 op 13E & 23.5E

Als ik aan tuner C (en of D) 19.2E toevoeg, werkt dat goed voor live-TV.

Maar: E2 weigert nu 19.2E op te nemen van tuner A (wat leidt tot veel timer conflicten, omdat ik nu eenmaal veel opneem van 23.5 op C&D). Zodra ik 19.2 van Tuner C (en of D) verwijder, wordt weer keurig met tuner A opgenomen.

 

Ook andere, op PLi gebaseerde images (o.a. ViX) hebben dit issue.


Re: vreemde tuner-pericelen #104 neo

  • PLi® Contributor
  • 715 posts

+48
Good

Posted 10 April 2023 - 16:32

Even testen met develop om te kijken of dit probleem is opgelost.

 

( google translate )


Re: vreemde tuner-pericelen #105 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 10 April 2023 - 16:53

Problem is in 8.3 and in Develop. This is a long standing bug.


Edited by Huevos, 10 April 2023 - 16:55.

Re: vreemde tuner-pericelen #106 Dimitrij

  • PLi® Core member
  • 10,299 posts

+347
Excellent

Posted 10 April 2023 - 18:24

Wellicht gerelateerd; een reeds lang bestaand probleem.

 

VUDUO2 met twee dubbele tuners draait 8.3 (release).

Tuner A = gemotoriseerd, en heeft o.a. 19.2E

Tuners C&D hebben elk een eigen feed met DiSEqC 1.0 op 13E & 23.5E

Als ik aan tuner C (en of D) 19.2E toevoeg, werkt dat goed voor live-TV.

Maar: E2 weigert nu 19.2E op te nemen van tuner A (wat leidt tot veel timer conflicten, omdat ik nu eenmaal veel opneem van 23.5 op C&D). Zodra ik 19.2 van Tuner C (en of D) verwijder, wordt weer keurig met tuner A opgenomen.

 

Ook andere, op PLi gebaseerde images (o.a. ViX) hebben dit issue.

Please debug log.

 

By the way, is this only a VUDUO2 problem?


Edited by Dimitrij, 10 April 2023 - 18:32.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: vreemde tuner-pericelen #107 Dimitrij

  • PLi® Core member
  • 10,299 posts

+347
Excellent

Posted 11 April 2023 - 05:23

 

Als ik aan tuner C (en of D) 19.2E toevoeg

Use DiSEqC?

 

Tuner A - one dish?

Tuner C/D - anoter dish?


Edited by Dimitrij, 11 April 2023 - 05:23.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: vreemde tuner-pericelen #108 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 11 April 2023 - 10:49

 

 

Als ik aan tuner C (en of D) 19.2E toevoeg

Use DiSEqC?

 

Tuner A - one dish?

Tuner C/D - anoter dish?

 

config.Nims.0.advanced.lnb.1.diseqcMode=1_2
config.Nims.0.advanced.lnb.1.increased_voltage=True
config.Nims.0.advanced.lnb.1.latitude=45.400
config.Nims.0.advanced.lnb.1.longitude=1.700
config.Nims.0.advanced.lnb.1.longitudeOrientation=west
config.Nims.0.advanced.lnb.1.powerMeasurement=False
config.Nims.0.advanced.lnb.1.tuningstepsize=0.150
config.Nims.0.advanced.lnb.1.turningspeedH=1.5
config.Nims.0.advanced.lnb.1.turningspeedV=1.5
config.Nims.0.advanced.lnb.2.diseqcMode=1_2
config.Nims.0.advanced.lnb.2.increased_voltage=True
config.Nims.0.advanced.lnb.2.latitude=45.400
config.Nims.0.advanced.lnb.2.longitude=1.400
config.Nims.0.advanced.lnb.2.longitudeOrientation=west
config.Nims.0.advanced.lnb.2.powerMeasurement=False
config.Nims.0.advanced.lnb.2.tuningstepsize=0.158
config.Nims.0.advanced.lnb.2.turningspeedH=1.5
config.Nims.0.advanced.lnb.2.turningspeedV=1.5
config.Nims.0.advanced.lnb.3.diseqcMode=1_2
config.Nims.0.advanced.lnb.3.increased_voltage=True
config.Nims.0.advanced.lnb.3.latitude=45.400
config.Nims.0.advanced.lnb.3.longitude=1.300
config.Nims.0.advanced.lnb.3.longitudeOrientation=west
config.Nims.0.advanced.lnb.3.powerMeasurement=False
config.Nims.0.advanced.lnb.3.tuningstepsize=0.150
config.Nims.0.advanced.lnb.3.turningspeedH=1.5
config.Nims.0.advanced.lnb.3.turningspeedV=1.5
config.Nims.0.advanced.sat.30.lnb=2
config.Nims.0.advanced.sat.48.lnb=2
config.Nims.0.advanced.sat.70.lnb=2
config.Nims.0.advanced.sat.90.lnb=2
config.Nims.0.advanced.sat.100.lnb=2
config.Nims.0.advanced.sat.130.lnb=2
config.Nims.0.advanced.sat.160.lnb=2
config.Nims.0.advanced.sat.192.lnb=2
config.Nims.0.advanced.sat.255.lnb=3
config.Nims.0.advanced.sat.260.lnb=3
config.Nims.0.advanced.sat.282.lnb=3
config.Nims.0.advanced.sat.315.lnb=3
config.Nims.0.advanced.sat.330.lnb=3
config.Nims.0.advanced.sat.360.lnb=3
config.Nims.0.advanced.sat.390.lnb=3
config.Nims.0.advanced.sat.400.lnb=3
config.Nims.0.advanced.sat.420.lnb=3
config.Nims.0.advanced.sat.450.lnb=3
config.Nims.0.advanced.sat.460.lnb=3
config.Nims.0.advanced.sat.500.lnb=3
config.Nims.0.advanced.sat.505.lnb=3
config.Nims.0.advanced.sat.520.lnb=3
config.Nims.0.advanced.sat.525.lnb=3
config.Nims.0.advanced.sat.530.lnb=3
config.Nims.0.advanced.sat.570.lnb=3
config.Nims.0.advanced.sat.3150.lnb=1
config.Nims.0.advanced.sat.3195.lnb=1
config.Nims.0.advanced.sat.3225.lnb=1
config.Nims.0.advanced.sat.3285.lnb=1
config.Nims.0.advanced.sat.3300.lnb=1
config.Nims.0.advanced.sat.3325.lnb=1
config.Nims.0.advanced.sat.3355.lnb=1
config.Nims.0.advanced.sat.3380.lnb=1
config.Nims.0.advanced.sat.3400.lnb=1
config.Nims.0.advanced.sat.3450.lnb=2
config.Nims.0.advanced.sat.3460.lnb=2
config.Nims.0.advanced.sat.3490.lnb=2
config.Nims.0.advanced.sat.3520.lnb=2
config.Nims.0.advanced.sat.3530.lnb=2
config.Nims.0.advanced.sat.3550.lnb=2
config.Nims.0.advanced.sat.3560.lnb=2
config.Nims.0.advanced.sat.3570.lnb=2
config.Nims.0.advanced.sat.3592.lnb=2
config.Nims.0.advanced.sats=235
config.Nims.0.configMode=advanced
config.Nims.0.diseqcA=130
config.Nims.0.diseqcB=192
config.Nims.0.diseqcC=235
config.Nims.0.diseqcD=282
config.Nims.0.diseqcMode=diseqc_a_b_c_d
config.Nims.0.lastsatrotorposition=192
config.Nims.0.simpleSingleSendDiSEqC=True
config.Nims.1.configMode=loopthrough
config.Nims.1.diseqcA=3601
config.Nims.1.diseqcB=3601
config.Nims.1.diseqcC=3601
config.Nims.1.diseqcD=3601
config.Nims.1.diseqcMode=diseqc_a_b_c_d
config.Nims.2.advanced.lnb.1.commitedDiseqcCommand=AA
config.Nims.2.advanced.lnb.1.diseqcMode=1_0
config.Nims.2.advanced.lnb.2.commitedDiseqcCommand=AB
config.Nims.2.advanced.lnb.2.diseqcMode=1_0
config.Nims.2.advanced.lnb.3.commitedDiseqcCommand=BA
config.Nims.2.advanced.lnb.3.diseqcMode=1_0
config.Nims.2.advanced.sat.130.lnb=1
config.Nims.2.advanced.sat.192.lnb=2
config.Nims.2.advanced.sat.235.lnb=3
config.Nims.2.advanced.sats=282
config.Nims.2.configMode=advanced
config.Nims.2.connectedTo=1
config.Nims.2.diseqcA=282
config.Nims.2.diseqcB=192
config.Nims.2.diseqcC=235
config.Nims.2.diseqcD=282
config.Nims.2.diseqcMode=diseqc_a_b_c_d
config.Nims.3.advanced.lnb.1.commitedDiseqcCommand=AA
config.Nims.3.advanced.lnb.1.diseqcMode=1_0
config.Nims.3.advanced.lnb.2.commitedDiseqcCommand=AB
config.Nims.3.advanced.lnb.2.diseqcMode=1_0
config.Nims.3.advanced.lnb.3.commitedDiseqcCommand=BA
config.Nims.3.advanced.lnb.3.diseqcMode=1_0
config.Nims.3.advanced.sat.130.lnb=1
config.Nims.3.advanced.sat.192.lnb=2
config.Nims.3.advanced.sat.235.lnb=3
config.Nims.3.advanced.sats=192
config.Nims.3.configMode=advanced
config.Nims.3.connectedTo=2
config.Nims.3.force_legacy_signal_stats=True

Edited by Huevos, 11 April 2023 - 10:51.

Re: vreemde tuner-pericelen #109 Dimitrij

  • PLi® Core member
  • 10,299 posts

+347
Excellent

Posted 11 April 2023 - 11:03

There are several dummy values in this config.

Maybe need reset config?

 And need debug log in start E2.


Edited by Dimitrij, 11 April 2023 - 11:05.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: vreemde tuner-pericelen #110 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 11 April 2023 - 11:05

 

 

Als ik aan tuner C (en of D) 19.2E toevoeg

Use DiSEqC?

 

Tuner A - one dish?

Tuner C/D - anoter dish?

 

Tuner A = Motorised dish

Tuners C&D have their own feeds (other dish, with DiSEqC 1.0)


Re: vreemde tuner-pericelen #111 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 11 April 2023 - 11:06

There are several dummy values in this config.

 Need debug log in start E2.

What do you mean dummy values? Which values?

 

This has been tried also in OpenViX and shows the same problem.

<107162.6995> 17:23:07.1754 [Skin] Processing screen 'TimerEntry' from list 'TimerEntry, Setuptimerentry, setup_timerentry, Setup', position=(0, 0), size=(1920 x 1080) for module 'TimerEntry'.
<107162.7454> 17:23:07.2213 [Skin] Attribute 'itemHeight' (with value of '45') in object of type 'eLabel' is not implemented!
<107162.7544> 17:23:07.2304 [Skin] Processing screen 'NumericalTextInputHelpDialog', position=(7, 600), size=(681 x 246) for module 'NumericalTextInputHelpDialog'.
<107162.7966> 17:23:07.2726 [Skin] Processing screen 'SetupSummary' from list 'TimerEntrySummary, SetuptimerentrySummary, setup_timerentrySummary, SetupSummary, ScreenSummary, TimerEntry_summary, Setuptimerentry_summary, setup_timerentry_summary, Setup_summary, SimpleSummary', position=(0, 0), size=(140 x 32) for module 'SetupSummary'.
<107163.8699> 17:23:08.3458 [eInputDeviceInit] 1 18f (399) 1
<107163.8700> 17:23:08.3460 [eRCDeviceInputDev] emit: 1
<107163.8709> 17:23:08.3468 [InfoBarGenerics] Key: 399 (Make) KeyID='KEY_GREEN' Binding='('GREEN',)'.
<107163.8727> 17:23:08.3487 [ActionMap] Keymap 'ConfigListActions' -> Action = 'save'.
<107164.1234> 17:23:08.5993 [eDVBFrontend2] opening frontend
e00000(DiSEqC reset)
e00003(DiSEqC peripherial power on)
e01038fb(?)
e01038f9(?)
<107164.1306> 17:23:08.6065 [eDVBFrontend3] opening frontend
e00000(DiSEqC reset)
e00003(DiSEqC peripherial power on)
e01038fb(?)
[...]
e01038fb(?)
<107164.2473> 17:23:08.7232 [TimerSanityCheck] conflict detected!
<107164.2482> 17:23:08.7242 [RecordTimer] timer conflict detected!
<107164.2499> 17:23:08.7259 [RecordTimerEntry(name=Nieuwsuur (NOS), begin=Mon Aug  8 21:25:00 2022, serviceref=1:0:19:17C0:C82:3:EB0000:0:0:0:, justplay=False, isAutoTimer=False, autoTimerId=None), RecordTimerEntry(name=Bumperkleef (AVROTROS), begin=Mon Aug  8 20:14:00 2022, serviceref=1:0:19:5230:C99:3:EB0000:0:0:0:, justplay=0, isAutoTimer=False, autoTimerId=None), RecordTimerEntry(name=Polynésie, un paradis bleu , begin=Mon Aug  8 20:55:00 2022, serviceref=1:0:1:1B03:3FE:1:C00000:0:0:0:, justplay=False, isAutoTimer=False, autoTimerId=None)]
e01038f9(?)
[...]
e01038fb(?)
<107164.3815> 17:23:08.8575 [TimerSanityCheck] conflict detected!
<107164.3824> 17:23:08.8584 [RecordTimer] timer conflict detected!
<107164.3838> 17:23:08.8598 [RecordTimerEntry(name=Nieuwsuur (NOS), begin=Mon Aug  8 21:25:00 2022, serviceref=1:0:19:17C0:C82:3:EB0000:0:0:0:, justplay=False, isAutoTimer=False, autoTimerId=None), RecordTimerEntry(name=Bumperkleef (AVROTROS), begin=Mon Aug  8 20:14:00 2022, serviceref=1:0:19:5230:C99:3:EB0000:0:0:0:, justplay=0, isAutoTimer=False, autoTimerId=None), RecordTimerEntry(name=Polynésie, un paradis bleu , begin=Mon Aug  8 20:55:00 2022, serviceref=1:0:1:1B03:3FE:1:C00000:0:0:0:, justplay=False, isAutoTimer=False, autoTimerId=None)]
<107164.3919> 17:23:08.8679 [TimerEdit] TimerSanityConflict

 


Re: vreemde tuner-pericelen #112 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 11 April 2023 - 11:13

 

 

 

Als ik aan tuner C (en of D) 19.2E toevoeg

Use DiSEqC?

 

Tuner A - one dish?

Tuner C/D - anoter dish?

 

Tuner A = Motorised dish

Tuners C&D have their own feeds (other dish, with DiSEqC 1.0)

 

config.Nims.0.advanced.lnb.2.diseqcMode=1_2
config.Nims.0.advanced.lnb.2.latitude=45.400
config.Nims.0.advanced.lnb.2.longitude=1.200
config.Nims.0.advanced.lnb.2.longitudeOrientation=west
config.Nims.0.advanced.lnb.2.powerMeasurement=false
config.Nims.0.advanced.lnb.2.tuningstepsize=0.150
config.Nims.0.advanced.lnb.2.turningspeedH=1.5
config.Nims.0.advanced.lnb.2.turningspeedV=1.5
config.Nims.0.advanced.sat.100.lnb=2
config.Nims.0.advanced.sat.130.lnb=2
config.Nims.0.advanced.sat.192.lnb=2
config.Nims.0.advanced.sat.282.lnb=2
config.Nims.0.advanced.sats=282
config.Nims.0.configMode=advanced
config.Nims.0.lastsatrotorposition=282
config.Nims.1.configMode=nothing
config.Nims.2.advanced.lnb.1.commitedDiseqcCommand=AA
config.Nims.2.advanced.lnb.1.diseqcMode=1_0
config.Nims.2.advanced.lnb.2.commitedDiseqcCommand=AB
config.Nims.2.advanced.lnb.2.diseqcMode=1_0
config.Nims.2.advanced.lnb.3.commitedDiseqcCommand=BA
config.Nims.2.advanced.lnb.3.diseqcMode=1_0
config.Nims.2.advanced.sat.130.lnb=1
config.Nims.2.advanced.sat.235.lnb=3
config.Nims.2.advanced.sats=192
config.Nims.2.configMode=advanced
config.Nims.3.configMode=equa

 

l

 


Re: vreemde tuner-pericelen #113 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 11 April 2023 - 11:19

 

 

 

Als ik aan tuner C (en of D) 19.2E toevoeg

Use DiSEqC?

 

Tuner A - one dish?

Tuner C/D - anoter dish?

 

Tuner A = Motorised dish

Tuners C&D have their own feeds (other dish, with DiSEqC 1.0)

 

 

Tuner A is DiSEqC motor for many positions.

 

Tuner B is loopthrough to tuner A.

 

 

Tuners C & D are from a static dish with 3 LNB (13.0E, 19.2E, 23.5E) and diseqc_a_b_c_d switches.

 

If tuners C & D are in use there is a timer config trying to start a recording on 19.2E... but... it is possible to watch live tv from Tuner A of channels on 19.2E. Therefore it is a false conflict as the tuner is a tuner is available and works.

Attached Files

  • Attached File  1.jpg   31.09KB   2 downloads
  • Attached File  2.jpg   31.32KB   2 downloads

Re: vreemde tuner-pericelen #114 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 11 April 2023 - 11:21

So Rob's config above is more or less the same as I explained, except, no loopthrough on tuner B.


Re: vreemde tuner-pericelen #115 Dimitrij

  • PLi® Core member
  • 10,299 posts

+347
Excellent

Posted 11 April 2023 - 11:46

 

Tuner A is DiSEqC motor for many positions.

 

Tuner B is loopthrough to tuner A.

 

Internal or extrernal loopthrough?


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: vreemde tuner-pericelen #116 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 11 April 2023 - 12:05

It is a Duo2 with 2x DVB-S2 twin tuner modules... so loop is internal.

 

But in Rob's config above Tuner B is disabled... so that tuner is not involved at all.


Re: vreemde tuner-pericelen #117 Dimitrij

  • PLi® Core member
  • 10,299 posts

+347
Excellent

Posted 11 April 2023 - 12:59

It is a Duo2 with 2x DVB-S2 twin tuner modules... so loop is internal.

 

But in Rob's config above Tuner B is disabled... so that tuner is not involved at all.

That is, the loop is not used?

And still there is a timer conflict error?

This is good, because in the case of a loop it is very difficult to understand the debug log, the loop makes the task very difficult.

 

Need full log.

"Restart enigma in debug mode"and perform actions that lead to a conflict of timers, it is advisable to periodically open the channel selector and assign timers from it.


Edited by Dimitrij, 11 April 2023 - 13:07.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: vreemde tuner-pericelen #118 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 11 April 2023 - 18:01

So Rob's config above is more or less the same as I explained, except, no loopthrough on tuner B.

I made the config on PLi as simple as possible, but it still does show the same bug. Adding 19.2E to Tuner C (and or D) prevents E2 from using 19.2E from tuner A.

 

A full log will take some time, as I'l need to switch to PLi again, and this is my 'household box'. The same applies to giving my feeds to my ET8k, to see if it suffers from the same issue.


Re: vreemde tuner-pericelen #119 Dimitrij

  • PLi® Core member
  • 10,299 posts

+347
Excellent

Posted 11 April 2023 - 19:11

 

So Rob's config above is more or less the same as I explained, except, no loopthrough on tuner B.

I made the config on PLi as simple as possible, but it still does show the same bug. Adding 19.2E to Tuner C (and or D) prevents E2 from using 19.2E from tuner A.

 

A full log will take some time, as I'l need to switch to PLi again, and this is my 'household box'. The same applies to giving my feeds to my ET8k, to see if it suffers from the same issue.

 

You can get a log from the current image for now, if it's openVIX. I don’t have similar equipment and I can’t simulate such a situation in any way. All my receivers, where there are many tuners, are FBC.

 

And my old Ultimo, with the same two dual tuners, died.


Edited by Dimitrij, 11 April 2023 - 19:13.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: vreemde tuner-pericelen #120 Dimitrij

  • PLi® Core member
  • 10,299 posts

+347
Excellent

Posted 12 April 2023 - 12:42

And need answers:
 

cat /proc/bus/nim_sockets

 

grep -r "" /proc/stb

 


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Back to [NL] Gebruikersondersteuning

17 user(s) are reading this topic

0 members, 17 guests, 0 anonymous users

  1. Forums
  2. → PLi® Support
  3. → [NL] Gebruikersondersteuning