[WT-support] OmniRig & CW keying
dl2alf
dl2alf at arcor.de
Tue May 4 06:56:09 CEST 2021
Hi all,
after running the May VHF contest here with new setup I am facing some new
problems.
My aimed setup is as follows:
- IC-9700
- CAT via OmniRig (mandatory due to multiple access from different
applications to rig needed)
- Win-Test V4.30
The only significant difference to previous setup is the connection via
OmniRig instead of a plain serial connection.
Everything went well until I tried to use the CW keyer from Win-Test
(Traditionally, CW keying was done via RTS/DTR status lines).
This function completely fails, so that I had to switch back to traditional
setup.
Meanwhile, I did some investigations on this topic.
I see two ways to get CW keying via OmniRig working:
#1: Use OmniRig status lines similar to serial connection
- feature is available at the OmniRig ActiveX interface
- is not supported by Win-Test so far
- may cause timing problems
#2: Use CW send text command supported by ICOM
- possible to send any text via CI-V
- I modified the great IcomScripts collection by Bob, N6TV, to get this
working (add IC-9700 as device, add some code for escape handling)
Id prefer #2 BUT:
If I define a new F1 command script for CQ, I was not able to access the
standard CW messages defined as $F1 .. $F8 so I must hardcode a new CQ text
in the script.
Not the best choice. Furthermore, I was not able to send it repeatedly as a
CQ loop does.
The best solution I came up with so far is to redefine CW standard texts
into #ICOMPLAY(
CQ
CQ
DE
) which runs the ICOM send text script with the
original text message.
Works but is also not the best choice as the defines seem to be stored
contest-specific in the *.wt4 files.
Any ideas?
73 de Frank, DL2ALF
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210504/12b1b5d4/attachment.html>
More information about the Support
mailing list