KG6NRV wrote: 08 May 2020, 23:21
Hi Nolan, thanks for the detailed reply and resources.
Yes, I am on a current version of the Log4OM.
The Rumlog export version of ADIF is not mentioned in the manual. Is there some why I can determine that by looking at the file? FWIW I'm also on a current version of Rumlog.
You mentioned that the single upload error was possibly from LOTW, and that appears to be the case. This error appears on any QSO, so it has nothing to do with the station involved. Also a syntax error appears on the screen. I am attempting to upload a screenshot though for some reason the 280K png file won't upload to the forum, "file too large" error. I guess it's just not my day for uploads.
Anyway, I put it on Dropbox, and hopefully you can see it here:
https://www.dropbox.com/s/uubhqd1bwylim ... r.png?dl=0
QSL status: I'm unclear if the "requested" status can be changed for QSOs already in the log. Also, wondering why that is the default setting if the QSO has never left the computer? Makes no sense to me. I did see a video where "nil" was the suggested default setting, though I believe that was an earlier version of the program.
Thanks again for all the tips; I've got some reading and watching to do. 73
Bill,
RUMlog may only provide one level of ADIF export. Many logging programs offer a couple various levels that can then export more data elements saved by the logging program than just the basics.
Don't watch (or if you did ... forget what you saw) any videos related to V1 of Log4OM. Very little of those "mature" videos will have any relation to how Log4OM V2 is operating. It is on a completely new database structure and virtually everything is handled differently.
Take some time to go through the Quick Start Guide (some of that will be 'old business' to you, but it won't hurt to have a refresh with you being a new user of Log4OM V2. Spend some time to watch Terry's YouTube videos. He has done them in sequence from the initial start-up and configuration and then on to many of the elements that are most-used.
Be sure that your station information, etc., is as accurate as it can be. Also, when you set up your External Sources (IE: HamQTH, HRDLog, Clublog, LOTW, eQSL) logins and passwords, be sure they are correct. Do not 'copy/paste' ... hand-key them in. Also for the LOTW (TQSL) login/password make sure you don't use the special characters that won't be accepted by TQSL, etc..
I think Terry used 'nil' in a V1 video and don't recall him using it in a V2 video, but it has been a few months since I've seen them all.
The "Requested" information label will be made more clear as you get into the UG and related to 'confirmations'. Again ... "Requested" is now the accepted/preferred verbiage for Q's that have been saved in a log and have NOT YET been uploaded (manually or automatically) or mailed by the OM. Once those Q's have been mailed/uploaded V2 will change the Requested label to "Yes" in the 'sent' field. As for mailing a paper QSL card it is up to the OM to change the Requested to Yes.
Now ... Many OM's (older fogeys like myself) came up with Q's having a "No" in the sent field and once sent they get a "Yes". Those OM's do then change the default from Requested to No and go on their way. I would hold off on making any grand switches until you get a good handle on that and the related changes you will have to tweak.
As I've noted earlier ... the "Requested" label is from the ADIF Standard V3 requirements that set the standards for such data. I can assure you that not everyone is in love with what they are doing, but they are the recognized standard bearer for the ADIF rules. Here is a link to the ADIF Standard that will totally make your head swim. ADIF 3.0.6
http://adif.org.uk/306/ADIF_306.htm
Again ... take your time and one step at a time and try not to get too far ahead of the basics to ensure you have a solid base of data in V2 for everything to work well for you.