Once again, thank you to the OP25 developers for such a great project!
The back story:
I have an RPi 3B+ running OP25-Boatbod, with a single RTL-SDR, monitoring a single control channel, and it works very well!
I tinker a bit with electronics, so I designed an RPI "Hat" that has a stereo - to - mono mixer, and an audio amp.
It additionally has several push button switches and LEDs.
On boot-up, it loads a particular configuration of the rx.py command with its associated white list.
One can select any of four modes of operation by pushing the respective push button switch.
The RPi de-selects the current mode, and selects the new mode, (new white list, etc.).
I can listen to just the local FD/EMS, or FD/EMS & local PD, or to the regional TG's of interest, or to any traffic on the system, (essentially a test mode).
The 5th PB switch tells the RPi to shut down, prior to turning off it's power.
With this little setup I can essentially have a headless 800 MHz radio, as I don't require the monitor, KB, and mouse to shut things down when needed, and I can easily select from several pre-configured setups with the push of a button.
Unfortunately, when there is no voice traffic, one hears some "computer noise" through the speaker.
When there is voice traffic, one can't hear the computer noise.
When there is no voice traffic it gets annoying with the constant background noise.
I believe that much of the noise is coupled through the power supply rail, while some of it is directly radiated, (EMI), from the RPI's PCB that sits right below it.
I can certainly make a new and improved Hat with better power supply filtering, but that really won't completely eliminate the noise.
Now, after that long winded intro, the suggestion:
It would be really great if down the road there was an up-dated version of the program that include one more option for the command line.
That option would be to enable an RPi's GPIO pin/line/signal as a Mute Audio signal.
Many small amplifier chips have a mute control input, which allows a radio's microcontroller to totally mute the audio output when tuning between stations.
In this case, when OP25 is just listening / scanning and there is no audio traffic to play, the mute signal could be used to totally silence the speaker output.
When the system is playing a talk-group's audio, the signal would enable the audio amplifier to play the voice traffic.
This option would only make sense for those running OP25 on an RPi, not on a PC.
The Mute flag on the rx.py command line could have a parameter that let the user select the RPI GPIO pin to use for the signal.
e.g. rx.py ...... -- mute 12 ... would route the mute signal to GPIO 12.
As some audio amp chips use a High to Mute signal, and others use a Low to Mute signal, one could get fancy and use a parameter of 12 for GPIO 12, High to Mute, or add 100 to the parameter and have 112 for GPIO 12, Low to Mute.
I throw this out there only as a suggestion to perhaps add to the future development wish list!
I know that everyone's time is valuable, and that higher priorities exist.
Once again, thank you for OP25, it is a great project!
Jay
The back story:
I have an RPi 3B+ running OP25-Boatbod, with a single RTL-SDR, monitoring a single control channel, and it works very well!
I tinker a bit with electronics, so I designed an RPI "Hat" that has a stereo - to - mono mixer, and an audio amp.
It additionally has several push button switches and LEDs.
On boot-up, it loads a particular configuration of the rx.py command with its associated white list.
One can select any of four modes of operation by pushing the respective push button switch.
The RPi de-selects the current mode, and selects the new mode, (new white list, etc.).
I can listen to just the local FD/EMS, or FD/EMS & local PD, or to the regional TG's of interest, or to any traffic on the system, (essentially a test mode).
The 5th PB switch tells the RPi to shut down, prior to turning off it's power.
With this little setup I can essentially have a headless 800 MHz radio, as I don't require the monitor, KB, and mouse to shut things down when needed, and I can easily select from several pre-configured setups with the push of a button.
Unfortunately, when there is no voice traffic, one hears some "computer noise" through the speaker.
When there is voice traffic, one can't hear the computer noise.
When there is no voice traffic it gets annoying with the constant background noise.
I believe that much of the noise is coupled through the power supply rail, while some of it is directly radiated, (EMI), from the RPI's PCB that sits right below it.
I can certainly make a new and improved Hat with better power supply filtering, but that really won't completely eliminate the noise.
Now, after that long winded intro, the suggestion:
It would be really great if down the road there was an up-dated version of the program that include one more option for the command line.
That option would be to enable an RPi's GPIO pin/line/signal as a Mute Audio signal.
Many small amplifier chips have a mute control input, which allows a radio's microcontroller to totally mute the audio output when tuning between stations.
In this case, when OP25 is just listening / scanning and there is no audio traffic to play, the mute signal could be used to totally silence the speaker output.
When the system is playing a talk-group's audio, the signal would enable the audio amplifier to play the voice traffic.
This option would only make sense for those running OP25 on an RPi, not on a PC.
The Mute flag on the rx.py command line could have a parameter that let the user select the RPI GPIO pin to use for the signal.
e.g. rx.py ...... -- mute 12 ... would route the mute signal to GPIO 12.
As some audio amp chips use a High to Mute signal, and others use a Low to Mute signal, one could get fancy and use a parameter of 12 for GPIO 12, High to Mute, or add 100 to the parameter and have 112 for GPIO 12, Low to Mute.
I throw this out there only as a suggestion to perhaps add to the future development wish list!
I know that everyone's time is valuable, and that higher priorities exist.
Once again, thank you for OP25, it is a great project!
Jay
Last edited: