FLNet 7.2.3 for Mac download Missing

I cannot download this file for the MacOSX as the file is not in the directory.  Only the PC version is there.


Posted by: ki4tjy-/E1597aS9LQAvxtiuMwx3w@public.gmane.org


Recording Power in QSO Macro or Log

1) Is there any way for FLDIGI to sense the power during a QSO and insert it into a Macro, and then have this reading recorded in the log for that QSO?, As opposed to manually programing the macro with an entry that doesn't change with each QSO or manually entering the power for each QSO. 2) Then is there a way to automatically have the power of each QSO to be entered into the log?

Have read all the manual and checked all the configuration tabs and just can't find anything like this. AA4SB Steve

Posted by: r57s59-/E1597aS9LQAvxtiuMwx3w@public.gmane.org


Build fldigi on Mac OS X 10.9 Xcode 6.4- Issue with Build Dependency Port Audio


I was working on getting the build dependencies on my mac and hit a problem getting Port Audio to compile.  Has anyone successfully been able to get Port Audio to compile with Mac OS X 10.9?  I’m working with Xcode 6.4

Is there another option for getting port audio beside compiling from source code?  I’m following the build instructions on https://fedorahosted.org/fldigi/wiki/Documentation/HOWTO/BuildOnOSX

libtool: compile:  gcc -c -std=c99 -g -O2 -DPA_LITTLE_ENDIAN -I./include -I./src/common -I./src/os/unix -Werror -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=8 -DHAVE_NANOSLEEP=1 -DPA_USE_COREAUDIO=1 src/hostapi/coreaudio/pa_mac_core.c -o src/hostapi/coreaudio/pa_mac_core.o
src/hostapi/coreaudio/pa_mac_core.c:140:12: error: 'AudioDeviceGetPropertyInfo' is deprecated: first deprecated in OS X 10.6 [-Werror,-Wdeprecated-declarations]
   error = AudioDeviceGetPropertyInfo( hostApiDevice,
/System/Library/Frameworks/CoreAudio.framework/Headers/AudioHardwareDeprecated.h:783:1: note: 'AudioDeviceGetPropertyInfo' has been explicitly marked deprecated here
AudioDeviceGetPropertyInfo( AudioDeviceID           inDevice,

Thank you

Posted by: Timothy S Powell <kd4iky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


Mini Dell - Dell Inspiron Mini Netbook

I have been considering the purchase of the Dell Mini 10” screen for digital message use. I am looking for comments regarding it’s use please

Frank Fox
192 Isabella St
Hayward, CA 94544

Posted by: Frank Fox <frankcfx-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>


OT: CoAx connectors (was Re: FLdigi or signalink issue)


> Have a look here:
> http://www.qsl.net/vk3jeg/pl259tst.html
> Things are not always quite what they seem. At HF the PL259/SO239 is
> perfectly fine provided that the ground connections are well made and
> are kept tight.

(That link really shows UHF connectors in a bad light, to my eyes at least, as an 
RF technician up at VHF+   HF?  Indeed, much less of an RF issue, but...)

...Thereby hangs the problem.   The connectors often work loose over 
(sometimes a very short) time, due to thermal changes, differential 
expansion/contraction etc.   Our HF radios often run "quite warm", especially if 
you have one such shoved under a shelf, or have other kit stacked up on and 
arround it, plus the temperature varies a lot over a relativley short time.

Even 'N' plugs, can start to work loose because of that, but they do not rely on 
direct force from the locking ring for electrical continuity of the coax outer, as 
does the UHF series of connectors.

When they (259/239 connectors) were used for baseband Video, in those places 
the temperature was fairly stable, so such trouble was a lot less prevelant.   Plus, 
one could argue that the original manufactured parts were of much better 
material and quality anyway, so diferential expansion/contraction effects were 
less of an issue.

And as for mobile use...   Forget it.   From hard won personal experience, I now 
fit adapters to BNC for such duty, secured with LocTite, or similar.   They don't 
work loose!   BNC connectors will happily handle over 100W with ease at HF, 
even into a bad match.

As for N connectors being difficult to assemble?  And no instructions with them.   
Who's products and where are you getting them from?

All the N connectors I have ever used, have always come either loosely 
pre-assembled (so you carefully dismantle them keeping parts in the same 
order) or they have a slip of paper detailing how to fit the cable and assemble 
them correctly.    If deteriorating eyesight is an issue (it is for me now too for 
closeup work)  Use a magnifier, there are many types out there.   Bench mount, 
freestanding or worn on the head.

Has to be said though, I have also come across many such connectors in my 
proffesional life, that though fitted by "Pro's" were fitted badly or just plain 
wrong (even with the correct instructions!)  That eventually resulted in failure of 
the braid.

Where I work, we regularly shove 100's of Watts through N's.   In general, they 
are OK up to 1kW at 1GHz, into a good match it has to be said.   Higher powers, 
use SC or 7/16 connectors.   (That's "seven sixteen", not "seven sixteenths", it 
relates to the physical dimensions of the inner and outer contuctors.)

Though I've even seen 7/16 connectors fail at high power and bad VSWR (2kW 
at 20MHz into 15:1 SWR!   A BiConic EMC test antenna to be precice, the balun 
exploded too!)

7/16's were originally intended as low intermod parts for the cellular industry, so 
I was told.   Though they can handle high power, it was never the intention.

'SC' (Screwed C type) is a nice connector too, like a giant TNC.   Electrically and 
mechanically rock solid.   Often found on QRO microwave parts, such as TWT's 
output ports etc.   (They don't work loose, even with the extreme thermal cycling 
of those things!)

The similar 'C' is just crap mechanically, but they still seem to be popular in the 
US (if nowhere else...)   In good condition, good for over 2000W up to low UHF.   
When found in Ham circles in the UK, they are often used to carry the +HT to a 
valve (tube) based amplifier.

Defiantely!  :)

