Jump to content


Photo

Unicable / simultaneous recordings


  • Please log in to reply
342 replies to this topic

#1 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 19 September 2018 - 11:41

Solo 4K, Unicable LNB, tested on 28.2 East.
Select 2 (or more) programs on different transponders that start simultaneously.
Set timers to record those programs.
Put box in standby.

Result:
Recordings are often zero length.
If you zap to any of the programs while record is in progress the "tune failed" message shows.
Delete/stop one recording, the other recording will start.

< 69796.350> [eDVBFrontend] opening frontend 0
< 69796.351> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0xe3, guard_offset 0
< 69796.351> **** Tuning JESS
< 69796.351> **** frequency_mhz: 10847
< 69796.351> **** lo_mhz: 9750
< 69796.351> **** T: 997
< 69796.351> **** position: 0
< 69796.351> **** ub: 0
< 69796.351> **** mode: 0
< 69796.351> **** JESS: 70 03 e5 00
7003e500(?)
< 69796.351> [eDVBFrontend] opening frontend 3
< 69796.351> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x28f6, guard_offset 0
< 69796.351> **** Tuning JESS
< 69796.351> **** frequency_mhz: 10714
< 69796.351> **** lo_mhz: 9750
< 69796.351> **** T: 864
< 69796.351> **** position: 0
< 69796.351> **** ub: 1
< 69796.351> **** mode: 2
< 69796.351> **** JESS: 70 0b 60 02
700b6002(?)
< 69796.352> [eDVBFrontend] opening frontend 4
< 69796.352> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x419e, guard_offset 0
< 69796.352> **** Tuning JESS
< 69796.352> **** frequency_mhz: 11126
< 69796.352> **** lo_mhz: 9750
< 69796.352> **** T: 1276
< 69796.352> **** position: 0
< 69796.352> **** ub: 2
< 69796.352> **** mode: 0
< 69796.352> **** JESS: 70 14 fc 00

How is the LNB supposed to cope receiving those commands just milliseconds apart?



Re: Unicable / simultaneous recordings #2 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 19 September 2018 - 12:21

I have exactly the same issue using the DUO2 and a simple 4-SCR Unicabe Inverto LNB, and it has always been like that.
My work-around is simply never to start recordings at the same time.

Re: Unicable / simultaneous recordings #3 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 19 September 2018 - 13:16

I have exactly the same issue using the DUO2 and a simple 4-SCR Unicabe Inverto LNB, and it has always been like that.
My work-around is simply never to start recordings at the same time.

Great. So what is supposed to happen when the recordings are set automatically? Don't bother to answer that, I'm joking of course. Anyway obviously not just limited to FBC tuners then.



Re: Unicable / simultaneous recordings #4 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 19 September 2018 - 13:23

Correct. I have been using Unicable for years (IIRC starting with the DUO) and it has always been like that.

Re: Unicable / simultaneous recordings #5 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 19 September 2018 - 13:25

I have exactly the same issue using the DUO2 and a simple 4-SCR Unicabe Inverto LNB, and it has always been like that.
My work-around is simply never to start recordings at the same time.

Great. So what is supposed to happen when the recordings are set automatically? Don't bother to answer that, I'm joking of course. Anyway obviously not just limited to FBC tuners then.

No joking: I go through all my timers at least once a week to check this and "correct" them when required.

Re: Unicable / simultaneous recordings #6 Erik Slagter

  • PLi® Core member
  • 46,960 posts

+541
Excellent

Posted 19 September 2018 - 15:42

This sounds like the usual problem where SCR LNB's need to "boot" after receiving power. I've been using SCR switches and never saw this issue.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Unicable / simultaneous recordings #7 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 19 September 2018 - 15:52

No. It is not that. I'm well aware of the LNB being a digital device that needs to boot but it is nothing to do with that. I'm using the SatalliteEquipmentControl plugin. There is a 1.5 second delay programmed in there, which is plenty for the LNB to wake up. Anyway there is another box using the LNB so I know the LNB is already powered up.

 

Anyway if it were that it would also fail on single records and that is not the case. The failure only happens on multiple recordings with simultaneous start times.



Re: Unicable / simultaneous recordings #8 Erik Slagter

  • PLi® Core member
  • 46,960 posts

+541
Excellent

Posted 19 September 2018 - 19:52

If we can find out what the exact conditions are, I guess we could also make a workaround. As long as it doesn't mean unneccessary delays for SCR switch users or regressions.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Unicable / simultaneous recordings #9 Abu Baniaz

  • PLi® Contributor
  • 2,439 posts

+62
Good

Posted 19 September 2018 - 20:17

I flashed 18/9/18 PLI image on solo 4k. It is connected to an inverto Unicable 2 LNB pointing to 28.2

