250 replies to this topic

[Huevos]

The default values are for a standard Universal LNB setup.

 

Universal is completely different because the voltage and 22kHz tone are sent continuously. So the LNB will interpret them as soon as it comes online.

 

Unicable is different because the control word is sent once and the LNB/switch needs to be in booted state to be able to understand it.

 

Every Unicable device is going to take a different time to boot and some are going to be permanently powered. So changing the default to suit some Unicable devices is not really an option. If it was going to be built in it would be user configurable.

[littlesat]

But I think it is not bad to enlarge this time by default from 200 to e.g. 900 ot even 1000 msec to at leasf allow such LNBs to boot... When you catch most of them that is already a win win... So I'm even considering to remove the diseqc repeat in simple config, but back the standard repeat to 120 msec and consider to change the delay after power change form diseqc from 20 to 80 msec... To give more room for that artifact... Or use 75 there as openatv proves this is a good value for it...

[Huevos]

That will slow zapping on regular LNBs. And selecting 1000 ms is not going to help devices that need 2000 ms. Would need to be user configurable.

Edited by Huevos, 6 January 2017 - 01:11.

[littlesat]

I think this will not slow down zapping on regular lnb's at all... As usually the Voltage is always there... we can also do it conditional...when we have Jess/unicable in that nim then use a different value with x msec, default 1000..(requires cpp change and an extra config).t

Edited by littlesat, 6 January 2017 - 10:01.

[Huevos]

Ok, but if you are going to do this please can it be configurable by the user?

[littlesat]

All these deseqc finetunings things are configurable by the user....

[Huevos]

Not in the base image. You need the plugin.

[littlesat]

Does that hurt in extreme conditions???

[littlesat]

In jess mode in line 717 in /lib/dvb/sec.cpp the delay when the power was switched on is set... we could consider to make a separate config for this one and set there at that place the different one... (to e.g. 1 second / 1000 msec)...

 

When there are LNBs that need a longer boot time we could let the user check via the plugin and consider to extend this when required....

Line 717 in sec.cpp
 
-sec_sequence.push_back( eSecCommand(eSecCommand::SLEEP, m_params[DELAY_AFTER_ENABLE_VOLTAGE_BEFORE_SWITCH_CMDS] ) );
+sec_sequence.push_back( eSecCommand(eSecCommand::SLEEP, m_params[DELAY_AFTER_ENABLE_VOLTAGE_BEFORE_SWITCH_CMDS_WHEN_UNICABLE_JESS] ) );
 
Add to NimManager.py
+config.sec.delay_after_enable_voltage_before_switch_command_when_unicable_jess = ConfigInteger(default=1000, limits = (0, 9999))
 
and arrange the swig to m_params....

Edited by littlesat, 6 January 2017 - 17:23.

[Erik Slagter]

@Erik, the reason Vu+ added "ForceLNBPower" and "ForceTone" was because the FBC links didn't work properly once the root tuner became inactive. i.e. a recording active on tuner C and the box put in standby and the recording would fail.

I am perfectly aware of that but I don't see the relevance here, context?

[Erik Slagter]

Littlesat, tred very carefully here. We already saw what happens when values are changed here. Some combination may start to work, others stop working.

 

IMHO the best solution is to not have the LNB being powered down to start with. Something like an option "this LNB must be powered continuously" and then the tuner always supplies at least 13V. As far a I understand the code, it should be possible to do it this way. This beats timers on "random" delays from every angle. When the receiver goes into deep standby, the tuner will be powered down anyway, so people that want to be economic here, use the deep standby mode.

[Eragon]

Please consider also that JESS multiswitches are always powered on due to the dedicated power supply or injector.

They shouldn't need any increased delay.

Edited by Eragon, 6 January 2017 - 20:16.

[littlesat]

Switch or LNB is known in UI... but nothing is done yet...

 

I hope next sunday I can try to add support for that specific sky-Q LNB... (but in multi unicable/jess mode where the first four are unicable..)

 

I do not have that LNB so I cannot really test it. I can only verify what happens with "grabbing" the LNB output to my digital scope...

Edited by littlesat, 6 January 2017 - 20:38.

[Erik Slagter]

I have updated information on SkyQ LNB's. It's NOT as simple as keeping the voltage low. It's an implementation upon DiSEqC, not related to either Unicable or JESS. I have the specs, for whoever is bored

 

Unless you mean something else?

[Erik Slagter]

Please consider also that JESS multiswitches are always powered on due to the dedicated power supply or injector.

They shouldn't need any increased delay.

Just like I say. No delays, just keep the LNB powered on.

[littlesat]

Unless you mean something else?

They support 2 different modi...one for sky-Q and the other that has mixed unicable/jess.... Unicable for the first 4 scrs and jess for scr 5 and above...

[WanWizard]

That just means the switch has to go into the XML three times: once as "legacy", once as "jess", and once as "new-skyq-mode".

 

The first two modes already exist, the only thing that needs to be added is a way to limit the number of scr's and/or define the frequency per scr.

[littlesat]

That just means the switch has to go into the XML three times: once as "legacy", once as "jess", and once as "new-skyq-mode".

->

Nope... It can go in one thing in the XML by adding a new format type specially for this type of LNB.... the rest goes automatically... when the index is 4 or below it selects unicable... when the index is 5 or above then it selects jess... This can be used for all switches that use the same chip as in this specific switch... You can connect a sky-Q LNB to one port and a enigma2 box to the other port... 

 

example of the line in unicable.xml

 

<product name="9732" positions="1" format="dSRC" scrs="1210,1420,1680,2040,985,1050,1115,1275,1340,1485,1550,1615,1745,1810,1875,1940"/>

 

And thanks through the structure we have it can be easily done...

Edited by littlesat, 6 January 2017 - 22:43.

[WanWizard]

Don't mix two separate discussions please.

 

As mentioned before (by for example Huevos), the SkyQ LNB is a wideband LNB, which feeds all horizontal polarisation down one cable, and all vertical ones down a second one, and requires two tuners to receive all channels. The SkyQ switch is a hybrid switch that supports both legacy, jess and sky-q receivers at the same time, with different SCR's.

 

Two completely different setups.

[littlesat]

It does not support jess.. It does support jess on index 5 and above... at index 4 and below (the first 4) it supports unicable...

 

What I want to do is add a format only for the unicable.xml stuff... 'dSCR' and when dSCR is selected then push 2 (for jess) to cpp when the scr index is 5 or above and push 1 (for unicable) when the index is 4 or below... Then this switch is fully supported by adding it to the unicable.xml... and changing 'just' two lines in NimManager.py....

 

Please give me a better name then dSCR when it exists for these 'kind' of switches.... The name is just the íssue why I did not pushed it yet... I can also call it 'hybrid' or 'mixed' as in fact it is a mixed unicable/jess switch... So I'm thinking of calling it mixed... (as first 4 are unicable others are jess)

 

The Wideband Sky-Q LNB we can't support as our tuners are currently not suitable for that wide spectrum at this moment.... but probably SKY does also has some switchable converters before the real tuner...

Edited by littlesat, 6 January 2017 - 23:20.