LogHX: English version

[RX4HX]

Send spot via telnet --> Insert macros in info
Please add [submode] field

Not problem!

[M0CGF]

I updated the log today and now I cannot open anything says open ADO connection error, log is bad, if I say no dont load it says autorisation failed. any ideas as cannot use my log at the moment as it won't open.

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

it has opened my older log from a few days ago, so I am missing QSO's is there a way to fault find the broken log?

[RX4HX]

open ADO connection error, log is bad

Please - make printscreen of error!

First - save log base file in another folder!
Second - find file \LogHX\Log\<BaseName>.lhx2_bkp
Thrid - rename <BaseName>.lhx2_bkp to <BaseName>.lhx2 and try load log again.

[M0CGF]

I tried the renaming steps below, still the same error from the bkp file

[Alde]

Hello Dear Alexei.

Issues about configuration to use the MSHV with LogHX :

1) - How to add: Command line option, (--inst-name=) to use the MSHV in multi-instance ?

2) - How to set up: LogHX JT (JT/FT - modes actives calls -> Setup auto Call) to MSHV when in FT8 mode ?

Thanks for your attentions,
73 de PY5EJ.

[RX4HX]

I tried the renaming steps below, still the same error from the bkp file

Send file to me rx4hx@mail.ru

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

Issues about configuration to use the MSHV with LogHX :

It's will be in 759 version of LogHX.

[M0CGF]

Thanks Alexei, sent a dropbox link to your email.

[RX4HX]

sent a dropbox link to your email.

I'm checking files. Only file M0CGF_20230905_2_20240329.lhx2 is Ok, all other files is absolutely empty!

[M0CGF]

oh damn! not good. OK let me place the whole of the log folder in there incase I missed one, the one that should be the latest shows 12mb filesize here.

There is a folder called Log that is uploading and contains 54 files.

[S50U]

Alex, thank you for the tremendous work you give to the amateur radio community with your LogHX3 programme.

Maybe it would not be a bad idea to remove the "Skimmer" option from the Spot machine window because switching this option on leads to a range of problems. As a dx cluster administrator I notice problems when connecting to the cluster in my case the "market leader" DXSpider which allows to receive spots also from the RBN network. The LogHX3 user mistakenly thinks that by turning on the "Skimmer" checkbox he will also receive skimmer spots. Enabling this option leads to a huge number of telnet retries (unknown command) and a headache for dx cluster administrators who consequently block the user from entering the dx cluster. Enabling RBN skimmer spots is done on the dx cluster itself. I am adding an S50CLX example which could be sensibly included in the LogHX3 instructions.

Server Name: S50CLX
Address: s50clx.infrax.si
Port: 41112

S50CLX DXSpider Skimmer Usage. Use command line in Telnet window to Send a command to the dx cluster

SET/SKIMMER (Enabling for ALL MODES)
SET/SKIMMER CW (Enabling for CW only)
SET/SKIMMER RTTY PSK (Enabling for RTTY, PSK/FSK)
SET/SKIMMER FT (Enabling for FT4/8 only)
SET/SEEME (Turn on RBN spots for own call)

UNSET/SKIMMER (Disabling for ALL MODES)

HELP RBN and HELP SET/SKIMMER for a full set of instructions on how to use a feature.

In case of problems connecting to S50CLX I am available via emial address, see qrz.com.

Thanks & 73 Dan S50U sysop S50CLX
https://s50clx.infrax.si

[PY5XT]

FT4 Wise, is this setup right? Do you have any improvement to suggest?



PS. Mode: MFSK SubMode: FT4 is what is in https://adif.org/314/ADIF_314.htm - III.B.9 Mode Enumeration

- - - Updated - - -

FT4 Wise, is this setup right? Do you have any improvement to suggest?



PS. Mode: MFSK with SubMode: FT4 is what is in https://adif.org/314/ADIF_314.htm - III.B.9 Mode Enumeration

[IK2XDE]

Alex, thank you for the tremendous work you give to the amateur radio community with your LogHX3 programme.

