Re: [Dx4win] Wish list, again -- LOTW Import
Not really necessary. DX4Win has a very handy feature... export to DX4Win format. It creates a text version of the file that can very easily be modified with search and replace. Don't use notebook... too slow... but you can download PFE which is easy to use and very fast for large searches... orders of magnitude faster than notebook. Lee Hallin wrote: > 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 > __ 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] Using the VE7CC cluster with DX4Win
Info must be somewhere, but I can't find it!! I have looked in the AD1C app notes and the searchable archives, I see lots of people asking the same question, but I can't find the answer. Could someone please let me have a link to how to set up DX4Win and VE7CC cluster so that they can be used together? 73, Dave, G3UEG __ 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] Using the VE7CC cluster with DX4Win
First thing to do is to edit your dx4win.tcp file (in the Save Folder) and add an entry that points to your localhost, port 7300. There are enough examples of that in the file itself you should be able to figure out how (I copy one of the other lines, paste it at the top of the .tcp file and modify it). Mine looks like K3NC-5>My computer,127.0.0.1:7300 Then, in CC user, select the Ports/Logging Program item under the Configuration menu item. This will open up a dialog box. In the middle of it is a group called Telnet. Click the checkbox that says "Enable TCP" and ensure the radio button that says "Use port 7300" is selected. On the right of the dialog is a list of the types of messages that CC User can send to DX4WIN. Select those you want, click Apply at the bottom. Then in DX4WIN's preferences, select TCP/IP for your DXCluster comm port, open the cluster window and right click in it to select the cluster you want (in my case it would be K3NC-5). You should be seeing messages from CC User flowing to DX4WIN very shortly! 73 Neal Campbell Abroham Neal Software Programming Services for Windows, OS X and Linux www.abrohamnealsoftware.com (540) 242 0911 On Fri, Apr 3, 2009 at 11:34 AM, David Gould wrote: > Info must be somewhere, but I can't find it!! I have looked in the > AD1C app notes and the searchable archives, I see lots of people > asking the same question, but I can't find the answer. > > Could someone please let me have a link to how to set up DX4Win and > VE7CC cluster so that they can be used together? > > 73, > Dave, G3UEG > > __ > 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] Using the VE7CC cluster with DX4Win
www.bcdxc.org/ve7cc/logging.htm 73, Masa, AJ3M On 4/3/09, David Gould wrote: > Info must be somewhere, but I can't find it!! I have looked in the > AD1C app notes and the searchable archives, I see lots of people > asking the same question, but I can't find the answer. > > Could someone please let me have a link to how to set up DX4Win and > VE7CC cluster so that they can be used together? > > 73, > Dave, G3UEG > > __ > 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 > -- Sent from my mobile device Masa Miura, AJ3M Bethesda, MD Website: http://www.minokobo.com/je2ywy/ywy12aj3m/ Skype: aj3m-masa Email: masa.miura.a...@gmail.com a...@pvrc.org __ 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] Using the VE7CC cluster with DX4Win
On Fri, Apr 3, 2009 at 9:53 AM, Neal Campbell wrote: > First thing to do is to edit your dx4win.tcp file (in the Save Folder) > and add an entry that points to your localhost, port 7300. There are > enough examples of that in the file itself you should be able to > figure out how (I copy one of the other lines, paste it at the top of > the .tcp file and modify it). Mine looks like > K3NC-5>My computer,127.0.0.1:7300 DX4WIN.TCP already contains that entry: LOCAL>CC User,localhost:7300 73 - Jim AD1C -- 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
Re: [Dx4win] Wish list, again -- LOTW Import
>Not really necessary. DX4Win has a very handy feature... export to >DX4Win format. It creates a text version of the file that can very >easily be modified with search and replace. That's the .DXQ file format. In my experience, WordPad (not Notepad) does a fine job with search and replace with these files, but I'm sure there are lots of third-party text editors that would be more powerful. The problem with the LOTW: stuff is that the text in each record is unique, so a straight search and replace won't work. I'm not aware of a text editor with a search and replace function that can find "LOTW: " and replace the entire string with a blank. Do you know of any that can do this? 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
Re: [Dx4win] Wish list, again -- LOTW Import
>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. Unchecking the detail box suppresses everything except the occurrence of the QSL. Actually, I WANT the state, grid, etc. information to update the log; this is especially useful for 6 meter VUCC updates and good to have just in case I should decide to start chasing counties in the future. I just don't see that it needs to be put in twice, once in the fields where it belongs and again in the QSO comments field. 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
Re: [Dx4win] Wish list, again -- LOTW Import
> -Original Message- > From: dx4win-boun...@mailman.qth.net [mailto:dx4win- > boun...@mailman.qth.net] On Behalf Of Randy Farmer > Sent: Friday, April 03, 2009 9:17 AM > To: Mel; Lee Hallin > Cc: dx4win@mailman.qth.net > Subject: Re: [Dx4win] Wish list, again -- LOTW Import > > > >Not really necessary. DX4Win has a very handy feature... export to > >DX4Win format. It creates a text version of the file that can very > >easily be modified with search and replace. > > That's the .DXQ file format. In my experience, WordPad (not Notepad) > does a fine job with search and replace with these files, but I'm > sure there are lots of third-party text editors that would be more > powerful. The problem with the LOTW: stuff is that the text in each > record is unique, so a straight search and replace won't work. I'm > not aware of a text editor with a search and replace function that > can find "LOTW: " and replace the > entire string with a blank. Do you know of any that can do this? Check out Boxer http://www.boxersoftware.com/ It can do regular expressions, but also has a powerful macro language as well. 73, Cliff K3LL/6 > > 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
Re: [Dx4win] Using the VE7CC cluster with DX4Win
Please let me know if I missed anything: http://dx4win.ad1c.us/cluster/index.htm#VE7CC 73 - Jim AD1C On Fri, Apr 3, 2009 at 9:34 AM, David Gould wrote: > Info must be somewhere, but I can't find it!! I have looked in the > AD1C app notes and the searchable archives, I see lots of people > asking the same question, but I can't find the answer. > > Could someone please let me have a link to how to set up DX4Win and > VE7CC cluster so that they can be used together? > > 73, > Dave, G3UEG -- 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
Re: [Dx4win] Wish list, again -- LOTW Import
I think we're missing Randy's point. Users shouldn't have to fix this stuff. Some will be able to, some won't. Perhaps Paul can make two changes: 1. An option to NOT put the LoTW comments in the "Notes for this QSO" field 2. A Multiple QSO operation to remove such comments from an existing log. DX4WIN still needs a way to identify cases where the LoTW data doesn't match what's already in the log. Randy, I assume that's OK with you. 73 - Jim AD1C -- 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
Re: [Dx4win] Wish list, again -- LOTW Import
>I think we're missing Randy's point. Users shouldn't have to fix this >stuff. Some will be able to, some won't. > >Perhaps Paul can make two changes: > >1. An option to NOT put the LoTW comments in the "Notes for this QSO" field > >2. A Multiple QSO operation to remove such comments from an existing log. > >DX4WIN still needs a way to identify cases where the LoTW data doesn't >match what's already in the log. Randy, I assume that's OK with you. I agree on all counts. Items 1 and 2 would have saved me a huge amount of time. It is important that data mismatches be flagged for resolution. 73... Randy __ 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] [Van spam verdacht] Wish list, again -- LOTW Import
Hi Randy and others, Here my comments and explanation why I like it this way, Some improvements from Paul will certainly reduce the amount and sometimes why I hate it But this is due USER mistakes. > 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. This could have been avoided if you didn´t check the ¨Include QSL details¨ on LoTW Download Report like Jim AD1C responded earlier today. But stuff like WAS-GRID Won´t be downloaded. and that is also not good. >>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 > 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!). The freq and other txt are a result of Jim AD1C his nice ADIF2DXQ conversion program and are placed by DX4WIN in the Notes for this call, but If you don´t like to have these comments in it you can use the freeware program I posted earlier this week and cut away the unneeded items (delete columm) almost forgot that it was you that announced the problem with . and , so you know how to handle that program, I use for editing files Textpad instead of wordpad because it can do much more You can create macros to select what you need to search for and replace with what you like. My adif imports from contest logs have been done with rewritten adif filters So WYSIWYG (What you see is what you get) > 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. I find that the start with ¨LoTW:¨ in notes is very usefull in dx4win Because with F8 looking up ¨LOTW: STATE¨ will only show up those qso´s where Both are present, same for other items. >"LOTW: State=GA County=Harris Grid=EM72 CQZone<>5" is written in the notes for this call because one of the items was incorrect-- in this case it is CQZone 5 like you explained. When all downloaded data is correct and put in the correct field there is NO LOTW: in the notes for this call. I am sure that Paul is reading this and will probably come up with something That for instance only shows the corrupt items like LOTW: CQZone<>5, wrong Grid This part needs the user his attention because there is a difference between the log And the import. I agree that with massive import this is a big job to correct but I prefer To have it in my log then somewhere on a report sheet. This get lost or deleted And your log stays bugged. I have 41k in my log and earlier this week I did a full download of all my LOTW confirmations(6500) (did it because I had more confirmed due a conflict), exported my log changed UPL CFN to N imported in a new file and then imported the lotw adif. First lookup with F8 in Notes with LOTW: showed 1700 problems Used my textpad editor on a new filtered export (only those 1700 where exported) After searching and replace on items like described b4 I imported again with overwrite Qso´s and this reduced my LOTW report problems to 321 qso´s now. (+/- 2hours) 181 where gridlocators because in my log was JO21ba and the upload showed JO21 only Selected only those with f8
[Dx4win] DX4WIN.CTY #60 - final call
This is the final call for input to DX4WIN.CTY Release #60. Current release notes are here: http://www.country-files.com/dx4win/release.htm#60 I have NOT updated the QSL Bureau flags. I'll try my best to get it into this release. I still plan to release the database the weekend of April 4/5 If you have any input, please get it me before then. 73 - Jim AD1C -- 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
Re: [Dx4win] [Van spam verdacht] Wish list, again -- LOTW Import
>I find that the start with ¨LoTW:¨ in notes is very usefull in dx4win >Because with F8 looking up ¨LOTW: STATE¨ will only show up those qso´s where > >Both are present, same for other items. This points out the need for a filter dropdown choice of "Not blank" in the State, Grid and Zone (and other?) fields, similar to that provided in Microsoft Excel. The fact that the record has been updated from LOTW is already denoted by the setting of the Upl Cnf flag. Use of the F8 filtering function to filter on a combination of Upl Cnf = Y and State = (notblank) would do the same job without requiring extra text in the log file. Inserting extra text in the log file to make up for a deficiency in the program's native search function is a less than optimum approach. Another feature that would be "really nice" for troubleshooting LOTW problems would be to provide an extra field in the log record for a date stamp when the Upl Cnf flag was set. This would require altering the structure of the log file, however, and is almost certainly not worth the complication. > >"LOTW: State=GA County=Harris Grid=EM72 CQZone<>5" is written in the notes >for this call because one of the items was incorrect-- in this case it is >CQZone 5 >like you explained. When all downloaded data is correct and put in the >correct >field there is NO LOTW: in the notes for this call. >I am sure that Paul is reading this and will probably come up with something >That for instance only shows the corrupt items like LOTW: CQZone<>5, wrong >Grid >This part needs the user his attention because there is a difference between >the log >And the import. Actually, the point of picking this particular example was that DX4WIN was wrong in selecting zone 4 and didn't correct the error on LOTW import. KU8E is actually in Georgia, which is zone 5. Of course there is no way for the software to know that, but the update after the LOTW record import should have picked this up when the State field was populated with GA. I also found plenty of records where there was no zone problem, just the updated State and County fields. Each of these got the "LOTW:" treatment too. So the "LOTW:" notation is not indicative of a just a conflict between existing log data and imported data. It simply indicates that there was information, correct or not, in the imported LOTW report record that wasn't in the original log record. I completely agree that imported data that conflicts with data already in the log should definitely be flagged so the conflict can be resolved. As I see it, the main problem with the "LOTW:" text insertion is that it blurs the distinction between updated information and conflicting information in the import record. In the case where imported information disagrees with information in the log, I'd prefer to see the same "ERROR:..." message that's used for flagging zone and country prefix differences. This alerts the user that there really is some sort of problem that needs to be looked at. In the case where the LOTW import simply filled previously blank fields, it's up to the user to verify the new information if he chooses to. The search procedure discussed above seems to be the best way to select the records that need to be examined. >I agree that with massive import this is a big job to correct but I prefer >To have it in my log then somewhere on a report sheet. This get lost or >deleted And your log stays bugged. I prefer to work from an import change list, especially one in comma-delimited format that I can drop into Excel and manipulate to pop out the changes that I care about. Then I can go to the log itself and fix only the records I've selected. To each his own. >...181 where gridlocators because in my log was JO21ba and the upload showed >JO21 only Which brings up another point. The program does wonders with pattern searches in looking for callsigns. Surely figuring out that JO21ba and JO21 are the same grid square can't be that difficult. The structure of grid square nomenclature is well-defined. If the first four characters match, it's the same grid. Requiring a literal string match in the Grid field seems rather primitive. >100 others where LOCATORS that didn´t match some of them there shack is in >the middle >Of the ocean, fixed it with QRZ.com when states and county were equal. >Now I am still stucked with 40 problems and these ARE USER FAULTS because in >my log >They lived in CO - DENVER county in 1991 and moved to a new qth in NY but >uploaded >There FULL log with data from the new qth and not from 18 years ago, >Never received paper qsl so can´t check it. I've gotten a few of those myself. Unfortunately, we can't expect the software to correct for mistakes at the supply end of the LOTW chain. When we get information from the guy on the other end of the QSO we have to assume he's providing good information. With humans involved in this operation sometimes that doesn't happen
Re: [Dx4win] [Van spam verdacht] Wish list, again -- LOTW Import
Hi Randy, > >I find that the start with ¨LoTW:¨ in notes is very usefull in dx4win > >Because with F8 looking up ¨LOTW: STATE¨ will only show up those qso´s > where > > > >Both are present, same for other items. > > This points out the need for a filter dropdown > choice of "Not blank" in the State, Grid and Zone > (and other?) fields This is possible Randy do F8 set prefix to K jump to State field and fill in !* Only K qso´s without state filled in will be displayed, this can be done for everything The Prefix is only needed when looking up STATE and COUNTIES Guy ON4AOI >From the helpfile Searching using patterns: The text specified has to match the field exactly, but upper / lower case differences are ignored. By adding special characters to the search field, the search results can be modified. The following characters have a special meaning : ! = Reverse the result of the search outcome (should be the first character) * = Matches zero or more characters; A single * indicates a match for one or more characters ? = Matches a single character Examples for pattern searching in a text field Pattern Matches HD Matches HD but not KK4HD KK?HD Matches KK4HD (and also KK5HD etc) AB* Begins with AB (matches ABCD but not CDAB) *AB AB at the end (matches CDAB but not BCDE) *AB* AB anywhere !AB Does not match AB (matches CDEF but not ABCD) !*AB Does not contain AB (matches BCDE but not CDAB) * Has any text in it (more useful for notes, states, counties etc. !* Has no text; the field is empty __ 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
