This is a multi-part message in MIME format.
------=_NextPart_000_0033_01C18B3E.8E833040
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
I used the voltmeter on LPT port a lot lately!
In early CT versions, just pin 1 was enough for TTL keying as it used
natural STROBE function going low when activated.
TR decided to key pin 16 with a positive signal. Universal keying circuit
needed NPN transistor for compatibility between both programs.
It claimed 50 mA keying capability which is way bellow pin 1 sink ratings.
ARRL handbook announced a circuit which used pin 1 as enable for PTT. It
used plenty of relays for various switching.
Writelog was keying both pins 1 and 16 affecting smooth PTT operation in
commercial SO2R boxes.
Free N1MMLogger didn't do that with pin 1.
Now we develop SO2R situation with pin 1 permanently low, pin 14 going low
for Radio B and no power source for my miniature LPT adapter :-(
May I kindly ask for a pin 1 to go low at PTT time and everything will work
fine in USA and EU!
73 de Mario, S56A, N1YU www.miletic.net
----- Original Message -----
From: W. Wright, W5XD
To: TOMK5RC@aol.com ; writelog@contesting.com
Sent: Saturday, December 22, 2001 5:33 PM
Subject: RE: [WriteLog] 10.69 Fixed the LPT Pin 16 Problem
in case anyone would really like to know what happened here...
Over the past 12 months or so a couple of folks reported that WL did not
handle pin 16 correctly.
I checked everything thoroughly and never found a problem in my shack.
This month, one kind sole actually put a voltmeter to his LPT port before
sending out emails about pin 16.
His report was that WriteLog was handling pin 1 differently than "everyone
else" (NA/CT/TR).
WL 10.29 changes WL's behavior on pin 1 (NOT PIN 16!).
Wayne
-----Original Message-----
From: writelog-admin@contesting.com
[mailto:writelog-admin@contesting.com]On Behalf Of TOMK5RC@aol.com
Sent: Saturday, December 22, 2001 15:49
To: writelog@contesting.com
Subject: [WriteLog] 10.69 Fixed the LPT Pin 16 Problem
I installed 10.69 last night and now my WX0B SO2R box works as
advertised. No more CW on Pin 16. Perhaps we will never know why it
happened, but I am a happy camper now.
Tom, K5RC
------=_NextPart_000_0033_01C18B3E.8E833040
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I used the voltmeter on LPT port a =
lot=20
lately! </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>In early CT versions, just pin 1 was =
enough for TTL=20
keying as it used natural STROBE function going low when =
activated.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>TR decided to key pin 16 with a =
positive=20
signal. Universal keying circuit needed NPN transistor for =
compatibility=20
between both programs. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>It claimed 50 mA keying capability =
which is way=20
bellow pin 1 sink ratings.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>ARRL handbook announced a circuit which =
used pin 1=20
as enable for PTT. It used plenty of relays for=20
various switching. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Writelog was keying both pins 1 and 16 =
affecting=20
smooth PTT operation in commercial SO2R boxes. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Free N1MMLogger didn't do that =
with pin=20
1.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Now we develop SO2R situation with =
pin 1=20
permanently low, pin 14 going low for Radio B and no power source for my =
miniature LPT adapter :-( </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>May I kindly ask for a pin 1 to go low =
at PTT time=20
and everything will work fine in USA and EU!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>73 de Mario, S56A, N1YU <A=20
href=3D"http://www.miletic.net";>www.miletic.net</A></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dw5xd@writelog.com href=3D"mailto:w5xd@writelog.com";>W. =
Wright, W5XD</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3DTOMK5RC@aol.com=20
href=3D"mailto:TOMK5RC@aol.com";>TOMK5RC@aol.com</A> ; <A=20
title=3Dwritelog@contesting.com=20
href=3D"mailto:writelog@contesting.com";>writelog@contesting.com</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Saturday, December 22, =
2001 5:33=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [WriteLog] 10.69 =
Fixed the=20
LPT Pin 16 Problem</DIV>
<DIV><BR></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D609462117-22122001>in case anyone would really like to =
know what=20
happened here...</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D609462117-22122001>Over the past 12 months or so a couple of =
folks=20
reported that WL did not handle pin 16=20
correctly.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D609462117-22122001>I checked everything thoroughly and never =
found a=20
problem in my shack.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D609462117-22122001></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D609462117-22122001>This month, one kind sole actually put a =
voltmeter to=20
his LPT port before sending out emails about pin=20
16.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D609462117-22122001></SPAN></FONT></FONT></FONT><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN class=3D609462117-22122001>His=20
</SPAN></FONT></FONT></FONT><FONT face=3DArial><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN class=3D609462117-22122001>report was that WriteLog was =
</SPAN></FONT></FONT></FONT><FONT face=3DArial><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN class=3D609462117-22122001>handling pin 1 differently =
than=20
"everyone else" (NA/CT/TR). </SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D609462117-22122001></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D609462117-22122001>WL 10.29 changes WL's behavior on pin 1 =
(NOT PIN=20
16!).</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D609462117-22122001></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D609462117-22122001>Wayne</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D609462117-22122001></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=3DTahoma size=3D2>-----Original =
Message-----<BR><B>From:</B>=20
writelog-admin@contesting.com =
[mailto:writelog-admin@contesting.com]<B>On=20
Behalf Of </B>TOMK5RC@aol.com<BR><B>Sent:</B> Saturday, December 22, =
2001=20
15:49<BR><B>To:</B> writelog@contesting.com<BR><B>Subject:</B> =
[WriteLog]=20
10.69 Fixed the LPT Pin 16 Problem<BR><BR></FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid"><FONT=20
face=3Darial,helvetica><FONT lang=3D0 face=3DArial size=3D2 =
FAMILY=3D"SANSSERIF">I=20
installed 10.69 last night and now my WX0B SO2R box works as =
advertised. No=20
more CW on Pin 16. Perhaps we will never know why it happened, but I =
am a=20
happy camper now.<BR><BR>Tom, K5RC</FONT>=20
</FONT></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0033_01C18B3E.8E833040--
|