Date   
MFSK16 bandwidth?

Dave Colter WA1ZCN
 

Does anyone know what MFSK16’s precise bandwidth is? Or its official emissions designator? I’m wondering if it qualifies as an image emission under FCC rules, thus legal to use in the phone sub-bands.

73

Dave WA1ZCN

New alpha versions posted for fldigi and flrig

Dave
 

Re: fldigi 4.1.09.27 posted

Dave
 

I see you're asking about setting which modes be associated with the CW identifier.

I'll check the code base.

73, David, W1HKJ

On 3/28/20 2:41 PM, Dave wrote:

fldigi only transmits a station CW identification at the end of each transmission.  Enable that with the "Transmit callsign" check box on the IDs/CW panel.

A mode identifier can be transmitted as waterfall video text.  Look on the IDs/Video panel.

73, David, W1HKJ

On 3/28/20 2:16 PM, Dave, KI7VLV wrote:

Good day,

I was wondering why the CW ID modes button/functionality was removed from .09 under ID -> CW ?

Re: fldigi 4.1.09.27 posted

Dave
 

fldigi only transmits a station CW identification at the end of each transmission.  Enable that with the "Transmit callsign" check box on the IDs/CW panel.

A mode identifier can be transmitted as waterfall video text.  Look on the IDs/Video panel.

73, David, W1HKJ

On 3/28/20 2:16 PM, Dave, KI7VLV wrote:

Good day,

I was wondering why the CW ID modes button/functionality was removed from .09 under ID -> CW ?

Re: fldigi 4.1.09.27 posted

Dave, KI7VLV
 

Good day,

I was wondering why the CW ID modes button/functionality was removed from .09 under ID -> CW ?

fldigi waterfall inop/black #macos #flrig

Ted KK6CSO
 

I’m using flrig/fldigi (4.1.09) on my Mac laptop OS X 10.14.6.  I had trouble with the Waterfall not working/inop.  Completely black.  
Here’s why:  During the fldigi install process, I apparently did not “allow incoming" to the ports when prompted.  Just a habit...
 
To correct this, open System Preferences in the Dock.
Select the “Security and Privacy” pane.
     Select the “Privacy” tab.
          Then, in the left window, click on “Microphone” and in the right window under “Allow the apps below to access your microphone,” make sure fldigi is checked.  (You should not need to do a restart, but it never hurts). 
This will allow the signal from your interface unit (Yaesu SCU-17 in my case) to be displayed on the waterfall.  If needed, you can start with the values: -30 and 70 settings next to the” WF" tab in the lower left corner of the fldigi screen. 
 
Also, always make sure to, in order: 1) Radio-ON with USB cable plugged into your Mac from your interface  3)  Launch flrig (if that’s how you control fldigi) and then fldigi.
Now you should Open System Preferences again and select the “Sound” panel.  Make sure "USB Audio CODEC" is selected in both the Input and Output tabs.
 
Hope this helps someone.  I’m just figuring out all this as I go…
 
Ted
KK6CSO

Re: FLMsg/FLDigi Interface running on Ubuntu 19.10

Bart N5BLP
 

Ah, working with computers is such a never ending joy!

After I posted I shut everything down and went outside to do some yard work.  Couple hours later I fired everything up and tried again.  VOILA!  Everything works.
     FLMsg mode follows FLDigi.
     Autosend works.
     Message reception works.

My guess - and it's a stretch - is that after installation a reboot was required to get the xmlrpc address and port to work.

A word about "Transfer direct to executing flmsg".
     I've been using it that way with the windows versions for years and have never once had a problem.  And it's working now on Ubuntu.

Thanks for the prompt replies everyone.

Bart N5BLP

Re: FLMsg/FLDigi Interface running on Ubuntu 19.10

W. T. Jones
 

I'll second that!


73,
WT Jones
WN3LIF
ARRL Amateur Radio Emergency Service
wn3lif@... <---
Eastern PA Section Emergency Coordinator
http://www.w3luz.org
ares County
                Basic Cert epa


On 3/26/20 12:39 PM, K4IVE wrote:
Uncheck " Transfer direct to executing flmsg."
 
That function is a special case and causes more problems than it worth.
 
Kevin
K4IVE
 
 
Sent: Thursday, March 26, 2020 at 10:37 AM
From: "Bart N5BLP via Groups.Io" <bartpearl@...>
To: nbems@groups.io
Subject: [nbems] FLMsg/FLDigi Interface running on Ubuntu 19.10
I've been running this stuff on Windows for years and have begun experimenting with ubuntu linux (version 19.10).

I've got FLDigi versioin 4.1.06 running just fine.

