I have the problem Mike describes below on my two PCI serial ports. It is
not WL having the problem, it is the way the cards buffer the commands from
WL.
Two solutions:
- There is a setting in the writelog.ini file for time delay before
beginning to transmit, and time delay before dropping PTT at the end of a
transmission. A little experimentation and I was able to find a time delay
at end that kept PTT on long enough for the buffered characters to complete.
- Move your FSK transmit to an on-board COM port (or to another COM port
board). I tried both of these with success on my set up.
Randy, K5ZD
> -----Original Message-----
> From: owner-writelog@contesting.com
> [mailto:owner-writelog@contesting.com]On Behalf Of Mike Mellinger WA0SXV
> Sent: Monday, January 22, 2001 11:59 PM
> To: writelog@contesting.com
> Subject: Re: [WriteLog] USB ports
>
>
>
> Actually, the White Heat (and Belkin) problem with sending FSK in kind of
> interesting. I suspect a problem with Writelog control of the comm ports.
>
> In essence, what appears to happen is this:
>
> 1. Writelog turns on PTT.
> 2. Writelog sends FSK characters, assuming that they are NOT buffered
> and therefore it won't finish until they are finished.
> 3. Writelog drops PTT.
>
> Unfortunately, it appears that the characters are buffered. So all
> characters are properly sent, but step 2 finishes early due to
> the buffering
> and the transmitter no longer has PTT somewhere along the way. If you
> control PTT by hand while all of this is happening, the characters are
> properly sent.
>
> Of course, we also have the other Writelog oddity. Using the
> normal COMTROL
> PCI boards, DX4WIN (and others) will control the rig off of a COMTROL
> Rocketport port. Writelog will not.
>
> Bizarre.
>
> 73,
> Mike WA0SXV
>
>
> --
> 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
|