Date   

#fldigi #fldigi

John Griffiths
 

Wefax Mode. Slant setting can be fixed depending on which station being received. Align however always reverts to default zero, even in 'auto'. 
I've checked out the config file but have been unable to find any line referencing this parameter.
Does anyone know if there's a way to 'fix' the align field value?


RsID not changing frequency (MFSK64 > MFSK32)

Dana Myers
 

Listening to Shortwave Radiogram #181, after sending pictures in MFSK64 using the usual
1500Hz center frequency, the program sent an RsID at 2000Hz to return to MFSK32, which
is correctly recognized as a mode-switch the MFSK32, but does not change the center
frequency to 2000Hz.

I have 'Searches Passband', 'Mark/prev freq/mode' selected (checked) in the configuration
dialog. I have 'Disable freq change' *not* checked in the configuration dialog.

I've seen this on 4.1.16 and 4.1.17 both.

Any idea what I might be missing?

Tnx es 73,
Dana  K6JQ


Re: CW Modem #modem

Pat
 

i wonder if it is some of your settings?
I used it in the ARRL160 meter cw contest
and decoded great!   You do have to set the recieve
setting up a bit.. I like it at 25 wpm.  I wonder if you have
QRN?


Re: CW Modem #modem

Pat
 

Bob.. some are handicap and not able to use a keyer
Murf
n7uvh


Re: Fldigi/Flrig and Winkeyer with a Ten-Tec Pegasus

Bob McGraw - K4TAX <rmcgraw@...>
 

Since the file location is selected when one chooses the RigCAT option, the parent directory is available for selecting the location.  Either works.  

Bob, K4TAX



On Dec 7, 2020, at 10:54 AM, Gene Rozea <gene_rozea@...> wrote:



Just for clarification, the 538 .xml file goes into the RIGS directory, not the parent directory.

 

 

From: Karl Heimbach
Sent: Monday, December 7, 2020 10:52 AM
To: winfldigi@groups.io
Subject: Re: [winfldigi] Fldigi/Flrig and Winkeyer with a Ten-Tec Pegasus

 

Thanks for the suggestions, but no success yet.  Downloaded the 538.xml  file and copied it to the fldigi directory.  No change.  Fldigi may not be the problem and perhaps it might have something to do with flrig.

In flrig configuration, under PTT, and then looking at CW mode PTT, if you uncheck "disable PTT in CW mode", all words typed will be sent by the winkeyer to fldigi, and the radio will key and transmit a steady carrier and then go back into receive once the winkeyer has sent the string.  If the "disable PTT in CW mode" box is checked, then winkeyer will send characters, the radio will transmit the only first word until it encounters a space, and then go back into receive.

I do not have a serial line connected for PTT.

Also, using the Hamlib selection in fldigi for control of the Pegasus, behavior is the same as with flrig and having the "disable PTT in CW mode" unchecked.

Had no luck with Rigcat at all.

Also, not sure of how to put the Pegasus into semi break-in.

Thanks for the help.

Karl

 


Re: Fldigi/Flrig and Winkeyer with a Ten-Tec Pegasus

Gene Rozea
 

Just for clarification, the 538 .xml file goes into the RIGS directory, not the parent directory.

 

 

From: Karl Heimbach
Sent: Monday, December 7, 2020 10:52 AM
To: winfldigi@groups.io
Subject: Re: [winfldigi] Fldigi/Flrig and Winkeyer with a Ten-Tec Pegasus

 

Thanks for the suggestions, but no success yet.  Downloaded the 538.xml  file and copied it to the fldigi directory.  No change.  Fldigi may not be the problem and perhaps it might have something to do with flrig.

In flrig configuration, under PTT, and then looking at CW mode PTT, if you uncheck "disable PTT in CW mode", all words typed will be sent by the winkeyer to fldigi, and the radio will key and transmit a steady carrier and then go back into receive once the winkeyer has sent the string.  If the "disable PTT in CW mode" box is checked, then winkeyer will send characters, the radio will transmit the only first word until it encounters a space, and then go back into receive.

I do not have a serial line connected for PTT.

Also, using the Hamlib selection in fldigi for control of the Pegasus, behavior is the same as with flrig and having the "disable PTT in CW mode" unchecked.

Had no luck with Rigcat at all.

Also, not sure of how to put the Pegasus into semi break-in.

Thanks for the help.

Karl

 


Re: Fldigi/Flrig and Winkeyer with a Ten-Tec Pegasus

Karl Heimbach
 

Thanks for the suggestions, but no success yet.  Downloaded the 538.xml  file and copied it to the fldigi directory.  No change.  Fldigi may not be the problem and perhaps it might have something to do with flrig.

