Date   
Re: fldigi 4.1.01 release

Ed W3NR
 

On 2/25/19 8:16 AM, gregsiemasz@... wrote:
Thank you for letting me join the group.
I am having a couple of issues with this version.
1: WX no longer works .
Being worked on.
2: When I change frequency from 40m to 20m the Frq box stays in 40m making it impossible to save QSO correctly and send accurate QSL's via the program.
I tried to change the Frq by putting cursor in that field but nothing happened.
What are you using for rig control ?
3. I try to input County information and nothing happens there either. If I click on the County tab or Frq tab I can see this ^ at front left but can not input any info.
I am running windows 10 Home 1803 and have had no issues with previous versions of Fldigi.
Use the drop down.
Below is just an example pic I got on line and is not the current version. The Frq is the same as the frequency. I pulled this pic off the internet.
I have uninstalled and reinstalled this version and it still has the same issues
I am new to this group and was not sure how to make the example smaller in the word processor.
Thank you and your help would be greatly appreciated.
Greg

_._,_._,_

Ed W3NR

Re: fldigi 4.1.01 release

gregsiemasz@...
 

Ed,
I am not using any rig control. I never got it to work with my Ten-Tec Jupiter.
I am connected to radio via SignalLink USB.
I just not that savvy to figure out how to make any of the rig controls to work with this radio.
I thought that if I right clicked on the drop down that appears and give you RST,QTH State and County it would input where it should go under County.
Greg

Re: fldigi 4.1.01 release

Ed W3NR
 

On 2/25/19 1:02 PM, gregsiemasz@... wrote:
Ed,
I am not using any rig control. I never got it to work with my Ten-Tec Jupiter.
I was the alpha tester when the jupiter was added to flrrig and it worked perfectly, so I don't know what problem you had.
I am connected to radio via SignalLink USB.
I just not that savvy to figure out how to make any of the rig controls to work with this radio.
Without rig control it must be done manually.
I thought that if I right clicked on the drop down that appears and give you RST,QTH State and County it would input where it should go under County.
Is this a state QSO party ?
Greg
_._,_._,_

Ed W3NR

Your call ?

Re: fldigi 4.1.01 release

gregsiemasz@...
 

Ed
I don’t know anything about flrrig. There was no information from Ten-Tec or anyone else. So would you like to help me with that? I have been doing it manually and it wasn’t a problem. I got use to it. New software has bugs and I take it will be fixed eventually. 
Ed I don’t understand some of your questions. Can you elaborate?

On Mon, Feb 25, 2019 at 2:14 PM Ed W3NR <autek@...> wrote:
On 2/25/19 1:02 PM, gregsiemasz@... wrote:
Ed,
I am not using any rig control. I never got it to work with my Ten-Tec Jupiter.
I was the alpha tester when the jupiter was added to flrrig and it worked perfectly, so I don't know what problem you had.
I am connected to radio via SignalLink USB.
I just not that savvy to figure out how to make any of the rig controls to work with this radio.
Without rig control it must be done manually.
I thought that if I right clicked on the drop down that appears and give you RST,QTH State and County it would input where it should go under County.
Is this a state QSO party ?
Greg

Re: fldigi 4.1.01.04 alpha posted

Greg Siemasz <gregsiemasz@...>
 

Dave,
I tried that version and it didn't resolve the issues I had from previous one.
WX issue was one and I see you are working on that and Frq box doesn't change from 40m to 20m when I change to 20m or any other frequency I change to. So I can't save the QSO on EQSL because it would be inaccurate.
Greg

FLDIGI 4.1.0.0 LoTW mode field not exporting causing an error

Bill Hamel
 

Good evening.

---
Fldigi 4.1.0.0
MAC OS High Sierra 10.13.6
Tsql: 2.4.3

When I try to use Fldigi to automatically update LoTW I get an error that says that the mode is missing, In this case PSK31

To help diagnose I unchecked the box that says “Quiet mode [-q], do not open tqsl dialog in Logbook->LoTW

Condition 1 
==========
When I finish a QSO and write the log a box pops up that reports 

