342 replies to this topic

[Erik Slagter]

Yes, that is what I say. 1x FBC and 1x standard tuner.

 

There is no such thing as a "dual" FBC tuner, it's marketing speak.

 

A single FBC tuner always has:

 

- one card or "complex"

- two inputs

- eight demodulators

 

The Lunix3-4k has one of these, the Ultimo4k two.

[Robinson]

Why are there 2 inputs in a single FBC tuner?

What if one input is used for 19E and the other for 13E?

[WanWizard]

So you can attach a wideband LNB to it, which has two outputs (one horizontal, one vertical).

 

You can also configure them as two separate FBC inputs (for example to a Unicable switch), as two legacy inputs (so it behaves like an old-fasioned dual tuner card), or as a combination (one Unicable input and one legacy input).

[Dimitrij]

So

single FBC tuner- as an option - two separate tuners

Edited by Dimitrij, 5 October 2018 - 12:34.

[WanWizard]

Is there a dual DVB-S2 tuner card available? As it has a built-in FBC complex plus 1 pluggable tuner slot. For the Xsarius Galaxy I can only find a dual DVB-C card.

[Dimitrij]

Lunix3-4k

pluggable tuners:

simple DVB-S2 or DVB-C/DVB-T2

[WanWizard]

Interesting, given the fact that the Galaxy 4K and the Lunix3-4K are exactly the same box...

[Abu Baniaz]

@Dimitrij, could you please try our test (without the recordtimer.py changes) to see if your device also has the same issue.

 

Schedule two simultaneous timed recording using a unicable LNB. The recordings have to be on different polarities so request is sent on two different SCR channels. I used 10847 V and 10964 H on 28.2.

[Dimitrij]

I do not have unicable LNB.

[littlesat]

The 1 second recording 'work-a-round' solves (also) a different issue...

[Huevos]

 

 

Yes, I already read that after I posted this. So it's not STB brand specific. Apparently it IS LNB/switch specific. And that's why I don't want a "generic" workaround, for me (and probably some others too) it now works and I'd very much like to keep it that way. A workaround is never allowed when it breaks the stuff that already worked.

Just because some switches aren't vulnerable to this bug doesn't mean the ones that are, are faulty. Too many devices affected and the one thing they have in common is running enigma2.

My rationale is: the standard doesn't require delays and some of the SCR switches prove this point. I am not against making non-standard adhering stuff work, but never at the expense of devices that already work without the workaround. So extra delays: fine, but only when explicitly requested or, if possible, auto-detected from the connected devices.

 

I still think the standard SEC delays should be tried first.

 

The only delay in there that I can see that is relevant to Unicable devices is "delay between enable voltage and diseqc command". i.e. give the Unicable device sufficient time to boot.

[Abu Baniaz]

@Athoik, I should add that in my test with your suggested cpp changes and no recordtimer.py changes, I took the receiver out of standby. It remained stating "tune failed" until I selected another service. So the statement that re-tune is attempted doe snot seem to apply in my case. So, we were meant to two services being accessed using the LNB. Can it be really true that it did not power up for well over 10 minutes?

Attached Files

•  Enigma2_debug_2018-10-04_11-34-34.log   877.57KB   2 downloads

Edited by Abu Baniaz, 5 October 2018 - 18:40.

[littlesat]