In flrig configuration, under PTT, and then looking at CW mode PTT, if you uncheck "disable PTT in CW mode", all words typed will be sent by the winkeyer to fldigi, and the radio will key and transmit a steady carrier and then go back into receive once the winkeyer has sent the string.  If the "disable PTT in CW mode" box is checked, then winkeyer will send characters, the radio will transmit the only first word until it encounters a space, and then go back into receive.

I do not have a serial line connected for PTT.

Also, using the Hamlib selection in fldigi for control of the Pegasus, behavior is the same as with flrig and having the "disable PTT in CW mode" unchecked.

Had no luck with Rigcat at all.

Also, not sure of how to put the Pegasus into semi break-in.

Thanks for the help.

Karl


Re: CW Modem #modem

Gary Woods
 

On Sun, 6 Dec 2020 15:37:58 -0600, you wrote:

Perfect sending from your straight key, all time.
Oh, crud! "Autotune" for the fist? How can I stretch out the "K" at
the end of a transmission for emphasis?
--
Gary Woods O- K2AHC Public keys at home.earthlink.net/~garygarlic, or get 0x1D64A93D via keyserver
fingerprint = E2 6F 50 93 7B C7 F3 CA 1F 8B 3C C0 B0 28 68

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Re: CW Modem #modem

Gary Woods
 

On Sun, 6 Dec 2020 17:24:11 -0500, you wrote:

I hear some of the worst "fists" ever these days on 40m, with the dah's maybe 5 times as long as a "dit" short sound. FLDIGI goes nuts trying to create print from most hand-key sent CW. Kind of a CW slang, of sorts.
And I can spot a cootie key from the minimal ratio of dots to dashes.
Of course, age, cold shack, and essential tremor haven't done my Navy
airdale fist any good. Gotta fine a "Navy knob" for my hand key.
--
Gary Woods O- K2AHC Public keys at home.earthlink.net/~garygarlic, or get 0x1D64A93D via keyserver
fingerprint = E2 6F 50 93 7B C7 F3 CA 1F 8B 3C C0 B0 28 68

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Re: Fldigi/Flrig and Winkeyer with a Ten-Tec Pegasus

Dave
 

Are you operating the Pegasus is semi or full break-in?  If not, I suggest you see if that makes a difference.

David

On 12/6/20 9:09 PM, Karl Heimbach wrote:

I've been struggling with making my Ten-Tec Pegasus send more than one word while using a Winkeyer.  I can send through the Winkeyer with a paddle to the Pegasus without any issue.  The Pegasus via the Winkeyer will send characters via the keyboard until a space is encountered and then it stops and returns to receive. I am using flrig as the control for fldigi.  I run both flrig/fldigi under Windows and under Linux and experience exactly the same issue with the Pegasus.

I've used the same Winkeyer and computer with Fldigi and Flrig without issue with a Xiegu G90.  I also used the Winkeyer and Fldigi with hamlib to key my Icom 735 during last weekend's CW contest.

The Winkeyer is new to me.  I am the original owner of the Pegasus and it was the third one sold by Ten-Tec.  I've been using flrig and fldigi with the Pegasus for many years.

Is there something different in either the configuration of flrig or fldigi that is causing the one word and out transmission?

Karl - W5QJ


Re: CW Modem #modem

 

I managed to get fldigi to decode my straight key - once. It took a lot of practice and was hard work! Now need to get my receiving back up to speed.

 

Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: Bob McGraw - K4TAX
Sent: 06 December 2020 22:28
To: winfldigi@groups.io
Subject: Re: [winfldigi] CW Modem #modem

 

Why not just use a keyer, let it apply the correct ratio of element length?  Sure works very nice with my Elecraft K3S.  

 

I practice in test mode with the radio and let FLDIGI decide.  If it decodes 100%, I’m good. 

Bob, K4TAX

 

 



On Dec 6, 2020, at 3:54 PM, Artie Langston <artielangston@...> wrote:



I think the challenge is not actually in signal processing, but in some sort of artificial intelligence. Fldigi reads extremely well considering, when it's another machine doing the sending. With the peculiarities of various humans, on various keys, not so much.

 

This leaves the question, is designing an AI of that sophistication going to be worth the time and investment required?

 

I have noticed that my Digital Audio Workstation I use in my work as a musician can do amazing things with what is referred to as Quantizing a musical performance to various degrees. It can take a rhythmically  imprecise musical performance and then "line it up" correctly with the beats and time signature, so it sounds pretty perfect.

 

Perhaps once the WPM is detected by the software, it could then quantize the CW before decoding, thus delivering something like W1AW or keyboard generated copy even from a shaky fist.

 

73

 

Artie

 


Re: Fldigi/Flrig and Winkeyer with a Ten-Tec Pegasus

Ed W3NR
 

I was one of the original testers along with Dave. This was pre flrig, and I was using a CMOS 4. But my Pegasus was long gone by the time flrig came about. See what trying rigCAT does and go from there. I also was an early tester for the 735 as well as the TTOmni6. All before flrig.
Ed W3NR


