Since I don't see anyone else trying to help, and you've
provided some pretty amazing diagnostics, I feel oblidged
to suggest SOMEthing.
Have you tried a null modem adapter on the USB serial adapter?
It almost sounds like the send and receive lines are flipped.
That would suggest it believes it's a terminal node or a modem, I forget.
If you're still having problems, I'll try thins myself over the weekend.
73, GL de Byron
At 20:11 2000-10-05 -0500, WA9ALS - John wrote:
>SRI bandwidth, but here are some specifics:
>
>If I put the RS-232 tester in the standard serial port (COM 1) on the
>back of the laptop and boot up:
>
>TD, RTS, and DTR all come up GREEN, turn to RED, then back to GREEN
>during bootup.
>
>When I tell Writelog there's a rig on COM 1, RTS and DTR stay GREEN, but
>TD turns RED, except for periodic green-flickering that I interpret as
>rig polling.
>
>If I now plug the 1000MP's CAT cable into the tester, DSR, CD, and CTS
>also
>come on GREEN, and now both TD and RD flicker green in sync with the CAT
>indicator on the MP.
>
>All is well, and Writelog is showing the freq and mode of the rig.
>DX4WIN also works with this port.
>********
>Now to compare the Targus USB->serial adaptor (COM 2):
>
>During bootup, instead of all three TD, RTS, and DTR changing colors
>together, I get TD and DTR RED, and RTS GREEN instead of all 3 GREEN.
>
>However, when I tell Writelog or DX4WIN there's a rig on COM 2, RTS and
>DTR stay
>GREEN, but TD turns RED, except for periodic green-flickering that I
>interpret as rig polling. So far, so good - just like the other port!
>
>If I now plug the rig's CAT cable into the tester, DSR, CD, and CTS also
>come on GREEN, and the TD light flickers - BUT THE RD DOES NOT!! And, of
>course, Writelog or DX4WIN is not reading the freq and mode of the rig.
>*******
>Now to recheck, put the MP back into the COM 1 port on the back of the
>laptop, and all is working again.
>
>So everything is the same between the 2 ports EXCEPT that there is no
>apparent received data from the CAT connection when the USB->serial port
>is used. Does that help you see something I could do to get it going??
>Maybe a communications parameter problem, e.g. baud rate, parity, or
>stop bits? Seems like that would make sense - rig is asking for info,
>but not talking the right language! However, I KNOW that N-8-2 is the
>correct setting, and that is in the Writelog ini file. I've also
>checked the place in Windoze where you can specify com parameters, but
>the Writelog author told me that Writelog does it's own thing from its
>ini file and pays no attention to the Windows settings anyway, and it
>doesn't make it work to change those to N-8-2. Anything else come to
>mind? Tnx
>
>------------------------------------------------------------
>WA9ALS - John
> email: jfleming@shelbynet.net
>homepage: http://www.qsl.net/wa9als
> logbook: http://www.qsl.net/wa9als/search.htm
>
>
>
>
>--
>WWW: http://www.writelog.com/
>Submissions: writelog@contesting.com
>Administrative requests: writelog-REQUEST@contesting.com
>Problems: owner-writelog@contesting.com
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|