Date   
Re: fldigi 4.1.01.04 alpha posted

dave_ad2q <dcrife16@...>
 

Not Found

The requested URL /alpha/fldigi/fldigi-4.1.01.04_setup.exe was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Re: fldigi 4.1.01.04 alpha posted

Deerik Shryock
 

David,

You're doing damn fine work, I really appreciate all your efforts and enjoy using fldigi.

Thanks again,
Deerik, KK7WE
73

Re: Serial # Sent in TX is Different that Serial# in Contest Window

Tim Thorson <9165radios@...>
 

Thanks Scott!

I actually missed typed and meant to say CW WPX. 

If there's a way to amend my  posts (for future readers) I would like to do so...

Tim Thorson
916-572-3467


On Mon, Feb 11, 2019, 4:05 AM Scott Davis via Groups.Io <SNKDavis=aol.com@groups.io wrote:
Hi Tim,
 
AC Log is designed as a general logging program, not contesting, so it doesn't auto increment sent serial numbers.  For the CQ WPX contest, please use my CQ WPX logging program.  The appropriate contest software (CQ WPX Log in this case) is designed to take care of the auto increment for you, and communicates that information with FLDigi.  Please always be sure to use the correct contest log for each contest.  Here is the program to use for CQ WPX RTTY;
 
 
Enjoy!

73, Scott
N3FJP
 
Serving the Amateur Radio community with contesting and general logging software since 1997.
 
1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...

Re: WPX RTTY - pleasant surprise

 

Try this to answer a call:

 

<TX>

<CALL> de <MYCALL> 599 <SERNO> <SERNO>

<RX>

 

When you hit the save, the serial # will automatically save and increment buy itself.

 

From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of James C. Hall, MD via Groups.Io
Sent: Sunday, February 10, 2019 11:33 PM
To: winfldigi@groups.io
Subject: [winfldigi] WPX RTTY - pleasant surprise

 

I’ve been a fan of flDigi for its emergency messaging capability for quite some time. I’ve never considered flDigi as a “contest” software. However, there is no denying that it  is popular in contest settings especially since it interfaces nice with N3FJP’s nice contest loggers. 

I’ve been working on FD for later this year in which we will use N3FJP as networked software with flDigi and JT/WSJT digital software. So I have one of the radios here, a Kenwood TS-480HX with a SignaLink interface, that I got to play nice with the software. It has 1.8 kHz SSB and 500 Hz CW filter. Since I’m using AFSK I’m relegated to the 1.8 MHz filter with DSP. 

So I decided to purchase the WPX contest software from N3FJP and use it with flDigi as I would for FD except there were serial numbers involved. So, I followed the instructions on setting up macros for the contest using the <CNTR> macro item. I usually use N1MM+ for contesting and used my old macros as a guide and setup the buttons with a little resizing, etc.

I must say I was pleasantly surprised at how well it all worked. I had some de-sensing from strong signals that I had to deal with and I used tight DSP settings. I use FFT as I would for RTTY on other software. But the flDigi demodulator did a credible job even when I couldn’t hear the signal. For casual contesting, this is all that’s necessary. I had to get used to a slightly different way of doing things with the macros, such as a separate macro for logging and increment the serial number when In S&P. Also, if you ham hand or double-clutch the log macro, you could end up skipping a serial number - you send one number, but what is logged is one number off. I had to edit a few QSO’s because of that.

Every software is different and this is no true “contest” software with niceties such as ESM, auto-CQ, multiple demodulators in separate windows with “deep in the weeds” settings such as tap settings, but it’ll do. And it does quite well. 

73, Jamie
WB4YDL

Re: FLDIGI 4.1.0.0 SCR help

Cliff
 

Loading it without N3FJP comes up just fine. Are you trying to connect to another logger?

73,
Cliff, AE5ZA

On Feb 11, 2019, at 08:30, Dave Alexander <dave.alexander1947@...> wrote:

I use the one by N3FJP. It plays nicely with FLDIGI.

-----Original Message-----
From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of N2RQ
Sent: Sunday, February 10, 2019 10:54 PM
To: winfldigi@groups.io
Subject: [winfldigi] FLDIGI 4.1.0.0 SCR help

After downloading the latest version, I found that it lists the School Club Roundup in its contests.  When I select it, the name appears in the window briefly and then disappears.  The SCR starts Monday.

Has anyone succeeded in setting it up?

Help

73, Lew, N2RQ@...



--
73 de Lew
n2rq@...
scr@...





Re: FLDIGI 4.1.0.0 SCR help

 

I use the one by N3FJP. It plays nicely with FLDIGI.

-----Original Message-----
From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of N2RQ
Sent: Sunday, February 10, 2019 10:54 PM
To: winfldigi@groups.io
Subject: [winfldigi] FLDIGI 4.1.0.0 SCR help

After downloading the latest version, I found that it lists the School Club Roundup in its contests. When I select it, the name appears in the window briefly and then disappears. The SCR starts Monday.

Has anyone succeeded in setting it up?

Help

73, Lew, N2RQ@...



--
73 de Lew
n2rq@...
scr@...

Re: Port Audio Error

Dave
 

Thank you Mr. Gates.

On 2/11/19 7:54 AM, Michael Black via Groups.Io wrote:
Yes...under Windows when the monitor goes to sleep it also turns off the audio -- I discovered the same thing a few weeks ago that was causing WSJT-X to lose transmit audio when it woke up.

de Mike W9MDB





On Monday, February 11, 2019, 7:42:59 AM CST, Chuck Farrell <chuckffarrell@...> wrote:


Just to close out the thread. On Sunday's net, which is mostly listening (and why the screen saver kicks on), I launched "Keep Display On" from FlDigi and no screen saver, no Port Audio Error, all good.

Re: Port Audio Error

Michael Black
 

Yes...under Windows when the monitor goes to sleep it also turns off the audio -- I discovered the same thing a few weeks ago that was causing WSJT-X to lose transmit audio when it woke up.

de Mike W9MDB





On Monday, February 11, 2019, 7:42:59 AM CST, Chuck Farrell <chuckffarrell@...> wrote:


Just to close out the thread. On Sunday's net, which is mostly listening (and why the screen saver kicks on), I launched "Keep Display On" from FlDigi and no screen saver, no Port Audio Error, all good.

Re: Port Audio Error

Chuck Farrell
 

Just to close out the thread. On Sunday's net, which is mostly listening (and why the screen saver kicks on), I launched "Keep Display On" from FlDigi and no screen saver, no Port Audio Error, all good.

Re: Serial # Sent in TX is Different that Serial# in Contest Window

Scott Davis
 

Hi Tim,
 
AC Log is designed as a general logging program, not contesting, so it doesn't auto increment sent serial numbers.  For the CQ WPX contest, please use my CQ WPX logging program.  The appropriate contest software (CQ WPX Log in this case) is designed to take care of the auto increment for you, and communicates that information with FLDigi.  Please always be sure to use the correct contest log for each contest.  Here is the program to use for CQ WPX RTTY;
 
http://www.n3fjp.com/cqwpx.html
 
Enjoy!

73, Scott
N3FJP
 
Serving the Amateur Radio community with contesting and general logging software since 1997.
 
1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...

WPX RTTY - pleasant surprise

James C. Hall, MD
 

I’ve been a fan of flDigi for its emergency messaging capability for quite some time. I’ve never considered flDigi as a “contest” software. However, there is no denying that it  is popular in contest settings especially since it interfaces nice with N3FJP’s nice contest loggers. 

I’ve been working on FD for later this year in which we will use N3FJP as networked software with flDigi and JT/WSJT digital software. So I have one of the radios here, a Kenwood TS-480HX with a SignaLink interface, that I got to play nice with the software. It has 1.8 kHz SSB and 500 Hz CW filter. Since I’m using AFSK I’m relegated to the 1.8 MHz filter with DSP. 

