-
06.09.2024, 20:42 #901
- Регистрация
- 03.02.2006
- Возраст
- 52
- Сообщений
- 18,857
- Поблагодарили
- 9074
- Поблагодарил
- 4806
73 de RX4HX, Alexei, http://rx4hx.qrz.ru
Ant.: UW4HW, Pwr.: ~500 Wtts
-
30.09.2024, 02:55 #902
- Регистрация
- 05.01.2024
- Возраст
- 40
- Сообщений
- 6
- Поблагодарили
- 0
- Поблагодарил
- 1
-
30.09.2024, 08:31 #903
- Регистрация
- 03.02.2006
- Возраст
- 52
- Сообщений
- 18,857
- Поблагодарили
- 9074
- Поблагодарил
- 4806
Try this test version - http://rx4hx.qrz.ru/files/loghx/test..._build_768.exe
73 de RX4HX, Alexei, http://rx4hx.qrz.ru
Ant.: UW4HW, Pwr.: ~500 Wtts
-
11.10.2024, 19:53 #904
- Регистрация
- 26.10.2019
- Сообщений
- 46
- Поблагодарили
- 17
- Поблагодарил
- 9
Addition of a comma in the County field.
Hello Alexei,
When importing an adif file, created by LogHX (build 768),
I noticed the inclusion or addition of a comma in the County field of some countries.
See the result after exports/imports in the LogHX 768 environment.
If necessary, I can send you an .adi file with the problem described above.
I ask for guidance to avoid the proliferation of this error.
Thank you in advance for any help,
73 from py5ej,
Pavanatti.
-
11.10.2024, 20:06 #905
- Регистрация
- 03.02.2006
- Возраст
- 52
- Сообщений
- 18,857
- Поблагодарили
- 9074
- Поблагодарил
- 4806
Look here -
https://adif.org/314/ADIF_314.htm#Se...ve_Subdivision
Problem here:
For JA-stations - <Two-digit prefecture code><Two-digit or four-digit city code> without comma!
For VE-stations - there are no secondary areas and their identification!73 de RX4HX, Alexei, http://rx4hx.qrz.ru
Ant.: UW4HW, Pwr.: ~500 Wtts
-
11.10.2024, 22:04 #906
- Регистрация
- 07.07.2023
- Сообщений
- 16
- Поблагодарили
- 3
- Поблагодарил
- 3
Alexei,
I totally agree that the county fields are been not used in the ADIF 314 standard. However, it seems that when he exported an ADIF file from LOGHX with these let say “unsupported” counties and then imported the same ADIF back in other computer, a comma (,) was added to those counties. I tested this and found that if we continuously keep exporting and reimporting the log in ADIF format, it keeps adding commas to forehead of the counties. This happens mainly because LOGHX exports counties as <CNTY:X>State,County. For supported counties, LOGHX aparently suppresses the comma, but for unsupported ones, it keeps the comma as the first character.
From my point of view, the user should be able to write whatever they want in those fields, and export/importing shouldn’t change the values. What am I misunderstanding?
-
11.10.2024, 23:43 #907
- Регистрация
- 03.02.2006
- Возраст
- 52
- Сообщений
- 18,857
- Поблагодарили
- 9074
- Поблагодарил
- 4806
73 de RX4HX, Alexei, http://rx4hx.qrz.ru
Ant.: UW4HW, Pwr.: ~500 Wtts
-
17.10.2024, 16:18 #908
- Регистрация
- 16.04.2020
- Сообщений
- 72
- Поблагодарили
- 3
- Поблагодарил
- 0
All, I have just swapped PC's in the shack and trying to get everything back to how it was.
I am having trouble with the CAT, I used to use CATHx with no issues.
Now I get errors that the radio cannot open CatHX.
If I try wsjtx v2.6.1 with CAThx selected with this I get
Hamlib error: 1:icom.c(4943):icom_set_conf entered
1:icom.c(4973):icom_set_conf returning(0)
1:rig.c(817):rig_open entered
rig_settings_get_path: path=.hamlib_settings
rig_settings_load_all: settings_file (.hamlib_settings): No such file or directory
rig_open: cwd=C:\LogHX
rig_open: C:\LogHX/hamlib_settings does not exist
rig_open: async_data_enable=0, async_data_supported=1
serial_open: COM4
serial_open(229): open failed#1
serial_open(229): open failed#2
serial_open(229): open failed#3
serial_open(229): open failed#4
serial_open: Unable to open COM4 - No such file or directory
port_open: serial_open(COM4) status=-6, err=No such file or directory
rig_open: rs->comm_state==0?=0
1:rig.c(1023):rig_open returning(-6) IO error
IO error
IO error
while opening connection to rig
Timestamp: 2024-10-17T13:10:19.894Z
However if I goto hamlib it works OK in my FT8 "View".
In my SSB "view" modes and freqs are all different.
How can I get back woking with CATHx?
-
17.10.2024, 20:28 #909
- Регистрация
- 03.02.2006
- Возраст
- 52
- Сообщений
- 18,857
- Поблагодарили
- 9074
- Поблагодарил
- 4806
73 de RX4HX, Alexei, http://rx4hx.qrz.ru
Ant.: UW4HW, Pwr.: ~500 Wtts
-
26.10.2024, 17:42 #910
- Регистрация
- 21.07.2022
- Возраст
- 79
- Сообщений
- 14
- Поблагодарили
- 1
- Поблагодарил
- 1
CW AutoCQ problem
In the last version 769 there is not AUTOCQ repeated (CQ on button is red). Also Alt+R does not work, I have to click on ESC everytime.
What I am doing bad?
73 Josef OK2WO
-
26.10.2024, 18:31 #911
- Регистрация
- 03.02.2006
- Возраст
- 52
- Сообщений
- 18,857
- Поблагодарили
- 9074
- Поблагодарил
- 4806
Check this version -
http://rx4hx.qrz.ru/files/loghx/test..._build_770.exe73 de RX4HX, Alexei, http://rx4hx.qrz.ru
Ant.: UW4HW, Pwr.: ~500 Wtts
-
30.10.2024, 22:18 #912
- Регистрация
- 16.04.2020
- Сообщений
- 72
- Поблагодарили
- 3
- Поблагодарил
- 0
Any idea on a socket error?
C:\LogHX\LogHX3.exe
Socket Error:
A Socket operation was attempted to an unreachable host.
When loading my FT8 view, not sure if its a radio setting or a WSJTX setting? Is there an error log to give more details?
-
30.10.2024, 23:16 #913
- Регистрация
- 03.02.2006
- Возраст
- 52
- Сообщений
- 18,857
- Поблагодарили
- 9074
- Поблагодарил
- 4806
73 de RX4HX, Alexei, http://rx4hx.qrz.ru
Ant.: UW4HW, Pwr.: ~500 Wtts
-
31.10.2024, 00:31 #914
- Регистрация
- 16.04.2020
- Сообщений
- 72
- Поблагодарили
- 3
- Поблагодарил
- 0
ah looks like I had multicast ticked in error. Thanks!
-
14.11.2024, 16:18 #915
- Регистрация
- 16.04.2020
- Сообщений
- 72
- Поблагодарили
- 3
- Поблагодарил
- 0
question on the worked confirmed window. I know you can configure the dates, however what I am trying to do is the following.
1. Show all time status
plus at the same time
2. Show status for only this month, as I have a club contest to work as many dxcc each month.
Is it possible to have both on display?
Социальные закладки