seems to install everything correctly and will swap back and forth between hotspot and wifi. one thing that is odd is that i get a hostapd masked on the first start. I run sudo systemctl unmask hostapd and this seems to clear up the issue. however, once hotspot is started, i am unable to connect with my phone or computer. Need to try manual install and see if it works to confirm it is a problem with the script. I have verified that all of the files installed by the script are in the correct location and have the correct contents. km4ack 20190409

piARDOP_GUI doesn't display on screen after running start-pat

this will allow time to be synced before GPS lock. Seems as though time is there even before the GPS has a lock.

edited /etc/default/gpsd to include the -r option

Needs update. See this line

My local wifi network has an SSID with a space in the name. ie. "Ye Ole Cabin". When searching for SSIDs with the Hotspot Tools, that SSID is only shown as "Ye" and when I select it, the pi will not connect to it. I have another SSID without spaces and the entire name shows on SSID search.

I just modified wpa_supplicant.conf so the SSID was correct. When I checked the "Manage SSIDs" menu, each work of Ye Ole Cabin was on a different line and was not selectable as a single SSID, instead, they were three different SSIDs in the menu.

Doesn't correctly account for Suffix (Jr/Sr/ etc.) if it exists.

.conkyrc L38 refers to to $HOME/bin/conky/grid which I believe is located at $HOME/pi-build/conky/grid

There is small typo in the grid-calc script which has no effect on the functionality of the app

"Updateing" should be "Updating"

For reference see here - https://github.com/km4ack/pi-scripts/blob/master/grid-calc#L67

Get hostapd masked error when first starting the hotspot. can run sudo systemctl unmask hostapd and reboot to clear the issue. can this be written into the script as a final command?

need initial config file to support port 8515 which is the default port. see ~/.config/G8BPQ/ARDOP_GUI..conf

Script should check to see if pat & xastir are installed on the system and warn user if not installed. Maybe offer to install?

Very nice app.
Enhancement: In the phone pop up, it would be nice to save the IP address and port number in a config file so that when one switches from phone to another source and back to phone one does not need to re-enter the information unless it changed.

Fix the autohotspot so that it will accept both y & Y as the correct answer.

I think your first line should be:
#!/bin/bash

The script didn't work first time for me this morning until I ran it thru bash.

I've been playing with hamlib/rigctl's functions for turning my FT-891 on/off from the command line. This feature only works with some radios, so it wouldn't be for every user. But the ability to turn on/off your rig from the pi would enable:

1. Putting the rig and all components/batteries/etc into a Pelican case (or harbor freight Apache case) and never having to open the case to operate the rig (ie in the rain, from the back seat of the truck, from a hidden-away cupboard in your home, etc).

• You could even go the extra mile and put a separation kit in the case to allow you to plug your hand mic directly into the side of the Pelican case.
• That way, you'd just have power hookup (or battery power switch) on the outside of the case (which would boot the pi), antenna hookup to the outside of the case, and handmic hookup to the outside of the case.

2. Remote operation of digital signals (via remoting into your home computer where your rig is located from anywhere in the world with an internet connection - via Chrome Remote Desktop or likewise).

I created this pastebin with my research https://pastebin.com/F9i7HXdJ . Feel free to use any/all of it in your pi scripts/build (future work would be a function to echo to the user that 1. the pi is attempting to turn on or off the radio for a few seconds. 2. That the radio is now on or off. Future work may also be possibly to run the radio turn on command at Pi startup and the radio turn off command on Pi shutdown).

autohotspotN isn't working correctly with Buster unless installed in the correct sequence. This is unique to Buster and doesn't have the same issue with Stretch. A link to this article https://www.patreon.com/posts/buster-29942780 has been included in the script for users running Buster. The fix needed is out of my control since I only wrote the install script and not the hotspot script. I have reached out to the developer in the comments section of his website. Currently awaiting the response. 20190915 km4ack

The path to the Pat mailbox needs to be updated to accommodate Pat versions greater than 0.12.0

add link to this github for those that want to edit the ip range of autohotspot https://github.com/lcgreenwald/autohotspot

Discovered something else. In /etc/chrony/chrony.conf there's an entry that sets the parameters of the reference time source NMEA.

refclock SHM 0 offset 0.0 delay 0.8 refid NMEA

I set the offset on that line to 0.0, it was 0.5 and that put my station within 100ms of most stations using only GPS as a time source.

As I understand it, setting that to 0.5 (500ms) is intended to make the NTP servers more preferred by Chrony when connected to the internet, basically an intentional 500ms error. Removing that offset gets the pi clock set very close to NTP server pool time. In a system set up for very accurate time off grid, I think that offset of 500ms should not be set.

from email with John Schultz

After last update could not run Packet Search tool. Had to do a manual install of Grid-Calc to get to run.

Is it possible to update the script to add other real time clocks? The code lists only DS1307, but there are others like DS3231. Or offer to enter your chip number during installation to continue the installation.

In getcall, line 55 can be changed to use $UID instead of 1000. This will make it independent of the pi user, for example if you create your own accounts.

FILE=/run/user/$UID/call.txt

https://groups.io/g/mobilinkd/topic/72456096