¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

N7XG Logger version 5.02.02 Release

 

I am trying to wrap up the next release 5.02.02 of the logger and need a couple of more beta testers tht are available to help. If interested please respond offline.

Summary of changes to this release:

Corrected a minor issue when the contacts grid was double clicked and there were no records being displayed incorrectly opening the edit screen in new record mode.

Updated email to support SSL/TLS

Moved email settings to System Options screen (Email Options)

Added fields to the System options screen (QSL 2nd Request) for the headers, body, and signature fields.

Minor changes to the Email QSL Request screen to add a Subject line field.

In this version if the logger determines that the outgoing email settings are not set you will not be able to attempt to use the email functions (disabled)

During logger startup the logger will attempt to write a file into the logger to determine if the files permissions are set correctly. If the user does not have write access then the logger will shutdown.

Redesigned the ADIF Export screen. Options are now selected from a dropdown list, better use of filters during export, and also added the ability to add /M or /P for mobile or portable stations.

Added new menu item under the Action menu to allow you to change several of the settings while monitoring a net.

Bakers Dozen award selector. This new feature will make it much easier to select and print out the Bakers Dozen Award.

New field in System Options ¨C MyCallArea

Updating the current bureau managers in the System Options table ¨C Currently KB8UEY and W2UJ

Update System Options table with correct Area Awards manager as it is defined in officers table.

Corrected the way the address field in the officers table was being stored




Re: Locking Up

 

¿ªÔÆÌåÓý

Dean,

?

Morning, I reloaded the program, left the computer off for 4 days and low and behold last night it launched. I put the new backup file from my other computer in and it seems to be working just fine.

Hope all is well.

Hi to Jan

Dwight - WF4H

?

From: N7XGlogsupport@... [mailto:N7XGlogsupport@...]
Sent: Tuesday, March 01, 2016 1:05 PM
To: N7XGlogsupport@...
Subject: re: [N7XGlogsupport] Locking Up

?

?

Dwight,

This is a file permission problem on your Win machine. Try running ad
administrator. If this does not work give me a call.



Dean Davis, N7XG

-------- Original Message --------
> From: "parrotham' parrotham@... [N7XGlogsupport]"

> Sent: Monday, February 29, 2016 6:38 PM
> To: N7XGlogsupport@...
> Subject: [N7XGlogsupport] Locking Up
>
> Dean,
>
> Any input on the emails from yesterday.
>
> When I try to launch the program with windows 10 it won't be past the
logo
> page and says the program has stopped working.
>
> If you can give me some info maybe I can fix it or I will have to reload
the
> program from scratch. This is locking up on my Logger Laptop I use when
NCS.
>
> Appreciate any help you can give me
>
> Thank You
>
>
>
> 73's
>
> Dwight WF4H 3905CCN 40M Early Net Coordinator


Re: ADIF Export

 

Sure thing, Dean. ?Thanks.

RJ, NA0L


--In N7XGlogsupport@..., <dean@...> wrote :

RJ, Rick,

OK, dug deeper and found the problem. I will get it corrected in 5.02.02.

RJ, when I get the beta ready could you do some testing for me?


Dean Davis, N7XG?


Re: ADIF Export

 

RJ, Rick,

OK, dug deeper and found the problem. I will get it corrected in 5.02.02.

RJ, when I get the beta ready could you do some testing for me?


Dean Davis, N7XG

-------- Original Message --------
From: "rjlorenzen@... [N7XGlogsupport]"
<N7XGlogsupport@...>
Sent: Thursday, March 03, 2016 2:29 AM
To: N7XGlogsupport@...
Subject: re: [N7XGlogsupport] Re: ADIF Export

Rick,

Are you sure you got only 7000 and not the full 17000, or some other
number? We may not be talking about the same thing. I am not saying that
ADIF export fails, but that, for example, if I filter a 3600 record
database by selecting a single callsign, for 6 records, I get a large
number of records in the export, not just the six I expected.. This happens
for 5.01.11, 5.01.15, and 5.02.01. I don't have 14c to test. I was happy to
exhibit the problem on a small database because it takes over an hour to
export "six" ADIF records from a 13,000 record database.

