Re: file cty.dat was not found
I think you're right Aki, the error message is not nearly cryptic or sarcastic enough for Logger32. Not even a 'The sky is falling' Chicken Little title. SeventyThree(s).
On 05/21/2025 8:46 PM EDT ja1nlx via groups.io <ayoshida0205@...> wrote:
?
?
I think this file is not for Logger32.
Maybe, other program use it.
?
On 2025-05-22 ľ 9:34:03, Richard Zalewski W7ZR via groups.io <dick.w7zr@...> wrote:
Never before:
So how do I fix?
|
Re: file cty.dat was not found
I think this file is not for Logger32. Maybe, other program use it.
On 2025-05-22 ľ 9:34:03, Richard Zalewski W7ZR via groups.io <dick.w7zr@...> wrote: Never before:  So how do I fix?
|
file cty.dat was not found
Never before:  So how do I fix?
|
toggle quoted message
Show quoted text
Il giorno lun 19 mag 2025 alle ore 11:40 Bob via <k4cy= [email protected]> ha scritto:
Thanks for the information about DXMap. I have no plans to provide a Logger32 interface to this software. SeventyThree(s).
?
?
Hi Bob,
I hope you are doing great!
I came across this interesting website
Just wondering if you consider interesting the possibility of connecting it with Logger32.
The API reference is available here
?
Features
- Live Keyboarding : While typing the callsign in the log, HamDXMap will be informed, this partial callsign is copied in the RX callsign zone of HamDXMap. You will be able to locate the caller on the worldmap. You can detect any inconsistencies in the situation by looking at the MUF/foF2 curve in the panel.
- Logged Call : When the callsign is logged, the entire callsign is saved in HamDXMap (client brownser side). A circle with red border is drawed on the map. The display of these points is globally authorised/forbidden by the user with the Log source, in the filter section.
- DX-Cluster : All the spots coming over wtTelnet () are memorized on your browser in HamDXMap during a giving configured time (Storage depth parameter). User can filter the spot and make a ring be sounded for all new spot displayed. The display of these DXCluster spots is globally authorised/forbidden by the user with the DXc source, in the filter section.
?
73
Andrea, iz2lsc
?
?
|
Thanks for the information about DXMap. I have no plans to provide a Logger32 interface to this software. SeventyThree(s).
On 05/19/2025 1:53 AM EDT Andrea via groups.io <fuffa2k5@...> wrote:
?
?
Hi Bob,
I hope you are doing great!
I came across this interesting website
Just wondering if you consider interesting the possibility of connecting it with Logger32.
The API reference is available here
?
- : While typing the callsign in the log, HamDXMap will be informed, this partial callsign is copied in the RX callsign zone of HamDXMap. You will be able to locate the caller on the worldmap. You can detect any inconsistencies in the situation by looking at the MUF/foF2 curve in the panel.
- : When the callsign is logged, the entire callsign is saved in HamDXMap (client brownser side). A circle with red border is drawed on the map. The display of these points is globally authorised/forbidden by the user with the Log source, in the filter section.
- : All the spots coming over wtTelnet () are memorized on your browser in HamDXMap during a giving configured time (Storage depth parameter). User can filter the spot and make a ring be sounded for all new spot displayed. The display of these DXCluster spots is globally authorised/forbidden by the user with the DXc source, in the filter section.
73
Andrea, iz2lsc
?
?
|
Hi Bob,
I hope you are doing great! I came across this interesting website Just wondering if you consider interesting the possibility of connecting it with Logger32. The API reference is available here
-
: While typing the callsign in the log, HamDXMap will be informed, this
partial callsign is copied in the RX callsign zone of HamDXMap. You
will be able to locate the caller on the worldmap. You can detect any
inconsistencies in the situation by looking at the MUF/foF2 curve in the
panel.
-
: When the callsign is logged, the entire callsign is saved in HamDXMap
(client brownser side). A circle with red border is drawed on the map.
The display of these points is globally authorised/forbidden by the user
with the Log source, in the filter section.
- : All the spots coming over wtTelnet ()
are memorized on your browser in HamDXMap during a giving configured
time (Storage depth parameter). User can filter the spot and make a ring
be sounded for all new spot displayed. The display of these DXCluster
spots is globally authorised/forbidden by the user with the DXc source, in the filter section.
73 Andrea, iz2lsc
|
Re: soemtimes Flex (SmartSDR) and logger lose each other
How is SmartSDR working now? I see no software updates, but Flex is?now offering a new radio ... looks to me like a 500w version (with built in ATU) of the 8xxx, 73.
On 05/14/2025 10:58 AM EDT Johan ZS1A via groups.io <j-s@...> wrote:
?
?
Hi Frank and Oom Bob. (It is a South African thing)
Ok I will from now on start Smart SDR first then Logger .? I also changed? the radio setup from Power SDR to Smart SDR..
Thanks Bob I enabled the Error Trapping.
Lets roll and see how it goes.
Thanks to all.
ZS1A
|
Hi Bob,
Even ham band markers would be nice.
?
73, Gerry
|
Hi Bob, thanks to your advice I solved
I set bands & mode between 5.354 and 5.360 and now everything works.
THANKS AGAIN !
73' IK6CGO
|
I don't know how you have Logger32 configured, but when Logging FT8 QSOs?from JTDX, the FREQ_TX field is logged as VFO + Tx audio. So, your VFO frequency? was less than 5357.? Try setting the USB segment of your BandPlan to start 5354.
?
Or something like that. SeventyThree(s).
On 05/16/2025 9:11 AM EDT IK6CGO via groups.io <ik6cgo@...> wrote:
?
?
5,357?
|
|
|
What is the frequency of the QSO with no band? SeventyThree(s)
On 05/16/2025 8:42 AM EDT IK6CGO via groups.io <ik6cgo@...> wrote:
?
?
A new screenshot of my Logbook page (only now I noticed this detail)
As you can see in the BAND field the band is not written
|
The error message is from Logger32. It is trying to modify a QSO in the logbook. If the modified record is missing a callsign, a band, or mode, you will see this message, and the logbook entry is not modified. In American, that's known as CYA. SeventyThree(s).
On 05/16/2025 8:26 AM EDT IK6CGO via groups.io <ik6cgo@...> wrote:
?
?
Hi Bob,?
this is my setup Bands & modes
I don't think the issue comes from Logger32 (qsos on 60 meters are recorded correctly) but from Rick's software N2AMG
But I'm not an expert in software and any suggestions are highly appreciated
Best 73' IK6CGO
|
A new screenshot of my Logbook page (only now I noticed this detail)
As you can see in the BAND field the band is not written
|
Hi Bob,?
this is my setup Bands & modes
I don't think the issue comes from Logger32 (qsos on 60 meters are recorded correctly) but from Rick's software N2AMG
But I'm not an expert in software and any suggestions are highly appreciated
Best 73' IK6CGO
|
Does your Logger32 know what 60m is? I just looked, and there is no 60m in my version. SeventyThree(s).
On 05/16/2025 1:58 AM EDT IK6CGO via groups.io <ik6cgo@...> wrote:
?
?
Hi,?
Logger32 version 4.0.336
L32LogSyncg version ?2.019.8
JTDX v2.2.160-rc7-d2
LogSync flagged with Auto Upload qsos to Lotw upon qso completion.
Same flag with Auto Upload qsos to ClubLog upon qso completion
So all qsos are always uploaded to Lotw and ClubLog without problems at the end of the qso
A popup appears when I work on 60 meters:
I am about to reset the complex keys in the database and have temporarily lost track of data for your QSO with (call station worked) on FT8. dbBusy flag is set to False. I have not modified your logbook. Please try this again
The qso is not uploaded to Lotw and ClubLog but is recorded on Logger32
Well... I change band, I do not touch anything on Logger32 or on L32LogSynch, I make the qso and at the end the qso is uploaded regularly on Lotw and Clublog
I change the band again, I go back to 60 meters and the same issue occurs, the qso make on 60 meter is not uploaded to Lotw and ClubLog
The issue only occurs when I'm working in 60 meters
Unfortunately I have not tested with WSJTX
What should I do to solve the problem?
Many thanks and best 73 de Gianni IK6CGO
?
|
Hi,?
Logger32 version 4.0.336
L32LogSyncg version ?2.019.8
JTDX v2.2.160-rc7-d2
LogSync flagged with Auto Upload qsos to Lotw upon qso completion.
Same flag with Auto Upload qsos to ClubLog upon qso completion
So all qsos are always uploaded to Lotw and ClubLog without problems at the end of the qso
A popup appears when I work on 60 meters:
I am about to reset the complex keys in the database and have temporarily lost track of data for your QSO with (call station worked) on FT8. dbBusy flag is set to False. I have not modified your logbook. Please try this again
The qso is not uploaded to Lotw and ClubLog but is recorded on Logger32
Well... I change band, I do not touch anything on Logger32 or on L32LogSynch, I make the qso and at the end the qso is uploaded regularly on Lotw and Clublog
I change the band again, I go back to 60 meters and the same issue occurs, the qso make on 60 meter is not uploaded to Lotw and ClubLog
The issue only occurs when I'm working in 60 meters
Unfortunately I have not tested with WSJTX
What should I do to solve the problem?
Many thanks and best 73 de Gianni IK6CGO
?
|
Re: Macros before starting JTDX
It looks like there is a timing problem. Looking at the radio debug window, I see manual start of JTDX? by clicking the menu it shows a line Sent $command blah;blah;blah;$' then another line Direct radio command blah;blah;blah;? The first line says the macro is queued to be sent. The second line says it has been sent to the radio.
?
With quick switch enabled, and clicking on an FT8 DX Spot, the Direct radio command is not sent before the port is closed.
?
I will make changes for the next auto-update.?
?
?
On 05/15/2025 1:19 AM EDT Vytas VQ via groups.io <v.kudelis@...> wrote:
?
?
Hello, when I start JTDX from UDP, the written macros work. If I start JTDX from DX Spot, the macros do not work. Delay after starting JTDX does not affect this.
Thanks!
73?? Vytas?? LZ2VQ
|
Re: Macros before starting JTDX
Hi Aki.? You misunderstood me. JTDX starts, but macros don't run.
73??? Vytas? LZ2VQ
2025-05-15 08:24, ja1nlx via groups.io:
toggle quoted message
Show quoted text
Vytas
This macro does nothing when you click DX spot.
If you want, then "Quick switch" option should be enabled.
On 2025-05-15 ľ
14:19:10, Vytas VQ via groups.io
<v.kudelis@...> wrote:
Hello, when I start JTDX from UDP, the written macros
work. If I start JTDX from DX Spot, the macros do not
work. Delay after starting JTDX does not affect this.
Thanks!
73?? Vytas?? LZ2VQ
|
Re: Macros before starting JTDX
Vytas This macro does nothing when you click DX spot. If you want, then "Quick switch" option should be enabled.
On 2025-05-15 ľ 14:19:10, Vytas VQ via groups.io <v.kudelis@...> wrote:
Hello, when I start JTDX from UDP, the written macros work. If I
start JTDX from DX Spot, the macros do not work. Delay after
starting JTDX does not affect this.
Thanks!
73?? Vytas?? LZ2VQ
|
IK6CGO