Date   

Re: DX spots have stopped

KX2A
 

Jim,

I followed these links: DX spots-> Setup -> DX spot -> blocking/pass filters -> tabbed display. I created the following:
Spotting cont. : no checks
Destination cont. : no checks
Band: blocked 60 M and 6 M and higher
Mode: no checks
DX: no checks
Originator: one US station blocked
Comment: blocked "Please"
Dupes: no checks

Result was still no spots to DX spots grid

73,
Jan, KX2A


Re: Comments from DX spots

n5kd
 

Ah…. I found it.

 

I had checked the box that says “Transfer DX comments to this field”.

 

You pointed me the right way… Thanks Aki.

 

73’ Pete, N5KD.

 

 

 

Sent from Mail for Windows 10

 

From: ja1nlx
Sent: Thursday, February 27, 2020 11:22 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Comments from DX spots

 

Pete

What is adif field for User field 5 ?

I do not duplicate this though...

73

On 2020/02/28 8:08, n5kd wrote:

Good evening,

 

I have a small issue since I upgraded to version 408 (I think that’s when it started).

 

When I click on a DX spot, the comments from that spot are being transferred into my log entry window in the “User field 5”.

 

It overwrites the preset text I have in there.

 

Is it just me? I have checked my settings for user field setup, and QSO masks. I don’t think anything has changed my end. So, currently my rig is being logged as a “Bingo”.   Must be a new Yaesu or something.

 

73’ Pete, N5KD.

 

 

 

 

Sent from Mail for Windows 10

 

--
73 de aki
JA1NLX

 


Re: Comments from DX spots

ja1nlx
 

Pete

What is adif field for User field 5 ?

I do not duplicate this though...

73

On 2020/02/28 8:08, n5kd wrote:

Good evening,

 

I have a small issue since I upgraded to version 408 (I think that’s when it started).

 

When I click on a DX spot, the comments from that spot are being transferred into my log entry window in the “User field 5”.

 

It overwrites the preset text I have in there.

 

Is it just me? I have checked my settings for user field setup, and QSO masks. I don’t think anything has changed my end. So, currently my rig is being logged as a “Bingo”.   Must be a new Yaesu or something.

 

73’ Pete, N5KD.

 

 

 

 

Sent from Mail for Windows 10

 

--
73 de aki
JA1NLX


Comments from DX spots

n5kd
 

Good evening,

 

I have a small issue since I upgraded to version 408 (I think that’s when it started).

 

When I click on a DX spot, the comments from that spot are being transferred into my log entry window in the “User field 5”.

 

It overwrites the preset text I have in there.

 

Is it just me? I have checked my settings for user field setup, and QSO masks. I don’t think anything has changed my end. So, currently my rig is being logged as a “Bingo”.   Must be a new Yaesu or something.

 

73’ Pete, N5KD.

 

 

 

 

Sent from Mail for Windows 10

 


New file uploaded to hamlogger@groups.io

hamlogger@groups.io Notification <hamlogger+notification@...>
 

Hello,

This email message is a notification to let you know that the following files have been uploaded to the Files area of the hamlogger@groups.io group.

Uploaded By: ja1nlx <ayoshida0205@...>

Description:
The revised UDP BandMap Help

Cheers,
The Groups.io Team


Re: DX spots have stopped

Jim Altman
 

Right mouse click in the DXSpots window and go to setup->DX Spot blocking/pass filters and see if you have anything checked under any of its tabs.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of KX2A
Sent: Thursday, February 27, 2020 10:20 AM
To: hamlogger@groups.io
Subject: [hamlogger] DX spots have stopped

 

When using Logger32 (any mode, not just FT8), DX spots show in the Telnet window, but no in the DX spots window.  However, the DX spots window shows when a WWV or propagation announcement is made.  "Hold off DX spots" is not checked or highlighted.

Help appreciated.

73,
Jan, KX2A


DX spots have stopped

KX2A
 

When using Logger32 (any mode, not just FT8), DX spots show in the Telnet window, but no in the DX spots window.  However, the DX spots window shows when a WWV or propagation announcement is made.  "Hold off DX spots" is not checked or highlighted.

Help appreciated.

73,
Jan, KX2A


LogPrint

Anthony Buscaglia
 

Strange.

I just went to use LogPrint and my saved label designs were gone.

I quite L32 and restarted it. Then went to LogPrint and there they were….

Well - I am good to go for now….

73
Tony
K2NV


[L32Beta] JTDX/Logger32 not playing together?

ja1nlx
 

from Bob

73
aki  JA1NLX



