Date   

Re: FTDX101MP

John Owens
 

Not sure what you mean by ovrershoot? I have had my MP for over a year now, and absolutely love it. It is the highest rated transceiver in the Sherwood Engr report, and deservedly so. I have owned an FT-100MP and a FTDX 5000 and it is well beyond the 5000. -  John Owens -  N7TK

On 02/28/2021 1:47 AM Jan <hamlogger@...> wrote:
 
 
Maybe this is of topic
So I appologize if so

I am thinking of purchasing a FTDX101MP

But I would like to know if there are members in this group who own a Yaesu FTDX101MP
If so do you notice any overshoot?

73
Jan
PA4JJ



Re: v4.0.245 is on-line ...

NICK K. PLUMIDAKIS
 

Up and running

TNKS

DE

SV1VS

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Sunday, February 28, 2021 4:49 PM
To: hamlogger@groups.io
Subject: [hamlogger] v4.0.245 is on-line ...

 

Nothing exciting. Minor bug fixes. 73.

_._,_._,_


Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#82899) | Reply To Group | Reply To Sender | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [sv1vs@...]

_._ ,_._,_


Re: v4.0.245 is on-line ...

Fabio IZ8MBW
 

Thank you!

73s
Fabio, IZ8MBW



Il domenica 28 febbraio 2021, 15:48:47 CET, Bob <k4cy@...> ha scritto:


Nothing exciting. Minor bug fixes. 73.


Re: v4.0.245 is on-line ...

Dave Colliau
 

Up and running !
Dave N8DC

On 02/28/2021 9:48 AM Bob <k4cy@...> wrote:
 
 
Nothing exciting. Minor bug fixes. 73.


v4.0.245 is on-line ...

Bob
 

Nothing exciting. Minor bug fixes. 73.


Re: Cherry-picking for LoTW users only

Fabio IZ8MBW
 

Probably a nice future feature.
Have a nice day.

73s
Fabio, IZ8MBW



Il domenica 28 febbraio 2021, 11:20:53 CET, Bob <k4cy@...> ha scritto:


It is not possible. 73.
On 02/28/2021 1:58 AM Fabio IZ8MBW via groups.io <iz8mbw@...> wrote:
 
 
Hello.
is it possible to use the Cherry-picking feature (for WSJT-X or JTDX) for call only LoTW users?
Thanks.
 
73s
Fabio, IZ8MBW
 


Re: Cherry-picking for LoTW users only

Bob
 

It is not possible. 73.

On 02/28/2021 1:58 AM Fabio IZ8MBW via groups.io <iz8mbw@...> wrote:
 
 
Hello.
is it possible to use the Cherry-picking feature (for WSJT-X or JTDX) for call only LoTW users?
Thanks.
 
73s
Fabio, IZ8MBW
 


FTDX101MP

Jan
 

Maybe this is of topic
So I appologize if so

I am thinking of purchasing a FTDX101MP

But I would like to know if there are members in this group who own a Yaesu FTDX101MP
If so do you notice any overshoot?

73
Jan
PA4JJ



Cherry-picking for LoTW users only

Fabio IZ8MBW
 

Hello.
is it possible to use the Cherry-picking feature (for WSJT-X or JTDX) for call only LoTW users?
Thanks.

73s
Fabio, IZ8MBW


Re: Atomic Clock

Bob
 

A very pretty picture. What is the bug? SeventyThree(s).

On 02/27/2021 3:01 PM Marcos Lima via groups.io <py1me@...> wrote:
 
 
Hello there,
 
I discovery a little bug. 
In Get atomic Clock Time Window
The setup options d'ont work.
see picture in anexo
 
I using Ver. 4,0,244
 
73
 
Marcos Lima - PY1 ME


Atomic Clock

Marcos Lima
 

Hello there,

I discovery a little bug. 
In Get atomic Clock Time Window
The setup options d'ont work.
see picture in anexo

I using Ver. 4,0,244

73

Marcos Lima - PY1 ME


Re: ADIF error with Labrador

Fabien TK5MH
 

Hi,
Edit the bad.adi file in the logger32 directory
Change the state from DC to MD
Do the same for VE provences
Rename the file to fixed.adi or anything else
Import this file into logger32
73, Fabien


Re: Country database exceptions from Club log - update error

Gary Hinson
 

I had a failure downloading the Club Log country exceptions this morning which I took to be a sporadic network or server issue.

 

I just tried it again and it worked:

 

 

If yours is now failing every time, you might check that your PC is connecting to the Club Log server e.g. in Resouce Monitor, I see this:

 

 

[It connects initially to 5.153.81.176 which is ClubLog.org, then redirects to G7VJR.org.]

 

73
Gary  ZL2iFB

 

