Вид для печати
Hello Alexei,
Is it my problem only or others have this too?
I started with eQSL a few weeks ago and when I downloaded eQSLs in LogHX the confirmed eQSLs not checked at all. All goes to the "Sent (eQSLS)". LoTW works fine but eQSL do this problem at me.
Thank you for help!
Is here checked?Цитата:
Сообщение от HA3MN
Вложение 339463
You must download only CFM eQSL - ADIF from eQSL have not field "eQSL CFM"!
Thank you Alexei! This method is works! 73 Egon
Hi Alexei,
Is there any possibility that you can mount Azimuth Map LogHX via PstRotator. That you can use it to operate beam.
73 Pat
Hello Alexei,
Is there a possibility to do the manager database update.
73 Pat
There is no nessesary, b'coz we have QRZcom/QRZru/IK3QAR and other services to get QSL route to callsign.Цитата:
Сообщение от ON3PAT
Here I do it manually If i have a time to do.
Recently I did update it POBEDA-78 memorial within.
This is the syntax of manager file to update database correctly:
File Structure qslmanager.txt (or another txt file) to import into LOG
-----------------------BEGIN-----------------------
<3 spaces>02-may-22
RP77A<7 spaces>RZ1OA
RP77KO<7 spaces>RA3VE
ON8X<7 spaces>ON8XXX
DK0XXX<7 spaces>DA4XXX
-----------------------/BEGIN----------------------
---begin-- & ---/begin--- you have to delete.
Hope it will help you in any cases for manual update.
Hi Pat, I've already contacted Alex about it, he's working on it and I hope everything will be ready soon.Цитата:
Сообщение от ON3PAT
Greetings.
73 de IK2XDE Andrea
About managers - best way to find managers for Stations:
Вложение 340299
Hello Alexei,
There is a new LogHX fan because I installed LogHX to a very good friend of mine. :s7:
Everything works fine, just only one thing we don't know...
How to control the PTT in VoiceHX window? [TX] [RX] commands does not do it.
With VOX or using MOX the messages are transmitting, no problem.
In Logger32's DVK window there was a COM port to control PTT.
He has microHAM 2R+ and FTdx5000.
Thank you for your help in advance!
73 Egon / HA3MN
[TX] [RX] commands must work!Цитата:
Сообщение от HA3MN
Example of macros:
[TX]
[CATCMD:MD2;]
CQ
CQ
[CATCMD:MD3;]
[RX]
Where - CQ is CQ.wav file in VoiceMacros folder.
Hello/Privet Alexei, Pat, AndreaЦитата:
Сообщение от ON3PAT
Another option is to use OK1RR's QSL Managers Database. Martin OK1RR updates this database every month. But he uses a different .txt file format than Alexei in LogHX. It is possible to modify this file as needed by LogHX. It would be better if Alexei made it possible to import a .txt file from OK1RR to LogHX. Would it be possible Alexei?
https://ok1rr.com/downloads/qsl-managers-database/
Vlado OM3BY
Hello Alexei,Цитата:
Сообщение от RX4HX
Sorry for the late answer but my friend was very QRL.
Well, DVK is functioning perfectly! Thank you for the ideas!
The format of the SSB solution is :
[TX][CATCMD:TX1;]msg1[CATCMD:TX0;][RX]
Thank you again!
I'm doing an import from a text file to manager database. But how to take into account the start date and the end date if they are not provided? After all, there may be different managers for same station at different times? How to log data from the OK1RR database when the start and end dates are not specified?Цитата:
Сообщение от Vlado
Hello Alexei,
Is it possible to save Radio1/Radio2 setup and Rotor1/Rotor2 setup into the "Views"?
My friend has two radios, one for HF and one for VHF but HF/VHF antennas are using the same rotor (there is only one rotor).
I made to him two "Views" to change radios/rotor(s). One for HF and one for VHF but when he is using the "Select view" menu and select the "HF" view or the "VHF" view,
the "Views" does not load the informations for which radio and rotor are belongs to the given "Views" because the LogHX does not save these informations.
Are we do something wrong?
Thank you again for your help in advance!
73 Egon / HA3MN
PS: There is an other friend of mine... I installed LogHX to him as well.
He said, LogHX is much better than his old log program, you made so GOOD program! :)
He loves it so much!
Dear Alexei,
I hope this email finds you well. I am writing to inquire about the availability of UDP Multicast support in LogHX and its potential inclusion in future releases.
As an operator who frequently utilizes applications such as WSJT-X and JTDX, I have come to appreciate the convenience and functionality provided by UDP Multicasting. It enables multiple applications running on the same PC to interact with WSJT-X using a shared UDP IP Address and Port. This capability proves particularly valuable when using programs like GridTracker and JTAlert in conjunction with LogHX.
However, upon my exploration of LogHX, I could not find any options or settings related to UDP Multicasting. Hence, I wanted to confirm if LogHX currently lacks support for this feature. If so, I kindly request you to consider implementing UDP Multicast support in future releases of LogHX. This enhancement would greatly enhance the interoperability and versatility of the LogHX application.
For reference, the versions of the applications I am currently using are as follows:
LogHX v3.0 build 730
JTDX v2.2.160-rc2 HF
WSJT-X v2.6.1 6b6d74
To provide an example, I have outlined below the necessary configuration settings for enabling Multicast UDP in WSJT-X:
1. Navigate to the Reporting tab in the WSJT-X Settings dialog.
2. Under the UDP Server group of controls, set the UDP Server: address field to a valid IP address within the 224.0.0.1 through 224.0.0.255 or 239.0.0.0 through 239.255.255.255 address range. The default value of 224.0.0.1 is commonly used.
3. Keep the default value of 2237 for the UDP Server port number: field.
4. From the Outgoing interfaces: drop-down listbox, select the loopback_n option. You may choose to select all available interfaces.
5. Set the Multicast TTL: field value to 1.
6. Ensure that the checkboxes for Accept UDP requests, Notify on accepted UDP request, and Accepted UDP request restores window are selected.
For visual reference, you can consult the following image from (https://support.hamradiodeluxe.com/s...multicasting):
I sincerely appreciate your attention to this matter. Introducing UDP Multicast support in LogHX would greatly enhance its compatibility and utility in multi-application environments. Thank you for considering my request, and I look forward to any updates or feedback you may provide.
73, PY5XT (Eleandro)