As I said, this may be a problem only with me; no-one else seems to be
experiencing it. I don't use the ADIF export anyway; I use CSV export to
Excel. to ADIF so that I can select all the data and just the days or other
time periods that I want and then fix date, time, band, and mode problems.
I was just trying to help others who may have the same problem in the
future.

I get the feeling that I'm not making myself clear with this and am
certainly obsessing about it, so I'll probably just check out of the
discussion unless and until someone else sees the same problem.

dih-dih-dih-dah-dih-dah,
RJ, NA0L

---In N7XGlogsupport@..., <wb5fdp@...> wrote :

My initial testing shows it doesn't work with 14c, but works with 5.02.01
where I exported around 7000 filtered records from my log of 17000
entries.





---In N7XGlogsupport@..., <wb5fdp@...> wrote :

My initial testing shows it doesn't work with 14c, but works with 5.02.01
where I exported around 7000 filtered records from my log of 17000
entries.


Re: ADIF Export

 

Rick,

Are you sure you got only 7000 and not the full 17000, or some other number?? We may not be talking about the same thing.? I am not saying that ADIF export fails, but that, for example, if I filter a 3600 record database by selecting a single callsign, for 6 records, I get a large number of records in the export, not just the six I expected.. This happens for 5.01.11, 5.01.15, and 5.02.01.? I don't have 14c to test.? I was happy to exhibit the problem on a small database because it takes over an hour to export "six" ADIF records from a 13,000 record database.

As I said, this may be a problem only with me; no-one else seems to be experiencing it.? I don't use the ADIF export anyway; I use CSV export to Excel. to ADIF so that I can select all the data and just the days or other time periods that I want and then fix date, time, band, and mode problems.? I was just trying to help others who may have the same problem in the future.

I get the feeling that I'm not making myself clear with this and am certainly obsessing about it, so I'll probably just check out of the discussion unless and until someone else sees the same problem.

dih-dih-dih-dah-dih-dah,
RJ, NA0L

---In N7XGlogsupport@..., <wb5fdp@...> wrote :

My initial testing shows it doesn't work with 14c, but works with 5.02.01 where I exported around 7000 filtered records from my log of 17000 entries.



---In N7XGlogsupport@..., <wb5fdp@...> wrote :

My initial testing shows it doesn't work with 14c, but works with 5.02.01 where I exported around 7000 filtered records from my log of 17000 entries.


Re: ADIF Export

 

My initial testing shows it doesn't work with 14c, but works with 5.02.01 where I exported around 7000 filtered records from my log of 17000 entries.


Re: ADIF Export

 

Thanks, Dean. ?I discovered some more info. ?I thought it might be a size related problem as I have 13,000 records in my database. ?I restored some old backups and found that for 2200 and fewer records an adif after filter works fine. ?For 2370 and more records, I would get the whole database exported even if only a few records were filtered. ?Hope this helps.

RJ, NA0L



---In N7XGlogsupport@..., <dean@...> wrote :

RJ,

OK I will look at it again and get it fixed in 5.02.02



Dean Davis, N7XG

-------- Original Message --------
> From: "rjlorenzen@... [N7XGlogsupport]"
<N7XGlogsupport@...>
> Sent: Tuesday, March 01, 2016 12:57 PM
> To: N7XGlogsupport@...
> Subject: re: [N7XGlogsupport] Re: ADIF Export
>
> OK, I guess it's just me. It has conistently failed to work across three
versions and four machines. As I said, csv export works fine with a filter.
I will try to create a simple db that exhibits the problem.
>
>
> RJ, NA0L
>
>
> ---In N7XGlogsupport@..., <dean@...> wrote :
>
> RJ,
>
> In any version of the logger you can filter data and export.


Re: ADIF Export

 

RJ,

OK I will look at it again and get it fixed in 5.02.02



Dean Davis, N7XG

