FLDIGI and High Sierra - Incompatible

Discussion in 'Mac Ham Radio on macOS & iOS' started by K8GRR, Oct 21, 2017.

ad: L-HROutlet
ad: l-rl
ad: abrind-2
ad: Left-3
ad: Subscribe
ad: Left-2
ad: L-MFJ
  1. K8GRR

    K8GRR Premium Subscriber QRZ Page

    I just upgraded my OS from Sierra to High Sierra v 10.13, and neither FLDIGI nor FLRIG will talk to my Kenwood TS570D (with Signalink USB sound card). They worked fine before the upgrade. The icon for FLDIGI in my Dock now has a question mark over it.

    After finding that FLDIGI and FLRIG no longer work following the upgrade to High Sierra, I updated to what I believe is the most current version of FLDIGI: 4.0.11. I have not look for updates to FLRIG.

    Is there anything I can do configuration-wise - or do I have to wait until FLDIGI and FLRIG catch up with High Sierra?


    Brian K8GRR

    PS I have the same problem with WSJT-X
  2. K3DCW

    K3DCW QRZ Lifetime Member #212 Volunteer Moderator Platinum Subscriber Life Member QRZ Page

    Both Fldigi and Flrig work just fine with High Sierra. You may have to "reauthorize" the apps to run with the Gatekeeper protection in place (go to Applications, right click on the Fldigi app, and select "Open". When it asks if you're sure, say yes.)

    The SignaLink is only a sound device. You should select USB Audio Codec in your soundcard setup in Fldigi in order to use it. It has nothing else to do with Flrig/Fldigi not talking to your TS570D.

    Now, how do you have the CAT control configured for Fldigi/Flrig? A USB-Serial cable or something similar? Odds are the driver didn't load. One thing you can check is to see whether there are updated drivers for that device. Sometimes simply unplugging the device and plugging it back in will cause the drivers to load. Also, you SHOULD go to your Security and Privacy settings in System Preferences. Look at the General tab. Near the bottom should be an option that says something like "Some system software was blocked from loading". If that is present, hit "allow" and choose the software. This has been a problem with some of the built-in USB CAT ports in rigs using the SILabs chipset.


    Then what makes you think this is a Fldigi and Flrig problem? For the record, WSJT-X v1.8 rc2 and rc3 work just fine as well on High Sierra.
  3. K8GRR

    K8GRR Premium Subscriber QRZ Page

    Thanks for sharing your thoughts on this.

    I downloaded and installed a new Silabs driver and now FLDIGI and FLRIG appear to be functioning normally.

    WSJT-X is also now talking to Signalink and my radio. Before downloading the driver I also unplugged the Signalink from the Mac, restarted the Mac and then plugged it back in. The curious thing now is that instead of both input and output both being labeled "Audio CODEC" , output is now labeled "Audio CODEC 1" and input is labeled as "Audio CODEC 2" in the Midi Setup. This doesn't seem to affect how things function and they both appear simply as "Audio CEDEC in the FLDIGI "Audio Devices" configuration page.


    Brian K8GRR
  4. K5KTD

    K5KTD Ham Member QRZ Page

    Just updated to High Sierra, and fldigi 4.1.18 crashes unexpectedly. Logg caption follows. Help, pls:
    Process: fldigi [23128]
    Path: /Applications/HamSoftware/fldigi-4.1.18.app/Contents/MacOS/fldigi
    Identifier: com.w1hkj.fldigi
    Version: 4.1..18 (4.1..18)
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: fldigi [23128]
    User ID: 501

    Date/Time: 2021-02-06 16:31:29.995 -0600
    OS Version: Mac OS X 10.13.6 (17G14042)
    Report Version: 12
    Anonymous UUID: 81D0D27E-83E2-ABCB-1B6E-50907C2F930F

    Sleep/Wake UUID: 1BCDE281-43C6-4B62-ADDF-52D38908A6E3

    Time Awake Since Boot: 83000 seconds
    Time Since Wake: 8700 seconds

    System Integrity Protection: enabled

    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Exception Codes: 0x0000000000000001, 0x0000000000000000
    Exception Note: EXC_CORPSE_NOTIFY

    Termination Signal: Illegal instruction: 4
    Termination Reason: Namespace SIGNAL, Code 0x4
    Terminating Process: exc handler [0]

    Application Specific Information:
  5. K3DCW

    K3DCW QRZ Lifetime Member #212 Volunteer Moderator Platinum Subscriber Life Member QRZ Page

    Make sure that you have the correct version of Fldigi, not one compiled for the M1 processor. The one you want should be downloaded HERE

    Second, when starting Fldigi, make sure that you give it access to the network. Some people think that "why does it need to access my network?", and so they deny access. Fldigi doesn't need to access the network, but it does use some networking protocols internally to run so it needs to be authorized.

    Third, assuming that everything is correct above and that you're upgrading from a previously functional version of Fldigi, then your problems are likely related to corrupted preference files. This is a common cause of sudden Fldigi crashes and fortunately the solution is relatively simple. From the terminal, do the following: (Feel free to cut and paste these into the terminal if you’re not comfortable working from the terminal. Do NOT forget the “.” Right before the word fldigi in the line starting with cd)

    cd .fldigi
    mv fldigi_def.xml fldigi_def.old
    mv fldigi.prefs fldigi.prefs.old

    Now, restart Fldigi and the setup wizard should pop up. Set everything up again and you should be good to go.

    I know that some people also make a backup of a known-good preferences setup and save it for quick restoration. You basically do the same as above, but save the known good preferences as
    something like

  6. WV8A

    WV8A Ham Member QRZ Page

    At the groups.io linuxham page, W1HKJ announced he has posted High Sierra specific builds as of Feb 8.

    signed High Sierra dmgs
    Are now posted at http://www.w1hkj.com/high_sierra/


Share This Page