-------- Forwarded Message --------
Subject: [L32Beta] JTDX/Logger32 not playing together?
Date: Wed, 26 Feb 2020 18:32:19 -0500 (EST)
From: Bob <k4cy@...>
Reply-To: L32Beta@groups.io
To: L32Beta@groups.io


C'mon guys ...

A narrow band of noise/signals in JTDX waterfall ... the radio is not in USB.

Frequencies are wrong ... Doesn't matter if Logger32 is controlling the radio, or JTDX is controlling the radio, QSOs will be logged on the frequency shown in the JTDX window. The only reason Logger32 needs to know the frequency is so that UDP BandMap want/need highlights are correct ...

This is not rocket science. I will not respond to any more direct emails unless there's a bug Ineed to fix. 73.


Re: JTDX problem with band and frequency

ja1nlx
 

and this is message from the author of JTDX.

Audio level dropped for USB Audio Codec:
 
Most likely Windows applying 32-bit driver configuration to 64-bit jtdx.exe process basing on previous registry records as Windows does not recognize the change from 32-bit process to 64-bit process for the same folder/path.
Try to install rc148-win64 into C:/JTDX64 folder, it should solve the issue.

73

On 2020/02/27 6:14, ja1nlx via Groups.Io wrote:

Mine is rc-148 64 bit version. It works as expected with Logger32 ver3.50.308.

Only thing we notice that it need re-adjust sound in/out level.

Jan

Please re-check your UDP BandMap settings.This option should be checked.

73


On 2020/02/27 6:02, Vilhjalmur Sigurjonsson wrote:

Jan,

Did you load the 32 bit or 64 bit version?

I downloaded the 64 bit version today and ran it with 3.50.308. It showed all kinds of anomalies here, I had to reconfigure the JTDX for display and other things.

I am in the process of installing the 32 bit version to see if that makes a difference. I think that this is JTDX, not Logger32 as I have been using  …308 for several days.

73 Villi
TF3VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of KX2A
Sent: miðvikudagur, 26. febrúar 2020 20:27
To: hamlogger@groups.io
Subject: [hamlogger] JTDX problem with band and frequency

 

I have JTDX V2.1.0-rc148, and I use it with Logger32, Version 3.50.308, which was downloaded this morning.   It was working for me yesterday.  Suddenly, today several things have gone wrong. 

First, the waterfall display showed only a large band, although the software was decoding stations.  After fiddling with the display controls, I got the correct display, and started to work stations. 

Contacts went OK, but I then discovered that,while the correct frequency was displayed in the logger data entry box, and was also recorded in the log following the QSO, every QSO was labelled as 10 meters, despite the 14 MHz. frequency in the frequency box.  I then noted that the station display for JTDX said that these were 10 meter signals (no matter what band I was on) and the analysis of what countries I needed was based on 10 meter records in Logger32, even though all these stations were on 20 meters.  I also received an error message about there being a frequency problem every time I logged a contact, although I saw the contacts enter the log.

Furthermore, when I shut down JTDX and restart it, my radio is switched to 40 meters, no matter where it was.

I think that this is a Logger32 problem.  Should I try to back up one version?  If so, how would I go about doing this?

Jan, KX2A

--
73 de aki
JA1NLX
--
73 de aki
JA1NLX


Re: JTDX problem with band and frequency

ja1nlx
 

Mine is rc-148 64 bit version. It works as expected with Logger32 ver3.50.308.

Only thing we notice that it need re-adjust sound in/out level.

Jan

Please re-check your UDP BandMap settings.This option should be checked.

73


On 2020/02/27 6:02, Vilhjalmur Sigurjonsson wrote:

Jan,

Did you load the 32 bit or 64 bit version?

I downloaded the 64 bit version today and ran it with 3.50.308. It showed all kinds of anomalies here, I had to reconfigure the JTDX for display and other things.

I am in the process of installing the 32 bit version to see if that makes a difference. I think that this is JTDX, not Logger32 as I have been using  …308 for several days.

73 Villi
TF3VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of KX2A
Sent: miðvikudagur, 26. febrúar 2020 20:27
To: hamlogger@groups.io
Subject: [hamlogger] JTDX problem with band and frequency

 

I have JTDX V2.1.0-rc148, and I use it with Logger32, Version 3.50.308, which was downloaded this morning.   It was working for me yesterday.  Suddenly, today several things have gone wrong. 

First, the waterfall display showed only a large band, although the software was decoding stations.  After fiddling with the display controls, I got the correct display, and started to work stations. 

