>From Ed'a message: > > Any other thoughts?? >
Ed, For my station I use DXBase 2007 to do everything LoTW related, export, import and even QSL cards. At this station I have been using all DXBase versions since DXB 2004 and now have DXB 2007. I have also been a LoTW user shortly after it came on line. My contest software is WriteLog which also tracks seconds and has a LoTW TQSL generator built-in, but I don't use the TQSL option in WL. Using only DXB I have never had the problem with the seconds at all, either going to LoTW or importing data back to DXBase. What I do here and have all along is, first, import my ADIF contest file into DXBase. I double check the last contest log import to see everything looks ok. I then export an ADIF file for the TQSL generator using only the 'No LoTW Submitted' filter in the DXB Selection Wizard (no worry about dates doing it this way). I upload the TQSL generated .tq8 file to ARRL. I always wait one full UTC day before downloading the lotwreport.adi file from ARRL. After downloading the report from ARRL, it is imported into DXB and if required I make minor corrections listed in the error log, mostly these are just county errors. Again, I have never seen a problem with the time with any of my imports from ARRL's LoTW. I only use one DXB station log and not separate logs for contesting and daily activity, simply because it is much easier to track QSL information this way. Also, with the powerful report generators and selection wizard built into DXBase I can extract just about any information I need from this one log. Besides LoTW, I QSL 100% and use the QSL card print program built into DXB. Good luck, Eric - VE3GSI. > -----Original Message----- > From: Ed K1EP > Sent: March-29-09 10:08 AM > To: Dxbase@mailman.qth.net > Subject: [Dxbase] DxBase - LoTW Problem > > LoTW allows one to upload any ADIF log, such as one from a contest > program or from DxBase/ When LoTW first came out, I tried loading > each contest ADIF output into LoTW and quickly realized that it would > be easier to load the contests into DxBase first and then > periodically upload the DxBase ADIF output into LoTW. This works > just fine, until you want to download your LoTW QSLs into > DxBase. Why? Because when DxBase imports ADIF contest logs, it > truncates seconds on the QSO time. Contest log ADIF outputs have > HH:MM:SS, but DxBase time converts it to HH:MM:00. So, if you have > uploaded an ADIF log directly from your contest program into LoTW and > then try to match up a QSL with the downloaded report from LoTW, you > get error messages like (the call has been changed to WA1ABC): > > ERROR: WA1ABC The changes you requested to the table were not > successful because they would create duplicate values in the index, > primary key, or relationship. Change the data in the field or fields > that contain duplicate data, remove the index, or redefine the index > to permit duplicate entries and try again. WA1ABC 20050220 > 192900 20m CW 599 599 > > The QSOs do not match up because the times are now different. So, I > created a new ADIF file from DxBase to upload to LoTW that would > overwrite the old logs. The original contest ADIF file that was both > uploaded to LoTW and DxBase looked like: > > <CALL:6>WA1ABC <QSO_DATE:8>20050220 <TIME_ON:6>192939 <MODE:2>CW > <BAND:3>20M > <FREQ:6>14.094 <RST_SENT:3>599 <RST_RCVD:3>599 <RX_PWR:3>100 <EOR> > > The new ADIF file from DxBase to upload looked like: > > <CALL:6>WA1ABC <QSO_DATE:8>20050220 <TIME_ON:6>192900 <RST_SENT:3>599 > <RST_RCVD:3>599 <QSL_VIA:4>None > <ITUZ:2>28 <OPERATOR:4>K1EP <PFX:3>HB9 <QSL_RCVD:1>N <DXBQSL_RCVD:1>0 > <FREQ:8>14.09400 > <BAND:3>20M <CQZ:2>14 > <MODE:2>CW <QSL_SENT:1>N <DXBQSL_SENT:1>2 <COMMENT:10>ARRL DX CW > <DXBPFX:2>HB <DXCC:3>287 <DXBMGRN:1>1 <DXBAWD:1>0 <DXBSEL:1>0 > <DXBVAL:1>3 > <EOR> > > That created the result in LoTW of a second unconfirmed QSO: > > Details K1EP WA1ABC 2005-02-20 > 19:29:39 20M CW 14.094 SWITZERLAND > Details K1EP WA1ABC 2005-02-20 > 19:29:00 20M CW 14.09400 > > It did not fix the problem, so the QSL from LoTW still has the one > with the seconds, so when I do a report, I still get the time with > seconds. > > <APP_LoTW_OWNCALL:4>K1EP > <STATION_CALLSIGN:4>K1EP > <CALL:6>WA1ABC > <BAND:3>20M > <MODE:2>CW > <QSO_DATE:8>20050220 > <TIME_ON:6>192939 > <QSL_RCVD:1>Y > <QSLRDATE:8>20090325 > <eor> > > About the only thing I can think of right now to fix this problem, is > to write a script to edit the downloaded LoTW report and change any > seconds to :00. > > Any other thoughts?? ______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Dxbase@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
