Jindra,
yes, just keep us posted when your done!
73
Gernot
PS: I guess you wanted to reply to the list.. you have to be careful
most email programs reply to the sender by default.
Hi Gernot,
That could be it... I am afraid I was expecting something like 40 chars
and did not bother reading full details :-)
It seems the correct approach is to split exchange into chunks of 24
chars max and instead of dumb chaining follow each chunk by KY; and wait
for KY2; response, and only then continue.
I was hoping to manage it without making the control program too busy,
obviously KX3 needs a little bit more attention.
Anyway, it is doing quite nice things in my Chrome packaged app. I can
manually switch everything and especially receive all responses with
100% reliability.
Hopefully it will be usable for comfortable work in PSK-D and FSK-D
modes (that is my main motivation), maybe for some CW contesting.
Would you be interested when it is done?
73 Jindra
Am 27.09.2015 um 00:31 schrieb [email protected]:
Jindra,
check the KYn; response for error / success. See manual re. the KY
command. Might be a buffer overrun ? The buffer is limited to 24 chars
according to the specs.
73
Gernot, DF5RF
Am 26.09.2015 um 20:18 schrieb Jindřich Vavruška:
Hello,
I am programming yet another utility to control KX3 and I encountered a
strange (inconsistent) behavior.
In digital mode contest traffic it is necessary to switch to RX
immediately
after exchange has been sent. I learned that the way to do this is to
send KYW<text
to send>;RX; to the serial interface. The RX; after KY will ensure
immediate switch to receive and the W in KYW will ensure that the RX;
will
be interpreted after text sending is finished, i.e. will not interrupt
ongoing transmission.
What surprised me is that when I send something like:
KYWCQ CQ CQ DE OK4RM;KYW DE OK4RM OK4RM PSE K;RX;
i.e. split a long text in shorter chunks. In such case I believe all
the
texts are sent (I have to verify that yet, though) but the effect of the
final RX; disappears.
Is this a mistake in my program workflow or could that be a firmware
peculiarity? (I hesitate to call it a bug as everything else seems to
work
perfectly.)
I think there will be no problem for a contest but if I wanted to use
the
same pattern for longer exchanges in casual digi QSOs that would make
things a little bit more complicated.
Thanks for any advice,
Jindra
OK4RM
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
