Just to clarify - I didn't find a fix. I just toughed it out. The dropout
likely affected the leading %R more than anything. I thought about adding a
space to all the messages as a cushion but never got around to it.
I have no idea what is causing it. I balked at the idea of trying to go
down rev on the router during the contest. The only other thing I could
think of to try was to re-install Writelog on the theory that something was
damaged. That wasn't happening mid contest either. ;)
If anyone has any other ideas I'd love to hear them ;) Thanks! - jeff wk6i
On Mon, Sep 25, 2017 at 6:00 PM, Jeff Stai <wk6i.jeff@gmail.com> wrote:
> I'm reporting this even though it is version 11, and the things that were
> changed this time one would think shouldn't have had any effect (Microham
> and 2tone versions). This setup has worked fine since sometime in early
> 2015. I plan to get
> caught up to version 12 before the Makrothen next month.
>
> The issue is when transmitting messages:
>
> 1. about 1/3 of the time the PTT would drop at the start of the message,
> just a momentary hiccup and then continue;
> 2. my F2 exchange message - %R%C 599 3 nv %E - would freeze after the %C
> and stay in transmit.
>
> #2 by itself was very rare, but if I preceded it with my call stacking
> message - %R%Ctu now %L %E - it would freeze after the %C in the exchange
> much more frequently. (The %C in call stacking never froze.)
>
> Other messages with %C also never froze. When it froze, the transmit print
> in the main RTTY window also froze. ESC killed transmit and I could try
> again.
>
> One other quirk. When #2 by itself froze, it was stuck there. It would
> freeze again and again until I sent a different message.
>
> My operating position is SO3R with one PC per radio - two K3S and one K3.
> Two of the PCs use Microham u2R routers for the FSK duties and one uses
> serial ports.
>
> This only happened on one of the three PCs. This one has the K3S and
> Microham router. Running Win7 32-bit, with all updates current. Writelog
> 11.24J
>
> Only two things were updated, other than Windows: I got around to
> installing the latest 2tone(16.02a to 16.11a), and the Microham version had
> been updated by my station host (8.4.6 to 8.8.2) - and one "maintenance"
> app had been installed.
>
> When I observed the hiccup I immediately went looking for something else
> running that might interfere, so I uninstalled that maintenance app. No
> effect. No other extraneous programs or processes were observed in Task
> Manager.
>
> I next went back to the previous version of 2tone. No luck.
>
> What I did notice next was that the Microham version on the other PC that
> didn't exhibit this behavior was not upgraded. It's still at 8.4.6.
>
> I can't imagine how the Microham version could be related, other than I
> noticed a "Stuff" checkbox is a new thing on the Ports tab, which does have
> something to do with the flow of FSK. I tried it both ways with no effect
> on this behavior.
>
> I hope this information is useful. 73 jeff wk6i
>
>
> --
> Jeff Stai ~ wk6i.jeff@gmail.com
> Twisted Oak Winery ~ http://www.twistedoak.com/
> Facebook ~ http://www.facebook.com/twistedoak
>
--
Jeff Stai ~ wk6i.jeff@gmail.com
Twisted Oak Winery ~ http://www.twistedoak.com/
Facebook ~ http://www.facebook.com/twistedoak
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|