Suggestion for setting frequencies once for RX888 and other ka9q dependant hardware

[waterwin]

Frequency settings are now made in the wsprdaemon.conf file as well as in the radiod@.. conf file

For the Kiwi the settings are taken directly from wsprdaemon.conf without the need to repeat them in a hardware related conf file.

[mijahauan]

Agreed! Phil designed radiod with the ability both to dynamically create receivers and to configure them all ahead of time. At the outset of using ka9q-radio with wsprdaemon it was expedient to simply match the frequency definitions. But, keeping two lists when one will do is inefficient and prone to error.

Having wsprdaemon simply direct radiod to what it wants to listen to (like with the kiwi) has been on the list of wd improvements for some time.

[rrobinett]

I of course would prefer there be no need to duplicate and coordinate configurations, but there is a tradeoff in doing so with the current KA9Q-radio code: If WD were to dynamically instruct radiod to start sending a new demodulated channel, that channel would be sent to its own multicast destination address. Since many WD systems run 50 or more receive channels, the CPU of the ethernet which would be heavily burdened by inspecting each packet all those multicast streams. There are of course ways to avoid those burdens, but they will require significant changes in both KA9Q-radio and WD. Since I haven't seen many problems with the current separate configurations, consolidating configurations is currently down my TODO list.

…

On Fri, Feb 28, 2025 at 5:36 AM Michael James Hauan < ***@***.***> wrote: Agreed! Phil designed radiod with the ability both to dynamically create receivers and to configure them all ahead of time. At the outset of using ka9q-radio with wsprdaemon it was expedient to simply match the frequency definitions. But, keeping two lists when one will do is inefficient and prone to error. Having wsprdaemon simply direct radiod to what it wants to listen to (like with the kiwi) has been on the list of wd improvements for some time. — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIFAQZAEWVZSOWVMMOAKIYT2SBQ4FAVCNFSM6AAAAABX7RI7Q2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJQGY3DOMJUGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> [image: mijahauan]*mijahauan* left a comment (rrobinett/wsprdaemon#37) <#37 (comment)> Agreed! Phil designed radiod with the ability both to dynamically create receivers and to configure them all ahead of time. At the outset of using ka9q-radio with wsprdaemon it was expedient to simply match the frequency definitions. But, keeping two lists when one will do is inefficient and prone to error. Having wsprdaemon simply direct radiod to what it wants to listen to (like with the kiwi) has been on the list of wd improvements for some time. — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIFAQZAEWVZSOWVMMOAKIYT2SBQ4FAVCNFSM6AAAAABX7RI7Q2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJQGY3DOMJUGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Rob Robinett AI6VN ***@***.*** mobile: +1 650 218 8896