Date   

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


ODP: [hamlogger] Speed change

Andy VA3PL
 

Darren
Thanks a lot...indeed it works.

Andy SP9KR


Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Darren Collins (G0TSM) <daz@...>
Wysłane: wtorek, 25 lutego 2020 18:53
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: [hamlogger] Speed change
 

$speed+$5nntu

puts my speed up by 2wpm with a Winkeyer USB then drops the speed back down (I just tried it).

73 Darren G0TSM


On 25/02/20 17:32, Andy None via Groups.Io wrote:
Hi there
I am using CW machine with WinKeyer USB.
I would like to have CW speed change for the such micro: QSL <<<5NN SP9KR>>>
None of the macros such $Speed+$ or $Speed-$ or $SpeedUP$ or $SpeedDWN$ work.
Any idea?
What am I doing it wrong?

Andy SP9KR


Re: Speed change

Darren Collins (G0TSM)
 

$speed+$5nntu

puts my speed up by 2wpm with a Winkeyer USB then drops the speed back down (I just tried it).

73 Darren G0TSM


On 25/02/20 17:32, Andy None via Groups.Io wrote:
Hi there
I am using CW machine with WinKeyer USB.
I would like to have CW speed change for the such micro: QSL <<<5NN SP9KR>>>
None of the macros such $Speed+$ or $Speed-$ or $SpeedUP$ or $SpeedDWN$ work.
Any idea?
What am I doing it wrong?

Andy SP9KR


Speed change

Andy None <va3pl@...>
 

Hi there
I am using CW machine with WinKeyer USB.
I would like to have CW speed change for the such micro: QSL <<<5NN SP9KR>>>
None of the macros such $Speed+$ or $Speed-$ or $SpeedUP$ or $SpeedDWN$ work.
Any idea?
What am I doing it wrong?

Andy SP9KR


Re: VP8PJ KC4/A?

Ilya Zozin,4Z1UF
 

Dear friends, 
Thanks a lot! It works for me.
73,
Ilya, 4Z1UF


vp8pj - s/o

John Owens
 

My thanks to those who responded to my problem with getting VP8PJ designated as S/O versus KC4/A. That problem is now solved, and thanks for the responses and suggestions.

John Owens -   N7TK
 



Re: Telnet Problem

EI6AL
 

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


FW: [L32Beta] Please post on the reflector ...

Jim Hargrave
 

Response from Bob / K4CY

 

Jim – w5ifp-

 

From: L32Beta@groups.io [mailto:L32Beta@groups.io] On Behalf Of Bob
Sent: Tuesday, February 25, 2020 8:43 AM
To: L32Beta@groups.io
Subject: [L32Beta] Please post on the reflector ...

 

Seems like I can hide, but I can't escape. I have received three direct eMails this morning about a reported Telnet problem. There are close to 4000 subscribers to the reflector. Someone must know how to make a Telnet connection … This is a demonstration of EXACTLY why the last QSO in my logbook is dated Feb 16, 2008 … I just celebrated my 12th anniversary, and thoroughly enjoying every minute of it.

 

Connect to K4UGA or VE6DXC (neither of which is currently on-line/accessible) and you'll get a reply something like this:

 

 

Google localhost port 27754 may give some insight. Having failed to connect, the port is temporarily in an unknown state. Try to connect somewhere else immediately and you will get a message like this:

 

 

