From john at kk9a.com Tue Dec 1 09:44:01 2020 From: john at kk9a.com (john at kk9a.com) Date: Tue, 01 Dec 2020 08:44:01 -0600 Subject: [WriteLog] WL Spots question Message-ID: <20201201084401.Horde.wj5oNaOCPeC04L_B-dYduOb@www11.qth.com> Jamie, nice to work you in Sweepstakes phone, your recorded voice system works very well. A do not operate assisted often but a long time ago I tried this category during a CQWW contest from Aruba. The internet connection was sketchy and I wound up spending more time re-connecting than it was worth. Then I learned about VE7CC's software which reconnects and never had an issue when using it. GL, John KK9A - W4AAA, P40A, etc. Jamie Dupree NS3T wrote: I don't use spots very often, so maybe there is a simple answer to this question. I don't send out spots. I just receive them. During CQWW CW, I kept getting disconnected from various Telnet Skimmer connections. It would happen sometimes after a few minutes, sometimes after an hour or a couple of hours. My conservative estimate is it happened at least 30 times. This wasn't an internet issue on my end as far as I could tell. When the spots stopped, I was using the same internet on the shack computer to look up various Telnet connection information. Is there some kind of instruction that I need to give, or box that I need to check to keep that from happening inside WL? Thanks. 73 Jamie NS3T From lists at w1nr.net Tue Dec 1 09:56:58 2020 From: lists at w1nr.net (Mike McCarthy, W1NR) Date: Tue, 1 Dec 2020 09:56:58 -0500 Subject: [WriteLog] WL Spots question In-Reply-To: <20201201084401.Horde.wj5oNaOCPeC04L_B-dYduOb@www11.qth.com> References: <20201201084401.Horde.wj5oNaOCPeC04L_B-dYduOb@www11.qth.com> Message-ID: If you have multiple connections you need to make each of them unique with an SSID. Try NS3T-1 for your main cluster connection and NS3T-2, NS3T-3, etc. for each skimmer. The cluster connections will bounce you off if it looks like you are connected more than once per SSID. Yes, all the nodes talk to each other regarding logged in call signs. 73 de Mike, W1NR On 12/1/2020 9:44 AM, john at kk9a.com wrote: > Jamie, nice to work you in Sweepstakes phone, your recorded voice system > works very well. > > A do not operate assisted often but a long time ago I tried this > category during a CQWW contest from Aruba.? The internet connection was > sketchy and I wound up spending more time re-connecting than it was > worth. Then I learned about VE7CC's software which reconnects and never > had an issue when using it. > > GL, > > John KK9A - W4AAA, P40A, etc. > > > Jamie Dupree NS3T wrote: > > I don't use spots very often, so maybe there is a simple answer to this > question. > I don't send out spots.? I just receive them. > During CQWW CW, I kept getting disconnected from various Telnet Skimmer > connections.? It would happen sometimes after a few minutes, sometimes > after an hour or a couple of hours.? My conservative estimate is it > happened at least 30 times. > This wasn't an internet issue on my end as far as I could tell.? When > the spots stopped, I was using the same internet on the shack computer > to look up various Telnet connection information. > Is there some kind of instruction that I need to give, or box that I > need to check to keep that from happening inside WL? > Thanks. > 73 Jamie NS3T > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web:? http://www.writelog.com/ From k0cf.craig at gmail.com Tue Dec 1 10:13:11 2020 From: k0cf.craig at gmail.com (k0cf-Craig) Date: Tue, 1 Dec 2020 09:13:11 -0600 Subject: [WriteLog] WriteLog ARRL 160M Contest prefill file Message-ID: I have just generated a WriteLog ADIF prefill file for the ARRL 160M contest and posted it to my club website, the Eastern Iowa DX Association. This link takes you directly to the Prefill section: < https://tinyurl.com/WLprefills > What you will download is a zip file containing the ADIF prefill file, which has the file extension ".adi". The source for this was the file ARRL160.txt from the N1MM+ web site, last updated Nov 30, 2020. After unzipping the ADIF file, start WriteLog and start a new log for the selected contest. Open the WriteLog "Tools" menu and select ?Preset Exchange from ADI file??, browse to the location of your ADIF file and load it. To test it, type a callsign from the ADIF file into the callsign field, press "space" or "tab" to leave that field upon which the received exchange field(s) should automatically fill with data from the prefill file. As always, the accuracy of the data in this file cannot be guaranteed; treat it as a "suggestion" and be sure to log what your QSO partner sends! 73, Craig, K0CF From stu at k6tu.net Tue Dec 1 19:32:57 2020 From: stu at k6tu.net (Stu Phillips) Date: Wed, 2 Dec 2020 00:32:57 +0000 Subject: [WriteLog] New Super Check Partial files available VER20201202 (02 DEC 2020) Message-ID: <44599ED1-BC45-4B72-9C15-40D170C27AE3@k6tu.net> A new release of the Super Check Partial database files is available at: http://www.supercheckpartial.com Calls in the MASTER.DTA file: 35,021 If you would like to contribute your CABRILLO format logs for the SCP database, please send them at any time. The easiest thing to do is to bcc the following email address: logs at supercheckpartial.com ...when you submit your log to the sponsor?s robot after each contest. Please DO NOT send ADIF files, your LOGGER database file, 3830 postings... just CABRILLO! :-) You can send more than one log attachment in a single email BUT PLEASE DON?T SEND THEM IN A ZIP file! If you want to check the version of the SCP files you are using, look for a call beginning with ?VER2". Every SCP file includes the version number in the list of calls in the format VERYYYYMMDD. The next release of the database will be at the beginning of January 2021. Any requested changes or deletions of callsigns received by NOON PST on January 1st, 2021 will be included in that release. PLEASE MAKE SURE TO SEND ADD/CHANGE MESSAGES WITHOUT ATTACHED LOGS OTHERWISE I PROBABLY WON?T SEE YOUR REQUEST due to the email processing robot. PLEASE SEND REQUESTS FOR ADD/CHANGE to logs at supercheckpartial.com - please help me help you - this way, requests don't get lost in my personal email. IMPORTANT: Before sending an add/change message, please check the LATEST version of the SCP database to see whether your requested change (especially add requests) is unnecessary because the call is already present. Please let me know if you find any bad calls in the files. Thanks again to all the contributors! Stu K6TU From k0cf.craig at gmail.com Thu Dec 3 13:57:59 2020 From: k0cf.craig at gmail.com (k0cf-Craig) Date: Thu, 3 Dec 2020 12:57:59 -0600 Subject: [WriteLog] WriteLog ARRL 160M Contest prefill file UPDATE Message-ID: I have just updated the WriteLog ADIF prefill file for the ARRL 160M contest and posted it to my club website, the Eastern Iowa DX Association. This link takes you directly to the Prefill section: < https://tinyurl.com/WLprefills > What you will download is a zip file containing the ADIF prefill file, which has the file extension ".adi". The source for this was the file ARRL160.txt from the N1MM+ web site, last updated Dec 3, 2020. After unzipping the ADIF file, start WriteLog and start a new log for the selected contest. Open the WriteLog "Tools" menu and select ?Preset Exchange from ADI file??, browse to the location of your ADIF file and load it. To test it, type a callsign from the ADIF file into the callsign field, press "space" or "tab" to leave that field upon which the received exchange field(s) should automatically fill with data from the prefill file. As always, the accuracy of the data in this file cannot be guaranteed; treat it as a "suggestion" and be sure to log what your QSO partner sends! 73, Craig, K0CF From gordon.lapoint at gmail.com Thu Dec 3 13:58:32 2020 From: gordon.lapoint at gmail.com (Gordon LaPoint) Date: Thu, 3 Dec 2020 13:58:32 -0500 Subject: [WriteLog] FTRoundup, which contest to use? Message-ID: <8de752cb-bd98-6b61-64c5-8f78dfe63f19@gmail.com> I can not see the FT Roundup in the list of contests, which one should I use?? Thanks, Gordon - N1MGO From gordon.lapoint at gmail.com Thu Dec 3 14:15:11 2020 From: gordon.lapoint at gmail.com (Gordon LaPoint) Date: Thu, 3 Dec 2020 14:15:11 -0500 Subject: [WriteLog] No signals showing in DigiRite Receive Message-ID: <13bcc7cf-d614-9f62-88f7-37df620a463e@gmail.com> I have DigiRite V 2.2.2.11 - built by AA5AU installed with WriteLog V12.54A.? Its decoding signals just fine but I have a blank waterfall, with one pixel line at the top that is showing signals, what do I have set wrong? Everything else seems to be working, and I used this setup last year for the FTRoundup without problems. Thanks, Gordon - N1MGO From kevin at rowett.org Thu Dec 3 14:55:11 2020 From: kevin at rowett.org (Kevin Rowett) Date: Thu, 3 Dec 2020 11:55:11 -0800 Subject: [WriteLog] FTRoundup, which contest to use? In-Reply-To: <8de752cb-bd98-6b61-64c5-8f78dfe63f19@gmail.com> References: <8de752cb-bd98-6b61-64c5-8f78dfe63f19@gmail.com> Message-ID: RTTY RU. Same rules, as for exchanges, etc. Fix only though, no RTTY. look at http://www.rttycontesting.com/ 73, K6TD > On Dec 3, 2020, at 10:58 AM, Gordon LaPoint wrote: > > I can not see the FT Roundup in the list of contests, which one should I use?? > > Thanks, > > Gordon - N1MGO > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ From aa5au at bellsouth.net Thu Dec 3 15:41:13 2020 From: aa5au at bellsouth.net (Don AA5AU) Date: Thu, 3 Dec 2020 20:41:13 +0000 (UTC) Subject: [WriteLog] FTRoundup, which contest to use? In-Reply-To: <8de752cb-bd98-6b61-64c5-8f78dfe63f19@gmail.com> References: <8de752cb-bd98-6b61-64c5-8f78dfe63f19@gmail.com> Message-ID: <1325382326.3658309.1607028073825@mail.yahoo.com> Use RTTY Roundup module and you'll need DigiRite. You'll need WriteLog 12.52F or later to use the latest version of DigiRite. Find DigiRite here: https://www.rttycontesting.com/downloads/ 73, Don AA5AU On Thursday, December 3, 2020, 12:58:44 PM CST, Gordon LaPoint wrote: I can not see the FT Roundup in the list of contests, which one should I use?? Thanks, Gordon - N1MGO _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ From gordon.lapoint at gmail.com Fri Dec 4 10:58:49 2020 From: gordon.lapoint at gmail.com (Gordon LaPoint) Date: Fri, 4 Dec 2020 10:58:49 -0500 Subject: [WriteLog] [RttyDigital] No signals showing in DigiRite Receive In-Reply-To: <957048022.3831932.1607090276770@mail.yahoo.com> References: <13bcc7cf-d614-9f62-88f7-37df620a463e@gmail.com> <957048022.3831932.1607090276770@mail.yahoo.com> Message-ID: Don, ?? Changed the size of the DigiRite Receive window and the waterfall showed up!! So now I know what to do if it happens again. Gordon - N1MGO On 12/4/2020 8:57 AM, Don AA5AU wrote: > Check your sound card settings in "sound board mixer control" under > the WriteLog program group in the Start menu. > > Don AA5AU > > On Friday, December 4, 2020, 03:28:35 AM CST, Gordon - N1MGO > wrote: > > > I have DigiRite V 2.2.2.11 - built by AA5AU installed with WriteLog > V12.54A.? Its decoding signals just fine but I have a blank waterfall, > with one pixel line at the top that is showing signals, what do I have > set wrong? > > Everything else seems to be working, and I used this setup last year for > the FTRoundup without problems. > > Thanks, > > Gordon - N1MGO > > > > -=-=-=-=-=-=-=-=-=-=-=- > Groups.io Links: You receive all messages sent to this group. > View/Reply Online (#1370): > https://groups.io/g/rttydigital/message/1370 > > Mute This Topic: https://groups.io/mt/78692312/361772 > > Group Owner: rttydigital+owner at groups.io > Unsubscribe: > https://groups.io/g/rttydigital/leave/3491136/344552604/xyzzy > >[aa5au at bellsouth.net ] > -=-=-=-=-=-=-=-=-=-=-=- > > From nrsmith at citlink.net Fri Dec 4 14:20:43 2020 From: nrsmith at citlink.net (Nick Smith) Date: Fri, 4 Dec 2020 13:20:43 -0600 Subject: [WriteLog] No Band Map In-Reply-To: <2a90701d-ae29-7c27-0e7c-aad284962c19@citlink.net> References: <2a90701d-ae29-7c27-0e7c-aad284962c19@citlink.net> Message-ID: No bandmap since installing 12.54A. I have never experienced this in any other update. Telnet skimmer spots are not as I had them set. Nick, W4GKM From aa5au at bellsouth.net Fri Dec 4 14:26:02 2020 From: aa5au at bellsouth.net (Don AA5AU) Date: Fri, 4 Dec 2020 19:26:02 +0000 (UTC) Subject: [WriteLog] No Band Map In-Reply-To: References: <2a90701d-ae29-7c27-0e7c-aad284962c19@citlink.net> Message-ID: <1538741788.3946410.1607109962622@mail.yahoo.com> What exactly do you mean by "No bandmap"? Do you mean the bandmap will not open or do you mean the bandmap opens but it's a blank bandmap? If it's a blank bandmap, and you are running Windows 10, re-install your last update. Windows 10 updates are known to mess up the bandmap. The fix is to re-install the last WriteLog update you have. No need to uninstall anything, just run the update. If the window doesn't open at all, I've not heard of that. Don AA5AU On Friday, December 4, 2020, 01:20:57 PM CST, Nick Smith wrote: ??? ??? ??? ??? No bandmap since installing 12.54A. I have never experienced this in any other update. Telnet skimmer spots are not as I had them set. Nick, W4GKM _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ From aa5au at bellsouth.net Fri Dec 4 14:28:13 2020 From: aa5au at bellsouth.net (Don AA5AU) Date: Fri, 4 Dec 2020 19:28:13 +0000 (UTC) Subject: [WriteLog] No Band Map In-Reply-To: <1538741788.3946410.1607109962622@mail.yahoo.com> References: <2a90701d-ae29-7c27-0e7c-aad284962c19@citlink.net> <1538741788.3946410.1607109962622@mail.yahoo.com> Message-ID: <2047519713.3944939.1607110093251@mail.yahoo.com> Let me clarify something. Do not re-install the Windows 10 update. Reinstall the last WriteLog update you have. Sorry. Don AA5AU On Friday, December 4, 2020, 01:26:14 PM CST, Don AA5AU wrote: What exactly do you mean by "No bandmap"? Do you mean the bandmap will not open or do you mean the bandmap opens but it's a blank bandmap? If it's a blank bandmap, and you are running Windows 10, re-install your last update. Windows 10 updates are known to mess up the bandmap. The fix is to re-install the last WriteLog update you have. No need to uninstall anything, just run the update. If the window doesn't open at all, I've not heard of that. Don AA5AU ? ? On Friday, December 4, 2020, 01:20:57 PM CST, Nick Smith wrote:? ??? ??? ??? ??? No bandmap since installing 12.54A. I have never experienced this in any other update. Telnet skimmer spots are not as I had them set. Nick, W4GKM _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ ? _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ From aa5au at bellsouth.net Fri Dec 4 19:42:43 2020 From: aa5au at bellsouth.net (Don AA5AU) Date: Sat, 5 Dec 2020 00:42:43 +0000 (UTC) Subject: [WriteLog] No Band Map In-Reply-To: <2047519713.3944939.1607110093251@mail.yahoo.com> References: <2a90701d-ae29-7c27-0e7c-aad284962c19@citlink.net> <1538741788.3946410.1607109962622@mail.yahoo.com> <2047519713.3944939.1607110093251@mail.yahoo.com> Message-ID: <1550661721.4037110.1607128963710@mail.yahoo.com> Nick reported directly to me that this fix worked for him. 73, Don AA5AU On Friday, December 4, 2020, 01:32:39 PM CST, Don AA5AU wrote: Let me clarify something. Do not re-install the Windows 10 update. Reinstall the last WriteLog update you have. Sorry. Don AA5AU ? ? On Friday, December 4, 2020, 01:26:14 PM CST, Don AA5AU wrote:? ? What exactly do you mean by "No bandmap"? Do you mean the bandmap will not open or do you mean the bandmap opens but it's a blank bandmap? If it's a blank bandmap, and you are running Windows 10, re-install your last update. Windows 10 updates are known to mess up the bandmap. The fix is to re-install the last WriteLog update you have. No need to uninstall anything, just run the update. If the window doesn't open at all, I've not heard of that. Don AA5AU ? ? On Friday, December 4, 2020, 01:20:57 PM CST, Nick Smith wrote:? ??? ??? ??? ??? No bandmap since installing 12.54A. I have never experienced this in any other update. Telnet skimmer spots are not as I had them set. Nick, W4GKM _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ ? _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ ? _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ From jamie.dupree at verizon.net Sat Dec 5 11:49:14 2020 From: jamie.dupree at verizon.net (Jamie Dupree) Date: Sat, 5 Dec 2020 16:49:14 +0000 (UTC) Subject: [WriteLog] W5XD keyer sidetone References: <316638631.4762112.1607186954864.ref@mail.yahoo.com> Message-ID: <316638631.4762112.1607186954864@mail.yahoo.com> Is there way to turn off, or change the pitch of the W5XD keyer sidetone, by making a change in the .ini file?? Thanks 73 Jamie NS3T From aa5au at bellsouth.net Sun Dec 6 19:21:39 2020 From: aa5au at bellsouth.net (Don AA5AU) Date: Mon, 7 Dec 2020 00:21:39 +0000 (UTC) Subject: [WriteLog] All FT4/FT8 QSOs show as RTTY in ADIF file References: <1701412334.4361015.1607300499880.ref@mail.yahoo.com> Message-ID: <1701412334.4361015.1607300499880@mail.yahoo.com> All the FT4/FT8 QSOs I made in the FT Roundup using the ARRL RTTY Roundup module and DigiRite are showing as RTTY. I'm guess this is not correct. Don AA5AU From aa5au at bellsouth.net Sun Dec 6 19:35:36 2020 From: aa5au at bellsouth.net (Don AA5AU) Date: Mon, 7 Dec 2020 00:35:36 +0000 (UTC) Subject: [WriteLog] All FT4/FT8 QSOs show as RTTY in ADIF file In-Reply-To: <1701412334.4361015.1607300499880@mail.yahoo.com> References: <1701412334.4361015.1607300499880.ref@mail.yahoo.com> <1701412334.4361015.1607300499880@mail.yahoo.com> Message-ID: <1691254984.4361496.1607301336896@mail.yahoo.com> I looked at my 2020 ARRL RTTY Roundup ADIF file and it shows MFSK as the mode for FT4 (apparently I didn't work any FT8 in the ARRL RTTY RU). Something has changed in the logging of FT4 and FT8 contacts for the ARRL RTTY Roundup module. Don AA5AU On Sunday, December 6, 2020, 06:22:41 PM CST, Don AA5AU wrote: All the FT4/FT8 QSOs I made in the FT Roundup using the ARRL RTTY Roundup module and DigiRite are showing as RTTY. I'm guess this is not correct. Don AA5AU _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ From aa5au at bellsouth.net Sun Dec 6 19:39:08 2020 From: aa5au at bellsouth.net (Don AA5AU) Date: Mon, 7 Dec 2020 00:39:08 +0000 (UTC) Subject: [WriteLog] All FT4/FT8 QSOs show as RTTY in ADIF file In-Reply-To: <1691254984.4361496.1607301336896@mail.yahoo.com> References: <1701412334.4361015.1607300499880.ref@mail.yahoo.com> <1701412334.4361015.1607300499880@mail.yahoo.com> <1691254984.4361496.1607301336896@mail.yahoo.com> Message-ID: <108236144.4359204.1607301548981@mail.yahoo.com> In addition, the Cabrillo file is wrong too. It shows all QSOs as RY instead of DG. Don AA5AU On Sunday, December 6, 2020, 06:35:43 PM CST, Don AA5AU wrote: I looked at my 2020 ARRL RTTY Roundup ADIF file and it shows MFSK as the mode for FT4 (apparently I didn't work any FT8 in the ARRL RTTY RU). Something has changed in the logging of FT4 and FT8 contacts for the ARRL RTTY Roundup module. Don AA5AU ? ? On Sunday, December 6, 2020, 06:22:41 PM CST, Don AA5AU wrote:? All the FT4/FT8 QSOs I made in the FT Roundup using the ARRL RTTY Roundup module and DigiRite are showing as RTTY. I'm guess this is not correct. Don AA5AU _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ ? _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ From rgarrett5 at comcast.net Sun Dec 6 20:36:17 2020 From: rgarrett5 at comcast.net (Robert Garrett) Date: Sun, 6 Dec 2020 20:36:17 -0500 Subject: [WriteLog] ARRL CW Module Message-ID: <003c01d6cc39$5c706400$15512c00$@comcast.net> Hello Wayne et al, Ok, I have a hopefully simple dilemma using WriteLog that I truly hope can be corrected. First, I'm a blind ham and have been active for 52 years. I have used WL for a very long time. I have attempted to use N1MM but it doesn't identify "DUPES" in a manner that I can detect using a screen reader. So WL is my software of choice. Now the problem. With at least the ARRL 160 CW contest module, it is possible to type in a callsign, hit the spacebar which moves you to the SEC field, and if you accidentally use the right arrow key, you can fill in the SEC hit enter and WL accepts the contact. The big problem is if you don't put the first letter of say EPA in the correct spot, WL will take it but not record it. You can imagine my dismay after the contest when I realized that my score was reduced from 1102 Q's to 1084 because I didn't have all of those sections place in the right position in the SEC field. Would it be that difficult for WL to let us know that the sec wasn't recorded? It sure happens in the CQWW module. If you fail to put in a Zone or forget to tap the spacebar to move to the Zone field, you won't be able to input the info. I hope this is a simple fix that will be a tremendous help to me, any other blind OPS and probably the general contesting community. TNX for indulging my issue. 73, Bob K3UL From k5zd at outlook.com Sun Dec 6 22:12:30 2020 From: k5zd at outlook.com (Randy Thompson) Date: Mon, 7 Dec 2020 03:12:30 +0000 Subject: [WriteLog] ARRL CW Module In-Reply-To: <003c01d6cc39$5c706400$15512c00$@comcast.net> References: <003c01d6cc39$5c706400$15512c00$@comcast.net> Message-ID: This is a good request. I can see and I made this mistake more than once. I suspect the challenge is that for DX contact, there is no exchange other than RST. So WL would have to look at the call to know if an empty exchange field was valid or not. Randy K5ZD -----Original Message----- From: WriteLog On Behalf Of Robert Garrett Sent: Sunday, December 6, 2020 8:36 PM To: 'Wayne, W5XD' ; 'Writelog Forum' Subject: [WriteLog] ARRL CW Module Hello Wayne et al, Ok, I have a hopefully simple dilemma using WriteLog that I truly hope can be corrected. First, I'm a blind ham and have been active for 52 years. I have used WL for a very long time. I have attempted to use N1MM but it doesn't identify "DUPES" in a manner that I can detect using a screen reader. So WL is my software of choice. Now the problem. With at least the ARRL 160 CW contest module, it is possible to type in a callsign, hit the spacebar which moves you to the SEC field, and if you accidentally use the right arrow key, you can fill in the SEC hit enter and WL accepts the contact. The big problem is if you don't put the first letter of say EPA in the correct spot, WL will take it but not record it. You can imagine my dismay after the contest when I realized that my score was reduced from 1102 Q's to 1084 because I didn't have all of those sections place in the right position in the SEC field. Would it be that difficult for WL to let us know that the sec wasn't recorded? It sure happens in the CQWW module. If you fail to put in a Zone or forget to tap the spacebar to move to the Zone field, you won't be able to input the info. I hope this is a simple fix that will be a tremendous help to me, any other blind OPS and probably the general contesting community. TNX for indulging my issue. 73, Bob K3UL _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web: http://www.writelog.com/ From aa5au at bellsouth.net Sun Dec 6 22:47:40 2020 From: aa5au at bellsouth.net (Don AA5AU) Date: Mon, 7 Dec 2020 03:47:40 +0000 (UTC) Subject: [WriteLog] All FT4/FT8 QSOs show as RTTY in ADIF file In-Reply-To: <108236144.4359204.1607301548981@mail.yahoo.com> References: <1701412334.4361015.1607300499880.ref@mail.yahoo.com> <1701412334.4361015.1607300499880@mail.yahoo.com> <1691254984.4361496.1607301336896@mail.yahoo.com> <108236144.4359204.1607301548981@mail.yahoo.com> Message-ID: <1066779262.4388045.1607312860010@mail.yahoo.com> I was using a beta version of WL (10.55G). Randy, K5ZD, reports that 10.55E reported the correct mode. Don AA5AU On Sunday, December 6, 2020, 06:39:19 PM CST, Don AA5AU wrote: In addition, the Cabrillo file is wrong too. It shows all QSOs as RY instead of DG. Don AA5AU ? ? On Sunday, December 6, 2020, 06:35:43 PM CST, Don AA5AU wrote:? ? I looked at my 2020 ARRL RTTY Roundup ADIF file and it shows MFSK as the mode for FT4 (apparently I didn't work any FT8 in the ARRL RTTY RU). Something has changed in the logging of FT4 and FT8 contacts for the ARRL RTTY Roundup module. Don AA5AU ? ? On Sunday, December 6, 2020, 06:22:41 PM CST, Don AA5AU wrote:? All the FT4/FT8 QSOs I made in the FT Roundup using the ARRL RTTY Roundup module and DigiRite are showing as RTTY. I'm guess this is not correct. Don AA5AU _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ ? _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ ? _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web:? http://www.writelog.com/ From ed at w0yk.com Sun Dec 6 23:09:26 2020 From: ed at w0yk.com (Ed W0YK) Date: Sun, 06 Dec 2020 20:09:26 -0800 Subject: [WriteLog] All FT4/FT8 QSOs show as RTTY in ADIF file In-Reply-To: <1066779262.4388045.1607312860010@mail.yahoo.com> Message-ID: I used WriteLog 12.55G and the Cabrillo mode was DG in the QSO lines.73,Ed W0YK -------- Original message --------From: Don AA5AU Date: 12/6/20 19:48 (GMT-08:00) To: WriteLog Reflector Subject: Re: [WriteLog] All FT4/FT8 QSOs show as RTTY in ADIF file I was using a beta version of WL (10.55G). Randy, K5ZD, reports that 10.55E reported the correct mode.Don AA5AU??? On Sunday, December 6, 2020, 06:39:19 PM CST, Don AA5AU wrote:? ? In addition, the Cabrillo file is wrong too. It shows all QSOs as RY instead of DG.Don AA5AU? ? On Sunday, December 6, 2020, 06:35:43 PM CST, Don AA5AU wrote:? ? I looked at my 2020 ARRL RTTY Roundup ADIF file and it shows MFSK as the mode for FT4 (apparently I didn't work any FT8 in the ARRL RTTY RU).Something has changed in the logging of FT4 and FT8 contacts for the ARRL RTTY Roundup module.Don AA5AU? ? On Sunday, December 6, 2020, 06:22:41 PM CST, Don AA5AU wrote:? All the FT4/FT8 QSOs I made in the FT Roundup using the ARRL RTTY Roundup module and DigiRite are showing as RTTY. I'm guess this is not correct.Don AA5AU_______________________________________________WriteLog mailing listWriteLog at contesting.comhttp://lists.contesting.com/mailman/listinfo/writelogWriteLog on the web:? http://www.writelog.com/? _______________________________________________WriteLog mailing listWriteLog at contesting.comhttp://lists.contesting.com/mailman/listinfo/writelogWriteLog on the web:? http://www.writelog.com/? _______________________________________________WriteLog mailing listWriteLog at contesting.comhttp://lists.contesting.com/mailman/listinfo/writelogWriteLog on the web:? http://www.writelog.com/? _______________________________________________WriteLog mailing listWriteLog at contesting.comhttp://lists.contesting.com/mailman/listinfo/writelogWriteLog on the web:? http://www.writelog.com/ From ad6e at arrl.net Mon Dec 7 14:03:29 2020 From: ad6e at arrl.net (Alan Maenchen) Date: Mon, 7 Dec 2020 09:03:29 -1000 Subject: [WriteLog] WriteLog Digest, Vol 216, Issue 6 In-Reply-To: References: Message-ID: Evidently only Don, AA5AU and myself have this problem. Don is trying to figure this out. Did anyone else find this problem? That is, using the WL RTTY RU module, QSOs are logged normally except the DGTL field is blank. When the file is output to ADIF or Cabrillo, the mode shows RTTY / RY. I used WL 12.53E and DigiRite 2.2.2.11 Don is using WL 12.55G and DigiRite 2.2.2.11 (same as Ed below) 73, Alan AD6E / KH6TU > > Message: 1 > Date: Sun, 06 Dec 2020 20:09:26 -0800 > From: Ed W0YK > To: Don AA5AU , WriteLog Reflector > > Subject: Re: [WriteLog] All FT4/FT8 QSOs show as RTTY in ADIF file > Message-ID: > Content-Type: text/plain; charset=utf-8 > > I used WriteLog 12.55G and the Cabrillo mode was DG in the QSO lines.73,Ed > W0YK > > _ > From nn5t at attglobal.net Mon Dec 7 15:07:37 2020 From: nn5t at attglobal.net (Jon Suehiro) Date: Mon, 7 Dec 2020 20:07:37 -0000 Subject: [WriteLog] WriteLog Digest, Vol 216, Issue 6 In-Reply-To: References: Message-ID: <000b01d6ccd4$9cff5300$d6fdf900$@attglobal.net> For your reference - I am OK case, the first is the actual WL session (SEQ 1 ~ 3 in FT4 and 20 ~ 22 in FT8), then 'Export Copy As...' in ADIF, then Cabrillo sent. BTW, thanks everyone for the QSO. 73 de Jon NN5T WL 12.54A / DigiRite 2.2.2.11 built by - AA5UU (X86 built), TS890 through microHAM DIGI KEYER II SEQ DATE TIME FREQ CALL SNT RCV QTH ML COUNTRY C PREF TIME-OFF DGTL 1 2020-12-05 1901 21080 K7STO 569 599 WA 1 United States K FT4 2 1902 21080 W7VXS 579 599 WA United States K FT4 3 1903 21080 W7PSK 579 569 WA United States K FT4 ---------- 20 1920 21090 W6ZQ 539 569 AZ 11 United States K FT8 21 1921 21090 CX7SS 549 559 0050 12 Uruguay CX FT8 22 1922 21090 PU2USK 559 559 0015 Brazil PY FT8 ADIF by WriteLog WriteLog 12.54A 20201205 190149 21.08000 15m 1 MFSK FT4 K7STO 569 599 WA WA 1 United States K FT4 20201205 190234 21.08000 15m 2 MFSK FT4 W7VXS 579 599 WA WA United States K FT4 20201205 190318 21.08000 15m 3 MFSK FT4 W7PSK 579 569 WA WA United States K FT4 ---------- 20201205 192053 21.09000 15m 20 FT8 W6ZQ 539 569 AZ AZ 11 United States K FT8 20201205 192151 21.09000 15m 21 FT8 CX7SS 549 559 0050 12 Uruguay CX FT8 20201205 192253 21.09000 15m 22 FT8 PU2USK 559 559 0015 Brazil PY FT8 START-OF-LOG: 3.0 LOCATION: NTX CALLSIGN: NN5T CATEGORY-OPERATOR: SINGLE-OP CATEGORY-ASSISTED: ASSISTED CATEGORY-BAND: ALL CATEGORY-POWER: LOW CATEGORY-MODE: FT CATEGORY-STATION: FIXED CATEGORY-TRANSMITTER: ONE CLAIMED-SCORE: 32153 CLUB: North Texas Contest Club CONTEST: FT Roundup CREATED-BY: WriteLog V12.54A NAME: Jon Suehiro ADDRESS: 6932 Hunters Ridge Drive ADDRESS-CITY: Dallas ADDRESS-STATE-PROVINCE: TX ADDRESS-POSTALCODE: 75248 ADDRESS-COUNTRY: USA EMAIL: nn5t at arrl.net OPERATORS: NN5T SOAPBOX: QSO: 21080 DG 2020-12-05 1901 NN5T 569 TX K7STO 599 WA QSO: 21080 DG 2020-12-05 1902 NN5T 579 TX W7VXS 599 WA QSO: 21080 DG 2020-12-05 1903 NN5T 579 TX W7PSK 569 WA ---------- QSO: 21090 DG 2020-12-05 1920 NN5T 539 TX W6ZQ 569 AZ QSO: 21090 DG 2020-12-05 1921 NN5T 549 TX CX7SS 559 0050 QSO: 21090 DG 2020-12-05 1922 NN5T 559 TX PU2USK 559 0015 -----Original Message----- From: WriteLog On Behalf Of Alan Maenchen Sent: December 7, 2020 19:03 To: WriteLog Reflector Subject: Re: [WriteLog] WriteLog Digest, Vol 216, Issue 6 Evidently only Don, AA5AU and myself have this problem. Don is trying to figure this out. Did anyone else find this problem? That is, using the WL RTTY RU module, QSOs are logged normally except the DGTL field is blank. When the file is output to ADIF or Cabrillo, the mode shows RTTY / RY. I used WL 12.53E and DigiRite 2.2.2.11 Don is using WL 12.55G and DigiRite 2.2.2.11 (same as Ed below) 73, Alan AD6E / KH6TU > > Message: 1 > Date: Sun, 06 Dec 2020 20:09:26 -0800 > From: Ed W0YK > To: Don AA5AU , WriteLog Reflector > > Subject: Re: [WriteLog] All FT4/FT8 QSOs show as RTTY in ADIF file > Message-ID: > Content-Type: text/plain; charset=utf-8 > > I used WriteLog 12.55G and the Cabrillo mode was DG in the QSO > lines.73,Ed W0YK > > _ > _______________________________________________ WriteLog mailing list mailto:WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web: http://www.writelog.com/ From k0cf.craig at gmail.com Tue Dec 8 11:13:50 2020 From: k0cf.craig at gmail.com (k0cf-Craig) Date: Tue, 8 Dec 2020 10:13:50 -0600 Subject: [WriteLog] WriteLog ARRL 10M Contest prefill file Message-ID: I have just generated a WriteLog ADIF prefill file for the ARRL 10M contest and posted it to my club website, the Eastern Iowa DX Association. This link takes you directly to the Prefill section: < https://tinyurl.com/WLprefills > What you will download is a zip file containing the ADIF prefill file, which has the file extension ".adi". The source for this was the file ARRL10M.txt from the N1MM+ website, last updated Dec 7, 2020. After unzipping the ADIF file, start WriteLog and start a new log for the selected contest. Open the WriteLog "Tools" menu and select ?Preset Exchange from ADI file??, browse to the location of your ADIF file and load it. To test it, type a callsign from the ADIF file into the callsign field, press "space" or "tab" to leave that field upon which the received exchange field(s) should automatically fill with data from the prefill file. As always, the accuracy of the data in this file cannot be guaranteed; treat it as a "suggestion" and be sure to log what your QSO partner sends! 73, Craig, K0CF From gordon.lapoint at gmail.com Tue Dec 8 16:44:09 2020 From: gordon.lapoint at gmail.com (Gordon LaPoint) Date: Tue, 8 Dec 2020 16:44:09 -0500 Subject: [WriteLog] Writelog + DigiRite UPD ? Message-ID: Got this question over on the RTTY Digital group, don't know the answer, does anyone here have the answer?? Thanks, Gordon - N1MGO Hi, Currently i use N1MM++ for contesting and DXLabs for daily use. My station is band switching automated by listening UDP packets send by N1MM++ and DXLabs. https://n1mmwp.hamdocs.com/appendices/external-udp-broadcasts/#radio-info Thinking to switch to WriteLog for contesting and my questions is: Can WriteLog send this type or similar frequency information over the network? -- 73 de Stefan / AF6SA www.af6sa.com From support at writelog.com Wed Dec 9 10:14:35 2020 From: support at writelog.com (Wayne) Date: Wed, 9 Dec 2020 07:14:35 -0800 Subject: [WriteLog] ARRL 160m CW Module Message-ID: > With at least the ARRL 160 CW contest module, it is > possible to type in a callsign, hit the spacebar which moves you to the SEC > field, and if you accidentally use the right arrow key, you can fill in the > SEC hit enter and WL accepts the contact. The big problem is if you don't > put the first letter of say EPA in the correct spot, WL will take it but not > record it. You can change this behavior using WriteLog's menu item Contest/Exchange-Format-Setup. In the left most column (labeled "Exchange Fields") click on the "SECT" entry. The "Required" check box by default is OFF. Click it ON. Then OK. File/Save to keep this change for the next time you open this .wl file. That module is old enough I cannot remember why the default for that check box is OFF. It feels like it should be ON. But the default is OFF for all recent versions of WriteLog, which means you must go through the above procedure after every File/New to create an ARRL 160m log. Wayne From k5zd at outlook.com Wed Dec 9 10:52:14 2020 From: k5zd at outlook.com (Randy Thompson) Date: Wed, 9 Dec 2020 15:52:14 +0000 Subject: [WriteLog] ARRL 160m CW Module In-Reply-To: References: Message-ID: The 160 contest does not require an exchange for DX stations. WL won't let you enter anything that is not a recognized section name. So you end up leaving the exchange field blank for DX. I suspect this is the reason the 160 contest defaults this way. If you set it to required, you would have trouble logging DX stations. Randy K5ZD -----Original Message----- From: WriteLog On Behalf Of Wayne Sent: Wednesday, December 9, 2020 10:15 AM To: Writelog Forum Subject: [WriteLog] ARRL 160m CW Module > With at least the ARRL 160 CW contest module, it is possible to type > in a callsign, hit the spacebar which moves you to the SEC field, and > if you accidentally use the right arrow key, you can fill in the SEC > hit enter and WL accepts the contact. The big problem is if you don't > put the first letter of say EPA in the correct spot, WL will take it > but not record it. You can change this behavior using WriteLog's menu item Contest/Exchange-Format-Setup. In the left most column (labeled "Exchange Fields") click on the "SECT" entry. The "Required" check box by default is OFF. Click it ON. Then OK. File/Save to keep this change for the next time you open this .wl file. That module is old enough I cannot remember why the default for that check box is OFF. It feels like it should be ON. But the default is OFF for all recent versions of WriteLog, which means you must go through the above procedure after every File/New to create an ARRL 160m log. Wayne _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web: http://www.writelog.com/ From support at writelog.com Wed Dec 9 13:15:47 2020 From: support at writelog.com (Wayne) Date: Wed, 9 Dec 2020 10:15:47 -0800 Subject: [WriteLog] Writelog + DigiRite UPD ? Message-ID: <133baeeb-ce98-f6d1-e6dc-8031d7c44df0@writelog.com> > Hi, > Currently i use N1MM++ for contesting and DXLabs for daily use. > My station is band switching automated by listening UDP > packets send by N1MM++ and DXLabs. > https://n1mmwp.hamdocs.com/appendices/external-udp-broadcasts/#radio-info > > > > > Thinking to switch to WriteLog for contesting and my questions is: > Can WriteLog send this type or similar frequency information over the > network? This might be of interest: ??? https://github.com/w5xd/WlRigRepeater The link is to the archive for an open source application does something similar to, but not identical to the N1MM link. Wayne From john at kk9a.com Wed Dec 9 13:25:48 2020 From: john at kk9a.com (john at kk9a.com) Date: Wed, 09 Dec 2020 12:25:48 -0600 Subject: [WriteLog] ARRL 160m CW Module Message-ID: <20201209122548.Horde.UPq4ZPeBnkAjGyh6sN69ovh@www11.qth.com> I have never played much with Writelog's exchange fields except for eliminating unnecessary fields so I found Wayne's post on its other settings interesting. For the ARRL 160m contest you could set the field to require an entry and then create a section multiplier called DX so you have something to enter when you work DX. I assume that the majority of stations worked have actual sections so this would not add much typing over the contest. Then you would have to delete "DX" text from the cabrillo file. Perhaps just using an alias section mult "DX= " would create a cabrillo file not needing editing. John KK9A Randy Thompson K5ZD wrote: The 160 contest does not require an exchange for DX stations. WL won't let you enter anything that is not a recognized section name. So you end up leaving the exchange field blank for DX. I suspect this is the reason the 160 contest defaults this way. If you set it to required, you would have trouble logging DX stations. Randy K5ZD From gordon.lapoint at gmail.com Wed Dec 9 15:31:26 2020 From: gordon.lapoint at gmail.com (Gordon LaPoint) Date: Wed, 9 Dec 2020 15:31:26 -0500 Subject: [WriteLog] Writelog + DigiRite UPD ? In-Reply-To: <133baeeb-ce98-f6d1-e6dc-8031d7c44df0@writelog.com> References: <133baeeb-ce98-f6d1-e6dc-8031d7c44df0@writelog.com> Message-ID: Wayne, ?? Thanks, I will take a look. Gordon - N1MGO On 12/9/2020 13:15 PM, Wayne wrote: >> Hi, >> Currently i use N1MM++ for contesting and DXLabs for daily use. >> My station is band switching automated by listening UDP >> packets send by N1MM++ and DXLabs. >> https://n1mmwp.hamdocs.com/appendices/external-udp-broadcasts/#radio-info >> >> > > >> >> Thinking to switch to WriteLog for contesting and my questions is: >> Can WriteLog send this type or similar frequency information over the >> network? > This might be of interest: > > ??? https://github.com/w5xd/WlRigRepeater > > The link is to the archive for an open source application does > something similar to, but not identical to the N1MM link. > > Wayne > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web:? http://www.writelog.com/ From jamie.dupree at verizon.net Thu Dec 10 08:13:41 2020 From: jamie.dupree at verizon.net (Jamie Dupree) Date: Thu, 10 Dec 2020 13:13:41 +0000 (UTC) Subject: [WriteLog] Sound board issue References: <293658962.6577543.1607606021325.ref@mail.yahoo.com> Message-ID: <293658962.6577543.1607606021325@mail.yahoo.com> Since the Windows10 update just before Thanksgiving, I've been having a recurring WL problem, which forces me to close out the program, and sometimes re-start the computer, which is somewhat inconvenient during a contest. WL will work fine for multiple hours, and then suddenly give me an error message: Failed to create sound board object: 0, 0x800700a4 WL will then refuse to send any recorded voice files.? It unchecks the box for "Enable Receiver Listen Loop" and acts like I don't have recorded .wav files on my shack hard drive. I know that troubleshooting our respective computers is totally hit and miss, but does anyone have an idea?? Google searches have not produced very much. Thanks. 73 Jamie NS3T From support at writelog.com Thu Dec 10 09:48:04 2020 From: support at writelog.com (Wayne) Date: Thu, 10 Dec 2020 06:48:04 -0800 Subject: [WriteLog] ARRL 160m CW Module Message-ID: > I have never played much with Writelog's exchange fields except for > eliminating unnecessary fields so I found Wayne's post on its other > settings interesting. For the ARRL 160m contest you could set the > field to require an entry and then create a section multiplier called > DX so you have something to enter when you work DX. I assume that the > majority of stations worked have actual sections so this would not add > much typing over the contest. Then you would have to delete "DX" text > from the cabrillo file. Perhaps just using an alias section mult "DX= > " would create a cabrillo file not needing editing. > John KK9A > > > Randy Thompson K5ZD wrote: > > The 160 contest does not require an exchange for DX stations. WL won't > let you enter anything that is not a recognized section name. So you > end up leaving the exchange field blank for DX. I suspect this is the > reason the 160 contest defaults this way. If you set it to required, > you would have trouble logging DX stations. > Randy K5ZD My suggestion remains as I previously posted. > You can change this behavior using WriteLog's menu item > Contest/Exchange-Format-Setup. In the left most column (labeled > "Exchange Fields") click on the "SECT" entry. The "Required" check box > by default is OFF. Click it ON. > > Then OK. > > File/Save to keep this change for the next time you open this .wl file. Anyone that follows my suggestion as written will get the results requested by the original posting. There are lots of ifs/ands and buts that can be considered, but I am quite sure that, of the postings quoted above, only my own has actually been tested on a running version of WriteLog. (I make this claim because I did the testing.) Wayne From marsh at ka5m.net Thu Dec 10 12:23:58 2020 From: marsh at ka5m.net (marsh at ka5m.net) Date: Thu, 10 Dec 2020 11:23:58 -0600 Subject: [WriteLog] ARRL 160m CW Module In-Reply-To: References: Message-ID: <000201d6cf19$3f3135d0$bd93a170$@ka5m.net> Just sayin'.... (Running Window Pro 64-bit Version 1909 and WriteLog Version 12.54A) For the ARRL 160M contest, I followed Wayne's instructions below to add "required" to SECT in the QSO Entry Window. I tested US and Canada callsigns, and all required I enter a valid Section to log the QSO Then I tested various DX callsigns and WriteLog would log them correctly WITHOUT an entry in SECT. 73, Marsh, KA5M -----Original Message----- From: WriteLog On Behalf Of Wayne Sent: Thursday, December 10, 2020 8:48 AM To: Writelog Forum Subject: [WriteLog] ARRL 160m CW Module > Randy Thompson K5ZD wrote: > > The 160 contest does not require an exchange for DX stations. WL won't > let you enter anything that is not a recognized section name. So you > end up leaving the exchange field blank for DX. I suspect this is the > reason the 160 contest defaults this way. If you set it to required, > you would have trouble logging DX stations. > Randy K5ZD My suggestion remains as I previously posted. > You can change this behavior using WriteLog's menu item > Contest/Exchange-Format-Setup. In the left most column (labeled > "Exchange Fields") click on the "SECT" entry. The "Required" check box > by default is OFF. Click it ON. > > Then OK. > > File/Save to keep this change for the next time you open this .wl file. Anyone that follows my suggestion as written will get the results requested by the original posting. There are lots of ifs/ands and buts that can be considered, but I am quite sure that, of the postings quoted above, only my own has actually been tested on a running version of WriteLog. (I make this claim because I did the testing.) Wayne _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web: http://www.writelog.com/ From john at kk9a.com Fri Dec 11 13:09:42 2020 From: john at kk9a.com (john at kk9a.com) Date: Fri, 11 Dec 2020 12:09:42 -0600 Subject: [WriteLog] ARRL 160m CW Module Message-ID: <20201211120942.Horde.nXDVTxG4uW5hKXG32UXDB3T@www11.qth.com> I have not operated the ARRL 160m contest in a long long time. I just tried Wayne's suggestion in my older version of Writelog. Changing SECT to "Field is required for entry in log" does still allow DX stations to have no field entry. This was not clear to me in Wayne's initial post. US/VE will require a field entry to log the QSO after this change is made. John KK9A. [WriteLog] ARRL 160m CW Module Wayne support wrote: > I have never played much with Writelog's exchange fields except for > eliminating unnecessary fields so I found Wayne's post on its other > settings interesting. For the ARRL 160m contest you could set the > field to require an entry and then create a section multiplier > called DX so you have something to enter when you work DX. I assume > that the majority of stations worked have actual sections so this > would not add much typing over the contest. Then you would have to > delete "DX" text from the cabrillo file. Perhaps just using an alias > section mult "DX= " would create a cabrillo file not needing editing. > John KK9A > > > Randy Thompson K5ZD wrote: > > The 160 contest does not require an exchange for DX stations. WL > won't let you enter anything that is not a recognized section name. > So you end up leaving the exchange field blank for DX. I suspect > this is the reason the 160 contest defaults this way. If you set it > to required, you would have trouble logging DX stations. > Randy K5ZD My suggestion remains as I previously posted. Anyone that follows my suggestion as written will get the results requested by the original posting. There are lots of ifs/ands and buts that can be considered, but I am quite sure that, of the postings quoted above, only my own has actually been tested on a running version of WriteLog. (I make this claim because I did the testing.) Wayne From jjreisert at alum.mit.edu Fri Dec 11 20:46:58 2020 From: jjreisert at alum.mit.edu (Jim Reisert AD1C) Date: Fri, 11 Dec 2020 18:46:58 -0700 Subject: [WriteLog] CTY-3021 Country Files - 12 December 2020 Message-ID: The Country (CTY) Files were updated on 12 December 2020: https://www.country-files.com/cty-3021-12-december-2020/ For installation instructions, start at: https://www.country-files.com/ Hover your mouse over the word Contest in the menu, then select the software you are using. To install the file, follow the link to your software at the top of the page. If you are interested in a bigger CTY.DAT for everyday logging, you can get it here: https://www.country-files.com/big-cty-12-december-2020/ Note that the release notes (and Version Entity) for this larger file are different than what is shown below. There is a separate link to them. As a reminder, there is an RSS feed of the latest country file announcements: https://www.country-files.com/feed/ Here are the release notes: 12 December 2020 (CTY-3021) VER20201212, Version entity is St. Kitts & Nevis, V4 Added/changed Entities/Prefixes/Callsigns: * 3D2AG/P is Rotuma Island, 3D2/r * RI01ANT is Antarctica, CE9 in CQ zone 39, ITU zone 69 * EA1RCI/CVG is Spain, EA * NHS is England, G * GB8LWF is Northern Ireland, GI * GB20YOTA is Wales, GW * IK5TBI/I/CT is Italy, I * JF7MTO/JD1 is Minami Torishima, JD/m * K0AU, K0DTJ, N5MF and NH6Z are all United States, K in CQ zone 3, ITU zone 6 * W2UP is United States, K in CQ zone 4, ITU zone 7 * AB4EJ, KM4RO, N4HAI, NU4N and W4JSI are all United States, K in CQ zone 4, ITU zone 8 * K8SYH, KD9QS, KI8I, N0YY, N6YMM, N8KH and W0CN are all United States, K in CQ zone 5, ITU zone 8 * KB3UWV, KB3UWW, KC8KPX, KD4NFW, KG6EZW, KJ6MQL, KK6DIT, KM4FPS, N6OM and W4AJM are all Hawaii, KH6 * KF6ILC, KF7MVM, KK4BAN, N6IGV, NC2US and WB7ULO are all Alaska, KL * LQ4D/D, LU1HYW/H, LU1IG/I, LU2JS/J, LU3DRP/D, LU3EEA/I, LU3HN/H, LU3HT/H, LU4GF/GA, LU4JJ/J, LU4LG/L, LU5JU/J, LU5LA/L, LU5QR/Q, LU7CC/E, LU7DZV/D, LU7EHR/E, LU7FMA/F and LU8AJM/D are all Argentina, LU * AZ1A/X and LU1VZ/V are both Argentina, LU in ITU zone 16 * R120AN, R30MCHS, R9JBH/7, R9OM/6 and RM41MB are all European Russia, UA * R8MB/1, RA1WS/1, RA3X/1 and RV1CC/1 are all European Russia, UA in CQ zone 17, ITU zone 20 * R8FF/8, RX6DL/8/P and RZ5D/9 are all Asiatic Russia, UA9 * RK4PA/9 and RV1CC/P are both Asiatic Russia, UA9 in ITU zone 20 * R30ARCK is Asiatic Russia, UA9 in CQ zone 18, ITU zone 32 Removed Entities/Prefixes/Callsigns: * IQ6KX/9 in Sicily, *IT9 * 9M4CRB and 9M4JAY in East Malaysia, 9M6 * EA5URE/P in Spain, EA * EA2EJO/8 in Canary Islands, EA8 * TO10CWO in Guadeloupe, FG * 2E0CVN/NHS in England, G * GB0CSG, GB0SJR and GB2SBS in Scotland, GM * AL4B, K4AVX, K6BFL, K8PO, K9JF, KL2RA, KL4CZ, KX4X, W6DVS, WB5WAJ and WB8BPU in United States, K * KG4NE in Guantanamo Bay, KG4 * AA1AB in Mariana Islands, KH0 * K6HNL and KM6UVP in Hawaii, KH6 * AI7CF, K7VRK, KD9QKS, KF7FLL, KF7FLM, KF7KTH, N7CGC and W2KRZ in Alaska, KL * KM4ZWY in Puerto Rico, KP4 * LU1HB/J, LU4AA/D and LU4AA/X in Argentina, LU * LX9S/J in Luxembourg, LX * PE1BOJ/J in Netherlands, PA * SV2JAO/J in Greece, SV * R0AI/3, R125SE, R450AKSU, R450STAR, R500LWTK, R7AB/P, RC8C/6, RN2FA/3, RU9CK/7 and UA9CSA/1 in European Russia, UA * RN1M/P in Kaliningrad, UA2 * R05SOTA, R0WA/P, R1FW/0, R8MZ/9, RA4RU/9, RN1CR/0 and RX6DL/8 in Asiatic Russia, UA9 73 - Jim AD1C -- Jim Reisert AD1C, , https://www.ad1c.us From jjreisert at alum.mit.edu Sat Dec 12 13:07:43 2020 From: jjreisert at alum.mit.edu (Jim Reisert AD1C) Date: Sat, 12 Dec 2020 11:07:43 -0700 Subject: [WriteLog] Band map won't stay docked to main window Message-ID: Last night I operated a bit of the ARRL 10m contest, and all was fine. This morning when I started WriteLog, the Band Map was a small square in the upper-left corner of my left monitor, not docked to the main window on my right monitor. I've redocked and re-started, but I can't make it stay. How do I fix this? -- Jim Reisert AD1C, , https://www.ad1c.us From jjreisert at alum.mit.edu Sat Dec 12 17:18:11 2020 From: jjreisert at alum.mit.edu (Jim Reisert AD1C) Date: Sat, 12 Dec 2020 15:18:11 -0700 Subject: [WriteLog] Band map won't stay docked to main window In-Reply-To: References: Message-ID: > This morning when I started WriteLog, the Band Map was a small square > in the upper-left corner of my left monitor, not docked to the main > window on my right monitor. I've redocked and re-started, but I can't > make it stay. How do I fix this? This is very strange. I shut down WriteLog but not the computer, then ran did errands for a couple of hours. When I got back, I started WriteLog. The Band Map was docked again! I had to quit to help someone on FT8, then when I re-started Write Log, the Band Map was undocked again. Something very weird is going on! This is 12.55D (beta release) Apparently 12.55G has been released, I'll try that one. -- Jim Reisert AD1C, , https://www.ad1c.us From dkarg at ekarg.com Sun Dec 13 11:20:29 2020 From: dkarg at ekarg.com (Dan) Date: Sun, 13 Dec 2020 10:20:29 -0600 Subject: [WriteLog] Band map won't stay docked to main window In-Reply-To: References: Message-ID: <5fd63f4d.1c69fb81.49fa7.bf12@mx.google.com> I noticed the same behavior in the last few weeks. I didn?t investigate further. That was with 12.54A Dan From: Jim Reisert AD1C Sent: Saturday, December 12, 2020 12:08 To: WriteLog Subject: [WriteLog] Band map won't stay docked to main window L From jjreisert at alum.mit.edu Sun Dec 13 19:07:49 2020 From: jjreisert at alum.mit.edu (Jim Reisert AD1C) Date: Sun, 13 Dec 2020 17:07:49 -0700 Subject: [WriteLog] Band map won't stay docked to main window In-Reply-To: <5fd63f4d.1c69fb81.49fa7.bf12@mx.google.com> References: <5fd63f4d.1c69fb81.49fa7.bf12@mx.google.com> Message-ID: And today, after taking a long break and starting Write Log, the Band Map was docked again. Dan, I'm glad I'm not the only one! On Sun, Dec 13, 2020 at 9:20 AM Dan wrote: > I noticed the same behavior in the last few weeks. I didn?t investigate > further. > That was with 12.54A > > Dan > > From: Jim Reisert AD1C > Sent: Saturday, December 12, 2020 12:08 > To: WriteLog > Subject: [WriteLog] Band map won't stay docked to main window > > L > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ > -- Jim Reisert AD1C, , https://www.ad1c.us From steve at n9oh.com Mon Dec 14 09:22:29 2020 From: steve at n9oh.com (Steve Woodruff) Date: Mon, 14 Dec 2020 09:22:29 -0500 Subject: [WriteLog] WriteLog 12.55 now available Message-ID: <16c3bcf8-c7fd-4729-a8dd-dd5fc1f02e51@www.fastmail.com> Hi Folks, WriteLog version 12.55 is a free upgrade for anyone who has purchased the full version of WriteLog since December 2019. If you are running an earlier version, go here to purchase a new registration code: http://writelog.com/ordering New in version 12.55 since 12.54: * Support rig-specific macros in f-key messages for Icom. * Better document and fool-proof TX Wave File folder select. * Better error messages on missing .WAV files for certain f-key programming sequences. * Improve ability to customize WAE RTTY QTC fill message. * Update build to use Visual Studio 2019 * Remove RttyRite support for obsolete P38, PCI3000 and PCI4000 TNCs * Add options to Audio Review to playback quad-recorded audio with the TX/RX recorded channels output as Left/Right stereo. * Update TQSL to version 2.5.7 * Remove actions from clicking on displays in Rate Window * Fix failure to honor Kenwood TS-590 DATA mode introduced in 12.50 * A recent Windows update decommissioned WriteLog old method for determining whether it can automate sending an email, which disabled WriteLog?s ability to email. Use a newer method. * Restore Check Call / Properties menu on right click that was lost in previous update. Notice: This release of WriteLog updates it to use the latest version of the widely used Microsoft Visual Studio 2019 components. Because this WriteLog release might bring those components to a newer Microsoft update, it is possible, or even likely, that the WriteLog installer will pop up a box that is not routine in WriteLog updates. This extra popup will indicate that some other, non WriteLog product, is forcing the WriteLog installer to use a reboot to complete its install. This is normal. For more information, read the help file in WriteLog. The upgrade installers are available here: http://writelog.com/downloads/writelog-versions Updating to 12.55 does not automatically update the necessary multiplier files. You must also File/update-data-files in WriteLog to download them. For anyone choosing to run WriteLog without upgrading, you still want to File/update-data-files in WriteLog to get the multiplier updates. Thanks, Steve N9OH & Wayne W5XD From wa1fcn at charter.net Wed Dec 16 18:53:45 2020 From: wa1fcn at charter.net (beaudoin) Date: Wed, 16 Dec 2020 17:53:45 -0600 Subject: [WriteLog] FTdx 5000 low monitor audio Message-ID: <4a91acc2-9b64-be71-ac17-d5324ce54a99@charter.net> ??? GE All ??? ??? Well I was struggling trying to get my new FTDX 5000 mp going on RTTY with Microham ??? ??? ??? Digikeyer 2.? I finally got a semi-local to sked a qso .... It turns out I was ok but what gave me ??? ??? ??? problem is monitor has no audio to listen to.? The local said his is VERY Low.? Is it a setting ??? ??? ??? we need to look at? ??? ??? ??? ??? ??? 73? BoB WA1FCN From lists at subich.com Wed Dec 16 19:33:41 2020 From: lists at subich.com (Joe Subich, W4TV) Date: Wed, 16 Dec 2020 19:33:41 -0500 Subject: [WriteLog] FTdx 5000 low monitor audio In-Reply-To: <4a91acc2-9b64-be71-ac17-d5324ce54a99@charter.net> References: <4a91acc2-9b64-be71-ac17-d5324ce54a99@charter.net> Message-ID: <9452153d-0b94-600d-c973-b9b4475d766e@subich.com> FTdx5000 monitor audio is a function of the transceiver. The FTdX5000 Operating Manual - page 81 only references Monitor in LSB/USB/AM/FM there is no reference as far as I can find to a Monitor function for RTTY/AFSK-based DATA operation. I suggest you contact Yaesu about a "RTTY/Data monitor" capability. DK II does not have a separate "sound card monitor" function. You can connect a *powered speaker* to the u2R Out jack to hear the output of the sound card but that is not a supported configuration. A non- amplified speaker will not work and will result in "hot mic" type operation. 73, ... Joe, W4TV On 2020-12-16 6:53 PM, beaudoin wrote: > > ??? GE All > > ??? ??? Well I was struggling trying to get my new FTDX 5000 mp going > on RTTY with Microham > > ??? ??? ??? Digikeyer 2.? I finally got a semi-local to sked a qso .... > It turns out I was ok but what gave me > > ??? ??? ??? problem is monitor has no audio to listen to.? The local > said his is VERY Low.? Is it a setting > > ??? ??? ??? we need to look at? > > ??? ??? ??? ??? ??? 73? BoB WA1FCN From keith at w3kb.net Wed Dec 16 19:44:32 2020 From: keith at w3kb.net (Keith Beebe W3KB) Date: Thu, 17 Dec 2020 00:44:32 +0000 Subject: [WriteLog] FTdx 5000 low monitor audio In-Reply-To: <9452153d-0b94-600d-c973-b9b4475d766e@subich.com> References: <4a91acc2-9b64-be71-ac17-d5324ce54a99@charter.net> <9452153d-0b94-600d-c973-b9b4475d766e@subich.com> Message-ID: Monitoring works just fine here on my FTDX 5000 on RTTY. The difference may be that I use FSK keying not AFSK. The volume controlled by the Monitor knob sounds very good. Keith W3KB -----Original Message----- From: WriteLog On Behalf Of Joe Subich, W4TV Sent: Wednesday, December 16, 2020 7:34 PM To: writelog at contesting.com Subject: Re: [WriteLog] FTdx 5000 low monitor audio FTdx5000 monitor audio is a function of the transceiver. The FTdX5000 Operating Manual - page 81 only references Monitor in LSB/USB/AM/FM there is no reference as far as I can find to a Monitor function for RTTY/AFSK-based DATA operation. I suggest you contact Yaesu about a "RTTY/Data monitor" capability. DK II does not have a separate "sound card monitor" function. You can connect a *powered speaker* to the u2R Out jack to hear the output of the sound card but that is not a supported configuration. A non- amplified speaker will not work and will result in "hot mic" type operation. 73, ... Joe, W4TV On 2020-12-16 6:53 PM, beaudoin wrote: > > ??? GE All > > ??? ??? Well I was struggling trying to get my new FTDX 5000 mp going > on RTTY with Microham > > ??? ??? ??? Digikeyer 2.? I finally got a semi-local to sked a qso .... > It turns out I was ok but what gave me > > ??? ??? ??? problem is monitor has no audio to listen to.? The local > said his is VERY Low.? Is it a setting > > ??? ??? ??? we need to look at? > > ??? ??? ??? ??? ??? 73? BoB WA1FCN _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web: http://www.writelog.com/ From wa1fcn at charter.net Wed Dec 16 20:40:46 2020 From: wa1fcn at charter.net (beaudoin) Date: Wed, 16 Dec 2020 19:40:46 -0600 Subject: [WriteLog] FTdx 5000 low monitor audio In-Reply-To: References: <4a91acc2-9b64-be71-ac17-d5324ce54a99@charter.net> <9452153d-0b94-600d-c973-b9b4475d766e@subich.com> Message-ID: GE Keith ??? ??? Well FSK is what I use also.? And Joe W4TV Yes I read page 81 and noticed it never mentioned ??? ??? ??? RTTY.? I am about to do some more experimenting now.? I wonder what your interface is ??? ??? Keith ??? If I find any helpful info I will pass it along. ??? ??? ??? ??? BoB WA1FCN On 12/16/2020 6:44 PM, Keith Beebe W3KB wrote: > Monitoring works just fine here on my FTDX 5000 on RTTY. The difference may be that I use FSK keying not AFSK. > > The volume controlled by the Monitor knob sounds very good. > > Keith W3KB > > > > -----Original Message----- > From: WriteLog On Behalf Of Joe Subich, W4TV > Sent: Wednesday, December 16, 2020 7:34 PM > To: writelog at contesting.com > Subject: Re: [WriteLog] FTdx 5000 low monitor audio > > > FTdx5000 monitor audio is a function of the transceiver. The FTdX5000 Operating Manual - page 81 only references Monitor in LSB/USB/AM/FM there is no reference as far as I can find to a Monitor function for > RTTY/AFSK-based DATA operation. I suggest you contact Yaesu about > a "RTTY/Data monitor" capability. > > DK II does not have a separate "sound card monitor" function. You can connect a *powered speaker* to the u2R Out jack to hear the output of the sound card but that is not a supported configuration. A non- amplified speaker will not work and will result in "hot mic" type operation. > > 73, > > ... Joe, W4TV > > > On 2020-12-16 6:53 PM, beaudoin wrote: >> ??? GE All >> >> ??? ??? Well I was struggling trying to get my new FTDX 5000 mp going >> on RTTY with Microham >> >> ??? ??? ??? Digikeyer 2.? I finally got a semi-local to sked a qso .... >> It turns out I was ok but what gave me >> >> ??? ??? ??? problem is monitor has no audio to listen to.? The local >> said his is VERY Low.? Is it a setting >> >> ??? ??? ??? we need to look at? >> >> ??? ??? ??? ??? ??? 73? BoB WA1FCN > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ From keith at w3kb.net Wed Dec 16 20:54:52 2020 From: keith at w3kb.net (Keith Beebe W3KB) Date: Thu, 17 Dec 2020 01:54:52 +0000 Subject: [WriteLog] FTdx 5000 low monitor audio In-Reply-To: References: <4a91acc2-9b64-be71-ac17-d5324ce54a99@charter.net> <9452153d-0b94-600d-c973-b9b4475d766e@subich.com> Message-ID: Mine is a homebrew RTTY interface. Have had it for years on several rigs. Don't know what else to tell you. The audio level using the Monitor volume control on the rig sounds fine here. You must have the MONI switch on and then control the volume via the Moni inner knob of the Moni/Proc volume control on the rig front panel. Keith W3KB -----Original Message----- From: WriteLog On Behalf Of beaudoin Sent: Wednesday, December 16, 2020 8:41 PM To: writelog at contesting.com Subject: Re: [WriteLog] FTdx 5000 low monitor audio GE Keith ??? ??? Well FSK is what I use also.? And Joe W4TV Yes I read page 81 and noticed it never mentioned ??? ??? ??? RTTY.? I am about to do some more experimenting now.? I wonder what your interface is ??? ??? Keith ??? If I find any helpful info I will pass it along. ??? ??? ??? ??? BoB WA1FCN On 12/16/2020 6:44 PM, Keith Beebe W3KB wrote: > Monitoring works just fine here on my FTDX 5000 on RTTY. The difference may be that I use FSK keying not AFSK. > > The volume controlled by the Monitor knob sounds very good. > > Keith W3KB > > > > -----Original Message----- > From: WriteLog On Behalf Of Joe > Subich, W4TV > Sent: Wednesday, December 16, 2020 7:34 PM > To: writelog at contesting.com > Subject: Re: [WriteLog] FTdx 5000 low monitor audio > > > FTdx5000 monitor audio is a function of the transceiver. The FTdX5000 Operating Manual - page 81 only references Monitor in LSB/USB/AM/FM there is no reference as far as I can find to a Monitor function for > RTTY/AFSK-based DATA operation. I suggest you contact Yaesu about > a "RTTY/Data monitor" capability. > > DK II does not have a separate "sound card monitor" function. You can connect a *powered speaker* to the u2R Out jack to hear the output of the sound card but that is not a supported configuration. A non- amplified speaker will not work and will result in "hot mic" type operation. > > 73, > > ... Joe, W4TV > > > On 2020-12-16 6:53 PM, beaudoin wrote: >> ??? GE All >> >> ??? ??? Well I was struggling trying to get my new FTDX 5000 mp >> going on RTTY with Microham >> >> ??? ??? ??? Digikeyer 2.? I finally got a semi-local to sked a qso .... >> It turns out I was ok but what gave me >> >> ??? ??? ??? problem is monitor has no audio to listen to.? The >> local said his is VERY Low.? Is it a setting >> >> ??? ??? ??? we need to look at? >> >> ??? ??? ??? ??? ??? 73? BoB WA1FCN > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web: http://www.writelog.com/ From wa1fcn at charter.net Wed Dec 16 21:10:19 2020 From: wa1fcn at charter.net (beaudoin) Date: Wed, 16 Dec 2020 20:10:19 -0600 Subject: [WriteLog] FTdx 5000 low monitor audio In-Reply-To: <9452153d-0b94-600d-c973-b9b4475d766e@subich.com> References: <4a91acc2-9b64-be71-ac17-d5324ce54a99@charter.net> <9452153d-0b94-600d-c973-b9b4475d766e@subich.com> Message-ID: <05194ef0-8222-1044-d624-92c25f2fdeee@charter.net> GE All ??? ??? ??? Well Ok I admit it...........Operator error, now remember I just got rig ??? ??? a couple days ago........?? I simply had monitor OFF !! A simple press of button ??? ??? and all the audio anyone could use! ??? ??? ??? ??? ??? See ya all in ARRL Roundup??????? BoB WA1FCN On 12/16/2020 6:33 PM, Joe Subich, W4TV wrote: > > FTdx5000 monitor audio is a function of the transceiver.? The FTdX5000 > Operating Manual - page 81 only references Monitor in LSB/USB/AM/FM > there is no reference as far as I can find to a Monitor function for > RTTY/AFSK-based DATA operation.?? I suggest you contact Yaesu about > a "RTTY/Data monitor" capability. > > DK II does not have a separate "sound card monitor" function.? You > can connect a *powered speaker* to the u2R Out jack to hear the output > of the sound card but that is not a supported configuration.? A non- > amplified speaker will not work and will result in "hot mic" type > operation. > > 73, > > ?? ... Joe, W4TV > > > On 2020-12-16 6:53 PM, beaudoin wrote: >> >> ???? GE All >> >> ???? ??? Well I was struggling trying to get my new FTDX 5000 mp >> going on RTTY with Microham >> >> ???? ??? ??? Digikeyer 2.? I finally got a semi-local to sked a qso >> .... It turns out I was ok but what gave me >> >> ???? ??? ??? problem is monitor has no audio to listen to.? The local >> said his is VERY Low.? Is it a setting >> >> ???? ??? ??? we need to look at? >> >> ???? ??? ??? ??? ??? 73? BoB WA1FCN > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web:? http://www.writelog.com/ From aa5au at bellsouth.net Sun Dec 20 12:34:47 2020 From: aa5au at bellsouth.net (Don Hill AA5AU) Date: Sun, 20 Dec 2020 11:34:47 -0600 Subject: [WriteLog] Unable to left-click callsigns in Rttyrite References: <004101d6d6f6$6a9b2660$3fd17320$.ref@net> Message-ID: <004101d6d6f6$6a9b2660$3fd17320$@net> I'm working with someone who, during the OK DX RTTY Contest, was unable to left-click callsigns (highlighted or not) in Rttyrite and have them populate the Entry Window. He said it worked at one time. He still has the same issue even when using a different module (ARRL RTTY Roundup). He can right-click and get those options. Also, ALT+C works for the call queue. I can't seem to think of anything that could cause this including unexpected changes to keyboard shortcuts. Anyone had this issue? Thanks, Don AA5AU From rwnewbould at comcast.net Sun Dec 20 13:08:11 2020 From: rwnewbould at comcast.net (Rich) Date: Sun, 20 Dec 2020 13:08:11 -0500 Subject: [WriteLog] Unable to left-click callsigns in Rttyrite In-Reply-To: <004101d6d6f6$6a9b2660$3fd17320$@net> References: <004101d6d6f6$6a9b2660$3fd17320$.ref@net> <004101d6d6f6$6a9b2660$3fd17320$@net> Message-ID: I did have this issue during the NAQP Rtty.?? All I did was restart the program and the issue went away. Probably not much help as they probably already did a restart Rich K3RWN On 12/20/2020 12:34 PM, Don Hill AA5AU wrote: > I'm working with someone who, during the OK DX RTTY Contest, was unable to > left-click callsigns (highlighted or not) in Rttyrite and have them populate > the Entry Window. He said it worked at one time. He still has the same issue > even when using a different module (ARRL RTTY Roundup). > > > > He can right-click and get those options. Also, ALT+C works for the call > queue. > > > > I can't seem to think of anything that could cause this including unexpected > changes to keyboard shortcuts. > > > > Anyone had this issue? > > > > Thanks, > > Don AA5AU > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ From aa5au at bellsouth.net Sun Dec 20 17:06:42 2020 From: aa5au at bellsouth.net (Don Hill AA5AU) Date: Sun, 20 Dec 2020 16:06:42 -0600 Subject: [WriteLog] Unable to left-click callsigns in Rttyrite In-Reply-To: References: <004101d6d6f6$6a9b2660$3fd17320$.ref@net> <004101d6d6f6$6a9b2660$3fd17320$@net> Message-ID: <002d01d6d71c$674e2900$35ea7b00$@net> This has been resolved. The user was able to take the INI file from his laptop and apply it to the desktop and it's working. So apparently corruption in the INI file caused the issue. Don AA5AU -----Original Message----- From: WriteLog [mailto:writelog-bounces at contesting.com] On Behalf Of Rich Sent: Sunday, December 20, 2020 12:08 PM To: writelog at contesting.com Subject: Re: [WriteLog] Unable to left-click callsigns in Rttyrite I did have this issue during the NAQP Rtty. All I did was restart the program and the issue went away. Probably not much help as they probably already did a restart Rich K3RWN On 12/20/2020 12:34 PM, Don Hill AA5AU wrote: > I'm working with someone who, during the OK DX RTTY Contest, was unable to > left-click callsigns (highlighted or not) in Rttyrite and have them populate > the Entry Window. He said it worked at one time. He still has the same issue > even when using a different module (ARRL RTTY Roundup). > > > > He can right-click and get those options. Also, ALT+C works for the call > queue. > > > > I can't seem to think of anything that could cause this including unexpected > changes to keyboard shortcuts. > > > > Anyone had this issue? > > > > Thanks, > > Don AA5AU > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web: http://www.writelog.com/ From KI1G at Verizon.net Tue Dec 22 10:44:10 2020 From: KI1G at Verizon.net (Rick Davenport) Date: Tue, 22 Dec 2020 10:44:10 -0500 Subject: [WriteLog] Unable to left-click callsigns in Rttyrite References: <000001d6d879$4b0639f0$e112add0$.ref@net> Message-ID: <000001d6d879$4b0639f0$e112add0$@net> A similar glitch that I am experiencing is when I move my Rttyrite window to my secondary display (Monitor #2), everything prints fine and I can click on menu items in Rttyrite but am unable to capture any callsigns. When I drag the Rttyrite window back to the main display (Monitor #1) and everything works fine. Using Windows 10 Pro and WL v 12.55G 73 Rick KI1G This has been resolved. The user was able to take the INI file from his laptop and apply it to the desktop and it's working. So apparently corruption in the INI file caused the issue. Don AA5AU -----Original Message----- From: WriteLog [mailto:writelog-bounces at contesting.com] On Behalf Of Rich Sent: Sunday, December 20, 2020 12:08 PM To: writelog at contesting.com Subject: Re: [WriteLog] Unable to left-click callsigns in Rttyrite I did have this issue during the NAQP Rtty. All I did was restart the program and the issue went away. Probably not much help as they probably already did a restart Rich K3RWN On 12/20/2020 12:34 PM, Don Hill AA5AU wrote: > I'm working with someone who, during the OK DX RTTY Contest, was unable to > left-click callsigns (highlighted or not) in Rttyrite and have them populate > the Entry Window. He said it worked at one time. He still has the same issue > even when using a different module (ARRL RTTY Roundup). > > > > He can right-click and get those options. Also, ALT+C works for the call > queue. > > > > I can't seem to think of anything that could cause this including unexpected > changes to keyboard shortcuts. > > > > Anyone had this issue? > > > > Thanks, > > Don AA5AU > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web: http://www.writelog.com/ _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web: http://www.writelog.com/ From gordon.lapoint at gmail.com Wed Dec 23 15:56:26 2020 From: gordon.lapoint at gmail.com (Gordon LaPoint) Date: Wed, 23 Dec 2020 15:56:26 -0500 Subject: [WriteLog] Remote Internet log hints? Message-ID: <8825d1be-e983-d8c6-3b92-eab23af1391c@gmail.com> I have just setup the writlog internet log server and tested it. So far it is working.? I'm looking for hints to enhance its usage. I installed the server on a linux box, which we access over a vpn, so the server is not open to the internet, just the local network as setup with openvpn. I did setup a username/password file also.? We are going to use it for the ARRL RTTY RU contest, with three remote users to the n1mgo590 remote. 2 of us have the RC-1101 and the third does not, should be fun and a first try at multi operator use of the remote.? We have setup time slots for each user, using WriteLog Control Site to connect to the remote radio, and the remote log server. So far we have used the remote, but only as a single user in? a contest. Thanks, Gordon - N1MGO From k0cf.craig at gmail.com Wed Dec 23 16:18:27 2020 From: k0cf.craig at gmail.com (k0cf-Craig) Date: Wed, 23 Dec 2020 15:18:27 -0600 Subject: [WriteLog] WriteLog Stew Perry Contest prefill file Message-ID: I have generated a WriteLog ADIF prefill file for the Stew Perry contest and posted it to my club website, the Eastern Iowa DX Association. This link takes you directly to the Prefill section: < https://tinyurl.com/WLprefills > What you will download is a zip file containing the ADIF prefill file, which has the file extension ".adi". The source for this was the file StewPerry.txt from the N1MM+ web site, last updated Nov 2, 2020. After unzipping the ADIF file, start WriteLog and start a new log for the selected contest. Open the WriteLog "Tools" menu and select ?Preset Exchange from ADI file??, browse to the location of your ADIF file and load it. To test it, type a callsign from the ADIF file into the callsign field, press "space" or "tab" to leave that field upon which the received exchange field(s) should automatically fill with data from the prefill file. As always, the accuracy of the data in this file cannot be guaranteed; treat it as a "suggestion" and be sure to log what your QSO partner sends! 73, Craig, K0CF From kevin at rowett.org Wed Dec 23 17:08:57 2020 From: kevin at rowett.org (Kevin Rowett) Date: Wed, 23 Dec 2020 14:08:57 -0800 Subject: [WriteLog] Remote Internet log hints? In-Reply-To: <8825d1be-e983-d8c6-3b92-eab23af1391c@gmail.com> References: <8825d1be-e983-d8c6-3b92-eab23af1391c@gmail.com> Message-ID: <67E16658-2B57-460C-89D5-BF913CA292D8@rowett.org> Gordon, Hope to work you in RU. I?ll be part of ND2T team, operating remotely to K6MTU. The term has used WL internet log server, now for several contests. Very, Successfully. WL Internet Server is very persistent, and QSO agnostic. It will gladly accept QSOs from any contest, and forward those QSOs to all connected writing instances. WL Internet Server keeps the QSOs in memory, so if you restart it, the server will forget all the QSOs. However, when the server restarts, any and all connected log books will re-send all their QSOs to the writelog internet server, which in turn, will send al the QSOs back to all the other log books. The net is - you have to work very, very hard to loose QSOs, or even DELETE A QSO. The only way to delete any QSOs out of a log connected to a WL internet server is - stop the internet server. Restart all the log books that were connected to it, LETE the QSOs from EVERY logbook, then, and ONLY then, restart the WL internet server. Like many, we often have practice QSOs in our logbook, prior to the start. Because fo the above, it?s very difficult to get rid of those practice QSOs. You can mark them as unclaimed. But, that doesn?t change the above behavior. Worse, unless some care is taken, you can end up with QSOs from a different contest, in all the logs. Test and practice before the start of the contest. That will eliminate the issues I?ve noted. Our radio setup is different, so we won?t be using the RRC boxes. GL! > On Dec 23, 2020, at 12:56 PM, Gordon LaPoint wrote: > > I have just setup the writlog internet log server and tested it. So far it is working. I'm looking for hints to enhance its usage. > > I installed the server on a linux box, which we access over a vpn, so the server is not open to the internet, just the local network as setup with openvpn. > > I did setup a username/password file also. We are going to use it for the ARRL RTTY RU contest, with three remote users to the n1mgo590 remote. > > 2 of us have the RC-1101 and the third does not, should be fun and a first try at multi operator use of the remote. We have setup time slots for each user, using WriteLog Control Site to connect to the remote radio, and the remote log server. > > So far we have used the remote, but only as a single user in a contest. > > > Thanks, > > Gordon - N1MGO > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ From jjreisert at alum.mit.edu Wed Dec 23 17:46:26 2020 From: jjreisert at alum.mit.edu (Jim Reisert AD1C) Date: Wed, 23 Dec 2020 15:46:26 -0700 Subject: [WriteLog] CTY-3022 Country Files - 23 December 2020 Message-ID: The Country (CTY) Files were updated on 23 December 2020: https://www.country-files.com/cty-3022-23-december-2020/ For installation instructions, start at: https://www.country-files.com/ Hover your mouse over the word Contest in the menu, then select the software you are using. To install the file, follow the link to your software at the top of the page. If you are interested in a bigger CTY.DAT for everyday logging, you can get it here: https://www.country-files.com/big-cty-23-december-2020/ Note that the release notes (and Version Entity) for this larger file are different than what is shown below. There is a separate link to them. As a reminder, there is an RSS feed of the latest country file announcements: https://www.country-files.com/feed/ Here are the release notes: 23 December 2020 (CTY-3022) VER20201223, Version entity is Comoros, D6 Added/changed Entities/Prefixes/Callsigns: * GB20YOTA is Scotland, GM * K0XX is United States, K in CQ zone 5, ITU zone 8 * AG5LT, KB3VLO and KL7TN/P are all Hawaii, KH6 * KN4LVS and W5SPY are both Alaska, KL * LU6EVD/D is Argentina, LU * R0AI/3, R20YOTA, R30RCK, RA21NY, RC21NY, RC30KR, RC8C/6, RD21NY, RG21NY, RG30KR, RJ21NY, RK21NY, RK30KR, RO21NY, RT30KR, RU21NY, RU30KR, RW21NY, RY21NY and RZ30KR are all European Russia, UA * RT21NY is European Russia, UA in ITU zone 30 * RV21NY is Kaliningrad, UA2 * R21HNY, RL21NY, RM21NY, RN21NY and RQ30KR are all Asiatic Russia, UA9 * RA30KR, RL30KR, RN30KR and RW30KR are all Asiatic Russia, UA9 in CQ zone 18, ITU zone 31 * RQ21NY is Asiatic Russia, UA9 in CQ zone 18, ITU zone 32 * RD30KR, RM30KR, RV30KR, RX21NY and RZ21NY are all Asiatic Russia, UA9 in CQ zone 19, ITU zone 34 * DT8A is South Shetland Islands, VP8/h Removed Entities/Prefixes/Callsigns: * TX0T in French Polynesia, FO * GB100RS in Guernsey, GU * GB20YOTA in Wales, GW * K4JMB, KG5CH and KL3JC in Hawaii, KH6 * KD2UVU in American Samoa, KH8 * K7CAP in Alaska, KL * KI5KQH in Puerto Rico, KP4 * LU4ARU/D and LU6FLZ/F in Argentina, LU * TA1HZ/2 in Asiatic Turkey, TA * R500TLKR and R925RZ in European Russia, UA * R9GM/8 and RA/UR8IF in Asiatic Russia, UA9 73 - Jim AD1C -- Jim Reisert AD1C, , https://www.ad1c.us From pvandyke1953 at gmail.com Thu Dec 24 17:45:29 2020 From: pvandyke1953 at gmail.com (Paul Van Dyke) Date: Thu, 24 Dec 2020 17:45:29 -0500 Subject: [WriteLog] K3S single setup Message-ID: I have seen at least 2 dozen of setup instruction files for multi-op radios But, NOW I have a single Elecraft K3S, not K3. I am believing there is not a major difference in basic setup, but it can make a difference. I am asking for help, and will judge if I go a different direction on the response Is there directions somewhere for a single K3S Thank you Paul KB9AVO From n1jez at burlingtontelecom.net Sat Dec 26 13:39:02 2020 From: n1jez at burlingtontelecom.net (Mike Seguin) Date: Sat, 26 Dec 2020 13:39:02 -0500 Subject: [WriteLog] IC-705 support Message-ID: <206e9d47-d17f-3e2c-05f9-351d5781f148@burlingtontelecom.net> Will the IC-705 be added to the supported rigs for CAT/CW control at some point? It's my new rig for running transverters. Tnx, Mike -- 73, Mike, N1JEZ "A closed mouth gathers no feet" From rgarrett5 at comcast.net Sat Dec 26 15:19:37 2020 From: rgarrett5 at comcast.net (Robert Garrett) Date: Sat, 26 Dec 2020 15:19:37 -0500 Subject: [WriteLog] Switching from VFo A to VFO B In WL Message-ID: <000901d6dbc4$6f4e3e40$4deabac0$@comcast.net> Greetings, Not immediately obvious to me. Using WL with my FTDX101D. What is the keyboard command to toggle between VFO A and VFO B? Any additional setup required? Any assistance would be a great help. Want to operate in the SPDX contest today. 73, Bob K3UL From marsh at ka5m.net Sun Dec 27 15:26:19 2020 From: marsh at ka5m.net (marsh at ka5m.net) Date: Sun, 27 Dec 2020 14:26:19 -0600 Subject: [WriteLog] Erratic Keying Message-ID: <000201d6dc8e$898ffcb0$9caff610$@ka5m.net> I have a problem with erratic keying. My setup: Dell Computer with an i5 Quad Core 3.1 MHz Windows 10 Pro 64-bit WriteLog v 12.55G Icom-7851 The Icom-7851 has the latest firmware version 1.31. For radio to computer communication, I'm using a single USB cable, Icom USB Driver and USB Audio CODEC version 1.30. The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and keying for RTTY. For contesting I press the [F2} key to send my exchange - for the Mini-CWT Sessions it is MARSH 1433. From 1 to 4 out of 10 [[F2] presses gibberish is sent. Any suggestions or comments would be appreciated. Marsh, KA5M From k2qmf at juno.com Sun Dec 27 15:45:40 2020 From: k2qmf at juno.com (Salvatore ["Ted"] K2QMF) Date: Sun, 27 Dec 2020 15:45:40 -0500 Subject: [WriteLog] Fw: Re: Erratic Keying In-Reply-To: References: <000201d6dc8e$898ffcb0$9caff610$@ka5m.net> Message-ID: ------ Forwarded Message -------- From: Salvatore ["Ted"] K2QMF Date: 12/27/2020 3:39:56 PM Subject: Re: [WriteLog] Erratic Keying To: marsh at ka5m.net, writelog at contesting.con This is normal!! One solution is to use a "WinKeyer USB" between the computer and the rig! You can set Writelog to key the WinKeyer from the PORT menu!!? 73,? Ted? K2QMF 12/27/2020 3:26:20 PM, marsh at ka5m.net wrote: I have a problem with erratic keying. My setup: Dell Computer with an i5 Quad Core 3.1 MHz Windows 10 Pro 64-bit WriteLog v 12.55G Icom-7851 The Icom-7851 has the latest firmware version 1.31. For radio to computer communication, I'm using a single USB cable, Icom USB Driver and USB Audio CODEC version 1.30. The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and keying for RTTY. For contesting I press the [F2} key to send my exchange - for the Mini-CWT Sessions it is MARSH 1433. From 1 to 4 out of 10 [[F2] presses gibberish is sent. Any suggestions or comments would be appreciated. Marsh, KA5M _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web: http://www.writelog.com/ ____________________________________________________________ Sponsored by https://www.newser.com/?utm_source=part&utm_medium=uol&utm_campaign=rss_taglines_more Possible Conspiracy Theory Link Emerges in Nashville http://thirdpartyoffers.juno.com/TGL3141/5fe8f2756f09d72750b61st03duc1 Sign the Bill, Lawmakers Tell Trump http://thirdpartyoffers.juno.com/TGL3141/5fe8f27592c7e72750b61st03duc2 Former WWE Champ Jon Huber Dead at 41 http://thirdpartyoffers.juno.com/TGL3141/5fe8f275b7a7d72750b61st03duc3 From nn5t at attglobal.net Sun Dec 27 16:29:24 2020 From: nn5t at attglobal.net (Jon Suehiro) Date: Sun, 27 Dec 2020 21:29:24 -0000 Subject: [WriteLog] Erratic Keying In-Reply-To: <000201d6dc8e$898ffcb0$9caff610$@ka5m.net> References: <000201d6dc8e$898ffcb0$9caff610$@ka5m.net> Message-ID: <000801d6dc97$5a113d60$0e33b820$@attglobal.net> I had exactly same with IC-7610 with USB. Mine was completely resolved by putting microHAM DIGIKER II in line. I got feedbacks many were thinking that caused by RFI getting into USB line but never tried back to USB connection. Try ferrites onto the USB cable (or use USB3 cable which is supposed to be better shieled). If still happening, think RFI, rather than USB data issue. GL & 73 de Jon NN5T -----Original Message----- From: WriteLog On Behalf Of marsh at ka5m.net Sent: December 27, 2020 20:26 To: WriteLog Subject: [WriteLog] Erratic Keying I have a problem with erratic keying. My setup: Dell Computer with an i5 Quad Core 3.1 MHz Windows 10 Pro 64-bit WriteLog v 12.55G Icom-7851 The Icom-7851 has the latest firmware version 1.31. For radio to computer communication, I'm using a single USB cable, Icom USB Driver and USB Audio CODEC version 1.30. The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and keying for RTTY. For contesting I press the [F2} key to send my exchange - for the Mini-CWT Sessions it is MARSH 1433. From 1 to 4 out of 10 [[F2] presses gibberish is sent. Any suggestions or comments would be appreciated. Marsh, KA5M _______________________________________________ WriteLog mailing list WriteLog at contesting.com http://lists.contesting.com/mailman/listinfo/writelog WriteLog on the web: http://www.writelog.com/ From geoffg4fka at virginmedia.com Mon Dec 28 04:31:54 2020 From: geoffg4fka at virginmedia.com (geoff plucknett) Date: Mon, 28 Dec 2020 09:31:54 +0000 (GMT) Subject: [WriteLog] Erratic Keying In-Reply-To: <000801d6dc97$5a113d60$0e33b820$@attglobal.net> References: <000201d6dc8e$898ffcb0$9caff610$@ka5m.net> <000801d6dc97$5a113d60$0e33b820$@attglobal.net> Message-ID: <1430927565.2501061.1609147914641@mail2.virginmedia.com> Same here with the IC-7610 and WriteLog; random times when CW messages turn to gibberish. Data modes and SSB work OK with same power so I think it is Windows timing, not an RFI issue. Like others I have recently bought a Winkeyer so will be trying that soon. Geoff G4FKA > On 27 December 2020 at 21:29 Jon Suehiro wrote: > > > > I had exactly same with IC-7610 with USB. Mine was completely resolved by > putting microHAM DIGIKER II in line. I got feedbacks many were thinking > that caused by RFI getting into USB line but never tried back to USB > connection. Try ferrites onto the USB cable (or use USB3 cable which is > supposed to be better shieled). If still happening, think RFI, rather than > USB data issue. GL & 73 de Jon NN5T > > -----Original Message----- > From: WriteLog On Behalf Of marsh at ka5m.net > Sent: December 27, 2020 20:26 > To: WriteLog > Subject: [WriteLog] Erratic Keying > > I have a problem with erratic keying. > > My setup: > Dell Computer with an i5 Quad Core 3.1 MHz Windows 10 Pro 64-bit WriteLog v > 12.55G > Icom-7851 > > The Icom-7851 has the latest firmware version 1.31. > For radio to computer communication, I'm using a single USB cable, Icom USB > Driver and USB Audio CODEC version 1.30. > The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for > rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and > keying for RTTY. > > For contesting I press the [F2} key to send my exchange - for the Mini-CWT > Sessions it is MARSH 1433. From 1 to 4 out of 10 [[F2] presses gibberish is > sent. > > Any suggestions or comments would be appreciated. > > Marsh, KA5M > > > > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ From jimw7ry at gmail.com Mon Dec 28 08:19:57 2020 From: jimw7ry at gmail.com (Jim) Date: Mon, 28 Dec 2020 07:19:57 -0600 Subject: [WriteLog] Fw: Re: Erratic Keying In-Reply-To: References: <000201d6dc8e$898ffcb0$9caff610$@ka5m.net> Message-ID: <343c184f-fab6-588d-6190-0fb8833357f6@gmail.com> I have no issues with keying my IC7610 with the ISB port. CW is good and clean. BUT.... I don't use virtual comm ports. I use a MORTTY for FSK. Much cleaner and more accurate FSK that way. I also use Windows 10 PRO. Thanks 73 Jim W7RY On 12/27/2020 2:45 PM, Salvatore ["Ted"] K2QMF wrote: > ------ Forwarded Message -------- > From: Salvatore ["Ted"] K2QMF > Date: 12/27/2020 3:39:56 PM > Subject: Re: [WriteLog] Erratic Keying > To: marsh at ka5m.net, writelog at contesting.con > > This is normal!! > One solution is to use a "WinKeyer USB" between the computer and the rig! > You can set Writelog to key the WinKeyer from the PORT menu!!? 73,? Ted? K2QMF > > > 12/27/2020 3:26:20 PM, marsh at ka5m.net wrote: > > I have a problem with erratic keying. > > My setup: > Dell Computer with an i5 Quad Core 3.1 MHz > Windows 10 Pro 64-bit > WriteLog v 12.55G > Icom-7851 > > The Icom-7851 has the latest firmware version 1.31. > For radio to computer communication, I'm using a single USB cable, Icom USB > Driver and USB Audio CODEC version 1.30. > The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for > rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and > keying for RTTY. > > For contesting I press the [F2} key to send my exchange - for the Mini-CWT > Sessions it is MARSH 1433. From 1 to 4 out of 10 [[F2] presses gibberish is > sent. > > Any suggestions or comments would be appreciated. > > Marsh, KA5M > > > > > > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ > > ____________________________________________________________ > Sponsored by https://www.newser.com/?utm_source=part&utm_medium=uol&utm_campaign=rss_taglines_more > > Possible Conspiracy Theory Link Emerges in Nashville > http://thirdpartyoffers.juno.com/TGL3141/5fe8f2756f09d72750b61st03duc1 > Sign the Bill, Lawmakers Tell Trump > http://thirdpartyoffers.juno.com/TGL3141/5fe8f27592c7e72750b61st03duc2 > Former WWE Champ Jon Huber Dead at 41 > http://thirdpartyoffers.juno.com/TGL3141/5fe8f275b7a7d72750b61st03duc3 > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ From ed at w0yk.com Mon Dec 28 08:29:21 2020 From: ed at w0yk.com (Ed W0YK) Date: Mon, 28 Dec 2020 05:29:21 -0800 Subject: [WriteLog] Erratic Keying In-Reply-To: <1430927565.2501061.1609147914641@mail2.virginmedia.com> Message-ID: This is common with both WriteLog and N1MM.? ?Only Win-Test keys reliably without a hardware keyer.? Otherwise, a Winkey, microHam interface, W5XD Keyer, etc is required.73,Ed W0YK -------- Original message --------From: geoff plucknett via WriteLog Date: 12/28/20 01:32 (GMT-08:00) To: Jon Suehiro , marsh at ka5m.net, WriteLog Subject: Re: [WriteLog] Erratic Keying Same here with the IC-7610 and WriteLog; random times when CW messages turn to gibberish. Data modes and SSB work OK with same power so I think it is Windows timing, not an RFI issue. Like others I have recently bought a Winkeyer so will be trying that soon.Geoff G4FKA> On 27 December 2020 at 21:29 Jon Suehiro wrote:> > > > I had exactly same with IC-7610 with USB.? Mine was completely resolved by> putting microHAM DIGIKER II in line.? I got feedbacks many were thinking> that caused by RFI getting into USB line but never tried back to USB> connection.? Try ferrites onto the USB cable (or use USB3 cable which is> supposed to be better shieled).? If still happening, think RFI, rather than> USB data issue.? GL & 73 de Jon NN5T> > -----Original Message-----> From: WriteLog On Behalf Of marsh at ka5m.net> Sent: December 27, 2020 20:26> To: WriteLog > Subject: [WriteLog] Erratic Keying> > I have a problem with erratic keying.> > My setup:> Dell Computer with an i5 Quad Core 3.1 MHz Windows 10 Pro 64-bit WriteLog v> 12.55G> Icom-7851> > The Icom-7851 has the latest firmware version 1.31.> For radio to computer communication, I'm using a single USB cable, Icom USB> Driver and USB Audio CODEC version 1.30.> The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for> rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and> keying for RTTY.> > For contesting I press the [F2} key to send my exchange - for the Mini-CWT> Sessions it is MARSH 1433. From 1 to 4 out of 10 [[F2] presses gibberish is> sent.> > Any suggestions or comments would be appreciated.> > Marsh, KA5M> > > > > _______________________________________________> WriteLog mailing list> WriteLog at contesting.com> http://lists.contesting.com/mailman/listinfo/writelog> WriteLog on the web:? http://www.writelog.com/> > _______________________________________________> WriteLog mailing list> WriteLog at contesting.com> http://lists.contesting.com/mailman/listinfo/writelog> WriteLog on the web:? http://www.writelog.com/_______________________________________________WriteLog mailing listWriteLog at contesting.comhttp://lists.contesting.com/mailman/listinfo/writelogWriteLog on the web:? http://www.writelog.com/ From marsh at ka5m.net Mon Dec 28 11:45:34 2020 From: marsh at ka5m.net (marsh at ka5m.net) Date: Mon, 28 Dec 2020 10:45:34 -0600 Subject: [WriteLog] Erratic Keying - Problem Resolved Message-ID: <002001d6dd38$dd496490$97dc2db0$@ka5m.net> Thanks to all who responded. A WinKeyer USB solved my erratic keying problem. Marsh, KA5M -----Original Message----- From: marsh at ka5m.net Sent: Sunday, December 27, 2020 2:26 PM To: WriteLog Subject: Erratic Keying I have a problem with erratic keying. My setup: Dell Computer with an i5 Quad Core 3.1 MHz Windows 10 Pro 64-bit WriteLog v 12.55G Icom-7851 The Icom-7851 has the latest firmware version 1.31. For radio to computer communication, I'm using a single USB cable, Icom USB Driver and USB Audio CODEC version 1.30. The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and keying for RTTY. For contesting I press the [F2} key to send my exchange - for the Mini-CWT Sessions it is MARSH 1433. From 1 to 4 out of 10 [F2] presses gibberish is sent. Any suggestions or comments would be appreciated. Marsh, KA5M From jimk0xu at gmail.com Mon Dec 28 13:37:49 2020 From: jimk0xu at gmail.com (Jim Rhodes) Date: Mon, 28 Dec 2020 12:37:49 -0600 Subject: [WriteLog] Erratic Keying - Problem Resolved In-Reply-To: <002001d6dd38$dd496490$97dc2db0$@ka5m.net> References: <002001d6dd38$dd496490$97dc2db0$@ka5m.net> Message-ID: Yes, computer port timing is not to be trusted for sending good CW. On Mon, Dec 28, 2020, 10:45 wrote: > Thanks to all who responded. A WinKeyer USB solved my erratic keying > problem. > > Marsh, KA5M > > > -----Original Message----- > From: marsh at ka5m.net > Sent: Sunday, December 27, 2020 2:26 PM > To: WriteLog > Subject: Erratic Keying > > I have a problem with erratic keying. > > My setup: > Dell Computer with an i5 Quad Core 3.1 MHz Windows 10 Pro 64-bit WriteLog v > 12.55G > Icom-7851 > > The Icom-7851 has the latest firmware version 1.31. > For radio to computer communication, I'm using a single USB cable, Icom USB > Driver and USB Audio CODEC version 1.30. > The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for > rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and > keying for RTTY. > > For contesting I press the [F2} key to send my exchange - for the Mini-CWT > Sessions it is MARSH 1433. From 1 to 4 out of 10 [F2] presses gibberish is > sent. > > Any suggestions or comments would be appreciated. > > Marsh, KA5M > > > > > > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ > From davidshealy16 at gmail.com Mon Dec 28 16:55:45 2020 From: davidshealy16 at gmail.com (David Shealy) Date: Mon, 28 Dec 2020 15:55:45 -0600 Subject: [WriteLog] WriteLog Digest, Vol 216, Issue 21 In-Reply-To: References: Message-ID: <3900FB68-5B43-4E8C-A3F3-5B2D8DF8D02A@gmail.com> Marsh, I followed the FB newsletter for setting up my ICOM7610 for FT8 using USB-D2 mode for WSJT-X..... Link to this FB newsletter https://www.fbnews.jp/201712/technical_en/ As you will read in this newsletter the only difference for setup on 7851 and 7610 is ICOM code for these two radios. I have used this info for good FT8 operations for past 2 years. 73?s David Sent from my iPhone David L Shealy, K4KSV davidshealy16 at gmail.com > On Dec 28, 2020, at 7:20 AM, writelog-request at contesting.com wrote: > ?Send WriteLog mailing list submissions to > writelog at contesting.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.contesting.com/mailman/listinfo/writelog > or, via email, send a message with subject or body 'help' to > writelog-request at contesting.com > > You can reach the person managing the list at > writelog-owner at contesting.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of WriteLog digest..." > > > Today's Topics: > > 1. Erratic Keying (marsh at ka5m.net) > 2. Fw: Re: Erratic Keying (Salvatore ["Ted"] K2QMF) > 3. Re: Erratic Keying (Jon Suehiro) > 4. Re: Erratic Keying (geoff plucknett) > 5. Re: Fw: Re: Erratic Keying (Jim) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 27 Dec 2020 14:26:19 -0600 > From: > To: "WriteLog" > Subject: [WriteLog] Erratic Keying > Message-ID: <000201d6dc8e$898ffcb0$9caff610$@ka5m.net> > Content-Type: text/plain; charset="us-ascii" > > I have a problem with erratic keying. > > My setup: > Dell Computer with an i5 Quad Core 3.1 MHz > Windows 10 Pro 64-bit > WriteLog v 12.55G > Icom-7851 > > The Icom-7851 has the latest firmware version 1.31. > For radio to computer communication, I'm using a single USB cable, Icom USB > Driver and USB Audio CODEC version 1.30. > The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for > rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and > keying for RTTY. > > For contesting I press the [F2} key to send my exchange - for the Mini-CWT > Sessions it is MARSH 1433. From 1 to 4 out of 10 [[F2] presses gibberish is > sent. > > Any suggestions or comments would be appreciated. > > Marsh, KA5M > > > > > > > > > ------------------------------ > > Message: 2 > Date: Sun, 27 Dec 2020 15:45:40 -0500 > From: "Salvatore [\"Ted\"] K2QMF" > To: "Mike Seguin via WriteLog" > Subject: [WriteLog] Fw: Re: Erratic Keying > Message-ID: > Content-Type: text/plain; charset="utf-8" > > > ------ Forwarded Message -------- > From: Salvatore ["Ted"] K2QMF > Date: 12/27/2020 3:39:56 PM > Subject: Re: [WriteLog] Erratic Keying > To: marsh at ka5m.net, writelog at contesting.con > > This is normal!! > One solution is to use a "WinKeyer USB" between the computer and the rig! > You can set Writelog to key the WinKeyer from the PORT menu!!? 73,? Ted? K2QMF > > > 12/27/2020 3:26:20 PM, marsh at ka5m.net wrote: > > I have a problem with erratic keying. > > My setup: > Dell Computer with an i5 Quad Core 3.1 MHz > Windows 10 Pro 64-bit > WriteLog v 12.55G > Icom-7851 > > The Icom-7851 has the latest firmware version 1.31. > For radio to computer communication, I'm using a single USB cable, Icom USB > Driver and USB Audio CODEC version 1.30. > The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for > rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and > keying for RTTY. > > For contesting I press the [F2} key to send my exchange - for the Mini-CWT > Sessions it is MARSH 1433. From 1 to 4 out of 10 [[F2] presses gibberish is > sent. > > Any suggestions or comments would be appreciated. > > Marsh, KA5M > > > > > > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ > > ____________________________________________________________ > Sponsored by https://www.newser.com/?utm_source=part&utm_medium=uol&utm_campaign=rss_taglines_more > > Possible Conspiracy Theory Link Emerges in Nashville > http://thirdpartyoffers.juno.com/TGL3141/5fe8f2756f09d72750b61st03duc1 > Sign the Bill, Lawmakers Tell Trump > http://thirdpartyoffers.juno.com/TGL3141/5fe8f27592c7e72750b61st03duc2 > Former WWE Champ Jon Huber Dead at 41 > http://thirdpartyoffers.juno.com/TGL3141/5fe8f275b7a7d72750b61st03duc3 > > ------------------------------ > > Message: 3 > Date: Sun, 27 Dec 2020 21:29:24 -0000 > From: "Jon Suehiro" > To: , "'WriteLog'" > Subject: Re: [WriteLog] Erratic Keying > Message-ID: <000801d6dc97$5a113d60$0e33b820$@attglobal.net> > Content-Type: text/plain; charset="us-ascii" > > > I had exactly same with IC-7610 with USB. Mine was completely resolved by > putting microHAM DIGIKER II in line. I got feedbacks many were thinking > that caused by RFI getting into USB line but never tried back to USB > connection. Try ferrites onto the USB cable (or use USB3 cable which is > supposed to be better shieled). If still happening, think RFI, rather than > USB data issue. GL & 73 de Jon NN5T > > -----Original Message----- > From: WriteLog On Behalf Of marsh at ka5m.net > Sent: December 27, 2020 20:26 > To: WriteLog > Subject: [WriteLog] Erratic Keying > > I have a problem with erratic keying. > > My setup: > Dell Computer with an i5 Quad Core 3.1 MHz Windows 10 Pro 64-bit WriteLog v > 12.55G > Icom-7851 > > The Icom-7851 has the latest firmware version 1.31. > For radio to computer communication, I'm using a single USB cable, Icom USB > Driver and USB Audio CODEC version 1.30. > The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for > rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and > keying for RTTY. > > For contesting I press the [F2} key to send my exchange - for the Mini-CWT > Sessions it is MARSH 1433. From 1 to 4 out of 10 [[F2] presses gibberish is > sent. > > Any suggestions or comments would be appreciated. > > Marsh, KA5M > > > > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ > > > > ------------------------------ > > Message: 4 > Date: Mon, 28 Dec 2020 09:31:54 +0000 (GMT) > From: geoff plucknett > To: Jon Suehiro , marsh at ka5m.net, WriteLog > > Subject: Re: [WriteLog] Erratic Keying > Message-ID: <1430927565.2501061.1609147914641 at mail2.virginmedia.com> > Content-Type: text/plain; charset=UTF-8 > > Same here with the IC-7610 and WriteLog; random times when CW messages turn to gibberish. Data modes and SSB work OK with same power so I think it is Windows timing, not an RFI issue. Like others I have recently bought a Winkeyer so will be trying that soon. > > Geoff G4FKA > >> On 27 December 2020 at 21:29 Jon Suehiro wrote: >> >> >> >> I had exactly same with IC-7610 with USB. Mine was completely resolved by >> putting microHAM DIGIKER II in line. I got feedbacks many were thinking >> that caused by RFI getting into USB line but never tried back to USB >> connection. Try ferrites onto the USB cable (or use USB3 cable which is >> supposed to be better shieled). If still happening, think RFI, rather than >> USB data issue. GL & 73 de Jon NN5T >> >> -----Original Message----- >> From: WriteLog On Behalf Of marsh at ka5m.net >> Sent: December 27, 2020 20:26 >> To: WriteLog >> Subject: [WriteLog] Erratic Keying >> >> I have a problem with erratic keying. >> >> My setup: >> Dell Computer with an i5 Quad Core 3.1 MHz Windows 10 Pro 64-bit WriteLog v >> 12.55G >> Icom-7851 >> >> The Icom-7851 has the latest firmware version 1.31. >> For radio to computer communication, I'm using a single USB cable, Icom USB >> Driver and USB Audio CODEC version 1.30. >> The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for >> rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and >> keying for RTTY. >> >> For contesting I press the [F2} key to send my exchange - for the Mini-CWT >> Sessions it is MARSH 1433. From 1 to 4 out of 10 [[F2] presses gibberish is >> sent. >> >> Any suggestions or comments would be appreciated. >> >> Marsh, KA5M >> >> >> >> >> _______________________________________________ >> WriteLog mailing list >> WriteLog at contesting.com >> http://lists.contesting.com/mailman/listinfo/writelog >> WriteLog on the web: http://www.writelog.com/ >> >> _______________________________________________ >> WriteLog mailing list >> WriteLog at contesting.com >> http://lists.contesting.com/mailman/listinfo/writelog >> WriteLog on the web: http://www.writelog.com/ > > > ------------------------------ > > Message: 5 > Date: Mon, 28 Dec 2020 07:19:57 -0600 > From: Jim > To: writelog at contesting.com > Subject: Re: [WriteLog] Fw: Re: Erratic Keying > Message-ID: <343c184f-fab6-588d-6190-0fb8833357f6 at gmail.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > I have no issues with keying my IC7610 with the ISB port. CW is good and > clean. > > BUT.... I don't use virtual comm ports. I use a MORTTY for FSK. Much > cleaner and more accurate FSK that way. > > > > I also use Windows 10 PRO. > > > Thanks > 73 > Jim W7RY > >> On 12/27/2020 2:45 PM, Salvatore ["Ted"] K2QMF wrote: >> ------ Forwarded Message -------- >> From: Salvatore ["Ted"] K2QMF >> Date: 12/27/2020 3:39:56 PM >> Subject: Re: [WriteLog] Erratic Keying >> To: marsh at ka5m.net, writelog at contesting.con >> >> This is normal!! >> One solution is to use a "WinKeyer USB" between the computer and the rig! >> You can set Writelog to key the WinKeyer from the PORT menu!!? 73,? Ted? K2QMF >> >> >> 12/27/2020 3:26:20 PM, marsh at ka5m.net wrote: >> >> I have a problem with erratic keying. >> >> My setup: >> Dell Computer with an i5 Quad Core 3.1 MHz >> Windows 10 Pro 64-bit >> WriteLog v 12.55G >> Icom-7851 >> >> The Icom-7851 has the latest firmware version 1.31. >> For radio to computer communication, I'm using a single USB cable, Icom USB >> Driver and USB Audio CODEC version 1.30. >> The USB Driver set up 2 virtual COM ports, COM5 and COM6. COM5 is used for >> rig control and CW keying on DTR. COM6 handles PTT for FT8, and PTT and >> keying for RTTY. >> >> For contesting I press the [F2} key to send my exchange - for the Mini-CWT >> Sessions it is MARSH 1433. From 1 to 4 out of 10 [[F2] presses gibberish is >> sent. >> >> Any suggestions or comments would be appreciated. >> >> Marsh, KA5M >> >> >> >> >> >> >> _______________________________________________ >> WriteLog mailing list >> WriteLog at contesting.com >> http://lists.contesting.com/mailman/listinfo/writelog >> WriteLog on the web: http://www.writelog.com/ >> >> ____________________________________________________________ >> Sponsored by https://www.newser.com/?utm_source=part&utm_medium=uol&utm_campaign=rss_taglines_more >> >> Possible Conspiracy Theory Link Emerges in Nashville >> http://thirdpartyoffers.juno.com/TGL3141/5fe8f2756f09d72750b61st03duc1 >> Sign the Bill, Lawmakers Tell Trump >> http://thirdpartyoffers.juno.com/TGL3141/5fe8f27592c7e72750b61st03duc2 >> Former WWE Champ Jon Huber Dead at 41 >> http://thirdpartyoffers.juno.com/TGL3141/5fe8f275b7a7d72750b61st03duc3 >> _______________________________________________ >> WriteLog mailing list >> WriteLog at contesting.com >> http://lists.contesting.com/mailman/listinfo/writelog >> WriteLog on the web: http://www.writelog.com/ > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > > > ------------------------------ > > End of WriteLog Digest, Vol 216, Issue 21 > ***************************************** From k0cf.craig at gmail.com Wed Dec 30 13:27:46 2020 From: k0cf.craig at gmail.com (k0cf-Craig) Date: Wed, 30 Dec 2020 12:27:46 -0600 Subject: [WriteLog] WriteLog ARRL RTTY Roundup Contest prefill file Message-ID: I have generated a WriteLog ADIF prefill file for the ARRL RTTY Roundup contest and posted it to my club website, the Eastern Iowa DX Association. This link takes you directly to the Prefill section: < https://tinyurl.com/WLprefills > What you will download is a zip file containing the ADIF prefill file, which has the file extension ".adi". The source for this was the file ARRLRTTY-002.txt from the N1MM+ website, last updated Dec 29, 2020. After unzipping the ADIF file, start WriteLog and start a new log for the selected contest. Open the WriteLog "Tools" menu and select ?Preset Exchange from ADI file??, browse to the location of your ADIF file and load it. To test it, type a callsign from the ADIF file into the callsign field, press "space" or "tab" to leave that field upon which the received exchange field(s) should automatically fill with data from the prefill file. As always, the accuracy of the data in this file cannot be guaranteed; treat it as a "suggestion" and be sure to log what your QSO partner sends! 73, Craig, K0CF From marsh at ka5m.net Wed Dec 30 18:50:59 2020 From: marsh at ka5m.net (marsh at ka5m.net) Date: Wed, 30 Dec 2020 17:50:59 -0600 Subject: [WriteLog] WriteLog & WinKeyer USB Message-ID: <000001d6df06$a0133720$e039a560$@ka5m.net> WL v12.55G WinKeyer USB 3.1.2 I have sidetone from the transceiver when I transmit with the WinKeyer USB or paddle. How do I turn off the WinKeyer USB sidetone with WriteLog? Marsh, KA5M From jimk0xu at gmail.com Wed Dec 30 19:32:40 2020 From: jimk0xu at gmail.com (Jim Rhodes) Date: Wed, 30 Dec 2020 18:32:40 -0600 Subject: [WriteLog] WriteLog & WinKeyer USB In-Reply-To: <000001d6df06$a0133720$e039a560$@ka5m.net> References: <000001d6df06$a0133720$e039a560$@ka5m.net> Message-ID: I think you have to turn it off with the WinKey program. I can barely hear mine so I just don't bother with it. It is a not right in front of me but up on a shelf oug over the way. On Wed, Dec 30, 2020, 18:10 wrote: > WL v12.55G > WinKeyer USB 3.1.2 > > I have sidetone from the transceiver when I transmit with the WinKeyer USB > or paddle. > > How do I turn off the WinKeyer USB sidetone with WriteLog? > > Marsh, KA5M > > > _______________________________________________ > WriteLog mailing list > WriteLog at contesting.com > http://lists.contesting.com/mailman/listinfo/writelog > WriteLog on the web: http://www.writelog.com/ >