Maybe it would not be a bad idea to remove the "Skimmer" option from the Spot machine window because switching this option on leads to a range of problems. As a dx cluster administrator I notice problems when connecting to the cluster in my case the "market leader" DXSpider which allows to receive spots also from the RBN network. The LogHX3 user mistakenly thinks that by turning on the "Skimmer" checkbox he will also receive skimmer spots. Enabling this option leads to a huge number of telnet retries (unknown command) and a headache for dx cluster administrators who consequently block the user from entering the dx cluster. Enabling RBN skimmer spots is done on the dx cluster itself. I am adding an S50CLX example which could be sensibly included in the LogHX3 instructions.

S50CLX DXSpider Skimmer Usage. Use command line in Telnet window to Send a command to the dx cluster

SET/SKIMMER (Enabling for ALL MODES)
SET/SKIMMER CW (Enabling for CW only)
SET/SKIMMER RTTY PSK (Enabling for RTTY, PSK/FSK)
SET/SKIMMER FT (Enabling for FT4/8 only)
SET/SEEME (Turn on RBN spots for own call)

UNSET/SKIMMER (Disabling for ALL MODES)

HELP RBN and HELP SET/SKIMMER for a full set of instructions on how to use a feature.

Dan is actually right.

Many users don't know the correct commands
to use the cluster and skimmer function.

Currently DXSPIDER and CC-Cluster (by VE7CC) are the two most popular cluster software

For example, these are the commands to use with a my CC-Cluster:

Server Name: IK2XDE-6
Address: ik2xde.ddns.net
Port: 8000

-----------------------------------------------------------------
command----> SET/SKIMMER (skimmer CW & RTTY spots enabled)
command----> UNSET/SKIMMER (skimmer CW & RTTY spots disabled)
-----------------------------------------------------------------
command--> SET/CW - SET/NOCW (Turn on/off CW spots)
command--> SET/RTTY - SET/NORTTY (Turn on/off RTTY spots)
command--> SET/FT8 - SET/NOFT8 (Turn on/off FT8 spots)
command--> SET/FT4 - SET/NOFT4 (Turn on/off FT4 spots)
command--> SET/BEACON - SET/NOBEACON (Turn on/off BEACON spots)
command--> SET/OWN - SET/NOOWN (Turn on/off spots for your own call)
-----------------------------------------------------------------


Thanks for the attention
73 de IK2XDE Andrea

[RX4HX]

FT4 Wise, is this setup right?

Not, you setup ADIF mode -> Log mode is wrong.
If you want use FT4 as Mode in log, you must:
- setup Log mode -> ADIF mode - is Ok!
- setup ADIF mode -> Log mode must be

[RC3C]

Server Name: IK2XDE-6
Address: ik2xde.ddns.net
Port: 8000

-----------------------------------------------------------------
command----> SET/SKIMMER (skimmer CW & RTTY spots enabled)
command----> UNSET/SKIMMER (skimmer CW & RTTY spots disabled)
-----------------------------------------------------------------
command--> SET/CW - SET/NOCW (Turn on/off CW spots)
command--> SET/RTTY - SET/NORTTY (Turn on/off RTTY spots)
command--> SET/FT8 - SET/NOFT8 (Turn on/off FT8 spots)
command--> SET/FT4 - SET/NOFT4 (Turn on/off FT4 spots)
command--> SET/BEACON - SET/NOBEACON (Turn on/off BEACON spots)
command--> SET/OWN - SET/NOOWN (Turn on/off spots for your own call)
-----------------------------------------------------------------

I have the same functionality on my DX Spider
RC3C-2 , dxc.rc3c.ru:17300

[DL2CC]

Hi Alexei, hi all, I've enabled UDP Adif broadcast but nothing happens, I don't see packets in wireshark when a QSO is entered.
Is UDP ADIF broadcast working?

Basically what I want to do, use a UDP listener to automatically upload QSOs to cloudlog.

Or Alexei, would you be interested in implementing an automatic QSO upload for cloudlog aka Clublog etc. ?
https://github.com/magicbug/Cloudlog/wiki/API

Thank you
73
Frank