"Not Linked" - but connected and TX/RX work.

Help with P25 issues
Post Reply
N6MIK
Posts: 59
Joined: Wed Apr 18, 2018 12:53 am

"Not Linked" - but connected and TX/RX work.

Post by N6MIK »

Running 4.1.6 on multiple hotspots, and have noticed that the P25 Network field on the dashboard reverts to "Not Linked", while the connection to the reflector remains up and active.

This appears to happen if the hotspot does not receive a local/RF transmission on P25 for some period of time. The last heard list on the dashboard updates as expected and TX and RX work fine.

Anyone else seeing this?
User avatar
AA1PR
Posts: 12
Joined: Thu Jun 25, 2020 5:00 am

Re: "Not Linked" - but connected and TX/RX work.

Post by AA1PR »

yes I just setup a 2nd duplex hotspot for all my fusion activities and I am getting the same error

it was just workign on my old HS a few days ago

Ive updated all firmware etc
ns2b
Posts: 11
Joined: Tue Apr 28, 2020 12:19 pm

Re: "Not Linked" - but connected and TX/RX work.

Post by ns2b »

I too am experiencing the same thing.

I've chased it to 2 scenarios - I think...

Scenario 1

On a fresh boot and you have a startup TG selected - it will show "Not linked" even though it is.
/var/www/dashboard/mmdvmhost/functions.php is missing this phrase in the P25 section:

if (strpos($logLine,"Statically linked to reflector")) {
$to = preg_replace('/[^0-9]/', '', substr($logLine, 55, 5));
$to = preg_replace('/[^0-9]/', '', $to);
return "TG ".$to;
}

Scenario 2

When P25Gateway reloads P25Hosts.txt and P25HostsLocal.txt at the default 60 minute interval, it appears it overwrites the P25Gateway log and the dashboard no longer has any source of knowledge of what TG you may or may not be linked to.

Just observations from my end - your mileage may vary...

Bob, NS2B
Post Reply