Date   
fldigi 4.1.04.11 posted

Dave
 

Development cycle alpha test

Date:   Mon May 20 10:24:21 2019 -0500

    main dialog title
      * force Windows to update window title when connecting to ACL

73, David, W1HKJ

FT-450 not powering on automatically?

Daniel Corwin
 

I'm having a problem where my FT-450 is not powering on when I start FLRig. If I send the appropriate commands (PS1;) it does power on. I then hit init in the transiver setup menu and I can control normally. When I close FLRig it shuts down the radio normally but it will not turn it back on.

PSKREPORTER no Spotted

Daniel
 


--
FLDIGI Pskreporter

Hello together, why does fldigi not make an entry in pskreporter?
Call sign is completed, locater with 6 character stands antene is also described and with settings generally psk reporter is active on gruen ...
Still no entry on pskreporter
Help...

73 Daniel

Re: NBEMS application version scheme

Dave
 

Current distribution versions of the NBEMS suite of programs can be found at http://www.w1hkj.com/files/

Current development versions of the NBEMS suite of can be found at http://www.w1hkj.com/alpha/

Drill down to the folder named for the application of interest.

Program Distribution Version Development Version
flaa 1.0.2 1.0.2.02
flamp 2.2.04 2.2.04.13
flcluster 1.0.4 1.0.4.02
fldigi 4.1.04 4.1.04.10
fllog 1.2.6 ---
flmsg 4.0.8 4.0.8.04
flrig 1.3.44 1.3.44.07
flnet 7.3.2 7.3.2.07
flwkey 1.2.3 1.2.3.05
flwrap 1.2.5 ---
linsim 2.0.3 ---
comptext 1.0.1 ---
comptty 1.0.1 ---

73,  David, W1HKJ

NBEMS application version scheme

Dave
 

At the request of 3rd party NBEMS developers I am changing the version numbering scheme for all NBEMS applications including fldigi, flarq, flrig, fllog etc.

The current triad numbering is still in effect: primary . secondary . tertiary, ie: fldigi-4.1.04

The change only applies to development cycle numbering: primary . secondary . tertiary . quaternary.  In the past the tertiary . quarternary would have bumped the tertiary number to the next release value.  In the future the tertiary will remain at the current release value.

fldigi-4.1.04  - current release

fldigi-4.1.04.28 - 28th development cycle release post 4.1.04.

73, David, W1HKJ

Re: 8PSK on 2 meters

Dave
 

Unless the transfer is 1:1 then use flmsg with ARQ.

Dave

On 5/15/19 6:29 PM, Ron via Groups.Io wrote:
Hi Klaus,

We also have an NBMES net on 2 meters and use either 8psk1000F or 8psk1200f.  Even though I have full scale at my location there still is a slight crackling noise and I don't get 100% copy. With that speed your reception has to be pretty close to full quieting. A few things to get better copy. I usually turn off digital squelch and unsquelch my radio. You get more noise text but better weak signal reception. In the PSK modem setting make sure everyone turns on the Pilot tone. If it's a repeater turn on the Pre-Signal Tone in the ID RsID setting to send a tone before your text. Make sure that your PTT delay is set. On my Signalink I have the DLY set to 12 o'clock. Of course audio setting, both transmit and receive has to be perfect. Not too low and not too high to distort the audio.

My personal opinion is if a large file is being sent with high speed then Flamp is better than Flmsg because you can ask for missing blocks instead of getting errors on the Flmsg and asking for the whole thing to be resent.

73, Ron NY3J

On 5/15/19 7:09 PM, khberkner@... wrote:
We run aa small fldigi/flmsg practice net on 2 meters.  Our workhorse mode has been MT63-2000L, but we have been exploring 8PSK and have been amazed by the increased speed (recognizing we give up the  error correction of MT63).

Here's my problem:  I used to have no problem decoding 8PSK 1200F until a few weeks ago.  Now I can't decode 1200F, although usually 1000F still works (most of the time).   None of the others on the net have this problem, and they can readily decode my 1200F transmissions.

