Just a thought, Simon - it may not be useful, and I wouldn't want to divert attention from more important things.
Under poor conditions, the displayed PI code may be absent for much of the time and vary when there is something to show.
The user will not remember the set of PI values and may not have a reliable impression of the most frequent.
Could there be an option to log and review these?
Understood it would have a performance penalty, would need "start" and "stop" actions, ought be used sparingly, and only during recording playback.
Maybe each new log session should delete previous log entries.
An off-the-cuff proposal is for a summary of Block 1 values, grouped by PI value and Boolean 'checksum-valid' (and DX Mode?), with "record" count.
Perhaps a text version of the table could be saved on demand as "evidence" (annotated with tuned frequency and start/stop date-times).
This may be less helpful for sporadic (mixed) reception, but it's all I can think of at the moment.
RDS Statistics
RDS Statistics
Paul White (Grumpy Old Git)
Re: RDS Statistics
Paul... there already is!
Receive.. Broadcast FM... Show Database.
I agree it could be worded better, maybe "Show RDS Log".
Receive.. Broadcast FM... Show Database.
I agree it could be worded better, maybe "Show RDS Log".
Jim, Bournemouth IO90BR
Re: RDS Statistics
Paul White (Grumpy Old Git)
- Simon G4ELI
- Posts: 2134
- Joined: Thu Aug 06, 2020 7:27 am
- Location: Mawnan Smith
- Contact:
Re: RDS Statistics
Just FWIW I may take a week in January to display the annotated bit stream so I can possibly improve the bit detection in a marginal situation.