—-------------------<SNIP>------------------------
Signing using Callsign K3TFM, DXCC Entity UNITED STATES OF AMERICA

Error: Invalid contact - QSO does not specify a mode on line 4
CALL: K5****
FREQ: 7.07269
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0206

Warning: Signing cancelled
No records to upload
---------------------</SNIP>————————————

Condition 2 
===========
When I use Fldigi to try a LoTW batch by doing Logbook->LoTW->Export
I make sure I select the LoTW button so it checks the relevant fields
(Note that I also will check the “Mode” box and try it that way also since when clicking the “LoTW” button it does not check the mode box)
I then select “SEND” and the following log entries occur in the log file

Note actual calls masked with “*"
—-------------------<SNIP>------------------------
Wed Feb 27 20:41:28 2019 tqsl_getNumBand
Wed Feb 27 20:41:28 2019 check_tqsl_error: rval=1
Wed Feb 27 20:41:28 2019 check_tqsl_error: msg=Invalid contact - QSO does not specify a mode
Error: Invalid contact - QSO does not specify a mode on line 6
CALL: KG5***
FREQ: 7.07254
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0059

Wed Feb 27 20:41:28 2019 tqsl_getNumBand
Wed Feb 27 20:41:28 2019 check_tqsl_error: rval=1
Wed Feb 27 20:41:28 2019 check_tqsl_error: msg=Invalid contact - QSO does not specify a mode
Error: Invalid contact - QSO does not specify a mode on line 7
CALL: AA5***
FREQ: 7.07232
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0113

Wed Feb 27 20:41:28 2019 MyFrame::UploadLogFile: Log converted, status = 9, numrecs=0
---------------------</SNIP>————————————

Condition 3 
--------------------
I can get it to work if I do the following

In FLDigi Logbook->ADIF->Export 

Check the same boxes that I do above using the LoTW methods above

Export the adif

From within Tsql do a “Sign a log and upload it automatically to LoTW”

And my log is successfully uploaded to LoTW including the Mode information

Any insight greatly appreciated.

Thanks,
Bill K3TFM







Re: FLDIGI 4.1.0.0 LoTW mode field not exporting causing an error

Bill Hamel
 

Not realizing that the Help -> “Check for updates” doesn’t actually check for updates since it kept tell me that no updates are available.

I manually found a v4.1.01 that says it fixes this problem in the release notes. I’ve installed it an it appears to be working now.

Thanks
-bh k3tfm

On Feb 27, 2019, at 9:34 PM, Bill Hamel <bill@...> wrote:

Good evening.

---
Fldigi 4.1.0.0
MAC OS High Sierra 10.13.6
Tsql: 2.4.3

When I try to use Fldigi to automatically update LoTW I get an error that says that the mode is missing, In this case PSK31

To help diagnose I unchecked the box that says “Quiet mode [-q], do not open tqsl dialog in Logbook->LoTW

Condition 1 
==========
When I finish a QSO and write the log a box pops up that reports 

—-------------------<SNIP>------------------------
Signing using Callsign K3TFM, DXCC Entity UNITED STATES OF AMERICA

Error: Invalid contact - QSO does not specify a mode on line 4
CALL: K5****
FREQ: 7.07269
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0206

Warning: Signing cancelled
No records to upload
---------------------</SNIP>————————————

Condition 2 
===========
When I use Fldigi to try a LoTW batch by doing Logbook->LoTW->Export
I make sure I select the LoTW button so it checks the relevant fields
(Note that I also will check the “Mode” box and try it that way also since when clicking the “LoTW” button it does not check the mode box)
I then select “SEND” and the following log entries occur in the log file

Note actual calls masked with “*"
—-------------------<SNIP>------------------------
Wed Feb 27 20:41:28 2019 tqsl_getNumBand
Wed Feb 27 20:41:28 2019 check_tqsl_error: rval=1
Wed Feb 27 20:41:28 2019 check_tqsl_error: msg=Invalid contact - QSO does not specify a mode
Error: Invalid contact - QSO does not specify a mode on line 6
CALL: KG5***
FREQ: 7.07254
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0059