I am running fldigi 4.1.03 and flmsg 4.0.8 on Windows 10.

Sometimes I get only gibberish, other times I see the text in the yellow screen, but no "wrap" at the beginning and hence no coupling to flmsg and my browser.

This has me baffled, and any thoughts would be appreciated.

Klaus K6KHB

Re: 8PSK on 2 meters

Ron
 

Hi Klaus,

We also have an NBMES net on 2 meters and use either 8psk1000F or 8psk1200f.  Even though I have full scale at my location there still is a slight crackling noise and I don't get 100% copy. With that speed your reception has to be pretty close to full quieting. A few things to get better copy. I usually turn off digital squelch and unsquelch my radio. You get more noise text but better weak signal reception. In the PSK modem setting make sure everyone turns on the Pilot tone. If it's a repeater turn on the Pre-Signal Tone in the ID RsID setting to send a tone before your text. Make sure that your PTT delay is set. On my Signalink I have the DLY set to 12 o'clock. Of course audio setting, both transmit and receive has to be perfect. Not too low and not too high to distort the audio.

My personal opinion is if a large file is being sent with high speed then Flamp is better than Flmsg because you can ask for missing blocks instead of getting errors on the Flmsg and asking for the whole thing to be resent.

73, Ron NY3J

On 5/15/19 7:09 PM, khberkner@... wrote:
We run aa small fldigi/flmsg practice net on 2 meters.  Our workhorse mode has been MT63-2000L, but we have been exploring 8PSK and have been amazed by the increased speed (recognizing we give up the  error correction of MT63).

Here's my problem:  I used to have no problem decoding 8PSK 1200F until a few weeks ago.  Now I can't decode 1200F, although usually 1000F still works (most of the time).   None of the others on the net have this problem, and they can readily decode my 1200F transmissions.

I am running fldigi 4.1.03 and flmsg 4.0.8 on Windows 10.

Sometimes I get only gibberish, other times I see the text in the yellow screen, but no "wrap" at the beginning and hence no coupling to flmsg and my browser.

This has me baffled, and any thoughts would be appreciated.

Klaus K6KHB

8PSK on 2 meters

khberkner@...
 

We run aa small fldigi/flmsg practice net on 2 meters.  Our workhorse mode has been MT63-2000L, but we have been exploring 8PSK and have been amazed by the increased speed (recognizing we give up the  error correction of MT63).

Here's my problem:  I used to have no problem decoding 8PSK 1200F until a few weeks ago.  Now I can't decode 1200F, although usually 1000F still works (most of the time).   None of the others on the net have this problem, and they can readily decode my 1200F transmissions.

I am running fldigi 4.1.03 and flmsg 4.0.8 on Windows 10.

Sometimes I get only gibberish, other times I see the text in the yellow screen, but no "wrap" at the beginning and hence no coupling to flmsg and my browser.

This has me baffled, and any thoughts would be appreciated.

Klaus K6KHB

Re: Modem Macro not working

Ron
 

WT,

I had the same thing happen with 4.1.03. I was able to fix it by entering <WAIT:00.1> between the MODEM and the TX command. Dave fixed it in 4.1.04.02. The latest Alpha is 4.1.04.07 so give that a try.

73, Ron NY3J

On 5/10/19 11:42 PM, W. T. Jones wrote:
Good Evening All,

I usually put a modem command in my macros so that I switch back to Thor22 as NCS for typing.
Last Thursday night I noticed that I was not switching modes after sending in Flamp. So I put a quick macro together to test it.

This is the macro...
<MODEM:THOR22>
<!DIGI>
<TX>

de <MYCALL>
-----
Fldigi was in 8PSK1200F modem. The macro should have changed the modem to Thor 22. The <!DIGI> reported 8PSK1200F and Fldigi's status line at the bottom reported 8PSK1200F as well. Tested with other modems and the same results. The MACRO command in the modem did not change the modem.

