LogHX: English version

AutoCQ works with FT991, not with FT991 DATA... 73 OK2WO

Does anyone use their rotator at all with this software? I cannot get mine to goto a heading when the callsign is entered. It just goes to North no matter the contact.

I try again to download and install the 778 version. No virus inside: everything is working. No more error in the tcp tansmission.

@M0CGF I'm using PstRotator and it works!

Can you share PSTROTATOR settings please.

I found my calibration was wrong, recalibrated and it worked but I want the USB COM connection to PSTrotator then I need a connection via TCP,IP,UDP or which ever works to LogHX. Right now I can work either programme standalone but not both, I like to see the direction of the antenna in pst.

Ah I got it working now!!

Цитата:

---

Сообщение от S50U

Alex hi

Maybe it would be interesting for users of your programme to improve the reception of telnet DXCluster spots for interested group of users of POTA and SOTA programme. On the S50CLX DXCluster I have implemented the integration of spots that are not part of the classical telnet DXCluster network. More in my note below. The user of your programme would thus have the possibility to select in the programme the reception of specific spots via a button, with predefined commands to be sent to the S50CLX DXCluster after a successful connection. Sorting, searching by reference ... etc is a matter of implementing of LogHX. The idea for the button is:

1. POTA ONLY spots -> command executed: ACC/SPOTS INFO -POTA-

2. SOTA ONLY spots -> command executed: ACC/SPOTS INFO -SOTA-

3. BOTH POTA&SOTA spots -> command executed: ACC/SPOTS INFO -POTA- OR INFO -SOTA-

4. S50CLX CLUSTER DEFAULT (all spots) -> command executed: CLEAR/SPOTS ALL

A connection via telnet protocol to S50CLX s50clx.infrax.si:41112 which is a completely free service is required to receive POTA/SOTA spots.

Good luck, Dan S50U


************
POTA and SOTA enthusiasts!

POTA (Parks On The Air) and SOTA (Summits On The Air) are internationally renowned programmes. They encourage licensed radio amateurs to operate outdoors in nature parks or on mountain peaks. Operators making contacts in parks or on summits are called activators, and the other operators who contact them are hunters.

On the S50CLX telnet DXCluster I implemented the collection of spots from POTA and SOTA that are not part of the classical telnet DXCluster network (potaapp and sotawatch). Such spots are tagged with [-POTA-] and [-SOTA-] respectively. In the comment field a spot tagged as such carries:

POTA:
- International POTA reference number, example: SI-0831
- Mode of operation, example: CW
- POTA reference name, example: Preval Vrh Ravni

SOTA:
- International SOTA peak reference number; example: S5/CP-002
- Mode of operation; example: SSB
- SOTA summit name, altitude, points; example: Porezen, 1630m, 8 points

With the right settings, the exact DX spots you want can be received and this is achieved using the filters below. To change an existing filter, simply overwrite it with a new command. Each command (BOLD formatted text) must be entered on a new line, confirm the entry by pressing ENTER.

- for receiving only POTA spots, command: ACC/SPOTS INFO -POTA-

- for receive only SOTA spots, command: ACC/SPOTS INFO -SOTA-

- for receiving POTA and SOTA spots, command: ACC/SPOTS INFO -POTA- OR INFO -SOTA-

The CLEAR/SPOTS ALL command removes all set filters and the S50CLX passes us all SOTA, POTA, DXCluster and optionally RBN (SET/SKIMMER <mode>) spots.

In cases where you do not want to receive POTA and SOTA spots e.g. in a contests, use the command as the first filter before all others REJ/SPOTS 1 INFO -POTA- OR INFO -SOTA-

Spot forwarding is based on the DXSpider DXCluster software validation and normalisation algorithm, rejecting duplicates spots and ensuring quality spots in the face of increasingly frequent malicious attacks on global amateur radio DXCluster network.

The S50CLX DXCluster can be reached via telnet at: s50clx.infrax.si port 41112

My small contribution to the promotion of outdoor activities in POTA and SOTA hamradio programmes. :-)

