Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+CW\s+direct\s+keying\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+CW\s+direct\s+keying\s*$/: 13 ]

Total 13 documents matching your query.

1. [WriteLog] CW direct keying (score: 1): Author: "Darren Collins (G0TSM)" <daz@g0tsm.com>; Date: Sat, 05 Jul 2014 22:38:39 +0100; Hi All, I'm on holiday in the Greek Islands and my Winkey compatible interface has failed, luckily I have a spare directkeying interface which is just an opto-isolater type. It works fine but everyno; /archives//html/WriteLog/2014-07/msg00004.html (7,313 bytes)
2. Re: [WriteLog] CW direct keying (score: 1): Author: "Darren Collins (G0TSM)" <daz@g0tsm.com>; Date: Sun, 06 Jul 2014 14:11:48 +0100; Hello Bill, thanks for replying but ignore Winkey, that interface is dead in the water. The backup is an opto-isolater type that is directly keyed, this is the one i'm trying to get to run smoothly.; /archives//html/WriteLog/2014-07/msg00005.html (9,774 bytes)
3. Re: [WriteLog] CW direct keying (score: 1): Author: "Wayne, W5XD" <w5xd@writelog.com>; Date: Sun, 06 Jul 2014 13:30:49 -0500; This is a tough one. The reason WinKey exists is exactly the situation you're in. Its not COM port settings that are your problem. Your problem is tasks that Windows thinks are higher priority than; /archives//html/WriteLog/2014-07/msg00006.html (8,473 bytes)
4. Re: [WriteLog] CW direct keying (score: 1): Author: "Darren Collins (G0TSM)" <daz@g0tsm.com>; Date: Sun, 06 Jul 2014 21:59:05 +0100; Wayne, Thanks for replying... Luckily the Winkey unit has sprung back into life after being disconnected for 24hrs, but i'll try your suggestion on direct keying tomorrow. 73 Darren (SV5/)G0TSM On 06; /archives//html/WriteLog/2014-07/msg00008.html (9,297 bytes)
5. Re: [WriteLog] CW direct keying (score: 1): Author: "Don Hill AA5AU" <aa5au@bellsouth.net>; Date: Sun, 6 Jul 2014 18:12:41 -0500; You can build a simple CW transistor interface. Diagram here: http://aa5au.com/rttyinterface.html 73, Don AA5AU Wayne, Thanks for replying... Luckily the Winkey unit has sprung back into life after b; /archives//html/WriteLog/2014-07/msg00009.html (10,315 bytes)
6. Re: [WriteLog] CW direct keying (score: 1): Author: Bryan Swadener via WriteLog <writelog@contesting.com>; Date: Mon, 7 Jul 2014 10:01:37 -0700; Hi Don, That simple transistor interface offers zero ground loop isolation between the PC and the rig. I used a dual optoisolator IC to provide isolation before switching to a fancy Rigblaster Pro (; /archives//html/WriteLog/2014-07/msg00010.html (9,362 bytes)
7. Re: [WriteLog] CW direct keying (score: 1): Author: Jay WS7I <ws7ik7tj@gmail.com>; Date: Mon, 07 Jul 2014 10:08:09 -0700; Been using that simple transistor device on each platform since Win98. When I switched from parallel to serial. Works fine on XP, Win7, and Mac. Single most important thing is junking Norton, McAfee; /archives//html/WriteLog/2014-07/msg00011.html (8,981 bytes)
8. Re: [WriteLog] CW direct keying (score: 1): Author: Steven Kline <skline4@verizon.net>; Date: Mon, 07 Jul 2014 12:37:15 -0500; Hi Bryan, Is it possible to provide optoisolator diagram similar to Dons diagram for simple transistor interface? Quite a few may be interested in building isolated circuit. Ive built the interfaces; /archives//html/WriteLog/2014-07/msg00012.html (10,231 bytes)
9. Re: [WriteLog] CW direct keying (score: 1): Author: Jay WS7I <ws7ik7tj@gmail.com>; Date: Mon, 07 Jul 2014 10:52:44 -0700; Everything you need. This is on my EWARG (Eastern Washington Amateur Radio Group) page. htt://www.ewarg.org Its down at the bottom of the main page and a PDF. I would add one more for CW that is just; /archives//html/WriteLog/2014-07/msg00013.html (10,948 bytes)
10. Re: [WriteLog] CW direct keying (score: 1): Author: "Darren Collins (G0TSM)" <daz@g0tsm.com>; Date: Wed, 09 Jul 2014 20:51:20 +0100; I re-hooked up the direct keying interface and tried changing the priority in the Windows task manager, but it made no difference, same issue kept cropping up, even with anti-virus disabled on the ne; /archives//html/WriteLog/2014-07/msg00015.html (11,612 bytes)
11. Re: [WriteLog] CW direct keying (score: 1): Author: Kostas SV1DPI <sv1dpi@otenet.gr>; Date: Thu, 10 Jul 2014 07:41:11 +0300; Unfortunately you will find that writelog does not work while almost any other piece of software I have tried, works (dx4win, logger, n1mm). Writelog needs to improve this but Wayne told abt it in th; /archives//html/WriteLog/2014-07/msg00016.html (13,242 bytes)
12. Re: [WriteLog] CW direct keying (score: 1): Author: "Joe Subich, W4TV" <lists@subich.com>; Date: Thu, 10 Jul 2014 10:08:53 -0400; Darren, If your interface is USB based try some of all of the following: Open Windows Device Manager and select the COM port created by your interface. Double click to open Properties, select the Por; /archives//html/WriteLog/2014-07/msg00017.html (13,085 bytes)
13. Re: [WriteLog] CW direct keying (score: 1): Author: "Darren Collins (G0TSM)" <daz@g0tsm.com>; Date: Fri, 11 Jul 2014 10:09:31 +0100; Hi Joe, The USB interface for direct CW keying is an old Prolific PL2030-H and the options you mentioned aren't shown for that port. I'll come back to this later as I mentioned that I only used this; /archives//html/WriteLog/2014-07/msg00019.html (14,900 bytes)

Current List: 1 - 13
Page: [1]