+1
Stewart/G3YSX
> On 23 Jul 2020, at 15:46, Paul Christensen wrote:
>
> I dread the thought that the K4 includes an embedded variant of the
> RemoteRig -- as a means to accelerate product development. Although it's
> probably too late for Elecraft to consider a real, internal WK chip (and
: Thursday, July 23, 2020 10:47 AM
To: elecraft@mailman.qth.net
Subject: [Elecraft] K4 and RTTY question
"This includes RemoteRig boxes, the YCCC SO2R Box, the Mortty, etc.
None
of them will pass the WKTEST program."
After two years, I gave up. RemoteRig's internal keyer and COM port
On
Behalf Of Paul Christensen
Sent: Thursday, July 23, 2020 10:47 AM
To: elecraft@mailman.qth.net
Subject: [Elecraft] K4 and RTTY question
>"This includes RemoteRig boxes, the YCCC SO2R Box, the Mortty, etc.
>None
of them will pass the WKTEST program."
After two years, I gave up. Remo
>"This includes RemoteRig boxes, the YCCC SO2R Box, the Mortty, etc. None
of them will pass the WKTEST program."
After two years, I gave up. RemoteRig's internal keyer and COM port path
when using N1MM are flat-out awful unless the Internet connection has
extremely low latency and jitter.
Apologies to the list. The message quoted below was meant just
for N6TV.
[I have BCCed the author of RUMlogNG.]
By way of explanation, After my last post on this thread, I got
a telephone call from TV Bob, N5TV. We discussed the problem and
narrowed it down quite a bit.
We assume that
I thought that the suggestion to include WinKey and FSK hardware was a
good one. It would be nice to plug directly in instead of needing
additional peripherals. There already is an internal keyer in most
newer transceivers so business was taken away from the many external
keyer
I got spotted 3 times with AE6JV and once with E6JV. ??!!??
Headed back to Rivermead after watching the comet. TTYL
73 Bill AE6JV
---
Bill Frantz| Truth and love must prevail | Periwinkle
(408)348-7900 | over lies
I don't think the logging software is the problem. Since the KY
command works for both CW and RTTY, I tried an experiment: I
switched the mode using the K3's front panel from Data to CW and
the problem did not occur. (I listened to the monitor output.)
The UI for the program still showed RTTY,
My intent was not to emulate the exact H/W and its problems, but the APIs used
(eg, programs using TinyFSK send [ , then text and ] to end the TX). I know
TinyFSK has issues. But I was not intending that Elecraft copy the problems.
I just wanted something similar to what TinyFSK does ( send
On Mon, Jul 20, 2020 at 7:03 AM Joe DeVincentis wrote:
> Personally, I'd like to see the K4 support something like the TinyFSK
> protocol for doing RTTY.
>
There's really no urgent reason to do this once the KY host command is
improved to allow message stacking with interrupt capability. If
+1 for winkeyer support. 73 de AI6KG
On Mon, Jul 20, 2020, 7:03 AM Joe DeVincentis wrote:
> Personally, I'd like to see the K4 support something like the TinyFSK
> protocol for doing RTTY.
>
> It could present multiple serial ports. one for CAT, one for FSK and one
> for Keying. The FSK
Personally, I'd like to see the K4 support something like the TinyFSK protocol
for doing RTTY.
It could present multiple serial ports. one for CAT, one for FSK and one for
Keying. The FSK could emulate tinyFSK and the keyer could emulate the K1EL
keyers. That way programs don't need to
Bill,
Before it can be "fixed" in the K4, the logging software has to be fixed to
send the proper KY command. If it is sending KY*somes-string*;,
then the messages are not going to be chained. If it is sending KYW
*some-string*;, then the messages should be properly chained, perhaps with
a very
I'm getting ready for NAQP RTTY today, and I am reminded of an
old bug using the KY CAT command to send RTTY text. I am using
RUMlogNG on my MacBook Pro in contest mode which uses the CAT
interface to send and receive RTTY. (It also uses CAT with CW.)
If I try to chain output, e.g. press the
14 matches
Mail list logo
