Closed lars18th closed 2 years ago
Hi @catalinii ,
The patch is ready to merge.
@lars18th I am fonfused related to the assumption that e2 will always report db always.
As every driver developer is free to use whichever measurement this ia probably not a generic implementation.
Thank you
Hi @catalinii ,
As I writed in https://github.com/catalinii/minisatip/issues/911#issuecomment-1048029529 I'm working on fixing this. However, it will be preferable to merge this PR. Then it will be more easy to fix it. Please think that this patch incorporates more tunning maps, fixes the calculation of dB->Signal, and adds the dB conversion to the get_signal()
function as well.
Regards.
Can we merge this? If there's anything that could be improved it could be done in a new PR?
@lars18th merged this one, but please submit a PR later about the enigma2 handling of relative (non db) measures
Hi @catalinii ,
@lars18th merged this one, but please submit a PR later about the enigma2 handling of relative (non db) measures
Yes. It's already in my TODO list. And my strategy for the next PR is this:
I hope you agree with this. Regards.
When the DVB adapter reports dB signal, fix the result value (it's less in the order of 100 smaller times). For Enigma STB devices assume that the driver reports dB allways.