Date   

Re: Starting JTDX with JTAlert in UDP bandmap does not work

Joseph LaFerla
 

Thanks Aki.  I assumed that would be the case.  

Joe VA3JLF


Language Files for Logger32 v4

Prasad
 

The language files for v4 of Logger32 have started arriving from the translators and are being posted on the website under the Support section: https://www.logger32.net/support.html 

The following language files have been received. I shall post other language files on the website as and when I receive them.

1.  BY
2.  EA
3. TF

For Translators: The email ID to send the translated files is vu2ptt -at- yahoo.com - Gmail does not allow the DLL files to come through.

73 de Prasad VU2PTT, W2PTT (ex-AF6DV)
Webmaster - Logger32 www.logger32.net


Re: Help Menu

Bob Schofield
 

Cancel

I figured it out after looking deeper I see I had to setup the location to the help files.  

Bob/VE1RSM


Help Menu

Bob Schofield
 

When I try to open the Help menu from the latest update I get an error message 404, page no longer exists or has been moved.

When I open Logger32 Web, and go to support documents I can open the Manual, but it is a differen address.

Bob/VE1RSM


Re: Starting JTDX with JTAlert in UDP bandmap does not work

ja1nlx
 

Joe

If use both JTDX and JTAlert then read manual carefully.

Short answer: You can not use UDP BandMap if you use JTAlert.

73

On 2021/02/22 22:29, Joseph LaFerla wrote:
I am trying to start JTDX as an autostart from JTAlert from a shortcut in the UDP Bandmap.  While JTAlert opens correctly, it does not seem to be "JTDX aware". because, after choosing to start JTDX instead of WSJT, I get a window saying "Waiting for JTDX to start" and I have to cancel out of that.  If I choose to start WSJT instead, WSJT opens up apparently correctly.

Starting JTAlert separately, i.e from the same shortcut but outside of the UDP bandmap, JTDX starts correctly. 

Am I missing something, probably something obvious?!

Thanks in advance.

Joe VA3JLF
--

73
aki JA1NLX


Starting JTDX with JTAlert in UDP bandmap does not work

Joseph LaFerla
 

I am trying to start JTDX as an autostart from JTAlert from a shortcut in the UDP Bandmap.  While JTAlert opens correctly, it does not seem to be "JTDX aware". because, after choosing to start JTDX instead of WSJT, I get a window saying "Waiting for JTDX to start" and I have to cancel out of that.  If I choose to start WSJT instead, WSJT opens up apparently correctly.

Starting JTAlert separately, i.e from the same shortcut but outside of the UDP bandmap, JTDX starts correctly. 

Am I missing something, probably something obvious?!

Thanks in advance.

Joe VA3JLF


v4.0.244 is on-line ...

Bob
 

Some bug fixes. 73.


Re: Cherry picking

Bob
 

Correct, but the cherry-picker relies on coloring/highlighting of the UDP BandMap to determine which cherries to pick. SeventyThree(s).

On 02/21/2021 4:39 PM Damian M0BKV via groups.io <damianm0bkv@...> wrote:
 
 
Excuse me if I'm wrong but the Cherry-picker, to my understanding, gets it's instruction through the UDP bandmap from your Logger32 log  The JTDX log and colours hasn't any influence.

On Sun, Feb 21, 2021, 19:58 Matthias Bellmann < Dk4wd@...> wrote:
 
Hi Bob
no, the station being calles is NOT shown in UDP-Bandmap, it is show in JTDX marked green (as wkg b4)
Until today i used logger 3. 50something
event viewer shows "Need IN52 on 40m/FT8 in Februar" Suppose this is the point? What must i do?
 
Gesendet: Sonntag, 21. Februar 2021 um 20:51 Uhr
Von: "Bob" < k4cy@...>
An:  hamlogger@groups.io
Betreff: Re: [hamlogger] Cherry picking
Well, Mattais, the first thing you have ignored is auto-update. The current version of Logger32 is v4.0.243 and there probably will be another one tomorrow.
 
When you say the cherry picker calls stations you have worked before, are those stations visible on the UDP BandMap? 
 
If you are configured for the cherry-picker to call any highlighted callsign, then the cherry-picker will do that. If a call is highlighted with "Need confirmation" color then the cherry picker will keep calling until the color is turned off. It does as it is told.
 