Wed Feb 27 20:41:28 2019 tqsl_getNumBand
Wed Feb 27 20:41:28 2019 check_tqsl_error: rval=1
Wed Feb 27 20:41:28 2019 check_tqsl_error: msg=Invalid contact - QSO does not specify a mode
Error: Invalid contact - QSO does not specify a mode on line 7
CALL: AA5***
FREQ: 7.07232
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0113

Wed Feb 27 20:41:28 2019 MyFrame::UploadLogFile: Log converted, status = 9, numrecs=0
---------------------</SNIP>————————————

Condition 3 
--------------------
I can get it to work if I do the following

In FLDigi Logbook->ADIF->Export 

Check the same boxes that I do above using the LoTW methods above

Export the adif

From within Tsql do a “Sign a log and upload it automatically to LoTW”

And my log is successfully uploaded to LoTW including the Mode information

Any insight greatly appreciated.

Thanks,
Bill K3TFM








Re: FLDIGI 4.1.0.0 LoTW mode field not exporting causing an error

Dave
 

Your statement is not true Bill.



4.1.0.0 was and is an alpha version and it's numbering will always be in sync with the final distribution, ie:

4.1.0.1
4.1.0.2
4.1.0.n ===> results in a distribution of 4.1.0.

As an alpha user you have the responsibility to monitor either linuxham@groups.io, or nbems@groups.io, or winfldigi@groups.io for announcements regarding new distributions, or personally check Source Forge (or the w1hkj.com site) for physical evidence of a new distribution.

The groups.io announcements always delineate what bugs have been fixed or changes implemented.

73, David, W1HKJ

On 2/28/19 8:54 AM, Bill Hamel wrote:
Not realizing that the Help -> “Check for updates” doesn’t actually check for updates since it kept tell me that no updates are available.

I manually found a v4.1.01 that says it fixes this problem in the release notes. I’ve installed it an it appears to be working now.

Thanks
-bh k3tfm

On Feb 27, 2019, at 9:34 PM, Bill Hamel <bill@...> wrote:

Good evening.

---
Fldigi 4.1.0.0
MAC OS High Sierra 10.13.6
Tsql: 2.4.3

When I try to use Fldigi to automatically update LoTW I get an error that says that the mode is missing, In this case PSK31

To help diagnose I unchecked the box that says “Quiet mode [-q], do not open tqsl dialog in Logbook->LoTW

Condition 1 
==========
When I finish a QSO and write the log a box pops up that reports 

—-------------------<SNIP>------------------------
Signing using Callsign K3TFM, DXCC Entity UNITED STATES OF AMERICA

Error: Invalid contact - QSO does not specify a mode on line 4
CALL: K5****
FREQ: 7.07269
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0206

Warning: Signing cancelled
No records to upload
---------------------</SNIP>————————————

Condition 2 
===========
When I use Fldigi to try a LoTW batch by doing Logbook->LoTW->Export
I make sure I select the LoTW button so it checks the relevant fields
(Note that I also will check the “Mode” box and try it that way also since when clicking the “LoTW” button it does not check the mode box)
I then select “SEND” and the following log entries occur in the log file

Note actual calls masked with “*"
—-------------------<SNIP>------------------------
Wed Feb 27 20:41:28 2019 tqsl_getNumBand
Wed Feb 27 20:41:28 2019 check_tqsl_error: rval=1
Wed Feb 27 20:41:28 2019 check_tqsl_error: msg=Invalid contact - QSO does not specify a mode
Error: Invalid contact - QSO does not specify a mode on line 6
CALL: KG5***
FREQ: 7.07254
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0059

Wed Feb 27 20:41:28 2019 tqsl_getNumBand
Wed Feb 27 20:41:28 2019 check_tqsl_error: rval=1
Wed Feb 27 20:41:28 2019 check_tqsl_error: msg=Invalid contact - QSO does not specify a mode
Error: Invalid contact - QSO does not specify a mode on line 7
CALL: AA5***
FREQ: 7.07232
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0113

