forum.pistar.uk

I have a similar issue, but in my case, my repeater shows up as a hotspot also. I figured I would go mess with the altitude and see if I could correct that, and the altitude setting is greyed-out for both.

My other repeater is not running MMDVM/Pi-Star and I can change that altitude...

Strange?

Wow. Yeah, that’s way over my head! Thank you for the explanation about how it works!

I have a P25 reflector, and I'd like it to 'announce itself' the way "Worldwide", "North America" and others do, upon first transmission. How is this done?

Thanks!
N6MIK

Thanks - I thought that was it, but with the version number so far off from 1.3.6, I'm wondering if I should try to force an update or let it ride...

How does one tell what version of FW is running?
I've got "FW: MMDVM:20170501" showing on the dashboard, running on an MMDVM_HS from the Zumspot guys, that that seems counterintuitive with the 1.3.6 release number.

There are a handful of 'patched' talkgroups that I'm aware of. They seem to be associated with a particular repeater group or club (as opposed to a geographic region, for example). 31665 is linked full time and has a multi-mode net on Fridays. The patching is transparent to the end-user; you configu...

Brandmeister requires a DMR radio for access. That said, there are some folks that are 'patching' other digital modes into Brandmeisger on specific talkgroups. For example - TG31665 is available in the pi-star P25Hosts and is connected to Brandmeister TG31665...

...Give it a try and let me know how that works for you an alternative would be to set up a p25 reflector and point unwanted talk groups to it. I've got a P25 Reflector running, so I ran a tail of the log while I transmitted on the 'intended' TG for the reflector and verified the logs. I then switc...

Thanks for that explanation - it helps tremendously!

For a "local" TG then - it seems I need to stick the local TG into the hosts file with a bogus IP address (or 127.0.0.1?) so it pulls traffic away from the networked group, but it doesn't route anywhere. Is that right?

Thank you Andy. I took another look at the history - and TG0 only happens with significant loss percentages. In my case, 7 of the last 10 activity log entries were "TG0" and between 6% and 22% 'loss', and all were unique callsigns. Is loss tied to high BER on the remote side, or more of a ...