Date   

Re: Refinement Request.

G4GIR
 

Ken
 
I assume you are in agreement with 1? If you are then you would need the date column to be added, as doing a SH/DX HV0A and then sorting on frequency would mix all the various spots up.
 
no2.  What use is that, they would be long out of date!!
 
No they would not  necessarily be out of date. You have a power cut, your PC and or L32 inexplicably shuts down. You've lost all the spots that were showing.
 
no3. what use is that, aren't they all today’s date?
 
No, they aren't all todays date, see below. You do a SH/DX HV0A for example when were these spots initiated, E51JD was today, or was it ? if the Date was there I would know.
 
We all do a SH/DX P5A don't we, up pops 12 entries, did I miss it? If the date was there I wouldn't be wasting time trawling the bands for it. Yes I know the date is shown in the Telnet window, but it would be cleaner if it was shown in the DX Spots window.
 
 I believe all 4 refinements go hand in hand.
 
73
 
Ian G4GIR
 
 
ImageA89466E3
 

----- Original Message -----
From: Ken McVie <kenmcvie2@...>
Sent: 15/10/2021 03:53:32
Subject: Re: [hamlogger] Refinement Request.

Ian

no2.  What use is that, they would be long out of date!!

no3. what use is that, aren't they all today’s date?

73

Ken ZL4NR

On 15/10/2021 2:42 am, g4girhb0 via groups.io wrote:
Bob
 
Is it possible to add a few refinements to the DX SPOTS window?
 
1. Have the columns able to be sorted by clicking the column headers.
2. Have the DX SPOTS retained in the window after shutting down so when re-starting the spots still show.
3. Add a date column.
4. Add a function to the RIGHT CLICK  menu to delete all spots in the DX SPOTS window.
 
Thanks
 
73
 
Ian G4GIR
 


Re: Refinement Request.

Ken McVie
 

Ian

no2.  What use is that, they would be long out of date!!

no3. what use is that, aren't they all today’s date?

73

Ken ZL4NR

On 15/10/2021 2:42 am, g4girhb0 via groups.io wrote:
Bob
 
Is it possible to add a few refinements to the DX SPOTS window?
 
1. Have the columns able to be sorted by clicking the column headers.
2. Have the DX SPOTS retained in the window after shutting down so when re-starting the spots still show.
3. Add a date column.
4. Add a function to the RIGHT CLICK  menu to delete all spots in the DX SPOTS window.
 
Thanks
 
73
 
Ian G4GIR
 


Re: SV2RSG/A

Rick Williams - VE7TK
 

I notice that the Oct 14, 2021 Country database exceptions from Club Log update has the exception for the recent Mt. Athos operation.

73, Rick
VE7TK


Re: SFI

Bob
 

... maar ek wil nie weer die Springbokke sien nie... maak nie saak hoeveel bier

On 10/14/2021 1:17 PM Johan ZS1A <j-s@...> wrote:
 
 
Dankie Oom Bob. 
Dit werk nou
Baie dankie ! Hou die Blou Bulle en die Springbokke dop die naweek ...met bier.
73ZS1A


Re: #JTDX #LOG Interface Issue? #jtdx #log

Bob
 

Bob, there are two logs at play - one in JTDX, the other in Logger32. Highlight colors in JTDX are based on what is in the JTDX log. Highlight colors in Logger32 are based on what is in the Logger32 log ... The two logs are not necessarily the same. SeventyThree(s).

On 10/14/2021 3:47 PM Bob, W3IDT <w3idt@comcast.net> wrote:


Very pleased with JTDX and Logger32 for the month or so I've been using
them; and with the help I've received from Dave, mm0hvu, and Arvo, es1ja.

I still have one problem which, I think, may be an issue with the
interface between Logger32's LOG and JTDX or, of course, some setting I
have wrong.

Attached ("W3IDT_COLORS.png") is a screen shot of the NOTIFICATIONS
color scheme I have set up in JTDX - dark green for new DXCC (as in GO);
light colors for everything else.

Also attached are two screen shots of Band Activity panel while the
programs are running:
1. "W3IDT_ON.png" shows ON4CQ in dark green - "new DXCC" -
on 15m while OO4U is in the LOG on 15m.
2. "W3IDT_LZ.png" shows the same issue: LZ4TL as "new DXCC" on 40m,
while LZ3CB is in the LOG on 15m.

What might I be doing wrong?

Bob, w3idt

--
.......
. Robert F. Teitel, W3IDT
.
. w3idt@comcast.net
. w3idt@arrl.net
........



#JTDX #LOG Interface Issue? #jtdx #log

Bob, W3IDT
 

Very pleased with JTDX and Logger32 for the month or so I've been using them; and with the help I've received from Dave, mm0hvu, and Arvo, es1ja.