Each hardware (lnb! Might require a different delay... couldn’t we consider to add this delay in unicable.xml when we know it for a specific lnb and add a delay in the manual config... than random and repeat stuff might not be required...

[Erik Slagter]

So you can attach a wideband LNB to it, which has two outputs (one horizontal, one vertical).

 

You can also configure them as two separate FBC inputs (for example to a Unicable switch), as two legacy inputs (so it behaves like an old-fasioned dual tuner card), or as a combination (one Unicable input and one legacy input).

Or even more possibilities:

 

- attach two switches, one of them supplying four positions and another supplying another four positions

- attach two switches and be able to record two services completely independent of each other (no need for same quadrant)

- or, in my case, attach to SCR switches, one supplies four positions and one supplies another, and then any one of the eight demodulators can use any of the eight positions.

 

So yes, there is really a use for it. And it's still a single tuner

[Erik Slagter]

The only delay in there that I can see that is relevant to Unicable devices is "delay between enable voltage and diseqc command". i.e. give the Unicable device sufficient time to boot.

To me this sounds actually like another feature: delay between voltage CHANGE and SEC command. In contrary to general delays, there is a minimum time specified between the voltage having changed and the SEC command being sent. In a "legacy" system, the voltage (low/high) is used for selecting high or low band, in an SCR system, the voltage is fixed, for Unicable it's high and for JESS it's low. So normally, using an SCR system, there are no voltage changes, unless you're doing weird things incorporating legacy or (real) DiSEqC, which I would really advise against.

 

If you install the DiSEqC timing plugin, you can tweak them all.

Edited by Erik Slagter, 6 October 2018 - 08:26.

[Erik Slagter]

Each hardware (lnb! Might require a different delay... couldn’t we consider to add this delay in unicable.xml when we know it for a specific lnb and add a delay in the manual config... than random and repeat stuff might not be required...

That is a step further in the workaround process. Let's start with finding out where's the bottleneck.

[Huevos]

I have got the diseqc delays plugin. None of the delays are relevant to unicable.

[littlesat]

That is a step further in the workaround process. Let's start with finding out where's the bottleneck.

I agree....

[athoik]

@Athoik, I should add that in my test with your suggested cpp changes and no recordtimer.py changes, I took the receiver out of standby. It remained stating "tune failed" until I selected another service. So the statement that re-tune is attempted doe snot seem to apply in my case. So, we were meant to two services being accessed using the LNB. Can it be really true that it did not power up for well over 10 minutes?

<  1310.951> [eDVBFrontend] set static current limiting
<  1310.951> [eDVBFrontend] set static current limiting
<  1310.951> [eDVBFrontend] invalidate current switch params
<  1310.951> [eDVBFrontend] invalidate current switch params
<  1310.952> [eDVBFrontend] setVoltage 1
<  1310.953> [eDVBFrontend] setVoltage 1
<  1310.953> [eDVBFrontend] sleep 1500ms
<  1310.953> [eDVBFrontend] sleep 1500ms
<  1310.963> [Trashcan] /media/hdd/movie/.Trash: Size: 0
<  1310.963> [Trashcan] /media/hdd/movie/.Trash: Size now: 0
<  1310.965> [Task] job Components.Task.Job name=Cleaning Trashes #tasks=1 completed with [] in None
<  1312.453> [eDVBFrontend] setVoltage 2
<  1312.454> [eDVBFrontend] setVoltage 2
<  1312.455> [eDVBFrontend] setTone 0
<  1312.456> [eDVBFrontend] setTone 0
<  1312.456> [eDVBFrontend] sleep 75ms
<  1312.456> [eDVBFrontend] sleep 75ms
<  1312.587> [eDVBFrontend] sendDiseqc: 7043e500(?)
<  1312.643> [eDVBFrontend] sendDiseqc: 704c5a02(?)
<  1312.643> [eDVBFrontend] sleep 100ms
<  1312.643> [eDVBFrontend] sleep 100ms
<  1312.743> [eDVBFrontend] setVoltage 1
<  1312.744> [eDVBFrontend] setVoltage 1
<  1312.744> [eDVBFrontend] update current switch params
<  1312.745> [eDVBFrontend] update current switch params
<  1312.745> [eDVBFrontend] startTuneTimeout 5000
<  1312.745> [eDVBFrontend] startTuneTimeout 5000
<  1312.745> [eDVBFrontend] setFrontend 1
<  1312.745> [eDVBFrontend] setting frontend 0
<  1312.748> [eDVBFrontend] (0)fe event: status 0, inversion off, m_tuning 1
<  1312.748> [eDVBFrontend] setFrontend 1
<  1312.748> [eDVBFrontend] setting frontend 1
<  1312.750> [eDVBFrontend] sleep 500ms
<  1312.802> [eDVBFrontend] (1)fe event: status 0, inversion off, m_tuning 1
<  1312.802> [eDVBFrontend] sleep 500ms
<  1312.803> [eDVBFrontend] (0)fe event: status 7, inversion off, m_tuning 2
<  1312.850> [eDVBFrontend] (1)fe event: status 7, inversion off, m_tuning 2
<  1313.052> [eDVBFrontend] (0)fe event: status 1f, inversion off, m_tuning 3



<  1322.979> [eDVBFrontend] (1)tune
<  1322.979> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x12936, guard_offset 0
<  1322.979> **** Tuning JESS
<  1322.979> **** frequency_mhz: 10964
<  1322.979> **** lo_mhz: 9750
<  1322.979> **** T: 1114
<  1322.979> **** position: 0
<  1322.979> **** ub: 9
<  1322.979> **** mode: 2
<  1322.979> **** JESS: 70 4c 5a 02
<  1322.979> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
<  1322.979> [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
<  1322.979> [eDVBFrontend] tuning to 1425 mhz
<  1322.979> [eDVBChannel] OURSTATE: tuning
<  1322.979> [eDVBServicePMTHandler] tune failed.
<  1322.979> [eDVBServiceRecord] RECORD service event 1
<  1322.979> [eDVBServiceRecord] record failed to tune
<  1322.980> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
<  1322.980> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
<  1322.980> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 809 current: ffffffff
<  1322.980> [eDVBServicePMTHandler] incorrect original_network_id. expected: 2 current: ffffffff
<  1322.980> [eDVBFrontend] set static current limiting
<  1322.980> [eDVBFrontend] invalidate current switch params
<  1322.980> [eDVBFrontend] set sequence pos 3
<  1322.980> [eDVBFrontend] setVoltage 2
<  1322.981> [eDVBFrontend] setTone 0
<  1322.981> [eDVBFrontend] sleep 75ms
<  1323.112> [eDVBFrontend] sendDiseqc: 704c5a02(?)
<  1323.113> [eDVBFrontend] sleep 100ms
<  1323.213> [eDVBFrontend] setVoltage 1
<  1323.214> [eDVBFrontend] update current switch params
<  1323.214> [eDVBFrontend] startTuneTimeout 5000
<  1323.214> [eDVBFrontend] setFrontend 1
<  1323.214> [eDVBFrontend] setting frontend 1
<  1323.214> [eDVBFrontend] (1)fe event: status 0, inversion off, m_tuning 1
<  1323.214> [eDVBFrontend] sleep 500ms
<  1323.260> [eDVBFrontend] (1)fe event: status 7, inversion off, m_tuning 2
<  1323.714> [eDVBFrontend] set dynamic current limiting
<  1328.214> [eDVBChannel] OURSTATE: failed, retune



<  1338.683> [eDVBFrontend] (1)tune
<  1338.683> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x12936, guard_offset 0
<  1338.683> **** Tuning JESS
<  1338.683> **** frequency_mhz: 10964
<  1338.683> **** lo_mhz: 9750
<  1338.683> **** T: 1114
<  1338.683> **** position: 0
<  1338.683> **** ub: 9
<  1338.683> **** mode: 2
<  1338.683> **** JESS: 70 4c 5a 02
<  1338.683> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
<  1338.683> [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
<  1338.683> [eDVBFrontend] tuning to 1425 mhz
<  1338.684> [eDVBChannel] OURSTATE: tuning
<  1338.684> [eDVBServicePMTHandler] tune failed.
<  1338.684> [eDVBServiceRecord] RECORD service event 1
<  1338.684> [eDVBServiceRecord] record failed to tune
<  1338.684> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
<  1338.684> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
<  1338.684> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 809 current: ffffffff
<  1338.684> [eDVBServicePMTHandler] incorrect original_network_id. expected: 2 current: ffffffff
<  1338.684> [eDVBFrontend] set static current limiting
<  1338.684> [eDVBFrontend] invalidate current switch params
<  1338.684> [eDVBFrontend] set sequence pos 3
<  1338.684> [eDVBFrontend] setVoltage 2
<  1338.685> [eDVBFrontend] setTone 0
<  1338.686> [eDVBFrontend] sleep 75ms
<  1338.817> [eDVBFrontend] sendDiseqc: 704c5a02(?)
<  1338.818> [eDVBFrontend] sleep 100ms
<  1338.918> [eDVBFrontend] setVoltage 1
<  1338.918> [eDVBFrontend] update current switch params
<  1338.918> [eDVBFrontend] startTuneTimeout 5000
<  1338.918> [eDVBFrontend] setFrontend 1
<  1338.918> [eDVBFrontend] setting frontend 1
<  1338.918> [eDVBFrontend] (1)fe event: status 0, inversion off, m_tuning 1
<  1338.918> [eDVBFrontend] sleep 500ms
<  1338.960> [eDVBFrontend] (1)fe event: status 7, inversion off, m_tuning 2
<  1339.419> [eDVBFrontend] set dynamic current limiting
<  1343.918> [eDVBChannel] OURSTATE: failed, retune


<  1349.153> [eDVBFrontend] (1)tune
<  1349.153> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x12936, guard_offset 0
<  1349.153> **** Tuning JESS
<  1349.153> **** frequency_mhz: 10964
<  1349.153> **** lo_mhz: 9750
<  1349.153> **** T: 1114
<  1349.153> **** position: 0
<  1349.153> **** ub: 9
<  1349.153> **** mode: 2
<  1349.153> **** JESS: 70 4c 5a 02
<  1349.153> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
<  1349.153> [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
<  1349.153> [eDVBFrontend] tuning to 1425 mhz
<  1349.154> [eDVBChannel] OURSTATE: tuning
<  1349.154> [eDVBServicePMTHandler] tune failed.
<  1349.154> [eDVBServiceRecord] RECORD service event 1
<  1349.154> [eDVBServiceRecord] record failed to tune
<  1349.154> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
<  1349.154> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
<  1349.154> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 809 current: ffffffff
<  1349.154> [eDVBServicePMTHandler] incorrect original_network_id. expected: 2 current: ffffffff
<  1349.154> [eDVBFrontend] set static current limiting
<  1349.154> [eDVBFrontend] invalidate current switch params
<  1349.154> [eDVBFrontend] set sequence pos 3
<  1349.154> [eDVBFrontend] setVoltage 2
<  1349.155> [eDVBFrontend] setTone 0
<  1349.156> [eDVBFrontend] sleep 75ms
<  1349.286> [eDVBFrontend] sendDiseqc: 704c5a02(?)
<  1349.287> [eDVBFrontend] sleep 100ms
<  1349.387> [eDVBFrontend] setVoltage 1
<  1349.388> [eDVBFrontend] update current switch params
<  1349.388> [eDVBFrontend] startTuneTimeout 5000
<  1349.388> [eDVBFrontend] setFrontend 1
<  1349.388> [eDVBFrontend] setting frontend 1
<  1349.388> [eDVBFrontend] (1)fe event: status 0, inversion off, m_tuning 1
<  1349.388> [eDVBFrontend] sleep 500ms
<  1349.430> [eDVBFrontend] (1)fe event: status 7, inversion off, m_tuning 2
<  1349.888> [eDVBFrontend] set dynamic current limiting
<  1354.388> [eDVBChannel] OURSTATE: failed, retune

Above you can see two tuners trying to tune, the tuner 0-A succeeds with status 1f, the tuner 1-B fails with status 7.

Then tuner B, tries several times, and it never tunes. It always fails with last status reported from tuner 7.

So the real question here is: Why tuner never got LOCK? Why re-tune failed?



In case you wonder what 7 or 1f is:

7 = FE_HAS_SIGNAL | FE_HAS_CARRIER | FE_HAS_VITEBRI

1f = FE_HAS_LOCK | FE_HAS_SYNC | FE_HAS_VITERBI | FE_HAS_CARRIER | FE_HAS_SIGNAL

/**
* enum fe_status - enumerates the possible frontend status
* @FE_HAS_SIGNAL: found something above the noise level
* @FE_HAS_CARRIER: found a DVB signal
* @FE_HAS_VITERBI: FEC is stable
* @FE_HAS_SYNC: found sync bytes
* @FE_HAS_LOCK: everything's working
* @FE_TIMEDOUT: no lock within the last ~2 seconds
* @FE_REINIT: frontend was reinitialized, application is recommended
* to reset DiSEqC, tone and parameters
*/
enum fe_status {
FE_HAS_SIGNAL = 0x01,
FE_HAS_CARRIER = 0x02,
FE_HAS_VITERBI = 0x04,
FE_HAS_SYNC = 0x08,
FE_HAS_LOCK = 0x10,
FE_TIMEDOUT = 0x20,
FE_REINIT = 0x40,
};

[Huevos]

@Athoik, "So the real question here is: Why tuner never got LOCK? Why re-tune failed?"

 

1) So why are both recordings zero length if one tuner is locked?

2) Is there any debug we could add to track down where the failure is?