342 replies to this topic

[Rob van der Does]

And meanwhile it's best not to buy/use any FBC/Unicable combination.....

[Abu Baniaz]

There is a workaround in the images, so the equipment works. There is no need to refrain from procurement or usage of the equipment.

The continuation of this thread is so that we can find a proper solution.

Sent from my Moto G (5S) using Forum Fiend v1.3.3.

[anudanan]

Thank you for sharing.

 

Today I only use a FBC tuner (uno4kse) with two legacy cables and that works fine.

 

Today I have no need for unicable because many german stations are on two of the four sat quadrants so there are many parallel recordings possible and if I have a need to use the third sat quadrant for live TC then I use today the great PLI fallbacktuner to a second box in my house,

 

I´ll check this thread here if I will switch to unicable in the future

[WanWizard]

The problem isn't restricted to a full Unicable/JESS setup.

 

The same problem exists in any situation where you have multiple tuners on a single cable. With an FBC tuner, you have potentially 8 tuners on a single cable, even it that cable is connected to a legacy LNB. Just create multiple timers for channels on the same transponder, starting all at the same time...

[anudanan]

Are you sure? I offen start timers at prime time at the same time, sometimes an the same tranponder, sometimes on different transponders which goes for example over the cable on tuner A.

 

My understand is that there are no commands on the sat cable with legacy.. So there is no problem with commands which are not correctly in sequence

 

Or have I understand the problem wrongly?

Edited by anudanan, 19 October 2018 - 14:32.

[WanWizard]

If there are no DiseqC commands being send, then indeed it is not a problem.

[anudanan]

I don´t use DiseqC so my setup is ok

 

But for my understanding with a DiseqC setup:

 

If a receiver use a legacy cable with DiseqC and a FBC tuner. My understanding ist that only Tuner A and with two cables also Tuner B sends DiseqC commands over the attached cable to the switch and the additional tuners C-H connect on demand internal to a chain after  tuner A or B, But C-H don´t send additiional DiseqC commands because they can only use the same Sat Signal as Tuner A or B.

[WanWizard]

Yes. I may have opened my mouth before engaging my brain (or what is left of it).

[anudanan]

I wish you a nice recreation weekend ;-))

[Erik Slagter]

No WanWizard was right. All FBC automatic loop through tuners are actually in the end looped through to either input A or input B. The SEC (not only DiSEqC but also legacy like voltage and toneburst) commands are sent to the indivual tuners, the one that needs to be addressed, but in the end they appear on the same cable, because they're looped through. Enigma currently does not recognise this situation and fails to serialize the commands belonging to each tuner before sending them out.

 

This is the same for either FBC tuners or any two or more tuners that are looped through, SCR or legacy. The only thing is that using SCR and FBC, the situation is more likely to occur.

Edited by Erik Slagter, 19 October 2018 - 18:06.

[Huevos]

Does anyone have any idea why this PR was refused? Thanks for any explanation.

 

https://github.com/O...igma2/pull/1778

Edited by Huevos, 19 October 2018 - 18:25.

[littlesat]

It did error while merging when I tried

Edited by littlesat, 19 October 2018 - 18:40.

[Huevos]

OK, thanks Littlesat. I will try again.

[anudanan]

so the result on legacy cable Is that the same voltage and toneburst signals will come from all tuners on the same cable but that is in not a real problem because the signal from the sat will stay stable after the first selection. All tuners on the same cable order the same signal

Is it possible that the fbc driver filters out the Vorlage and toneburst Commands to the tuners c-h

Edited by anudanan, 19 October 2018 - 19:06.

[Erik Slagter]

I think it would be wise that you read all of the discussion. Your view on the topic lacks quite a bit of information. For instance it has nothing to do with neither FBC nor SCR (unicable).

Edited by Erik Slagter, 19 October 2018 - 20:27.

[WanWizard]

It did error while merging when I tried

 

Compile error? https://travis-ci.or.../jobs/443564715

[athoik]

Yes

It did error while merging when I tried

 
Compile error? https://travis-ci.or.../jobs/443564715

Correct, the prepareTurnOffSatCR misses simulate variable. So we cannot use eDebugNoSimulate unless we define simulate variable.

[littlesat]

So I refuses

[littlesat]

I’m afraid the only way to solve this issue is arrange that per dvb-s physical input we only can give one diseqc command... and not per tuner...

[Huevos]

It still won't solve it. I.e. 2 cable leave the STB. They join up externally at a unicable splitter, then the diseqc commands go over a single cable to the LNB/switch.

 

Only way to cure this properly is not send any parallel commands. Commands need to go in a queue. Send the commands for one tuner. Don't send any more commands until either tuning on that tuner is confirmed, or tuning timeout has been reached. Then move on to the next set of commands in the queue.

 

Also you need to decide how to handle a failure to tune, so that failure to tune on one tuner does not block tuning another tuner.

 

I can't see an easy fix. Looks like it would need a big code rewrite.