Is it possible to use writelog for general day to day casual contacts? What would be the best module to use? Thanks! Ke6qr _______________________________________________ WriteLog mailing list WriteL
I have been using the DXpedition mode for general logging for many years. I think the latest version has a general logging module if my memory serves me right, but will have to check. It loads up to
Gary I use for years the DXpedition mode in writelog for my daily log and really works well, if you want to use it for contesting the daily use of WL help you to become more familiar and easy to solv
Hi Andre I would say yes, with a few caveats. Since I'm set up as SO2R on all bands and all modes, I've found it easier to use WL for just about all my logging. For general logging, I use two differe
Start WriteLog. Select Start a New Log... From the WriteLog Contest Selection box, select "General DXCC log keeper" It's good for general day-to-day contact logging. 73, Norm - W1MO On 2/4/2013 17:59
There is one major problem in using Writelog's general tracking mode for everyday operation and then uploading to LotW directly. WriteLog is not alone in the problem - there are half a dozen other c
Joe, I thought LOTW had the capability of simply rejecting a record that matches 100% of what was loaded before. One would think this should not be a major problem for such a complex server? 73 NJ0F
I convert my log to .adi format. During the signing process, I am given the opportunity of selecting a specific date range, rather than sending the entire log file. It's no trouble, really. 73, Norm
Yes, LotW has the capability or rejecting duplicate QSOs - but not until the QSO has been checked to see if it is already in the database! The most "expensive" part of the entire LotW process is che
Thanks for the explanation and I will keep this in mind. Perhaps select a date range as another user on the forum explained a few minutes ago. 73 NJ0F Sent from my iPhone ____________________________
Yes, as Norm explained if one exports the log as and ADIF file and uses that as an input to tQSL it is possible to select a date range when manually signing the file. The downside is that takes more
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 exp
Sure. To minimize wear and tear on my brain, I use one logger (Writelog) for everything. I built my own general operating file template with fields for Call, RST-S, RST-R, Name, QTH, Comments, Power,
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
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 ti
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 o
Joe, it could be something as simple as the addition of a new field in the log file itself.... "LOTW qsl sent." With that flagged, it would only send those whose flag isn't "Y." Stupidly simple idea,
Mike, You are correct - adding "LotW_QSL_Sent" and the date (LotW_QSLSDATE) is consistent with the the workflow envisioned in the Amateur Data Interchange Format (ADIF) and many loggers that provide
Good point Joe..... It IS a contest logger, after all. I guess I was thinking a bit more generically and forgetting the real purpose of writelog in the first place :). Thanks for reminding me ......
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 I agree this is a cumbersome process and would hope a fix coul