Contacts went OK, but I then discovered that,while the correct frequency was displayed in the logger data entry box, and was also recorded in the log following the QSO, every QSO was labelled as 10 meters, despite the 14 MHz. frequency in the frequency box.  I then noted that the station display for JTDX said that these were 10 meter signals (no matter what band I was on) and the analysis of what countries I needed was based on 10 meter records in Logger32, even though all these stations were on 20 meters.  I also received an error message about there being a frequency problem every time I logged a contact, although I saw the contacts enter the log.

Furthermore, when I shut down JTDX and restart it, my radio is switched to 40 meters, no matter where it was.

I think that this is a Logger32 problem.  Should I try to back up one version?  If so, how would I go about doing this?

Jan, KX2A

--
73 de aki
JA1NLX


Re: JTDX problem with band and frequency

Vilhjalmur Sigurjonsson
 

Installed the 32bit version and all is back to normal: Normal output level, does not go to 40m at start etc.
At least for now I will just stick with the 32bit version, hihi
73 Villi
TF3VS

On 2020-02-26 21:02, Vilhjalmur Sigurjonsson wrote:
Jan,
Did you load the 32 bit or 64 bit version?
I downloaded the 64 bit version today and ran it with 3.50.308. It
showed all kinds of anomalies here, I had to reconfigure the JTDX for
display and other things.
I am in the process of installing the 32 bit version to see if that
makes a difference. I think that this is JTDX, not Logger32 as I have
been using …308 for several days.
73 Villi
TF3VS
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of
KX2A
Sent: miðvikudagur, 26. febrúar 2020 20:27
To: hamlogger@groups.io
Subject: [hamlogger] JTDX problem with band and frequency
I have JTDX V2.1.0-rc148, and I use it with Logger32, Version
3.50.308, which was downloaded this morning. It was working for me
yesterday. Suddenly, today several things have gone wrong.
First, the waterfall display showed only a large band, although the
software was decoding stations. After fiddling with the display
controls, I got the correct display, and started to work stations.
Contacts went OK, but I then discovered that,while the correct
frequency was displayed in the logger data entry box, and was also
recorded in the log following the QSO, every QSO was labelled as 10
meters, despite the 14 MHz. frequency in the frequency box. I then
noted that the station display for JTDX said that these were 10 meter
signals (no matter what band I was on) and the analysis of what
countries I needed was based on 10 meter records in Logger32, even
though all these stations were on 20 meters. I also received an error
message about there being a frequency problem every time I logged a
contact, although I saw the contacts enter the log.
Furthermore, when I shut down JTDX and restart it, my radio is
switched to 40 meters, no matter where it was.
I think that this is a Logger32 problem. Should I try to back up one
version? If so, how would I go about doing this?
Jan, KX2A
Links:
------
[1] https://groups.io/g/hamlogger/message/79005
[2] https://groups.io/mt/71573136/385597
[3] https://groups.io/g/hamlogger/post
[4] https://groups.io/g/hamlogger/editsub/385597
[5] https://groups.io/g/hamlogger/leave/defanged


Re: JTDX problem with band and frequency

Vilhjalmur Sigurjonsson
 

Jan,

Did you load the 32 bit or 64 bit version?

I downloaded the 64 bit version today and ran it with 3.50.308. It showed all kinds of anomalies here, I had to reconfigure the JTDX for display and other things.

I am in the process of installing the 32 bit version to see if that makes a difference. I think that this is JTDX, not Logger32 as I have been using  …308 for several days.

73 Villi
TF3VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of KX2A
Sent: miðvikudagur, 26. febrúar 2020 20:27
To: hamlogger@groups.io
Subject: [hamlogger] JTDX problem with band and frequency

 

I have JTDX V2.1.0-rc148, and I use it with Logger32, Version 3.50.308, which was downloaded this morning.   It was working for me yesterday.  Suddenly, today several things have gone wrong. 

First, the waterfall display showed only a large band, although the software was decoding stations.  After fiddling with the display controls, I got the correct display, and started to work stations. 

Contacts went OK, but I then discovered that,while the correct frequency was displayed in the logger data entry box, and was also recorded in the log following the QSO, every QSO was labelled as 10 meters, despite the 14 MHz. frequency in the frequency box.  I then noted that the station display for JTDX said that these were 10 meter signals (no matter what band I was on) and the analysis of what countries I needed was based on 10 meter records in Logger32, even though all these stations were on 20 meters.  I also received an error message about there being a frequency problem every time I logged a contact, although I saw the contacts enter the log.

Furthermore, when I shut down JTDX and restart it, my radio is switched to 40 meters, no matter where it was.

I think that this is a Logger32 problem.  Should I try to back up one version?  If so, how would I go about doing this?

