The simplest might be to use an app.
On Android, Heavens Above, a product of the 25-year-old website of the same name, stores the orbital elements of the satellites of interest, and does the pass calculations on your phone.
The app uses the GPS to find your location. It likes to get fresh elements from the Internet on startup, but it caches them, so as long ...
You can find the code in packjt77.f90. Callsign encoding (for "standard" callsigns that don't require hashing) is in function pack28. A quick summary:
Adjust a few strange prefixes that don't follow the usual arrangement of letters and numbers. Swaziland 3DA0* will be encoded as if it was 3D0* instead, and Guinea 3XA1A will be encoded as if it was ...
Found on the JTDX groups.io (link won't work without login, unfortunately):
sybmol • - this operator loaded his log into LoTW
symbol ° - this operator loaded his log into LoTW and this is Hint decode (FT8 AP or matched filter based decoder in JT65 JT9 T10 modes)
symbol * - Hint decode (FT8 AP or matched filter based decoder in JT65 JT9 T10 modes)
You have to provide the -i option to invert the signal in order to decode it properly. The lowpass filter is not really required as this is a quite strong signal (but does not harm either).
$ ./rs41ptu -i --crc -vx wav/20140717_402MHz.wav
bits : 8
channels : 1
[ 5047] (K1930308) Do 2014-07-17 12:32:13.999 lat: ...
To track the satellites, you need the Keplerian TLE orbital coefficients. Once you have those, you can track the sats without internet access. The TLE's are accurate enough for about a week. The TLE file format is standardized and works with nearly all the tracking software, and most software either downloads them on command or can import from a file.
Since there was no such repeater listing out there, I started my own database:
As a bonus, there is a service to comment on, and favorite to get status notifications about a repeater, something I haven't seen in other listings. Also, a topo map showing where each of the nearby repeaters is, is now available in Repeater-START ...
Listen tcp 0.0.0.0:5000 bind address already in use.
This sounds like a somewhat generic error, not necessarily related to your AX.25 software itself but certainly a bummer to encounter it while setting up!
What this means is the software you're trying to run wants to listen on port 5000, on all network interfaces (the 0.0.0.0 part). But something is ...
With correct settings for the transceiver's CAT interface in the Winlink software, Winlink should be able to control the transceiver. There should be no need for another "computer control program" interfacing with Winlink.