Wed Feb 27 20:41:28 2019 MyFrame::UploadLogFile: Log converted, status = 9, numrecs=0
---------------------</SNIP>————————————

Condition 3 
--------------------
I can get it to work if I do the following

In FLDigi Logbook->ADIF->Export 

Check the same boxes that I do above using the LoTW methods above

Export the adif

From within Tsql do a “Sign a log and upload it automatically to LoTW”

And my log is successfully uploaded to LoTW including the Mode information

Any insight greatly appreciated.

Thanks,
Bill K3TFM









Re: FLDIGI 4.1.0.0 LoTW mode field not exporting causing an error

Bill Hamel
 

Hi David,

I’m not sure if the box you are showing pops up when you check for updates, if it is, what I’m seeing on a Mac is different.



If 4.1.0.1 is not supposed to be considered "the latest version" I’ll keep that in mind for future versions that are in the x of 4.1.0.x versioning.

Returning the message in the box you displayed would make more sense here.

I guess I got confused when I saw ver 4.1.00 which I thought meant 4.1.0.0

Thanks,
-bh k3tfm



On Feb 28, 2019, at 10:15 AM, Dave <w1hkj@...> wrote:

Your statement is not true Bill.

<apjeacjpiapdeefk.png>

4.1.0.0 was and is an alpha version and it's numbering will always be in sync with the final distribution, ie:

4.1.0.1
4.1.0.2
4.1.0.n ===> results in a distribution of 4.1.0.

As an alpha user you have the responsibility to monitor either linuxham@groups.io, or nbems@groups.io, or winfldigi@groups.io for announcements regarding new distributions, or personally check Source Forge (or the w1hkj.com site) for physical evidence of a new distribution.

The groups.io announcements always delineate what bugs have been fixed or changes implemented.

73, David, W1HKJ

On 2/28/19 8:54 AM, Bill Hamel wrote:
Not realizing that the Help -> “Check for updates” doesn’t actually check for updates since it kept tell me that no updates are available.

I manually found a v4.1.01 that says it fixes this problem in the release notes. I’ve installed it an it appears to be working now.

Thanks
-bh k3tfm

On Feb 27, 2019, at 9:34 PM, Bill Hamel <bill@...> wrote:

Good evening.

---
Fldigi 4.1.0.0
MAC OS High Sierra 10.13.6
Tsql: 2.4.3

When I try to use Fldigi to automatically update LoTW I get an error that says that the mode is missing, In this case PSK31

To help diagnose I unchecked the box that says “Quiet mode [-q], do not open tqsl dialog in Logbook->LoTW

Condition 1 
==========
When I finish a QSO and write the log a box pops up that reports 

—-------------------<SNIP>------------------------
Signing using Callsign K3TFM, DXCC Entity UNITED STATES OF AMERICA

Error: Invalid contact - QSO does not specify a mode on line 4
CALL: K5****
FREQ: 7.07269
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0206

Warning: Signing cancelled
No records to upload
---------------------</SNIP>————————————

Condition 2 
===========
When I use Fldigi to try a LoTW batch by doing Logbook->LoTW->Export
I make sure I select the LoTW button so it checks the relevant fields
(Note that I also will check the “Mode” box and try it that way also since when clicking the “LoTW” button it does not check the mode box)
I then select “SEND” and the following log entries occur in the log file

Note actual calls masked with “*"
—-------------------<SNIP>------------------------
Wed Feb 27 20:41:28 2019 tqsl_getNumBand
Wed Feb 27 20:41:28 2019 check_tqsl_error: rval=1
Wed Feb 27 20:41:28 2019 check_tqsl_error: msg=Invalid contact - QSO does not specify a mode
Error: Invalid contact - QSO does not specify a mode on line 6
CALL: KG5***
FREQ: 7.07254
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0059

Wed Feb 27 20:41:28 2019 tqsl_getNumBand
Wed Feb 27 20:41:28 2019 check_tqsl_error: rval=1
Wed Feb 27 20:41:28 2019 check_tqsl_error: msg=Invalid contact - QSO does not specify a mode
Error: Invalid contact - QSO does not specify a mode on line 7
CALL: AA5***
FREQ: 7.07232
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0113

