Date   

Re: Logger 32 / Wsjtx / Cherry picking

Bob
 

Open the cherry-picking event viewer (and all will be revealed) ... Send a picture of the events that occurred.  I suspect you will see Logger32 send a command to WSJT to call the station. After a few seconds Logger32 noticed that WSJT was not transmitting (How Rude!). So, Logger32 gets in a huff, and tells WSJT to forget it and turn off TxEnabled ... ad nauseum  ... If this is what you see, there's an option somewhere on WSJT (I don't have it on my PC) to enable it to accept UDP reply messages ... SeventyThree(s).

On 07/06/2020 5:55 PM nodrog79 via groups.io <nodrog79@...> wrote:


Hi, 

I'm pulling my hair out with this one and would appreciate if anyone could help. 

I have wsjt-x working great. I have tried to go one further and use this with Logger 32 and the cherry-picking option. 

I right click UDP and open up the bandmap. The band map then populates with CQs coming from wsjt-x. 

I tick the cherry picking box and it automatically starts calling new countries from the CQ calls on wsjtx. 

Should the station reply it immediately sends a TX halt message to Wsjtx and starts calling any other CQing call sign which is a new country. It will do this all day calling new wanted stations but won't initiate the QSO sequence. Its seems to just halt as soon as there is a reply.

I can't find a lot of information on this and it seems to be almost working but I'm not sure what to try now. 

Can anyone help? 

Best 73

Gordon
GM7WCO 


Logger 32 / Wsjtx / Cherry picking

nodrog79@...
 

Hi, 

I'm pulling my hair out with this one and would appreciate if anyone could help. 

I have wsjt-x working great. I have tried to go one further and use this with Logger 32 and the cherry-picking option. 

I right click UDP and open up the bandmap. The band map then populates with CQs coming from wsjt-x. 

I tick the cherry picking box and it automatically starts calling new countries from the CQ calls on wsjtx. 

Should the station reply it immediately sends a TX halt message to Wsjtx and starts calling any other CQing call sign which is a new country. It will do this all day calling new wanted stations but won't initiate the QSO sequence. Its seems to just halt as soon as there is a reply.

I can't find a lot of information on this and it seems to be almost working but I'm not sure what to try now. 

Can anyone help? 

Best 73

Gordon
GM7WCO 


Re: Telnet

Bob
 



73

On 07/05/2020 3:10 PM redd@... wrote:


GB7UJS

On Sun, Jul 5, 2020 at 02:07 PM, Bob wrote:
What DX Cluster are you trying to connect to? 73.


Re: Telnet

redd@...
 

GB7UJS


On Sun, Jul 5, 2020 at 02:07 PM, Bob wrote:
What DX Cluster are you trying to connect to? 73.


Re: Telnet

Bob
 

What DX Cluster are you trying to connect to? 73.

On 07/05/2020 2:03 PM redd@... wrote:


I can not connect via Telnet (DX cluster), winsock returned:


Re: Telnet

redd@...
 

thank


Re: Telnet

redd@...
 

Ok, it began to work


Re: Telnet

Vilhjalmur Sigurjonsson
 

First Help file section 3.7.2

Try this one, it is working FB

 

 

73 Villi
TF3VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of redd@...
Sent: sunnudagur, 5. júlí 2020 18:41
To: hamlogger@groups.io
Subject: Re: [hamlogger] Telnet

 

Where to register a cluster ???



On Sun, Jul 5, 2020 at 01:21 PM, Jan wrote:

Your default cluster may be oof line. Try another cluster


Re: Telnet

redd@...
 

Where to register a cluster ???


On Sun, Jul 5, 2020 at 01:21 PM, Jan wrote:
Your default cluster may be oof line. Try another cluster


Re: Telnet

Jan
 

Your default cluster may be oof line. Try another cluster

73
Jan PA4JJ

Op 5-7-2020 om 20:03 schreef redd@...:

I can not connect via Telnet (DX cluster), winsock returned:

-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Telnet

redd@...
 


I can not connect via Telnet (DX cluster), winsock returned:


Re: Any Help appreciated

Bob
 

Good job Mike. Hard to tell from the picture, but are you filtering out the digital modes du jour from the BandMaps? You can block them from the DX Spots Window and the BandMaps. So, in theory, all you'd see are CW spots. I can see beacon spots in the BandMaps, you should be able to block them as well. Enjoy, 73.

On 07/05/2020 12:29 PM Michael Buckle via groups.io <mikejohnb@...> wrote:


Bob, I have sorted the RTTY selection issue, I have no idea why Logger32 suddenly started selecting RTTY instead of CW, perhaps the Gremlins have attacked.

I rebuilt any Band Monitor which demonstrated the RTTY issue by deleting the original monitor and replacing it with a newly formatted replacement.

As you suggested, I have zoomed the monitor windows to show only the first 100Khz and reset the Graticule Scale to 10Khz as shown on the Photo Below. Once again Bob, thanks for your help, 73s Mike G4RMV

On 04/07/2020 16:26, Bob wrote:
If you operate CW only, then yes, remove all the other modes from the BandPlan (if nothing else it will make things go much faster without having to plough through all the garbage to get to CW at the bottom of the list. Also, if you use the Logger32 CW Machine, toy can click the "Mode from Sound Card/CW Machine" option. that way, when the CW Machine is open the radio mode defaults to CW. SeventyThree(s).
On 07/04/2020 11:16 AM Michael Buckle via groups.io <mikejohnb@...> wrote:




Re: strange resut in v3.5 and in v4

Jim Hargrave
 

We can't reveal everything. J

Jim – w5ifp-

 

>> -----Original Message-----

>> From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf

>> Of Tom Wylie

>> Sent: Sunday, July 5, 2020 11:23 AM

>> To: hamlogger@groups.io

>> Subject: Re: [hamlogger] strange resut in v3.5 and in v4

>>

>> Which Christmas?  :o)

