To my memory I had this problem a couple of years ago. WriteLog seemed
to set the time interval to the amount of time between the beginning of
one CQ message to the next.. And, a 5 or 6 second CQ with a T value of
4 caused a never ending CQ. I remember having to set the time at 10
seconds plus to get a decent amount of non transmit time between CQs.
Somewhere in the last year or two this changed to the T variable being
the amount of between CQs. In looking at the WriteLog history file and
I found this.
Version 10.10 October, 1999
Auto CQ delay now is from end of message to beginning of next if WriteLog
can see the end of the message. Some DVK?s, CW keyers, and TNCs do not
support this.
So my guess is either your TNC doesn't support this or you need to
upgrade to a newer version
73 W0ETCetera, etcetera
On Sat, 28 Sep 2002 14:30:53 -0500 "WA9ALS - John" <wa9als@starband.net>
writes:
> Way too short. 10-15 sec is more like it. Maybe the timer starts
> from the
> beginning of the CQ.
>
> ----- Original Message -----
> From: "Ian McCloy" <ian_mccloy@telus.net>
> To: <WriteLog@contesting.com>
> Sent: Tuesday, September 17, 2002 12:20 PM
> Subject: [WriteLog] Auto Cq
>
>
>
> i had a major problem trying to use the automatic cq in the
> contest.
>
> i had it setup for 4.0 seconds and on f2 for calling cq
>
> problem was it would never stop transmitting cq until i hit the esq
> key
> any ideas what is wrong
>
> Ian VA7SW
>
>
> --- StripMime Report -- processed MIME parts ---
> multipart/alternative
> text/plain (text body -- kept)
> text/html
> ---
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
>
>
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
>
>
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
|