So I decided to purchase the WPX contest software from N3FJP and use it with flDigi as I would for FD except there were serial numbers involved. So, I followed the instructions on setting up macros for the contest using the <CNTR> macro item. I usually use N1MM+ for contesting and used my old macros as a guide and setup the buttons with a little resizing, etc.

I must say I was pleasantly surprised at how well it all worked. I had some de-sensing from strong signals that I had to deal with and I used tight DSP settings. I use FFT as I would for RTTY on other software. But the flDigi demodulator did a credible job even when I couldn’t hear the signal. For casual contesting, this is all that’s necessary. I had to get used to a slightly different way of doing things with the macros, such as a separate macro for logging and increment the serial number when In S&P. Also, if you ham hand or double-clutch the log macro, you could end up skipping a serial number - you send one number, but what is logged is one number off. I had to edit a few QSO’s because of that.

Every software is different and this is no true “contest” software with niceties such as ESM, auto-CQ, multiple demodulators in separate windows with “deep in the weeds” settings such as tap settings, but it’ll do. And it does quite well. 

73, Jamie
WB4YDL

FLDIGI 4.1.0.0 SCR help

N2RQ
 

After downloading the latest version, I found that it lists the School
Club Roundup in its contests.  When I select it, the name appears in the
window briefly and then disappears.  The SCR starts Monday.

Has anyone succeeded in setting it up?

Help

73, Lew, N2RQ@...



--
73 de Lew
n2rq@...
scr@...

Contest counters - CQ WPX with fldigi

Tim Thorson <9165radios@...>
 

Revelation:

In addition to logging count issues, I kept getting Hiccups from Dup warning "dupe-duplicate"
I found checked Enable Data Stream under UI>Log>N3FJP Caused this (Multi packetts?)  = FIXED!

However,
This caused the counters issue(s) to have a twist.

The SERNO count (that was 148) displaying in S # field now reset to the (old) CNTR count (124)

Just Had to hit my INCR a few times to get back up to current count.

Motto= Don't use Enable Data Stream during contest (only testing)  <whew!>

All-in-All Hats off to Scott & David and their team(s) for making this contest my personal best!

73

Tim - KD6HOF




Re: Serial # Sent in TX is Different that Serial# in Contest Window

Jim Ruff
 

I'm running N3FJP contest logger which has been working great with FLdigi except once in awhile, the call window in Fldigi will not turn purple when there is a dupe, even though the N3FJP shows a dupe.
Thanks,
Jim W7JHR

Re: Serial # Sent in TX is Different that Serial# in Contest Window

Tim Thorson <9165radios@...>
 

Experiment - 
I Logged the current CQ WPX QSO for SN 144 ok
AClog took it ok - But fldigi did NOT advance S # field (verified not just a display glitch by test-macro "SERNO = <SERNO>"
While fldigi saying it was currently @ 144 (wrong), I decided to log a fake QSO to see what would happen.
  I used my call and arbitrary info
 The QSO logged to AClog with the next # correctly (145)
 and fldigi now reflects # as 146 (correct for next QSO)

...If AClog is supplying current S# back to fldigi, it's occasionally getting lost.
I have been simply clicking LOG again to force it to update (with an expected DUP warning from AClog) although, this is just to make sure...





On Sun, Feb 10, 2019 at 12:59 PM Tim Thorson via Groups.Io <9165radios=gmail.com@groups.io> wrote:
I think we are seeing the same elephant from different angles. (fldigi & AClog)

I stopped using <CTNR> and now use<SERNO>

I discovered If there is anything after <LOG> command the SERNO fails to auto-Increment .
Using <INCR> only works on CNTR not SERNO (still dunno why two different counters) - So I have to LOG again to get SERNO to increment. (ACLOG Dup warning expected)

Other observations:

Even a mistaken [space] after <LOG> in macro will cause it to log and NOT increment.
<CLRLOG> wont work - unless used as part of TX mode, not RX
-- 
Tim KD6HOF

On Sun, Feb 10, 2019 at 12:54 PM Dave Alexander <dave.alexander1947@...> wrote:

I am currently testing the newest version and that problem doesn’t exist unless I lose the connection between FLDIGI and N3FJP.

 

I can reset it if it does with no problem.

 

From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of Jim Ruff via Groups.Io
Sent: Sunday, February 10, 2019 3:41 PM
To: winfldigi@groups.io
Subject: Re: [winfldigi] Serial # Sent in TX is Different that Serial# in Contest Window

 

Here is what I've tried without consistent success. 

  • Went into config>contest>START#> set number to next #r> hit reset> save.  The correct number would usually show up in the S# window.
  • Sent TX and 90% of the time, the transmitted serial # would be a different # from the correct serial #.  The numbers in the TX were random. i.e. 002 or 036 etc.
  • When I hit the SAVE button it would usually move the serial# up one.
  • When the SAVE button wouldn't move the serial # up one, I would use one of two macros, either <SERNO><INCR> or <LOG><INCR>. Usually one of these macros would move the serial # up one, but had no effect on what serial # was transmitted.

When all else failed, I shut down Fldigi and restarted it and did the process all over again.  What I found was that the first QSO after I restarted usually transmitted correctly, but all the problems started on the next QSO with the wrong serial # transmitted and the Serial # randomly not increasing when logged.

 

Does anyone think that this may be a bug in the new version that will get worked out or should I be looking into my computer?  Just so you know, up until I downloaded the new version, this was the best functioning software I've ever used including WSJT-X.  It's always worked perfectly.

 

Thanks,

Jim W7JHR



--
Tim Thorson
916-572-3467





--
Tim Thorson
916-572-3467



Re: Serial # Sent in TX is Different that Serial# in Contest Window

Tim Thorson <9165radios@...>
 

I think we are seeing the same elephant from different angles. (fldigi & AClog)

I stopped using <CTNR> and now use<SERNO>

I discovered If there is anything after <LOG> command the SERNO fails to auto-Increment .
Using <INCR> only works on CNTR not SERNO (still dunno why two different counters) - So I have to LOG again to get SERNO to increment. (ACLOG Dup warning expected)

Other observations:

Even a mistaken [space] after <LOG> in macro will cause it to log and NOT increment.
<CLRLOG> wont work - unless used as part of TX mode, not RX
-- 
Tim KD6HOF

On Sun, Feb 10, 2019 at 12:54 PM Dave Alexander <dave.alexander1947@...> wrote:

I am currently testing the newest version and that problem doesn’t exist unless I lose the connection between FLDIGI and N3FJP.

 

I can reset it if it does with no problem.

 

From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of Jim Ruff via Groups.Io
Sent: Sunday, February 10, 2019 3:41 PM
To: winfldigi@groups.io
Subject: Re: [winfldigi] Serial # Sent in TX is Different that Serial# in Contest Window

 

Here is what I've tried without consistent success. 

  • Went into config>contest>START#> set number to next #r> hit reset> save.  The correct number would usually show up in the S# window.
  • Sent TX and 90% of the time, the transmitted serial # would be a different # from the correct serial #.  The numbers in the TX were random. i.e. 002 or 036 etc.
  • When I hit the SAVE button it would usually move the serial# up one.
  • When the SAVE button wouldn't move the serial # up one, I would use one of two macros, either <SERNO><INCR> or <LOG><INCR>. Usually one of these macros would move the serial # up one, but had no effect on what serial # was transmitted.

When all else failed, I shut down Fldigi and restarted it and did the process all over again.  What I found was that the first QSO after I restarted usually transmitted correctly, but all the problems started on the next QSO with the wrong serial # transmitted and the Serial # randomly not increasing when logged.

 

