Mostly just wanted to share a thanks and success story on OP25 (boatbod).
Over the past month I've moved from initial setup and trial, to now having a pretty rocksolid multi receiver setup. Will include a little bit of what I have setup, and some of the challenges I found but managed to overcome by searching through various posts and tutorials.
My setup:
- I'm in Australia, Victoria to be a little more specific.
- Our main public service radio system is P25 trunked and split across a 165MHz component and a 420MHz component. Some users operate on only 1 of those, and some operate on both, through a combination of patches, and separate channel selection. So it can be a challenging one to scan to a satisfactory level unless you have multiple scanners running
- So, I'm not running 2 receivers
- Pi4 - mainly headless
- multi-rx
- icecast
- web interface
- So the 2 receivers go to the 1 web interface and I use the buttons on that to change viewing between the 2 sites
- I have icecast streaming to 2 separate addresses. When using a computer to listen, I can open up both streams, while on phone I pick which one I want at the time
This enables me to use VLC and browsers on my main computer or phone or ipad depending on what I'm doing, and with a VPN to home I can easily access wherever I am.
The 'Journey'
- I started out using a single receiver, rx.py. Intially with local audio, and then very quickly moved to icecast. This was mostly quite straightforward and I had good results coming through except for when I was starting to test a few things. I recall having a couple of challenges with icecast early on and managed to iron those out after some searching and correcting some updates.
- I experimented with tracking different sites, and particularly trying some more distant sites to receive traffic I don't normally receive at home. I found that OP25 was best left to work on a site with more certain coverage, as it's a little cumbersome the way it drops out and then works to change to the next CC. I may return to that at some point, or even add another receiver for that task
- After getting good results with this, I considered running 2 instances of rx.py, but decided to jump in to multi instead. Well, that was a whole new set of banging head on desk as I figured out what was the same and what operated differently, and how it all worked together.
- Only a little bit of banging head, and I had managed to get the 2 receivers working and the 2 icecast streams working (I've probably found the icecast side the more challenging)
- the last piece of the puzzle that I've just solved is getting everything to work on autostart so it can get up and running remotely without input. I probably need to figure a way to make sure I can boot it if we have a power loss, but at least from power on, it does everything needed to start listening remotely again. I've done service enables before but had a few issues, and then the last hurdle was having to update the user path to the apps directory (d;oh!)
- The one unesolved challenge is whether I can get RID/alias to display in metadata to VLC like I could with rx.py. I attempted the same syntax in the config json for multi_rx and it did not like me.
I've found the pi/linux route so much easier to get good trunking and audio than the troubles I had in the past with unitrunker and DSD, particularly once systems in our area went to digital. And OP25 is a nice easy to execute solution. For those who are struggling with it, I recommend working through it and just taking your time. Sure beats the money spent on a single Uniden scanner!
Over the past month I've moved from initial setup and trial, to now having a pretty rocksolid multi receiver setup. Will include a little bit of what I have setup, and some of the challenges I found but managed to overcome by searching through various posts and tutorials.
My setup:
- I'm in Australia, Victoria to be a little more specific.
- Our main public service radio system is P25 trunked and split across a 165MHz component and a 420MHz component. Some users operate on only 1 of those, and some operate on both, through a combination of patches, and separate channel selection. So it can be a challenging one to scan to a satisfactory level unless you have multiple scanners running
- So, I'm not running 2 receivers
- Pi4 - mainly headless
- multi-rx
- icecast
- web interface
- So the 2 receivers go to the 1 web interface and I use the buttons on that to change viewing between the 2 sites
- I have icecast streaming to 2 separate addresses. When using a computer to listen, I can open up both streams, while on phone I pick which one I want at the time
This enables me to use VLC and browsers on my main computer or phone or ipad depending on what I'm doing, and with a VPN to home I can easily access wherever I am.
The 'Journey'
- I started out using a single receiver, rx.py. Intially with local audio, and then very quickly moved to icecast. This was mostly quite straightforward and I had good results coming through except for when I was starting to test a few things. I recall having a couple of challenges with icecast early on and managed to iron those out after some searching and correcting some updates.
- I experimented with tracking different sites, and particularly trying some more distant sites to receive traffic I don't normally receive at home. I found that OP25 was best left to work on a site with more certain coverage, as it's a little cumbersome the way it drops out and then works to change to the next CC. I may return to that at some point, or even add another receiver for that task
- After getting good results with this, I considered running 2 instances of rx.py, but decided to jump in to multi instead. Well, that was a whole new set of banging head on desk as I figured out what was the same and what operated differently, and how it all worked together.
- Only a little bit of banging head, and I had managed to get the 2 receivers working and the 2 icecast streams working (I've probably found the icecast side the more challenging)
- the last piece of the puzzle that I've just solved is getting everything to work on autostart so it can get up and running remotely without input. I probably need to figure a way to make sure I can boot it if we have a power loss, but at least from power on, it does everything needed to start listening remotely again. I've done service enables before but had a few issues, and then the last hurdle was having to update the user path to the apps directory (d;oh!)
- The one unesolved challenge is whether I can get RID/alias to display in metadata to VLC like I could with rx.py. I attempted the same syntax in the config json for multi_rx and it did not like me.
I've found the pi/linux route so much easier to get good trunking and audio than the troubles I had in the past with unitrunker and DSD, particularly once systems in our area went to digital. And OP25 is a nice easy to execute solution. For those who are struggling with it, I recommend working through it and just taking your time. Sure beats the money spent on a single Uniden scanner!