With FLMsg version 4.0.11, I'm having trouble getting it to interface properly with FLDigi.  Here's what I've got going on:
    In FLDigi, I have the NBEMS interface configured as follows (the same way I have it configured on my Windows system):
      NBEMS data file interface enabled. Open in message folder DISabled.
      Transfer direct to executing flmsg enabled.
      Open with flmsg and open in browser DISabled.
    In FLMsg, I have it configured to sync modem to FLDigi (also the same way I have it configured on my Windows system).  All other FLMsg configurations are default.

With the above configuration, the received message apparently never gets transferred to FLMsg.  (And yes, I do have it up and running).  Nothing shows up in the Received Messages window or in the main FLMsg window.  Going the other way, Autosend doesn't work.  Nothing goes out.  Also, changing the modem in FLDigi does NOT result in the modem being changed in FLMsg.

I then tried it with Open with flmsg enabled (in FLDigi) and the proper path specified.  With that configuration, a new iteration of FLMsg is started and the message is displayed.  But this way I wind up with multiple iterations running.  Also, going the other way Autosend still doesn't work and the modem still doesn't follow FLDigi.

Any help getting FLMsg and FLDigi to interface properly would be greatly appreciated.

Bart N5BLP

Re: FLMsg/FLDigi Interface running on Ubuntu 19.10

K4IVE
 

Uncheck " Transfer direct to executing flmsg."
 
That function is a special case and causes more problems than it worth.
 
Kevin
K4IVE

 
 
Sent: Thursday, March 26, 2020 at 10:37 AM
From: "Bart N5BLP via Groups.Io" <bartpearl@...>
To: nbems@groups.io
Subject: [nbems] FLMsg/FLDigi Interface running on Ubuntu 19.10
I've been running this stuff on Windows for years and have begun experimenting with ubuntu linux (version 19.10).

I've got FLDigi versioin 4.1.06 running just fine.

With FLMsg version 4.0.11, I'm having trouble getting it to interface properly with FLDigi.  Here's what I've got going on:
    In FLDigi, I have the NBEMS interface configured as follows (the same way I have it configured on my Windows system):
      NBEMS data file interface enabled. Open in message folder DISabled.
      Transfer direct to executing flmsg enabled.
      Open with flmsg and open in browser DISabled.
    In FLMsg, I have it configured to sync modem to FLDigi (also the same way I have it configured on my Windows system).  All other FLMsg configurations are default.

With the above configuration, the received message apparently never gets transferred to FLMsg.  (And yes, I do have it up and running).  Nothing shows up in the Received Messages window or in the main FLMsg window.  Going the other way, Autosend doesn't work.  Nothing goes out.  Also, changing the modem in FLDigi does NOT result in the modem being changed in FLMsg.

I then tried it with Open with flmsg enabled (in FLDigi) and the proper path specified.  With that configuration, a new iteration of FLMsg is started and the message is displayed.  But this way I wind up with multiple iterations running.  Also, going the other way Autosend still doesn't work and the modem still doesn't follow FLDigi.

Any help getting FLMsg and FLDigi to interface properly would be greatly appreciated.

Bart N5BLP

Re: FLMsg/FLDigi Interface running on Ubuntu 19.10

Ron
 

Bart,

Here's a screen shot of my Fldigi, Misc, NBEMS Interface.



Open with flmsg has to be checked. I think you found that out when you said you checked in. So when you receive an Flmsg it will automatically open a new Flmsg if there are no errors or ask you if you want to open it if the checksum doesn't match. When you check Transfer direct to executing flmsg it won't automatically open but it will show you a list of messages that you can open. I don't like this because I've missed messages with errors and didn't know there were errors. I'd rather have every message open. Of course I have 2 monitors and plenty of desktop space :-)

I'm not sure why the Flmsg mode doesn't follow the Fldigi mode. Here's my Flmsg ARQ configuration.



With Sync modem to fldigi checked flmsg should follow fldigi mode changes.

73, Ron NY3J

On 3/26/20 11:37 AM, Bart N5BLP via Groups.Io wrote:
I've been running this stuff on Windows for years and have begun experimenting with ubuntu linux (version 19.10).

I've got FLDigi versioin 4.1.06 running just fine.

With FLMsg version 4.0.11, I'm having trouble getting it to interface properly with FLDigi.  Here's what I've got going on:
    In FLDigi, I have the NBEMS interface configured as follows (the same way I have it configured on my Windows system):
      NBEMS data file interface enabled. Open in message folder DISabled.
      Transfer direct to executing flmsg enabled.
      Open with flmsg and open in browser DISabled.
    In FLMsg, I have it configured to sync modem to FLDigi (also the same way I have it configured on my Windows system).  All other FLMsg configurations are default.

With the above configuration, the received message apparently never gets transferred to FLMsg.  (And yes, I do have it up and running).  Nothing shows up in the Received Messages window or in the main FLMsg window.  Going the other way, Autosend doesn't work.  Nothing goes out.  Also, changing the modem in FLDigi does NOT result in the modem being changed in FLMsg.

