[WriteLog] Com Port problems

Ron Lodewyck rwlodewyck at gmail.com
Thu Mar 14 19:20:47 EDT 2019


If windows did an upgrade recently check Device Manager and verify the COM port number assignments haven’t changed. 
GL,
Ron N6EE


Sent from my iPhone

> On Mar 14, 2019, at 4:09 PM, Don Hill AA5AU <aa5au at bellsouth.net> wrote:
> 
> Sorry, this one has me stumped. 
> 
> If you can't get radio control to work with any program then I would suspect
> a hardware problem - either COM port board or radio or cable between them.
> 
> Do you have any other devices that use a COM port that you can test with
> like a rotator or old KAM or PK232?
> 
> Does this radio have a DB9 connector on the back like the TS-870 and other
> Kenwood radios? If so, have you tried reseating the connector on each end or
> trying a different cable?
> 
> Have you tried resetting the radio back to default?
> 
> Don AA5AU
> 
> -----Original Message-----
> From: WriteLog [mailto:writelog-bounces at contesting.com] On Behalf Of James
> Brown
> Sent: Thursday, March 14, 2019 2:02 PM
> To: John; writelog at contesting.com
> Subject: Re: [WriteLog] Com Port problems
> 
> Hi John
> 
> Checked in Device Mgr.  Not using USB to serial port converter .  Am using
> PCI com port board.
> 
> Port says that it is working ok.  Baud rate set at 9600, same as in
> Writelog.
> 
> 
> 
>> On Thu, Mar 14, 2019 at 2:44 PM John <jlockj at earthlink.net> wrote:
>> 
>> 
>> Hi Jim,
>> 
>> Have you checked:
>> 
>> 1)  Control Panel > Device Manager > Ports
>> To see if the computer is seeing the USB to serial port chip in the
>> TS-590S?  What Serial Port Number and Baud rate does it say it is?
>> 
>> 2)  The TS-590S menu item for Port Speed?  9600?  **Mine is set for
>> 57600**  Works with Writelog and WSJT-X.
>> 
>> John  W0DC
>> 
>> ------------------------------------
>> 
>>> On 3/14/2019 12:29 PM, James Brown wrote:
>>> Hi Don and Group
>>> 
>>> Trying to set up for BARTG.
>>> 
>>> The TS590 is not communicating with the Wrtielog.  The port setting in
>> the
>>> radio are correct, ie.9600, 8 1.  Same in Writelog.
>>> 
>>> Com 5 selected in Wrtielog.  Same as always.  Tried COM 6, but same
>> result.
>>> 
>>> I tried a different logging program that uses that com port, and it is
>> not
>>> communicating with the port either.
>>> 
>>> This happened once before, after messing around with N1MM.  But, then it
>>> straightened out somehow, and started communicating ok in Writelog.
> Dont
>>> know how.
>>> 
>>> Checked the connections and cables.  Seem ok.
>>> 
>>> Any suggestions? I am at a loss.
>>> 
>>> Thanks      Jim      W4LC
>>> _______________________________________________
>>> WriteLog mailing list
>>> WriteLog at contesting.com
>>> http://lists.contesting.com/mailman/listinfo/writelog
>>> WriteLog on the web:  http://www.writelog.com/
>>> 
>> 
> _______________________________________________
> WriteLog mailing list
> WriteLog at contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/
> 
> _______________________________________________
> WriteLog mailing list
> WriteLog at contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/


More information about the WriteLog mailing list