Date   
Re: Flrig with ft 891

Gunnn Er
 

Thanks Cliff
It is flrig that changes from data-u to am. The radio does not change.
I hope that is clearer.
Thanks 
KE8EZA 
Mike

Re: Flrig with ft 891

Cliff
 

Ok. I guessed that was what you meant, but didn’t want to assume it was.

Is this the first time you’ve used flrig?

If I understand correctly your problem is one of the following:  you put the radio mode in flrig to DATA-U and then it changes to AM in flrig or it’s still DATA-U in flrig and the radio is in AM? Please confirm the details of exactly what you are seeing.

In the first case it sounds like some sort of data corruption in the flrig data files so I would rename the directory c:/Users/<user name>/flrig.files and redo the flrig setup.

In the second case it sounds like some sort of communication issue or some menu setting on the radio isn’t correct. I don’t have a 891 to can’t verify anything, but maybe someone that does can be of help.

73,
Cliff, AE5ZA

On Apr 15, 2019, at 22:03, Gunnn Er <Gunnner@...> wrote:

I doubt it is your ignorance Cliff. If anything it is mine. I'm speaking of flrig on my computer screen which controls my ft 891. Not sure of the proper name.

KE8EZA 73

Re: Flrig with ft 891

Gunnn Er
 

I doubt it is your ignorance Cliff. If anything it is mine. I'm speaking of flrig on my computer screen which controls my ft 891. Not sure of the proper name.

KE8EZA 73

Re: Flrig with ft 891

Frank Mellott
 

for my Yaesu FTDX1200 I use Data U in FLRIG with no issues. I use FLRIG with both FLDIGI and WSJT-X.

Not sure why your 891 switches to AM.

Frank Mellott

KB3PQT

Re: Flrig with ft 891

Cliff
 

Pardon my ignorance, but what are you referring to as the “virtual tuner”?

73,
Cliff, AE5ZA

On Apr 15, 2019, at 19:14, Gunnn Er <Gunnner@...> wrote:

I have fldigi flrig and other fl programs connected to my yaesu ft 891. In the virtual tuner should I put usb or data-u? I've  tried both. If i put data -u it changes to am. Thanks in advance.

Flrig with ft 891

Gunnn Er
 

I have fldigi flrig and other fl programs connected to my yaesu ft 891. In the virtual tuner should I put usb or data-u? I've  tried both. If i put data -u it changes to am. Thanks in advance.

Re: A Solution To The Digital Mode Recognition Issue #Mode Recognition #mode

Gene Rozea
 

For receive ID to work, it requires that the transmitting station enable (and send) the mode ID prior to sending the message.

 


From: winfldigi@groups.io <winfldigi@groups.io> on behalf of Tony <DXDX@...>
Sent: Monday, April 15, 2019 6:29:04 PM
To: main@digitalradio.groups.io; multipsk@groups.io; winfldigi@groups.io
Subject: [winfldigi] A Solution To The Digital Mode Recognition Issue #Mode Recognition
 
All:

Most are aware that mode identification became a necessity more than a
decade ago as the number of sound card modes grew. The problem was
solved early on thanks to the Reed Solomon Identifier developed by
F6CTE. Yet here we are years later with more modes than ever before and
we're still not using RS-ID when we should be.

It's puzzling because there are only a handful of modes that are
discernible by sight and sound so we're left with dozens of variants and
sub-modes that require RS-ID in order to be identified quickly and
efficiently.

Prompt identification by observation is impossible because many variants
share the same modem with their primary counterparts so their appearance
is identical. We also have protocols that share the same modulation type
which have visual and audible similarities that make it difficult to
distinguish one from the other.

The solution would be to automate the process by having the TX-RSID
engage by default whenever a difficult-to-decipher mode is selected. An
easier approach for developers to implement might be to add a pop-up
that reminds the user to engage the TX/RX ID when selecting certain modes.

It's not only bad practice not use mode ID when attempting to
communicate with a protocol that's not easily recognized, it's a waste
of time. It also sends the wrong message to new comers and it's
certainly not the way to promote amateur radio to the public in a field
day setting or at other public events.

This video explains the need for mode identifiers:
https://www.youtube.com/watch?v=nwkz0GNpA0I

Tony -K2MO







A Solution To The Digital Mode Recognition Issue #Mode Recognition #mode

Tony
 

All:

