250 replies to this topic

[athoik]

See: https://github.com/O...enigma2/network

[Erik Slagter]

It was merged from "jess" not from "origin/jess" 

[Huevos]

Erik, all your SCRs start from 1. What is going to happen for a device that the SCRs run 4,5,6 and doesn't have 1,2,3?

Edited by Huevos, 13 December 2016 - 16:08.

[littlesat]

Do you know such device? I think it makes no sense such device exists. Why should you 'skip' SCRs?

 

As I could not find any I did not include real proactive actions for this. Why making it more complex as needed?

 

If so I know some... please give me a config for the xml and I can adapt the code....

 

Please note adaption in code extreme simple (~add one line and adapt 3)... And the syntax for the XML is already prepared by me... The 'comma split' does most of the job for you  An empty string between comma's can defined a not used SCR slot... ... Done

 

scrs= ",1210,,1420,,1680,,2040"

E.g. when you only want to configure src 2,4,6,8....

 

scrs= ",,,1210,1420,1680"

E.g. when you only want to configure src 4,5,6.... your example...

 

Unless this I still hope such wierd device simply does not exist... 

 

So I start worrying when I see such device...  I just tried to keep it simple and better readable... and when something occurs that does not fit into this... we'll fix it on demand...

Edited by littlesat, 13 December 2016 - 16:27.

[Huevos]

Well one example would be self configured. i.e. you put 2 matrix on one cable and program the first to 1,2,3 and the second to 4,5,6. This would give you possibility of 4 satellites over single cable without using expensive U II switches.

[Huevos]

Do you know such device? I think it makes no sense such device exists. Why should you 'skip' SCRs?

 

As I could not find any I did not include real proactive actions for this. Why making it more complex as needed?

 

If so I know some... please give me a config for the xml and I can adapt the code....

 

Please note adaption in code extreme simple (~add one line and adapt 3)... And the syntax for the XML is already prepared by me... The 'comma split' does most of the job for you  An empty string between comma's can defined a not used SCR slot... ... Done

 

scrs= ",1210,,1420,,1680,,2040"

E.g. when you only want to configure src 2,4,6,8....

 

Unless this I still hope such wierd device simply does not exist...

If it is a simple fix I recommend you do it for the sake of completeness.

 

Also wouldn't a Dict be better than comma separated values?

Edited by Huevos, 13 December 2016 - 16:29.

[littlesat]

For self configured it is no issue at all.... You do not select on an input a SCR you do not need... So even the frequency there is a don't care...

 

Please do not search for issue that do not exist (yet)...

 

Well one example would be self configured. i.e. you put 2 matrix on one cable and program the first to 1,2,3 and the second to 4,5,6. This would give you possibility of 4 satellites over single cable without using expensive U II switches.

How do you think making this possible...?

Edited by littlesat, 13 December 2016 - 16:33.

[littlesat]

If it is a simple fix I recommend you do it for the sake of completeness.

 

Also wouldn't a Dict be better than comma separated values?

I will not do....

 

As there is no issue at all yet..... And i do not want to make it more complicated as long this is not required at all... As far i know it is complete now.... and the manufacturer list is relevant to manual config

 

But it seems there are some out there that prefer to make it more complicated than really required...

 

I'm only considering to change something here when I really got good examples and a concrete requirement.

 

Note at this moment we cleaned-up the complete UNICABLE/JESS stuff from the chaos it was.... and we try to keep it as simple and clean as possible and not add code that is not required at all...

 

Also wouldn't a Dict be better than comma separated values?

->

Only when we have a lot of switches and/or lnbs that are skipping SCRs? For now this is not a requirement....

Edited by littlesat, 13 December 2016 - 16:47.

[Huevos]

For self configured it is no issue at all.... You do not select on an input a SCR you do not need... So even the frequency there is a don't care...

 

I don't think you understand what I am telling you. Each tuner operates on a single frequency so it does not interfere with other STBs on the same cable.

 

So let's say you configure a tuner to use 1210.

 

You have 2 switches on the same cable. You need to be able to configure different SCRs to both return on 1210.

 

Or are you saying you only want PLi to work if a switch uses the standard factory defaults?

Edited by Huevos, 13 December 2016 - 16:53.

[littlesat]

All is possible with the current situation... I do not see the issue you mention at all... You can program same frequencies on different SCRs when you like... The frequencies can be changed on demand...

 

And all this is unrelated to the default values 'loaded' via the xml....

The manual config behaves basically exact the same as it was in the 'legacy' code... 8 or 32 frequencies with 2 or 64 positions...

 

you need to be able to configure different SCRs to both return on 1210.

->Wouldn't this interfere...???