If the modem command is changed to inline execution it works.

System: Ubuntu 18.04LTS (latest patches)
Also tested on Windows 10 - same results.
Downloaded the 4.01.04.01 Alpha and tested on Ubuntu with the same results.

Anyone else seeing this behavior?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

Modem Macro not working

W. T. Jones
 

Good Evening All,

I usually put a modem command in my macros so that I switch back to Thor22 as NCS for typing.
Last Thursday night I noticed that I was not switching modes after sending in Flamp. So I put a quick macro together to test it.

This is the macro...
<MODEM:THOR22>
<!DIGI>
<TX>

de <MYCALL>
-----
Fldigi was in 8PSK1200F modem. The macro should have changed the modem to Thor 22. The <!DIGI> reported 8PSK1200F and Fldigi's status line at the bottom reported 8PSK1200F as well. Tested with other modems and the same results. The MACRO command in the modem did not change the modem.

If the modem command is changed to inline execution it works.

System: Ubuntu 18.04LTS (latest patches)
Also tested on Windows 10 - same results.
Downloaded the 4.01.04.01 Alpha and tested on Ubuntu with the same results.

Anyone else seeing this behavior?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

Re: Raspberry PI 7 Touchscreen and Resolution at 800x600 #flmsg

Dave
 

Download the source archive, fldigi-4.1.03.tar.gz.  You cannot just reduce the size of the main dialog without seriously effecting the final product.  Some of the contained controls (widgets in Unix speak) are size constrained by design.  The raster image controls for feldhell and wefax are in that category.

What steps have you take to reduce the vertical height of the main dialog?

Try reduce the vertical size of the waterfall to the minimum of 100 (or less by code change)

Dave

Re: Raspberry PI 7 Touchscreen and Resolution at 800x600 #flmsg

Curly Frazier
 

Unsubscribe


On Tue, May 7, 2019, 12:46 Aaron Jones <aaron@...> wrote:
Hello,

I researched this a bit but couldn't find a thread specifically to use of the Raspberry PI3 and the Raspberry PI 7" touchscreen.  The max you can run the screen at is 800x600 resolution which is pretty small.  I have been able to resize the FLDIG interface such that everything fits by using fewer macro rows and smaller fonts.  However, when I run FLMSG I cannot get the full screen to fit so if I try to use ARQ when you open  the ARQ inteface on FLMSG it goes below the screen, moving the window as far above the title bar as you can move with the mouse allows a partial view.  Is there a way to allow screens to be further sizeable vertically below current limits?

Re: Raspberry PI 7 Touchscreen and Resolution at 800x600 #flmsg

Ronald Pfeiffer
 

If the user interface was developed using fluid is the file available to
users for editing?

On May 7, 2019 at 4:14 PM Brian <@VE3IBW> wrote:


I have the same setup as you and here is what I found works:
1. Change the geometry when you startup FLxxx programs. Most FLxxx
programs support a -g switch. See
http://www.w1hkj.com/FldigiHelp/command_line_switches_page.html for the
command line switch. I set mine to 750x480 (e.g., fldigi *-g 750x400)*
2. Use the alt key and the mouse to move the window around. This is a
Linux thing, not an FLxxx thing. See this link for an explanation:
https://forums.linuxmint.com/viewtopic.php?t=264172

regards,
Brian
VE3IBW


On Tue, May 7, 2019 at 2:46 PM Aaron Jones <aaron@...> wrote:

Hello,

I researched this a bit but couldn't find a thread specifically to use of
the Raspberry PI3 and the Raspberry PI 7" touchscreen. The max you can run
the screen at is 800x600 resolution which is pretty small. I have been
able to resize the FLDIG interface such that everything fits by using fewer
macro rows and smaller fonts. However, when I run FLMSG I cannot get the
full screen to fit so if I try to use ARQ when you open the ARQ inteface
on FLMSG it goes below the screen, moving the window as far above the title
bar as you can move with the mouse allows a partial view. Is there a way
to allow screens to be further sizeable vertically below current limits?