-------- Original Message --------
From: "rjlorenzen@... [N7XGlogsupport]"
<N7XGlogsupport@...>
Sent: Tuesday, March 01, 2016 12:57 PM
To: N7XGlogsupport@...
Subject: re: [N7XGlogsupport] Re: ADIF Export

OK, I guess it's just me. It has conistently failed to work across three
versions and four machines. As I said, csv export works fine with a filter.
I will try to create a simple db that exhibits the problem.


RJ, NA0L


---In N7XGlogsupport@..., <dean@...> wrote :

RJ,

In any version of the logger you can filter data and export.


Re: ADIF Export

 

OK, I guess it's just me. ?It has conistently failed to work across three versions and four machines. ?As I said, csv export works fine with a filter. ?I will try to create a simple db that exhibits the problem.

RJ, NA0L

---In N7XGlogsupport@..., <dean@...> wrote :

RJ,

In any version of the logger you can filter data and export.


Re: Locking Up

Chuck Barnett
 

I just got a brand new Windows 10 computer and the logger works perfectly for me. KM9U


Re: Locking Up

 

Dwight,

This is a file permission problem on your Win machine. Try running ad
administrator. If this does not work give me a call.



Dean Davis, N7XG

-------- Original Message --------
From: "parrotham' parrotham@... [N7XGlogsupport]"
<N7XGlogsupport@...>
Sent: Monday, February 29, 2016 6:38 PM
To: N7XGlogsupport@...
Subject: [N7XGlogsupport] Locking Up

Dean,

Any input on the emails from yesterday.

When I try to launch the program with windows 10 it won't be past the
logo
page and says the program has stopped working.

If you can give me some info maybe I can fix it or I will have to reload
the
program from scratch. This is locking up on my Logger Laptop I use when
NCS.

Appreciate any help you can give me

Thank You



73's

Dwight WF4H 3905CCN 40M Early Net Coordinator


Re: Future plans

 

I suppose what I need to do is not export the state field and figure out
how the ADIF specification wants it.



Dean Davis, N7XG

-------- Original Message --------
From: "rjlorenzen@... [N7XGlogsupport]"
<N7XGlogsupport@...>
Sent: Monday, February 29, 2016 11:13 PM
To: N7XGlogsupport@...
Subject: re: [N7XGlogsupport] Re: Future plans

Dean Davis wrote:

Another question arose about DX, specifically Canada. How should
these be reported in ADIF.
-----------
The ADIF people apparently are deprecating VE_PROV in favor of two-letter
province abbrev in the STATE field.


RJ, NA0L


Re: ADIF Export

 

RJ,

In any version of the logger you can filter data and export.



Dean Davis, N7XG

-------- Original Message --------
From: "rjlorenzen@... [N7XGlogsupport]"
<N7XGlogsupport@...>
Sent: Tuesday, March 01, 2016 12:56 AM
To: N7XGlogsupport@...
Subject: [N7XGlogsupport] Re: ADIF Export

Dean,


That was me. Even after filtering to a handful of contacts, ADIF export
always outputs the entire database. This is still true in version 5.02.01.


RJ, NA0L


---In N7XGlogsupport@..., <dean@...> wrote :

Johnny,

I think in an earlier post you expressed a desire to be more selective
when you do ADIF exports. In the current version on the main menu you
can
filter contacts and when you do an ADIF export it will apply that
filter.



Dean Davis, N7XG


Re: ADIF Export

 


Dean,

That was me. ?Even if I filter down to a handful of contacts, ADIF always exports the entire database. ?This is still true in 5.02.01. ?CSV export works as it should.

RJ, NA0L


---In N7XGlogsupport@..., <dean@...> wrote :

Johnny,

I think in an earlier post you expressed a desire to be more selective
when you do ADIF exports. In the current version on the main menu you can
filter contacts and when you do an ADIF export it will apply that filter.



Dean Davis, N7XG


Re: Future plans

 

Dean Davis wrote:

Another question arose about DX, specifically Canada. How should?
these be reported in ADIF.
-----------
The ADIF people apparently are deprecating VE_PROV in favor of two-letter province abbrev in the STATE field.

RJ, NA0L


Locking Up

 

¿ªÔÆÌåÓý

Dean,

Any input on the emails from yesterday.

When I try to launch the program with windows 10 it won't be past the logo page and says the program has stopped working.

If you can give me some info maybe I can fix it or I will have to reload the program from scratch. This is locking up on my Logger Laptop I use when NCS.

Appreciate any help you can give me

Thank You

?

73's

Dwight????? WF4H 3905CCN 40M Early Net Coordinator

?


Re: Future plans

 

Dean

For Canada, a US op is supposed to sign as Call/Canadian identifier, e.g., KI4WCQ/VE3.

I think that is the way the call should be entered under call in a logger.? Most of the time one would see the above logged in N7XG as KI4WCQ? portable?? VE3, which may work for the way the logger keeps track of everything, but I don't think it's the way it should be done....i.e., as how it would be done in any other logger or on paper.

I have heard many US stations check into our nets from Canada, and they generally don't sign their call as the rules for Canadian operation state, or the call isn't usually put into the logger the way they signed or should sign.

OTOH, stations like K9EA check in properly with the Canadian identifier on the nets where I saw him in Canada and it seems to have made it into the logger in those cases.? When it doesn't, this could be remedied by the NCS, but sometimes one may not be familiar with CEPT or IARP rules.? Some require the country identifier before the call, some require it at the end of the call as Canada.

I think in these few DX cases, we can deal with a manual edit if we need to.

73,
Johnny KI4WCQ


---In N7XGlogsupport@..., <dean@...> wrote :

What I have seen in the past were things like this:

VE3/W1ABC

or

W1ABC/VE3

What I will add is a second check ox to append the /P and hopefully people
can figure it out for them selves.



Dean Davis, N7XG

-------- Original Message --------
> From: "ki4wcq52@... [N7XGlogsupport]"
<N7XGlogsupport@...>
> Sent: Sunday, February 28, 2016 7:07 AM
> To: N7XGlogsupport@...
> Subject: re: [N7XGlogsupport] Re: Future plans
>
> I see the problem a P5 would cause, but you can't account for all cases
of stupidity or ignorance by an operator. I would simply offer the option
of /P. If it is something more unusual such as /call area or some other way
to sign a call, we just live with it and know it means manual editing for
an upload.
>
> I don't know what you are asking in regards to DX and Canada. Can you
elaborate?
>
> Johnny KI4WCQ
>
>
> ---In N7XGlogsupport@..., <dean@...> wrote :
>
> Greetings,
>
> I have added an option on the ADIF export screen to allow /M to be
> appended for mobile contacts.
>
> I think the /P is a bit more messy. a couple of years ago one of our
> members sent out a huge pile of cards and he had his call sign appended
> with /P5. Another question arose about DX, specifically Canada. How
should
> these be reported in ADIF
>
>
>
> Dean Davis, N7XG
>
> -------- Original Message --------
> > From: "rjlorenzen@... mailto:rjlorenzen@... [N7XGlogsupport]"
> <N7XGlogsupport@... mailto:N7XGlogsupport@...>
> > Sent: Monday, February 22, 2016 4:08 PM
> > To: N7XGlogsupport@...
mailto:N7XGlogsupport@...
> > Subject: [N7XGlogsupport] Re: Future plans
> >
> > Thanks for the feedback, Johnny. I haven't gone far enough along to
see
> much of a pattern for how people sign mobile, etc. You might consider
> adding a duplicate qso without the /M suffix; it might up your match
rate.
> In all but one of my matched qsos with mobiles, they used just their
base
> callsigns.
> >
> >
> > As to ARRL not believing that I can be in two places at the same time,
> they do accept our cards and we DO believe that! It is possible to get
two
> or three matches from state lines or tri-states. It is only neccessary
for
> the fixed station to upload duplicate qsos at slightly different times
(a
> minute difference works), else the records just overwrite each other.
The
> mobile just does a separate upload for each state (which is normal), but
> again with the qsos at slightly different times. This gets more
interesting
> with mobile to mobile tri-states, however.
> >
> >
> > RJ, NA0L
> >
> > ---In N7XGlogsupport@...
mailto:N7XGlogsupport@..., <ki4wcq52@...> wrote :
> >
> > RJ,
> >
> > Yes, my thought was for LoTW. I log a station the way he signs his
call.
> If he says mobile, I log /M. Likewise if he says portable, it is /P or
if
> he says stoke 3 I log /3. Hopefully he has made a certifcate for the way
he
> signs on the air.
> >
> > If the op uses LoTW, I usually get a match on the call. I have no
control
> on where he indicates he is, that is determined by the certificate he
used
> to sign the log...which means he would need multiple mobile or portable
> certificates for the state visited and signs with the right one.
> >
> > I have several LoTW confirms from W9OO/M and KT8D/M or W8JMF/M, to name
a
> few, from various states they operated from. Also, have them from no CCN
> ops who signed their call and was recorded in that manner.
> >
> > I will concede that not a lot of CCN folks use LoTW even operating
from
> home, let alone mobile or portable.
> >
> > A check would work ok as you suggested.
> >
> > The reason for the difficulty you note with state lines is that the
> position of ARRL is that you can't be in two places at the same time.
> >
> > 73,
> > Johnny KI4WCQ