TNC's are very nice, but are not easy to find in general circulation outside of the 
USA.    BNC's (same internal dimensions) are cheap and plentiful by comparison.



Posted by: "Dave B" <g8kbvdave@...>


OT: Re: SignaLink and Other USB Digital Interfaces - Huge Bug - What about OSX

> Re: SignaLink and Other USB Digital Interfaces - Huge Bug - What
> abo
>     Posted by: "Ron Herring" w7hd@... w7hd
>     Date: Thu Jul 30, 2015 2:45 pm ((PDT))
> This only affects Windows Vista and Windows 7.  Linux and MAC are okay
> - they don't have the buggy Microsoft driver.  Win 8.1 and later are
> fine.

Win 7 is in effect Vista fixed!   There are a lot of similarities between the two.  
This "Bug" (or undocumented feature) appears to be another similarity...

Probably related to the change in the way the OS handles sound I/O, that was 
changed during the transition from XP (2000 with extra eye candy) to Vista.

A lot of popular soundcard based audio tools (and some SDR programs) would 
not work at all under Vista at first, until the authors updated them to handle the 
"new way" of doing sound I/O.   (I forget the exact differences...)



Posted by: "Dave B" <g8kbvdave@...>



re:" But the main factor is that it is difficult to assemble an N 
connector and is actually beyond the capabilities of many hams."

And that is really scary ,,,,,,

Just goes to show how far the "CB" group has came into ham,,,,,
Lets "Dumb it down some more" ........

2 UPC's from a Cracker Jack Box....and your a HAM!!!!!

KT4WO - Trip said that!!

Posted by: kt67 <kt4wo67@...>


SignaLink and Other USB Digital Interfaces - Huge Bug - What about OS X?

There’s a bug with the USB audio chipset used in many ham radio sound interfaces that occurs in windows vista and later. The affected chipset is the TI PCM2900 series PCM2904 and below, pre-C revisions

- All Icoms with built in USB Audio

- All Kenwoods with built in USB Audio

- All Yaesus with built in USB Audio, as well as the SCU-17 Interfac

- All Signalink USB

When you read the article it says "There’s a bug with the USB audio chipset used in many ham radio sound interfaces that occurs in windows vista and later.

What about OS X?  Anyone know if this bug shows up with OS X?

Dick AA5VU

Posted by: Richard Kriss <aa5vu-fOdFMYwuEsI@public.gmane.org>


follow up to OT post on win 10

Win 10 up and running on my desktop and laptop. In both cases grub was unaffected. Maybe MS IS finally learning how to play nice. Thanks to advice givers for useful info on workarounds.


Patricia Wilson
Apache Junction, AZ
Member NRA, ARRL
WB8DXX (Extra)

Posted by: Patricia Wilson <wilson.pr.gm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


Re: FLdigi or signalink

> Re: FLdigi or signalink issue
>     Posted by: "D.J.J. Ring, Jr." n1ea@... djringjr
>     Date: Tue Jul 28, 2015 6:22 am ((PDT))
> G8KBV Dave, great point about the UHF connector.  That piece of
> information eluded me for years, once solved, problems went away,
> signals improved as my connections were no longer intermittent on
> receive.
> 73 and a tap of the key in acknowledgement of a great post,
> David N1EA

Thanks David.   Much appreciated your time to reply.



Posted by: "Dave B" <g8kbvdave@...>


Way OT but will win10 upgrade wipe grub from a win7 ubuntu system?

Anybody here know?

"ab8o-ur4TIblo6goN+BqQ9rBEUg@public.gmane.org [linuxham]" <linuxham-hHKSG33TihhbjbujkaE4pw@public.gmane.org> wrote:

I see a 2MB log from yesterday listed under FLDIGI
File - Fldigi config - temp
This might be the one...
how do I point fldigi to use it or open it at least?

Posted by: Patricia Wilson <wilson.pr.gm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>