81 replies to this topic

[Huevos]

How (without doing a complete retune from scratch... get rawchannel... get frontend... etc)?

[littlesat]

That is exactly the challenge.... (to do it without pressing a button).

Edited by littlesat, 22 September 2017 - 10:37.

[Huevos]

I can do it without pressing a button with my code. The question was has enigma got a method to grab TSID/ONID that continues to update after the first instance is found.

[Huevos]

Also, if that data was available in the convertor there wouldn't need to be any code change in the plugin. Just changes to the skin. So the real problem is this data is missing from frontendinfo.

[littlesat]

I did not look into it at al yet... but if it is not there it should be made... When it can give a trigger when this info is available we could also add a function to 'poll' it.

[Huevos]

That is exactly the challenge.... (to do it without pressing a button).

Got that working. Pity it is not possible using current enigma code.

 

 screenshot.jpg   74.35KB   5 downloads

[jpuigs]

????

I've finally got it working on my ET10000....  (OP with enigma develop version)

Edited by jpuigs, 18 October 2017 - 19:35.

[jpuigs]

I mean I've got working the window which shows services.

I haven't tried to show TS ID,  ON ID.

[Abu Baniaz]

You will need to add the widgets in your skin

https://github.com/OpenViX/skins/commit/7a6110326ce77ea954f2c783c444704b2610a13e

Attached Files

•  signalfinder.jpg   98.43KB   3 downloads

Edited by Abu Baniaz, 18 October 2017 - 19:55.

[jpuigs]

yes, I know. Thanks.

[Huevos]

I've got a newer version now that continuously updates. So you will see TSID, ONID, and orbital position update as you move the dish to find the correct satellite.

 

https://github.com/H...2f879a4d1ed9662

[Robinson]

Is there a problem to integrate it into OpenPLi?

[littlesat]

Brrrrr polling in a while break loop

Edited by littlesat, 19 October 2017 - 08:35.

[WanWizard]

What is the alternative?

[littlesat]

Trigger on unlock and lock tuner... (by adding a python function on them).

Edited by littlesat, 19 October 2017 - 11:29.

[Huevos]

Trigger on unlock and lock tuner... (by adding a python function on them).

How? Please provide some example code? How can python know of tuner lock without polling something. Is it really such bad coding to test for tuner lock once per second, and only until a short timeout has elapsed?

[Huevos]

@Littlesat, I really don't understand your comments about not polling for tuner lock, because that is precisely what the enigma2 cpp code does. Or did you mean something else?

<  3094.258> [eDVBFrontend] set sequence pos -3
<  3094.258> [eDVBFrontend] sleep 250ms
<  3094.509> [eDVBFrontend] rotor locked step 0 failed (not locked)
<  3094.509> [eDVBFrontend] set sequence pos -3
<  3094.509> [eDVBFrontend] sleep 250ms
<  3094.761> [eDVBFrontend] rotor locked step 0 failed (not locked)
<  3094.761> [eDVBFrontend] set sequence pos -3
<  3094.761> [eDVBFrontend] sleep 250ms
<  3095.011> [eDVBFrontend] rotor locked step 0 failed (not locked)
<  3095.011> [eDVBFrontend] set sequence pos -3
<  3095.011> [eDVBFrontend] sleep 250ms
<  3095.262> [eDVBFrontend] rotor locked step 0 failed (not locked)
<  3095.262> [eDVBFrontend] set sequence pos -3
<  3095.262> [eDVBFrontend] sleep 250ms
<  3095.512> [eDVBFrontend] rotor locked step 0 failed (not locked)
<  3095.512> [eDVBFrontend] set sequence pos -3
<  3095.513> [eDVBFrontend] sleep 250ms
<  3095.852> [eDVBFrontend] rotor locked step 0 failed (not locked)
<  3095.852> [eDVBFrontend] set sequence pos -3
<  3095.852> [eDVBFrontend] sleep 250ms
<  3096.103> [eDVBFrontend] rotor locked step 0 failed (not locked)
<  3096.103> [eDVBFrontend] set sequence pos -3
<  3096.103> [eDVBFrontend] sleep 250ms
<  3096.353> [eDVBFrontend] rotor locked step 0 failed (not locked)
<  3096.354> [eDVBFrontend] set sequence pos -3
<  3096.354> [eDVBFrontend] sleep 250ms
<  3096.604> [eDVBFrontend] rotor locked step 0 failed (not locked)
<  3096.604> [eDVBFrontend] set sequence pos -3
<  3096.604> [eDVBFrontend] sleep 250ms
<  3096.854> [eDVBFrontend] rotor locked step 0 failed (not locked)
<  3096.855> [eDVBFrontend] set sequence pos -3
<  3096.855> [eDVBFrontend] sleep 250ms

[littlesat]

Maybe indeed something needs to be changed to cpp code... I mean let cpp call a python function when the tuner locked... as far I know these functions calls should already be there... that ia where lock/unlock on the ui is coming from... Maybe also a skin renderer showing these valies on a lock change might help...

Edited by littlesat, 20 October 2017 - 13:52.

[Huevos]

Maybe also a skin renderer showing these valies on a lock change might help...

So we have gone full circle now. At the start I suggested auto-updating TSID and ONID values be available in the renderer, but such a thing doesn't currently exist.

 

Also orbital position.

 

And not just fake values from lamedb. Real values from the service information tables like I am currently reading.

Edited by Huevos, 20 October 2017 - 17:28.

[littlesat]

Yep the circel is round.... polling in a while endless lope with delays is not Actually not done..: