|
|
---
|
|
|
title: Winlink on a Windows computer and a TX-500
|
|
|
summary: >
|
|
|
For anyone interested and mainly for my notes archive, this is the setup that
|
|
|
I currently have set up on my Windows equipment for Winlink. I started taking notes
|
|
|
on the **Microsoft Surface 2 Go** and ended up installing all this on the **HP Elitebook 830 G6**
|
|
|
(which has an **integrated GPS sensor**).
|
|
|
# date: 2024-05-11T23:53:55+02:00
|
|
|
date: 2024-06-01T09:45:09+02:00
|
|
|
lastmod: 2024-09-28T23:48:07+0000
|
|
|
coverCaption: Winlink Express
|
|
|
categories:
|
|
|
- amateur-radio
|
|
|
tags:
|
|
|
- winlink
|
|
|
- portable
|
|
|
- digirig
|
|
|
- mobilinkd
|
|
|
- packet radio
|
|
|
- vara fm
|
|
|
- vara hf
|
|
|
- gps
|
|
|
---
|
|
|
|
|
|
First let us start with what I used until now for any Winlink session that
|
|
|
I made (either at home or portable in the field/forest/mountain).
|
|
|
|
|
|
## The old setup (on a linux box)
|
|
|
|
|
|
I use a Lenovo X1 Carbon as my daily driver. It is quick enough and compact
|
|
|
and I used it for a while now for hamradio stuff too. I never did FT8 or
|
|
|
similar "messengers" on it though. In particular I did some winlink sessions
|
|
|
using [Pat] in combination with [rigctld], [direwolf], the [AX.25 tools],
|
|
|
[VARA] (HF and FM) and [ARDOPCF] (never got one connection from home).
|
|
|
|
|
|
[Pat]: https://getpat.io/
|
|
|
[rigctld]: https://hamlib.github.io/
|
|
|
[direwolf]: https://github.com/wb2osz/direwolf
|
|
|
[AX.25 tools]: https://packet-radio.net/ax-25/
|
|
|
[VARA]: https://rosmodem.wordpress.com/
|
|
|
[ARDOPCF]: https://github.com/Dinsmoor/ardopcf
|
|
|
|
|
|
A more precise note on how I established different connection types is
|
|
|
[already
|
|
|
written down in the article before]({{< ref "64-packet-radio-vara-mobilinkd-and-digirig-on-linux" >}}
|
|
|
"Packet radio, VARA (FM+HF), Mobilinkd, Digirig and the SignaLink USB on Linux").
|
|
|
|
|
|
## Using Winlink Express on a Windows computer
|
|
|
|
|
|
I planned to use the Surface 2 Go tablet for Winlink and related tasks -- but while I
|
|
|
wrote down my notes in this article I finally realized that I want to user a more
|
|
|
powerful device than the Surface 2 Go. I ordered a used HP Elitebook 830 for this
|
|
|
and I finished the main setup already.
|
|
|
|
|
|
<abbr title="For your information">FYI</abbr>: most screenshots are still from the Surface tablet.
|
|
|
|
|
|
|
|
|
|
|
|
I like to have the sound control open to adjust volume levels.
|
|
|
|
|
|
## ARDOP setup
|
|
|
|
|
|
Following some screenshots showing my settings for ARDOP:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Set the desired drive level within these settings. I usually have to set it to <kbd>87</kbd>-<kbd>88</kbd>.
|
|
|
|
|
|
|
|
|
|
|
|
I use a Lab599 Discovery TX-500 (with Lab599 as the CAT option).
|
|
|
|
|
|
I also use a Digirig and I can therefore use the COM port to trigger the PTT function.
|
|
|
|
|
|
|
|
|
|
|
|
{{< video "ardop-session-web" "An ARDOP session" >}}
|
|
|
|
|
|
## VARA HF setup
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{{< video "vara-session-web" "A VARA HF session" >}}
|
|
|
|
|
|
## VARA FM setup
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Digirig was not connected at the time when I made the screenshot here, so you see an invalid soundcard setting above.
|
|
|
Make sure to select the proper USB sound devices.
|
|
|
|
|
|
|
|
|
|
|
|
{{< video "varafm-session-web" "A VARA FM session" >}}
|
|
|
|
|
|
## Packet radio setup
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{{< video "packet-session-web" "A packet radio session" >}}
|
|
|
|
|
|
## Using the internal GPS sensor
|
|
|
|
|
|
My Surface 2 Go was a non-LTE version and I think those versions are the only ones with built-in GPS sensors
|
|
|
so I always had to use external GPS devices like the [U-blox7 GPS stick](https://www.amazon.com//dp/B01MTU9KTF/).
|
|
|
|
|
|
But starting with the Elitebook 830 G6 I now have a device with integrated GPS sensors that I want to
|
|
|
use with Winlink Express.
|
|
|
|
|
|
Heads up: Winlink Express let you use a COM port or a TCP/IP connection to obtain coordinates, so we will
|
|
|
need some sort of middleware that can read the internal sensors and forward the location information to a
|
|
|
**virtual COM port**.
|
|
|
|
|
|
### GPSREverse and GPSDirect
|
|
|
|
|
|
I have tried [GPSReverse and GPSDirect](https://www.gpssensordrivers.com/) first but had no luck with it.
|
|
|
|
|
|
I then started another try on a search engine but specifically looked for experienced off-grid operators like
|
|
|
Julian, OH8STN -- because I remembered some videos of him using a Surface tablet as well. And of course, he
|
|
|
[also used the internal GPS device of his LTE model](https://oh8stn.org/blog/2023/11/02/microsoft-surface-go-lte-gps-for-ham-radio/).
|
|
|
|
|
|
### Using GpsGate Splitter
|
|
|
|
|
|
Goto the [GpsGate Splitter](https://gpsgate.com/gpsgate-splitter) website and download the Splitter aswell as
|
|
|
the **Windows Location API Plugin** (scroll down a bit).
|
|
|
|
|
|
{{< alert >}}
|
|
|
The program is a 14-day free trial and can be bought for EUR 30€ (USD 40$) and is well worth the
|
|
|
investment.
|
|
|
{{< /alert >}}
|
|
|
|
|
|
On the welcome screen click <kbd>Advanced setup...</kbd> on the bottom. This opens the GpsGate settings dialog.
|
|
|
Select <kbd>Windows Location API</kbd> as input.
|
|
|
|
|
|
|
|
|
|
|
|
Move to the tab <kbd>Output</kbd> and choose <kbd>Virtual COM Port</kbd> in the drop-down menu
|
|
|
for the output. Click <kbd>Add</kbd> and choose which port to use (I use <kbd>COM1</kbd>).
|
|
|
|
|
|
|
|
|
|
|
|
Go back to the <kbd>Input</kbd> tab and click <kbd>Open</kbd>. You can now close the dialog
|
|
|
form and it will remain active in the systray (bottom right of the screen, somewhere near the clock).
|
|
|
|
|
|
After a reboot the GpsGate service should start automatically and restore your virtual COM port that
|
|
|
you can select in Winlink Express.
|
|
|
|
|
|
{{< alert >}}
|
|
|
**Update on June 16<sup>th</sup>**
|
|
|
I experienced some problems with this already, and I fixed it by using the Service.
|
|
|
|
|
|
Open the service manager (<kbd>Win</kbd>+<kbd>R</kbd> → `services.msc` → hit <kbd>Enter</kbd>
|
|
|
or click <kbd>OK</kbd>) and enable <kbd>Franson GpsGate 2.0</kbd> Service (doubleclick and set
|
|
|
the Starttype to <kbd>Automatic</kbd>). You can also start it manually by clicking <kbd>Start</kbd>.
|
|
|
{{< /alert >}}
|
|
|
|
|
|
## What you have to look for
|
|
|
|
|
|
There are probably more things to keep an eye on, but those are the few ones that
|
|
|
I usually take care of.
|
|
|
|
|
|
### Time synchronisation
|
|
|
|
|
|
Most digital modes rely on accurate time settings, so you may synchronise with a timeserver or use
|
|
|
the GPS mouse.
|
|
|
|
|
|
### RX signal
|
|
|
|
|
|
In ARDOP try to get your receiving signal withing the green bar. 
|
|
|
The top blue bar will then change to green aswell.
|
|
|
|
|
|
In VARA HF make sure the left indicator is near the needle as in this screenshot. 
|
|
|
|
|
|
You can achieve this with different methods.
|
|
|
|
|
|
- Change the microphone level within Windows.
|
|
|
I try to leave this setting to <kbd>80%</kbd> but I sometimes have to adjust it a bit.
|
|
|
It is good at <kbd>80%</kbd> for VARA FM, but for ARDOP I often have to increase it to <kbd>100%</kbd>.
|
|
|
- Change the REF level on your radio.
|
|
|
On the TX-500 I usually maintain a REF level between <kbd>-12</kbd> and <kbd>-19</kbd>.
|
|
|
|
|
|
### TX signal
|
|
|
|
|
|
You may need to look into your radios manual to get the optimum value of the signal.
|
|
|
On the TX-500 I look at the DIG meter. Get the bar nearly full and you are good to go.
|
|
|
|
|
|
(The ALC meter on the TX-500 does not move a bit on my setup)
|
|
|
|
|
|
## Some nice shortcut commands for the desktop
|
|
|
|
|
|
I catch myself often doing quick looks into the device manager to verify
|
|
|
the actual COM ports are still what they are used to be and I am also adjusting
|
|
|
sound volumes (USB speaker & mic) very often.
|
|
|
|
|
|
I created two links on my desktop that open the device manager and the
|
|
|
extended sound options just with a double-click for me.
|
|
|
|
|
|
Device Manager
|
|
|
: Right click on the desktop, select <kbd>New ›</kbd> → <kbd>Link</kbd>
|
|
|
and enter `devmgmt.msc`. Hit <kbd>Enter</kbd> or click <kbd>Next</kbd>,
|
|
|
name the new link appropriate and you're done with this one.
|
|
|
|
|
|
Sound control
|
|
|
: Right click on the desktop, select <kbd>New ›</kbd> → <kbd>Link</kbd>
|
|
|
and enter `mmsys.cpl sounds`. Hit <kbd>Enter</kbd> or click <kbd>Next</kbd>,
|
|
|
name the new link appropriate and you're also done with that one.
|
|
|
|
|
|
The sound control shortcut may have a non-ideal symbol, to change it right click
|
|
|
onto the new shortcut, select <kbd>Properties</kbd> and click on the button
|
|
|
<kbd>Other symbol...</kbd>. In the next dialog I choose another file
|
|
|
(click the button <kbd>Search...</kbd> next to the textfield). I use the
|
|
|
symbol from `C:\Windows\System32\SndVol.exe` -- open that file and you can
|
|
|
choose between three simple symbols for this new shortcut on your desktop.
|
|
|
Close all dialogs by clicking on <kbd>OK</kbd> and that's it!
|
