Re: [Dx4win] Report
Leave the QSO’s as confirmed, but change the DXCC status to “I” for invalid. This is what I’ve done for unapproved operations or Q’s where my call was busted or NIL. Tom > On Feb 7, 2020, at 9:06 AM, Luc wrote: > > Chris, if cnfm is set to "N" and yet it still appears as confirmed. > > 73 de EA8AM > >> El vie., 7 feb. 2020 a las 14:04, Luc () escribió: >> >> Thanks Mike for your answer. >> If, indeed, I had already checked with F5 that in the DXCC window in >> Mixed, Band and Mode - - >> Thank you for the information about Afghanistan, but unfortunately, I now >> have my antennas on the ground for tower maintenance. >> 73 de EA8AM >> >> El vie., 7 feb. 2020 a las 12:30, Chris Sauvageot () >> escribió: >> >>> Am 07.02.2020 um 13:25 schrieb Luc: change the "Y" to "N" in Cnfm >>> >>> >>> ...there 3 different QSL cnfm exist in DX4WIN >>> QSL card >>> LOTW >>> QSL >>> >>> 73 Chris >>> DL5NAM >>> >>> __ >>> 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 >>> >> >> >> -- >> Si reenvía este correo, es OBLIGACIÓN LEGAL según la "Agencia Española de >> Protección de Datos de Carácter Personal" proteger la intimidad de sus >> contactos, para ello y para evitar SPAM (correo no deseado) hay que seguir >> los siguientes pasos: >> >> 1.- Borre la dirección del remitente y cualquier otra dirección que >> aparezca en el cuerpo del mensaje. >> >> 2.- Introduzca los destinatarios en el apartado CCO (CON COPIA OCULTA) >> >> Recuerde: >> >> Para: Déjelo en blanco. >> >> Ccc: Déjelo en blanco. >> >> Cco: Incluya aquí a sus destinatarios. >> >> Coloque esta nota en sus mensajes. >> >> GRACIAS POR COLABORAR. >> > > > -- > Si reenvía este correo, es OBLIGACIÓN LEGAL según la "Agencia Española de > Protección de Datos de Carácter Personal" proteger la intimidad de sus > contactos, para ello y para evitar SPAM (correo no deseado) hay que seguir > los siguientes pasos: > > 1.- Borre la dirección del remitente y cualquier otra dirección que > aparezca en el cuerpo del mensaje. > > 2.- Introduzca los destinatarios en el apartado CCO (CON COPIA OCULTA) > > Recuerde: > > Para: Déjelo en blanco. > > Ccc: Déjelo en blanco. > > Cco: Incluya aquí a sus destinatarios. > > Coloque esta nota en sus mensajes. > > GRACIAS POR COLABORAR. > __ > 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] eQSL confirmation instead of LOTW
Thank you, Ian and Mike. I’m quite sure that’s what I did, and happy to learn that I made such a careless error, and that it was operator error. I like logical explanations. Thanks again to you and anyone else who responds. Tom K8BKM > On Jan 3, 2020, at 12:22 PM, Mike Cizek W0VTT wrote: > > Hello Tom, > > Is it possible that you clicked on "Confirm eQSL using ADIF File" instead of > "Confirm LoTW using ADIF File" by mistake? They are right next to each > other in the QSO window. > > -- > 73, > Mike Cizek W0VTT > > -Original Message- > From: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net] > On Behalf Of Tom Hammond > Sent: Friday, January 03, 2020 11:05 > To: dx4win@mailman.qth.net > Subject: [Dx4win] eQSL confirmation instead of LOTW > > Greetings, > > I downloaded new LOTW confirmations today (81 of them), saved to an .adi > file, then used that file to confirm QSO's in my log. After importing these > confirmations I noticed that the state and county was updated but not the > LOTW confirmed flag, rather the eQSL flag was changed to Y. I've never > uploaded to eQSL and don't use that method to QSL. I filtered the Q's that > had an eQSL flag of Y and manually changed to LOTW flag to Y. I'm just > wondering why this happened. Any thoughts? I'm okay with "operator error" > but I'd like to know what I did wrong so I never do it again! > > 73, Tom > K8BKM > > > __ > 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] eQSL confirmation instead of LOTW
Greetings, I downloaded new LOTW confirmations today (81 of them), saved to an .adi file, then used that file to confirm QSO’s in my log. After importing these confirmations I noticed that the state and county was updated but not the LOTW confirmed flag, rather the eQSL flag was changed to Y. I’ve never uploaded to eQSL and don’t use that method to QSL. I filtered the Q’s that had an eQSL flag of Y and manually changed to LOTW flag to Y. I’m just wondering why this happened. Any thoughts? I’m okay with “operator error” but I’d like to know what I did wrong so I never do it again! 73, Tom K8BKM __ 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] 3Y0Z
Thanks everyone for the suggestion. Worked as advertised. Tom, K8BKM -Original Message- From: n...@vci.net [mailto:n...@vci.net] Sent: Wednesday, January 10, 2018 4:44 PM To: 'Tom Hammond' <thamm...@chartermi.net>; DX4WIN@mailman.qth.net Subject: RE: [Dx4win] 3Y0Z Add the call sign, change country to Bouvet and save the QSO. Then reselect the QSO and delete it. 3Y0Z will now come up as Bouvet. 73, Dave, N4QS -Original Message- From: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net] On Behalf Of Tom Hammond Sent: Wednesday, January 10, 2018 2:59 PM To: DX4WIN@mailman.qth.net Subject: [Dx4win] 3Y0Z I tried to pre-emptively add 3Y0Z (Bouvet) before the expedition actually begins so I can see spots as soon as they start appearing - or should I say so I can be alerted when an ATNO is spotted. Right now 3Y0Z is coming up Antarctica. I tried to add the callsign to Bouvet but when I select File, Database, Countries, I get a screen saying "Country editor not available". So, will AD1C be publishing a new country file that includes 3Y0Z with a start date of "around" January 23, 2018, the earliest estimated date of arrival on the island? Good luck everyone! See you in the pileups. 73, Tom K8BKM __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to n...@vci.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 Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] 3Y0Z
I tried to pre-emptively add 3Y0Z (Bouvet) before the expedition actually begins so I can see spots as soon as they start appearing - or should I say so I can be alerted when an ATNO is spotted. Right now 3Y0Z is coming up Antarctica. I tried to add the callsign to Bouvet but when I select File, Database, Countries, I get a screen saying "Country editor not available". So, will AD1C be publishing a new country file that includes 3Y0Z with a start date of "around" January 23, 2018, the earliest estimated date of arrival on the island? Good luck everyone! See you in the pileups. 73, Tom K8BKM __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] Uploading FT8 QSO's to LOTW
Greetings folks. Thought I'd share an experience that might help you, or, someone might point out how to do this differently. I've made a handful of FT8 QSO's. Since DX4WIN doesn't have an FT8 mode (YET!) I was selecting a similar mode of JT65. When the ARRL announced that FT8 was now a supported mode on LOTW, I decided to export my FT8 QSO's and upload to LOTW. So, in DX4WIN, I exported my QSOs creating an .adi file. I then edited this file and changed all occurrences of JT65 to FT8. I saved the file and then used TQSL to sign and upload my .adi file. However, TQSL said the "FT8 " was an invalid mode. Wait, what? Maybe you already know where I went wrong. In the .adi file there are XML-like field names. My .adi file had FT8. Well, it turns out that "4" after MODE means that the mode is 4-characters long, BECAUSE, I had originally chosen JT65 as the mode which IS 4-characters long. Once I figured this out, I changed the field heading to FT8 and saved the file. This time my file was signed and uploaded with no errors. I've done similar search and replace from FSK441 to MSK144 but both of those mode strings are 6 characters, so I didn't have to change the field heading. So, lesson to be learned here is, when selecting an alternative mode for your FT8 QSO's, try to find a 3-character mode so that when you perform a search and replace of your adi file, you also won't have to change each occurrence of the length character. There's got to be an easier way.. 73, Tom K8BKM __ 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] new mode
Greetings, How can I add "MSK144" as a new mode to select from in the QSO window? Just made my first two QSO's on this new WSJT-X mode. 73, Tom K8BKM __ 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] QSO distance
Greetings, In the DX4WIN QSO window, in the upper right-hand corner is a display-only field that shows a logged station's Country|IOTA|GridSquare, Heading, and Distance. I would like to know if this information is saved as part of the QSO record, or if it's calculated on the fly. I would like to create a report (or export) of my log data and includes the distance (from my home QTH) so I can do some reporting / analysis by band. Is the distance calculation an internal algorithm that displays the value only, or is the data available to report on? If the answer is no (distance is not stored) then if I export my log data along with a grid square, does anyone know of a macro or external function that I could call from Excel to calculate to populate a distance column? I'm already anticipating the response "how do you know if the QSO was LP or SP?". Well, I don't. I think it's by far the majority of my Q's that were made via a LP, and I don't record that (generally). TIA 73, Tom K8BKM __ 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] Country file updates
Greetings, Recently I updated my country file (and other info) using the AD1C DX4WIN Data Updater. After doing so, I noticed that my DXCC summary statistics were altered and incorrect. It took quite a bit of time and effort to discover that during the update, some of my logged and confirmed QSO's were changed from one country to another. I assume that this is because the update REPLACED my "custom" country file rather than MERGING changes with my file. I have some QSO's that have "odd" or non-standard callsign mappings for particular countries. For example, VE1CR is CY9 (St. Paul Island), not VE (Canada). After the update, this QSO was changed to VE. There are numerous other QSO's that were changed. How do I prevent this from happening with future updates using the Data Updater tool? Do I need to provide these custom callsign mappings to AD1C to add to his database? 73, Tom K8BKM __ 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