-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chris.9A2X
Sent: 27 February 2021 10:42
To: hamlogger@groups.io
Subject: Re: [hamlogger] Country database exceptions from Club log - update error

 

Mike,

Since I didn't find any previous posts here or elsewhere on the net with same problem described, I'm not surprised with your info. Hope that someone here have idea how to fix that corruption in my installation.

 

regards, chris

 

 

 


Re: Country database exceptions from Club log - update error

Chris.9A2X
 

Mike,
Since I didn't find any previous posts here or elsewhere on the net with same problem described, I'm not surprised with your info. Hope that someone here have idea how to fix that corruption in my installation.

regards, chris


Re: Country database exceptions from Club log - update error

Michael Harris
 

Chris,

Win10/64 Pro, L32 4.0.244

My PC has just completed that action in 68 seconds. So it seems to be working OK, not a global failure.

Regards,

Mike VP8NO

On 26/02/2021 17:28, Chris.9A2X wrote:
Hi,
I'm getting the error while trying to update 'Country database exceptions from Club log':
logger32 QRX ...Connection to https://clublog.org/cty.php failed
I checked first all the network/firewall stuff but with no results.
The upper link in Web browser throws the message:
Access to this form requires a valid API key. For more info see: https://clublog.org/need_api.php
It started to show up abt. 3 months ago with v3. It's still here after succcesfull upgrade from v3 to v4 (3.50.424 -> 4.0.132).
I realized that 'Load the LoTW users file (from Clublog)' feature hungs up as well ('Waiting...' sindrome).
73 chris


Country database exceptions from Club log - update error

Chris.9A2X
 

Hi,

I'm getting the error while trying to update 'Country database exceptions from Club log':

logger32 QRX ...Connection to https://clublog.org/cty.php failed

I checked first all the network/firewall stuff but with no results.

The upper link in Web browser throws the message:
Access to this form requires a valid API key. For more info see: https://clublog.org/need_api.php

It started to show up abt. 3 months ago with v3. It's still here after succcesfull upgrade from v3 to v4 (3.50.424 -> 4.0.132).
I realized that 'Load the LoTW users file (from Clublog)' feature hungs up as well ('Waiting...' sindrome).

73 chris


Re: UDP question

Bob
 

There's no radio being polled, and no frequency information from JTAlert. I thought that under those conditions, the BandMap was supposed to default to 20m. Oh well, never mind. SeventyThree(s).

On 02/26/2021 8:59 AM Kenneth Hansen <khansen@...> wrote:
 
 
It does, but not frequency, so I believe that is why the band map says “I’m lost”

On Fri, Feb 26, 2021 at 8:52 AM Bob < k4cy@...> wrote:
There's supposed to be some kinda JTAlert window that Logger32 can detect, and once found, read the band/mode from the windows caption. That's the theory anyway. SeventyThree(s).
On 02/26/2021 8:47 AM Kenneth Hansen < khansen@...> wrote:
 
 
Good morning,
Found an undocumented feature (I believe)
When I set the band/mode to JTAlert, the band map (not UDP band map) reports 
“I’m lost”, guess it not seeing the frequency 

On Thu, Feb 25, 2021 at 3:04 PM Bob < k4cy@...> wrote:
I don't think so. JTAlert connects to JTDX on UDP port 2237. JTAlert forwards QSL Logged messages only on UDP port 2333 (or something). 
 
So, I'd guess in Logger32 you'd configure like this:
 
a) Open the UDP BandMap.  Set the Band/Mode option to be from JTAlert. Close the UDP BandMap (There's nothing to see).
b) Open one of the receive only UDP sockets on port 2223 (or whatever). 
c) Kick back and make a not to yourself - Damn This DXing is fun.
 
SeventyThree(s).
 
 
there's no data to be displayed in the UDP MandMap.
On 02/25/2021 2:43 PM Kenneth Hansen < khansen@...> wrote:
 
 
Sorry, should be 2333 of course 

On Thu, Feb 25, 2021 at 2:35 PM Kenneth Hansen via groups.io <khansen= satsnj.com@groups.io> wrote:
All,
 
I’m looking at section 32.3 in the manual.
Does the UDP band map work together with JTAlert?
I did set the UDP port to 3332 in Logger32, but when I open the socket, JTAlert stops updating.
What am I missing?
 
de KB2SSE
Ken
--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC
 

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC


Re: UDP question

Kenneth Hansen
 

It does, but not frequency, so I believe that is why the band map says “I’m lost”

