On 2/28/2013 10:55 AM, Michael Armstrong wrote:
Well, to be totally honest guys, I normally export my writelog
contents at the end of that particular contest and import it to my
normal daily logging program......
You are correct - this is not generally a problem for *contest* logs
since they are typically exported once at the end of the contest.
The ADIF is imported to another "everyday logger" and handled that
way or the Cabrillo is used as an input to tQSL and archived.
> Unless I am missing something here...... or is it that the "subject
> line" above is the operative point..... Someone is trying to use
> writelog for general logging chores.
Yes, the subject line is the operative point. There are many who
prefer to use their contest logger for everyday operation - whether
it be WriteLog or one of the half-dozen or more other contest
programs - as they believe using the same logger eery day makes them
more productive in the contest (muscle memory, familiarity, etc.).
Unfortunately, a "contest" like the "General DXCC DXCC tracking log
keeper" or "Dxpedition Mode" (other contest loggers have similar
facilities) does not end at 2359z on Sunday. This means that those
who use the contest logger and "push the button" when then close the
station often upload every (non-contest) QSO they have ever made each
time they upload logs to Logbook (in some cases every day!).
Again, the issue is not limited to Writelog by a long shot ... it is
inherent in a "contest that never ends." The solution lies not only
in additional controls with the software but with user education and
a willingness of the user to make the effort to "upload responsibly."
73,
... Joe, W4TV
On 2/28/2013 10:55 AM, Michael Armstrong wrote:
Well, to be totally honest guys, I normally export my writelog contents
at the end of that particular contest and import it to my normal daily
logging program...... From there I do the LOTW thing because it does
what I mentioned earlier and flags the QSOs for LOTW sent or not. So I
tell the "daily" logging program to export the LOTW qsos that haven't
been flagged as sent and then tell it to flag them as sent at the same
time.
So that keeps me up to date with LOTW without having to use date ranges
and the like. It IS a really good point, given the recent LOTW issues
with delayed processing after major contests, that there should be a
facility that flags LOTW sent (or something of that nature) in writelog
so that ENTIRE logs aren't uploaded again and again and again. However,
I am not really sure that is a truly valid issue since a contest log,
for any particular contest, should contain only those qsos from that
particular contest only, right? If so, then uploading a contest log to
LOTW should only contain the qsos from that ONE contest. So no
issue........
Unless I am missing something here...... or is it that the "subject
line" above is the operative point..... Someone is trying to use
writelog for general logging chores. I don't think I would recommend
that, personally, because so many features, in the generic logging
software, are missing in writelog..... which is the way it should be to
speed up the program and not have all those unnecessary functions
hogging memory during a contest.
Hope that wasn't too long. BTW, I am switching from Logger 32 (a VERY
good logging program) to a commercial one that I paid for recently. The
commercial one has some features I find particularly useful and they
aren't likely to be written into Logger32 any time soon because, quite
frankly, they wouldn't be of interest to the vast majority of hams.....
just me.... LOL. Anyway, I find the LOTW export functions and the
importing of logs from Writelog into Logger 32 to be flawless..... In
case anyone was wondering what I was using and how easy/difficult it was
to switch between the two programs (Logger 32 and Writelog).
Mike AB7ZU
On 2/28/2013 8:20 AM, Jay WS7I wrote:
Well I just log my own callsign at the time I send to LOTW. So I just
use writelog's find call and select the dates in between.
Jay WS7I
On 2/27/2013 6:28 PM, Joe Subich, W4TV wrote:
I agree this is a cumbersome process and would hope a fix could be
provided so WL can export the date ranges itself rather than have to
produce the entire adif and then hone it down further outside of WL.
It could be something as simple as storing the date/time of the last
exported QSO in each log and then not exporting anything prior to
that unless the user confirmed an "override": "You have already
signed the QSOs before YYYY-MM-DD HH:MM for LotW. Are you sure?"
(for "General DXCC Tracking Log") or "You have already signed this
log. Are you sure?" (for a specific contest log).
73,
... Joe, W4TV
On 2/27/2013 9:14 PM, Gary AL9A wrote:
Frank,
Yes, I've seen that work around mentioned on the reflectors before. It
will work, provided the pilot is as conscientious as you and makes note
of the start and end dates to be uploaded each time. I agree this is a
cumbersome process and would hope a fix could be provided so WL can
export the date ranges itself rather than have to produce the entire
adif and then hone it down further outside of WL. Many opportunities
for something to go wrong or for inexperienced/lazy pilots to just
upload the whole shooting match each time!
73,
Gary AL9A
----- Original Message ----- From: "Frank Fallon" <n2ff@optonline.net>
To: <writelog@contesting.com>
Sent: February 27, 2013 3:12 PM
Subject: Re: [WriteLog] Writelog for general logging?
Good point, Gary.
But there is another alternative which avoids downloading another
logging program. It's a little bit more cumbersome, but I solve the
problem by having Writelog export my general DX log as an ADIF file to
a folder I named "LOTW" and then I call up TQSL and ask it to sign the
entire file. At a point in the process I then have the ability to
specify start and end dates. Using that feature enables me to send a
much smaller file. Yes, it takes more time but avoids using another
logging program. Yes, It certain would be great if the date range
features was directly available in Writelog. (hint hint nudge nudge).
Frank...N2FF....
On 2/5/2013 5:02 AM, Gary AL9A wrote:
There is a problem with using the both the DXpedition mode and
General DXCC tracking log keeper and exporting to LOTW from these
modules. Whenever you do a File/Export/Trusted QSL file... you are
exporting the ENTIRE log to LOTW, not just the latest QSOs. Unlike a
true general logger, WriteLog's various modules lack the ability to
select just some QSOs in the log by specifying a range of dates to be
included in the upload. This is not a problem for uploading a
contest log as you do want to upload the entire record. But...
If your log is small this is not a big problem. However, if your log
contains thousands of QSOs you are needlessly uploading thousands of
duplicate transactions to LOTW with each update. This is an enormous
waste of LOTW computer resources and needlessly causes delays for the
entire LOTW community. A far better approach would be to find a good
general purpose logger, either a freebee from the internet, or a low
cost product that offers the features necessary to control which of
your log records are going to be uploaded to LOTW. The DXLabs suite
at http://www.dxlabsuite.com/ comes to mind as it is a powerful
package that is free for the asking.
If you have need of a general logger and want to use one of the
WriteLog modules fine. Just be a considerate amateur and don't
utilize the LOTW upload directly from these modules. Instead find
another way to create a tq8 file that contains only the few new QSOs
that you need to upload.
73,
Gary AL9A
-
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2899 / Virus Database: 2641/6136 - Release Date:
02/27/13
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|