I still have one problem which, I think, may be an issue with the interface between Logger32's LOG and JTDX or, of course, some setting I have wrong.

Attached ("W3IDT_COLORS.png") is a screen shot of the NOTIFICATIONS color scheme I have set up in JTDX - dark green for new DXCC (as in GO); light colors for everything else.

Also attached are two screen shots of Band Activity panel while the programs are running:
1. "W3IDT_ON.png" shows ON4CQ in dark green - "new DXCC" -
on 15m while OO4U is in the LOG on 15m.
2. "W3IDT_LZ.png" shows the same issue: LZ4TL as "new DXCC" on 40m,
while LZ3CB is in the LOG on 15m.

What might I be doing wrong?

Bob, w3idt

--
.......
. Robert F. Teitel, W3IDT
.
. w3idt@comcast.net
. w3idt@arrl.net
........


Re: SFI

John Owens
 

I meant Sh/WWV. - John Owens -  N7TK


Fw: [hamlogger] v4.0.278 auto-update is on-line ...

g4girhb0 <ian.frith@...>
 

Plus the WORKED/CONFIRMED TABLES are not updating. Also if the spot isn't a recognized FT8/FT4 frequency L32 rejects it. I guess there's now't you can do about that?
 
 
73
 
Ian G4GIR
 

----- Original Message -----
From: g4girhb0 via groups.io <ian.frith@...>
Sent: 14/10/2021 18:58:18
Subject: Fw: [hamlogger] v4.0.278 auto-update is on-line ...

Bob
 
The only thing not happening with the JTDX/DXSPOT mod, is the Logging window is not populated with the Call sign etc, after clicking on the DX SPOT.
 
73
 
Ian
G4GIR
 
----- Original Message -----
From: Ian <IAN.FRITH@...>
Sent: 14/10/2021 15:44:38
Subject: Re: [hamlogger] v4.0.278 auto-update is on-line ...

Cheers Bob,
Seems good.
 
73
 
    Ian G4GIR
 
----- Original Message -----
From: Bob <k4cy@...>
Sent: 14/10/2021 15:20:24
Subject: [hamlogger] v4.0.278 auto-update is on-line ...

This is primarily a maintenance release. Several small bugs are fixed.
Eelcraft K4 CAT support is added. It is essentially the same as the K3, but as users find differences between the two they will be added to the K4 support. The K4 CAT commands may use a embedded $ in the command. This interferes with the Logger32 practice of making macros like this $command MaryHadALittleLamb;$ now the K4 may have $command Mary$Had$A$Little$Lamb$;$. This won't work, so if your K4 macro includes embedded $, then replace them with chr(36) and your K4 macro becomes $command Marychr(36)Hadchr(36)Achr(36)Littlechr(36)Lambchr(36);$.
Also, in this version, if you are running JTDX with the JTDX control panel connected, you can click on FT4/8 DX Spots on different bands/modes and the JTDX control panel will QSY JTDX.
SeventyThree(s).


Re: SFI

John Owens
 

Just sene the SH/DX WWV Telnet command to your cluster and you will get the latest and a bunch of previous others. John Owens -  N7TK


Fw: [hamlogger] v4.0.278 auto-update is on-line ...

g4girhb0 <ian.frith@...>
 

Bob
 
The only thing not happening with the JTDX/DXSPOT mod, is the Logging window is not populated with the Call sign etc, after clicking on the DX SPOT.
 
73
 
Ian
G4GIR
 

----- Original Message -----
From: Ian <IAN.FRITH@...>
Sent: 14/10/2021 15:44:38
Subject: Re: [hamlogger] v4.0.278 auto-update is on-line ...

Cheers Bob,
Seems good.
 
73
 
    Ian G4GIR
 
----- Original Message -----
From: Bob <k4cy@...>
Sent: 14/10/2021 15:20:24
Subject: [hamlogger] v4.0.278 auto-update is on-line ...

This is primarily a maintenance release. Several small bugs are fixed.
Eelcraft K4 CAT support is added. It is essentially the same as the K3, but as users find differences between the two they will be added to the K4 support. The K4 CAT commands may use a embedded $ in the command. This interferes with the Logger32 practice of making macros like this $command MaryHadALittleLamb;$ now the K4 may have $command Mary$Had$A$Little$Lamb$;$. This won't work, so if your K4 macro includes embedded $, then replace them with chr(36) and your K4 macro becomes $command Marychr(36)Hadchr(36)Achr(36)Littlechr(36)Lambchr(36);$.
Also, in this version, if you are running JTDX with the JTDX control panel connected, you can click on FT4/8 DX Spots on different bands/modes and the JTDX control panel will QSY JTDX.
SeventyThree(s).


