[Ham-Mac] Fldigi fails to fill in all fields

Sun Mar 2 16:48:20 EST 2014

Thanks for the advice Robert.  
     When RUMLog is active the logged QSOs go directly to my main log.  In the fldigi box I have Host=localhost; Port=7362; the send and read data boxes are NOT checked; and the log location is filled in and correct.  Do I need to change the host to the IP you mentioned?  At the bottom of the Logbook pulldown menu there is a box for "connect to server"--should this be checked?

     I have the country file loaded, but to make sure I downloaded a new copy and put it in the .fldigi folder and restarted the program.
     Here is the output for one QSO:
<FREQ:9>21.070629<CALL:6>WA4EEZ<MODE:5>PSK31<NAME:6>Leslie<QSO_DATE:8>20140302<QSO_DATE_OFF:8>20140302<TIME_OFF:6>011310<TIME_ON:6>011310<QTH:16>Saint Petersburg<RST_RCVD:3>599<RST_SENT:3>599<STATE:2>FL<NOTES:94>Leslie Johnson   070 359  Ninellas County
6601 Bougainvilla Ave So
Saint Petersburg, FL  33707<GRIDSQUARE:6>EL87ps<BAND:3>15m<COUNTRY:13>United States<TX_PWR:2>50<EOR>
     When this was imported directly or indirectly into RUMLog, the DXCC info is not taken from the country name and is <dxcc:2>-1.  If I manually put in the DXCC number (291 in this case) it will be moved correctly from fldigi to RUMLog and it will be <dxcc:3>291.  By the way, MacLoggerDX also does not automatically fill in the DXCC data when a QSO is imported from fldigi.

Maybe I am expecting too much for fldigi to correctly fill in the country DXCC number, but I assumed it would fill in all data, just as RUMLog and MacLoggerDX do with a QSO that originates within the programs.

Maybe it is just better to leave things alone because fldigi is working fine otherwise, and I can update the info correctly within RUMLog.

Thanks,
73, Scott  AA0AA

