¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Grid Square not set in pat configure #bap


 

I continue to get the "grid square not set in pat configure" and I've been through all the recommended fixes I can find in this group. I've started over from scratch reinstalling a new copy of raspibios, doing all its updates, and then reinstalling BAP. I still get the grid-square message. The most recent BAP install has these lines:

2021/11/08 15:26:29 Unable to load/write config: unexpected end of JSON input
pat: no process found
pat version 12 or greater detected
mv: cannot move '/home/pi/pi-build/temp/config.json' to '/home/pi/.wl2k/': Not a directory

and when running pat configure in a terminal window I get a file with 0 lines.

Suggestions? Comments?

73,

Gordon KF5JWL

?


K3JRZ
 

I just got this spam error when I updated BAP, Pat & Pat Menu just now. Now Pat doesn't load as it normally did.?
"This site can¡¯t be reached ?127.0.0.1 refused to connect."


 

¿ªÔÆÌåÓý

Jeff, this should be a new thread so we don't detract from the original thread concerning a grid square and pat, however im guessing you have SES loaded as part of your BaP build?? If so check out this thread for a possible solution?Pat V0.12 port configuration issue :: SOLVED (groups.io)

Thanks,
Terry K4HNT




---- On Mon, 08 Nov 2021 18:18:22 -0500 K3JRZ <k3jrz.jeff@...> wrote ----

I just got this spam error when I updated BAP, Pat & Pat Menu just now. Now Pat doesn't load as it normally did.?
"This site can¡¯t be reached ?127.0.0.1 refused to connect."






 

Me too.? Just did an upgrade to 3.1.3 of BAP Update and several apps needed refreshing.? This happens when I start the Packet Modem from PAT Menu.? I can ping 127.0.0.1 from the Pi so this address is valid.

I can bring up the browser manually and I see two entries in the body to do a quick connect, Web store and km4ack (KM4ACK) - github).? If I connect to 127.0.0.1 I get this:

SEND EMAIL
Use the ¡°Send Email/Check Replies¡± link above to compose your email or check for replies to emails you have already sent. Updates will also be published below as they become available.
ACCESS FORUMS
Anyone can access and read the forums using the link at the top of this page. To post, you will need to register. Be sure to check the forums for additional information.
PURPOSE
The purpose of this page is to give the operator a place where updates can be published to the webserver making it easy to disseminate information to anyone who logs onto the Emergency Email Server.
MODIFYING THIS PAGE
This page may be modified using the Ghost Writer application installed on the Raspberry pi. Simply open the app and from the main menu. Once the application is open, choose File>Open. In the documents folder look for a file called info.markdown Once the file is opened you can make changes. When you are ready to publish the changes to the webserver, choose File>Export. Choose the documents folder and the info.html file. Then click Save. The file will be automatically copied to the webserver. This takes up to 60 seconds to complete. Help Video

etc....
Now the browser has and entry to 127.0.0.1

System is broken, can't run PAT Winlink.


 

Jason has a fix for this.? It is listed in this forum as a PAT V0.12 Port Issue if you have the Emergency Email Server installed.? What is happening is the PAT port is getting set to 8080 instead of the normal 5000.? Run this fix and PAT is happy again.


K3JRZ
 

My port was originally set up at 5000. Ran that thing. Still is. Something isn't working though. It's broke. LOL.


On Wed, Nov 10, 2021 at 5:56 PM Dave Christensen <dkc2030@...> wrote:
Jason has a fix for this.? It is listed in this forum as a PAT V0.12 Port Issue if you have the Emergency Email Server installed.? What is happening is the PAT port is getting set to 8080 instead of the normal 5000.? Run this fix and PAT is happy again.


 

I think my port showed up as 5000 in the PAT > Settings > Current but when I did a pat configure it was port 8080.? Changed it to 5000 there and stuff started working again.


 

My port was originally set up at 5000. Ran that thing. Still is. Something isn't working though. It's broke. LOL.
Run these commands from a terminal:
sudo killall pat
pat http

and post any errors. The above commands stop pat from running in the background and restart pat manually. If you don't get errors, leave the terminal window open and open the web browser. Navigate to 127.0.0.1:8080 If that doesn't work, try 127.0.0.1:5000 The correct address depends on your setup. Let us know which one works.

--
73, de KM4ACK
|
|