Re: SFI

Johan ZS1A
 

Dankie Oom Bob. 
Dit werk nou
Baie dankie ! Hou die Blou Bulle en die Springbokke dop die naweek ...met bier.
73ZS1A


Re: SFI

Bob
 

On 10/14/2021 12:33 PM Johan ZS1A <j-s@...> wrote:
 
 
SFI gets it the SFI info when starting Logger32 from the Telnet (VE7CC-1) However sometimes this data is old or wrong from the source.
If I right click on the WWV pane right hand side bottom (Get NOAA Update) then it says I don't have internet connection. I then (thought I am clever) changed the standard URRL in the NOAA popup window. Can I please get the correct URRL for this to work ?
73 ZS1A


SFI

Johan ZS1A
 

SFI gets it the SFI info when starting Logger32 from the Telnet (VE7CC-1) However sometimes this data is old or wrong from the source.
If I right click on the WWV pane right hand side bottom (Get NOAA Update) then it says I don't have internet connection. I then (thought I am clever) changed the standard URRL in the NOAA popup window. Can I please get the correct URRL for this to work ?
73 ZS1A


Re: v4.0.278 auto-update is on-line ...

g4girhb0 <ian.frith@...>
 

Cheers Bob,
Seems good.
 
73
 
    Ian G4GIR
 

----- Original Message -----
From: Bob <k4cy@...>
Sent: 14/10/2021 15:20:24
Subject: [hamlogger] v4.0.278 auto-update is on-line ...

This is primarily a maintenance release. Several small bugs are fixed.
Eelcraft K4 CAT support is added. It is essentially the same as the K3, but as users find differences between the two they will be added to the K4 support. The K4 CAT commands may use a embedded $ in the command. This interferes with the Logger32 practice of making macros like this $command MaryHadALittleLamb;$ now the K4 may have $command Mary$Had$A$Little$Lamb$;$. This won't work, so if your K4 macro includes embedded $, then replace them with chr(36) and your K4 macro becomes $command Marychr(36)Hadchr(36)Achr(36)Littlechr(36)Lambchr(36);$.
Also, in this version, if you are running JTDX with the JTDX control panel connected, you can click on FT4/8 DX Spots on different bands/modes and the JTDX control panel will QSY JTDX.
SeventyThree(s).


v4.0.278 auto-update is on-line ...

Bob
 

This is primarily a maintenance release. Several small bugs are fixed.
 
Eelcraft K4 CAT support is added. It is essentially the same as the K3, but as users find differences between the two they will be added to the K4 support. The K4 CAT commands may use a embedded $ in the command. This interferes with the Logger32 practice of making macros like this $command MaryHadALittleLamb;$ now the K4 may have $command Mary$Had$A$Little$Lamb$;$. This won't work, so if your K4 macro includes embedded $, then replace them with chr(36) and your K4 macro becomes $command Marychr(36)Hadchr(36)Achr(36)Littlechr(36)Lambchr(36);$.
 
Also, in this version, if you are running JTDX with the JTDX control panel connected, you can click on FT4/8 DX Spots on different bands/modes and the JTDX control panel will QSY JTDX.
 
SeventyThree(s).


Re: PowerSDR (as the Radio)

Alec SP2EWQ <aleksander.otulak@...>
 




Bob,

OK - thanks for such a picturesque oxymoronic suggestion.
Appreciated.

Best regards,
Alec




------ Wiadomość oryginalna ------
Od: "Bob" <k4cy@...>
Data: 14.10.2021 15:41:27
Temat: Re: [hamlogger] PowerSDR (as the Radio)

Alec, check out section 35.5 (Page 623) of the help file. With the options avaliable, you should be able to make PowerSDR stand to attention and play Mazurek Dabrowskiego. 73.
On 10/14/2021 9:30 AM Alec SP2EWQ <aleksander.otulak@...> wrote:
 
 
 
 
Bob (et al),
 
sure - let's forget and leave the mode matter behind - my mistake...
Sorry...
 
However, another matter is going SPLIT with PowerSDR.
 
If a spot contains SPLIT information, then for
DIGI modes:          L32 should turn the XIT ON and set the offset frequency in there
Any other:             L32 should turn the VFOB ON and set its freq according to the spot info.
 
To me, L32 does neither...
 
Best regards,
Alec
 
 
 
 
 
------ Wiadomość oryginalna ------
Od: "Bob" < k4cy@...>
Data: 14.10.2021 14:57:36
Temat: Re: [hamlogger] PowerSDR (as the Radio)
 
Alec, is this PowerSDR specific, or does it apply to any/all radios? You might want to take a peek at section 2.6.4 (page 39) of the help file. 73.
On 10/14/2021 5:42 AM Alec SP2EWQ < aleksander.otulak@...> wrote:
 
 
 
 
 
 
Hi,
 
