64 replies to this topic

[littlesat]

Can you put tuned type and the calculation here?

[moli87]

Do you mean tuner type of both VU+?

[littlesat]

Just 'tuner-tuner' type (not model of receiver) with the calculation...

[moli87]

is there a command to use in terminal to get that info?

[littlesat]

Menu information then 2nd option (your receiver) and then check detected tuners

[moli87]

Hi,

 

sorry for the late response....

 

Solo4k:

 

Tuner A-H        Vuplus DVB-S NIM (7376 FBC) (DVB-S2)

Tuner I-J          Vuplus DVB-C NIM (SSH108) (DVB-C)

 

Duo4k:

 

Tuner A-H       Vuplus DVB-S NIM (45308x FBC) (DVB-S2x)

Tuner I-P         Vuplus DVB-C NIM (BCM3158) (DVB-C)

 

The calculation is working for both receiver with different tuners. Same Values.

 

Still no time to try to implement it in Frontend.cpp

Edited by moli87, 13 May 2020 - 00:05.

[littlesat]

And the calculation formular per tuner?

Edited by littlesat, 13 May 2020 - 06:32.

[moli87]

i did implement this one we were talking about in this thread.....

 

return "%3.1f dB" % (((self.source.snr / (65536.0 / 100.0)) * 0.1800) - 1.0000)

 

I did implement this line into each release of FrontendInfo.py, cause the solo4k have openpli 6.2 and the duo4k have openpli 7.2 and it is working for both tuners, both receiver with same values. Everything is working now, no issues or something missing. 

 

For me just perfect.

 

Cheers,

Edited by moli87, 14 May 2020 - 00:33.

[littlesat]

This should be moved frontend.cpp.... it would be helpfull to get an overview tuner type vs formuler... so I can implement it in one go.... frontend.py is not the good place... (unless we decide to move all calculations to python but all of them are now in cpp)

Or is this the same for all the dvb-s tuners above? For dvb-c I need a different formula

Where did you get the formula from

Edited by littlesat, 14 May 2020 - 06:48.

[Abu Baniaz]

I think benefit of being in the py file as people can edit and test and report back changes. CPP needs a build.

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

[littlesat]

Yep I know... but moving it into py means we need remove it from cpp. And then for all tuner types... In addition in renderers in python we should keep the code as simple as possible to gain performance. So keeping it into cpp isn't a bad place... And it is an one time thing for each type of tuner...

 

I still do not have an overview so I can add it in cpp...

Edited by littlesat, 14 May 2020 - 13:44.

[littlesat]

But I see OpenATV did include it partly

 

for 7376 FBC

https://github.com/o...ntend.cpp#L1438

 

for BCM3158

https://github.com/o...ntend.cpp#L1438

 

Also missing there:

Vuplus DVB-C NIM (SSH108)

Vuplus DVB-S NIM (45308x FBC)

 

So I need formulars for these two...

Edited by littlesat, 14 May 2020 - 13:48.

[Stosun]

Interestingly, in the AeonFHDmod skin it works without a problem.

[littlesat]

Skins can add as ugly and bad it is their own renderers in python code.... and in there they could as terrible it is their own calculations.... which is actually not done... Ok it works but it is not how it should work! It is quick and dirty!

[Stosun]

It may be fast and dirty, but it works. It also fits with the satelite finder.

 

[Stosun]

I wanted to write that the db also matches the satellite finder

[littlesat]

To get the match in satfinder you need to put it in cpp... this proves hacking the renderer is not done.
But it works is not the openpli style!

Edited by littlesat, 14 May 2020 - 17:17.

[moli87]

Yes it is the same, which i used for both receiver and it is working for both receiver with both tuner (Sat and Cable) There is no different calculation for cable. It works with just that line in FrontendInfo.py:

 

 return "%3.1f dB" % (((self.source.snr / (65536.0 / 100.0)) * 0.1800) - 1.0000)

 

Stosun, just wanna told you that it is working also for the satellite finder. Nothing other needed and no crashes! Yeah it is a quick and dirty fix but it works like i want. 

As i started this thread i did never ask to implement this formula into the image releases, instead of that i did ask where i can find that file to implement it myself and maybe some others can do it also by themself.

 

I really dont get what you are asking for, cause i did nothing more. I did implement 1 line into the FrontendInfo.py as i did it already 3 years ago. 

 

No other formula for cable or something else what you are asking for. And i got same Values for the tuners.

[littlesat]

Please be a bit patience... I have something prepared... 

[Stosun]

moli87

 

 return "%3.1f dB" % (((self.source.snr / (65536.0 / 100.0)) * 0.1800) - 1.0000)

 

Does it matter where you insert the line? Can it be at the end of the sheet?