Integrate stats available via dvbv5

[jaredmauch]

There are additional statistics which may be better available to diagnose signal strength related issues.

dvb-fe-tool -v -m

can report suitable statistics including the Signal:Noise or Carrier:Noise ratio in dBm

print_frontend_stats provides examples

I intend to submit a pull request that would cause the printing of statistics such as Info: DVB: Bit error rate: -1 Signal strength: 64224 SNR: 260 Uncorrected blocks: 0

to be replaced with appropriate stats such as:

Lock (0x1f) Signal= -66.00dBm C/N= 26.01dB

for places that currently display statistics like:

Info:  Tune:  Strength:      63568
Info:  Tune:  SNR:        258
Info:  Tune:  Event:  Frequency: 581000000
Info:  Tune:  Bit error rate: -1
Info:  Tune:  Signal strength: 63568
Info:  Tune:  SNR: 260
Info:  Main:  Card 1, tuner 0 tuned

Ideally this would also be passed through to the other data locations that would flow through to the json and other outputs.

[braice]

I think it is a good idea.

As far as I remember some cards do not report dBm so it might be interesting to keep the arb units values too just in case

Brice

On Sat, Jan 14, 2023, 19:19 Jared Mauch @.***> wrote:

There are additional statistics which may be better available to diagnose signal strength related issues.

dvb-fe-tool -v -m

can report suitable statistics including the Signal:Noise or Carrier:Noise ratio in dBm

print_frontend_stats provides examples

I intend to submit a pull request that would cause the printing of statistics such as Info: DVB: Bit error rate: -1 Signal strength: 64224 SNR: 260 Uncorrected blocks: 0

to be replaced with appropriate stats such as:

Lock (0x1f) Signal= -66.00dBm C/N= 26.01dB

for places that currently display statistics like:

Info: Tune: Strength: 63568 Info: Tune: SNR: 258 Info: Tune: Event: Frequency: 581000000 Info: Tune: Bit error rate: -1 Info: Tune: Signal strength: 63568 Info: Tune: SNR: 260 Info: Main: Card 1, tuner 0 tuned

Ideally this would also be passed through to the other data locations that would flow through to the json and other outputs.

— Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/304, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACRID33OC4OYH3M64XTZM3WSLUZZANCNFSM6AAAAAAT3MYFHU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[SonnyWalkman]

Yes please! Include a signal lock Boolean to allow for quick validation of signal.

Is there a way to convert the values to 0-100 for bar graph (calculations to give db etc)?

[braice]

Hello

I would be happy to review your pull request on that !

On the 0-100 question, that depends on the typical expected values, and I am not sure what limits would be relevant.

Brice

On Sun, Jun 25, 2023 at 5:41 AM Sonny Walkman @.***> wrote:

Yes please! Include a signal lock Boolean to allow for quick validation of signal.

Is there a way to convert the values to 0-100 for bar graph (calculations to give db etc)?

— Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/304#issuecomment-1605850892, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACRIDYWQH6BT66L3BDDN43XM6XP5ANCNFSM6AAAAAAT3MYFHU . You are receiving this because you commented.Message ID: @.***>