I'm pretty sure that's one of the main functions of the new WriteLog box.
It started out to do just that, and then matured into an SO2R box.
Robert K5PI
-----Original Message-----
From: owner-trlog@contesting.com [mailto:owner-trlog@contesting.com]On
Behalf Of Jim Smith
Sent: Monday, October 15, 2001 5:32 PM
To: trlog@contesting.com
Subject: Re: [TRLog] TRLog in the RTTY Sprint (long)
Hi all,
I have never used a hardware keyer so I may be talking nonsense
here. It seems to me that if clean cw is the main issue with
respect to cw in a Win environment it shouldn't be too hard to
make a hardware box that receives ASCII from the computer,
converts it to Morse and drives a relay to key the rig. Now the
only timing issue is to meter out the ASCII symbols from a buffer
at the desired wpm rate. Heck, maybe even I could do it.
This would obviously add to the cost but, if it was supplied in
kit form, I would think that, TRLoggers being a hardy lot, it
could be an acceptable workaround.
So, blaze away, tell me where I am wrong
73 de Jim Smith VE7FO
LogWindows@aol.com wrote:
>
> To do CW flawlessly in the Win32 environment would require a vxd, kernel
mode
> or WDM level device driver (depending on the O/S, since all flavors of
> Windows dont use the same device driver model). This code would run at
Ring
> 0 of the processor, where it would be able to preempts the O/S at the
> processor level and provide real time CW.
>
> Good device driver coders want about $60,000 to $80,000 a year.
--
FAQ on WWW: http://www.contesting.com/FAQ/trlog
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
--
FAQ on WWW: http://www.contesting.com/FAQ/trlog
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|