LogHX: English version

Hello Alexei.
In Windows 10, up to Test version 759 of 2024-April-24 the Sleep Screen function worked properly, but now with Prerelease build_759 of 2024-May-13 it no longer works.
Is there any configuration to be done?
Thanks for any guidance,
73 from py5ej.
Pavanatti.

Цитата:

---

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

In Windows 10, up to Test version 759 of 2024-April-24 the Sleep Screen function worked properly, but now with Prerelease build_759 of 2024-May-13 it no longer works.

---

Yes, now log controls that the computer does not go into sleep mode. If need, I can make this feature on/off.

Цитата:

---

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

sleep mode. If need, I can make this feature on/off.

---

Hello Alexei;
Thank you for your attention.
The on/off functionality would be great, thanks for implementing it.
Sleep mode is useful for monitoring reception on the VHF bands (e.g. 2m, 6m), or on HF (e.g. 60m, 80m or 160m).
Thank you for your dedication to the fine work of developing LogHX.
73 from py5ej,
Pavanatti.

Цитата:

---

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

The on/off functionality would be great, thanks for implementing it.

---

Done - Setup->Default->add "Disable computer sleep mode" checkbox
Reload -
http://rx4hx.qrz.ru/files/loghx/prer..._build_759.exe

Hello,
I still have a very long process of synchronisation with eqsl, clublog... ending with an error in "reading adif" And sometimes it's very quick without error. QSO numbers is not important. It can freeze at the first as at the 600th
73, Thierry.

Цитата:

---

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

I still have a very long process of synchronisation with eqsl, clublog... ending with an error in "reading adif"

---

Hello! Show error printscreen.

Цитата:

---

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

Hello! Show error printscreen.

---

Hello Alexei,
I think that I've found the problem. The lhx2 file was stored on a cloud syncronised folder. I had multi conflicted .ldb files.
What I did: I moved the database on a local drive and it seems ok.
I will check lotw when it will be back.
73, Thierry.

Dear Alexi,

I have noticed a strange behavior with my micro KEYER III. At startup, I receive the following errors regarding the internal CW Keyer WinKey2 (see attached files). I have to press OK twice, and then the WinKey2 is recognized.

I suspect that some routines are checking for the presence of the WinKey2.

Just an FYI, and I hope you can provide a fix in the near future.

73,
HB9DHG Fulvio

Цитата:

---

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

The lhx2 file was stored on a cloud syncronised folder. I had multi conflicted .ldb files.

---

Yes, it is, that's the reason. LogHX is slowly syncing with the cloud. The right decision -

Цитата:

---

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

I moved the database on a local drive and it seems ok.

---

Цитата:

---

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

I suspect that some routines are checking for the presence of the WinKey2.

---

Do you use one or two Radios? May be do you setup WinKey for both Radios? (If use two Radio).

Цитата:

---

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

Yes, it is, that's the reason. LogHX is slowly syncing with the cloud. The right decision -




Do you use one or two Radios? May be do you setup WinKey for both Radios? (If use two Radio).

---

That's a good tip, Alexei.
I'm using two radios. How I can disable the winKey on one radio and use it only on the second one?

Thanks, Fulvio

UPDATED: never mind Alexei,
You pointed out to the right direction. I had to select RADIO 1 first, then disable WinKey.
Everything is fine now and I do appreciate your help with my issue.

Much appreciated!!!
HB9DHG Fulvio

Цитата:

---

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

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.

---

Is the problem fixed in the latest 761 as I don't see it written in the "Change log"? I only ask enough to inform the DXSpider sysop community. Alex keep up the good work. :p-up:

Вложение 356670

Dan S50U sys S50CLX
https://s50clx.infrax.si

In the new version of the log (build 762), this setting will be "hidden" so that it cannot be accidentally enabled.

Hello,

in the last version of LogHX I am noticed the problem:

QSO from MSHV is written to log with ?????? as callsign, sometimes. Previous versions were OK, no ??????...

73 de Josef, OK2WO

Цитата:

---

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

in the last version of LogHX I am noticed the problem:

---

Yes, I am aware of this problem. Use the 758 version. There will be a 762 version soon. This problem will be fixed there.

SunSDR2DX with ESDR 1.0.8 with LogHX build 762
CW Macros from LOGHX work great with TCI

Problem with SSB Macros from LOGHX - do NOT send audio via TCI
How we can config it.....??
NO TCI in the Output option.

(Work correct with IC-7600+COM PTT and Audio from PC)

-- -- --

Normally I keep only one band map open, the one relating to the radio I am using.
Normally
Radio 1 - ICOM IC-7600 - Band Maps 1
Radio 2 - SunSDR2DX - Band Maps 2

It would be nice if when I change the radio, the band maps would also change automatically,
so if I am with radio 1 and switch to radio 2, it should automatically close band maps 1 and open band maps 2

I don't know if it's possible and easy to implement, but it would be a nice utility


Thanks for attention.
73 de IK2XDE Andrea.