108 replies to this topic

[littlesat]

I only need time to create it...

 

I also have the Solo4K and at least with Ziggo I could not discover any "transponders"  that could not be tuned. But of course this could be related because I'm using cable scan only...

 

And typically that all frequencies are "off" 0.750 Mhz....

Edited by littlesat, 10 October 2016 - 11:29.

[littlesat]

Suggestion - not tested

 

 

self.scan_cab.frequency = ConfigInteger(default = defaultCab["frequency"], limits = (50000, 999000))

->

self.scan_cab.frequency = ConfigFloat(default = defaultCab["frequency"], limits = [(50, 999),(0,999)])

 

self.scan_cab.frequency.value*1000

->

self.scan_cab.frequency.value[0]*1000+self.scan_cab.frequency.value[1]

[Abu Baniaz]

I tried editing the scansetup.py and got a crash. Just in case I made a mistake, can you attach the test file/s please?

<   171.791>   File "/usr/lib/enigma2/python/Components/ActionMap.py", line 66, in action
<   171.792>   File "/usr/lib/enigma2/python/Components/ActionMap.py", line 46, in action
<   171.792>   File "/usr/lib/enigma2/python/Screens/Menu.py", line 53, in okbuttonClick
<   171.792>   File "/usr/lib/enigma2/python/Tools/BoundFunction.py", line 9, in __call__
<   171.792>   File "/usr/lib/enigma2/python/Screens/Menu.py", line 68, in runScreen
<   171.792>   File "/usr/lib/enigma2/python/Screens/Menu.py", line 74, in openDialog
<   171.792>   File "/usr/lib/enigma2/python/mytest.py", line 279, in openWithCallback
<   171.792>     dlg = self.open(screen, *arguments, **kwargs)
<   171.792>   File "/usr/lib/enigma2/python/mytest.py", line 289, in open
<   171.793>     dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
<   171.793>   File "/usr/lib/enigma2/python/mytest.py", line 232, in instantiateDialog
<   171.793>     return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
<   171.793>   File "/usr/lib/enigma2/python/mytest.py", line 249, in doInstantiateDialog
<   171.793>     dlg = screen(self, *arguments, **kwargs)
<   171.793>   File "/usr/lib/enigma2/python/Screens/ScanSetup.py", line 588, in __init__
<   171.794>     self.createConfig(frontendData)
<   171.794>   File "/usr/lib/enigma2/python/Screens/ScanSetup.py", line 989, in createConfig
<   171.794>     self.scan_cab.frequency = ConfigFloat(default = defaultCab["frequency"], limits = [(50, 999),(0,999)])
<   171.794> NameError: global name 'ConfigFloat' is not defined

[arn354]

Import of ConfigFloat is missing.

from Components.config import ...., ConfigFloat

[Erik Slagter]

Huevos, changing the value type to float is the correct way to go, really. Don't see it as kHz like it is handled internally, see it as a MHz value, fractioned or not at will. Most of us (really!) will never need to specify sub-MHz fractions. For those, they can continue to enter MHz like they used to. For the few that need to use sub-MHz fractions (for whatever reason), they can simply enter a decimal point and specify up to whatever decimal digits are required to get the tuner going. I cannot think of a solution that is more correct and nice.

 

Patches are always appreciated, but they're never commited without our consent. At least we're the ones that are responsible for the product as a whole, not someone that supplies a patch.

 

I'm a bit disappointed in your remark about JESS support. I have spent three days of my holidays vacation days trying to get the dvbadenin set of patches into PLi, in a NEAT and ORGANISED way. While doing that, I discovered most of the code has no relation to JESS at all and changes all sorts of code at "random" places as the authors suits. I tried the final result and it just doesn't work.

 

So that is where we decided we're going to do it ourselves, from scratch, properly. On the technical level, the way of controlling a Unicable switch is almost identical to controlling a JESS switch. So if thousands of lines of code are supplied to do just that, I really think something is wrong.

 

That means the work has to be done by ourselves, in our spare time, which at least I am not abundant in. If you want to have JESS rather dearly, it will help more if you join development which will start shortly.

[Abu Baniaz]