I then tried it with Open with flmsg enabled (in FLDigi) and the proper path specified.  With that configuration, a new iteration of FLMsg is started and the message is displayed.  But this way I wind up with multiple iterations running.  Also, going the other way Autosend still doesn't work and the modem still doesn't follow FLDigi.

Any help getting FLMsg and FLDigi to interface properly would be greatly appreciated.

Bart N5BLP

FLMsg/FLDigi Interface running on Ubuntu 19.10

Bart N5BLP
 

I've been running this stuff on Windows for years and have begun experimenting with ubuntu linux (version 19.10).

I've got FLDigi versioin 4.1.06 running just fine.

With FLMsg version 4.0.11, I'm having trouble getting it to interface properly with FLDigi.  Here's what I've got going on:
    In FLDigi, I have the NBEMS interface configured as follows (the same way I have it configured on my Windows system):
      NBEMS data file interface enabled. Open in message folder DISabled.
      Transfer direct to executing flmsg enabled.
      Open with flmsg and open in browser DISabled.
    In FLMsg, I have it configured to sync modem to FLDigi (also the same way I have it configured on my Windows system).  All other FLMsg configurations are default.

With the above configuration, the received message apparently never gets transferred to FLMsg.  (And yes, I do have it up and running).  Nothing shows up in the Received Messages window or in the main FLMsg window.  Going the other way, Autosend doesn't work.  Nothing goes out.  Also, changing the modem in FLDigi does NOT result in the modem being changed in FLMsg.

I then tried it with Open with flmsg enabled (in FLDigi) and the proper path specified.  With that configuration, a new iteration of FLMsg is started and the message is displayed.  But this way I wind up with multiple iterations running.  Also, going the other way Autosend still doesn't work and the modem still doesn't follow FLDigi.

Any help getting FLMsg and FLDigi to interface properly would be greatly appreciated.

Bart N5BLP

Re: fldigi 4.1.09.27 posted

Charles Hargrove
 

Sorry Bill. I missed the joke.

On 3/25/2020 2:54 PM, Bill Audley via Groups.Io wrote:
Sorry.  No Politics.
On Wednesday, March 25, 2020, 11:48:30 AM PDT, Charles Hargrove <n2nov@...> wrote:
Subject line says 27 but link is 26 on email and alpha webpage.
--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.

NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
http://www.nyc-arecs.org

NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32

"Information is the oxygen of the modern age. It seeps through the walls topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan

"The more corrupt the state, the more it legislates." - Tacitus

"Molann an obair an fear" - Irish Saying
(The work praises the man.)

"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan

Re: fldigi 4.1.09.27 posted

Dave
 

Re: fldigi 4.1.09.27 posted

Bill Audley
 

Sorry.  No Politics.




On Wednesday, March 25, 2020, 11:48:30 AM PDT, Charles Hargrove <n2nov@...> wrote:


Subject line says 27 but link is 26 on email and alpha webpage.

--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.

NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
http://www.nyc-arecs.org

NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32

"Information is the oxygen of the modern age. It seeps through the walls
topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan

"The more corrupt the state, the more it legislates." - Tacitus

"Molann an obair an fear" - Irish Saying
(The work praises the man.)

"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan



Re: fldigi 4.1.09.27 posted

Charles Hargrove
 

Subject line says 27 but link is 26 on email and alpha webpage.

--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.

NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
http://www.nyc-arecs.org

NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32

"Information is the oxygen of the modern age. It seeps through the walls topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan

"The more corrupt the state, the more it legislates." - Tacitus

"Molann an obair an fear" - Irish Saying
(The work praises the man.)

"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan

fldigi 4.1.09.27 posted

Dave
 

At http://www.w1hkj.com/alpha/fldigi

73, Dave, W1HKJ

alpha 4.1.09.27 - changes pos 4.1.09

  TUNE macro
   * Restore execution code for <TUNE
   * Retain delayed execution code for <!TUNE
   * Create new macro <@TUNE
   * All three versions allow tune interval to be spec'd
     in fractional seconds, i.e. 2.5, 5.1 10.0 15
   * <TUNE:nn.nn> used alone returns to receive
   * <TUNE:nn.nn> followed by text remains in transmit
     to complete the transmission.
   * Examples:
     . <TUNE:10.0>
     . <TUNE:5>
       <TX>tune test <!TUNE:1.5> de w1hkj k
       <RX>
       <@TUNE:2.5>

  RigCat config
    * restore missing control labels

  CW 5 wpm
    * 5 wpm farnsworth speed demands larger OUTBUFSIZE
      - increase output buffer to 65536

  audio alert
    * fix seg fault
      - test for existence of audio_alert instance

  analysis mode
    * changes to data file output - submitted by John Gibbons, N8OBJ

  flrig auto off
    * add ability to shutdown flrig/xcvr during fldigi shutdown

  maclogger
    * correct interpretation of UDP frequency string
    * update transceiver frequency based on UDP frequency

  mkappbundle
    * modify 'version' to include patch level

  nanoIO
    * Correct TTY interface code

  start/stop transitions
    * add code to soften the start/stop transitions for all modems

  CW DTR-RTS
    * generate CW on selected DTR/RTS signal line
    * CW DTR/RTS signals generated concurrent
      with AF counterparts and within a separate thread.

  Olivia 2 tones
    * correct trailing edge cutoff of postamble tones

  Xmlrpc Xcvr
    * enable QSY when Xmlrpc client xcvr is connected

  mp3
    * simplify mp3 conversions
      - test for file access using fopen
      - use linear sample rate converter

  contestia cr
    * correct suppression of <CR> display

  serial port
    * insure that DTR and RTS are always disabled when closing port

  Check Version
    * correct version check logic

