Hello!
Is there a maximum length for CW macro? It seems that more than 151 characters in the macro introduces problems. Here's an example that you can use to test and confirm this bug. I'm using K1EL Winkeyer WKUSB-SMT.
Defined CW macros:
F1:
cq cq cq de %mc %mc cq cq cq de %mc %mc pse k
F2:
%c de %mc %mc pse k
F3:
%c de %mc = gd dr om es tnx fer call = ur rst %r %r = my name is s i n i s a s i n i s a es my qth is i n d j i j a i n d j i j a = so hw? %c de %mc pse k
(Please note extra spaces in my name and QTH.)
I have tried removing extra spaces and entering any kind of arbitrary text to make the macro longer than 151 chars, always with the same result: the %c in the beginning gets shortened, and the part of F2 macro gets somehow inserted before %mc.
I'd be more than grateful if you'd address this bug and solve it in the next release of this otherwise great piece of software. :)
Thank you!
Thu, 2014-06-26 02:11
#1
yu1sx
CW message macro max length
Hi,
it seems it's limitation of message length directly in WinKeyer firmware. I just looked at source code and there is not any limit.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Can we then have a solution to call another message from the current one, that is, to link two or more messages by some macro in CQRLOG itself? Something like %f1 - %f10 (call the message defined under F1 - F10).
That way we'd be able to split longer messages in several parts, and the overall CW functionality would increase signifficantlly. :)
73 de YU1SX
This wouldn't help. CQRLOG sends to WinKeyer the whole text. The macros are replaced with right values inside the CQRLOG. If you have %f1 and %f10 in the macro text, CQRLOG will split the F1 and F10 messages and sends it to Winkeyer.
73 Petr
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Could CQRLOG somehow mimic the WinKeyer's standalone mode embedded messages feature? Let's say we have the following in CQRLOG's F1 memory: "rig hr is #2 es ant is dipole"
and in F2 memory: "icom ic7k"
CQRLOG would detect that there's an embedded message #2 in the first of it's internal CW memories, expand both messages and send the whole thing to WinKeyer:
"rig hr is icom ic7k es ant is dipole".
Would it be too much to wish for? :)
73 de YU1SX
Hello, Petr!
Unfortunately, it seems it can't be done, at least not the way I proposed. I tried to define two CW messages in CQRLOG, F1 and F2, that are together longer than WinKeyer's limit. Pressing F1 alone works, as well as F2. But pressing F2 immediately after F1 leads to the same problem as described earlier.
Thank you once again for the great piece of software. :)
73 de YU1SX
Hello, Petr!
I just got an answer from Hamcrafters regarding the problem with lengthy messages, and they say: "You are overflowing the input FIFO. You have to include a mechanism that receives and keeps track of the unsolicited status messages that are sent to the host asynchronously. Bit 0 in the register that indicates when the buffer is 2/3 full. "
So it's theoretically possible to send a novel to the Winkeyer, but sending it chunk by chunk, checking the async messages and keeping an eye to bit 0 in that register.
Best regards!
73 de YU1SX
Hi, Petr!
Did you read my last message in this thread? Would it be possible to implement this WinKeyer communication logic in CQRLOG?
Thank you!
73 de YU1SX