Re: [Dx4win] Need Help With BV7 Softtware
Hi Randy, Thanks for letting us know about this issue Didn´t had this problem, I am in the , part hi Guy ON4AOI -Oorspronkelijk bericht- Van: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net] Namens Randy Farmer Verzonden: donderdag 2 april 2009 4:12 Aan: dx4win@mailman.qth.net Onderwerp: Re: [Dx4win] Need Help With BV7 Softtware > On the web is a free adif program (editor/converter) called ADIFMASTER >- You can open your adif file with that prg and check if names,fields are >correct Which brings up an interesting experience I just had with ADIFMASTER. It's a really useful tool for looking at and editing ADIF files, but I found that after I did an edit and saved the modified file the new file would crash AD1C's ADIF2DXQ program. After about an hour of hair pulling I looked closely at the modified file and found that it had converted all the decimal points in the frequency field values to European standard commas. This blew the software's mind. The fix was easy; I just did a global search and replace in WordPad to change the commas back to periods. A word to the wise. 73... Randy, W8FN __ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Dx4win@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html __ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Dx4win@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] K31 Extended Command Set
GM: I'm running a K3, S/N 2432 (with MCU 3.06/2.12) with a microKEYER II (with Router 7.2.4) and DX4Win V7.07.02 It seems that the Data Submodes (Data A, AFSK A, FSK D & PSK D) are not being reported by and / or received by the microKEYER II and I'm loosing some functionality (FSK memories). The suggestion from microHAM USA is that DX4Win needs to support the K31 extended command set - or at least enable them when Dx4Win initializes the K3. Can anyone confirm whether DX4Win 7.07.02 does provide this level of K3 support / interface - and if so how do I enable it, since it seems not to be working here. Thanks & 73 Doug, VE3MV __ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Dx4win@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] K31 Extended Command Set
No I'm pretty certain it doesn't. Nor does it with the Icoms (PSK, RTTY). DX4Win is getting a bit long in the tooth... it has it's charms (very fast, very accurate DXCC reporting) but it remains to be seen if Paul has the time or inclination to make it current. You might want to consider using a more appropriate platform for digital modes. I use MixW... there is also WinWarbler and DM780. I import my MixW log into DX4Win and do all my tracking/QSLing etc from there. Works well for me... Mel, VE2DC Doug Joyce wrote: > GM: > > I'm running a K3, S/N 2432 (with MCU 3.06/2.12) with a microKEYER II (with > Router 7.2.4) and DX4Win V7.07.02 > > It seems that the Data Submodes (Data A, AFSK A, FSK D & PSK D) are not being > reported by and / or received by the microKEYER II and I'm loosing some > functionality (FSK memories). The suggestion from microHAM USA is that > DX4Win needs to support the K31 extended command set - or at least enable > them when Dx4Win initializes the K3. > > Can anyone confirm whether DX4Win 7.07.02 does provide this level of K3 > support / interface - and if so how do I enable it, since it seems not to be > working here. > > Thanks & 73 > > Doug, VE3MV > > __ > Dx4win mailing list > Home: http://mailman.qth.net/mailman/listinfo/dx4win > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:Dx4win@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > __ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Dx4win@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] Need Help With BV7 Softtware
Crashing is bad. I'll add a check so the program doesn't crash if this occurs (badly-formed ADIF freq. field). - Jim On Wed, Apr 1, 2009 at 8:12 PM, Randy Farmer wrote: > >> On the web is a free adif program (editor/converter) called ADIFMASTER >>- You can open your adif file with that prg and check if names,fields are >>correct > > Which brings up an interesting experience I just had with ADIFMASTER. > It's a really useful tool for looking at and editing ADIF files, but > I found that after I did an edit and saved the modified file the new > file would crash AD1C's ADIF2DXQ program. After about an hour of hair > pulling I looked closely at the modified file and found that it had > converted all the decimal points in the frequency field values to > European standard commas. This blew the software's mind. The fix was > easy; I just did a global search and replace in WordPad to change the > commas back to periods. > > A word to the wise. > > 73... > Randy, W8FN -- Jim Reisert AD1C/Ø, , http://www.ad1c.us __ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Dx4win@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] Wish list, again -- LOTW Import
Having just done a major cleanup of a log with around 55K QSOs, many of them imports from contest logs, I would like to revive the "Wish List" thread in hopes of influencing the development of future versions of DX4WIN. Specifically, there is room for major improvement in how DX4WIN handles data imports from downloaded LOTW reports. About a year ago, I bit the bullet and decided to import all the 50K+ QSOs from my electronic contest logs, going back to 1989. When the import was complete, I uploaded the log (in several installments) to the LOTW server and was rewarded with around 4000 QSLs. I just did the import of the LOTW report ADIF files back into DX4WIN with the "Imported QSO sets Upload Flag" option set, and have continued to follow that procedure with succeeding updates ever since. This worked fine, and I have picked up lots of DXCC credits from this process. A couple of weeks ago, I happened to be scrolling through the logbook window and realized that the log file was terribly cluttered with large amounts of redundant information in the Notes for this QSO field. I decided to see if I could clean up a lot of this stuff. To my horror, I found in excess of 3000 records that needed to have this material expunged. What do I mean by redundant? If you look at what happens when the program imports a LOTW report, you'll understand. To give a near worst-case example, let's say I get a LOTW QSL for a QSO I made with my friend KU8E in the CQ WPX contest. Since the only exchange in WPX consists of a 599 and serial number, the original contest QSO record will have only the received serial number in the Received log field and the Notes for this QSO field will say "Freq=xx,xxxKHz, WPX CW ". (This is the result of using AD1C's very nice ADIF2DXQ software -- thanks, Jim!). When I do the import of the LOTW record, assuming Jeff has provided all the possible information, the following will be appended to the text in the Notes for this QSO field: "LOTW: State=GA County=Harris Grid=EM72 CQZone<>5". What's redundant here? Practically everything! The "LOTW:" part isn't needed, since the record import sets the Upl Cnf flag. The 'State=GA County=Harris" aren't needed, since the record import populates the State and County fields. Similarly, the Grid field is also populated, so the "Grid=EM72" isn't needed. The "CQZone<>5" part IS useful information, given that the initial import of the contest QSO caused DX4WIN to populate the Zone field with a 4 based on the "8" in the call. Unfortunately, DX4WIN does NOT update the Zone from the imported data. This may not be all bad, since there are a good many LOTW users who mistakenly enter their IARU zone in the CQ zone box when they upload their log files and thus provide the wrong zone in their QSL record. The details of the log changes are really good to have, but they certainly don't belong in the Notes for this QSO field. This information should instead be placed in a transaction log that is generated (or appended to) by the import process. Some sort of indicator in the log that there is updated data that conflicts with previously logged information is a good idea, but this would be much less intrusive than filling the log file with what amounts to a transaction log of the import process. By the way, manually editing thousands of records in the log to get rid of the spurious text was simply too overwhelming to contemplate, as the program provides no tools to manipulate the notes field. What I ended up doing was to export the log in chunks as a .dxq file (choose File > Import/Export from the main window, and then select DX4WIN6 format > File > Export in the Import/Export Filters window) and use WordPad to edit the .dxq file. Editing the .dxq file with WordPad is still a major pain, since the text following the "LOTW:" in each record is unique and you can't just do a search and replace to remove the unwanted text. But it does go much, much faster working with the text file to select and delete the spurious content from each record. After fixing the .dxq file, I then re-imported it into the original log file and let the imported dupes replace the existing records. I broke the project into manageable chunks and finally got all the log entries fixed. It was a monumental job. You can bet I'll stay on top of it in the future. Lest this sound like too much like whining, I want to be clear that I'm still extremely pleased with the comprehensive capabilities of DX4WIN. It does a great job of keeping track of award status and gives the user unparalleled flexibility in handling log data. But like any software, there's always room for improvement. In my book fixing the LOTW import process would be a great leap forward. 73... Randy, W8FN __ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: m
Re: [Dx4win] Wish list, again -- LOTW Import
This is easily solved, but BEFORE the fact. Before you download the lotwreport.adi file from ARRL, there is a check box (normally UNCHECKED) that allows you to include extra information in the downloaded lotwreport.adi file. You must be checking that box, because that is what is adding all the extra data into your log. 73 - Jim AD1C On Thu, Apr 2, 2009 at 7:34 PM, Randy Farmer wrote: > Having just done a major cleanup of a log with around 55K QSOs, many > of them imports from contest logs, I would like to revive the "Wish > List" thread in hopes of influencing the development of future > versions of DX4WIN. Specifically, there is room for major improvement > in how DX4WIN handles data imports from downloaded LOTW reports. > > About a year ago, I bit the bullet and decided to import all the 50K+ > QSOs from my electronic contest logs, going back to 1989. When the > import was complete, I uploaded the log (in several installments) to > the LOTW server and was rewarded with around 4000 QSLs. I just did > the import of the LOTW report ADIF files back into DX4WIN with the > "Imported QSO sets Upload Flag" option set, and have continued to > follow that procedure with succeeding updates ever since. This worked > fine, and I have picked up lots of DXCC credits from this process. > > A couple of weeks ago, I happened to be scrolling through the logbook > window and realized that the log file was terribly cluttered with > large amounts of redundant information in the Notes for this QSO > field. I decided to see if I could clean up a lot of this stuff. To > my horror, I found in excess of 3000 records that needed to have this > material expunged. > > What do I mean by redundant? If you look at what happens when the > program imports a LOTW report, you'll understand. To give a near > worst-case example, let's say I get a LOTW QSL for a QSO I made with > my friend KU8E in the CQ WPX contest. Since the only exchange in WPX > consists of a 599 and serial number, the original contest QSO record > will have only the received serial number in the Received log field > and the Notes for this QSO field will say "Freq=xx,xxxKHz, WPX CW > ". (This is the result of using AD1C's very nice ADIF2DXQ > software -- thanks, Jim!). When I do the import of the LOTW record, > assuming Jeff has provided all the possible information, the > following will be appended to the text in the Notes for this QSO > field: "LOTW: State=GA County=Harris Grid=EM72 CQZone<>5". > > What's redundant here? Practically everything! The "LOTW:" part isn't > needed, since the record import sets the Upl Cnf flag. The 'State=GA > County=Harris" aren't needed, since the record import populates the > State and County fields. Similarly, the Grid field is also populated, > so the "Grid=EM72" isn't needed. > > The "CQZone<>5" part IS useful information, given that the initial > import of the contest QSO caused DX4WIN to populate the Zone field > with a 4 based on the "8" in the call. Unfortunately, DX4WIN does NOT > update the Zone from the imported data. This may not be all bad, > since there are a good many LOTW users who mistakenly enter their > IARU zone in the CQ zone box when they upload their log files and > thus provide the wrong zone in their QSL record. > > The details of the log changes are really good to have, but they > certainly don't belong in the Notes for this QSO field. This > information should instead be placed in a transaction log that is > generated (or appended to) by the import process. Some sort of > indicator in the log that there is updated data that conflicts with > previously logged information is a good idea, but this would be much > less intrusive than filling the log file with what amounts to a > transaction log of the import process. > > By the way, manually editing thousands of records in the log to get > rid of the spurious text was simply too overwhelming to contemplate, > as the program provides no tools to manipulate the notes field. What > I ended up doing was to export the log in chunks as a .dxq file > (choose File > Import/Export from the main window, and then select > DX4WIN6 format > File > Export in the Import/Export Filters window) > and use WordPad to edit the .dxq file. > > Editing the .dxq file with WordPad is still a major pain, since the > text following the "LOTW:" in each record is unique and you can't > just do a search and replace to remove the unwanted text. But it does > go much, much faster working with the text file to select and delete > the spurious content from each record. After fixing the .dxq file, I > then re-imported it into the original log file and let the imported > dupes replace the existing records. > > I broke the project into manageable chunks and finally got all the > log entries fixed. It was a monumental job. You can bet I'll stay on > top of it in the future. > > Lest this sound like too much like whining, I want to be clear that > I'm still extremely pleased with the comprehensive
Re: [Dx4win] Wish list, again -- LOTW Import
Hi all, I realize that Randy was wanting the "fix" in the next DX4WIN version; but... Does anyone else dislike the LOTW: phrase as much as Randy? Let me know direct (save band-width). If enough people would like it removed, I can write a program that would remove all, or the non-conflicting fields, fields from the log (either a ADIF or .DXQ file). If I write a program, are there any other "clean up" options that anyone might want? For instance, if I find a "Error:Mode=OLIVIA" msg in the QSO Notes, should I change the MODE to OLIVIA and remove the msg from the notes? 73, Lee N7NU __ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Dx4win@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