Jan, KX2A


JTDX problem with band and frequency

KX2A
 

I have JTDX V2.1.0-rc148, and I use it with Logger32, Version 3.50.308, which was downloaded this morning.   It was working for me yesterday.  Suddenly, today several things have gone wrong. 

First, the waterfall display showed only a large band, although the software was decoding stations.  After fiddling with the display controls, I got the correct display, and started to work stations. 

Contacts went OK, but I then discovered that,while the correct frequency was displayed in the logger data entry box, and was also recorded in the log following the QSO, every QSO was labelled as 10 meters, despite the 14 MHz. frequency in the frequency box.  I then noted that the station display for JTDX said that these were 10 meter signals (no matter what band I was on) and the analysis of what countries I needed was based on 10 meter records in Logger32, even though all these stations were on 20 meters.  I also received an error message about there being a frequency problem every time I logged a contact, although I saw the contacts enter the log.

Furthermore, when I shut down JTDX and restart it, my radio is switched to 40 meters, no matter where it was.

I think that this is a Logger32 problem.  Should I try to back up one version?  If so, how would I go about doing this?

Jan, KX2A


Re: new RDA list

Sante - IK0HBN
 

Thank you Costantin!
Poka
Sante

At 17:36 26/02/2020, you wrote:
Sante,

I will post current RDA list (as .CSV) later this or next week, qrx...

--
Constantin Semyonov, UA1AKE
http://ua1ake.qrz.ru


2020-02-26 6:16 GMT+03:00, Sante - IK0HBN via Groups.Io
<ik0hbn=libero.it@groups.io>:
Hello everybody,
do anybody know where to download new RDA list started on 01/01/2020?
I look for it on FILES section at Groups.io, but there is an old
instance dated 2016.
A Russian version exists at:
http://logger32.qrz.ru/files/350admin.zip
but it's in Russian language.
Thank you
Sante


Re: new RDA list

Constantin UA1AKE
 

Sante,

I will post current RDA list (as .CSV) later this or next week, qrx...

--
Constantin Semyonov, UA1AKE
http://ua1ake.qrz.ru


2020-02-26 6:16 GMT+03:00, Sante - IK0HBN via Groups.Io
<ik0hbn=libero.it@groups.io>:

Hello everybody,
do anybody know where to download new RDA list started on 01/01/2020?
I look for it on FILES section at Groups.io, but there is an old
instance dated 2016.
A Russian version exists at:
http://logger32.qrz.ru/files/350admin.zip
but it's in Russian language.
Thank you
Sante


new RDA list

Sante - IK0HBN
 

Hello everybody,
do anybody know where to download new RDA list started on 01/01/2020? I look for it on FILES section at Groups.io, but there is an old instance dated 2016.
A Russian version exists at:
http://logger32.qrz.ru/files/350admin.zip
but it's in Russian language.
Thank you
Sante


Re: FT8 UDP logging issue

ja1nlx
 

Following additional information should be logged.

NAME, QTH, ADDRESS. COMMENT, QSL_VIA, IOTA, STATE, and CNTY

73

On 2020/02/26 7:39, ja1nlx via Groups.Io wrote:

my apologies...

The author added IOTA, QSL_VIA to be logged.

73

On 2020/02/25 23:36, Mike wrote:
On Sun, Feb 23, 2020 at 11:59 PM, ja1nlx wrote:
QSL_VIA is not logged.
Why IOTA field is logged and QSL_VIA is wiped clean?
When option:

is selected QSL_VIA should be preserved as IOTA is.
Mike
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX


Re: FT8 UDP logging issue

ja1nlx
 

my apologies...

The author added IOTA, QSL_VIA to be logged.

73

On 2020/02/25 23:36, Mike wrote:
On Sun, Feb 23, 2020 at 11:59 PM, ja1nlx wrote:
QSL_VIA is not logged.
Why IOTA field is logged and QSL_VIA is wiped clean?
When option:

is selected QSL_VIA should be preserved as IOTA is.
Mike
--
73 de aki
JA1NLX


Re: Telnet Problem

Jim Hargrave
 

Hi Dave,

I’m glad you got it sorted out. Thanks for the feedback.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of EI6AL
Sent: Tuesday, February 25, 2020 9:33 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Telnet Problem

 

Problem sorted (thanks Jim!)   Turns out the three remote hosts I was trying to connect to were all offline - hence the default to port 27754.  Simple solution was to find an online host - clusters now working perfectly.  One offline would be ok, second was coincidental, third was just not my day.

 

73     Dave EI6AL

4541 - 4560 of 83536