Signal wire attached to tuner A.

No signal wire attached to tuner B.

Tuners B-H set as connected to Tuner A.

All have unique SCR.

 

I set a timer about 10 minutes ahead for BBC 1 HD

I set another timer to match the times for Channel 5 HD

 

Put the receiver in standby.

Wake it up  while it is recording

You get a tune failed message.

Stop one of the recordings and the tune failed message clears

 

Only plugin installed is AutoBouquetsMaker.

 

The above fault is the same as Huevos is experiencing in OpenVix

 

I repeated the test on a TM Nano 3T combo (using OpenVix). It does not have FBC tuners, so both satellite tuners had a signal wire attached. There was no fault.



Re: Unicable / simultaneous recordings #10 Abu Baniaz

  • PLi® Contributor
  • 2,439 posts

+62
Good

Posted 19 September 2018 - 20:34

Slightly different test to above, signal wire attached to tuner B and tuner config set as appropriate. C-H still set as connected to A, had same problem.



Re: Unicable / simultaneous recordings #11 Abu Baniaz

  • PLi® Contributor
  • 2,439 posts

+62
Good

Posted 19 September 2018 - 20:37

Changed the test, Tuners A&B have signal wires connected. C-H set as FBC automatic.

 

Same problem



Re: Unicable / simultaneous recordings #12 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 19 September 2018 - 21:18

@Abu, thanks for confirming.

 

@Erik, not sure how to avoid a small time delay.

 

I attached the spectrum analyser to the same cable and all the correct SCRs are active but for some reason what each SCR is tuned to seems to be mixed up.

 

e.g. Tuner A = SCR1, Tuner B = SCR2. Tuner A is supposed to be recording BBC1 (according to the log) and Tuner B is supposed to be recording Channel5. But in reality they are mixed up.

 

So I checked the log and the frontend number changes. FIrst it is trying to tune 10847 on one frontend, then a fraction later it is tuning the same transponder on a different frontend.

< 66446.685> [eDVBChannel] OURSTATE: failed, retune
< 66446.685> [eDVBFrontend] (0)tune
< 66446.691> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0xe3, guard_offset 0
< 66446.691> **** Tuning JESS
< 66446.691> **** frequency_mhz: 10847
< 66446.691> **** lo_mhz: 9750
< 66446.691> **** T: 997
< 66446.691> **** position: 0
< 66446.691> **** ub: 0
< 66446.691> **** mode: 0
< 66446.691> **** JESS: 70 03 e5 00
< 66446.691> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 66446.691> [eDVBFrontend] prepare_sat System 1 Freq 10847000 Pol 1 SR 23000000 INV 2 FEC 2 orbpos 282 system 1 modulation 2 pilot 2, rolloff 1, is_id -1, pls_mode 1, pls_code 0
< 66446.691> [eDVBFrontend] tuning to 1211 mhz
< 66446.691> [eDVBChannel] OURSTATE: tuning
< 66446.691> [eDVBServicePMTHandler] tune failed.
< 66446.691> [eDVBServiceRecord] RECORD service event 1
< 66446.691> [eDVBServiceRecord] record failed to tune
< 66446.692> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 66446.692> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
< 66446.692> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 802 current: ffffffff
< 66446.692> [eDVBServicePMTHandler] incorrect namespace. expected: 2 current: ffffffff
< 66446.692> [eDVBChannel] OURSTATE: failed, retune


Re: Unicable / simultaneous recordings #13 WanWizard

  • PLi® Core member
  • 68,605 posts

+1,739
Excellent

Posted 19 September 2018 - 21:21

Sounds like a command queue is needed so the commands are processed sequentially and in the correct order. It is then also possible to inject a "delay" command in the queue to pause when needed, instead of doing something hardcoded.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Unicable / simultaneous recordings #14 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 19 September 2018 - 21:22

Right now I am guessing it is a timing issue and the commands are being sent too close together or overlapping.

 

I am happy to try any test anyone suggests.



Re: Unicable / simultaneous recordings #15 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 19 September 2018 - 21:48

Also this is wrong. It should say ONID but says namespace.

< 66446.692> [eDVBServicePMTHandler] incorrect namespace. expected: 2 current: ffffffff


Re: Unicable / simultaneous recordings #16 Erik Slagter

  • PLi® Core member
  • 46,960 posts

+541
Excellent

Posted 20 September 2018 - 09:42

I don't have any knowledge of where that comes from.

 

What I do have knowledge of is Unicable and JESS. Unicable is almost the same implementation that DVBAdenin supplied to DMM years ago, which imho, is "suboptimal" and probably is also the base for the code in "Open"ViX. The JESS implementation in OpenPLi is from scratch (I am sure you all still know), by myself.

 

