Re: Is this even possible?
Cort N0MJS <n0mjs@...>
When I started this, there was DMRlink – MMDVM didn’t yet exist. After I wrote HBlink, I still developed on DMRlink first, and then ported changes to HBlink, but have kept pretty good parity between both of them.
As of now, I’d say the best determining factor would be what kind of repeaters do you have more of? Motorola or MMDVM? That’s the advice I typically give. If you’re predominantly a Motorola operation, then use DMRlink’s confbridge.py as the main hub; if MMDVM, then use hb_confbridge.py.
But this is about to change. Going forward, now that HBlink has OpenBridge support, HBlink will be what gets developed first – and at some point, I may even sunset further development on DMRlink applications (e.g. confbridge.py). Using multiple IPSC connections to a c-Bridge to pick up TGIDs (or multiple HBP connections to Brandmeister, etc.) is cumbersome. OpenBridge allows “server-to-server” type access to Brandmeister, DMR-MARC and DMR+, and that’s my reason for shifting primary development (and there’s about to be quite a bit of it) to HBlink first.
I’d like to see a few improvements in IPSC_Bridge, and hopefully can contribute to them. Even on K0USY Group’s systems, it looks like the future will be trading out our XPR series repeaters for MMDMV-based ones, or putting a “backpack” on each one (SBC running IPSC_Bridge/HB_Bridge) and converting them all to Homebrew at the repeater site. I’ll likely keep one XPR for DMRlink development, but that’s probably it.
0x49 DE N0MJS
P.S. - if anyone is in the market for lightly used (I run the power at 25W on them and NEVER burn up PAs that way) K0USY Group will soon have a number of XPR8300s and XPR8400s available for sale or trade for MTR2000s.