Edited by littlesat, 13 December 2016 - 17:06.

[Huevos]

All is possible with the current situation...The manual config behaves basically exact the same as it was in the legacy code...

In the legacy code the frequency is locked to the SCR, i.e. under  "Configuration Mode: Unicable LNB" frequency is displayed but it is impossible to modify.

[littlesat]

I'm afraid you miss something... With manual config frequency the can be adapted.

Edited by littlesat, 13 December 2016 - 17:57.

[Huevos]

Yes, you can do it manually, but doesn't that defeat the purpose of having the .xml file?

[littlesat]

Sorry... I'm really lost here... The xml file contains fixed switches and lnbs.... why should you adapt stuff that is loaded from there??? The xml is intend to quickly connect standard stuff by setlecting your connected switch and then a SCR belongs also to a fixed frequency... - there is no way to get around this...

Edited by littlesat, 13 December 2016 - 18:49.

[Erik Slagter]

Yes, you can do it manually, but doesn't that defeat the purpose of having the .xml file?

It's exactly alike settings lists. They're suitable for 99% of the users and perfectly sufficient for them. It's not sufficient for me, so I do scan tuners manually. For non-standard switch configurations exactly the same, the predefined models will be perfectly suitable for 99% of the users and for the others, there is the manual input.

 

If you think there is a switch missing from the list, please send a patch and we will include it.

[littlesat]

And when there is one that slips scrs I adapt the code

[Huevos]

Unfortunately it doesn't work properly yet.

 

PLi image dated 2016-12-13 (no update currently available).

Edison OS Mini +

Inverto IDLU-32Ul40_UNBOO-OPP (this is probably the most popular Unicable II LNB of all).

 

SCR 1-8 tuner locks

SCR 9-32 no tuner lock

 

Hardware works fine with Adenin version.

 

I'm happy to keep this box active on this image for the time being and run some debug on it if necessary.

Edited by Huevos, 13 December 2016 - 23:54.

[Eragon]

Here my proposed addition to unicable.xml:

<manufacturer name="Unitron-Johansson for Sky">
	<product name="dCSS-41" positions="1" format="jess" scrs="1210,1420,1680,2040,985,1050,1115,1275,1340,1485,1550,1615,1745,1810,1875,1940"/>
	<product name="9732" positions="1" format="jess" scrs="1210,1420,1680,2040,985,1050,1115,1275,1340,1485,1550,1615,1745,1810,1875,1940"/>
</manufacturer>

Tested on my Vu+ Duo2 (just updated) connected to the Unitron-Johansson 9732 (multiswitch with 2 outputs, 16 user bands each)

http://unitrongroup.....html#downloads

 

The 2 outputs of the multiswitch were in use at the same time:

1) Sky+ Pro

2) Vu+ Duo2

 

The 2 Duo2's sat tuners were configured as follows:

Tuner A (with sat cable):  SCR 5 - 985

Tuner B (connected to A): SCR 6 - 1050

 

Tested with PIP: 2 channels tuned from different transponders with different polarity.

 

But one thing is IMHO very important to note:

 

The 2 tuners works with this JESS configuration only if 2 user bands are assigned contiguously to the tuners, starting with the first EN50607 unassigned user band.

 

I mean: for my multiswitch these are the results for all possible JESS user band assignments, starting from 5 (first available EN50607):

 

Tuner A: 5 - Tuner B: 6  ----> ALL OK

Tuner A: 5 - Tuner B: >6  ----> ONLY TUNER A WORKS

Tuner A: >5 - Tuner B: SCR Tuner A + 1 (or more than + 1)  ---> NO TUNER WORKS

Edited by Eragon, 14 December 2016 - 00:27.

[Eragon]

Some findings from further testing...

 

Sat cable moved from Tuner A to Tuner B, Tuner A configured as "Connect to: Tuner B"

 

Tuner A: 6 - Tuner B: 5 --> ONLY ONE CHANNEL AT A TIME WORKS

Tuner A: 5 - Tuner B: 6 --> ONLY ONE CHANNEL AT A TIME WORKS

 

So, to get 2 channels tuned at the same time, the cable must be connected to Tuner A and Tuner A must be assigned to the first available JESS (EN50607) SCR user band.

 

I didn't play with the tuner priority configuration options, all left as default after image installation.

Edited by Eragon, 14 December 2016 - 02:08.

[littlesat]

@huevos, can you check if we have a good frequency for scrs > 8?... Out switches for testing had only 6 scrs... It could als be some 'filter' in our code...
Whe it is some 'filter' or bitmask I'm sure you can find it as our code is 200+ lines less complicated...

Edited by littlesat, 14 December 2016 - 07:52.