开云体育

I have my grid square defined in the config.json file. I've updated it manually and by GPS in Pat Menu. Conky is showing my grid square and the "Find Gateways" script sees my grid square,. But when the auto download of the RMS list occurs, it fails with "Grid square not set in Pat Configure".




When "Download Home Grid Gateway List" is run manually from within Pat Menu, it succeeds (the Dec 13, 2021 entry).

What might be causing this problem with the auto download?

Julian

I found the script "getardoplist" in /home/pi/patmenu2. Inside it says:

You are probably using a slightly out of date version of Pat Menu that had an error with the latest Pat Winlink (0.12.x). Run these commands and it should resolve.

cd ~/patmenu2
git pull

BTW.....getarodop-cron is a hidden file in the patmenu2 directory. If you open the terminal, you can see it by running:
ls -a ~/patmenu2
--

On Thu, Dec 16, 2021 at 06:27 AM, km4ack wrote:

You are probably using a slightly out of date version of Pat Menu

Running "git pull" says I'm already up to date.

Based on the notes in the getardop script, it looks like ".getardop-cron" should be the script used in the crontab. I made that change, as a test...
I changed:
30 08 * * * /home/pi/patmenu2/getardoplist
to:
08 30 * * * /home/pi/patmenu2/.getardoplist-cron

...But still got the same error "Grid square not set in Pat Configure". Since it made no difference, I set it back to how it was.

Julian

I found the problem.

Firstly, the script that updates the crontab file creates an entry in the crontab that uses "getardoplist" instead of ".getardoplist-cron".
Secondly, the path to Pat's config file is incorrect in the ".getardoplist-cron" script.

The script ".getardop-cron" is using the wrong path to the Pat configuration file. It references the folder ".wl2k", which no longer exists with the latest version of Pat -- apparently, it got renamed to ".wl2k-old" during an update. The Pat configuration files are now in "/home/pi/.config/pat".

So, the two lines in ".getardoplist-cron" that say:

Those changes will certainly work but you shouldn't have had to go to that much trouble and I suspect you will run into other issues with Pat Menu. Can you tell me which version of BAP you are running? If you aren't sure, run:
grep version ~/pi-build/changelog | head -1

and which branch of Pat Menu are you using? If unsure, run these two commands:
cd ~/patmenu2
git status | head -1

There are two different branches for Pat Menu depending on which version of Pat Winlnk you are running. The Pat Winlink development team changed the location of the data files (mailbox & config) in v0.12.0. Pat Menu should support both and Build a Pi is designed to move you to the correct branch of Pat Menu depending on which version of Pat Winlink you are using. If the "git status" command above returns "master", you can move to the correct branch by running:
git checkout version12
which will sync Pat Winlink with Pat Menu since you have already updated Pat Winlink to v0.12.x

One last question, are you using Buster or Bullseye?
grep VERSION /etc/os-release
--

Hi Jason,

I've been keeping my pi current, both on OS and BAP updates, so there should be no mismatches. I'm still on Buster. The last date on any file in the .wl2k-old file was Nov 5, 2021, so that's when things changed (IE. I did an apt update/upgrade and ran BAP update). I've run updates since then too.

grep version ~/pi-build/changelog | head -1

version=3.1.3

git status | head -1

On branch version12

git checkout version12

M??? .getardoplist-cron
M??? config
D??? setup
Already on 'version12'
Your branch is up to date with 'origin/version12'.

grep VERSION /etc/os-release

VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster

Thanks for the info. This will help in diagnosing the issue.
--

Hi Jason,

Just to keep you up to date... I got another SD card and installed Bullseye, followed by a very limited clean install of BAP. I got PAT and PAT Menu working, but I get the exact same error message "Grid square not set in Pat configure" whenever it tries to automatically download the RMS station list.

Seems there's a problem with the script, rather than Pat?

Thanks,

Julian

Seems there's a problem with the script, rather than Pat?

Yes. There is a bug in the Pat Menu script that I need to run down.

--

I don't mean to be a hassle, but I've run into this issue today when running on a new pi build. Is there a proper fix for this currently? Cheers

On Sun, Feb 20, 2022 at 03:39 PM, Taubin wrote:

I don't mean to be a hassle, but I've run into this issue today when running on a new pi build. Is there a proper fix for this currently? Cheers

Assuming you are running the latest Pat Winlink (0.12.1) and you are running Pi OS Bullseye, run the following commands:
cd ~/patmenu2
git checkout master
git pull
?
--

Thank you Jason,

I did that and it showed me as being current and the latest being pulled already.

I realized however I'm on the 64 bit version of raspbien so I'm re-flashing the 32 bit version. I'm guessing it's an issue with the 64 bit version. 73s

No, it's not limited to the 64-bit version. I'm still on the 32-bit version and have the same problem both with Bullseye (and, if I remember correctly, also with Buster... but not sure of that).

Thank you Jason,

I did that and it showed me as being current and the latest being pulled already.

I realized however I'm on the 64 bit version of raspbien so I'm re-flashing the 32 bit version. I'm guessing it's an issue with the 64 bit version. 73s

Pat won't install with BAP (stable version) on the 64 bit OS as of right now. It is working on the dev version of BAP. It should work fine on the 32 bit version.

No, it's not limited to the 64-bit version. I'm still on the 32-bit version and have the same problem both with Bullseye (and, if I remember correctly, also with Buster... but not sure of that).

Did you try following the directions mentioned in this thread to remedy the issue?

--