LogHX: English version

[lb2eg]

I have been using LogHX as my main log program for the last few weeks.

Exporting my log from UCXLog to ADIF v.3, and importing into LogHX3, I realized that LogHX did not recognize deleted DXCC entities. Y2 calls signs from before oct 3 1990 are not recognized as DDR, OK calls signs before 1993 are not recognized as Czechoslovakia, and so on. It looks like all call signs are allocated to the current use of the prefix, and I cannot find any way to change that in LogHX.

This is no big deal as I do not count deleted countries and I have all the Europeans in the log anyway. But as my old PJ QSOs is wrongfully recognized as the today PJ-entities, the filtered cluster list in LogHX get messed up.

To fix this I have moved all the deleted entity QSOs to a separate log in the log database.

Is this the way to do it, or have I overlooked something?

(I do not read Russian, but I do read the Russian language forum using google translate)

73 de LB2EG Richard

(SunSDR2-DX, LogHX 3.541)

[M0CGF]

This is what I see. Without JTalert running the callsigns goto loghx, on 2333. with it running they don't. wsjt and jtlert on 2237

[RX4HX]

recognize deleted DXCC entities

About deleted countries: yes, log doesn't work with deleted countries right now, but I can do it if necessary.

[RX4HX]

Without JTalert running the callsigns goto loghx, on 2333. with it running they don't.

It's right: JTalert captures data from WSJT-X. But you can setup JTalert as "bridge" from WSJT-X to log. How to do this - it is better to ask on the forum about JTalert.

[lb2eg]

Alexei,
thanks for the clarification on the deleted entities. Time beeing I have found a OK solution exporting the deleted countries QSOs into a separate log book in the log database.

One more question:

Sometimes i run 3 active sessions of JTDX in parallel; Sunsdr2-DX RX1 and RX2 + a remote site. I understand that LogHX offers only one UDP port for simultaneous logging from JTDX/WSJT-X, and there is no option letting LogHX read a combined (with symlinks) ADIF log wsjtx_log.adi.

UCXlog that I have uses for many years can monitor changes in the wsjt_log.adi and import new qsos into the log.

I such a feature planned for LogHX?

I have as a quick fix solved the UDP conflicts by using Log4OM v2 as a middleware, as that program can read data from several UDP ports and forward the data to one port. I guess there may exist smaller programs than this 500 MB memory Hog to solve this matter. Anyway, the proxy system seems like av feasible feature exploring the capabilities in SunSDR (and Flex-6000 series) to control RX/TX on several slices with CAT control.

Is a UDP proxy feature planned for LogHX?

73 de LB2EG Richard

[M0CGF]

Thanks, all sorted, I hadn't quite got the UDP settings correct.

Can you help on the QSO entry design? I seem to not be able to edit it to how the example is and I like that example design.

[RX4HX]

Is a UDP proxy feature planned for LogHX?

Yes, this is not difficult to do. As soon as I solve the problem with the search on QRZ.COM - I'll do it.

Can you help on the QSO entry design?

Here:

[M0CGF]

Thanks, what I cannot get to happen is the infomation box to move from the top, to make it go on the right side of of the columns.

[RX4HX]

what I cannot get to happen is the infomation box to move from the top

You use old version of log. Last version here (see links in header):

https://forum.qrz.ru/355-loghx-appar...izmeneniy.html

Last version:

http://rx4hx.qrz.ru/files/loghx/prer..._build_538.exe

[RX4HX]

UCXlog that I have uses for many years can monitor changes in the wsjt_log.adi and import new qsos into the log.

LogHX also monitor changes in the wsjt_log.adi and import new qsos into the log, but this work when UDP function unchecked.

Sometimes i run 3 active sessions of JTDX in parallel

Write all JTDX QSO to one wsjt_log.adi file?

For all users LogHX: install new version of log -

http://rx4hx.qrz.ru/files/loghx/prer..._build_542.exe

here fixed problem with search call data in internet.

[lb2eg]

LogHX also monitor changes in the wsjt_log.adi and import new qsos into the log, but this work when UDP function unchecked.

I can, unfortunately, not get this to work. I have disabled (checked off) the UPD port support in LogHX, and written the log path to the common wsjtx_log.adi file. But LogHX does not automatically import new qsos written to the ADIF-file. I the drop down "programs" list, I have checked "Use JTDX" and "External program used".

My set up window looks like this:



Using JTDX I have one setup folder for every RX in ... ... \AppData\Local\... ; one standard \JTDX and two defined with the --rig-name= extention when starting jtdx.exe. The common wsjtx_log.adi is located in a sub-folder i my user space document-folder, with symlinks pointing to it in the 3 jtdx folders. As stated in a previous post, this setup works fine using UCXlog. In the LogHX setup I have not filled in the path to the jtdx.exe. This to avoid starting and closing jtdx when restarting logHX etc.

An observation, running 3 Jtdx sessions using this setup, the QSO ENTRY window in LogHX receives QSO data from the JTDX session using the ordinary \AppData\Local\JTDX setup directory. This does not happen when running QSOs with the two other JTDX sessions.

Clearly, I must have overlooked something in the setup. I would be very happy to receive some advise on this.

I am using LogHX 3.542. and JTDX 2.1.0_rc149_32A

73 de LB2EG Richard

[RX4HX]

not get this to work

Problem fixed - try this version:

http://rx4hx.qrz.ru/files/loghx/prer..._build_543.exe

Uncheck "Use UDP", now log will be correct read QSO from wsjtx_log.adi.

[lb2eg]

Problem fixed - try this version:

http://rx4hx.qrz.ru/files/loghx/prer..._build_543.exe

Uncheck "Use UDP", now log will be correct read QSO from wsjtx_log.adi.

Works, but does not pick up FT4 Submode. FT4 QSOs only logged as MFSK. Works OK using UDP.

73 de LB2EG Richard

[lb2eg]

I have a problem with program freeze uploading QSOs to LOTW, when web receipt window does not appear. LogHX stays then in limbo and i have to terminate the program with windows tools.



This is a time to time occurrence on in home shack and 2nd home shack. Using win10 1909 and (new) Edge as standard browser on both QTHs. Now at my 2nd home shack i use LogHX3 545.

Checking lotw.arrl.org, shows that the QSOs has been transferred, and the problem seems to be that LogHX is stuck waiting for a receipt on that.

Is there any way out of this other than terminate LogHX?

73 de LB2EG Richard

[M0CGF]

I am on the newest 525 SW now, still the same.

Also as many people use the IC7300 and tend to have recording audio on, I wonder if there could be a future feature to somehow log or link to an audio file of the QSO?