Date   

locked Re: [Ham-Apps] log time

signal <signalhz@...>
 

Here's the screen capture of the qso. It couldn't have logged it right.


On 2/18/2012 11:12 PM, Laurie, VK3AMA wrote:
 

Eddy,

I checked your JT-Alert Session file and the QSO logged correctly. The HRD "Time On" field is the time of the QSO start which is retrieved from the "Start Time" of the JT65-HF log for that QSO. JT-Alert correctly logged the data as retrieved from JT65-HF

From the Session file, the
N0LWF qso data as prepared for sending to the HRD Log, ....

46493.    02:17:51:845 : Set Log Data : CALL : N0LWF
46494.    02:17:51:847 : Set Log Data : BAND : 40
46495.    02:17:51:850 : Set Log Data : BAND_RX : 40
46496.    02:17:51:852 : Set Log Data : QSO_DATE : 20120219
46497.    02:17:51:855 : Set Log Data : TIME_ON : 015900
46498.    02:17:51:857 : Set Log Data : TIME_OFF : 021700

And the previous ZR1ADI QSO as logged to HRD
46316.    02:08:56:132 : Set Log Data : CALL : ZR1ADI
46317.    02:08:56:135 : Set Log Data : BAND : 40
46318.    02:08:56:137 : Set Log Data : BAND_RX : 40
46319.    02:08:56:140 : Set Log Data : QSO_DATE : 20120219
46320.    02:08:56:142 : Set Log Data : TIME_ON : 015900
46321.    02:08:56:145 : Set Log Data : TIME_OFF : 020800

This raises the question why did JT65-HF have the 0159 Start Time for the N0LWF QSO when 0159 was the Start Time for your previous QSO with ZR1ADI which had a Stop Time of 0208. Your N0LWF Start Time should have been after 0208.

