Perhaps I added too much information as background in my initial post.? All of the above is running Raspberry Pi OS and I have tried it with 32 bit bullseye on a Pi 4 and on 64-bit bookworm on a Pi 5 with the same result.
I have a file "start-rigctld" that contains one line:
rigctld -m 3070 -r /dev/ttyUSB0 -s 19200 &
I can open a terminal window and enter:
rigctld -m 3070 -r /dev/ttyUSB0 -s 19200 &
and terminal reports a PID.? I can check using "ps aux" and I see a task under user "pi" matching the PID with the "rigctld..." command.
I can then run patmenu2 and select Start/Stop Modems, start a Packet Modem, and Pat starts.? I can select Action > Connect, and when I select an alias, the frequency changes to the correct frequency for each Gateway I select.
After rebooting,??
I can then open a terminal session, and enter
./start-rigctld
and when I run?
ps aux
there is a task running with user pi and with the "rigctld..." string.
I can then run patmenu2 and select Start/Stop Modems, start a Packet Modem, and Pat starts.? I can select Action > Connect, and when I select an alias, the frequency DOES NOT change to the correct frequency for each Gateway I select.
So it seems that even though I can see what appear to be identical tasks running, Pat cannot use its alias function to change frequencies.
The difference is how I start the "rigctld" task.? In one case, I directly enter a command in Terminal, while in the second case, I execute a file containing the same command but the results are different.
What can I do to get the same result entering the command vs. running the command from a file?
I am baffled by this difference.
--Bill AA6BD