if clicked on any DIGI (FT8, FT4, PSK, RTTY, etc.) spot,
the PowerSDR should go to DIGU.
 
If clicked on CW spot,
PowerSDR should preferably go to CWU.
 
In both cases , 
PowerSDR goes to USB, which is wrong and confusing.
 
Any help.
please?
 
Best regards,
Alec
 
 
 
 

 

 


Fw: Refinement Request.

g4girhb0 <ian.frith@...>
 

Ok,
 
Just realised clear all entries already there.
 
 
 

----- Original Message -----
From: Ian <IAN.FRITH@...>
Sent: 14/10/2021 14:42:01
Subject: Refinement Request.

Bob
 
Is it possible to add a few refinements to the DX SPOTS window?
 
1. Have the columns able to be sorted by clicking the column headers.
2. Have the DX SPOTS retained in the window after shutting down so when re-starting the spots still show.
3. Add a date column.
4. Add a function to the RIGHT CLICK  menu to delete all spots in the DX SPOTS window.
 
Thanks
 
73
 
Ian G4GIR
 


Refinement Request.

g4girhb0 <ian.frith@...>
 

Bob
 
Is it possible to add a few refinements to the DX SPOTS window?
 
1. Have the columns able to be sorted by clicking the column headers.
2. Have the DX SPOTS retained in the window after shutting down so when re-starting the spots still show.
3. Add a date column.
4. Add a function to the RIGHT CLICK  menu to delete all spots in the DX SPOTS window.
 
Thanks
 
73
 
Ian G4GIR
 


Re: PowerSDR (as the Radio)

Bob
 

Alec, check out section 35.5 (Page 623) of the help file. With the options avaliable, you should be able to make PowerSDR stand to attention and play Mazurek Dabrowskiego. 73.

On 10/14/2021 9:30 AM Alec SP2EWQ <aleksander.otulak@...> wrote:
 
 
 
 
Bob (et al),
 
sure - let's forget and leave the mode matter behind - my mistake...
Sorry...
 
However, another matter is going SPLIT with PowerSDR.
 
If a spot contains SPLIT information, then for
DIGI modes:          L32 should turn the XIT ON and set the offset frequency in there
Any other:             L32 should turn the VFOB ON and set its freq according to the spot info.
 
To me, L32 does neither...
 
Best regards,
Alec
 
 
 
 
 
------ Wiadomość oryginalna ------
Od: "Bob" < k4cy@...>
Data: 14.10.2021 14:57:36
Temat: Re: [hamlogger] PowerSDR (as the Radio)
 
Alec, is this PowerSDR specific, or does it apply to any/all radios? You might want to take a peek at section 2.6.4 (page 39) of the help file. 73.
On 10/14/2021 5:42 AM Alec SP2EWQ < aleksander.otulak@...> wrote:
 
 
 
 
 
 
Hi,
 
if clicked on any DIGI (FT8, FT4, PSK, RTTY, etc.) spot,
the PowerSDR should go to DIGU.
 
If clicked on CW spot,
PowerSDR should preferably go to CWU.
 
In both cases , 
PowerSDR goes to USB, which is wrong and confusing.
 
Any help.
please?
 
Best regards,
Alec
 
 
 
 

 

 


Re: PowerSDR (as the Radio)

Alec SP2EWQ <aleksander.otulak@...>
 



Bob (et al),

sure - let's forget and leave the mode matter behind - my mistake...
Sorry...

However, another matter is going SPLIT with PowerSDR.

If a spot contains SPLIT information, then for
DIGI modes:          L32 should turn the XIT ON and set the offset frequency in there
Any other:             L32 should turn the VFOB ON and set its freq according to the spot info.

To me, L32 does neither...

Best regards,
Alec





------ Wiadomość oryginalna ------
Od: "Bob" <k4cy@...>
Data: 14.10.2021 14:57:36
Temat: Re: [hamlogger] PowerSDR (as the Radio)

Alec, is this PowerSDR specific, or does it apply to any/all radios? You might want to take a peek at section 2.6.4 (page 39) of the help file. 73.
On 10/14/2021 5:42 AM Alec SP2EWQ <aleksander.otulak@...> wrote:
 
 
 
 
 
 
Hi,
 
if clicked on any DIGI (FT8, FT4, PSK, RTTY, etc.) spot,
the PowerSDR should go to DIGU.
 
If clicked on CW spot,
PowerSDR should preferably go to CWU.
 
In both cases , 
PowerSDR goes to USB, which is wrong and confusing.
 
Any help.
please?
 
Best regards,
Alec
 
 
 
 

2321 - 2340 of 88395