{"id":1740,"date":"2026-01-03T14:25:00","date_gmt":"2026-01-03T13:25:00","guid":{"rendered":"https:\/\/sp4thk.elfro.pl\/?page_id=1740"},"modified":"2026-02-22T10:00:13","modified_gmt":"2026-02-22T09:00:13","slug":"telnet-clusters-wsjt-x-ntp-scheduler","status":"publish","type":"page","link":"https:\/\/sp4thk.elfro.pl\/index.php\/en\/logbook-2\/telnet-clusters-wsjt-x-ntp-scheduler\/","title":{"rendered":"Telnet Clusters, WSJT-X, NTP, Scheduler"},"content":{"rendered":"\n

\ud83d\udda7 Telnet Clusters<\/strong><\/p>\n\n\n\n

\u2699\ufe0f Configuration<\/strong><\/p>\n\n\n\n

In the configuration window, select the Clusters \/ Telnet<\/strong> tab:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

The program supports up to 10 clusters<\/strong>.
On the left side, there is a list where you can add, remove, or edit<\/strong> Telnet clusters.<\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n\n\n

A cluster can be selected from the cluster list by clicking Get from cluster list<\/strong>:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

Most clusters require you to provide your callsign<\/strong> for login.
Additionally, if you want to send spots<\/strong>, the cluster usually requires user registration<\/strong> and a password<\/strong>.
For receiving spots, registration and password login are typically not required<\/strong>.<\/p>\n\n\n\n

Among all added clusters, only one<\/strong> can be set as the default cluster<\/strong>.
When you send a spot, it will be sent only to this default cluster<\/strong>.<\/p>\n\n\n\n

Faster auto-refresh<\/strong> \u2013 for clusters, automatic refresh is enabled at twice the normal speed<\/strong>.
Global refresh settings are configured in the Scheduler<\/strong> section.<\/p>\n\n\n\n

Keep connection alive<\/strong> \u2013 a highly recommended option.
The connection to the cluster will not be closed. Some clusters do not tolerate frequent connections and disconnections and may block the user<\/strong>.<\/p>\n\n\n\n

Basic spot mode<\/strong> and Advanced spot mode with Telnet window<\/strong><\/p>\n\n\n\n

When you want to send a spot to a cluster, you have two options.
The first is a simple spot window<\/strong>, where you enter the data and send the spot:<\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n\n\n

Advanced spot mode<\/strong> simply opens the full Telnet console window<\/strong>.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

It is recommended to keep the Basic spot mode<\/strong> option enabled.<\/p>\n\n\n\n

Spot merging options<\/h3>\n\n\n\n

If multiple clusters are configured, the same data may appear more than once.
The program can attempt to merge identical or similar spots into a single entry<\/strong>.
There are four available options defining how spots should be merged:<\/p>\n\n\n\n

    \n
  • Do not merge spots<\/strong><\/li>\n\n\n\n
  • Merge spots by Callsign only<\/strong><\/li>\n\n\n\n
  • Merge spots by Callsign and Frequency (\u00b12 kHz)<\/strong><\/li>\n\n\n\n
  • Merge spots by Callsign, Frequency (\u00b12 kHz), and Spotter<\/strong><\/li>\n<\/ul>\n\n\n\n

    Stay on first row after refresh<\/h3>\n\n\n\n

    If this option is disabled and you click a selected spot in the Logbook list, the program will remember the selected position and, after refreshing cluster data, return to the same place (if possible).<\/p>\n\n\n\n

    If this option is enabled, each refresh will move the view back to the top of the list<\/strong>.<\/p>\n\n\n\n

    Try to detect mode from comment or frequency<\/h3>\n\n\n\n

    Clusters do not provide explicit information about the operating mode<\/strong> \u2014 typically only the frequency<\/strong> and callsign<\/strong> are available.
    The actual mode (CW, SSB, FT8, etc.) is therefore unknown. No logging program \u2014 even the best one \u2014 can know it for sure, but it can try to infer it<\/strong> \ud83d\ude42<\/p>\n\n\n\n

    Spotters often include mode information in the comments<\/strong>.
    The program can attempt to extract the mode from these comments.
    If that fails, it will try to guess the mode based on frequency<\/strong>, using a simplified band plan (for example, 7074 kHz<\/strong> is most likely FT8<\/strong>).<\/p>\n\n\n\n

    Of course, this approach may occasionally result in incorrect assumptions<\/strong>.<\/p>\n\n\n\n

    \ud83d\udce1 Working with clusters in the Logbook<\/strong><\/p>\n\n\n\n

    In the main Logbook window, there is a selector for My Logbook<\/strong>, followed by POTA<\/strong>, SOTA<\/strong>, and other clusters.
    At the very end, there is the Telnet Clusters<\/strong> option.
    After selecting it, an indicator light<\/strong> will appear next to it.<\/p>\n\n\n\n

    The indicator can have the following colors:<\/p>\n\n\n\n

      \n
    • Yellow<\/strong> \u2013 connection in progress<\/li>\n\n\n\n
    • Green<\/strong> \u2013 connected and operating correctly<\/li>\n\n\n\n
    • Red<\/strong> \u2013 an error has occurred<\/li>\n<\/ul>\n\n\n\n

      Clicking on this indicator light will display a menu:<\/p>\n\n\n\n

      \"\"<\/figure>\n\n\n\n

      Additionally, each cluster in the list at the bottom has its own submenu<\/strong>:<\/p>\n\n\n

      \n
      \"\"<\/figure>\n<\/div>\n\n\n

      \ud83d\udce1 Cluster spots<\/strong><\/p>\n\n\n\n

      How to create a spot? There are several ways:<\/p>\n\n\n\n

        \n
      • By clicking the green indicator light<\/strong><\/li>\n\n\n\n
      • By selecting the option from the Menu<\/strong><\/li>\n\n\n\n
      • By right-clicking<\/strong> on the cluster spot list and choosing the option from the context menu<\/li>\n<\/ul>\n\n\n\n

        Depending on the context, the program will automatically suggest<\/strong> who the spot should be created for by default.<\/p>\n\n\n\n

        When right-clicking on the log list<\/strong>, the callsign is taken from the clicked record<\/strong> (not the one highlighted in blue).
        When selecting the option from the Menu, the program first checks whether the Callsign field<\/strong> is filled \u2014 if so, that callsign will be used by default instead of one from the list.<\/p>\n\n\n

        \n
        \"\"<\/figure>\n<\/div>\n\n\n

        When clicking the green indicator light<\/strong>, if the Callsign field is filled, you will have two options for that callsign and one empty option<\/strong> to choose from.<\/p>\n\n\n\n

        Of course, after opening the spot window, all values can be freely modified<\/strong>.<\/p>\n\n\n\n

        \n\n\n\n

        \ud83d\udce1 WSJT-X \/ JTDX integration<\/strong><\/p>\n\n\n\n

        Applications such as WSJT-X<\/strong> and JTDX<\/strong> support digital modes, for example FT8<\/strong>.
        They can automatically send data to logging programs like this Logbook, allowing QSOs to be saved automatically<\/strong>.<\/p>\n\n\n\n

        Configuration is simple.
        Open the configuration window and select the WSJTX \/ NTP<\/strong> tab.<\/p>\n\n\n

        \n
        \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n\n\n

        Here you configure the UDP port<\/strong>, IP address<\/strong>, and whether incoming data from WSJT-X \/ JTDX<\/strong> should be accepted automatically<\/strong>.<\/p>\n\n\n\n

        UDP Hub<\/h3>\n\n\n\n

        UDP Hub is a unique feature that launches a separate application running in the Windows system tray.<\/p>\n\n\n\n

        Its purpose is to distribute data sent to a single UDP port (e.g., from WSJT-X\/JTDX) to multiple independent programs.<\/p>\n\n\n\n

        \n\n\n\n

        How does it work in the standard setup?<\/strong><\/p>\n\n\n\n

        WSJT-X sends its data via a UDP port.
        By default, this data can be received by only one application.<\/p>\n\n\n\n

        Although a multicast option (sending data to multiple recipients) is available in the settings, under Windows this feature often does not work reliably or can be difficult to configure.<\/p>\n\n\n\n

        If we want to use multiple applications at the same time, such as:<\/p>\n\n\n\n

          \n
        • GridTracker<\/li>\n\n\n\n
        • HamClock<\/li>\n\n\n\n
        • RigAndLog<\/li>\n<\/ul>\n\n\n\n

          a so-called dependency chain is created:<\/p>\n\n\n\n

          WSJT-X \u2192 GridTracker \u2192 HamClock \u2192 RigAndLog<\/pre>\n\n\n\n
          Each program receives the data and forwards it to the next UDP port in the chain.<\/p>\n\n\n\n
          Problems with the Standard Chain Solution<\/strong><\/p>\n\n\n\n
          Such a dependency chain has several significant drawbacks:<\/p>\n\n\n\n
            \n
          • It requires all programs to be started in a specific order.<\/li>\n\n\n\n
          • The configuration is rigid and not very flexible.<\/li>\n\n\n\n
          • If any single component crashes or is closed, the entire chain stops working.<\/li>\n\n\n\n
          • Not every application supports forwarding data to another UDP port (UDP forwarding).<\/li>\n<\/ul>\n\n\n\n
            Solution \u2013 UDP Hub<\/strong><\/p>\n\n\n\n
            UDP Hub eliminates the dependency chain.<\/p>\n\n\n\n
            It works in a simple and reliable way:<\/p>\n\n\n\n
              \n
            • It listens on a single UDP port (e.g., the one configured in WSJT-X).<\/li>\n\n\n\n
            • It receives the data.<\/li>\n\n\n\n
            • It distributes the data in parallel to multiple additional UDP ports (e.g., 5 ports).<\/li>\n\n\n\n
            • Each program connects directly to UDP Hub instead of another application.<\/li>\n<\/ul>\n\n\n\n
              As a result, we get a star topology architecture<\/strong> instead of an unstable linear chain.<\/p>\n\n\n\n
              The difference between these two approaches is illustrated in the diagram below.<\/p>\n\n\n
              \n
              \"\"<\/figure>\n<\/div>\n\n\n
              Advantages of UDP Hub<\/strong><\/p>\n\n\n\n
                \n
              • The program runs in the system tray and does not interfere with normal operation.<\/li>\n\n\n\n
              • No dependency chain.<\/li>\n\n\n\n
              • All connected applications work independently.<\/li>\n\n\n\n
              • Improved overall system stability.<\/li>\n\n\n\n
              • Simpler configuration and support for multiple clients (up to 5).<\/li>\n<\/ul>\n\n\n\n
                After launching, the program displays a single, simple configuration window.<\/p>\n\n\n
                \n
                \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n\n\n
                We can also click the Advanced Configuration<\/strong> button.
                A simple menu will appear, allowing you to configure how the program should start.<\/p>\n\n\n
                \n
                \"\"<\/figure>\n<\/div>\n\n\n
                \n\n\n\n
                \u231a Time synchronization with an NTP server at program startup<\/strong><\/p>\n\n\n\n
                Having a properly synchronized system clock is quite important when logging QSOs.
                Accurate time becomes critical<\/strong> for digital modes, where an incorrect clock may prevent successful decoding and, as a result, make communication impossible.<\/p>\n\n\n\n
                The program includes a separate module<\/strong> responsible for time synchronization.<\/p>\n\n\n\n
                On Windows<\/strong>, synchronizing the system time requires the program to be run with administrator privileges<\/strong> or as a system service<\/strong>.
                A simple solution is used here \u2014 a separate utility called SET_NTP_TIME.exe<\/code><\/strong> is launched, and the user must confirm its execution with administrator permissions<\/strong>.<\/p>\n\n\n
                \n
                \"\"<\/figure>\n<\/div>\n\n\n
                \n\n\n\n
                \ud83d\udcc5 Scheduler<\/strong><\/p>\n\n\n\n
                \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n
                On the left side, there are three main options<\/strong> related to QRZ<\/strong> and LoTW<\/strong>:<\/p>\n\n\n\n
                Do not use Scheduler<\/strong><\/p>\n\n\n\n
                Use Scheduler with QRZ\/LoTW log button visible<\/strong>
                The program will periodically check whether there is anything to upload to QRZ or LoTW.
                When new QSOs are detected, a button will appear on the bottom status bar<\/strong> of the program.
                Clicking this button will open the upload window or display a selection menu.
                The program will not send anything automatically in the background<\/strong>.<\/p>\n\n\n\n
                Use Scheduler with automatic upload to QRZ and LoTW<\/strong>
                With this option enabled, the program will automatically upload data to QRZ and LoTW in the background<\/strong> at specified intervals.<\/p>\n\n\n\n
                \n\n\n\n
                Two additional options at the end are:<\/p>\n\n\n\n
                Check QRZ on exit<\/strong> and Check LoTW on exit<\/strong>
                Regardless of whether checks were performed earlier or scheduled intervals are configured, the program can check on exit whether there is anything that still needs to be uploaded.<\/p>\n\n\n\n
                Automatically open upload windows<\/strong>
                By default, when closing the program or pressing the upload button, a selection menu may appear.
                When this option is enabled, the selection menu is skipped and the program will open the QRZ and LoTW upload windows sequentially<\/strong>.<\/p>\n\n\n\n
                \n","protected":false},"excerpt":{"rendered":"
                \ud83d\udda7 Telnet Clusters \u2699\ufe0f Configuration In the configuration window, select the Clusters \/ Telnet tab: The program supports up to 10 clusters.On the left side, there is a list where you can add, remove, or edit Telnet clusters. A cluster can be selected from the cluster list by clicking Get from cluster list: Most clusters […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":531,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-1740","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/pages\/1740","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/comments?post=1740"}],"version-history":[{"count":6,"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/pages\/1740\/revisions"}],"predecessor-version":[{"id":2102,"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/pages\/1740\/revisions\/2102"}],"up":[{"embeddable":true,"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/pages\/531"}],"wp:attachment":[{"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/media?parent=1740"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}