Most are aware that mode identification became a necessity more than a decade ago as the number of sound card modes grew. The problem was solved early on thanks to the Reed Solomon Identifier developed by F6CTE. Yet here we are years later with more modes than ever before and we're still not using RS-ID when we should be.

It's puzzling because there are only a handful of modes that are discernible by sight and sound so we're left with dozens of variants and sub-modes that require RS-ID in order to be identified quickly and efficiently.

Prompt identification by observation is impossible because many variants share the same modem with their primary counterparts so their appearance is identical. We also have protocols that share the same modulation type which have visual and audible similarities that make it difficult to distinguish one from the other.

The solution would be to automate the process by having the TX-RSID engage by default whenever a difficult-to-decipher mode is selected. An easier approach for developers to implement might be to add a pop-up that reminds the user to engage the TX/RX ID when selecting certain modes.

It's not only bad practice not use mode ID when attempting to communicate with a protocol that's not easily recognized, it's a waste of time. It also sends the wrong message to new comers and it's certainly not the way to promote amateur radio to the public in a field day setting or at other public events.

This video explains the need for mode identifiers: https://www.youtube.com/watch?v=nwkz0GNpA0I

Tony -K2MO

Re: Issues Running the EA RTTY Contest This Past Weekend

 

N3FJP can also be used. FLDigi recently underwent a rewrite to include it for most of the major contests. I participated in the alpha testing and I can assure you it is bug free.

-----Original Message-----
From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of WA7SKG via Groups.Io
Sent: Monday, April 15, 2019 4:11 PM
To: winfldigi@groups.io
Subject: Re: [winfldigi] Issues Running the EA RTTY Contest This Past Weekend

Consider using N1MM+ for logging? I've used it in previous RTTY contests with fldigi and it worked great. That is what I plan to use with 7QP.

Michael WA7SKG (Operating RTTY and PSK31 for 7QP under W7PRA, ORCRO/ORWHE, 8 POINTS PER DIGITAL CONTACT!)


Jim Ruff via Groups.Io wrote on 4/7/19 8:54 PM:
I was operating the latest version of Fldigi with a KX3/KXPA100 and
using AClog regular log, not their contest log and encountered the
following issues:
1. When logging the qso, it logged properly into he Fldigi log, but in
the AClog it said DIGI not RTTY and it didn't log the frequency.
2. From time to time Fldigi would revert back to regular operating mode
from contest mode.
3. When I would click on the received serial number in the RX pane, it
wouldn't fill the received serial box in the call window.

I've had these same problems in the past. Can anyone help me with
this? I'd like to use RTTY for 7QP and want to have the confidence that
it will work properly.
Thanks,
Jim W7JHR

Re: Issues Running the EA RTTY Contest This Past Weekend

WA7SKG <wa7skg@...>
 

Consider using N1MM+ for logging? I've used it in previous RTTY contests with fldigi and it worked great. That is what I plan to use with 7QP.

Michael WA7SKG (Operating RTTY and PSK31 for 7QP under W7PRA, ORCRO/ORWHE, 8 POINTS PER DIGITAL CONTACT!)


Jim Ruff via Groups.Io wrote on 4/7/19 8:54 PM:

I was operating the latest version of Fldigi with a KX3/KXPA100 and using AClog regular log, not their contest log and encountered the following issues:
1.  When logging the qso, it logged properly into he Fldigi log, but in the AClog it said DIGI not RTTY and it didn't log the frequency.
2.  From time to time Fldigi would revert back to regular operating mode from contest mode.
3.  When I would click on the received serial number in the RX pane, it wouldn't fill the received serial box in the call window.
I've had these same problems in the past.  Can anyone help me with this?  I'd like to use RTTY for 7QP and want to have the confidence that it will work properly.
Thanks,
Jim W7JHR

Re: start fldigi with script name on command line

Craig Perry <craigp84@...>
 

Autohotkey could do this for you. You'd schedule a .ahk script and that would be responsible for opening fldigi and sending mouse / keyboard commands

All the best

Craig

On Mon, 15 Apr 2019 at 00:22, Farren Constable <farren@...> wrote:
Maybe there's a more proper way of accomplishing what I'm trying to do, but here's what I'm looking for:  a way of starting fldigi and specifying a script on the command line so that it runs the script when it starts.  This is on Windows 7.  I'm wanting to schedule fldigi using the Windows scheduler so that at certain times it will start up and move to a specific frequency, mode, waterfall position, etc. so I can capture some digital nets.  I've read the docs about the command line switches and I don't see any way of starting it with a script. Is there a way to do this?  Thanks!