From your session file, I can see the callsign N0LWF was entered into JT65-HF at 0210 which caused JT-Alert to do a lookup of the new callsign
46402.    02:10:58:021 : Last QSO : Logger : HRD V5 (ODBC) : [MSAccess] : HRD My Logbook - Access
46403.    02:10:58:024 : Last QSO : Query : SELECT * FROM [TABLE_HRD_CONTACTS_V01] WHERE....
46404.    02:10:58:027 : Last QSO : Records : found
46405.    02:10:58:030 : Last QSO :  Callsign : N0LWF
It would appear that you double-clicked an old (0209 with white font) JT65-HF message to populate the "TX to Call Sign" field which should have set the JT65-HF Start Time to 0210 (the actual time of the double-click). I note the message clicked didn't have your callsign, so perhaps, JT65-HF doesn't set the Start time in those cases and incorrectly uses the start time of the last QSO
(this is speculation, I haven't tested).

If it was me making this QSO, where the callsign was in the TX field before the QSO had actually been started, I would have double-clicked the first message I received back from the station, in your case the message at 0213 (
02:13  4 -12 -0.3  -939  B N4ABN N0LWF -09), since you didn't start the QSO by double clicking a CQ.

In Summary - If you have had a callsign in JT65-HF waiting for a future chance to work that station, you should be double-clicking the first message you get from that station to set the start time, otherwise the start time gets set to when the callsign was first entered into JT65-HF.

Maybe some more experienced JT65-HF users can shed some light on this behaviour with the early start time.

de Laurie, VK3AMA

On 19-February-2012 13:45, signal wrote:
01:59 N0LWF supposed to log time as 02:12 I have a screen shot of the JT65-HF window and the HRD log window. They are both included here. The time wasn't off much. It's the first two at the top of the log as you can see. The time on was the same for both but that couldn't happen in reality.





On 2/13/2012 1:18 AM, Laurie, VK3AMA wrote:
 

Eddy,

There have been no other reports of this behaviour.

Next time this happens, use the "Contact Support" menu in JT-Alert. Please include a note of the affected callsign(s) and the date/time of the logged QSO and the date/time reported by HRDLog. I will review your session files to see if JT-Alert is logging the incorrect data.

de Laurie, VK3AMA

On 13-February-2012 00:53, signal wrote:

Hi Laurie,

I don't know if it''s JT-Alert or JT65-HF or HRD Logbook logging wrong time. It has happened twice this morning. It logs the correct day and reports and call signs. The time logged was off a couple of hours. Has any one else seen this happen?

Eddy
N4ABN

-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/

-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked New JT-Alert Sound & Voice Files V1.0.3 available for download

Laurie, VK3AMA <groups03@...>
 

JT-Alert Sound & Voice Files V1.0.3 is available for download from...
 http://ham-apps.com/dnl/JT-Alert/JT-Alert_Sounds_1.0.3_Setup.exe

This release includes an additional wave file for the new JT-Alert WAZ alert (available in the next release).

All the voice files have been regenerated using newer voice synthesis software to overcome some of the pronunciation oddities of the old files. All the voice files have been normalised in volume so that regarless of the alert, the files all play at the same volume.


de Laurie, VK3AMA


locked Re: [Ham-Apps] log time

Laurie, VK3AMA <groups03@...>
 

Eddy,

I checked your JT-Alert Session file and the QSO logged correctly. The HRD "Time On" field is the time of the QSO start which is retrieved from the "Start Time" of the JT65-HF log for that QSO. JT-Alert correctly logged the data as retrieved from JT65-HF

From the Session file, the
N0LWF qso data as prepared for sending to the HRD Log, ....
46493.    02:17:51:845 : Set Log Data : CALL : N0LWF
46494.    02:17:51:847 : Set Log Data : BAND : 40
46495.    02:17:51:850 : Set Log Data : BAND_RX : 40
46496.    02:17:51:852 : Set Log Data : QSO_DATE : 20120219
46497.    02:17:51:855 : Set Log Data : TIME_ON : 015900
46498.    02:17:51:857 : Set Log Data : TIME_OFF : 021700

And the previous ZR1ADI QSO as logged to HRD
46316.    02:08:56:132 : Set Log Data : CALL : ZR1ADI
46317.    02:08:56:135 : Set Log Data : BAND : 40
46318.    02:08:56:137 : Set Log Data : BAND_RX : 40
46319.    02:08:56:140 : Set Log Data : QSO_DATE : 20120219
46320.    02:08:56:142 : Set Log Data : TIME_ON : 015900
46321.    02:08:56:145 : Set Log Data : TIME_OFF : 020800

This raises the question why did JT65-HF have the 0159 Start Time for the N0LWF QSO when 0159 was the Start Time for your previous QSO with ZR1ADI which had a Stop Time of 0208. Your N0LWF Start Time should have been after 0208.

From your session file, I can see the callsign N0LWF was entered into JT65-HF at 0210 which caused JT-Alert to do a lookup of the new callsign
46402.    02:10:58:021 : Last QSO : Logger : HRD V5 (ODBC) : [MSAccess] : HRD My Logbook - Access
46403.    02:10:58:024 : Last QSO : Query : SELECT * FROM [TABLE_HRD_CONTACTS_V01] WHERE....
46404.    02:10:58:027 : Last QSO : Records : found
46405.    02:10:58:030 : Last QSO :  Callsign : N0LWF
It would appear that you double-clicked an old (0209 with white font) JT65-HF message to populate the "TX to Call Sign" field which should have set the JT65-HF Start Time to 0210 (the actual time of the double-click). I note the message clicked didn't have your callsign, so perhaps, JT65-HF doesn't set the Start time in those cases and incorrectly uses the start time of the last QSO
(this is speculation, I haven't tested).

If it was me making this QSO, where the callsign was in the TX field before the QSO had actually been started, I would have double-clicked the first message I received back from the station, in your case the message at 0213 (
02:13  4 -12 -0.3  -939  B N4ABN N0LWF -09), since you didn't start the QSO by double clicking a CQ.

In Summary - If you have had a callsign in JT65-HF waiting for a future chance to work that station, you should be double-clicking the first message you get from that station to set the start time, otherwise the start time gets set to when the callsign was first entered into JT65-HF.

Maybe some more experienced JT65-HF users can shed some light on this behaviour with the early start time.

de Laurie, VK3AMA

On 19-February-2012 13:45, signal wrote:
01:59 N0LWF supposed to log time as 02:12 I have a screen shot of the JT65-HF window and the HRD log window. They are both included here. The time wasn't off much. It's the first two at the top of the log as you can see. The time on was the same for both but that couldn't happen in reality.





On 2/13/2012 1:18 AM, Laurie, VK3AMA wrote:
 

Eddy,

There have been no other reports of this behaviour.

Next time this happens, use the "Contact Support" menu in JT-Alert. Please include a note of the affected callsign(s) and the date/time of the logged QSO and the date/time reported by HRDLog. I will review your session files to see if JT-Alert is logging the incorrect data.

de Laurie, VK3AMA

On 13-February-2012 00:53, signal wrote:

Hi Laurie,

I don't know if it''s JT-Alert or JT65-HF or HRD Logbook logging wrong time. It has happened twice this morning. It logs the correct day and reports and call signs. The time logged was off a couple of hours. Has any one else seen this happen?

Eddy
N4ABN

-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: [Ham-Apps] log time

signal <signalhz@...>
 

01:59 N0LWF supposed to log time as 02:12 I have a screen shot of the JT65-HF window and the HRD log window. They are both included here. The time wasn't off much. It's the first two at the top of the log as you can see. The time on was the same for both but that couldn't happen in reality.





On 2/13/2012 1:18 AM, Laurie, VK3AMA wrote:
 

Eddy,

There have been no other reports of this behaviour.

Next time this happens, use the "Contact Support" menu in JT-Alert. Please include a note of the affected callsign(s) and the date/time of the logged QSO and the date/time reported by HRDLog. I will review your session files to see if JT-Alert is logging the incorrect data.

de Laurie, VK3AMA

On 13-February-2012 00:53, signal wrote:

Hi Laurie,

I don't know if it''s JT-Alert or JT65-HF or HRD Logbook logging wrong time. It has happened twice this morning. It logs the correct day and reports and call signs. The time logged was off a couple of hours. Has any one else seen this happen?

Eddy
N4ABN

-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked JT-Alert Callsign Databases - New version, 12.02.15 (2012-February-15), available

Laurie, VK3AMA <groups03@...>
 

Latest Callsign Databases (12.01.29) file available for download from
http://ham-apps.com/dnl/JT-Alert/JT-Alert_Databases_12.02.15_Setup.exe


Simply run the executable to install or update existing files.

The version number reflects the creation and release date.
12 = year, 02 = month, 15 = day. So this file created and released 2012-February-15

de Laurie, VK3AMA


locked Re: [Ham-Apps] log time

signal <signalhz@...>
 

Hi Laurie, ok will do.

73
Eddy N4ABN

On 2/13/2012 1:18 AM, Laurie, VK3AMA wrote:
 

Eddy,

There have been no other reports of this behaviour.

Next time this happens, use the "Contact Support" menu in JT-Alert. Please include a note of the affected callsign(s) and the date/time of the logged QSO and the date/time reported by HRDLog. I will review your session files to see if JT-Alert is logging the incorrect data.

de Laurie, VK3AMA

On 13-February-2012 00:53, signal wrote:

Hi Laurie,

I don't know if it''s JT-Alert or JT65-HF or HRD Logbook logging wrong time. It has happened twice this morning. It logs the correct day and reports and call signs. The time logged was off a couple of hours. Has any one else seen this happen?

Eddy
N4ABN

-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: [Ham-Apps] log time

Laurie, VK3AMA <groups03@...>
 

Eddy,

There have been no other reports of this behaviour.

Next time this happens, use the "Contact Support" menu in JT-Alert. Please include a note of the affected callsign(s) and the date/time of the logged QSO and the date/time reported by HRDLog. I will review your session files to see if JT-Alert is logging the incorrect data.

de Laurie, VK3AMA

On 13-February-2012 00:53, signal wrote:
Hi Laurie,

I don't know if it''s JT-Alert or JT65-HF or HRD Logbook logging wrong time. It has happened twice this morning. It logs the correct day and reports and call signs. The time logged was off a couple of hours. Has any one else seen this happen?

Eddy
N4ABN


locked Re: [Ham-Apps] log time

signal <signalhz@...>
 

I'm using the new HRD version too

On 2/12/2012 10:36 AM, Jim - N4ST wrote:
 

Most likely unrelated to your issue, but there is a new HRD Version 5.1 available from the new owners.

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of signal
Sent: Sunday, February 12, 2012 10:12
To: Ham-Apps@...
Subject: Re: [Ham-Apps] log time

 

 

Hi Jim, it's set to UTC time.  It only happens once in a while. Actually it's only happened twice.

Eddy N4ABN

On 2/12/2012 9:15 AM, Jim - N4ST wrote:

 

Is your time error off by the difference between local and UTC time?

If so, check your HRD Logbook Configure/Appearance/Logbook display and see if you have selected UTC or Local time for the display.


-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: [Ham-Apps] log time

Jim - N4ST
 

Most likely unrelated to your issue, but there is a new HRD Version 5.1 available from the new owners.

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of signal
Sent: Sunday, February 12, 2012 10:12
To: Ham-Apps@...
Subject: Re: [Ham-Apps] log time

 

 

Hi Jim, it's set to UTC time.  It only happens once in a while. Actually it's only happened twice.

Eddy N4ABN

On 2/12/2012 9:15 AM, Jim - N4ST wrote:

 

Is your time error off by the difference between local and UTC time?

If so, check your HRD Logbook Configure/Appearance/Logbook display and see if you have selected UTC or Local time for the display.


locked Re: [Ham-Apps] log time

signal <signalhz@...>
 

No I didn't verify it before I clicked on ok or whatever it said. I will from now on and try to get screen shots and other info to help pin it down to what's happening.

Haven't done that scenario you're talking about.

73 Eddy N4ABN

On 2/12/2012 9:26 AM, David Westbrook wrote:
�

Did you verify the time in the "Log QSO" window in JT65-HF?


I�occasionally see the wrong start time��pre-populated in there .. �I think (working from memory here) that this scenario reproduces it:
� at 14:00, dbl-click on a "CQ" message to work someone
� take a break, leaving the prrogram on
� come back at 16:00 (e.g. when JT-Alert sounds a wanted state)..
� See the wanted call in a QSO, and dbl-click it.. ==> but dbl-click a cq-answer, report, or 73 msg .. NOT a CQ.
� � �and then change DF, and wait for him to finish QSO.
� � �then call him and work him.

In that case i think i see the old start_time ... �so I always glance at the start/end times in the "Log QSO" window.

--david
KJ4IZW

On Sun, Feb 12, 2012 at 8:53 AM, signal <signalhz@...> wrote:
�

Hi Laurie,

I don't know if it''s JT-Alert or JT65-HF or HRD Logbook logging wrong time. It has happened twice this morning. It logs the correct day and reports and call signs. The time logged was off a couple of hours. Has any one else seen this happen?

Eddy
N4ABN

-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: [Ham-Apps] log time

signal <signalhz@...>
 

Hi Jim, it's set to UTC time.  It only happens once in a while. Actually it's only happened twice.

Eddy N4ABN

On 2/12/2012 9:15 AM, Jim - N4ST wrote:
 

Is your time error off by the difference between local and UTC time?

If so, check your HRD Logbook Configure/Appearance/Logbook display and see if you have selected UTC or Local time for the display.

 

_________

Jim – N4ST

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of signal
Sent: Sunday, February 12, 2012 08:53
To: Ham-Apps@...
Subject: [Ham-Apps] log time

 

 

Hi Laurie,

I don't know if it''s JT-Alert or JT65-HF or HRD Logbook logging wrong time. It has happened twice this morning. It logs the correct day and reports and call signs. The time logged was off a couple of hours. Has any one else seen this happen?

Eddy


-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: [Ham-Apps] log time

David Westbrook
 

Did you verify the time in the "Log QSO" window in JT65-HF?

I occasionally see the wrong start time  pre-populated in there ..  I think (working from memory here) that this scenario reproduces it:
  at 14:00, dbl-click on a "CQ" message to work someone
  take a break, leaving the prrogram on
  come back at 16:00 (e.g. when JT-Alert sounds a wanted state)..
  See the wanted call in a QSO, and dbl-click it.. ==> but dbl-click a cq-answer, report, or 73 msg .. NOT a CQ.
     and then change DF, and wait for him to finish QSO.
     then call him and work him.

In that case i think i see the old start_time ...  so I always glance at the start/end times in the "Log QSO" window.

--david
KJ4IZW

On Sun, Feb 12, 2012 at 8:53 AM, signal <signalhz@...> wrote:
 

Hi Laurie,

I don't know if it''s JT-Alert or JT65-HF or HRD Logbook logging wrong time. It has happened twice this morning. It logs the correct day and reports and call signs. The time logged was off a couple of hours. Has any one else seen this happen?

Eddy
N4ABN

--
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/



locked Re: [Ham-Apps] log time

Jim - N4ST
 

Is your time error off by the difference between local and UTC time?

If so, check your HRD Logbook Configure/Appearance/Logbook display and see if you have selected UTC or Local time for the display.

 

_________

Jim – N4ST

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of signal
Sent: Sunday, February 12, 2012 08:53
To: Ham-Apps@...
Subject: [Ham-Apps] log time

 

 

Hi Laurie,

I don't know if it''s JT-Alert or JT65-HF or HRD Logbook logging wrong time. It has happened twice this morning. It logs the correct day and reports and call signs. The time logged was off a couple of hours. Has any one else seen this happen?

Eddy


locked log time

signal <signalhz@...>
 

Hi Laurie,

I don't know if it''s JT-Alert or JT65-HF or HRD Logbook logging wrong time. It has happened twice this morning. It logs the correct day and reports and call signs. The time logged was off a couple of hours. Has any one else seen this happen?

Eddy
N4ABN
-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: "Save config button" Feature Request

Costas J. Dovas - SV4FFL
 

Hello Laurie
I am totally ok with all of your informations!!
73 es tnx agn.
BTW Hope cu soon on the air!!
73
Costas SV4FFL


locked Re: [Ham-Apps] "Save config button" Feature Request

Laurie, VK3AMA <groups03@...>
 

Hi Costas,

The only important file to save is the config.ini file. The .001, .002, etc, files are just previous versions of the config.ini file. Everytime JT-Alert is closed, the current config.ini is saved to config.001 and the current in memory configuration is saved to config.ini ready for the next start of JT-Alert. This is part of a config backup and restore function that I initially developed, but never enabled. I will have another look at the code and may have it enabled for the next release.

Currently, JT-Macros settings are saved in the Windows registry. I have plans to move those settings to a file based system similar to JT-Alert, but it is not high on my priority list.

Regards
Laurie, VK3AMA

On 08-February-2012 20:41, Κωστας wrote:
Hello Laurie
First i would like to thank you for the great plugins you give as.
It was my dream to check out my new ones and stop making double qsos all the time!!
One question and propose. If i want to make a complete setting backup, the config.ini is enough on "C:\Documents and Settings\User\Local Settings\Application Data\Ham-Apps\JT-Alert\SV4FFL\configs" folder? What about the other files? (config.001,config.002, etc)
Do you beleive that will be a good feature for someone to just click "save config" button? Also the same feature on JT Macros will be fine!!
73 and keep up the great job!!

Costas J. Dovas
SV4FFL
Loc: KM19li
e-mail: sv4ffl@...
web: http://www.qsl.net/sv4ffl


locked "Save config button" Feature Request

Costas J. Dovas - SV4FFL
 

Hello Laurie
First i would like to thank you for the great plugins you give as.
It was my dream to check out my new ones and stop making double qsos all the time!!
One question and propose. If i want to make a complete setting backup, the config.ini is enough on "C:&#92;Documents and Settings&#92;User&#92;Local Settings&#92;Application Data&#92;Ham-Apps&#92;JT-Alert&#92;SV4FFL&#92;configs" folder? What about the other files? (config.001,config.002, etc)
Do you beleive that will be a good feature for someone to just click "save config" button? Also the same feature on JT Macros will be fine!!
73 and keep up the great job!!

Costas J. Dovas
SV4FFL
Loc: KM19li
e-mail: sv4ffl@raag.org
web: http://www.qsl.net/sv4ffl


locked Re: [Ham-Apps] Feature Request

pontotochs <pontotochs@...>
 

That is great Laurie. Nice to find out about the "hidden" features.
  73,
    Rick, N5RB


From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Laurie, VK3AMA
Sent: Tuesday, February 07, 2012 6:56 PM
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Feature Request

 

Hi Bruce,

This functionality already exists within JT-Alert, but I have not advertised the feature because I haven't written the documentation yet ;)

Follow the following steps...

  • Create a new shortcut to the JT-Alert executable giving it a suitable name.
  • Open the properties window of that shortcut.
  • Add to the end of the Target field, /callsign=NEWCALL where NEWCALL is the desired callsign of the guest op.
  • Close the properties window.
  • Start JT-Alert using this new shortcut. You will see the new callsign in the titlebar.
  • Open the JT-Alert configuration and set the necessary settings.
  • Finished.


There is no limit to the number of shortcuts you can have, except for Windows limits (is there one?) and disk space. Each callsigns will have an independent config file and session files stored on the harddrive.

Let me know how this works for you.

de Laurie, VK3AMA


On 08-February-2012 00:48, Bruce McLain wrote:
I would like to be able to easily swap the JT-Alert and JT65-HF
configurations between operators.  I have some guest operators that
visit my qth and it would very nice to have a configuration defined
with their callsign and log file location so all they would have to do
was select the operator.

Bruce McLain - K5WBM


locked Re: [Ham-Apps] JT Alert log into logbook?

signal <signalhz@...>
 

Ok got it Laurie. Thanks

73
Eddy N4ABN

On 2/7/2012 8:00 PM, Laurie, VK3AMA wrote:
 

Eddy,

Assuming you have JT-Alert successfully logging to HRD (you should get a success popup message after completing the log action in JT65-HF), then all that is required is to click the refresh button in HRDLog for the new QSO to be visible (assuming you don't have some sort of filter applied to HRDLog that my not show the QSO).

de Laurie, VK3AMA


On 07-February-2012 23:29, signal wrote:

How does one configure JT Alert to load the station worked into HRD? I saw the page talking about refresh after. What other setting do I have to enable to get it to load the station into the qso window or log?

73
Eddy
N4ABN
-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/

-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: [Ham-Apps] JT Alert log into logbook?

Laurie, VK3AMA <groups03@...>
 

Eddy,

Assuming you have JT-Alert successfully logging to HRD (you should get a success popup message after completing the log action in JT65-HF), then all that is required is to click the refresh button in HRDLog for the new QSO to be visible (assuming you don't have some sort of filter applied to HRDLog that my not show the QSO).

de Laurie, VK3AMA


On 07-February-2012 23:29, signal wrote:
How does one configure JT Alert to load the station worked into HRD? I saw the page talking about refresh after. What other setting do I have to enable to get it to load the station into the qso window or log?

73
Eddy
N4ABN
-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/