Message: 3
>Date: Sun, 2 Mar 2014 19:17:56 +0100
>From: IZ1TGH Roberto Waha <iz1tgh at gmail.com>
>To: Mac enthusiasts involved in amateur radio applications
>    <ham-mac at mailman.qth.net>
>Subject: Re: [Ham-Mac] Fldigi fails to fill in all fields
>Message-ID:
>    <CAJS4jVw1AL2fUCoBAyVX9GPromFp6VC5S8Y8fk9t9OgUJuhz0w at mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>Hi Scott!
>
>2014-03-02 18:25 GMT+01:00 Scott <cq_dx_de_aa0aa at yahoo.com>:
>
>> Hi all,
>>
>> I have found a source of DXCC=-1 errors in my log.  fldigi is not filling
>> in all of the fields.  The regular infor (qth, state, country, location,
>> etc.) is getting filled in but not the county, iota, cqz, ituz, cont, and
>> dxcc info.
>>
>
>You're probably missing a CTY.DAT file for Fldigi.
>Here you can find all the instructions.
>http://www.country-files.com/
>
>Another feature you may be missing is the direct connection between Fldigi
>and RUMLog through XML-RPC.
>Open RUMLog preferences, click on the Digi tab and set "127.0.0.1" in the
>Fldigi Host field, 7362 in the Port field and check both Read and Send
>(using CAT with Fldigi, which is definitely better than RUMLog CAT
>capabilities).
>In this way, you can also avoid using all the data of the Fldigi logger and
>use RUMLog as main logger by importing the callsign from Fldigi by clicking
>CMD-F.
>
>Ciao, 73!
>
>-- 
>+------------=* IZ1TGH Roberto Waha - IZ1TGH at gmail.com *=-------------+
>|          El Senyor ?s la meva for?a, el Senyor el meu cant.         |
>|       Ell m'ha estat la salvaci?. En Ell conf?o i no tinc por.      |
>+---------------------------------------------------------------------+
>
>
>------------------------------
>
>Message: 4
>Date: Sun, 2 Mar 2014 20:26:09 +0000
>From: Alan Hawrylyshen <alan at polyphase.ca>
>To: linuxham at yahoogroups.com, al7cr at arrl.net,    Mac enthusiasts involved
>    in amateur radio applications    <ham-mac at mailman.qth.net>
>Subject: Re: [Ham-Mac] [linuxham] Log to Aether Script
>Message-ID: <6B2F78DD-A0F4-4984-BAA1-29C60DC9BE0E at polyphase.ca>
>Content-Type: text/plain;    charset=windows-1252
>
>Wow - talk about an old thread - I am just seeing this now. 
>I suspect I am the author of the script that doesn?t work in these cases.
>I?m no fan of Apple Script either; but I?ll see if there is a good reason for why your use-case fails. It would hopefully be easy to fix.
>
>Cheers,
>Alan
>K2ACK
>M0WTH
>
>On 4 Apr 2013, at 14:16, Dick Kriss <aa5vu at att.net> wrote:
>
>> Dean AL7CR,
>> 
>> 
>> Sorry, I cannot duplicate the issue. I just typed your call into fldigi, did a fldigi lookup via HamQTH.com and then clicked on my "Log to Aether" macro. Your call with all of the data was logged to Aether. I had both fldigi and Aeter running before starting.
>> 
>> I personally do not use the "Log to Aether" option. I log everything in the fldigi Logbook, then export to Aether every few days.  The fldigi "Log to Aether" macro and script works fine under OSX 10.8.3 with fldigi-3.21.68.
>> 
>> Dick AA5VU
>> 
>> ----------
>>> 
>>> Wed Apr 3, 2013 4:13 pm (PDT) . Posted by:
>>> 
>>> "al7cr" al7cr
>>> 
>>> I have done some rather extensive testing of this script on several machines using several combinations of OS X version, Fldigi version, and Aether version. I have what at least to me are interesting results.
>>> 
>>> On my Snow Leopard machine using my current installation of OS X 10.6.8, Fldigi 3.21.68, and Aether 1.5.12 neither the python or the suggested Applescript script ever work. However, the python script DOES work with this software combination, with the below discussed limitations, if installed from scratch. Hence there is obviously some corruption somewhere in my current system. Sadly I was never able to get the Applescript script to ever function.
>>> 
>>> The limitation to the operation of the script is that one must NOT lookup call data by any method in Fldigi prior to running the Log to Aether script. If this is done the Log to Aether Script fails. If one does not run any Fldigi logbook lookup then the Log to Aether script works as advertised.
>>> 
>>> Why would you look up data in Fldigi prior to logging in Aether? My reason is to fill the data fields so that I have info for my macros to function, such as my contacts name and QTH. This limitation makes the script useless for my style of operation.
>>> 
>>> I do not mean to criticize the work of the ham who developed the script to help folks integrate the programs. I simply find the way the programs interact as very strange from my point of view. It would never have occurred to me that this was why the script was failing in a new installation. I only found this difficulty after a lot of testing.
>>> 
>>> My thanks to those who gave assistance to me. I will return to using the very nice Fldigi logbook while making contacts and simply importing them via ADIF to Aether once in a while.
>> 
>> 
>> __._,_.___
>> Reply via web post    Reply to sender    Reply to group    Start a New Topic    Messages in this topic (11)
>> RECENT ACTIVITY: New Members 12
>> Visit Your Group
>> Switch to: Text-Only, Daily Digest ? Unsubscribe ? Terms of Use ? Send us Feedback
>> .
>>  
>> __,_._,___
>
>
>
>------------------------------
>
>Message: 5
>Date: Mon, 3 Mar 2014 07:48:52 +1100
>From: Clifford Hynds <vk2ccj at gmail.com>
>To: Mac enthusiasts involved in amateur radio applications
>    <ham-mac at mailman.qth.net>
>Subject: Re: [Ham-Mac] Solved my FlDigi Audio Port Error 2 Problem
>    simple as dropping the sample rate
>Message-ID:
>    <CAGORupaAe3T1caAbcFcLZtHLeQ=qK6Ys1EzJk5GTzBKR1VawOg at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>Hello Dick,
>
>I was running native and yes before I had no issues so something changed I
>know not what ?, I am running under Mountain Lion ,
>Anyway I ran all day yesterday an was rock solid so I'll leave it at 11025
>for now,nice to be Windows free again mostly
>
>Cheers
>Cliff Vk2CCJ
>
>
>
>
>
>
>On Sun, Mar 2, 2014 at 11:07 PM, Richard Kriss <aa5vu at att.net> wrote:
>
>>
>> On Mar 1, 2014, at 11:40 PM, Clifford Hynds <vk2ccj at gmail.com> wrote:
>>
>> > Hi,
>> >
>> > I have been trying to figure this out and had to use that other OS so now
>> > back on the Mac just dropped the sample rate in the FlDigi sound card
>> > settings to 11025 and no more lockups
>> >
>> > Hope this helps someone,
>> >
>> > Using OSX 10.8.5 and latest FlDigi
>> >
>> > A side note does anyone know how to update to Mavericks without
>> destroying
>> > the Bootcamp Partition,?
>> >
>> > 73
>> > Cliff VK2CCJ
>>
>> Cliff,
>>
>> You changed from what setting to 11025?  I have been using the native
>> 44100 with fldigi for years under several different OS X releases with no
>> issues. You must have changed something else. I just remembered you may be
>> using the Windows version of fldigi under Bootcamp and there may be a
>> Windows issue with the sampling rate.
>>
>> I don't use Bootcamp so cannot comment on you other question. I was not
>> aware that updating to Mavericks would destroy a Bootcamp partition.
>>
>> Dick AA5VU
>> iMac with OS X 10.9.2
>>
>> ______________________________________________________________
>> Ham-Mac mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/ham-mac
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:Ham-Mac at mailman.qth.net
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>>
>
>
>------------------------------
>
>_______________________________________________
>Ham-Mac mailing list
>Ham-Mac at mailman.qth.net
>http://mailman.qth.net/mailman/listinfo/ham-mac
>
>
>End of Ham-Mac Digest, Vol 121, Issue 2
>***************************************
>
>
>