forum.pistar.uk

Ok, so it drops off the network, but does it start advertising an Access Point that you can access? Do you have a spare monitor and keyboard you can plug into one of the hotspots and leave attached until a failure occurs and see if you can query the system at that point? And ... are there some nearb...

You say they lock up, but are their dashboards still accessible? Or can you get to the command line (SSH) directly in such situations? It's possible the MMDVMHost program has stalled because it hasn't properly resynced with BM after an internet interruption and/or you've run out of log (tmpfs) space...

(Assuming you're using the lastest version:) migrate from the main dashboard --> admin --> expert --> CSS Tool, and then pick QRZ from the drop-down under the Lookup section, and hit Apply.

For starters, you can simply check the connection status: iwconfig ifconfig And check to see what IP and routing addresses are assigned: hostname -I netstat -r And then scan the logs for more info: grep -shie "wpa_supp\|dhcpcd\|wlan0\|ifup" {/var/log/syslog.1,/var/log/syslog} and check ava...

I think you misread/misunderstood something here: you are not going to being able to connect to the Brandmeister network without an API key. And, if your HS's have been down for year or so, then they are/were probably configured for V1 keys which are obsolete now. You need to update 'em. You can do ...

Well, I'm still unsure of the power fluctuations as a cause, mainly because I haven't been able to correlate to external sources of such fluctuations. What I do see, on occasion, is nevertheless strange: here's an example: : : : : M: 2023-02-03 14:13:14.088 DMR Slot 1, received network voice header ...

I'm thinking more along the lines of voltage sags, not brownouts, not uncommon around here, given the condition of our power lines. Not sure I would notice them much unless the lights flicker; would need to put a long-term power monitor up to verify but who has one of those just laying around? ;) Mo...

[My days of working at the circuit level are long gone so I appreciate your insights here.] Do we know for sure that the errant clocking causes the message to be generated? Is there a way to have the firmware "defense" against this, i.e. to detect the bad clocking and/or the erroneous data...

Been monitoring this problem for a couple months now and from time to time would get the sense noise/interference was the culprit but could never pin it down or correlate it to or even reproduce it with the any of the usual environmental sources. A drifting clock was another thought I had. But what ...

All applicable firmware is up-to-date here. Yet, others may be modifying (and testing) theirs. Who knows?