Re: Fldigi/Flrig and Winkeyer with a Ten-Tec Pegasus

Bob McGraw - K4TAX <rmcgraw@...>
 

You may need the 538.XML file on the FLDIGI Source Forge site.  Download the file and save in your FLDIGI folder.  I recall the Pegasus control is the same was the Jupiter. 

Bob, K4TAX



On Dec 6, 2020, at 9:11 PM, Karl Heimbach <kheimbach@...> wrote:

I've been struggling with making my Ten-Tec Pegasus send more than one word while using a Winkeyer.  I can send through the Winkeyer with a paddle to the Pegasus without any issue.  The Pegasus via the Winkeyer will send characters via the keyboard until a space is encountered and then it stops and returns to receive. I am using flrig as the control for fldigi.  I run both flrig/fldigi under Windows and under Linux and experience exactly the same issue with the Pegasus.

I've used the same Winkeyer and computer with Fldigi and Flrig without issue with a Xiegu G90.  I also used the Winkeyer and Fldigi with hamlib to key my Icom 735 during last weekend's CW contest.

The Winkeyer is new to me.  I am the original owner of the Pegasus and it was the third one sold by Ten-Tec.  I've been using flrig and fldigi with the Pegasus for many years.

Is there something different in either the configuration of flrig or fldigi that is causing the one word and out transmission?

Karl - W5QJ


Fldigi/Flrig and Winkeyer with a Ten-Tec Pegasus

Karl Heimbach
 

I've been struggling with making my Ten-Tec Pegasus send more than one word while using a Winkeyer.  I can send through the Winkeyer with a paddle to the Pegasus without any issue.  The Pegasus via the Winkeyer will send characters via the keyboard until a space is encountered and then it stops and returns to receive. I am using flrig as the control for fldigi.  I run both flrig/fldigi under Windows and under Linux and experience exactly the same issue with the Pegasus.

I've used the same Winkeyer and computer with Fldigi and Flrig without issue with a Xiegu G90.  I also used the Winkeyer and Fldigi with hamlib to key my Icom 735 during last weekend's CW contest.

The Winkeyer is new to me.  I am the original owner of the Pegasus and it was the third one sold by Ten-Tec.  I've been using flrig and fldigi with the Pegasus for many years.

Is there something different in either the configuration of flrig or fldigi that is causing the one word and out transmission?

Karl - W5QJ


Re: CW Modem #modem

Mark Hubelbank
 

Actually, that is the challenge. I have been doing things for years that machines mostly can't do.

On 12/6/2020 10:52 AM, Nathan Rosenthal wrote:
Mark, you do realize that Morse code was never meant to be decoded by a machine. Characters have varying lengths and there are no start and stop signals. The ear and brain are much better at deciphering inconsistent code signals than any machine. 

-- 
Mark Hubelbank
NorthEast Monitoring
141 Parker St
Suite 200
Maynard, MA, 01754 - USA
mhubel@...
978-443-3955


Re: CW Modem #modem

Bob McGraw - K4TAX <rmcgraw@...>
 

Why not just use a keyer, let it apply the correct ratio of element length?  Sure works very nice with my Elecraft K3S.  

I practice in test mode with the radio and let FLDIGI decide.  If it decodes 100%, I’m good. 

Bob, K4TAX



On Dec 6, 2020, at 3:54 PM, Artie Langston <artielangston@...> wrote:


I think the challenge is not actually in signal processing, but in some sort of artificial intelligence. Fldigi reads extremely well considering, when it's another machine doing the sending. With the peculiarities of various humans, on various keys, not so much.

This leaves the question, is designing an AI of that sophistication going to be worth the time and investment required?

I have noticed that my Digital Audio Workstation I use in my work as a musician can do amazing things with what is referred to as Quantizing a musical performance to various degrees. It can take a rhythmically  imprecise musical performance and then "line it up" correctly with the beats and time signature, so it sounds pretty perfect.

Perhaps once the WPM is detected by the software, it could then quantize the CW before decoding, thus delivering something like W1AW or keyboard generated copy even from a shaky fist.

73

Artie


Re: CW Modem #modem

K3eui <K3eui@...>
 

Interesting conversation about different ways of perceiving CW.
I hear some of the worst "fists" ever these days on 40m, with the dah's maybe 5 times as long as a "dit" short sound. FLDIGI goes nuts trying to create print from most hand-key sent CW.  Kind of a CW slang, of sorts.


When I was a teenager (60 yr ago) I had no trouble copying anyone sending 20-30 wpm with those Vibroplex semi-automatic bugs, or even a straight key. But in my older years (now 75) I find the thrill of copying poorly sent CW not as rewarding, and straining now.