Wed Feb 27 20:41:28 2019 MyFrame::UploadLogFile: Log converted, status = 9, numrecs=0
---------------------</SNIP>————————————

Condition 3 
--------------------
I can get it to work if I do the following

In FLDigi Logbook->ADIF->Export 

Check the same boxes that I do above using the LoTW methods above

Export the adif

From within Tsql do a “Sign a log and upload it automatically to LoTW”

And my log is successfully uploaded to LoTW including the Mode information

Any insight greatly appreciated.

Thanks,
Bill K3TFM










Re: FLDIGI 4.1.0.0 LoTW mode field not exporting causing an error

Marty Hartwell
 

Hi

To be sure,  since there is not such version as 4.1.00, I would have assumed that same thing.

I personally don't want the alpha releases for daily use, if I am experiencing the issue it is correcting

then I will download, compile and use to see if it corrects the issue. Then when it is released as a full

full release then replace the alpha and retest and use.

Now since moving to the new condo and it is winter I will be operating mostly QRV from my car at a picnic

table.

I expect the original op was not to familiar with software version standards.


Marty kd8bj

On 2/28/19 9:59 AM, Bill Hamel wrote:
Hi David,

I’m not sure if the box you are showing pops up when you check for updates, if it is, what I’m seeing on a Mac is different.



If 4.1.0.1 is not supposed to be considered "the latest version" I’ll keep that in mind for future versions that are in the x of 4.1.0.x versioning.

Returning the message in the box you displayed would make more sense here.

I guess I got confused when I saw ver 4.1.00 which I thought meant 4.1.0.0

Thanks,
-bh k3tfm



On Feb 28, 2019, at 10:15 AM, Dave <@w1hkj <mailto:@w1hkj>> wrote:

Your statement is not true Bill.

<apjeacjpiapdeefk.png>

4.1.0.0 was and is an alpha version and it's numbering will always be in sync with the final distribution, ie:

4.1.0.1
4.1.0.2
4.1.0.n ===> results in a distribution of 4.1.0.