On Fri, Feb 26, 2021 at 8:52 AM Bob <k4cy@...> wrote:
There's supposed to be some kinda JTAlert window that Logger32 can detect, and once found, read the band/mode from the windows caption. That's the theory anyway. SeventyThree(s).
On 02/26/2021 8:47 AM Kenneth Hansen <khansen@...> wrote:
 
 
Good morning,
Found an undocumented feature (I believe)
When I set the band/mode to JTAlert, the band map (not UDP band map) reports 
“I’m lost”, guess it not seeing the frequency 

On Thu, Feb 25, 2021 at 3:04 PM Bob < k4cy@...> wrote:
I don't think so. JTAlert connects to JTDX on UDP port 2237. JTAlert forwards QSL Logged messages only on UDP port 2333 (or something). 
 
So, I'd guess in Logger32 you'd configure like this:
 
a) Open the UDP BandMap.  Set the Band/Mode option to be from JTAlert. Close the UDP BandMap (There's nothing to see).
b) Open one of the receive only UDP sockets on port 2223 (or whatever). 
c) Kick back and make a not to yourself - Damn This DXing is fun.
 
SeventyThree(s).
 
 
there's no data to be displayed in the UDP MandMap.
On 02/25/2021 2:43 PM Kenneth Hansen < khansen@...> wrote:
 
 
Sorry, should be 2333 of course 

On Thu, Feb 25, 2021 at 2:35 PM Kenneth Hansen via groups.io <khansen= satsnj.com@groups.io> wrote:
All,
 
I’m looking at section 32.3 in the manual.
Does the UDP band map work together with JTAlert?
I did set the UDP port to 3332 in Logger32, but when I open the socket, JTAlert stops updating.
What am I missing?
 
de KB2SSE
Ken
--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC


Re: UDP question

Bob
 

There's supposed to be some kinda JTAlert window that Logger32 can detect, and once found, read the band/mode from the windows caption. That's the theory anyway. SeventyThree(s).

On 02/26/2021 8:47 AM Kenneth Hansen <khansen@...> wrote:
 
 
Good morning,
Found an undocumented feature (I believe)
When I set the band/mode to JTAlert, the band map (not UDP band map) reports 
“I’m lost”, guess it not seeing the frequency 

On Thu, Feb 25, 2021 at 3:04 PM Bob < k4cy@...> wrote:
I don't think so. JTAlert connects to JTDX on UDP port 2237. JTAlert forwards QSL Logged messages only on UDP port 2333 (or something). 
 
So, I'd guess in Logger32 you'd configure like this:
 
a) Open the UDP BandMap.  Set the Band/Mode option to be from JTAlert. Close the UDP BandMap (There's nothing to see).
b) Open one of the receive only UDP sockets on port 2223 (or whatever). 
c) Kick back and make a not to yourself - Damn This DXing is fun.
 
SeventyThree(s).
 
 
there's no data to be displayed in the UDP MandMap.
On 02/25/2021 2:43 PM Kenneth Hansen < khansen@...> wrote:
 
 
Sorry, should be 2333 of course 

On Thu, Feb 25, 2021 at 2:35 PM Kenneth Hansen via groups.io <khansen= satsnj.com@groups.io> wrote:
All,
 
I’m looking at section 32.3 in the manual.
Does the UDP band map work together with JTAlert?
I did set the UDP port to 3332 in Logger32, but when I open the socket, JTAlert stops updating.
What am I missing?
 
de KB2SSE
Ken
--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC


Re: UDP question

Kenneth Hansen
 

Good morning,
Found an undocumented feature (I believe)
When I set the band/mode to JTAlert, the band map (not UDP band map) reports 
“I’m lost”, guess it not seeing the frequency 

On Thu, Feb 25, 2021 at 3:04 PM Bob <k4cy@...> wrote:
I don't think so. JTAlert connects to JTDX on UDP port 2237. JTAlert forwards QSL Logged messages only on UDP port 2333 (or something). 
 
So, I'd guess in Logger32 you'd configure like this:
 
a) Open the UDP BandMap.  Set the Band/Mode option to be from JTAlert. Close the UDP BandMap (There's nothing to see).
b) Open one of the receive only UDP sockets on port 2223 (or whatever). 
c) Kick back and make a not to yourself - Damn This DXing is fun.
 
SeventyThree(s).
 
 
there's no data to be displayed in the UDP MandMap.
On 02/25/2021 2:43 PM Kenneth Hansen <khansen@...> wrote:
 
 
Sorry, should be 2333 of course 

On Thu, Feb 25, 2021 at 2:35 PM Kenneth Hansen via groups.io <khansen= satsnj.com@groups.io> wrote:
All,
 
I’m looking at section 32.3 in the manual.
Does the UDP band map work together with JTAlert?
I did set the UDP port to 3332 in Logger32, but when I open the socket, JTAlert stops updating.
What am I missing?
 
de KB2SSE
Ken
--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

1881 - 1900 of 84753