PAT journey

[Jeff VA2SS]

Hi everyone,

I would like to simply thank PAT developper team for their excellent work.

So far, I can finally run PAT on Mac OS with VARA HF and FM using CrossOver flawlessly.

I also really like the fact that we can control everything from scripts, starting from the transceiver thru scheduling P2P with automatic band change, etc... Of course, a lot of work to customize all these processes.... but this is amazing..... so long Winlink... :-) HiHiiiiii!!! 😝😜🎉  I even write a Python script to convert received P2P messages to create a Winlink registry file format to support Winlink Florida W4AKH net.

Long live to PAT!

Best regards.

73 de Jeff | VA2SS 

[Jeff VA2SS]

Hi everyone,

I'm still at the beginning of a POC (proof of concept) I am doing for my needs, but I again say PAT is totally awesome!! 

So far, I push my automation process when hosting P2P session on HF using VARA with Florida W4AKH Winlink net to a step further.

By using a task scheduler, like CRON for Linux or Task Scheduler embedded within Windows, I call my own script to automate band changes, filters setting, and even tuning the antenna for my Icom IC-7300.

Just as an example of my QSY script that I'm currently writing for my needs... I'm running Windows 11 at this moment, but a Linux version can be easily done.

I'm using Hamlib to control my 7300 and a command called PLINK that comes with Putty to send command over TCP.... similar to NETCAT under Linux.

@echo off
echo.
echo Setting Winlink P2P session on %1 ...
echo.

if [%1] == [] goto :error

echo QSY on %1
echo F %1 | plink -raw -P 4532 127.0.0.1 > nul:
echo QSY Done!

echo Set mode to USB-D and Filter 3 (narrow)...
echo w \0xFE\0xFE\0x94\0xE0\0x26\0x00\0x01\0x01\0x03\0xFD | plink -raw -P 4532 127.0.0.1 > nul:
echo Mode and filter set!

echo Set AGC Fast...
echo w \0xFE\0xFE\0x94\0xE0\0x16\0x12\0x01\0xFD | plink -raw -P 4532 127.0.0.1 > nul:
echo AGC set !

echo Tuning transceiver...
echo w \0xFE\0xFE\0x94\0xE0\0x1C\0x01\0x02\0xFD | plink -raw -P 4532 127.0.0.1 > nul:
echo Tuned!

echo.
echo Setting P2P session done!

goto :end

:error

echo.
echo Frequency missing !!!
echo.
echo Usage : QSY {frequency}
echo frequency = MMKKKHHH Ex. 7090000 = 7.090.000 on 40m
echo.

:end

Hopefully, I use a doublet antenne using a modifed Icom AH-4. So I can virtually tune everything without being nervous, even when I am not at home.

This is an example of my connect script for my IC-7300. I always keep an opened Window to send manually command, just in case, while RIGCTLD is running in the background; then killing the process when quitting.

@echo off
cls
echo IIIII  CCCCC         7777777 333333   00000   00000
echo  III  CC    C            777    3333 00   00 00   00
echo  III  CC      _____     777    3333  00   00 00   00
echo  III  CC    C          777       333 00   00 00   00
echo IIIII  CCCCC          777    333333   00000   00000
echo.
echo Connected !
echo.
start /b rigctld -m 3073 -r COM5 -s 19200 -c 0x94 -t 4532 -v

timeout /t 2 /nobreak > nul:

rigctl -m 2 -r 127.0.0.1:4532

taskkill /IM rigctld.exe /F > nul:

cls
echo IIIII  CCCCC         7777777 333333   00000   00000
echo  III  CC    C            777    3333 00   00 00   00
echo  III  CC      _____     777    3333  00   00 00   00
echo  III  CC    C          777       333 00   00 00   00
echo IIIII  CCCCC          777    333333   00000   00000
echo.
echo Disonnected !
echo.

There is an example of Windows Task Scheduler that I use to call my QSY script at specific time.

I will even write a Python script soon to generate XML file that will be easily imported within Windows Task Scheduler with P2P time period, frequency value, etc...

There is ssooooooooo much potential here when using PAT !!! OMG :-)

Have a great Field Day!

73 de Jeff VA2SS

[Michael Woodmansee]

Hi Jeff,

Thanks for the posts and keeping the group updated on your journey.

I'm already following in your footsteps in getting Pat up and running on Mac and would appreciate your feedback, since you seem to already have sorted that aspect:

The install commands for the Pat Web GUI at the Pat GitHub page are for Linux and the Mac, of course, is running UNIX. I've figured out that I need to be using launchctl place of systemctl, but the command "sudo launchctl start gui/$UID/pat" does not give me a pat process shown under ps the way running "pat http" from the command line does.

Your thoughts/advice would be greatly appreciated!

73s,

Mike KO6CGS

[Jeff VA2SS]

Hi Mike,

On MacOS, I only followed the basic installation process by installing the MacOS version of PAT.pkg : PAT for MacOS

Once you finished with PAT basic configuration, callsign, etc. you will then be able to start PAT with http support.

I am not using PAT as a service, but I only launch PAT when needed.

73 de Jeff VA2SS

[Paul Caraway]

I see you are using the Mac OS version of Pat... I have a Mac Intel not an AMD64 Will this work with the Intel version? I would hate to crater my system... ;)

Sincerely,
Paul

[Jeff VA2SS]

The filname of PAT installer is ....amd64.pkg..... so it is an app compiled for Intel CPU.... So, you are good to go.