Re: Raspberry PI 7 Touchscreen and Resolution at 800x600 #flmsg

Brian
 

The other thing I do is "maximize" the Fldigi main window.  This seems to help resize many of the UI controls so that it can mostly fit within the 7" screen 800x480.  I do still have to use the alt-mouse trick to move the FLdigi window up so that it covers the Raspbian main menu bar across the top of the screen.  If I am running FLdigi, I really don't need access to the Raspbian top bar all that often.  When I do, I just alt-mouse to nudge the maximized window down.

Aaron, you are correct, now that I recall, the geometry switch setting only helped somewhat.  Other apps, like wsjtx, seem better at resizing to fit smaller form factors than FLdigi.

regards, 
Brian
VE3IBW

On Tue, May 7, 2019 at 6:07 PM Aaron Jones <aaron@...> wrote:

All,


thanks for the feedback.  I find that no matter how i set my command line switch I can't get below the minimum geometry of 800x600. 


HOWEVER - the alt key + mouse click to move the window helps a ton, I did not know that linux feature. 


Thanks again.


Aaron

AG7GK

https://www.ag7gk.org


On 5/7/2019 1:14 PM, Brian wrote:
I have the same setup as you and here is what I found works:
1. Change the geometry when you startup FLxxx programs.  Most FLxxx programs support a -g switch.  See http://www.w1hkj.com/FldigiHelp/command_line_switches_page.html for the command line switch.  I set mine to 750x480 (e.g., fldigi -g 750x400)
2. Use the alt key and the mouse to move the window around.  This is a Linux thing, not an FLxxx thing.  See this link for an explanation: https://forums.linuxmint.com/viewtopic.php?t=264172

regards,
Brian
VE3IBW


On Tue, May 7, 2019 at 2:46 PM Aaron Jones <aaron@...> wrote:
Hello,

I researched this a bit but couldn't find a thread specifically to use of the Raspberry PI3 and the Raspberry PI 7" touchscreen.  The max you can run the screen at is 800x600 resolution which is pretty small.  I have been able to resize the FLDIG interface such that everything fits by using fewer macro rows and smaller fonts.  However, when I run FLMSG I cannot get the full screen to fit so if I try to use ARQ when you open  the ARQ inteface on FLMSG it goes below the screen, moving the window as far above the title bar as you can move with the mouse allows a partial view.  Is there a way to allow screens to be further sizeable vertically below current limits?

Re: Raspberry PI 7 Touchscreen and Resolution at 800x600 #flmsg

Aaron Jones
 

All,


thanks for the feedback.  I find that no matter how i set my command line switch I can't get below the minimum geometry of 800x600. 


HOWEVER - the alt key + mouse click to move the window helps a ton, I did not know that linux feature. 


Thanks again.


Aaron

AG7GK

https://www.ag7gk.org


On 5/7/2019 1:14 PM, Brian wrote:
I have the same setup as you and here is what I found works:
1. Change the geometry when you startup FLxxx programs.  Most FLxxx programs support a -g switch.  See http://www.w1hkj.com/FldigiHelp/command_line_switches_page.html for the command line switch.  I set mine to 750x480 (e.g., fldigi -g 750x400)
2. Use the alt key and the mouse to move the window around.  This is a Linux thing, not an FLxxx thing.  See this link for an explanation: https://forums.linuxmint.com/viewtopic.php?t=264172

regards,
Brian
VE3IBW


On Tue, May 7, 2019 at 2:46 PM Aaron Jones <aaron@...> wrote:
Hello,

I researched this a bit but couldn't find a thread specifically to use of the Raspberry PI3 and the Raspberry PI 7" touchscreen.  The max you can run the screen at is 800x600 resolution which is pretty small.  I have been able to resize the FLDIG interface such that everything fits by using fewer macro rows and smaller fonts.  However, when I run FLMSG I cannot get the full screen to fit so if I try to use ARQ when you open  the ARQ inteface on FLMSG it goes below the screen, moving the window as far above the title bar as you can move with the mouse allows a partial view.  Is there a way to allow screens to be further sizeable vertically below current limits?