Relax, count to 10, take a deep breath, and try again after 30 seconds or so (after the port has reset itself, then try to connect to a functional Telnet cluster like this:

 

 

And, please don't eMail me directly. There's more than enough subscribers on the reflector to solve these "problems". SeventyThree(s).

 

 

 


Re: FT8 UDP logging issue

Mike
 

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


Re: Telnet Problem

EI6AL
 

Thanks for the suggestions Gary.  Unfortunately I had tried those changes without success.  Both machines had been showing the clusters without a problem, one via VE6DXC and one via K4UGA.  Telnet failed on both at the same time and on different networks. After failute the full telnet startup message on the main log is as follows:

Telnet socket auto connect to 64.59.129.23 port number 8000.  Initial data received (47 bytes)  "error on connect to local host port 27754 (111) <LF>"

Any attempts to setup an alternative remote host gives me "winsock returned "invalid operation at current state".   I have added other remote hosts to the list and switched between them, always with the same result.  The problem appears to center on the switch from port 8000 to port 27754, I have no idea what the (111)<LF> messages indicate.  I can generally find solutions if I work on something long enough - I have been two days on this one and no joy!

73   Dave   EI6AL



On Mon, 24 Feb 2020 at 20:09, Gary Hinson <Gary@...> wrote:

Hi EI-ham

 

That message suggest that you may have been using a local DXcluster system, perhaps an SDR/skimmer or VE7CC’s Cluster User program, on Localhost:27754 … but for some reason that port is no longer in use.

 

To check/change the Telnet host and port settings, open the Telnet window and Local tab, then right-click à Setup à Setup remote hosts:

 

 

That opens the settings form which is fairly self-explanatory:

 

 

Type the info in the white boxes then click Add current entry to save it.  Shortcut is whatever name you like for the connection.

 

To connect directly to a DXcluster node on the Web, you’ll need to put its Telnet address and port in the Remote host and Port boxes – for example   cluster.g3ldi.co.uk    port 7000

 

To connect to a local DXcluster node running on the same PC as Logger32, use “localhost” (or “127.0.0.1”) as the Remote host address while the Port is determined by the DXcluster application you are running – often 7300 or 7373.  I don’t know where your 27754 port came from.

 

Having done that, click Connect to [shortcut] and go through the login process to start receiving DXcluster spots.

 

73

Gary  ZL2iFB

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of EI6AL
Sent: 25 February 2020 07:26
To: hamlogger@groups.io
Subject: [hamlogger] Telnet Problem

 

I use logger 32 at the home qth and on a laptop for remote.  Both now give an error message when the program starts up: error on connect to localhost port 27754 (111).  Guess this is external to logger.32 but wondering if anyone else has seen this or has any ideas? 


Re: Telnet Problem

Gary Hinson
 

Hi EI-ham

 

That message suggest that you may have been using a local DXcluster system, perhaps an SDR/skimmer or VE7CC’s Cluster User program, on Localhost:27754 … but for some reason that port is no longer in use.

 

To check/change the Telnet host and port settings, open the Telnet window and Local tab, then right-click à Setup à Setup remote hosts:

 

 

That opens the settings form which is fairly self-explanatory:

 

 

Type the info in the white boxes then click Add current entry to save it.  Shortcut is whatever name you like for the connection.

 

To connect directly to a DXcluster node on the Web, you’ll need to put its Telnet address and port in the Remote host and Port boxes – for example   cluster.g3ldi.co.uk    port 7000

 

To connect to a local DXcluster node running on the same PC as Logger32, use “localhost” (or “127.0.0.1”) as the Remote host address while the Port is determined by the DXcluster application you are running – often 7300 or 7373.  I don’t know where your 27754 port came from.

 

Having done that, click Connect to [shortcut] and go through the login process to start receiving DXcluster spots.

 

73

Gary  ZL2iFB

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of EI6AL
Sent: 25 February 2020 07:26
To: hamlogger@groups.io
Subject: [hamlogger] Telnet Problem

 

I use logger 32 at the home qth and on a laptop for remote.  Both now give an error message when the program starts up: error on connect to localhost port 27754 (111).  Guess this is external to logger.32 but wondering if anyone else has seen this or has any ideas? 


Re: VP8PJ KC4/A?

Tom Wylie
 

What I said! 🤔

Tom

On Mon, 24 Feb 2020, 18:41 DL7VOG, <gerd@...> wrote:
Shalom Ilja,
you should go to database maintenance, DXCC/Prefix maintenance, select KC4\A Antarctica - in the opening window click to the dropdown-list in the row Alternative Prefixes, scroll down - there is an entry VP8PJ which you have to delete (cklick on VP8PJ and click to the button "Delete").
Then go back to the country database mainenance window, select VP8\O. Click on it and in the upcoming window go to the dropdown list "Alternative Prefixes", write VP8PJ into it and press the "Add" button. Close all windows and insert VP8PJ into th log window. Now it should show you VP8PJ as VP8\O.

Good luck and 73 - Gerd / DL7VOG

Hope to cu in Friedrichshafen in a few weeks.



Am 24.02.2020 um 18:18 schrieb Ilya Zozin,4Z1UF:
Could you please  teach me how to do either of these?
Thanks,
Ilya, 4Z1UF


Re: VP8PJ KC4/A?

DL7VOG
 

Shalom Ilja,
you should go to database maintenance, DXCC/Prefix maintenance, select KC4\A Antarctica - in the opening window click to the dropdown-list in the row Alternative Prefixes, scroll down - there is an entry VP8PJ which you have to delete (cklick on VP8PJ and click to the button "Delete").
Then go back to the country database mainenance window, select VP8\O. Click on it and in the upcoming window go to the dropdown list "Alternative Prefixes", write VP8PJ into it and press the "Add" button. Close all windows and insert VP8PJ into th log window. Now it should show you VP8PJ as VP8\O.

Good luck and 73 - Gerd / DL7VOG

Hope to cu in Friedrichshafen in a few weeks.



Am 24.02.2020 um 18:18 schrieb Ilya Zozin,4Z1UF:

Could you please  teach me how to do either of these?
Thanks,
Ilya, 4Z1UF


Re: VP8PJ KC4/A?

Tom Wylie
 

I found that in the country database, vp8pj is listed as a callsign for KC4/a.  If delete it there you can add it as a definitive call sign for  VP8/o.  Works for me and now shows it as correct.

Tom 
GM4FDM 

On Mon, 24 Feb 2020, 18:28 Carey Magee, <arsk2rny@...> wrote:
Hi Ilya:

Here is a snippet from the Logger32 Help File.
image.png
So, at the menus on the top select 'Setup'.  Then select 'Updates, then 'Country database exceptions from ClubLog'.  You can then set it to enable auto updates (Happens every day), but also you can select to have it look for updates now.

I hope this helps!!
73,
Carey Magee, K2RNY
Rochester New York
Grid: FN13ef


On Mon, Feb 24, 2020 at 1:18 PM Ilya Zozin,4Z1UF <4z1uf@...> wrote:
Could you please  teach me how to do either of these?
Thanks,
Ilya, 4Z1UF

4581 - 4600 of 83563