So my first question is here, when does this problem appear, is it with Unicable, JESS, or both?

 

My first impression would be that the actual switching hardware might be acting too slow (either the hardware or the driver), but I think we can rule that out because it all works flawlessly on both Unicable and JESS switches.

 

Huevos, if you start multiple recording, I'd expect multiple entries in the log, can you collect them and link them to the recordings you're making?


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Unicable / simultaneous recordings #17 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 20 September 2018 - 13:47

Erik, the Unicable/Jess code in OpenViX is PLi version. Originally it was Adenin version but I switched it to the PLi version (your version). If you remember I patch Adenin version to PLi but it was rejected.

 

Remove Adenin version: https://github.com/O...519d0ab55099cb4

Add OpenPLi version: https://github.com/O...519d0ab55099cb4

 

So with regard to Unicable/Jess our code (and debug) is identical to OpenPLi.

 

The LNB I am using for the test is Inverto IDLU-32UL40-UNBOO-OPP, format JESS. This is one of the most common Unicable LNBs.

 

My current tuner setup is 28.2 East. Cable to tuner A and linked to tuners D-H. SCRs 1-6. Tuners B+C are linked to my multisat setup.

 

Abu is using the same LNB. He tested in PLi. Dish cable to tuner A, and internally linked to tuners B-H. Tested on OpenPLi. Bug exists.

 

Rob is using an Inverto, but not format JESS. Tested on OpenPLi. Bug exists.



Re: Unicable / simultaneous recordings #18 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 20 September 2018 - 14:54

Here is a log.

 

Starting two recordings with the receiver in standby. LNB already has voltage because another STB is active.

 

Record BBC One HD, 28.2E, 10847 V.

Record Channel 5 HD, 28.2E, 10964 H.

 

Both recordings are zero length.

 

Note: enigma knows something is wrong because there are recurring retune events.

