Cloudlog assistant
Cloudlog assistantIt is a lightweightCloudlog/WavelogThe assistant program supports automatic uploading of current radio information and real-time QSO data to Cloudlog/Wavelog/Clublog, while also supporting most mainstream radios and withJTDX/WSJT-XWaiting for software collaboration!
If your computer's performance is struggling, or you simply need an automated QSO/radio information upload tool, consider trying this.Cloudlog Helper！
Download link details are available at the end of this article.
💻 Supported platforms
- Windows 7 Service Pack 1+
- Ubuntu 20.04 or later, or other popular distributions
- Adapting to macOS...
⚡️ Get started quickly!
You can also choose to compile it yourself; please refer to the instructions below.CompilationChapter.
FromReleaseDownload the software version corresponding to your system. If you are using Linux and need to use the radio data reporting function, please start the software with sudo.
Open the software, click.Settings->Basic SettingsOpen the Settings page.
Please read this document in its entirety before starting to use it, and also review the disclaimer at the end of the document.
📌 Cloudlog Configuration
Enter your Cloudlog server address (also referred to as Cloudlog) and its corresponding API key.
Click "Test". If your input is correct, a dropdown box will appear below the API key to select the Site ID. If you are using Cloudlog /
Wavelog has configured multiple sites. Please select the correct ID here, and all subsequent QSOs will be uploaded to this ID.
📌 Clublog Configuration
Enter your call sign, email address, and password that you used when registering on Clublog.
Click "Test". If the test passes, you can enable "Automatically upload QSO to Clublog" in the "UDP Settings".
📌 Hamlib Configuration
If you do not need the automatic upload of radio data functionality, you can simply skip this step.
Because, after enabling JTDX (or WSJT-X, referred to as JTDX), the control of the radio will be exclusively held by JTDX, therefore, this function and JTDX cannot be enabled simultaneously before setting up JTDX. Please see [可查看]Collaborate with JTDXSome possible solutions.
This software allows you to schedule the upload of radio station information (frequency, mode, etc.) to your Cloudlog server. When you need to record QSO information, Cloudlog will automatically retrieve and populate the current frequency, mode, and other data into the corresponding input fields, avoiding manual entry errors. Additionally, the main interface of Cloudlog displays the radio station's frequency, mode, and other information in real-time, making it convenient for reference during operation.
InRadio modelSelect the model of your radio from the dropdown menu.
InDevice portSelect the port on which your device is located.
Click the "Test" button. After successful testing, you can check the box for "Automatically report radio data." Click "Confirm" to save the configuration.
The main software interface should display the radio-related information that has been read. Open your Cloudlog website, and the homepage should show your radio information:
In "Station", select your radio station. Subsequently, Cloudlog will automatically populate information such as frequency and mode when you enter QSO details.
📌 UDP Server Configuration
This part works in a similar way to...GridTracker，JTDXIt will broadcast information such as the current decoded call sign, frequency, and signal report using the UDP protocol.CloudlogHelperReceive and decode this information, and upload the results in real-time to your Cloudlog server.
This section doesn't require extensive configuration. If you change the port number for this part, be sure to update the UDP server configuration in JTDX accordingly.Please note that if JTDX and CloudlogHelper are running on different machines, you need to select the "Allow external connection" option and change the IP address field for the UDP server in JTDX to be the IP address of the machine running CloudlogHelper.
Subsequently, when JTDX is in transmit mode or has completed a QSO, the main software interface will display the corresponding information.
🚀 Advanced
🎯 Collaborate with JTDX/Wsjt-x
If you want to transmit radio data in real time while using JTDX, please refer to the following information. The operation process of Wsjt-x is similar.
When you start JTDX, the radio's control will be exclusively held by JTDX. At this point, you won't be able to read the radio frequency using this software. Fortunately, both JTDX and this software can use Rigctld as the radio's backend controller. You simply need to modify the network server address in JTDX so that both this software and JTDX share a single Rigctld backend.
Please do not set the polling interval for both JTDX and this software to be too short. Excessive data requests may overwhelm the radio, leading to errors. A suggested setting is to have the time interval in JTDX's "Radio Settings" at 8 seconds, and the polling interval in this software at 15 seconds.Please note that neither can be a multiple of an integer.
The specific steps are as follows (using Windows 7 as an example):
Open Cloudlog Helper and navigate to the "Settings" page. After filling in the relevant radio station information, check the box for "Automatic Radio Station Information Reporting." Note:Do notCheck boxDisable PTT control. JTDX relies on this function to control radio transmission.
Click "Apply Changes".
OpenJTDX, enterSettings-Radio, toWireless devicesChange toHamlib NET rig control
In CAT control, the network server should be configured with the rigctld backend address (defaulting to 127.0.0.1:4534), and the PTT method should remain unchanged.
After verifying that both CAT and PTT are available, click "OK".
You have now successfully integrated CloudlogHelper and JTDX.
🎯 Explanation of each configuration option
⚙️ Hamlib Configuration
| Configuration options | Instructions |
|---|
| Automatic reporting of radio data | If this option is selected, the software will automatically upload the radio information it has obtained to the specified cloudlog server. |
| Polling interval | Specify the time interval at which to retrieve radio data from the rigctld backend. The default value is 9 seconds. |
| Radio model | The currently supported radio models are read from the rigctld database, so theoretically, any radio that hamlib supports should be compatible with the software. |
| Device port | The port on which the radio operates. |
| Report out-of-band information | When polling, request frequency information (using different frequencies during reception and transmission) from rigctld. Some radio stations do not support this function or the data read is incorrect. |
| Report transmit power | When polling, request the current transmit power from rigctld. Some radio stations do not support this feature or provide incorrect data. |
| Advanced Settings - rigctld command line parameters | Manually specify the command-line parameters for the rigctld backend. This option has the highest priority, and if it is not empty, all other related configurations (disabling PTT control/enabling external control) will be ignored.If you choose to manually specify command-line parameters, you must explicitly specify the IP address and port of rigctld (-T). <ip> -t <port>), the software will automatically parse the port from command-line arguments. |
| Advanced Settings - Disable PTT control | Disable RTS and DTR control during startup (add parameters)--set-conf "rts_state=OFF" --set-conf "dtr_state=OFF"). This option only needs to be enabled on certain Linux systems. If you need to work with third-party software such as JTDX, this option should not be selected. |
| Advanced Settings - Enable external control | Allow interaction with the rigctld backend from devices other than localhost (add parameters) - T 0.0.0.0 ）。 |
Advanced Settings - Allow proxy requests | Start a proxy server that forwards external requests to the software, which then automatically sends them to rigctld in order of priority. |
| Use an external rigctld service | Use an external rigctld as the backend for the software's rigctld. For example, if you manually started a rigctld instance, you can select this option to configure the software to use the rigctld backend that you specified. |
⚙️ UDP Server Configuration
| Configuration options | Instructions |
|---|
| Enable the UDP server. | Start a UDP server to receive QSO data sent from third-party software. |
| Port number | The port number for the UDP server. |
| Allow external connections | Allow requests from devices other than localhost to be received. |
| Automatically upload QSO to Cloudlog | Automatically upload received QSO data to the specified Cloudlog server. |
| Automatically upload QSO to Clublog | Automatically upload received QSOs to the specified ClubLog server. |
| Number of retries for failed QSO upload | Specify the number of times to retry a failed QSO upload. |
🛠Compilation
Please see the README file on GitHub.
✨ Other
Please see the README file on GitHub.
🙏 Acknowledgments
- Hamlib: Hobby radio equipment control library (supports radios, transmitters, receivers, and amplifiers)
- WsjtxUtils: Using a C# class library and example code, through .NET & Interaction between the .NET Framework 4.8 UDP interface and WSJT-X
📝 License
Cloudlog HelperThis is free and open-source software, released under a permissive license. Anyone can copy, modify, distribute, use, compile, sell, or otherwise make available this software for any purpose (commercial or non-commercial), in any form (source code or compiled files).
For complete license information, please refer to the repository.UnlicenseFiles.
⚠️ Disclaimer
Software Usage
Cloudlog Helper is a free, open-source software designed to provide convenient assistance for amateur radio enthusiasts using Cloudlog/Wavelog. Users are free to download, use, or modify the software, but they are solely responsible for any risks associated with its use. The developers and contributors are not liable for any direct or indirect losses resulting from the use of this software, including but not limited to:
- Data loss or corruption
- Radio equipment malfunction or failure
- Network communication issues
- Other consequences arising from software incompatibility, misconfiguration, or improper operation.
Function limitations
Testing Phase Statement: This software is currently in the testing phase (UNDER TESTING) and may contain undiscovered defects or functional instability. Users are advised to back up important data before using the software and to avoid relying solely on it for critical operations.
Third-party dependencies: This software relies on third-party libraries or tools such as Hamlib, JTDX/WSJT-X, and its functionality and compatibility are limited by the support range of these components. The developers cannot guarantee compatibility with all devices or software.
Data security and privacy
Users are responsible for ensuring the security of sensitive data such as Cloudlog/Wavelog API keys and Clublog account information that they input. This software does not actively collect or store this information, but users must take responsibility for any data breaches caused by their devices or network environment.
QSO data received via a UDP server is, by default, only processed locally. Enabling the "Allow external connections" feature may increase security risks, so please configure it with caution.
Equipment operation risks
When using Hamlib to control a radio, be sure to follow the operating instructions provided by the device manufacturer. Incorrect polling intervals or configurations can cause the radio to malfunction. It is recommended to test the functionality without connecting the radio during initial use.
When working with software such as JTDX/WSJT-X, it is important to avoid port conflicts or control competition issues. Developers are not liable for damage to equipment caused by misconfiguration.
Download address
GitHub: https://github.com/SydneyOwl/cloudlog-helper Welcome, Star!
BlueZone Cloud:https://wwbk.lanzouq.com/b00uz66gsd Password: 5ii8
闽ICP备2021006864号-7
闽公网安备35020602002794号