About a week ago, I posted that I could not get my PK232 to play as a
packet TNC on COM7 , but it worked on that port in DX4WIN. Later I found
that i could not get Writelog to recognize the PK232 on any COM port COM 5
or higher ( I have up to COM10). Writelog did however recognize the PK232
if it was on COM3 or COM4 just fine. All COM ports COM3-COM 10 are the same
manufacturer (SiiG)
The TNC sits way over on left out of the way and the computer is on the
floor just to the right of my chair. There are two shielded cables in the
line on a 12' run cable ( computer ...6ft DB-9 /DB-25 .+ 6ft DB-25/DB-25
...PK232).
Tonight I isolated the problem to the DB-25/DB-25 extension cable...I
think. Detection was pure luck.I have a 2nd PK232 sitting on the shelf that
I was checking out this evening in preparation for getting ready to sell
it. I had hooked it to COM4 when as an afterthought thinking my above
mentioned problem might be a problem with the PK232 and not Writelog. So I
hooked it to COM 7 and sure enough it played just fine under Writelog. Next
I changed out he cables to PK232 #1 and it too now played just fine on
COM7. I ohmed out the DB-25/DB-25 and it was just fine pin for pin.
So puzzle fans what is it about this cable that COM5-COM10 and writelog
don't like...any theorys?
Dave
NR1DX
nr1dx@arrl.net
"A man who picks a cat up by the tail learns a lesson he can learn no other
way" .... Mark Twain
|