-Farren / KB0AZJ

start fldigi with script name on command line

Farren Constable
 

Maybe there's a more proper way of accomplishing what I'm trying to do, but here's what I'm looking for:  a way of starting fldigi and specifying a script on the command line so that it runs the script when it starts.  This is on Windows 7.  I'm wanting to schedule fldigi using the Windows scheduler so that at certain times it will start up and move to a specific frequency, mode, waterfall position, etc. so I can capture some digital nets.  I've read the docs about the command line switches and I don't see any way of starting it with a script. Is there a way to do this?  Thanks!

-Farren / KB0AZJ

Re: FLDIGI PSEUDO FSK

iz1fks
 

unfortunately this ambiguity on display and trasmitting frequency discorages use of fldigi with pseudo FSK while this function is great, i'm using it also during rtty contest with n1mm. Since the frequency trasmitted in FSK mode is the frequency (mark) of the rig dial the signal should not be displayed at the cursor frequency on the waterfall. An automatic (mouse button or a pushbutton on software like QSY that lacks until disactivated) in order to automatically set qsy of the rtty signal received somewhere on the waterfall an set to the right dial frequency. Otherwise using pseudo-FSK the user always need to remeber to maually QSY the signal in order to trasmit on the same frequency of the received signal.

73 de Phil iz1fks/ai4yn

Re: New postings for fldigi, flrig and fllog

Howard Grams
 

OK Rick, thanks for the update.

73, Howard K7JNX

Re: New postings for fldigi, flrig and fllog

Rick Ellison
 

Hi Howard..

Yes there is.. I’m about ¾ of the way thru a total re-write of the gateway. Most of the controls I had used in it no longer work in Windows 10. I’m fitting this in here and there between work and other coding issues I’m working on….

 

73 Rick N2AMG

 

From: winfldigi@groups.io [mailto:winfldigi@groups.io] On Behalf Of Howard Grams
Sent: Sunday, April 14, 2019 6:59 AM
To: winfldigi@groups.io
Subject: Re: [winfldigi] New postings for fldigi, flrig and fllog

 

Rick, is there hope for the Fldigi-DXLabs Gateway?

Regards,
   Howard  K7JNX


Virus-free. www.avast.com

Re: New postings for fldigi, flrig and fllog

Howard Grams
 

Rick, is there hope for the Fldigi-DXLabs Gateway?

Regards,
   Howard  K7JNX

Re: New postings for fldigi, flrig and fllog

Kevin Utzy
 

Rick,

 

Thanks you very much for the answer.  I didn’t know you guys kept in touch.  Cool

 

73,
Kevin
KX4KU

 

From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of Rick Ellison
Sent: Saturday, April 13, 2019 11:18 PM
To: winfldigi@groups.io
Subject: Re: [winfldigi] New postings for fldigi, flrig and fllog

 

Kevin..

No problem with N1MM. The next release of N1MM (Tuesday) has things working with no issues at all.

Most of us developers are in touch with each other. Dave and I have exchanged  a few emails over the last week..

 

73 Rick N2AMG

N1MM Digital Developer

 

From: winfldigi@groups.io [mailto:winfldigi@groups.io] On Behalf Of Kevin Utzy
Sent: Saturday, April 13, 2019 11:05 PM
To: winfldigi@groups.io
Subject: Re: [winfldigi] New postings for fldigi, flrig and fllog

 

Dave,

 

Sorry I haven’t been a die hard reader of everything but I have a question.   I looked at the readme for the release.  I noticed in them you depreciated xml-rpc rig control.   When you use Fldigi with N1MM, that is how N1MM communicates with Fldigi.  So how is this going to be handled in the future with regards to N1MM?  I didn’t see it depreciated documentation you referred to.

 

73,
Kevin
KX4KU

 

 

From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of Dave
Sent: Saturday, April 13, 2019 8:08 AM
To: winfldigi@groups.io
Subject: Re: [winfldigi] New postings for fldigi, flrig and fllog

 

Alphas are always the next release + an alpha release #, i.e. 4.1.02.46 is an alpha release for the general release 4.1.02.

Dave

On 4/13/19 6:51 AM, Dave Alexander wrote:

Dave,

 

What is the full #. I have 4.1.02.46.

 

From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of Dave
Sent: Saturday, April 13, 2019 7:46 AM
To: linuxham@groups.io
Subject: [winfldigi] New postings for fldigi, flrig and fllog

 