As an alpha user you have the responsibility to monitor either linuxham@groups.io, or nbems@groups.io, or winfldigi@groups.io for announcements regarding new distributions, or personally check Source Forge (or the w1hkj.com <http://w1hkj.com> site) for physical evidence of a new distribution.

The groups.io <http://groups.io> announcements always delineate what bugs have been fixed or changes implemented.

73, David, W1HKJ

On 2/28/19 8:54 AM, Bill Hamel wrote:
Not realizing that the Help -> “Check for updates” doesn’t actually check for updates since it kept tell me that no updates are available.

I manually found a v4.1.01 that says it fixes this problem in the release notes. I’ve installed it an it appears to be working now.

Thanks
-bh k3tfm

On Feb 27, 2019, at 9:34 PM, Bill Hamel <bill@... <mailto:bill@...>> wrote:

Good evening.

---
Fldigi 4.1.0.0
MAC OS High Sierra 10.13.6
Tsql: 2.4.3


When I try to use Fldigi to automatically update LoTW I get an error that says that the mode is missing, In this case PSK31

To help diagnose I unchecked the box that says “Quiet mode [-q], do not open tqsl dialog in Logbook->LoTW

Condition 1
==========
When I finish a QSO and write the log a box pops up that reports

—-------------------<SNIP>------------------------
Signing using Callsign K3TFM, DXCC Entity UNITED STATES OF AMERICA

Error: Invalid contact - QSO does not specify a mode on line 4
CALL: K5****
FREQ: 7.07269
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0206

Warning: Signing cancelled
No records to upload
---------------------</SNIP>————————————

Condition 2
===========
When I use Fldigi to try a LoTW batch by doing Logbook->LoTW->Export
I make sure I select the LoTW button so it checks the relevant fields
(Note that I also will check the “Mode” box and try it that way also since when clicking the “LoTW” button it does not check the mode box)
I then select “SEND” and the following log entries occur in the log file

Note actual calls masked with “*"
—-------------------<SNIP>------------------------
Wed Feb 27 20:41:28 2019 tqsl_getNumBand
Wed Feb 27 20:41:28 2019 check_tqsl_error: rval=1
Wed Feb 27 20:41:28 2019 check_tqsl_error: msg=Invalid contact - QSO does not specify a mode
Error: Invalid contact - QSO does not specify a mode on line 6
CALL: KG5***
FREQ: 7.07254
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0059

Wed Feb 27 20:41:28 2019 tqsl_getNumBand
Wed Feb 27 20:41:28 2019 check_tqsl_error: rval=1
Wed Feb 27 20:41:28 2019 check_tqsl_error: msg=Invalid contact - QSO does not specify a mode
Error: Invalid contact - QSO does not specify a mode on line 7
CALL: AA5***
FREQ: 7.07232
QSO_DATE: 20190228
BAND: 40m
TIME_ON: 0113

Wed Feb 27 20:41:28 2019 MyFrame::UploadLogFile: Log converted, status = 9, numrecs=0
---------------------</SNIP>————————————

Condition 3
--------------------
I can get it to work if I do the following

In FLDigi Logbook->ADIF->Export

Check the same boxes that I do above using the LoTW methods above

Export the adif

From within Tsql do a “Sign a log and upload it automatically to LoTW”

And my log is successfully uploaded to LoTW including the Mode information

Any insight greatly appreciated.

Thanks,
Bill K3TFM






Minor glitch

Ralph Alden Brigham
 

Hello and Greetings,

I have started having a problem with FLDigi recently - after I receive an
FLmsg or FLwrap file my program starts reading an .xml file into the
reception box and starts transmitting said.

Currently running Win10 Home
FLDigi 4.1.00

Current versions of Flmsg and FLwrap installed and behaving.

What have I mucked up?

-- ***** ---
Ralph Brigham KG4CSQ -- EM64RQ2OOQ
W5YI VE 33080; ARRL VE
ARRL #1000033463
ARES/RACES SKYWARN
(931) 906-9277
-- ****

Re: fldigi 4.1.01 release

Greg Siemasz <gregsiemasz@...>
 

Below are a couple of pic of my computer screen that explain what I am seeing in Fldigi 4.1.00
After I close the program with it on 14.070 it should load the next time but it doesn't. It opens on 7.070 instead.
This is done manually and not by any rig control.
I hope this helps.


Re: FLDIGI 4.1.0.0 LoTW mode field not exporting causing an error

Dave
 



You might expect to see something like the above if you are running a recent alpha version.  Not sure why you did not.

Note this is on a Mac.

David

Re: fldigi 4.1.01 release

Marty Hartwell
 

Hi

I just briefly tried this on my issue of Fldigi 4.1.0.1 and don't see this action with no rig connected

or configured in rig control. What I have in the large frequency window on the left in blue matches

what is the the smaller window on the right labeled Freq with the difference in the frequency + or -

the amount in the waterfall window as expected.

My first question is do you have any check marks in any of the three rig control methods "Flrig,

RigCat, or Hamlib". In my case I usually use Flrig and had a check mark in that tab, but nothing else,

as expected, in the other two tabs. If there is a check mark in one of those tabs then Fldigi may be

expecting to see a connection on the serial port.

Other then that I have no other ideas.

Good Luck.

Marty kd8bj

On 2/28/19 1:20 PM, Greg Siemasz wrote:
Below are a couple of pic of my computer screen that explain what I am seeing in Fldigi 4.1.00
After I close the program with it on 14.070 it should load the next time but it doesn't. It opens on 7.070 instead.
This is done manually and not by any rig control.
I hope this helps.


Re: fldigi 4.1.01 release

Greg Siemasz <gregsiemasz@...>
 

Marty,
No rig control no boxes checked in any of the three.
Greg

Re: fldigi 4.1.01 release

Greg Siemasz <gregsiemasz@...>
 

Dave,
Would you please let me know when you have a fix for the problems I reported.
I take it will be new version of software.
I would surly appreciate it.
Thank you.Greg

Matched pair alpha test suite

Dave
 

Please download and test this set of fldigi/flamp files if you have been experiencing lost blocks when transmitting large flamp files.  WN3LIF, WT, my intrepid tester and I have labored for the past two weeks to resolve this issue and this is the result.  We cannot make it break, but welcome any problem reports (and kudos as well).  The fix required changes in both flamp and fldigi.

Please note this configuration panel change in flamp

The "Tx Duration Mins" was limited to 1 minute intervals.  That has change to 0.05 minor and 1.0 major increments.  0.05 minutes ==> 3 minute.  The selection is enumerated in the control to the right labeled "mm:ss".

The flamp script parser has been changed to also work with fractional minutes; M.mm where mm is factors of 0.05.

73, David, W1HKJ


Re: fldigi 4.1.01 release

Dave
 

Your bug report is very local Greg.  I've tested on Linux, Windows and OS X sans rig control.  Change the frequency selection (using the top/bottom digit left click), close fldigi, restart and the last entered vfo value is displayed.  Works as it always has.

I have a feeling you might be using keyboard entry for the frequency entry.  If you are, then you must press the Enter key for the new frequency value to be a saved as a valid value.  The Enter key will also insure that the log control for frequency is based on the new entry.  Your screen shots show otherwise.

David

Re: fldigi 4.1.01 release

Greg Siemasz <gregsiemasz@...>
 

Dave,
I am not using any rig control.
I change the main frequency through the icon open list that looks like a little book next to the enter the call button. If I change that the frequency stays on 40m. If I close the program, it defaults to 40m
image.png
The Frq never changes and I never had this problem before.
image.png
Frq is stuck in 40m.
It never did that before. The frq always changed when I changed the frequency through open list icon.
Greg


On Thu, Mar 7, 2019 at 6:28 PM Dave <w1hkj@...> wrote:
Your bug report is very local Greg.  I've tested on Linux, Windows and OS X sans rig control.  Change the frequency selection (using the top/bottom digit left click), close fldigi, restart and the last entered vfo value is displayed.  Works as it always has.

I have a feeling you might be using keyboard entry for the frequency entry.  If you are, then you must press the Enter key for the new frequency value to be a saved as a valid value.  The Enter key will also insure that the log control for frequency is based on the new entry.  Your screen shots show otherwise.

David

Re: fldigi 4.1.01 release

Greg Siemasz <gregsiemasz@...>
 

Dave,
I have uninstalled the program and cleaned out registry and since you claim it is a local problem I am beginning to think it is not compatible with windows 10 which is constantly changing through upgrades.
It is beyond my control and have decided to remove it from computer for now.
I have never used a rig control and did frequency changes manually and as I explained, Flq always changed with respect to the "main" frequency and when I closed program and opened it again, it never defaulted back to 40 meters. It use to open on the frequency that I closed the program on. If it was 14.070, it would open back up on 14.070. If closed on 21.070 then it would open up on 21.070 not on 7.070 like it is doing now. Something is wrong.
Greg


On Fri, Mar 8, 2019 at 2:23 PM Greg Siemasz via Groups.Io <gregsiemasz=gmail.com@groups.io> wrote:
Dave,
I am not using any rig control.
I change the main frequency through the icon open list that looks like a little book next to the enter the call button. If I change that the frequency stays on 40m. If I close the program, it defaults to 40m
image.png
The Frq never changes and I never had this problem before.
image.png
Frq is stuck in 40m.
It never did that before. The frq always changed when I changed the frequency through open list icon.
Greg

On Thu, Mar 7, 2019 at 6:28 PM Dave <w1hkj@...> wrote:
Your bug report is very local Greg.  I've tested on Linux, Windows and OS X sans rig control.  Change the frequency selection (using the top/bottom digit left click), close fldigi, restart and the last entered vfo value is displayed.  Works as it always has.

I have a feeling you might be using keyboard entry for the frequency entry.  If you are, then you must press the Enter key for the new frequency value to be a saved as a valid value.  The Enter key will also insure that the log control for frequency is based on the new entry.  Your screen shots show otherwise.

David