Does anyone think that this may be a bug in the new version that will get worked out or should I be looking into my computer?  Just so you know, up until I downloaded the new version, this was the best functioning software I've ever used including WSJT-X.  It's always worked perfectly.

 

Thanks,

Jim W7JHR



--
Tim Thorson
916-572-3467



Re: Serial # Sent in TX is Different that Serial# in Contest Window

 

I am currently testing the newest version and that problem doesn’t exist unless I lose the connection between FLDIGI and N3FJP.

 

I can reset it if it does with no problem.

 

From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of Jim Ruff via Groups.Io
Sent: Sunday, February 10, 2019 3:41 PM
To: winfldigi@groups.io
Subject: Re: [winfldigi] Serial # Sent in TX is Different that Serial# in Contest Window

 

Here is what I've tried without consistent success. 

  • Went into config>contest>START#> set number to next #r> hit reset> save.  The correct number would usually show up in the S# window.
  • Sent TX and 90% of the time, the transmitted serial # would be a different # from the correct serial #.  The numbers in the TX were random. i.e. 002 or 036 etc.
  • When I hit the SAVE button it would usually move the serial# up one.
  • When the SAVE button wouldn't move the serial # up one, I would use one of two macros, either <SERNO><INCR> or <LOG><INCR>. Usually one of these macros would move the serial # up one, but had no effect on what serial # was transmitted.

When all else failed, I shut down Fldigi and restarted it and did the process all over again.  What I found was that the first QSO after I restarted usually transmitted correctly, but all the problems started on the next QSO with the wrong serial # transmitted and the Serial # randomly not increasing when logged.

 

Does anyone think that this may be a bug in the new version that will get worked out or should I be looking into my computer?  Just so you know, up until I downloaded the new version, this was the best functioning software I've ever used including WSJT-X.  It's always worked perfectly.

 

Thanks,

Jim W7JHR

Re: The SAVE button

 

That's where it belongs. Just be careful. I have done the same thing.

-----Original Message-----
From: winfldigi@groups.io <winfldigi@groups.io> On Behalf Of Fred K2DFC via Groups.Io
Sent: Sunday, February 10, 2019 3:31 PM
To: winfldigi@groups.io
Subject: Re: [winfldigi] The SAVE button

4.1.00

All versions I've ever used had the SAVE button under the CLEAR.

Re: Serial # Sent in TX is Different that Serial# in Contest Window

Dave
 

Are you running fldigi alone or with an N3FJP logger connected ?

David

On 2/10/19 2:41 PM, Jim Ruff via Groups.Io wrote:
Here is what I've tried without consistent success. 
  • Went into config>contest>START#> set number to next #r> hit reset> save.  The correct number would usually show up in the S# window.
  • Sent TX and 90% of the time, the transmitted serial # would be a different # from the correct serial #.  The numbers in the TX were random. i.e. 002 or 036 etc.
  • When I hit the SAVE button it would usually move the serial# up one.
  • When the SAVE button wouldn't move the serial # up one, I would use one of two macros, either <SERNO><INCR> or <LOG><INCR>. Usually one of these macros would move the serial # up one, but had no effect on what serial # was transmitted.
When all else failed, I shut down Fldigi and restarted it and did the process all over again.  What I found was that the first QSO after I restarted usually transmitted correctly, but all the problems started on the next QSO with the wrong serial # transmitted and the Serial # randomly not increasing when logged.

Does anyone think that this may be a bug in the new version that will get worked out or should I be looking into my computer?  Just so you know, up until I downloaded the new version, this was the best functioning software I've ever used including WSJT-X.  It's always worked perfectly.

Thanks,
Jim W7JHR

Re: The SAVE button

Dave
 






Depends on the menu selection, View / Rig/Log controls / Full, Partial or None

David

On 2/10/19 2:31 PM, Fred K2DFC via Groups.Io wrote:
[Edited Message Follows]

4.1.00

All versions I've ever used had the SAVE button under the CLEAR. Guess I should have said it would be better to the right of the serial numbers.