ADIF Export

 

Johnny,

I think in an earlier post you expressed a desire to be more selective
when you do ADIF exports. In the current version on the main menu you can
filter contacts and when you do an ADIF export it will apply that filter.



Dean Davis, N7XG


Re: Future plans

 

What I have seen in the past were things like this:

VE3/W1ABC

or

W1ABC/VE3

What I will add is a second check ox to append the /P and hopefully people
can figure it out for them selves.



Dean Davis, N7XG

-------- Original Message --------
From: "ki4wcq52@... [N7XGlogsupport]"
<N7XGlogsupport@...>
Sent: Sunday, February 28, 2016 7:07 AM
To: N7XGlogsupport@...
Subject: re: [N7XGlogsupport] Re: Future plans

I see the problem a P5 would cause, but you can't account for all cases
of stupidity or ignorance by an operator. I would simply offer the option
of /P. If it is something more unusual such as /call area or some other way
to sign a call, we just live with it and know it means manual editing for
an upload.

I don't know what you are asking in regards to DX and Canada. Can you
elaborate?

Johnny KI4WCQ


---In N7XGlogsupport@..., <dean@...> wrote :

Greetings,

I have added an option on the ADIF export screen to allow /M to be
appended for mobile contacts.

I think the /P is a bit more messy. a couple of years ago one of our
members sent out a huge pile of cards and he had his call sign appended
with /P5. Another question arose about DX, specifically Canada. How
should
these be reported in ADIF



Dean Davis, N7XG

-------- Original Message --------
From: "rjlorenzen@... mailto:rjlorenzen@... [N7XGlogsupport]"
<N7XGlogsupport@... mailto:N7XGlogsupport@...>
Sent: Monday, February 22, 2016 4:08 PM
To: N7XGlogsupport@...
mailto:N7XGlogsupport@...
Subject: [N7XGlogsupport] Re: Future plans

Thanks for the feedback, Johnny. I haven't gone far enough along to
see
much of a pattern for how people sign mobile, etc. You might consider
adding a duplicate qso without the /M suffix; it might up your match
rate.
In all but one of my matched qsos with mobiles, they used just their
base
callsigns.


As to ARRL not believing that I can be in two places at the same time,
they do accept our cards and we DO believe that! It is possible to get
two
or three matches from state lines or tri-states. It is only neccessary
for
the fixed station to upload duplicate qsos at slightly different times
(a
minute difference works), else the records just overwrite each other.
The
mobile just does a separate upload for each state (which is normal), but
again with the qsos at slightly different times. This gets more
interesting
with mobile to mobile tri-states, however.