The Cherry-picker event viewer tell you exactly why it is calling a station. What does it say?
 
SeventyThree(s).
 
On 02/21/2021 2:36 PM Matthias Bellmann < dk4wd@...> wrote:
 
 
Some month ago i got cherry picking to work fine, but only for a short time.
I am using logger V 4.0.132 and HELP 4.0.242.
My setup:
udp bandmap - config - show/block callsigns worked before - :
      show/block callsigns qsod this band/mode b4
      block selected callsigns QSOd b4
Nevertheless my cherry-picker keeps calling stations qsod b4, even when the last qso was only few minutes ago.
Is there anything i ignored?
 73 Matthias dk4wd
 
 

 

 


Re: Cherry picking

Damian M0BKV
 

Excuse me if I'm wrong but the Cherry-picker, to my understanding, gets it's instruction through the UDP bandmap from your Logger32 log  The JTDX log and colours hasn't any influence.


On Sun, Feb 21, 2021, 19:58 Matthias Bellmann <Dk4wd@...> wrote:
 
Hi Bob
no, the station being calles is NOT shown in UDP-Bandmap, it is show in JTDX marked green (as wkg b4)
Until today i used logger 3. 50something
event viewer shows "Need IN52 on 40m/FT8 in Februar" Suppose this is the point? What must i do?
 
Gesendet: Sonntag, 21. Februar 2021 um 20:51 Uhr
Von: "Bob" <k4cy@...>
An: hamlogger@groups.io
Betreff: Re: [hamlogger] Cherry picking
Well, Mattais, the first thing you have ignored is auto-update. The current version of Logger32 is v4.0.243 and there probably will be another one tomorrow.
 
When you say the cherry picker calls stations you have worked before, are those stations visible on the UDP BandMap? 
 
If you are configured for the cherry-picker to call any highlighted callsign, then the cherry-picker will do that. If a call is highlighted with "Need confirmation" color then the cherry picker will keep calling until the color is turned off. It does as it is told.
 
The Cherry-picker event viewer tell you exactly why it is calling a station. What does it say?
 
SeventyThree(s).
 
On 02/21/2021 2:36 PM Matthias Bellmann <dk4wd@...> wrote:
 
 
Some month ago i got cherry picking to work fine, but only for a short time.
I am using logger V 4.0.132 and HELP 4.0.242.
My setup:
udp bandmap - config - show/block callsigns worked before - :
      show/block callsigns qsod this band/mode b4
      block selected callsigns QSOd b4
Nevertheless my cherry-picker keeps calling stations qsod b4, even when the last qso was only few minutes ago.
Is there anything i ignored?
 73 Matthias dk4wd
 
 


Re: Band plan : Invalid Operation pop up

Radio Ktwonf
 

DUH- that works very well   :)
TNX K2NF


On Sun, Feb 21, 2021 at 2:59 PM Bob <k4cy@...> wrote:
Click VIEW and UNcheck the option ENABLE OUT OF BAND MESSAGES. SeventyThree(s).
On 02/21/2021 2:56 PM Radio Ktwonf <k2nf.k2nf@...> wrote:
 
 
image.png Anyone know a way to fully disable this warning or make it self clearing, i.e have it pop up when you go out of the band map frequency range and auto - clear when you go back into the band map frequency range ? 
 
TIA K2NF 

--
K2NF


--
K2NF


Re: Cherry picking

Bob
 

This is correct. You probable need to work new gridsquares once per band/mode, and not once per band/mode/month. SeventyThree(s).          

On 02/21/2021 3:05 PM Matthias Bellmann <dk4wd@...> wrote:
 
 
In the meantime i disabled in udp bandmap highlight colors "need gridsquare b/m in 2021 and "need gridsqare b/m in fbruary".
Was that my mistake?
 
 
Gesendet: Sonntag, 21. Februar 2021 um 20:58 Uhr
Von: "Matthias Bellmann" <Dk4wd@...>
An: hamlogger@groups.io
Betreff: Re: [hamlogger] Cherry picking
 
