Rich,
I found this same thing but it only happened to me maybe 10 times or so
(didn't know if it was my keyboard or not).
I ended up using the brand new version 6.79 and moved the Icom times to 400
and 500 or something similar and I was very happy with the way it ran. I
didn't get any 'noncw' entries in the log. When I use a DVP that seems to
tax the frequency reading the most (for some reason) (keep that in mind for
testing).
I had an earlier concern about band map blinking but it again seemed ok (and
blinked). I started out using 6.85 ( I think) and quickly switched.
Mike W9RE
> -----Original Message-----
> From: trlog-bounces@contesting.com
> [mailto:trlog-bounces@contesting.com]On Behalf Of KL7RA
> Sent: Monday, December 01, 2003 12:18 AM
> To: TRLog
> Subject: [Trlog] No msg launch during WW code
>
>
> Found occasionally when calling CQ and hitting the [enter] key the
> rpt didn't get sent. Not enough times to worry about but later when
> I was working Ja's at my standard rate of one every three minutes
> I could spend time to catch the error. The freq would disappear then
> blink back on again. I would see the mode flash to SSB (or not) and
> back to CW. This would explain the message not being sent as the
> DVK was not on.
>
> I remembered Mike's,W9RE, post about the Icom response timeout
> with mode problems so I moved it from 100 to 500 and that stopped
> the problem.
>
> This was version 6.74. I believe Tree has fixed it in a later version
> with the "Fliter radio message length" so it's probably a non-issue
> but for those of us that stay back a few releases this error might catch
> you as it did me.
>
> Other then the above which required the default to be changed, 6.74
> worked perfect.
>
> Rich KL7RA
>
> _______________________________________________
> Trlog mailing list
> Trlog@contesting.com
> http://lists.contesting.com/mailman/listinfo/trlog
>
_______________________________________________
Trlog mailing list
Trlog@contesting.com
http://lists.contesting.com/mailman/listinfo/trlog
|