RJ, NA0L

---In N7XGlogsupport@...
mailto:N7XGlogsupport@..., <ki4wcq52@...> wrote :

RJ,

Yes, my thought was for LoTW. I log a station the way he signs his
call.
If he says mobile, I log /M. Likewise if he says portable, it is /P or
if
he says stoke 3 I log /3. Hopefully he has made a certifcate for the way
he
signs on the air.

If the op uses LoTW, I usually get a match on the call. I have no
control
on where he indicates he is, that is determined by the certificate he
used
to sign the log...which means he would need multiple mobile or portable
certificates for the state visited and signs with the right one.

I have several LoTW confirms from W9OO/M and KT8D/M or W8JMF/M, to name
a
few, from various states they operated from. Also, have them from no CCN
ops who signed their call and was recorded in that manner.

I will concede that not a lot of CCN folks use LoTW even operating
from
home, let alone mobile or portable.

A check would work ok as you suggested.

The reason for the difficulty you note with state lines is that the
position of ARRL is that you can't be in two places at the same time.

73,
Johnny KI4WCQ


Re: Future plans

 

I see the problem a P5 would cause, but you can't account for all cases of stupidity or ignorance by an operator.? I would simply offer the option of /P.? If it is something more unusual such as /call area or some other way to sign a call, we just live with it and know it means manual editing for an upload.

I don't know what you are asking in regards to DX and Canada.? Can you elaborate?

Johnny KI4WCQ


---In N7XGlogsupport@..., <dean@...> wrote :

Greetings,

I have added an option on the ADIF export screen to allow /M to be
appended for mobile contacts.

I think the /P is a bit more messy. a couple of years ago one of our
members sent out a huge pile of cards and he had his call sign appended
with /P5. Another question arose about DX, specifically Canada. How should
these be reported in ADIF



Dean Davis, N7XG

-------- Original Message --------
> From: "rjlorenzen@... [N7XGlogsupport]"
<N7XGlogsupport@...>
> Sent: Monday, February 22, 2016 4:08 PM
> To: N7XGlogsupport@...
> Subject: [N7XGlogsupport] Re: Future plans
>
> Thanks for the feedback, Johnny. I haven't gone far enough along to see
much of a pattern for how people sign mobile, etc. You might consider
adding a duplicate qso without the /M suffix; it might up your match rate.
In all but one of my matched qsos with mobiles, they used just their base
callsigns.
>
>
> As to ARRL not believing that I can be in two places at the same time,
they do accept our cards and we DO believe that! It is possible to get two
or three matches from state lines or tri-states. It is only neccessary for
the fixed station to upload duplicate qsos at slightly different times (a
minute difference works), else the records just overwrite each other. The
mobile just does a separate upload for each state (which is normal), but
again with the qsos at slightly different times. This gets more interesting
with mobile to mobile tri-states, however.
>
>
> RJ, NA0L
>
> ---In N7XGlogsupport@..., <ki4wcq52@...> wrote :
>
> RJ,
>
> Yes, my thought was for LoTW. I log a station the way he signs his call.
If he says mobile, I log /M. Likewise if he says portable, it is /P or if
he says stoke 3 I log /3. Hopefully he has made a certifcate for the way he
signs on the air.
>
> If the op uses LoTW, I usually get a match on the call. I have no control
on where he indicates he is, that is determined by the certificate he used
to sign the log...which means he would need multiple mobile or portable
certificates for the state visited and signs with the right one.
>
> I have several LoTW confirms from W9OO/M and KT8D/M or W8JMF/M, to name a
few, from various states they operated from. Also, have them from no CCN
ops who signed their call and was recorded in that manner.
>
> I will concede that not a lot of CCN folks use LoTW even operating from
home, let alone mobile or portable.
>
> A check would work ok as you suggested.
>
> The reason for the difficulty you note with state lines is that the
position of ARRL is that you can't be in two places at the same time.
>
> 73,
> Johnny KI4WCQ