Hi Bob
no, the station being calles is NOT shown in UDP-Bandmap, it is show in JTDX marked green (as wkg b4)
Until today i used logger 3. 50something
event viewer shows "Need IN52 on 40m/FT8 in Februar" Suppose this is the point? What must i do?
 
Gesendet: Sonntag, 21. Februar 2021 um 20:51 Uhr
Von: "Bob" <k4cy@...>
An: hamlogger@groups.io
Betreff: Re: [hamlogger] Cherry picking
Well, Mattais, the first thing you have ignored is auto-update. The current version of Logger32 is v4.0.243 and there probably will be another one tomorrow.
 
When you say the cherry picker calls stations you have worked before, are those stations visible on the UDP BandMap? 
 
If you are configured for the cherry-picker to call any highlighted callsign, then the cherry-picker will do that. If a call is highlighted with "Need confirmation" color then the cherry picker will keep calling until the color is turned off. It does as it is told.
 
The Cherry-picker event viewer tell you exactly why it is calling a station. What does it say?
 
SeventyThree(s).
 
On 02/21/2021 2:36 PM Matthias Bellmann <dk4wd@...> wrote:
 
 
Some month ago i got cherry picking to work fine, but only for a short time.
I am using logger V 4.0.132 and HELP 4.0.242.
My setup:
udp bandmap - config - show/block callsigns worked before - :
      show/block callsigns qsod this band/mode b4
      block selected callsigns QSOd b4
Nevertheless my cherry-picker keeps calling stations qsod b4, even when the last qso was only few minutes ago.
Is there anything i ignored?
 73 Matthias dk4wd
 
 


Re: Cherry picking

Matthias Bellmann
 

Many thanks and stay safe. Community needs you!
 
 
Gesendet: Sonntag, 21. Februar 2021 um 21:01 Uhr
Von: "Bob" <k4cy@...>
An: hamlogger@groups.io
Betreff: Re: [hamlogger] Cherry picking
On the UDP BandMap click CONFIG | CHERRY-PICKING OPTIONS | SETUP GRIDSQUARE CALLING OPTIONS. SeventyThree(s).

On 02/21/2021 2:58 PM Matthias Bellmann <dk4wd@...> wrote:
 
 
 
Hi Bob
no, the station being calles is NOT shown in UDP-Bandmap, it is show in JTDX marked green (as wkg b4)
Until today i used logger 3. 50something
event viewer shows "Need IN52 on 40m/FT8 in Februar" Suppose this is the point? What must i do?
 
Gesendet: Sonntag, 21. Februar 2021 um 20:51 Uhr
Von: "Bob" <k4cy@...>
An: hamlogger@groups.io
Betreff: Re: [hamlogger] Cherry picking
Well, Mattais, the first thing you have ignored is auto-update. The current version of Logger32 is v4.0.243 and there probably will be another one tomorrow.
 
When you say the cherry picker calls stations you have worked before, are those stations visible on the UDP BandMap? 
 
If you are configured for the cherry-picker to call any highlighted callsign, then the cherry-picker will do that. If a call is highlighted with "Need confirmation" color then the cherry picker will keep calling until the color is turned off. It does as it is told.
 
The Cherry-picker event viewer tell you exactly why it is calling a station. What does it say?
 
SeventyThree(s).
 
On 02/21/2021 2:36 PM Matthias Bellmann <dk4wd@...> wrote:
 
 
Some month ago i got cherry picking to work fine, but only for a short time.
I am using logger V 4.0.132 and HELP 4.0.242.
My setup:
udp bandmap - config - show/block callsigns worked before - :
      show/block callsigns qsod this band/mode b4
      block selected callsigns QSOd b4
Nevertheless my cherry-picker keeps calling stations qsod b4, even when the last qso was only few minutes ago.
Is there anything i ignored?
 73 Matthias dk4wd
 
 


Re: Cherry picking

Matthias Bellmann
 

In the meantime i disabled in udp bandmap highlight colors "need gridsquare b/m in 2021 and "need gridsqare b/m in fbruary".
Was that my mistake?
 
 
Gesendet: Sonntag, 21. Februar 2021 um 20:58 Uhr
Von: "Matthias Bellmann" <Dk4wd@...>
An: hamlogger@groups.io
Betreff: Re: [hamlogger] Cherry picking
 