I wonder, had FT8 or PSK31 been "invented" before CW (on/off keying of a carrier) would be so obsessed with this mode called CW? PSK and FT8 take up less spectrum than CW, and create fewer fewer problems.

With CW, the brain has distinguish a tone, or no signal, but the darn "noise" is in our way. There is never silence, especially on noisy HF bands these days.  My mind can not (virtually) eliminate the noise the way it used to when I was younger.  In fact, the lower pitch CW tone around 600 Hz is harder now for me to understand than a higher pitch tone of around 1000 Hz.  Why is that?

I find myself operating CW more now with my (Icom) rig in USB-D mode, and tune in CW to 1000 Hz  to  1500 Hz on the FLDIGI waterfall. 
That sound can be separated from the background "noise" more easily now. I like to run a 500 Hz bw but center it at 1500 Hz.

I'm not sure why I do this, but it is less tiring for my brain than listening to CW at 600 Hz pitch.
I'm a former bassoon player, so I did enjoy those bass sounds.

Barry  k3eui



On Dec 6, 2020, at 4:25 PM, Artie Langston <artielangston@...> wrote:

I think the challenge is not actually in signal processing, but in some sort of artificial intelligence. Fldigi reads extremely well considering, when it's another machine doing the sending. With the peculiarities of various humans, on various keys, not so much.

This leaves the question, is designing an AI of that sophistication going to be worth the time and investment required?

I have noticed that my Digital Audio Workstation I use in my work as a musician can do amazing things with what is referred to as Quantizing a musical performance to various degrees. It can take a rhythmically  imprecise musical performance and then "line it up" correctly with the beats and time signature, so it sounds pretty perfect.

Perhaps once the WPM is detected by the software, it could then quantize the CW before decoding, thus delivering something like W1AW or keyboard generated copy even from a shaky fist.

73

Artie


Re: CW Modem #modem

Artie Langston <artielangston@...>
 

If 3:1 is the 'ideal' ratio when it comes to being able to hear and differentiate between dots and dashes for the average to good operator, then a dot is simply, say, a dotted 16th note to the dash's quarter note. I'm going to record some people on air, and then try to quantize them in the music software, and see how that turns out. Maybe it could be like a speech processor for your fist. Perfect sending from your straight key, all time.

Or maybe, much more likely,  a complete waste of time. It will be fun any way.

Artie


On Sun, Dec 6, 2020 at 3:25 PM Artie Langston via groups.io <artielangston=gmail.com@groups.io> wrote:
I think the challenge is not actually in signal processing, but in some sort of artificial intelligence. Fldigi reads extremely well considering, when it's another machine doing the sending. With the peculiarities of various humans, on various keys, not so much.

This leaves the question, is designing an AI of that sophistication going to be worth the time and investment required?

I have noticed that my Digital Audio Workstation I use in my work as a musician can do amazing things with what is referred to as Quantizing a musical performance to various degrees. It can take a rhythmically  imprecise musical performance and then "line it up" correctly with the beats and time signature, so it sounds pretty perfect.

Perhaps once the WPM is detected by the software, it could then quantize the CW before decoding, thus delivering something like W1AW or keyboard generated copy even from a shaky fist.

73

Artie


Re: CW Modem #modem

Artie Langston <artielangston@...>
 

I think the challenge is not actually in signal processing, but in some sort of artificial intelligence. Fldigi reads extremely well considering, when it's another machine doing the sending. With the peculiarities of various humans, on various keys, not so much.

This leaves the question, is designing an AI of that sophistication going to be worth the time and investment required?

I have noticed that my Digital Audio Workstation I use in my work as a musician can do amazing things with what is referred to as Quantizing a musical performance to various degrees. It can take a rhythmically  imprecise musical performance and then "line it up" correctly with the beats and time signature, so it sounds pretty perfect.

Perhaps once the WPM is detected by the software, it could then quantize the CW before decoding, thus delivering something like W1AW or keyboard generated copy even from a shaky fist.

73

Artie


Re: CW Modem #modem

Gary Rondeau <grondeau@...>
 

I've been using FLDIGi's CW decoder for several years now.  It has been my "trainer" as I gradually really learn what CW sounds like.  There is no question that a trained ear is better than the decoder, but the issues are mostly on leading characters when the decoder is trying to track speeds.  I'm sure modern neural net approaches could eventually perform very well for even hand-sent code.  There could be improvements in handling over the pole flutter where maybe a neural net could "hear" the underlying message more like a human would.  

The present decoder serves very well, however, I've managed my CW DXCC using teh FLDIGI deocder and what my ear has learned along the way.  ITtprovides a very accessible entry point to the CW world that is a real benefit to the community.

These days I prefer to send using TTL serial logic using N1MM as the control program, but I keep FLDIGI on the RX signal.  Soon I may be able to dispense with the crutch...  but it has been a great aid getting to where I am.
Gary AF7NX

4321 - 4340 of 32572