Spread the news, thanks
73 Danilo S50U sys S50CLX DXCluster

p.s. The information is also published on the Radioklub Cerkno S50E website https://s50e.si/pota-sota-dxcluster/

---

Hi, this is a very good idea !
I hope that Alex could work on it.
73s Christian F8GHE

By default, I use "N" in the PrintQueue field.
With version 779 of 05/08/2025, if I manually save a QSO, everything works correctly.
However, if I connect WSJT-X and the QSO in FT8 is automatically saved, the PrintQueue field is not saved
and the field in the log, remains empty.

Вложение 372608


73 de IK2XDE Andrea.
ik2xde@gmail.com

Цитата:

---

Сообщение от IK2XDE

By default, I use "N" in the PrintQueue field.
With version 779 of 05/08/2025, if I manually save a QSO, everything works correctly.
However, if I connect WSJT-X and the QSO in FT8 is automatically saved, the PrintQueue field is not saved
and the field in the log, remains empty.

Вложение 372608


73 de IK2XDE Andrea.
ik2xde@gmail.com

---

This problem is present in versions 777-778-779, in the old version 776 everything works correctly.

- - - Добавлено - - -

When I close the log and exit permanently, version 779 doesn't seem to close SpotMachineServer.exe and CWServerHX.exe properly.
I have to close them manually from Task Manager.

73 de IK2XDE Andrea.

Цитата:

---

Сообщение от IK2XDE

PrintQueue field is not saved

---

Do yuo use 779 release? I've just checked that this field is saved correctly.

Цитата:

---

Сообщение от RX4HX

Do yuo use 779 release? I've just checked that this field is saved correctly.

---

I try with v 779 dated 05-08-2025 (not today release)
Problem also with 777-778

Now I use version 776 without problem.

- - -

With version 779 dated 05-08-2025
When I close the log and exit permanently, version 779 doesn't seem to close SpotMachineServer.exe and CWServerHX.exe properly.
I have to close them manually from Task Manager.

Thanks.

73 de IK2XDE Andrea.

Now I try
v 779 dated 14/08
v 780 dated 19/08 (test version)
problem persist.
When WSJT-X save qso , LOGHX save qso with PRINTQUEUE field "EMPTY"
Not save "N" that I put in the "QSO ENTRY" windows.

All ok with version 776

Thanks in advance.
73 de IK2XDE Andrea.

Цитата:

---

Сообщение от IK2XDE

When WSJT-X save qso , LOGHX save qso with PRINTQUEUE field "EMPTY"

---

Yes Andrea! Today I found problem! Pse QRX! I will fix the problem as soon as possible.

Fixed, please try:
http://rx4hx.qrz.ru/files/loghx/test..._build_780.exe

Цитата:

---

Сообщение от RX4HX

Yes Andrea! Today I found problem! Pse QRX! I will fix the problem as soon as possible.

Fixed, please try:
http://rx4hx.qrz.ru/files/loghx/test..._build_780.exe

---

Unfortunately, even with this version the problem persists.
It also does not save other fields from qrz.com lije Name, qth, mail..ecc...

73 de IK2XDE Andrea

- - - Добавлено - - -

Цитата:

---

Сообщение от IK2XDE

Unfortunately, even with this version the problem persists.
It also does not save other fields from qrz.com like Name, qth, mail..ecc...

---

In practice, it doesn't take into account what's displayed in the QSO entry window,
it doesn't save data from QRZ Name, locator, QTH, mail, etc., and it doesn't save the PrintQueue field.
It only saves data from wsjt-x

Here

https://forum.qrz.ru/355-loghx-appar...ml#post2107085

is same problem as you problem. And today's 780 version has solved it.

Цитата:

---

Сообщение от RX4HX

Here

https://forum.qrz.ru/355-loghx-appar...ml#post2107085

is same problem as you problem. And today's 780 version has solved it.

---

With the latest version, all fields are saved correctly, except the PRINTQUEUE field.
The problem with this field persists; it saves a blank field, not with the "N" (qsl not needed).