Hi Bob
no, the station being calles is NOT shown in UDP-Bandmap, it is show in JTDX marked green (as wkg b4)
Until today i used logger 3. 50something
event viewer shows "Need IN52 on 40m/FT8 in Februar" Suppose this is the point? What must i do?
 
Gesendet: Sonntag, 21. Februar 2021 um 20:51 Uhr
Von: "Bob" <k4cy@...>
An: hamlogger@groups.io
Betreff: Re: [hamlogger] Cherry picking
Well, Mattais, the first thing you have ignored is auto-update. The current version of Logger32 is v4.0.243 and there probably will be another one tomorrow.
 
When you say the cherry picker calls stations you have worked before, are those stations visible on the UDP BandMap? 
 
If you are configured for the cherry-picker to call any highlighted callsign, then the cherry-picker will do that. If a call is highlighted with "Need confirmation" color then the cherry picker will keep calling until the color is turned off. It does as it is told.
 
The Cherry-picker event viewer tell you exactly why it is calling a station. What does it say?
 
SeventyThree(s).
 

On 02/21/2021 2:36 PM Matthias Bellmann <dk4wd@...> wrote:
 
 
Some month ago i got cherry picking to work fine, but only for a short time.
I am using logger V 4.0.132 and HELP 4.0.242.
My setup:
udp bandmap - config - show/block callsigns worked before - :
      show/block callsigns qsod this band/mode b4
      block selected callsigns QSOd b4
Nevertheless my cherry-picker keeps calling stations qsod b4, even when the last qso was only few minutes ago.
Is there anything i ignored?
 73 Matthias dk4wd
 
 


Re: Cherry picking

Bob
 

On the UDP BandMap click CONFIG | CHERRY-PICKING OPTIONS | SETUP GRIDSQUARE CALLING OPTIONS. SeventyThree(s).

On 02/21/2021 2:58 PM Matthias Bellmann <dk4wd@...> wrote:
 
 
 
Hi Bob
no, the station being calles is NOT shown in UDP-Bandmap, it is show in JTDX marked green (as wkg b4)
Until today i used logger 3. 50something
event viewer shows "Need IN52 on 40m/FT8 in Februar" Suppose this is the point? What must i do?
 
Gesendet: Sonntag, 21. Februar 2021 um 20:51 Uhr
Von: "Bob" <k4cy@...>
An: hamlogger@groups.io
Betreff: Re: [hamlogger] Cherry picking
Well, Mattais, the first thing you have ignored is auto-update. The current version of Logger32 is v4.0.243 and there probably will be another one tomorrow.
 
When you say the cherry picker calls stations you have worked before, are those stations visible on the UDP BandMap? 
 
If you are configured for the cherry-picker to call any highlighted callsign, then the cherry-picker will do that. If a call is highlighted with "Need confirmation" color then the cherry picker will keep calling until the color is turned off. It does as it is told.
 
The Cherry-picker event viewer tell you exactly why it is calling a station. What does it say?
 
SeventyThree(s).
 
On 02/21/2021 2:36 PM Matthias Bellmann <dk4wd@...> wrote:
 
 
Some month ago i got cherry picking to work fine, but only for a short time.
I am using logger V 4.0.132 and HELP 4.0.242.
My setup:
udp bandmap - config - show/block callsigns worked before - :
      show/block callsigns qsod this band/mode b4
      block selected callsigns QSOd b4
Nevertheless my cherry-picker keeps calling stations qsod b4, even when the last qso was only few minutes ago.
Is there anything i ignored?
 73 Matthias dk4wd
 
 


Re: Band plan : Invalid Operation pop up

Bob
 

Click VIEW and UNcheck the option ENABLE OUT OF BAND MESSAGES. SeventyThree(s).

On 02/21/2021 2:56 PM Radio Ktwonf <k2nf.k2nf@...> wrote:
 
 
image.png Anyone know a way to fully disable this warning or make it self clearing, i.e have it pop up when you go out of the band map frequency range and auto - clear when you go back into the band map frequency range ? 
 
TIA K2NF 

--
K2NF


Re: Cherry picking

Matthias Bellmann
 

 
Hi Bob
no, the station being calles is NOT shown in UDP-Bandmap, it is show in JTDX marked green (as wkg b4)
Until today i used logger 3. 50something
event viewer shows "Need IN52 on 40m/FT8 in Februar" Suppose this is the point? What must i do?
 
