forum.pistar.uk

kc7ngc wrote: ↑Mon Dec 23, 2019 6:20 pm I realize OP has reverted back so doesn't have an issue. But posting here just in case someone has same issue:

Thanks, Craig!

Apologies, this must be a recent change in Pi-Star.

Dennis, do you know how to set the system time using the new ntpsec-ntpdate command?

UPDATE: This process doesn't work for Pi-Star 4.1.x. For the updated process, see the post by KC7NGC below. Hi Ian, The RPi uses Network Time Protocol (NTP) to synchronize its clock to UTC. In some cases, the time may get out of sync. In that case, you can simply restart the RPi and the NTP daemon s...

Same good initial results with a 3A+ hotspot.

You tried the solution provided by kc7ngc ? Since I installed the PI3 A + it works perfectly. So far it has not failed in any startup, and I have done many. Not yet. So far, I've just getting all my hotspots on RC7. With several of them, that has meant starting with a fresh image, so it has been a ...

You tried the solution provided by kc7ngc ? Since I installed the PI3 A + it works perfectly. So far it has not failed in any startup, and I have done many. Not yet. So far, I've just getting all my hotspots on RC7. With several of them, that has meant starting with a fresh image, so it has been a ...

Interesting.

After a day and a half of things appearing to work better, I'm experiencing this issue again this morning.

"my 4 digit code": Do you mean your callsign? If yes, that gets entered on the Configuration page > General Configuration > Node callsign.

Try a different DMR Master.

I'm noticing only one minor issue: when I'm first configuring my wireless network for the RC7 image and choose my country code, US, then scan for network, the country code appears to get set back to JP. If I select US again, and then select my network, enter my PSK, and click Save (and connect), it ...