<  2199.820> Traceback (most recent call last):
<  2199.820>   File "/usr/lib/enigma2/python/Components/config.py", line 140, in __call__
<  2199.821>   File "/usr/lib/enigma2/python/Components/config.py", line 630, in getMulti
<  2199.821>   File "/usr/lib/enigma2/python/Components/config.py", line 613, in genText
<  2199.821> TypeError: 'int' object is not iterable
<  2201.628> Traceback (most recent call last):
<  2201.628>   File "/usr/lib/enigma2/python/Components/ConfigList.py", line 75, in selectionChanged
<  2201.628>   File "/usr/lib/enigma2/python/Screens/Setup.py", line 59, in selectionChanged
<  2201.628>   File "/usr/lib/enigma2/python/Components/ConfigList.py", line 179, in getCurrentValue
<  2201.628>   File "/usr/lib/enigma2/python/Components/config.py", line 626, in getText
<  2201.628>   File "/usr/lib/enigma2/python/Components/config.py", line 613, in genText
<  2201.629> TypeError: 'int' object is not iterable

Attached Files

•  ScanSetup_1800.zip   14.2KB   3 downloads
•  enigma2_crash_1476119579.log   14.76KB   1 downloads

[littlesat]

You need to import ConfigFloat on top in the from config import .... Section of couse....

[Abu Baniaz]

You need to import ConfigFloat on top in the from config import .... Section of couse....

That has been done. Please check attachment.

Edited by Abu Baniaz, 10 October 2016 - 19:41.

[littlesat]

Devug what is coming back from the config.... As far I understand blindly it should be a tupple with a number before the dot and the number after e dot...

[Abu Baniaz]

It does not even go that far.

Attached Files

•  puttylog-20161010-195402.txt   10.12KB   10 downloads

[Huevos]

Huevos,

 

I'm a bit disappointed in your remark about JESS support. I have spent three days of my holidays vacation days trying to get the dvbadenin set of patches into PLi, in a NEAT and ORGANISED way. While doing that, I discovered most of the code has no relation to JESS at all and changes all sorts of code at "random" places as the authors suits. I tried the final result and it just doesn't work.

The patch I supplied was fully working. Several of the PLi team built it and tested. Anyway no point going over old ground now. If it is not good enough for PLi that is up to them.

[littlesat]

Please help us to implement jess in the prober way and not in the hacky way...
I did already spend hours in the jess-ui brench and I removed more then 100 lines and then code is doing the same (even improved) without storing the manufacturers list three times....
We are currently not that far away of completing it withou also I guess also more than 100 lines less in cpp....

[arn354]

I doubt people are interested in a new, cleaner and maybe better way - because it is right now simply very difficult to replace the existing, working but "bad" implementation in their images.
In addition i allready noticed some problems we allready had 2 years ago in your new approach.
Sorry for offtopic - we should not move this to unicable ii discussion.

Edited by arn354, 10 October 2016 - 20:54.

[littlesat]

https://github.com/O...4c09c13f475579e

 

But still we need actually to fix DVB-T and ATSC regarding this topic....

[Abu Baniaz]

Many thanks, that is working.

I think some work is needed in tranponder.py too. Reason being, when you are on an active channel and proceed to scan, it should pre-load the current frequency. At the moment if I am on 370.750 MHz and proceed to scan, it loads up on 370.000 MHz.

[littlesat]

Thanks for the feedback... Let's say work in progress....

Can you make a screenshot from both tuner screens with manu, information, service (yellow and blue)?

Edited by littlesat, 11 October 2016 - 06:47.

[Abu Baniaz]

I have attached satellite and cable pictures for you.

DVB-C Multiplex
 pli dvbc multiplex.jpg   47.44KB   3 downloads

DVB-C Tuner Status
 pli dvbc tuner status.jpg   49.08KB   3 downloads

282 Multiplex
 pli 282 multiplex.jpg   60.48KB   3 downloads

282 Tuner status
 pli 282 tuner status.jpg   58.29KB   3 downloads

[littlesat]

Mmmm the frequency is also there in KHz....

[Abu Baniaz]

Some bad news...
1. predefined transponder does not show up.
2. Default tuner config is frequency bands. When I change provider, entering teh manual scan page results in a crash.

Attached Files

•  enigma2_crash_1476169945.log   14.93KB   4 downloads

[Rob van der Does]

Mmmm the frequency is also there in KHz....

Isn't that what Abu said before?

If displaying values in MHz is of utmost importance, the service information and scanning stage will also need adapting. They were in kHz last time I checked.

Edited by Rob van der Does, 11 October 2016 - 08:19.