>>

>>

>>

>> Tom

>> GM4FDM

>>

>> On 05/07/2020 17:15, Jim Hargrave wrote:

>> > Mike,

>> >

>> > L32 ver 4.0 is in controlled Beta /Debug testing.

>> >

>> > Anticipate public release by Christmas.

>> >

>> > Jim – w5ifp-*//*

>> >

>> > *From:*hamlogger@groups.io [mailto:hamlogger@groups.io] *On

>> Behalf Of *Mike

>> > *Sent:* Sunday, July 5, 2020 10:37 AM

>> > *To:* hamlogger@groups.io

>> > *Subject:* Re: [hamlogger] strange resut in v3.5 and in v4

>> >

>> >  From where did you get L32 4.0?

>> > Mike

>> >

>> >

>>

>>


Re: strange resut in v3.5 and in v4

Jan
 

The white one Tom... :-D

73
Jan
PA4JJ
Op 5-7-2020 om 18:23 schreef Tom Wylie:
Which Christmas?  :o)



Tom
GM4FDM

On 05/07/2020 17:15, Jim Hargrave wrote:
Mike,

L32 ver 4.0 is in controlled Beta /Debug testing.

Anticipate public release by Christmas.

Jim – w5ifp-*//*

*From:*hamlogger@groups.io [mailto:hamlogger@groups.io] *On Behalf Of *Mike
*Sent:* Sunday, July 5, 2020 10:37 AM
*To:* hamlogger@groups.io
*Subject:* Re: [hamlogger] strange resut in v3.5 and in v4

 From where did you get L32 4.0?
Mike






-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Re: strange resut in v3.5 and in v4

Bob
 

A valid question Tom. That entirely depends on when new state-of-the-art documentation is available. SeventyThree(s).

On 07/05/2020 12:23 PM Tom Wylie <thomasgwylie@...> wrote:


Which Christmas? :o)



Tom
GM4FDM

On 05/07/2020 17:15, Jim Hargrave wrote:
Mike,

L32 ver 4.0 is in controlled Beta /Debug testing.

Anticipate public release by Christmas.

Jim – w5ifp-*//*

*From:*hamlogger@groups.io [mailto:hamlogger@groups.io] *On Behalf Of *Mike
*Sent:* Sunday, July 5, 2020 10:37 AM
*To:* hamlogger@groups.io
*Subject:* Re: [hamlogger] strange resut in v3.5 and in v4

From where did you get L32 4.0?
Mike


Re: Any Help appreciated

Michael Buckle
 

Bob, I have sorted the RTTY selection issue, I have no idea why Logger32 suddenly started selecting RTTY instead of CW, perhaps the Gremlins have attacked.

I rebuilt any Band Monitor which demonstrated the RTTY issue by deleting the original monitor and replacing it with a newly formatted replacement.

As you suggested, I have zoomed the monitor windows to show only the first 100Khz and reset the Graticule Scale to 10Khz as shown on the Photo Below. Once again Bob, thanks for your help, 73s Mike G4RMV

On 04/07/2020 16:26, Bob wrote:
If you operate CW only, then yes, remove all the other modes from the BandPlan (if nothing else it will make things go much faster without having to plough through all the garbage to get to CW at the bottom of the list. Also, if you use the Logger32 CW Machine, toy can click the "Mode from Sound Card/CW Machine" option. that way, when the CW Machine is open the radio mode defaults to CW. SeventyThree(s).
On 07/04/2020 11:16 AM Michael Buckle via groups.io <mikejohnb@...> wrote:




Re: strange resut in v3.5 and in v4

Tom Wylie
 

Which Christmas? :o)



Tom
GM4FDM

On 05/07/2020 17:15, Jim Hargrave wrote:
Mike,
L32 ver 4.0 is in controlled Beta /Debug testing.
Anticipate public release by Christmas.
Jim – w5ifp-*//*
*From:*hamlogger@groups.io [mailto:hamlogger@groups.io] *On Behalf Of *Mike
*Sent:* Sunday, July 5, 2020 10:37 AM
*To:* hamlogger@groups.io
*Subject:* Re: [hamlogger] strange resut in v3.5 and in v4
From where did you get L32 4.0?
Mike


Re: strange resut in v3.5 and in v4

Jim Hargrave
 

Mike,

 

L32 ver 4.0 is in controlled Beta /Debug testing.

Anticipate public release by Christmas.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Mike
Sent: Sunday, July 5, 2020 10:37 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

From where did you get L32 4.0?
Mike


Re: strange resut in v3.5 and in v4

Mike
 

From where did you get L32 4.0?
Mike


Re: new contacts not populating the logbook

Bob
 

First, make sure that the Logbook Page Window is sorted by DATE (Click on the QSO DATE column header - the text will turn red). If you are sorted by some other field, then new QSOs will not necessarily be added at the bottom of the Logbook Page. SeventyThree(s).

On 07/05/2020 10:36 AM John Caulfield <jcaulfield@...> wrote:


When I enter (try to) a new contact it will not populate the logbook.
I  started a new logbook and that worked and then I imported the old log files into the new logbook and the problem started again.  do I have some sort of corruption and how might I  fix it?
thanks
John KØFUZ