开云体育

1. I installed pat winlink from the website, last week, on an rpi 4b 4g buster.? It was working fine.? I could make telnet connections to send and receive.
2.? I installed ardop in case I need this pi in a pinch for RF connections.? It installed and runs fine.

so far so good.

3. I figured I would also add the pat menu to this pi, for the benfits of easy ardop launch, and the pat menu catalog (propagation reports, GPS weather reports, rms list, etc.).? It appeared to install fine.? The ardop modem launched.? But when I tried using the catalog to request a GPS weather, or propagation report, a popup dialog said the appropriate message was being posted to the outbox.? I was then told to go make a connection.? I first looked in the outbox to see if all the requests were there properly, as in other BAP installs.? There was nothing in the outbox.

As I type this, I am making another propagation report request on a different BAP (pi4b 8g bullseye).? The request properly appeared in *that* outbox.? I connected on *that* BAP in order to send out the request.? I did NOT make a second connection from *that* BAP.? The response should be sitting on the server waiting for me to make another connection to retrieve the response.

...

I am now back at this problematic pi (4b 4g buster) and making a connection to see if *this* inbox will fetch and have the resulting requested report.
connecting.... yes, it does.? But *this* pi, on which I singly installed pat winlink, successfully, ardop, successfully, and then pat menu, is not properly finding and posting requests to its outbox.

I have not tested anything else pat menu related on *this* buster pi.? This is a highly customized daily desktop purposed rpi, and I did not want to run the full BAP script on it (which I suppose would have given it the same versions, working, as on the bullseye pi4b8g).

If I compose a simple TEST@...? message on *this* buster pi, since the pat menu install, it works, so it is only, apparently, the pat menu catalog scripts that are not finding the outbox.

I am now backing it up again, since all my other software is still working fine, but I would like to know what to do for the pat menu to work properly, that is, find and use the outbox properly.? The github script had installed pat menu v 2.4.0.? The only reason I installed pat winlink on this pi was so that, using telenet, I could make propagation report and rms list requests from *this* rpi, using telnet -- and have it as an ardop backup.

Thank you to Jason and the community for all their service and support to the pi ham community.

ks
K4GMV

Thanks for the report. I have created an issue ticket so this can be addressed.

I suspect it is due to the path change in Pat v0.12.0. I'll dig into it and correct ASAP.
--

Where should I look in the file system for the outbox location?

I did find archive, in, out, sent in this path...

./home/pi/.local/share/pat/mailbox/K4GMV

so I then searched the entire system to see if there was another out hiding somewhere, with

sudo find -iname "out"

but it returned nothing other than the one I already had found at

./home/pi/.local/share/pat/mailbox/K4GMV/out

ks
K4GMV

Pat Winlink prior to version 0.12.0 stored the mailbox data in ~/.wl2k/mailbox/ They changed where the mailbox data was stored beginning with 0.12.0 to the directory mentioned above.
--

Thank you Jason.? So the older Pat Menu 2.4.0 is probably looking to post the propagation report request to the out that it expects to find in the .wl2k/mailbox/??? ---- but of course, since I installed Pat Winlink 0.12.0? there is no .wl2k path on this system.? This begins to make sense.? When it fails to find the .wl2k path, it does not bother to give me any type of error to let me know that the directory does not exist,? and that was the frustrating mystery.

Therefore, either I could edit your script to point it to the correct path, or, nuch simpler I imagine, I could update the Pat Menu version to one that works with Pat Winlink 0.12.0 or greater, to the proper current path.

I prefer to simply update the Pat Menu, if you would kindly detail your more preferred way of doing such an update of Pat Menu, I am hoping that will be all that is needed.? If? you have written a script that allows selecting to update both Pat Winlink and Pat Menu to their latest, please steer me to that script, and I will make those two selections only.? 8^)

Karl,

Run these commands to move to Pat Menu 2.5.0. This is specifically designed to work with the new paths of Pat 0.12.x but won't work with older versions of Pat Winlink
cd ~/patmenu2
git pull
git checkout version12
--

Thank Jason,

What also worked was the following...

Using several grep searches, I found quite a few references to the .wl2k path that I would need to edit.? I decided against creating my own future maintenance issues.? Recall, this was all a simple attempt to add winlink and the catalog scripts to my pi4B *desktop*.? So instead, I removed the previous installs, and ran BAP, but only installed, patmenu2, winlink, grid calculator, and a few other minor utilities, and ardop (just in case).? That install now has a properly functioning pat winlink and catalog scripts, working fine with telnet.? And the advantage (I hope) of the automated updates.

I did see also that current BAP installs will no longer be supporting buster officially.? I'm not looking forward to updating all the pi's to bullseye, but I suppose its about that time....

Thank you again, and I have certainly made note of the git pull in case I go back to a latest pat winlink.? I hope this all helped others with partial installs that do not use the full BAP scripts.?? :-)

ks
K4GMV