Gesendet: Sonntag, 21. Februar 2021 um 20:51 Uhr
Von: "Bob" <k4cy@...>
An: hamlogger@groups.io
Betreff: Re: [hamlogger] Cherry picking
Well, Mattais, the first thing you have ignored is auto-update. The current version of Logger32 is v4.0.243 and there probably will be another one tomorrow.
 
When you say the cherry picker calls stations you have worked before, are those stations visible on the UDP BandMap? 
 
If you are configured for the cherry-picker to call any highlighted callsign, then the cherry-picker will do that. If a call is highlighted with "Need confirmation" color then the cherry picker will keep calling until the color is turned off. It does as it is told.
 
The Cherry-picker event viewer tell you exactly why it is calling a station. What does it say?
 
SeventyThree(s).
 

On 02/21/2021 2:36 PM Matthias Bellmann <dk4wd@...> wrote:
 
 
Some month ago i got cherry picking to work fine, but only for a short time.
I am using logger V 4.0.132 and HELP 4.0.242.
My setup:
udp bandmap - config - show/block callsigns worked before - :
      show/block callsigns qsod this band/mode b4
      block selected callsigns QSOd b4
Nevertheless my cherry-picker keeps calling stations qsod b4, even when the last qso was only few minutes ago.
Is there anything i ignored?
 73 Matthias dk4wd
 
 


Band plan : Invalid Operation pop up

Radio Ktwonf
 

image.pngAnyone know a way to fully disable this warning or make it self clearing, i.e have it pop up when you go out of the band map frequency range and auto - clear when you go back into the band map frequency range ? 

TIA K2NF 

--
K2NF


Re: Cherry picking

Bob
 

Well, Mattais, the first thing you have ignored is auto-update. The current version of Logger32 is v4.0.243 and there probably will be another one tomorrow.
 
When you say the cherry picker calls stations you have worked before, are those stations visible on the UDP BandMap? 
 
If you are configured for the cherry-picker to call any highlighted callsign, then the cherry-picker will do that. If a call is highlighted with "Need confirmation" color then the cherry picker will keep calling until the color is turned off. It does as it is told.
 
The Cherry-picker event viewer tell you exactly why it is calling a station. What does it say?
 
SeventyThree(s).
 

On 02/21/2021 2:36 PM Matthias Bellmann <dk4wd@...> wrote:
 
 
Some month ago i got cherry picking to work fine, but only for a short time.
I am using logger V 4.0.132 and HELP 4.0.242.
My setup:
udp bandmap - config - show/block callsigns worked before - :
      show/block callsigns qsod this band/mode b4
      block selected callsigns QSOd b4
Nevertheless my cherry-picker keeps calling stations qsod b4, even when the last qso was only few minutes ago.
Is there anything i ignored?
 73 Matthias dk4wd
 
 


Cherry picking

Matthias Bellmann
 

Some month ago i got cherry picking to work fine, but only for a short time.
I am using logger V 4.0.132 and HELP 4.0.242.
My setup:
udp bandmap - config - show/block callsigns worked before - :
      show/block callsigns qsod this band/mode b4
      block selected callsigns QSOd b4
Nevertheless my cherry-picker keeps calling stations qsod b4, even when the last qso was only few minutes ago.
Is there anything i ignored?
 73 Matthias dk4wd
 
 


Re: Logbook Page Columns

Bob
 

You were probably sorting the logbook by/with the column you hid. You will notice (when things are working as expected) that one of the column headers. This is how the logbook page is sorted. Typically the Date column is the column to sort by (unless your looking for something specific). Have you tried clicking on the DATE column header to sort the logbook correctly. SeventyThree(s).

On 02/21/2021 2:11 PM ai3h@... wrote:
 
 
Hi, In the Logbook page I was moving some columns around, which worked fine, but when I tried to hide one column in the Logbook Page Window, by deselecting the Column is Visible box, my whole log disappeared and a new completely empty Logbook page appeared.  I deselected the User 1 column, which was empty to begin with.

Does anyone have any suggestions on how to recover my logbook?

Mike, AI3H

1961 - 1980 of 84754