Any news on how to run remote CW with V1.2 for IC-7300?

Has anyone made it to run a cw keyer with wfview-solution? Or is this still a feature to be done in the future? Thanks for your help.
regards,
Suitbert, DF2PI

3 Likes

I too am very interested in this topic.

Paul B

2 Likes

I three am interested in getting CW to work threw WFView.
Anybody with any work around or additions to make this work?

No news yet, but several of the wfview developers are skilled CW ops and believe me, there is pressure to get this working one way or another.

For now, I think MCW via fldigi is your best bet.

You can also use the pseudo-term device with any program that supports Icom’s built-in keyer CI-V commands.

–E
de W6EL

Is this what y’all want? Just a window where you can type things and it becomes this command?

—E
de W6EL

Please, no window where we have to type characters!!!
Remote CW is like this: connect a keyer / paddle to your client-PC, where you have your wfview-client running. Use the keyer / paddle to transmit CW via LAN/WAN the wfview-server, which is connected to the transceiver (IC-7300). Maybe we will have to add some additional hardware components, to get the keyer/paddle running, like USB-serial-adapter or something like that.
regards,
Suitbert, DF2PI

1 Like

To be fair Suitbert, that is YOUR definition of remote CW, others may (and do) have an alternative view.

Wfview is not just used with the IC7300, so a solution that works with the built-in LAN server on other rigs must also be sought. Exactly what form that takes is still to be determined but we “hope” to support both keyboard and key/paddle sending.

73 Phil M0VSE

Hello Phil,
well your are right, others may have another definition of CW. I only have tried to adapt / describe the standard-method of doing CW with a key / keyer to the remote-world. Even this seems to me as being the more challenging method of doing CW remote.
And of course I am aware of, the IC-7300 is only one example of many other transceivers supported by wfview. Thanks a lot.
vy 73, Suitbert, DF2PI

I responded to Phil in private – I do lots of cw contests and out of 300+ contacts, I mostly use macros and if I touch the paddle once or twice, that’s it.

The positive part of sending using the remote control CW is that if you feed the rig “PA3MET”, it will send PA3MET, exactly with all the params that are attached to it. speed, ratio etc.

I sometimes hear people sending this “-.-.–.- -.-.–.-” – and yes I know what they mean biut ot’s now what’s being sent. I am not aware of “-.-.–.-” being a shortcut/definition of CQ.

Now consider high speed cw, like 30 wpm; if you have latencies and or drop outs, and you switch the rig on/off, you will have botched code as shown above; and that’s when things go reasonably well.

We should not discuss “what is real cw”. I don’t even care if people use a decoder themselves. Else we can say that FT* is also not real; WSPR is not real, etc.

We have one goal I think and that is to have a way to make CW readable at the other hand and quickly too with low latencies. If you look at RSBA1 – there is no paddle / key support either, unless you use a kbd.

At ome time in my life I used an SDR type rig with a remote display and the latencies were over 150ms which made SSB contests already a problem. Let alone a high speed cw call.

We’ll have to see what we can do with paddles/keyers.

and as a final note – if generaly skip bad cw handwriting. Too much work to discern shoddy written text. I mean CQ is easy and even that some people will f* up …

But then again. that’s my view on it…

The question mentioned above was “Is this what y’all want?” So I described my way of doing CW. Maybe I am the only one (doing so for 45 years now). Just tried to “transfer” it to the remote world. No discussion on “what is real cw”, no try to convince someone of using a keyboard or whatever. Just to give my personal answer the first question … Thank you.

Suitbert,

You are not the only one!

My remote CW definition is exactly as how you explained above and I am looking for a solution exactly same as you described.

73, Murat TA1DB

1 Like

I think the point is, there is no single answer to the question :slight_smile:

We have potential methods of achieving true remove keyed CW, but it is fraught with difficulties and will require very careful implementation.

Keyboard or macro based CW is much easier to implement, which is why it is likely to be the first solution that we provide.

Eventually, we hope to be able to do both.

73 Phil M0VSE

1 Like

I operate CW with wfview both with an IC-705 and IC-7300. Simplest way is to use Fldigi. With Fldigi you can either use CAT to send CW or connect a USB CW keyer. Works great and does not require modifications to wfview which might add complexity.

73,
Harry W3YJ

1 Like

Are you using this remote ?

73 La7hm. Pål

Harry,

Could you please explain a bit how you do it.

I run Flrig on a Raspberry Pi server which is connected to my rig with cat and keyer inputs through 2 separate usb-serial converters (1 for cat 1 for keyer). I also get audio from rig’s audio jack and loop back it using a usb sound card. From a remote client I can connect to the server over Ethernet with FlDigi, I can control the rig, send cw messages - from keyboard unfortunately ! - and I can hear audio from client as well. These all work very good.

What I want to do is to connect my paddle the the client. I found this remote morse key project but this is not exactly what I want.

73, Murat

1 Like

Unfortunately I am not aware of any method for connecting a CW key to a computer and using it to send CW. When I operate my IC-7300 remotely, I just accept that and use Fldigi as a CW keyboard. For my IC-705, I’m always within a few feet of the radio, so I use wfview or kappanhang to connect to it wirelessly, run Fldigi for CW, and plug my N3ZN paddle (the best!) into the radio.

73,
Harry Bloomberg W3YJ