Farnsworth timing segmentation fault

Dave
 

Alpha release fixes reported problem.
73, David, W1HKJ

alpha 4.1.09.25

    CW 5 wpm
      * 5 wpm farnsworth speed demands larger OUTBUFSIZE
        - increase output buffer to 65536

    audio alert
      * fix seg fault
        - test for existence of audio_alert instance

    analysis mode
      * changes to data file output - submitted by John Gibbons, N8OBJ

    flrig auto off
      * add ability to shutdown flrig/xcvr during fldigi
        shutdown

    maclogger
      * correct interpretation of UDP frequency string
      * update transceiver frequency based on UDP frequency

    mkappbundle
      * modify 'version' to include patch level

    nanoIO
      * Correct TTY interface code

    start/stop transitions
      * add code to soften the start/stop transitions for all
        modems

    CW DTR-RTS
      * generate CW on selected DTR/RTS signal line
      * CW DTR/RTS signals generated concurrent
        with AF counterparts and within a separate thread.

    Olivia 2 tones
      * correct trailing edge cutoff of postamble tones

    Xmlrpc Xcvr
      * enable QSY when Xmlrpc client xcvr is connected

    mp3
      * simplify mp3 conversions
        - test for file access using fopen
        - use linear sample rate converter

    TUNE macro
     * Restore execution code for <TUNE
     * Retain delayed execution code for <!TUNE

    contestia cr
      * correct suppression of <CR> display

    serial port
      * insure that DTR and RTS are always disabled when closing port

    Check Version
      * correct version check logic

Re: Fldigi works, Flrig doesn't...Port set-up problem in OS X? #macos #flrig

Ted KK6CSO
 

Good to hear Bill!
I’ve got flrig and fldigi playing well with my FT-857D except for the waterfall.
More on that to follow...

73
Ted  : )
_________________________

On Mar 15, 2020, at 7:53 AM, Bill <remnant.1@...> wrote:

Flrig is now playing nice on the Mac and with Fldigi thanks to Ted's advice on how to set up the USB drivers:


<dummyfile.0.part>

Thank you again Ted!

Bill de K0AN

Re: Fldigi works, Flrig doesn't...Port set-up problem in OS X? #macos #flrig

Bill de K0AN
 

Flrig is now playing nice on the Mac and with Fldigi thanks to Ted's advice on how to set up the USB drivers:




Thank you again Ted!

Bill de K0AN

Re: Trying to get FlRig working with TS890

Cathryn Mataga
 

Oh, thanks. That actually did work. Not sure what what happened, but it seemed to me rebooting and deleting those flrig.files must have healed it.

On 3/14/2020 5:54 AM, Dave wrote:

Cathryn,

  • Make sure that no other application is attached to the TS890 USB serial port.  This may require a computer reboot.
  • Delete the files that are found in \Users\<username>\flrig.files\.  Deleting the files insures that you will be starting the configuration anew.
  • Turn on the transceiver and configure the serial port(s) to 115200 baud
  • Start flrig  without fldigi or any other flxxx application
  • Configure flrig for the TS890S


    • Select the COM port from the list box.
    • Make sure you have selected the Virtual Standard COM and not the Virtual Enhanced COM port (used for CW/FSK keying)
    • Check that all of the controls are set as above and then press the Init button

The "Connected" indicator should illuminate if the connection is established with the transceiver.

If the connection occurs then you may proceed to test the various flrig main dialog controls for bi-directional control of the transceiver.

When you are satisfied that control is working correctly you may then start fldigi and configure it to use flrig as it's transceiver control agent.

73, David, W1HKJ

On 3/13/20 10:29 PM, Cathryn Mataga wrote:
I'm trying to get FlRig working with my TS890.   This is version 1.3.49.  This is connected to the USB port on the radio, which emulates a serial port. This same setting works with wsjt.  I tried turning on logging and got this as a result. I can never connect with the program.  Let me know if you need more information.