< 69234.095> [RecordTimer] activating state 1
< 69234.096> [RecordTimer] Found enough free space to record
< 69234.097> [RecordTimer] Filename calculated as: '/media/hdd/movie/20180920 1512 - BBC One HD - Chase the Case'
< 69234.097> [Navigation] recording service: 1:0:19:1B1D:802:2:11A0000:0:0:0:
< 69234.098> [eDVBResourceManager] allocate channel.. 0802:0002
< 69234.098> [eDVBFrontend] opening frontend 0
< 69234.102> [eDVBFrontend] (0)tune
< 69234.102> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0xe3, guard_offset 0
< 69234.102> **** Tuning JESS
< 69234.102> **** frequency_mhz: 10847
< 69234.102> **** lo_mhz: 9750
< 69234.102> **** T: 997
< 69234.102> **** position: 0
< 69234.102> **** ub: 0
< 69234.102> **** mode: 0
< 69234.102> **** JESS: 70 03 e5 00
< 69234.102> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 69234.103> [eDVBFrontend] prepare_sat System 1 Freq 10847000 Pol 1 SR 23000000 INV 2 FEC 2 orbpos 282 system 1 modulation 2 pilot 2, rolloff 1, is_id -1, pls_mode 1, pls_code 0
< 69234.103> [eDVBFrontend] tuning to 1211 mhz
< 69234.103> [eDVBChannel] OURSTATE: tuning
< 69234.103> [eDVBServicePMTHandler] allocate Channel: res 0
< 69234.103> [eDVBCIInterfaces] addPMTHandler 1:0:19:1B1D:802:2:11A0000:0:0:0:
< 69234.103> [eDVBChannel] getDemux cap=00
< 69234.103> [eDVBResourceManager] allocate demux cap=00
< 69234.103> [eDVBResourceManager] allocating demux adapter=0, demux=0, source=1 fesource=0
< 69234.103> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 69234.104> [eEPGCache] saveEventToFile epg event id d0d6
< 69234.104> [RecordTimer] prepare ok, waiting for begin
< 69234.106> [Trashcan] probing folders
< 69234.108> [Trashcan] found following trashcan's: ['/media/hdd/.Trash', '/media/hdd/movie/.Trash']
< 69234.108> [Trashcan] looking in trashcan /media/hdd/.Trash
< 69234.108> [Trashcan] /media/hdd/.Trash: Size: 0
< 69234.108> [Trashcan] /media/hdd/.Trash: Size now: 0
< 69234.108> [Trashcan] looking in trashcan /media/hdd/movie/.Trash
< 69234.109> [Trashcan] /media/hdd/movie/.Trash: Size: 852676492
< 69234.110> [Trashcan] /media/hdd/movie/.Trash: Size now: 852676492
< 69234.111> [RecordTimer] activating state 1
< 69234.112> [RecordTimer] Found enough free space to record
< 69234.113> [RecordTimer] Filename calculated as: '/media/hdd/movie/20180920 1512 - Channel 5 HD - The Nanny Betrayal'
< 69234.113> [Navigation] recording service: 1:0:19:1E46:809:2:11A0000:0:0:0:
< 69234.113> [eDVBResourceManager] allocate channel.. 0809:0002
< 69234.113> [eDVBResourceManager] available channel.. 0802:0002
< 69234.113> [eDVBFrontend] opening frontend 3
< 69234.116> [eDVBFrontend] (3)tune
< 69234.116> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x2935, guard_offset 0
< 69234.116> **** Tuning JESS
< 69234.116> **** frequency_mhz: 10964
< 69234.116> **** lo_mhz: 9750
< 69234.116> **** T: 1114
< 69234.116> **** position: 0
< 69234.116> **** ub: 1
< 69234.116> **** mode: 2
< 69234.116> **** JESS: 70 0c 5a 02
< 69234.116> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 69234.116> [eDVBFrontend] prepare_sat System 0 Freq 10964250 Pol 0 SR 22000000 INV 2 FEC 4 orbpos 282 system 0 modulation 1 pilot 2, rolloff 0, is_id -1, pls_mode 1, pls_code 0
< 69234.116> [eDVBFrontend] tuning to 1421 mhz
< 69234.116> [eDVBChannel] OURSTATE: tuning
< 69234.116> [eDVBServicePMTHandler] allocate Channel: res 0
< 69234.116> [eDVBCIInterfaces] addPMTHandler 1:0:19:1E46:809:2:11A0000:0:0:0:
< 69234.116> [eDVBChannel] getDemux cap=00
< 69234.116> [eDVBResourceManager] allocate demux cap=00
< 69234.116> [eDVBResourceManager] allocating demux adapter=0, demux=1, source=-1 fesource=3
< 69234.116> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 69234.117> [eEPGCache] saveEventToFile epg event id 9119
< 69234.117> [RecordTimer] prepare ok, waiting for begin
< 69234.117> [Trashcan] Cleanup already running
< 69234.119> [Task] job Components.Task.Job name=Cleaning Trashes #tasks=1 completed with [] in None
< 69234.121> [eDVBFrontend] set static current limiting
< 69234.121> [eDVBFrontend] set static current limiting
< 69234.122> [eDVBFrontend] invalidate current switch params
< 69234.122> [eDVBFrontend] invalidate current switch params
< 69234.122> [eDVBFrontend] setVoltage 1
< 69234.123> [eDVBFrontend] setVoltage 1
< 69234.123> [eDVBFrontend] sleep 1500ms
< 69234.123> [eDVBFrontend] sleep 1500ms
< 69235.623> [eDVBFrontend] setVoltage 2
< 69235.625> [eDVBFrontend] setVoltage 2
< 69235.625> [eDVBFrontend] setTone 0
< 69235.626> [eDVBFrontend] setTone 0
< 69235.627> [eDVBFrontend] sleep 75ms
< 69235.627> [eDVBFrontend] sleep 75ms
< 69235.758> [eDVBFrontend] sendDiseqc: 7003e500(?)
< 69235.814> [eDVBFrontend] sendDiseqc: 700c5a02(?)
< 69235.814> [eDVBFrontend] sleep 100ms
< 69235.815> [eDVBFrontend] sleep 100ms
< 69235.914> [eDVBFrontend] setVoltage 1
< 69235.915> [eDVBFrontend] update current switch params
< 69235.915> [eDVBFrontend] startTuneTimeout 5000
< 69235.915> [eDVBFrontend] setFrontend 1
< 69235.915> [eDVBFrontend] setting frontend 0
< 69235.922> [eDVBFrontend] (0)fe event: status 0, inversion off, m_tuning 1
< 69235.922> [eDVBFrontend] setVoltage 1
< 69235.923> [eDVBFrontend] sleep 500ms
< 69235.923> [eDVBFrontend] update current switch params
< 69235.923> [eDVBFrontend] startTuneTimeout 5000
< 69235.923> [eDVBFrontend] setFrontend 1
< 69235.923> [eDVBFrontend] setting frontend 3
< 69235.926> [eDVBFrontend] (3)fe event: status 0, inversion off, m_tuning 1
< 69235.927> [eDVBFrontend] sleep 500ms
< 69235.970> [eDVBFrontend] (3)fe event: status 7, inversion off, m_tuning 2
< 69235.970> [eDVBFrontend] (0)fe event: status 7, inversion off, m_tuning 2
< 69236.423> [eDVBFrontend] set dynamic current limiting
< 69236.427> [eDVBFrontend] set dynamic current limiting
< 69240.915> [eDVBChannel] OURSTATE: failed, retune
< 69240.915> [eDVBFrontend] (0)tune
< 69240.915> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0xe3, guard_offset 0
< 69240.915> **** Tuning JESS
< 69240.915> **** frequency_mhz: 10847
< 69240.915> **** lo_mhz: 9750
< 69240.915> **** T: 997
< 69240.915> **** position: 0
< 69240.915> **** ub: 0
< 69240.915> **** mode: 0
< 69240.915> **** JESS: 70 03 e5 00
< 69240.915> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 69240.915> [eDVBFrontend] prepare_sat System 1 Freq 10847000 Pol 1 SR 23000000 INV 2 FEC 2 orbpos 282 system 1 modulation 2 pilot 2, rolloff 1, is_id -1, pls_mode 1, pls_code 0
< 69240.915> [eDVBFrontend] tuning to 1211 mhz
< 69240.915> [eDVBChannel] OURSTATE: tuning
< 69240.915> [eDVBServicePMTHandler] tune failed.
< 69240.915> [eDVBServiceRecord] RECORD service event 1
< 69240.915> [eDVBServiceRecord] record failed to tune
< 69240.916> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 69240.916> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
< 69240.916> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 802 current: ffffffff
< 69240.916> [eDVBServicePMTHandler] incorrect namespace. expected: 2 current: ffffffff
< 69240.916> [eDVBFrontend] set static current limiting
< 69240.916> [eDVBFrontend] invalidate current switch params
< 69240.916> [eDVBFrontend] set sequence pos 3
< 69240.916> [eDVBFrontend] setVoltage 2
< 69240.917> [eDVBFrontend] setTone 0
< 69240.917> [eDVBFrontend] sleep 75ms
< 69240.923> [eDVBChannel] OURSTATE: failed, retune
< 69240.923> [eDVBFrontend] (3)tune
< 69240.924> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x2935, guard_offset 0
< 69240.924> **** Tuning JESS
< 69240.924> **** frequency_mhz: 10964
< 69240.924> **** lo_mhz: 9750
< 69240.924> **** T: 1114
< 69240.924> **** position: 0
< 69240.924> **** ub: 1
< 69240.924> **** mode: 2
< 69240.924> **** JESS: 70 0c 5a 02
< 69240.924> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 69240.924> [eDVBFrontend] prepare_sat System 0 Freq 10964250 Pol 0 SR 22000000 INV 2 FEC 4 orbpos 282 system 0 modulation 1 pilot 2, rolloff 0, is_id -1, pls_mode 1, pls_code 0
< 69240.924> [eDVBFrontend] tuning to 1421 mhz
< 69240.924> [eDVBChannel] OURSTATE: tuning
< 69240.924> [eDVBServicePMTHandler] tune failed.
< 69240.924> [eDVBServiceRecord] RECORD service event 1
< 69240.924> [eDVBServiceRecord] record failed to tune
< 69240.924> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 69240.924> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
< 69240.924> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 809 current: ffffffff
< 69240.924> [eDVBServicePMTHandler] incorrect namespace. expected: 2 current: ffffffff
< 69240.924> [eDVBFrontend] set static current limiting
< 69240.924> [eDVBFrontend] invalidate current switch params
< 69240.924> [eDVBFrontend] set sequence pos 3
< 69240.924> [eDVBFrontend] setVoltage 2
< 69240.925> [eDVBFrontend] setTone 0
< 69240.926> [eDVBFrontend] sleep 75ms
< 69241.048> [eDVBFrontend] sendDiseqc: 7003e500(?)
< 69241.104> [eDVBFrontend] sendDiseqc: 700c5a02(?)
< 69241.104> [eDVBFrontend] sleep 100ms
< 69241.104> [eDVBFrontend] sleep 100ms
< 69241.204> [eDVBFrontend] setVoltage 1
< 69241.205> [eDVBFrontend] setVoltage 1
< 69241.206> [eDVBFrontend] update current switch params
< 69241.206> [eDVBFrontend] update current switch params
< 69241.206> [eDVBFrontend] startTuneTimeout 5000
< 69241.206> [eDVBFrontend] startTuneTimeout 5000
< 69241.206> [eDVBFrontend] setFrontend 1
< 69241.206> [eDVBFrontend] setting frontend 0
< 69241.206> [eDVBFrontend] (0)fe event: status 0, inversion off, m_tuning 1
< 69241.206> [eDVBFrontend] setFrontend 1
< 69241.206> [eDVBFrontend] setting frontend 3
< 69241.206> [eDVBFrontend] sleep 500ms
< 69241.206> [eDVBFrontend] (3)fe event: status 0, inversion off, m_tuning 1
< 69241.206> [eDVBFrontend] sleep 500ms
< 69241.250> [eDVBFrontend] (0)fe event: status 7, inversion off, m_tuning 2
< 69241.250> [eDVBFrontend] (3)fe event: status 7, inversion off, m_tuning 2
< 69241.706> [eDVBFrontend] set dynamic current limiting
< 69241.707> [eDVBFrontend] set dynamic current limiting
< 69246.206> [eDVBChannel] OURSTATE: failed, retune
< 69246.206> [eDVBFrontend] (0)tune
< 69246.206> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0xe3, guard_offset 0
< 69246.206> **** Tuning JESS
< 69246.206> **** frequency_mhz: 10847
< 69246.206> **** lo_mhz: 9750
< 69246.206> **** T: 997
< 69246.206> **** position: 0
< 69246.206> **** ub: 0
< 69246.206> **** mode: 0
< 69246.206> **** JESS: 70 03 e5 00
< 69246.206> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 69246.206> [eDVBFrontend] prepare_sat System 1 Freq 10847000 Pol 1 SR 23000000 INV 2 FEC 2 orbpos 282 system 1 modulation 2 pilot 2, rolloff 1, is_id -1, pls_mode 1, pls_code 0
< 69246.206> [eDVBFrontend] tuning to 1211 mhz
< 69246.206> [eDVBChannel] OURSTATE: tuning
< 69246.206> [eDVBServicePMTHandler] tune failed.
< 69246.206> [eDVBServiceRecord] RECORD service event 1
< 69246.206> [eDVBServiceRecord] record failed to tune
< 69246.207> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 69246.207> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
< 69246.207> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 802 current: ffffffff
< 69246.207> [eDVBServicePMTHandler] incorrect namespace. expected: 2 current: ffffffff
< 69246.207> [eDVBChannel] OURSTATE: failed, retune
< 69246.207> [eDVBFrontend] (3)tune
< 69246.207> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x2935, guard_offset 0
< 69246.207> **** Tuning JESS
< 69246.207> **** frequency_mhz: 10964
< 69246.207> **** lo_mhz: 9750
< 69246.207> **** T: 1114
< 69246.207> **** position: 0
< 69246.207> **** ub: 1
< 69246.207> **** mode: 2
< 69246.207> **** JESS: 70 0c 5a 02
< 69246.207> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 69246.207> [eDVBFrontend] prepare_sat System 0 Freq 10964250 Pol 0 SR 22000000 INV 2 FEC 4 orbpos 282 system 0 modulation 1 pilot 2, rolloff 0, is_id -1, pls_mode 1, pls_code 0
< 69246.207> [eDVBFrontend] tuning to 1421 mhz
< 69246.207> [eDVBChannel] OURSTATE: tuning
< 69246.207> [eDVBServicePMTHandler] tune failed.
< 69246.207> [eDVBServiceRecord] RECORD service event 1
< 69246.207> [eDVBServiceRecord] record failed to tune
< 69246.207> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 69246.207> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
< 69246.207> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 809 current: ffffffff
< 69246.207> [eDVBServicePMTHandler] incorrect namespace. expected: 2 current: ffffffff
< 69246.207> [eDVBFrontend] set static current limiting
< 69246.208> [eDVBFrontend] set static current limiting
< 69246.208> [eDVBFrontend] invalidate current switch params
< 69246.208> [eDVBFrontend] invalidate current switch params
< 69246.208> [eDVBFrontend] set sequence pos 3
< 69246.208> [eDVBFrontend] set sequence pos 3
< 69246.208> [eDVBFrontend] setVoltage 2
< 69246.209> [eDVBFrontend] setVoltage 2
< 69246.209> [eDVBFrontend] setTone 0
< 69246.210> [eDVBFrontend] setTone 0
< 69246.211> [eDVBFrontend] sleep 75ms
< 69246.211> [eDVBFrontend] sleep 75ms
< 69246.342> [eDVBFrontend] sendDiseqc: 7003e500(?)
< 69246.398> [eDVBFrontend] sendDiseqc: 700c5a02(?)
< 69246.399> [eDVBFrontend] sleep 100ms
< 69246.399> [eDVBFrontend] sleep 100ms
< 69246.499> [eDVBFrontend] setVoltage 1
< 69246.500> [eDVBFrontend] setVoltage 1
< 69246.501> [eDVBFrontend] update current switch params
< 69246.501> [eDVBFrontend] update current switch params
< 69246.501> [eDVBFrontend] startTuneTimeout 5000
< 69246.501> [eDVBFrontend] startTuneTimeout 5000
< 69246.501> [eDVBFrontend] setFrontend 1
< 69246.501> [eDVBFrontend] setting frontend 0
< 69246.501> [eDVBFrontend] (0)fe event: status 0, inversion off, m_tuning 1
< 69246.501> [eDVBFrontend] setFrontend 1
< 69246.501> [eDVBFrontend] setting frontend 3
< 69246.501> [eDVBFrontend] sleep 500ms
< 69246.501> [eDVBFrontend] (3)fe event: status 0, inversion off, m_tuning 1
< 69246.501> [eDVBFrontend] sleep 500ms
< 69246.550> [eDVBFrontend] (0)fe event: status 7, inversion off, m_tuning 2
< 69246.550> [eDVBFrontend] (3)fe event: status 7, inversion off, m_tuning 2
< 69247.001> [eDVBFrontend] set dynamic current limiting
< 69247.002> [eDVBFrontend] set dynamic current limiting
< 69251.501> [eDVBChannel] OURSTATE: failed, retune
< 69251.501> [eDVBFrontend] (0)tune
< 69251.501> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0xe3, guard_offset 0
< 69251.501> **** Tuning JESS
< 69251.501> **** frequency_mhz: 10847
< 69251.501> **** lo_mhz: 9750
< 69251.501> **** T: 997
< 69251.501> **** position: 0
< 69251.501> **** ub: 0
< 69251.501> **** mode: 0
< 69251.501> **** JESS: 70 03 e5 00
< 69251.501> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 69251.501> [eDVBFrontend] prepare_sat System 1 Freq 10847000 Pol 1 SR 23000000 INV 2 FEC 2 orbpos 282 system 1 modulation 2 pilot 2, rolloff 1, is_id -1, pls_mode 1, pls_code 0
< 69251.501> [eDVBFrontend] tuning to 1211 mhz
< 69251.501> [eDVBChannel] OURSTATE: tuning
< 69251.501> [eDVBServicePMTHandler] tune failed.
< 69251.501> [eDVBServiceRecord] RECORD service event 1
< 69251.501> [eDVBServiceRecord] record failed to tune
< 69251.502> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 69251.502> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
< 69251.502> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 802 current: ffffffff
< 69251.502> [eDVBServicePMTHandler] incorrect namespace. expected: 2 current: ffffffff
< 69251.502> [eDVBChannel] OURSTATE: failed, retune
< 69251.502> [eDVBFrontend] (3)tune
< 69251.502> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x2935, guard_offset 0
< 69251.502> **** Tuning JESS
< 69251.502> **** frequency_mhz: 10964
< 69251.502> **** lo_mhz: 9750
< 69251.502> **** T: 1114
< 69251.502> **** position: 0
< 69251.502> **** ub: 1
< 69251.502> **** mode: 2
< 69251.502> **** JESS: 70 0c 5a 02
< 69251.502> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 69251.502> [eDVBFrontend] prepare_sat System 0 Freq 10964250 Pol 0 SR 22000000 INV 2 FEC 4 orbpos 282 system 0 modulation 1 pilot 2, rolloff 0, is_id -1, pls_mode 1, pls_code 0
< 69251.502> [eDVBFrontend] tuning to 1421 mhz
< 69251.502> [eDVBChannel] OURSTATE: tuning
< 69251.502> [eDVBServicePMTHandler] tune failed.
< 69251.502> [eDVBServiceRecord] RECORD service event 1
< 69251.502> [eDVBServiceRecord] record failed to tune
< 69251.502> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 69251.502> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
< 69251.502> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 809 current: ffffffff
< 69251.502> [eDVBServicePMTHandler] incorrect namespace. expected: 2 current: ffffffff
< 69251.502> [eDVBFrontend] set static current limiting
< 69251.503> [eDVBFrontend] set static current limiting
< 69251.503> [eDVBFrontend] invalidate current switch params
< 69251.503> [eDVBFrontend] invalidate current switch params
< 69251.503> [eDVBFrontend] set sequence pos 3
< 69251.503> [eDVBFrontend] set sequence pos 3
< 69251.503> [eDVBFrontend] setVoltage 2
< 69251.504> [eDVBFrontend] setVoltage 2
< 69251.505> [eDVBFrontend] setTone 0
< 69251.505> [eDVBFrontend] setTone 0
< 69251.506> [eDVBFrontend] sleep 75ms
< 69251.506> [eDVBFrontend] sleep 75ms
< 69251.637> [eDVBFrontend] sendDiseqc: 7003e500(?)
< 69251.693> [eDVBFrontend] sendDiseqc: 700c5a02(?)
< 69251.693> [eDVBFrontend] sleep 100ms
< 69251.693> [eDVBFrontend] sleep 100ms
< 69251.793> [eDVBFrontend] setVoltage 1
< 69251.794> [eDVBFrontend] setVoltage 1
< 69251.794> [eDVBFrontend] update current switch params
< 69251.794> [eDVBFrontend] update current switch params
< 69251.794> [eDVBFrontend] startTuneTimeout 5000
< 69251.794> [eDVBFrontend] startTuneTimeout 5000
< 69251.794> [eDVBFrontend] setFrontend 1
< 69251.794> [eDVBFrontend] setting frontend 0
< 69251.794> [eDVBFrontend] (0)fe event: status 0, inversion off, m_tuning 1
< 69251.794> [eDVBFrontend] setFrontend 1
< 69251.794> [eDVBFrontend] setting frontend 3
< 69251.794> [eDVBFrontend] sleep 500ms
< 69251.795> [eDVBFrontend] (3)fe event: status 0, inversion off, m_tuning 1
< 69251.795> [eDVBFrontend] sleep 500ms
< 69251.840> [eDVBFrontend] (0)fe event: status 7, inversion off, m_tuning 2
< 69251.840> [eDVBFrontend] (3)fe event: status 7, inversion off, m_tuning 2
< 69252.295> [eDVBFrontend] set dynamic current limiting
< 69252.295> [eDVBFrontend] set dynamic current limiting
< 69254.118> [RecordTimer] activating state 2
< 69254.120> [RecordTimer] start recording on tuner: A
< 69254.120> [RecordTimer] activating state 2
< 69254.121> [RecordTimer] start recording on tuner: D
< 69256.794> [eDVBChannel] OURSTATE: failed, retune
< 69256.794> [eDVBFrontend] (0)tune
< 69256.795> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0xe3, guard_offset 0
< 69256.795> **** Tuning JESS
< 69256.795> **** frequency_mhz: 10847
< 69256.795> **** lo_mhz: 9750
< 69256.795> **** T: 997
< 69256.795> **** position: 0
< 69256.795> **** ub: 0
< 69256.795> **** mode: 0
< 69256.795> **** JESS: 70 03 e5 00
< 69256.795> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 69256.795> [eDVBFrontend] prepare_sat System 1 Freq 10847000 Pol 1 SR 23000000 INV 2 FEC 2 orbpos 282 system 1 modulation 2 pilot 2, rolloff 1, is_id -1, pls_mode 1, pls_code 0
< 69256.795> [eDVBFrontend] tuning to 1211 mhz
< 69256.795> [eDVBChannel] OURSTATE: tuning
< 69256.795> [eDVBServicePMTHandler] tune failed.
< 69256.795> [eDVBServiceRecord] RECORD service event 1
< 69256.795> [eDVBServiceRecord] record failed to tune
< 69256.795> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 69256.795> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
< 69256.795> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 802 current: ffffffff
< 69256.795> [eDVBServicePMTHandler] incorrect namespace. expected: 2 current: ffffffff
< 69256.795> [eDVBChannel] OURSTATE: failed, retune
< 69256.795> [eDVBFrontend] (3)tune
< 69256.795> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x2935, guard_offset 0
< 69256.795> **** Tuning JESS
< 69256.795> **** frequency_mhz: 10964
< 69256.795> **** lo_mhz: 9750
< 69256.795> **** T: 1114
< 69256.795> **** position: 0
< 69256.795> **** ub: 1
< 69256.795> **** mode: 2
< 69256.795> **** JESS: 70 0c 5a 02
< 69256.796> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 69256.796> [eDVBFrontend] prepare_sat System 0 Freq 10964250 Pol 0 SR 22000000 INV 2 FEC 4 orbpos 282 system 0 modulation 1 pilot 2, rolloff 0, is_id -1, pls_mode 1, pls_code 0
< 69256.796> [eDVBFrontend] tuning to 1421 mhz
< 69256.796> [eDVBChannel] OURSTATE: tuning
< 69256.796> [eDVBServicePMTHandler] tune failed.
< 69256.796> [eDVBServiceRecord] RECORD service event 1
< 69256.796> [eDVBServiceRecord] record failed to tune
< 69256.796> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 69256.796> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
< 69256.796> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 809 current: ffffffff
< 69256.796> [eDVBServicePMTHandler] incorrect namespace. expected: 2 current: ffffffff

.


Edited by Huevos, 20 September 2018 - 14:56.


Re: Unicable / simultaneous recordings #19 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 20 September 2018 - 15:05

If you look here "< 69246.206>" you can see the retune events are sent to the LNB just 1 millisecond apart. Surely this cannot be correct.



Re: Unicable / simultaneous recordings #20 Erik Slagter

  • PLi® Core member
  • 46,960 posts

+541
Excellent

Posted 20 September 2018 - 16:37

That enigma2 subsystem I have no knowledge of. Enigma gets a failed event from DVB and will retry to tune, that part I understand ;)

 

But can you confirm the JESS tuning is correct (frequency and user band is correct)?

 

BTW Unicable != JESS. Unicable is SCR and JESS is SCR. The Unicable code in enigma2 is not from me, although I'd probably have to write it from scratch, just as the JESS code.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users