Re: Raspberry PI 7 Touchscreen and Resolution at 800x600 #flmsg

Brian
 

I have the same setup as you and here is what I found works:
1. Change the geometry when you startup FLxxx programs.  Most FLxxx programs support a -g switch.  See http://www.w1hkj.com/FldigiHelp/command_line_switches_page.html for the command line switch.  I set mine to 750x480 (e.g., fldigi -g 750x400)
2. Use the alt key and the mouse to move the window around.  This is a Linux thing, not an FLxxx thing.  See this link for an explanation: https://forums.linuxmint.com/viewtopic.php?t=264172

regards,
Brian
VE3IBW


On Tue, May 7, 2019 at 2:46 PM Aaron Jones <aaron@...> wrote:
Hello,

I researched this a bit but couldn't find a thread specifically to use of the Raspberry PI3 and the Raspberry PI 7" touchscreen.  The max you can run the screen at is 800x600 resolution which is pretty small.  I have been able to resize the FLDIG interface such that everything fits by using fewer macro rows and smaller fonts.  However, when I run FLMSG I cannot get the full screen to fit so if I try to use ARQ when you open  the ARQ inteface on FLMSG it goes below the screen, moving the window as far above the title bar as you can move with the mouse allows a partial view.  Is there a way to allow screens to be further sizeable vertically below current limits?

Re: Raspberry PI 7 Touchscreen and Resolution at 800x600 #flmsg

J T
 

You can commpress desktop space down so as to get more on the screen by setting the resolution in the config.txt file to a resolution of 1280 x 760 which will fill the screen - a type of “pixel-doubling.” Get your reading glasses out though - you’ll need’em.

Jeff - KG7HDZ

On May 7, 2019, at 11:46 AM, Aaron Jones <aaron@...> wrote:

Hello,

I researched this a bit but couldn't find a thread specifically to use of the Raspberry PI3 and the Raspberry PI 7" touchscreen.  The max you can run the screen at is 800x600 resolution which is pretty small.  I have been able to resize the FLDIG interface such that everything fits by using fewer macro rows and smaller fonts.  However, when I run FLMSG I cannot get the full screen to fit so if I try to use ARQ when you open  the ARQ inteface on FLMSG it goes below the screen, moving the window as far above the title bar as you can move with the mouse allows a partial view.  Is there a way to allow screens to be further sizeable vertically below current limits?

<FLMSG_SIZING_RPI.jpg><FULLSCREENFLDIGIRPI.jpg>

Re: Raspberry PI 7 Touchscreen and Resolution at 800x600 #flmsg

Dave
 

You would need to modify the flmsg source to reduce the vertical space needed by the user interface.

David

Raspberry PI 7 Touchscreen and Resolution at 800x600 #flmsg

Aaron Jones
 

Hello,

I researched this a bit but couldn't find a thread specifically to use of the Raspberry PI3 and the Raspberry PI 7" touchscreen.  The max you can run the screen at is 800x600 resolution which is pretty small.  I have been able to resize the FLDIG interface such that everything fits by using fewer macro rows and smaller fonts.  However, when I run FLMSG I cannot get the full screen to fit so if I try to use ARQ when you open  the ARQ inteface on FLMSG it goes below the screen, moving the window as far above the title bar as you can move with the mouse allows a partial view.  Is there a way to allow screens to be further sizeable vertically below current limits?

flrig 1.3.44 posted

Dave
 

Version 1.3.44 * Maintenance release

?? IC mode type
?????? * add missing generic get_modetype

Effects the sideband sense of modes like CW/CW-R, RTTY/RTTY-R for a number of Icom transceivers including the Icom 7300.

73, David, W1HKJ