WriteLog
[Top] [All Lists]

[WriteLog] Chopped CW

To: <writelog@contesting.com>
Subject: [WriteLog] Chopped CW
From: K4IA@aol.com (K4IA@aol.com)
Date: Tue, 19 Feb 2002 11:11:10 EST
--part1_160.906a67c.29a3d31e_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Could the problem be the LPT1 port?

Seems to me that printers print a lot slower than they receive data.  Also 
printers have their own buffers.  Therefore, printers are designed to 
accepting chunks of data sent at high speed but sporadically.  That would 
lead computer designers to give the LPT1 port a very low priority compared to 
other tasks and communication going on in the computer -- the printer is so 
slow the data can always catch up.

Now if you're keying the rig through the LPT1 port, wouldn't the port 
continue to behave the same way?  Since CW (or any communication meant to be 
transmitted on the rig) is sent to the rig in "real time" and at a fairly 
slow rate (1200 bps - 9600 bps), anything other than full and complete access 
to LPT1 makes a big difference at the rig.  There are no buffers in the rig 
to hold data and you don't have any delay like a slow printer.

Would the serial port behave better?  Can WriteLog be configured to use a USB 
port?  I am neither a computer not a WriteLog expert but leave the issues to 
others who may be able to shed some more light (not flame) on the issue.

Radio K4IA
Craig Buck
Fredericksburg, Virginia USA
QRP ARCI #2550  FISTS #6702 CC 788 Diamond #64
K1 #470    K2 #2460 
----------------------------------------------
For cheap long distance, 800#s and more

Tune to <A 
HREF="http://www.ld.net/?bucksavers";>http://www.ld.net/?bucksavers</A>
4.9 cents/min - no monthly fees

--part1_160.906a67c.29a3d31e_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>Could the problem be the LPT1 
port?<BR>
<BR>
Seems to me that printers print a lot slower than they receive data.&nbsp; Also 
printers have their own buffers.&nbsp; Therefore, printers are designed to 
accepting chunks of data sent at high speed but sporadically.&nbsp; That would 
lead computer designers to give the LPT1 port a very low priority compared to 
other tasks and communication going on in the computer -- the printer is so 
slow the data can always catch up.<BR>
<BR>
Now if you're keying the rig through the LPT1 port, wouldn't the port continue 
to behave the same way?&nbsp; Since CW (or any communication meant to be 
transmitted on the rig) is sent to the rig in "real time" and at a fairly slow 
rate (1200 bps - 9600 bps), anything other than full and complete access to 
LPT1 makes a big difference at the rig.&nbsp; There are no buffers in the rig 
to hold data and you don't have any delay like a slow printer.<BR>
<BR>
Would the serial port behave better?&nbsp; Can WriteLog be configured to use a 
USB port?&nbsp; I am neither a computer not a WriteLog expert but leave the 
issues to others who may be able to shed some more light (not flame) on the 
issue.<BR>
<BR>
Radio K4IA<BR>
Craig Buck<BR>
Fredericksburg, Virginia USA<BR>
QRP ARCI #2550&nbsp; FISTS #6702 CC 788 Diamond #64<BR>
K1 #470&nbsp;&nbsp;&nbsp; K2 #2460 <BR>
----------------------------------------------<BR>
For cheap long distance, 800#s and more<BR>
<BR>
Tune to <A 
HREF="http://www.ld.net/?bucksavers";>http://www.ld.net/?bucksavers</A><BR>
4.9 cents/min - no monthly fees</FONT></HTML>

--part1_160.906a67c.29a3d31e_boundary--

<Prev in Thread] Current Thread [Next in Thread>