|
BG6LH
Hi, I am very new to fldigi. maybe my question was a very old one. I am using both SCU-LAN10, SCU-17 with my FTDX10. SCU-17 connect from FTDX10's RS-232 and DATA jack, then go to a Raspberry Pi4. RPI4 running WSJT-X for FT8. All of them work very stable. Now, I complied fldigi-4.1.23.19 on my RPI4, by reading this helpful post: https://sourceforge.net/p/fldigi/wiki/debian_howto/I am sure I have installed the fldigi, portaudio, pluseaudio correct. Because I can sent RTTY, PSKUSB signal out, here it from rig's MONI audio, and watch it from ALC, PO, SWR indicator. However, when I switched to CW mode in fldigi, and clicked the CQ macro F1, nothing was send out. there was no audio, no ALC, no PO, no SWR. BUT, the rig's PTT was activated on, the waterfall of fidigi and the volume bar of PulesAudio Volume Control shown there was audio generated.......that's really puzzle Does I lost anything important? I hope you can give some suggestion. Thanks! BG6LH 2022/11/21
|
|
|
On Mon, 21 Nov 2022 10:17:08 -0800 "BG6LH via groups.io" <jamflying@...> wrote: Hi, I am very new to fldigi. maybe my question was a very old one.
I am using both SCU-LAN10, SCU-17 with my FTDX10.
SCU-17 connect from FTDX10's RS-232 and DATA jack, then go to a
Raspberry Pi4. RPI4 running WSJT-X for FT8.
All of them work very stable.
Now, I complied fldigi-4.1.23.19 on my RPI4, by reading this helpful
post: https://sourceforge.net/p/fldigi/wiki/debian_howto/
I am sure I have installed the fldigi, portaudio, pluseaudio correct.
Because I can sent RTTY, PSKUSB signal out, here it from rig's MONI
audio, and watch it from ALC, PO, SWR indicator.
However, when I *switched to CW mode* in fldigi, and clicked the CQ
macro F1, nothing was send out. there was *no audio, no ALC, no PO,
no SWR*. BUT, the rig's PTT was activated on, the waterfall of
fidigi and the volume bar of PulesAudio Volume Control shown there
was audio generated.......that's really puzzle
Does I lost anything important? I hope you can give some suggestion.
Thanks!
BG6LH
2022/11/21 See if this helps: http://www.w1hkj.com/FldigiHelp/cw_dtr_rts_keying.htmlEd W3NR
|
|
|
On Mon, 21 Nov 2022 10:17:08 -0800 "BG6LH via groups.io" <jamflying@...> wrote: Hi, I am very new to fldigi. maybe my question was a very old one.
I am using both SCU-LAN10, SCU-17 with my FTDX10.
SCU-17 connect from FTDX10's RS-232 and DATA jack, then go to a
Raspberry Pi4. RPI4 running WSJT-X for FT8.
All of them work very stable.
Now, I complied fldigi-4.1.23.19 on my RPI4, by reading this helpful
post: https://sourceforge.net/p/fldigi/wiki/debian_howto/
I am sure I have installed the fldigi, portaudio, pluseaudio correct.
Because I can sent RTTY, PSKUSB signal out, here it from rig's MONI
audio, and watch it from ALC, PO, SWR indicator.
However, when I *switched to CW mode* in fldigi, and clicked the CQ
macro F1, nothing was send out. there was *no audio, no ALC, no PO,
no SWR*. BUT, the rig's PTT was activated on, the waterfall of
fidigi and the volume bar of PulesAudio Volume Control shown there
was audio generated.......that's really puzzle
Does I lost anything important? I hope you can give some suggestion.
Thanks!
BG6LH
2022/11/21 Another choice: http://www.w1hkj.com/FldigiHelp/cw_cat_keying.htmlEd W3NR
|
|
|
Is your radio being put into CW mode? If so, it's
probably expecting to receive CW signals via *FSK* input from the
SCU-17 instead of AFSK (audio) which is Fldigi's main mechanism to
send/receive digital modes. Fldigi does supports CW FSK via a
Winkeyer interface or a NanoIO interface. Maybe this could be
supported using the new serial CW port keying mechanism (
http://www.w1hkj.com/FldigiHelp/cw_dtr_rts_keying.html ). This
assumes the FSK signal on your SCU-17 can be addressed via one of
the serial port signals (DTR, etc). If that a try.
--David
KI6ZHD
On 11/21/2022 10:17 AM, BG6LH via
groups.io wrote:
toggle quoted messageShow quoted text
Hi, I am very new to fldigi. maybe my question was a
very old one.
I am using both SCU-LAN10, SCU-17 with my FTDX10.
SCU-17 connect from FTDX10's RS-232 and DATA jack, then go to
a Raspberry Pi4.
RPI4 running WSJT-X for FT8.
All of them work very stable.
Now, I complied fldigi-4.1.23.19 on my RPI4, by reading this
helpful post:
https://sourceforge.net/p/fldigi/wiki/debian_howto/
I am sure I have installed the fldigi, portaudio, pluseaudio
correct.
Because I can sent RTTY, PSKUSB signal out, here it from rig's
MONI audio, and watch it from ALC, PO, SWR indicator.
However, when I switched to CW mode in fldigi,
and clicked the CQ macro F1, nothing was send out. there was no
audio, no ALC, no PO, no SWR. BUT, the rig's PTT was
activated on, the waterfall of fidigi and the volume bar of
PulesAudio Volume Control shown there was audio
generated.......that's really puzzle
Does I lost anything important? I hope you can give some
suggestion.
Thanks!
BG6LH
2022/11/21
|
|
|
Did you leave the rig in the same mode as for PSK31? Do not put the rig into CW, just like you said, fldigi in CW, but rig in USB or what ever USB mode is use for PSK31.
Hi, I am very new to fldigi. maybe my question was a very old one. I am using both SCU-LAN10, SCU-17 with my FTDX10. SCU-17 connect from FTDX10's RS-232 and DATA jack, then go to a Raspberry Pi4. RPI4 running WSJT-X for FT8. All of them work very stable. Now, I complied fldigi-4.1.23.19 on my RPI4, by reading this helpful post: https://sourceforge.net/p/fldigi/wiki/debian_howto/I am sure I have installed the fldigi, portaudio, pluseaudio correct. Because I can sent RTTY, PSKUSB signal out, here it from rig's MONI audio, and watch it from ALC, PO, SWR indicator. However, when I switched to CW mode in fldigi, and clicked the CQ macro F1, nothing was send out. there was no audio, no ALC, no PO, no SWR. BUT, the rig's PTT was activated on, the waterfall of fidigi and the volume bar of PulesAudio Volume Control shown there was audio generated.......that's really puzzle Does I lost anything important? I hope you can give some suggestion. Thanks! BG6LH 2022/11/21
|
|
|
With the FTDX10 like the FTDX101 you should see PC keying option
in CW mode settings on radio,
Set to RTS and set FLdigi to suit here, using the standard
comport (not the cat enhanced comport which is separate)
in 'USE Separate Keying Serial Port" dropdown select shown;
Set CW keyline dropdown select to RTS.
Set the radio CAT RTS option off. use the standard comport for
all ptt in applications with RTS., even those with afsk.soundcard
use., PSK.. etc.
No afsk /soundcard is required for CW, and you use true CW-U mode
direct and have use of the decoder and other in radio CW features.
73
Adrian ... vk4tux
On 22/11/22 04:17, BG6LH via groups.io
wrote:
toggle quoted messageShow quoted text
Hi, I am very new to fldigi. maybe my question was a very old one.
I am using both SCU-LAN10, SCU-17 with my FTDX10.
SCU-17 connect from FTDX10's RS-232 and DATA jack, then go to
a Raspberry Pi4.
RPI4 running WSJT-X for FT8.
All of them work very stable.
Now, I complied fldigi-4.1.23.19 on my RPI4, by reading this
helpful post:
https://sourceforge.net/p/fldigi/wiki/debian_howto/
I am sure I have installed the fldigi, portaudio, pluseaudio
correct.
Because I can sent RTTY, PSKUSB signal out, here it from rig's
MONI audio, and watch it from ALC, PO, SWR indicator.
However, when I switched to CW mode in fldigi,
and clicked the CQ macro F1, nothing was send out. there was no
audio, no ALC, no PO, no SWR. BUT, the rig's PTT was
activated on, the waterfall of fidigi and the volume bar of
PulesAudio Volume Control shown there was audio
generated.......that's really puzzle
Does I lost anything important? I hope you can give some
suggestion.
Thanks!
BG6LH
2022/11/21
|
|
|
BG6LH
Thanks all of your helpful suggestions! That let me notice that, I made big miss understandings about FLDIGI. So, I did a simply try : taking a way SCU-LAN10, SCU-17, Just leaving a USB cable connect RPI4 to FTDX10 ONLY...... CW FKS KEYING WORKS!! :D both RTS and DTR, even on FLRIG, they all can do keying well! It's really a simple config only about Modem/CW/RTS-DTR Keying.....nothing about audio, hardware PTT, separate serial port, etc... So, I turn back to the SCU-LAN10, SCU-17, connect them back to FTDX10, RS-232C....made a same config in Modem/CW/RTS-DTR Keying...However, IT NO KEYING AGAIN... :~( I test in different ways: * FLDIGI in CW, rig in CW, there is no signal out, only PTT is ON. * FLDIGI in CW, rig in any DATA mods, the AFSK works well. * FLDIGI in CW, rig in any SSB mods, FUNNY, I can get something like FSK happen, my rig TX like a FULL BK-IN, actually it's setting on SEMI....signals was sent but not in morse code...sounds like timing was chaos. When I slow down WPM about 5, I can tell they are really morse code.... I think the problem was on SCU-17 and FTDX10's settings. Here is a table, the last column is my FTDX10's final setting. "--" means as same as DEFAULT. Hope you can give help, I am very grateful!
|
OPERATION SETTING
|
Sub-Options
|
DEFAULT
|
YAESU's PRESET for FT8
|
SCU-LAN10
(on USB)
|
SCU-17
(on RS-232C&DATA)
|
|
GENERAL
|
232C Rate
|
4800 (bps)
|
|
|
38400 (bps)
|
|
|
232 TIME OUT TIMER
|
10ms
|
|
|
--
|
|
OPERATION SETTING
|
|
|
|
|
|
|
GENERAL
|
CAT RATE
|
38400 (bps)
|
--
|
--
|
--
|
|
|
CAT TIME OT TIMER
|
10ms
|
--
|
--
|
--
|
|
|
CAT RTS
|
ON
|
OFF
|
ON
|
OFF
|
|
|
TX TIME OUT TIMER
|
OFF
|
|
1-30(min)
|
--
|
|
TX GENTERAL
|
VOX SELECT
|
MIC
|
|
DATA
|
DATA
|
|
RADIO SETTING
|
|
|
|
|
|
|
MODE SSB
|
SSB MODE SOURCE
|
REAR
|
|
--
|
--
|
|
|
REAR SELECT
|
DATA
|
|
USB
|
DATA
|
|
|
RPTT SELECT
|
DAKY
|
|
|
--
|
|
MODE AM
|
AM MODE SOURCE
|
REAR
|
|
--
|
--
|
|
|
REAR SELECT
|
DATA
|
|
USB
|
--
|
|
|
PRTT SELECT
|
DAKY
|
|
|
--
|
|
MODE FM
|
FM MODE SOURCE
|
REAR
|
|
--
|
--
|
|
|
REAR SELECT
|
DATA
|
|
USB
|
--
|
|
|
RPTT SELECT
|
DAKY
|
|
|
--
|
|
MOD PSK/DATA
|
TX BPF SEL
|
300-2700Hz
|
50-3050HZ
|
|
50-3050Hz
|
|
|
DATA MOD SOURCE
|
REAR
|
|
|
--
|
|
|
REAR SELECT
|
DATA
|
USB
|
|
DATA
|
|
|
RPORT GAIN
|
50
|
10
|
|
10
|
|
|
PRTT SELECT
|
DAKY
|
RTS
|
|
RTS
|
|
|
LCUT FREQ
|
300 (50Hz/step)
|
100
|
|
100
|
|
|
HCUT FREQ
|
3000 (50Hz/step)
|
3200
|
|
3200
|
|
|
AGC FAST DELAY
|
160 (20ms/step)
|
--
|
|
--
|
|
|
AGC MID DELAY
|
500 (20ms/step)
|
--
|
|
--
|
|
|
AGC SLOW DELAY
|
1500 (20ms/step)
|
--
|
|
--
|
|
|
LCUT SLOPE
|
18db/oct
|
--
|
|
--
|
|
|
HCUT SLOPE
|
18db/oct
|
--
|
|
--
|
|
MODE RTTY
|
RPTT SELECT
|
DAKY
|
|
|
--
|
|
CW SETTING
|
|
|
|
|
|
|
MODE CW
|
CW FREQ DISPLAY
|
PITCH OFFSET
|
|
|
--
|
|
MODE CW
|
PC KEYING
|
OFF
|
|
|
RTS
|
|
|
CW AUTO MODE
|
OFF
|
|
|
--
|
|
|
CW BK-IN TYPE
|
SEMI
|
|
|
--
|
|
KEYER
|
KEYER TYPE
|
ELEKEY-B
|
|
|
--
|
|
[FUNC] MAIN MENU
|
|
|
|
|
|
|
|
KEYER
|
OFF
|
|
|
--
|
|
|
BK-IN
|
OFF
|
|
|
--
|
|
|
|
Dave, W1HKJ
You do not need the SCU-17 etc
with the FTdx10. That interface is redundant and can conflict
with the transceiver internal virtual ports on the USB
interface.
David
On 11/22/22 13:56, BG6LH via groups.io
wrote:
toggle quoted messageShow quoted text
Thanks all of your helpful suggestions!
That let me notice that, I made big miss understandings about
FLDIGI.
So, I did a simply try : taking a way SCU-LAN10, SCU-17, Just
leaving a USB cable connect RPI4 to FTDX10 ONLY......CW
FKS KEYING WORKS!! :D
both RTS and DTR, even on FLRIG, they all can do keying well!
It's really a simple config only about Modem/CW/RTS-DTR
Keying.....nothing about audio, hardware PTT, separate
serial port, etc...
So, I turn back to the SCU-LAN10, SCU-17, connect them back to
FTDX10, RS-232C....made a same config in Modem/CW/RTS-DTR
Keying...However, IT NO KEYING AGAIN... :~(
I test in different ways:
* FLDIGI in CW, rig in CW, there is no signal out, only PTT is ON.
* FLDIGI in CW, rig in any DATA mods, the AFSK works well.
* FLDIGI in CW, rig in any SSB mods, FUNNY, I
can get something like FSK happen, my rig TX like a FULL BK-IN,
actually it's setting on SEMI....signals was sent but not in morse
code...sounds like timing was chaos. When I slow down WPM about 5,
I can tell they are really morse code....
I think the problem was on SCU-17 and FTDX10's settings. Here is a
table, the last column is my FTDX10's final setting.
Hope you can give help, I am very grateful!
|
OPERATION SETTING
|
Sub-Options
|
DEFAULT
|
YAESU's
PRESET for FT8
|
SCU-LAN10
(on USB)
|
SCU-17
(on
RS-232C&DATA)
|
|
GENERAL
|
232C Rate
|
4800 (bps)
|
|
|
38400 (bps)
|
|
|
232 TIME OUT TIMER
|
10ms
|
|
|
--
|
|
OPERATION
SETTING
|
|
|
|
|
|
|
GENERAL
|
CAT RATE
|
38400 (bps)
|
--
|
--
|
--
|
|
|
CAT TIME OT TIMER
|
10ms
|
--
|
--
|
--
|
|
|
CAT RTS
|
ON
|
OFF
|
ON
|
OFF
|
|
|
TX TIME OUT TIMER
|
OFF
|
|
1-30(min)
|
--
|
|
TX GENTERAL
|
VOX SELECT
|
MIC
|
|
DATA
|
DATA
|
|
RADIO SETTING
|
|
|
|
|
|
|
MODE SSB
|
SSB MODE SOURCE
|
REAR
|
|
--
|
--
|
|
|
REAR SELECT
|
DATA
|
|
USB
|
DATA
|
|
|
RPTT SELECT
|
DAKY
|
|
|
--
|
|
MODE AM
|
AM MODE SOURCE
|
REAR
|
|
--
|
--
|
|
|
REAR SELECT
|
DATA
|
|
USB
|
--
|
|
|
PRTT SELECT
|
DAKY
|
|
|
--
|
|
MODE FM
|
FM MODE SOURCE
|
REAR
|
|
--
|
--
|
|
|
REAR SELECT
|
DATA
|
|
USB
|
--
|
|
|
RPTT SELECT
|
DAKY
|
|
|
--
|
|
MOD PSK/DATA
|
TX BPF SEL
|
300-2700Hz
|
50-3050HZ
|
|
50-3050Hz
|
|
|
DATA MOD SOURCE
|
REAR
|
|
|
--
|
|
|
REAR SELECT
|
DATA
|
USB
|
|
DATA
|
|
|
RPORT GAIN
|
50
|
10
|
|
10
|
|
|
PRTT SELECT
|
DAKY
|
RTS
|
|
RTS
|
|
|
LCUT FREQ
|
300 (50Hz/step)
|
100
|
|
100
|
|
|
HCUT FREQ
|
3000 (50Hz/step)
|
3200
|
|
3200
|
|
|
AGC FAST DELAY
|
160 (20ms/step)
|
--
|
|
--
|
|
|
AGC MID DELAY
|
500 (20ms/step)
|
--
|
|
--
|
|
|
AGC SLOW DELAY
|
1500 (20ms/step)
|
--
|
|
--
|
|
|
LCUT SLOPE
|
18db/oct
|
--
|
|
--
|
|
|
HCUT SLOPE
|
18db/oct
|
--
|
|
--
|
|
MODE RTTY
|
RPTT SELECT
|
DAKY
|
|
|
--
|
|
CW SETTING
|
|
|
|
|
|
|
MODE CW
|
CW FREQ DISPLAY
|
PITCH OFFSET
|
|
|
--
|
|
MODE CW
|
PC KEYING
|
OFF
|
|
|
RTS
|
|
|
CW AUTO MODE
|
OFF
|
|
|
--
|
|
|
CW BK-IN TYPE
|
SEMI
|
|
|
--
|
|
KEYER
|
KEYER TYPE
|
ELEKEY-B
|
|
|
--
|
|
[FUNC] MAIN
MENU
|
|
|
|
|
|
|
|
KEYER
|
OFF
|
|
|
--
|
|
|
BK-IN
|
OFF
|
|
|
--
|
|
|
|
The scu-lan10 should be connecting to your radio using the usb
line, which makes it unavailable for PC programs.
You connect the rs-232 to your PC for programs like FLdigi to use
for CAT and rts use etc.
An audio interface is needed as the scu-lan10 takes over the
radio usb codec. however just use a simple audio interface like
xxgcomms etc via rtty/data jack,
or just connect to your Pi sound system, so that You have the
rs-232 available for CAT with FLdigi etc, Wasting a port on the
scu-17 is unnecessary.
FLdigi afsk will use DAKY for ptt with the rtty/data xxgcomms
type audio/ptt interface.
73
Adrian ... vk4tux
On 23/11/22 06:06, BG6LH via groups.io
wrote:
toggle quoted messageShow quoted text
Thanks all of your helpful
suggestions!
That let me notice that, I made big miss understandings about
FLDIGI.
So, I did a simply try : taking a way SCU-LAN10, SCU-17, Just leaving a USB cable connect RPI4
to FTDX10 ONLY......CW
FKS KEYING WORKS!! :D
both RTS and DTR, even on FLRIG, they all can do keying well!
It's really a simple config only
about Modem/CW/RTS-DTR Keying.....nothing about audio,
hardware PTT, separate serial port, etc...
So, I turn back to the SCU-LAN10, SCU-17, connect them back to
FTDX10, RS-232C....made a same config in Modem/CW/RTS-DTR
Keying...However, IT NO KEYING AGAIN... :~(
I test in different ways:
* FLDIGI in CW, rig in CW, there is no signal out, only PTT is ON.
* FLDIGI in CW, rig in any DATA mods, the AFSK works well.
* FLDIGI in CW, rig in any SSB mods, FUNNY, I can get something like FSK happen, my rig
TX like a FULL BK-IN, actually it's setting on SEMI....signals was
sent but not in morse code...sounds like timing was chaos. When I
slow down WPM about 5, I can tell they are really morse code....
I think the problem was on SCU-17 and FTDX10's settings. Here is a
table, the last column is my FTDX10's final setting.
"--" means as same as DEFAULT.
Hope you can give help, I am very grateful!
|
OPERATION SETTING
|
Sub-Options
|
DEFAULT
|
YAESU's
PRESET for FT8
|
SCU-LAN10
(on USB)
|
SCU-17
(on
RS-232C&DATA)
|
|
GENERAL
|
232C Rate
|
4800
(bps)
|
|
|
38400 (bps)
|
|
|
232 TIME OUT TIMER
|
10ms
|
|
|
--
|
|
OPERATION SETTING
|
|
|
|
|
|
|
GENERAL
|
CAT RATE
|
38400
(bps)
|
--
|
--
|
--
|
|
|
CAT TIME OT TIMER
|
10ms
|
--
|
--
|
--
|
|
|
CAT RTS
|
ON
|
OFF
|
ON
|
OFF
|
|
|
TX TIME OUT TIMER
|
OFF
|
|
1-30(min)
|
--
|
|
TX GENTERAL
|
VOX SELECT
|
MIC
|
|
DATA
|
DATA
|
|
RADIO SETTING
|
|
|
|
|
|
|
MODE SSB
|
SSB MODE SOURCE
|
REAR
|
|
--
|
--
|
|
|
REAR SELECT
|
DATA
|
|
USB
|
DATA
|
|
|
RPTT SELECT
|
DAKY
|
|
|
--
|
|
MODE AM
|
AM MODE SOURCE
|
REAR
|
|
--
|
--
|
|
|
REAR SELECT
|
DATA
|
|
USB
|
--
|
|
|
PRTT SELECT
|
DAKY
|
|
|
--
|
|
MODE FM
|
FM MODE SOURCE
|
REAR
|
|
--
|
--
|
|
|
REAR SELECT
|
DATA
|
|
USB
|
--
|
|
|
RPTT SELECT
|
DAKY
|
|
|
--
|
|
MOD PSK/DATA
|
TX BPF SEL
|
300-2700Hz
|
50-3050HZ
|
|
50-3050Hz
|
|
|
DATA MOD SOURCE
|
REAR
|
|
|
--
|
|
|
REAR SELECT
|
DATA
|
USB
|
|
DATA
|
|
|
RPORT GAIN
|
50
|
10
|
|
10
|
|
|
PRTT SELECT
|
DAKY
|
RTS
|
|
RTS
|
|
|
LCUT FREQ
|
300
(50Hz/step)
|
100
|
|
100
|
|
|
HCUT FREQ
|
3000
(50Hz/step)
|
3200
|
|
3200
|
|
|
AGC FAST DELAY
|
160
(20ms/step)
|
--
|
|
--
|
|
|
AGC MID DELAY
|
500
(20ms/step)
|
--
|
|
--
|
|
|
AGC SLOW DELAY
|
1500
(20ms/step)
|
--
|
|
--
|
|
|
LCUT SLOPE
|
18db/oct
|
--
|
|
--
|
|
|
HCUT SLOPE
|
18db/oct
|
--
|
|
--
|
|
MODE RTTY
|
RPTT SELECT
|
DAKY
|
|
|
--
|
|
CW SETTING
|
|
|
|
|
|
|
MODE CW
|
CW FREQ
DISPLAY
|
PITCH OFFSET
|
|
|
--
|
|
MODE CW
|
PC KEYING
|
OFF
|
|
|
RTS
|
|
|
CW AUTO MODE
|
OFF
|
|
|
--
|
|
|
CW BK-IN TYPE
|
SEMI
|
|
|
--
|
|
KEYER
|
KEYER TYPE
|
ELEKEY-B
|
|
|
--
|
|
[FUNC]
MAIN MENU
|
|
|
|
|
|
|
|
KEYER
|
OFF
|
|
|
--
|
|
|
BK-IN
|
OFF
|
|
|
--
|
|
|
|
BG6LH
Thanks, Dave! I also noticed SCU-17's virtual ports may conflict to FTDX10's virtual ports too. When FTDX10's PC KEYING was set to RTS/DTR, it will set to his main USB jack on rear. So, by reading the manual, I make a little trying to set its PC KEYING to DAKY. then FLDIGI RTS FSK WORKS~~! :D But only on RTS, not on DTR, whatever, it works!! 
|
|
|
BG6LH
Yes, Adrian!
As you're saying, SCU-LAN10 occupied the only USB port for YAESU itself. We have to use RS-232 and DATA jacks to do everything.So I tried many ways to test how can they work.Thanks for all of the help in this topics~~Now my FTDX10 can be REAL Remote Control and QSO in SSB/FT8/FSK Keying.
Let me share my final setting here. compare to rig's default, yaesu's PRESET for FT8, and SCU-LAN10 required, the SCU-17 is my final setting.
"--" mean as same as default. 
|
|
|
