I have not encountered (or heard reports of) problems with COMM PTT =
RTS (which is new in 11.23). In general the problem has occurred with
COMM PTT = Yes or Sync. However, since COM PTT = RTS is new, I would
not discount the possibility of an issue there.
73,
... Joe, W4TV
On 2014-12-07 11:24 PM, Ed Muns wrote:
That was indeed my problem. Sure enough, Comm PTT was set to 'RTS' instead
of 'No' in the Setup/Ports window for the second K3 receiver. PTT didn't
release only on my sub-receiver Rttyrite window and only about half the
time.
However, this setting reverts to 'RTS' when WriteLog is exited and reloaded.
The first receiver stays where I set it ... 'No'. So, the setting on that
one box is not sticky even with both the Configuration saved and the log
file saved. When I'm in the Ports window I always make sure Comm PTT is off
for all the radios, but forget to check it every time I load WriteLog.
I'd call this a bug, though there is a (inconvenient) work-around.
Ed W0YK
----------------------------------------------------------------------------
-
Joe W4TV wrote:
Make sure Writelog is *not* using "COM PTT" (PTT commands on the serial
port) as several rigs appear to have a subtle race condition between PTT
via CAT commands and hardware PTT.
My suspicion is that the rigs in question mask changes on the PTT input
while processing CAT PTT commands but ignore a CAT PTT off if the PTT
input is asserted ... then when unmasking the PTT input the transition
has been missed. I've never seen the issue (or heard reports of it)
in systems where COM PTT (or equivalent software PTT) has been disabled.
73,
... Joe, W4TV
On 2014-12-07 9:28 PM, Ed Muns wrote:
I have the same problem, but only when the K3 is FSK-keyed from a Rttyrite
window tied to the sub-receiver. It is intermittent, failing to release
PTT
about half the time, and behaves as though the %E is ignored in the
message.
Hitting ESC will release PTT, but it is a pain to constantly be hitting
ESC
throughout the contest.
I've never had this problem with a Rttyrite window tied to the main
receiver, but I can't figure out what the difference is. In your case, I
guess it is the single Rttyrite window linked to the main receiver.
I do not use a microKeyer, just simple homebrew FSK/PTT Com port cables.
I suspect that whatever the cause, it may be common to both our cases. It
"seems" to be in WriteLog, but not sure.
Ed W0YK
-----------------------------------------------------------------
Eric W3DQ wrote:
My station is a Microkeyer 2 and an Orion 565.
My plan was to use MTTY as my RTTY engine w/WL for today's 10m RTTY
contest.
I was able to receive well, but on TX it wouldn't stop (unkey) after the
message was sent.
Not sure what went wrong, as it worked with the same settings with N1MM.
I would guess that it's something to do with the PTT and/or keying line,
but beyond that, I haven't a clue.
Any thoughts?
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|