Please review the readme.txt file associated with each program.

The links below are for direct access to the W1HKJ download pages.

The Source Forge files pages have also been updated.


FLDIGI:


FLRIG:


FLLOG:


Direct access is also available to other W1HKJ programs using these URL links:


Report any download problems, or program issues back to this forum.

Note that a ppc.dmg has not been created for this update.  Users needing an OS-X disc image file for the Motorola G4 processor will have to request the same from me at my return address.

73, David, W1HKJ

 

 

 

 

Virus-free. www.avast.com

Re: New postings for fldigi, flrig and fllog

Rick Ellison
 

Kevin..

No problem with N1MM. The next release of N1MM (Tuesday) has things working with no issues at all.

Most of us developers are in touch with each other. Dave and I have exchanged  a few emails over the last week..

 

73 Rick N2AMG

N1MM Digital Developer

 

From: winfldigi@groups.io [mailto:winfldigi@groups.io] On Behalf Of Kevin Utzy
Sent: Saturday, April 13, 2019 11:05 PM
To: winfldigi@groups.io
Subject: Re: [winfldigi] New postings for fldigi, flrig and fllog

 

Dave,

 

Sorry I haven’t been a die hard reader of everything but I have a question.   I looked at the readme for the release.  I noticed in them you depreciated xml-rpc rig control.   When you use Fldigi with N1MM, that is how N1MM communicates with Fldigi.  So how is this going to be handled in the future with regards to N1MM?  I didn’t see it depreciated documentation you referred to.

 

73,
Kevin
KX4KU

 

 

From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of Dave
Sent: Saturday, April 13, 2019 8:08 AM
To: winfldigi@groups.io
Subject: Re: [winfldigi] New postings for fldigi, flrig and fllog

 

Alphas are always the next release + an alpha release #, i.e. 4.1.02.46 is an alpha release for the general release 4.1.02.

Dave

On 4/13/19 6:51 AM, Dave Alexander wrote:

Dave,

 

What is the full #. I have 4.1.02.46.

 

From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of Dave
Sent: Saturday, April 13, 2019 7:46 AM
To: linuxham@groups.io
Subject: [winfldigi] New postings for fldigi, flrig and fllog

 

Please review the readme.txt file associated with each program.

The links below are for direct access to the W1HKJ download pages.

The Source Forge files pages have also been updated.


FLDIGI:


FLRIG:


FLLOG:


Direct access is also available to other W1HKJ programs using these URL links:


Report any download problems, or program issues back to this forum.

Note that a ppc.dmg has not been created for this update.  Users needing an OS-X disc image file for the Motorola G4 processor will have to request the same from me at my return address.

73, David, W1HKJ

 

 

 


Virus-free. www.avast.com

Re: New postings for fldigi, flrig and fllog

Kevin Utzy
 

Dave,

 

Sorry I haven’t been a die hard reader of everything but I have a question.   I looked at the readme for the release.  I noticed in them you depreciated xml-rpc rig control.   When you use Fldigi with N1MM, that is how N1MM communicates with Fldigi.  So how is this going to be handled in the future with regards to N1MM?  I didn’t see it depreciated documentation you referred to.

 

73,
Kevin
KX4KU

 

 

From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of Dave
Sent: Saturday, April 13, 2019 8:08 AM
To: winfldigi@groups.io
Subject: Re: [winfldigi] New postings for fldigi, flrig and fllog

 

Alphas are always the next release + an alpha release #, i.e. 4.1.02.46 is an alpha release for the general release 4.1.02.

Dave

On 4/13/19 6:51 AM, Dave Alexander wrote:

Dave,

 

What is the full #. I have 4.1.02.46.

 

From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of Dave
Sent: Saturday, April 13, 2019 7:46 AM
To: linuxham@groups.io
Subject: [winfldigi] New postings for fldigi, flrig and fllog

 

Please review the readme.txt file associated with each program.

The links below are for direct access to the W1HKJ download pages.

The Source Forge files pages have also been updated.


FLDIGI:


FLRIG:


FLLOG:


Direct access is also available to other W1HKJ programs using these URL links:


Report any download problems, or program issues back to this forum.

Note that a ppc.dmg has not been created for this update.  Users needing an OS-X disc image file for the Motorola G4 processor will have to request the same from me at my return address.

73, David, W1HKJ

 

 

 

Re: fldigi problems with new versions

iz1fks
 

thanks, it works!

73 de Phil