Page 4 of 4

Re: mmdvm's connect ok and after a period of days or hours ignore pi-star.local access

Posted: Mon Dec 09, 2019 4:59 am
by w9mt
Ok, I've got the old load 3.4.17 running in pi-star0 mmdvm (YSF) and the 4.1.0-RC4 new beta load running in the DMR mmdvm now entitled pi-star2a. (I kept the old sdhc chip containing name pi-star2 with its old 01/2019 3.4.17 load using the same DMR settings.)

My heart sank when the new DMR pi-star load went "ignorant" to dashboard queries and simple updates to the info on an open and active dashboard tab on my laptop. The YSF older load on the other mmdvm also froze to queries a few hours later.

I had a hamfest to go to that day and didn't bother rebooting or resetting anything. Then something weird happened...

When I got back from Mesa AZ (near PHX) and back to my AZ QTH in Vail AZ (near Tucson) about 12 hours later, both mmdvm's were again responding (sometimes albeit more slowly) to dashboard queries again. This is Sunday night, more than another day later and they STILL are behaving.

I really don't like things that "fix themselves", as they usually "unfix themselves" at some future point. I did NOT do the command line interface suggestion that another poster had recommended for the RPi "power_save" disabling function, either.

Anyone have any idea what is haunting my home network? (For now things seem to be running and I'm going to leave them alone and see what develops !!!)

Re: mmdvm's connect ok and after a period of days or hours ignore pi-star.local access

Posted: Mon Dec 09, 2019 7:44 pm
by KE7FNS
w9mt wrote:
Mon Dec 09, 2019 4:59 am
I did NOT do the command line interface suggestion that another poster had recommended for the RPi "power_save" disabling function, either.
OMG, WHY???? I explained it a day or so ago...
KE7FNS wrote:
Sat Dec 07, 2019 8:47 pm
To the OP can you just post the result of the wifi power save query? Its driving me nuts you have taken this long for such a simple thing. I understand your step by step procedures you are following, but that command I posted doesn't change or set anything it just tells you what it is set to, so it can't affect any of your tests.
You only have to run the command on the old 3.4.17 configuration, we already know what that setting is in 4.1, we don't know what your current 3.4.17 setting is.

Re: mmdvm's connect ok and after a period of days or hours ignore pi-star.local access

Posted: Wed Dec 11, 2019 4:03 am
by w9mt
Because it was the newer 4.0 load that failed and turned "ignorant" on Saturday morning prior to my drive to a distant hamfest.

When I got home, both of my mmdvm's with the new 4.0 load (DMR) and the old load 3.4.17 (Fusion) both started working. They have not failed since.

Nothing's currently broken, so right now there's nothing to fix. I'm gonna let the "sleeping dog lie".

Rest assured, if the problem returns, the recommended CLI function will be the first thing I will try in order to get more data, and then proceed from there.

For now, I'd be chasing something that's perfectly functional. I'll let if fail first, or just let it run forever...be it the mystery it is....

Tony (W9MT)

Re: mmdvm's connect ok and after a period of days or hours ignore pi-star.local access

Posted: Wed Dec 11, 2019 6:19 am
by KE7FNS
w9mt wrote:
Wed Dec 11, 2019 4:03 am
For now, I'd be chasing something that's perfectly functional. I'll let if fail first, or just let it run forever...be it the mystery it is....
No, you wouldn't. The command I asked you to run and post the results of DOES NOT MODIFY ANY SETTINGS. It just tells you what the current wifi power save setting is set to. I've explained that in multiple posts now and somehow you still haven't understood it.

You can get that information right this second without disturbing your precious sleeping dog.

Re: mmdvm's connect ok and after a period of days or hours ignore pi-star.local access

Posted: Wed Dec 11, 2019 4:07 pm
by w9mt
No, I understood you quite well.

I just have other fish to fry, and when I get to it, I will be happy to post the exact results. I am just as curious to examine the state of the setting as you are, but the holidays are coming. I've neglected stuff that needs to be done around the house, and this issue and getting a Hardrock 50 amp I bought for my FT-817, supposedly "like new" at a hamfest (it didn't work either) truly turned my 50 year ham radio hobby into an all-encompassing obsession for the past several weeks.

It's time to change direction and come back to this later. I'd also like to see how long this continues to work. So, that's MY choice. I will be stopping the pursuit for now at this point. But, I truly appreciated your recommendation and rest assured, it WILL happen, and I'll report it back here at that time for all to benefit from and see.

So, don't let this trouble you. I'm sure whatever the normal default for that setting should be is what it is, not only for me, but all pi-star users.

73, and best of the holiday season...and stay tuned...
Tony (W9MT)

Re: mmdvm's connect ok and after a period of days or hours ignore pi-star.local access

Posted: Sun Dec 15, 2019 7:35 pm
by w9mt
No, I haven't changed anything further in today's current set up's from what I previously posted, but I'm seeing what looks like a suspicious correlation...

In AZ, I live in an area with Cox's high speed internet. I pay for 300Mbps service so throughput right now shouldn't be a concern...when things are working. Intermittent drops in the connection to the cable modem recently have been common. With my area exploding in population (hundreds of new houses going in, and plans for up to 6000 to be eventually built), the neighborhood blog has been complaining about wide spread outages lasting from many minutes to hours.

When I bought my first assembled mmdvm, and then built two more from kits, I was at my alternate QTH in IL, where I have Comcast's Xfinity service (250Mbps, max). There was not one single drop in service at that street address from the time I put the mmdvm's into service until I brought them to AZ in October.

That's when the trouble began. I'm beginning to think that the pi-star software may have been doing a data transaction over the wider Internet during one of the spotty drops which lead the software into some kind of indeterminant state, causing my originally described "ignorant to dashboard requests over local wifi" issue and drops in communications on DMR and YSF (especially) during QSO's whilst ignorant to wifi queries on the home network.

I've recently queried my D-LInk C500 DOCSYS 3.0 cable modem, and the "critical" events (including the "wifi ignorant response" ones seem to be correlating from a time and date stamp comparison.

I've also noticed that the service connection drops have seemed to have stopped this past week and I haven't had a single problem from the mmdvm's.

Coincidence? I don't think so, but I really cannot say with 100% certainty, and will continue to monitor the situation.