Date   
flrig 1.3.42 posted

Dave
 

At www.w1hkj.com

And Source Forge.

Source Forge git repository updated.

Version 1.3.42

  FT1000 debugging
    add trace debugging statements to FT1000 backend
  FLTK 1.4 test
    add test for valid FLTK 1.4 lib/headers
  FTdx3000
   add ALC read
   add power out calibration table
  Parse -psn
    correct launch issue on recent MacOS update

73, David, W1HKJ


flamp 2.2.04 posted

Dave
 

At www.w1hkj.com

And Source Forge.  Source Forge git repository master branch updated to 2.2.04.

Version 2.0.4

  Thumb Drive
    * Correct home drive assignment when executable located on a thumb drive device

  OS X build scripts
    * Modify script to only build dmg with dylibs

  win-mingw
    * update to mingw target code

  flxmlrpc config
    * change flxmlrpc configure summary report

  INSTALL
    * update file contents

  fix xmlRpc tm_mday comparison typo, author: Kamal Mostafa <kamal@...>
    xmlrpcpp/XmlRpcValue.cpp: In function ‘bool XmlRpc::tmEq(const tm&,const tm&)’:
    xmlrpcpp/XmlRpcValue.cpp:159:52: warning: self-comparison always
    evaluates to true [-Wtautological-compare]
      t1.tm_hour == t2.tm_hour && t1.tm_mday == t1.tm_mday &&

  mxe update
    * corrected build scripts

  Fldigi on-line
    * Add check for existence of fldigi at start
      - warn if fldigi not on line, exit
    * Test for fldigi presence and exit gracefully if fldigi is closed before flamp

73, David, W1HKJ

Shortwave Radiogram, 1-3 February 2019

kd9xb
 

Shortwave Radiogram this weekend is in the usual mix of MFSK32 and MFSK64. The winner of the Tecsun Radios Australia decoding competition will be announced.

There will, however, be a special DRM-only edition of Shortwave Radiogram testing super-fast text modes, today (Friday), 1500-1530 UTC, 13690 kHz from WINB Pennsylvania. 

http://swradiogram.net/post/182470963662/shortwave-radiogram-1-3-february-2019-and-the

Kim
KD9XB

Re: [winfldigi] Fldigi ver 4.1.00 Not Loading Fields from QRZ

Dave
 

I have been receiving QRZ query issues when made from fldigi.  My W1HKJ QRZ account is current:



I tested the following versions with identical unsuccessful query requests to QRZ.com

  • 4.1.00  (released Jan 31 2019)
  • 4.0.18
  • 4.0.17
  • 4.0.16
  • 4.0.14
  • ...
  • 3.23.14 (released Jan 29 2017)
The 3.23.14 test was to insure that no change in the fldigi socket interface code caused the problem.  The most recent version of fldigi supports both IPV4 and IPV6 network protocol.

Did you change the server protocol?  Please advise.  I have filed a service request on the QRZ.com website.

Thank you.

73, David, W1HKJ
fldigi principal developer

The socket data stream i/o is basically the same for all versions

QRZ.COM socket stream:

Q: main: fldigi 4.1.00 log started on Fri Feb  1 15:38:47 2019

D: [15:39:28] misc/threads.cxx:101: fldigi thread 2 is LWP 4576
I: [15:39:28] logbook/lookupcall.cxx:1142: Request sent to
qrz.com...
V: [15:39:28] logbook/lookupcall.cxx:127: QRZ session key query:
GET /bin/xml?username=w1hkj;password=########;version=fldigi/4.1.00 HTTP/1.0
Host: xml.qrz.com
Connection: close



V: [15:39:28] misc/network.cxx:51:
========================================================================
node: xml.qrz.com
service: http
========================================================================
D: [15:39:28] misc/socket.cxx:634:
Address    [107.21.98.143]:80
Family     AF_INET
Sock type  1
Protocol   6
I: [15:39:28] misc/socket.cxx:643: Trying [107.21.98.143]:80
I: [15:39:28] misc/socket.cxx:942:  Connected to sockfd 58: [107.21.98.143]:80
V: [15:39:28] misc/network.cxx:72:
=============================== SENT ===================================
GET /bin/xml?username=w1hkj;password=perri06;version=fldigi/4.1.00 HTTP/1.0
Host: xml.qrz.com
Connection: close


========================================================================
V: [15:39:29] misc/network.cxx:82:
============================== REPLY ===================================
HTTP/1.1 400 Bad Request
Date: Fri, 01 Feb 2019 21:39:29 GMT
Server: Apache/2.4.29 (Ubuntu)
Content-Length: 318
Connection: close
Content-Type: text/html; charset=iso-8859-1



The same type of request made to HamQTH.com (European provider) with an IPV6 capable server works every time and is very fast.

www.hamqth.com socket stream:

Q: main: fldigi 4.1.00 log started on Fri Feb  1 16:02:06 2019

D: [16:02:38] misc/threads.cxx:101: fldigi thread 2 is LWP 5400
I: [16:02:38] logbook/lookupcall.cxx:1164: Request sent to https://www.hamqth.com/
V: [16:02:38] misc/network.cxx:51:
========================================================================
node: www.hamqth.com
service: http
========================================================================
D: [16:02:38] misc/socket.cxx:634:
Address    [2001:41d0:2:7d6b::]:80
Family     AF_INET6
Sock type  1
Protocol   6
D: [16:02:38] misc/socket.cxx:634:
Address    [94.23.250.107]:80
Family     AF_INET
Sock type  1
Protocol   6
I: [16:02:38] misc/socket.cxx:643: Trying [94.23.250.107]:80
I: [16:02:38] misc/socket.cxx:942:  Connected to sockfd 58: [94.23.250.107]:80
V: [16:02:38] misc/network.cxx:72:
=============================== SENT ===================================
GET /xml.php?u=w1hkj&p=###### HTTP/1.0
Host: www.hamqth.com
Connection: close
 

========================================================================
V: [16:02:38] misc/network.cxx:82:
============================== REPLY ===================================
HTTP/1.1 200 OK
Date: Fri, 01 Feb 2019 22:02:38 GMT
Server: Apache/2.4.18 (Ubuntu)
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: nette-browser=6zkk4yu2em; path=/; domain=.hamqth.com; httponly
Set-Cookie: PHPSESSID=v1ke0svh66roitjvbqgegg7297; expires=Sun, 03-Mar-2019 22:02:38 GMT; Max-Age=2592000; path=/; domain=.hamqth.com; HttpOnly
Set-Cookie: hamqthlang=en; expires=Sun, 12-May-2019 22:02:38 GMT; Max-Age=8640000
Vary: Accept-Encoding
Content-Length: 187
Connection: close
Content-Type: application/xml
 
<?xml version="1.0"?>
<HamQTH version="2.8" xmlns="http://www.hamqth.com">
    <session>
        <session_id>12c4c637b51f45aabdd775f573af7af57ebdffa7</session_id>
    </session>
</HamQTH>
========================================================================
I: [16:02:38] misc/socket.cxx:655: sockfd 58
V: [16:02:38] logbook/lookupcall.cxx:131: HamQTH session id data:
12c4c637b51f45aabdd775f573af7af57ebdffa7

V: [16:02:38] logbook/lookupcall.cxx:127: HamQTH query:
http://www.hamqth.com/xml.php?id=12c4c637b51f45aabdd775f573af7af57ebdffa7&callsign=w1hkj&prg=FLDIGI

V: [16:02:38] misc/network.cxx:51:
========================================================================
node: www.hamqth.com
service: http
========================================================================
D: [16:02:39] misc/socket.cxx:634:
Address    [2001:41d0:2:7d6b::]:80
Family     AF_INET6
Sock type  1
Protocol   6
D: [16:02:39] misc/socket.cxx:634:
Address    [94.23.250.107]:80
Family     AF_INET
Sock type  1
Protocol   6
I: [16:02:39] misc/socket.cxx:643: Trying [94.23.250.107]:80
I: [16:02:39] misc/socket.cxx:942:  Connected to sockfd 58: [94.23.250.107]:80
V: [16:02:39] misc/network.cxx:72:
=============================== SENT ===================================
GET /xml.php?id=12c4c637b51f45aabdd775f573af7af57ebdffa7&callsign=w1hkj&prg=FLDIGI HTTP/1.0
Host: www.hamqth.com
Connection: close
 

========================================================================
V: [16:02:39] misc/network.cxx:82:
============================== REPLY ===================================
HTTP/1.1 200 OK
Date: Fri, 01 Feb 2019 22:02:39 GMT
Server: Apache/2.4.18 (Ubuntu)
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: nette-browser=j6p9nv6ggx; path=/; domain=.hamqth.com; httponly
Set-Cookie: PHPSESSID=cr4aqfl0udnnu56vhih9elclf7; expires=Sun, 03-Mar-2019 22:02:39 GMT; Max-Age=2592000; path=/; domain=.hamqth.com; HttpOnly
Set-Cookie: hamqthlang=en; expires=Sun, 12-May-2019 22:02:39 GMT; Max-Age=8640000
Vary: Accept-Encoding
Content-Length: 1081
Connection: close
Content-Type: application/xml
 
<?xml version="1.0"?>
<HamQTH version="2.8" xmlns="http://www.hamqth.com">
    <search>
        <callsign>w1hkj</callsign>
        <nick>David</nick>
        <qth>Toney</qth>
        <country>United States</country>
        <adif>291</adif>
        <itu>8</itu>
        <cq>4</cq>
        <grid>EM64</grid>
        <adr_name>David H Freese</adr_name>
        <adr_street1>106 Whitfield Drive</adr_street1>
        <adr_city>Toney</adr_city>
        <adr_zip>35773</adr_zip>
        <adr_country>United States</adr_country>
        <adr_adif>291</adr_adif>
        <us_state>AL</us_state>
        <us_county>Madison</us_county>
        <lotw>Y</lotw>
        <qsldirect>?</qsldirect>
        <qsl>Y</qsl>
        <eqsl>Y</eqsl>
        <email>w1hkj@...</email>
        <birth_year>1938</birth_year>
        <lic_year>1957</lic_year>
        <latitude>34.9</latitude>
        <longitude>-86.72</longitude>
        <continent>NA</continent>
        <utc_offset>6</utc_offset>
        <picture>http://www.hamqth.com/images/default/ts-930.jpg</picture>
    </search>
</HamQTH>
========================================================================
I: [16:02:39] misc/socket.cxx:655: sockfd 58
V: [16:02:39] logbook/lookupcall.cxx:131: HamQth html data:
HTTP/1.1 200 OK
Date: Fri, 01 Feb 2019 22:02:39 GMT
Server: Apache/2.4.18 (Ubuntu)
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: nette-browser=j6p9nv6ggx; path=/; domain=.hamqth.com; httponly
Set-Cookie: PHPSESSID=cr4aqfl0udnnu56vhih9elclf7; expires=Sun, 03-Mar-2019 22:02:39 GMT; Max-Age=2592000; path=/; domain=.hamqth.com; HttpOnly
Set-Cookie: hamqthlang=en; expires=Sun, 12-May-2019 22:02:39 GMT; Max-Age=8640000
Vary: Accept-Encoding
Content-Length: 1081
Connection: close
Content-Type: application/xml
 
<?xml version="1.0"?>
<HamQTH version="2.8" xmlns="http://www.hamqth.com">
    <search>
        <callsign>w1hkj</callsign>
        <nick>David</nick>
        <qth>Toney</qth>
        <country>United States</country>
        <adif>291</adif>
        <itu>8</itu>
        <cq>4</cq>
        <grid>EM64</grid>
        <adr_name>David H Freese</adr_name>
        <adr_street1>106 Whitfield Drive</adr_street1>
        <adr_city>Toney</adr_city>
        <adr_zip>35773</adr_zip>
        <adr_country>United States</adr_country>
        <adr_adif>291</adr_adif>
        <us_state>AL</us_state>
        <us_county>Madison</us_county>
        <lotw>Y</lotw>
        <qsldirect>?</qsldirect>
        <qsl>Y</qsl>
        <eqsl>Y</eqsl>
        <email>w1hkj@...</email>
        <birth_year>1938</birth_year>
        <lic_year>1957</lic_year>
        <latitude>34.9</latitude>
        <longitude>-86.72</longitude>
        <continent>NA</continent>
        <utc_offset>6</utc_offset>
        <picture>http://www.hamqth.com/images/default/ts-930.jpg</picture>
    </search>
</HamQTH>


Re: [winfldigi] Fldigi ver 4.1.00 Not Loading Fields from QRZ

Marvin Penepent
 

I get the same thing.


Marvin
KF5MLP

------ Original Message ------
From: "Dave" <w1hkj@...>
To: "Fred Lloyd, AA7BQ" <flloyd@...>
Sent: 2/1/2019 4:09:32 PM
Subject: Re: [nbems] [winfldigi] Fldigi ver 4.1.00 Not Loading Fields from QRZ

I have been receiving QRZ query issues when made from fldigi.  My W1HKJ QRZ account is current:



I tested the following versions with identical unsuccessful query requests to QRZ.com

  • 4.1.00  (released Jan 31 2019)
  • 4.0.18
  • 4.0.17
  • 4.0.16
  • 4.0.14
  • ...
  • 3.23.14 (released Jan 29 2017)
The 3.23.14 test was to insure that no change in the fldigi socket interface code caused the problem.  The most recent version of fldigi supports both IPV4 and IPV6 network protocol.

Did you change the server protocol?  Please advise.  I have filed a service request on the QRZ.com website.

Thank you.

73, David, W1HKJ
fldigi principal developer

The socket data stream i/o is basically the same for all versions

QRZ.COM socket stream:

Q: main: fldigi 4.1.00 log started on Fri Feb  1 15:38:47 2019

D: [15:39:28] misc/threads.cxx:101: fldigi thread 2 is LWP 4576
I: [15:39:28] logbook/lookupcall.cxx:1142: Request sent to
qrz.com...
V: [15:39:28] logbook/lookupcall.cxx:127: QRZ session key query:
GET /bin/xml?username=w1hkj;password=########;version=fldigi/4.1.00 HTTP/1.0
Host: xml.qrz.com
Connection: close



V: [15:39:28] misc/network.cxx:51:
========================================================================
node: xml.qrz.com
service: http
========================================================================
D: [15:39:28] misc/socket.cxx:634:
Address    [107.21.98.143]:80
Family     AF_INET
Sock type  1
Protocol   6
I: [15:39:28] misc/socket.cxx:643: Trying [107.21.98.143]:80
I: [15:39:28] misc/socket.cxx:942:  Connected to sockfd 58: [107.21.98.143]:80
V: [15:39:28] misc/network.cxx:72:
=============================== SENT ===================================
GET /bin/xml?username=w1hkj;password=perri06;version=fldigi/4.1.00 HTTP/1.0
Host: xml.qrz.com
Connection: close


========================================================================
V: [15:39:29] misc/network.cxx:82:
============================== REPLY ===================================
HTTP/1.1 400 Bad Request
Date: Fri, 01 Feb 2019 21:39:29 GMT
Server: Apache/2.4.29 (Ubuntu)
Content-Length: 318
Connection: close
Content-Type: text/html; charset=iso-8859-1



The same type of request made to HamQTH.com (European provider) with an IPV6 capable server works every time and is very fast.

www.hamqth.com socket stream:

Q: main: fldigi 4.1.00 log started on Fri Feb  1 16:02:06 2019

D: [16:02:38] misc/threads.cxx:101: fldigi thread 2 is LWP 5400
I: [16:02:38] logbook/lookupcall.cxx:1164: Request sent to https://www.hamqth.com/
V: [16:02:38] misc/network.cxx:51:
========================================================================
node: www.hamqth.com
service: http
========================================================================
D: [16:02:38] misc/socket.cxx:634:
Address    [2001:41d0:2:7d6b::]:80
Family     AF_INET6
Sock type  1
Protocol   6
D: [16:02:38] misc/socket.cxx:634:
Address    [94.23.250.107]:80
Family     AF_INET
Sock type  1
Protocol   6
I: [16:02:38] misc/socket.cxx:643: Trying [94.23.250.107]:80
I: [16:02:38] misc/socket.cxx:942:  Connected to sockfd 58: [94.23.250.107]:80
V: [16:02:38] misc/network.cxx:72:
=============================== SENT ===================================
GET /xml.php?u=w1hkj&p=###### HTTP/1.0
Host: www.hamqth.com
Connection: close
 

========================================================================
V: [16:02:38] misc/network.cxx:82:
============================== REPLY ===================================
HTTP/1.1 200 OK
Date: Fri, 01 Feb 2019 22:02:38 GMT
Server: Apache/2.4.18 (Ubuntu)
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: nette-browser=6zkk4yu2em; path=/; domain=.hamqth.com; httponly
Set-Cookie: PHPSESSID=v1ke0svh66roitjvbqgegg7297; expires=Sun, 03-Mar-2019 22:02:38 GMT; Max-Age=2592000; path=/; domain=.hamqth.com; HttpOnly
Set-Cookie: hamqthlang=en; expires=Sun, 12-May-2019 22:02:38 GMT; Max-Age=8640000
Vary: Accept-Encoding
Content-Length: 187
Connection: close
Content-Type: application/xml
 
<?xml version="1.0"?>
<HamQTH version="2.8" xmlns="http://www.hamqth.com">
    <session>
        <session_id>12c4c637b51f45aabdd775f573af7af57ebdffa7</session_id>
    </session>
</HamQTH>
========================================================================
I: [16:02:38] misc/socket.cxx:655: sockfd 58
V: [16:02:38] logbook/lookupcall.cxx:131: HamQTH session id data:
12c4c637b51f45aabdd775f573af7af57ebdffa7

V: [16:02:38] logbook/lookupcall.cxx:127: HamQTH query:
http://www.hamqth.com/xml.php?id=12c4c637b51f45aabdd775f573af7af57ebdffa7&callsign=w1hkj&prg=FLDIGI

V: [16:02:38] misc/network.cxx:51:
========================================================================
node: www.hamqth.com
service: http
========================================================================
D: [16:02:39] misc/socket.cxx:634:
Address    [2001:41d0:2:7d6b::]:80
Family     AF_INET6
Sock type  1
Protocol   6
D: [16:02:39] misc/socket.cxx:634:
Address    [94.23.250.107]:80
Family     AF_INET
Sock type  1
Protocol   6
I: [16:02:39] misc/socket.cxx:643: Trying [94.23.250.107]:80
I: [16:02:39] misc/socket.cxx:942:  Connected to sockfd 58: [94.23.250.107]:80
V: [16:02:39] misc/network.cxx:72:
=============================== SENT ===================================
GET /xml.php?id=12c4c637b51f45aabdd775f573af7af57ebdffa7&callsign=w1hkj&prg=FLDIGI HTTP/1.0
Host: www.hamqth.com
Connection: close
 

========================================================================
V: [16:02:39] misc/network.cxx:82:
============================== REPLY ===================================
HTTP/1.1 200 OK
Date: Fri, 01 Feb 2019 22:02:39 GMT
Server: Apache/2.4.18 (Ubuntu)
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: nette-browser=j6p9nv6ggx; path=/; domain=.hamqth.com; httponly
Set-Cookie: PHPSESSID=cr4aqfl0udnnu56vhih9elclf7; expires=Sun, 03-Mar-2019 22:02:39 GMT; Max-Age=2592000; path=/; domain=.hamqth.com; HttpOnly
Set-Cookie: hamqthlang=en; expires=Sun, 12-May-2019 22:02:39 GMT; Max-Age=8640000
Vary: Accept-Encoding
Content-Length: 1081
Connection: close
Content-Type: application/xml
 
<?xml version="1.0"?>
<HamQTH version="2.8" xmlns="http://www.hamqth.com">
    <search>
        <callsign>w1hkj</callsign>
        <nick>David</nick>
        <qth>Toney</qth>
        <country>United States</country>
        <adif>291</adif>
        <itu>8</itu>
        <cq>4</cq>
        <grid>EM64</grid>
        <adr_name>David H Freese</adr_name>
        <adr_street1>106 Whitfield Drive</adr_street1>
        <adr_city>Toney</adr_city>
        <adr_zip>35773</adr_zip>
        <adr_country>United States</adr_country>
        <adr_adif>291</adr_adif>
        <us_state>AL</us_state>
        <us_county>Madison</us_county>
        <lotw>Y</lotw>
        <qsldirect>?</qsldirect>
        <qsl>Y</qsl>
        <eqsl>Y</eqsl>
        <email>w1hkj@...</email>
        <birth_year>1938</birth_year>
        <lic_year>1957</lic_year>
        <latitude>34.9</latitude>
        <longitude>-86.72</longitude>
        <continent>NA</continent>
        <utc_offset>6</utc_offset>
        <picture>http://www.hamqth.com/images/default/ts-930.jpg</picture>
    </search>
</HamQTH>
========================================================================
I: [16:02:39] misc/socket.cxx:655: sockfd 58
V: [16:02:39] logbook/lookupcall.cxx:131: HamQth html data:
HTTP/1.1 200 OK
Date: Fri, 01 Feb 2019 22:02:39 GMT
Server: Apache/2.4.18 (Ubuntu)
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: nette-browser=j6p9nv6ggx; path=/; domain=.hamqth.com; httponly
Set-Cookie: PHPSESSID=cr4aqfl0udnnu56vhih9elclf7; expires=Sun, 03-Mar-2019 22:02:39 GMT; Max-Age=2592000; path=/; domain=.hamqth.com; HttpOnly
Set-Cookie: hamqthlang=en; expires=Sun, 12-May-2019 22:02:39 GMT; Max-Age=8640000
Vary: Accept-Encoding
Content-Length: 1081
Connection: close
Content-Type: application/xml
 
<?xml version="1.0"?>
<HamQTH version="2.8" xmlns="http://www.hamqth.com">
    <search>
        <callsign>w1hkj</callsign>
        <nick>David</nick>
        <qth>Toney</qth>
        <country>United States</country>
        <adif>291</adif>
        <itu>8</itu>
        <cq>4</cq>
        <grid>EM64</grid>
        <adr_name>David H Freese</adr_name>
        <adr_street1>106 Whitfield Drive</adr_street1>
        <adr_city>Toney</adr_city>
        <adr_zip>35773</adr_zip>
        <adr_country>United States</adr_country>
        <adr_adif>291</adr_adif>
        <us_state>AL</us_state>
        <us_county>Madison</us_county>
        <lotw>Y</lotw>
        <qsldirect>?</qsldirect>
        <qsl>Y</qsl>
        <eqsl>Y</eqsl>
        <email>w1hkj@...</email>
        <birth_year>1938</birth_year>
        <lic_year>1957</lic_year>
        <latitude>34.9</latitude>
        <longitude>-86.72</longitude>
        <continent>NA</continent>
        <utc_offset>6</utc_offset>
        <picture>http://www.hamqth.com/images/default/ts-930.jpg</picture>
    </search>
</HamQTH>


Re: [winfldigi] Fldigi ver 4.1.00 Not Loading Fields from QRZ

Dave
 

The support team sent the following message:

I'm sorry for the trouble.  We're still working out some kinks with the new server.  Everything should be back to normal shortly.  You might see some unusual stuff in the meantime.  Thanks for your patience.

73, The QRZ Support Team

Re: fldigi 4.1.00 release

Randy
 

Greetings,
 
I have 2 things to note on the new release of fldigi.
 
The counties in South Dakota do not sort alphabetically in the drop down box. 
 
Configure/UI/Operator includes input for a station callsign and an operator callsign.  Both can go to the log and export from the log and Station callsign transfers to MYCALL in a macro but operator callsign is not available for inclusion in a macro.
 
Randy

KJ0RE

http://mit.midco.net/rpratt

 

-----Original Message-----
From: nbems@groups.io [mailto:nbems@groups.io] On Behalf Of Dave
Sent: Tuesday, January 29, 2019 8:20 AM
To: linuxham@groups.io
Subject: [nbems] fldigi 4.1.00 release

Pushed to Source Forge Project, and GitHub.

Posted at Source Forge download page.
Posted at www.w1hkj.com
Source archive for building on local disk: fldigi-4.1.00.tar.gz
Apple 32 bit disk image for OS-X < 10.14:  fldigi-4.1.00_i386.dmg
Apple 64 bit disk image for OS-X >= 10.13: fldigi-4.1.00_x86_64q.dmg
Apple 64 bit disk image for Motorola CPU:  fldigi-4.1.00_ppc.dmg
Windows set up executable for all Win Ver: fldigi-4.1.00_setup.exe

SHA256 checksum for Windows installation file:

f46763a480f7b2e02356f467374915ab8223c5dd5d7f1af2a085e10166e37804  fldigi-4.1.00_setup.exe

Contains major changes to contest support (see below and on-line contest help).

73, David, W1HKJ

**** Version 4.1.0 Update release ****
  po update
      * update to el.po

  WWV doc
    * Update to WWV calibration procedure

  contest-docs

  arq-override
    * fix --arq-port override flag

  flmsg-dir
    * fix command line parser

  Winkeyer FSK
    * Add Winkeyer USB version 3 FSK module
    * test for WK version 31 or greater for WKFSK support

  Contests
    * Added support / N3FJP support for these contests
      - ARRL Field Day
      - ARRL Winter Field Day
      - ARRL Kids Day
      - ARRL Rookie Roundup
      - ARRL RTTY
      - ARRL School Club Roundup
      - ARRL Jamboree On The Air
      - CQ WPX
      - CQWW Rtty
      - Italian ARI International DX
      - North American QSO Party
      - North American Sprint
      - Sweepstakes
      - State QSO parties
      - Ten Ten
      - Africa International DX
      - VHF
      - Worked All Europe
      - State QSO Parties
    * replace with globally defined uppercase in strutil
    * Change all occurrences of FDCLASS to CLASS
      - allow CLASS to be used generically
    * Change all occurrences of FDSECTION to SECTION
      - allow SECTION to be u sed generically
    * fixed the missing gARRL_RTTY group hide by default
    * contest field validity checks
    * select contest type based on N3FJP logger initialization
    * add user help notes for all contests.
    * Maintain cursor position during edit of log widgets
    * allow user to grab 1, 2, 3, or 4 words by clicking
      on first word
      - left click : 1 word
      - shift-left click : 2 words
      - ctl-left click : 3 words
      - shift-cltl-left click : 4 words
    * add __APPLE__ pragma to avoid change in Fltk 1.3->1.4
      support of Fl_Surface_Device
    * Change surrounding widget from Fl_Pack to Fl_Group
      - Fl_Pack positioning algorithm not working as expected
    * LotW Modes
      - Add LotW export names for all modes
      - Increased max MODE string to 20.
    * Kid's Day
      - separate State / Province capture-entries
    * fix compile warnings
    * use single instance of cboCountyfor all full view logging
    * change all county names with MS$ extended character set
      long hypen with normal hyphen
    * add state field to hawaii
    * IARI contest uses separate fields for fldigi entry
      transfered to spcnum (single field) for n3fjp logger
    * County lists for SQSO, NEQP and 7QP are initialized from
      internal strings.  Written to files:
      - fldigi.files/data/SQSO.txt
      - fldigi.files/data/NEQP.txt
      - fldigi.files/data/7QP.txt
      upon exiting fldigi.
      Subsequent fldigi execution reads data from files.
      Files may be edited by user.  File format compatible with
      ASCII text editor, or spreadsheet program.  Must be saved
      as plain text from editor, or as comma separated value from
      spreadsheet program.
    * text capture remove all leading sub strings such as
      - loc:
      - op:
      - nam:
      - qth:

  fldigi_def.xml
    * removed "-->" from GPIO description string
      - caused xml parse error by mismatching closing element in <!- --> comment pairs

  socket_mods

  wefax
    * disable wefax thread when modem not in use !

  nanoIO
    * fix for TTY interface
    * fix for initialization

  CW SOM table
    * error in entry for 'J'

  flrig: macro
    * correct send string

  Audio adjust docs
    * Change description of setting audio input levels

  Version check
    * Change version check
      - test each string element individually

  Fltk 1.4 mod
    * Change to waterfall widget to accommodate changes in fltk 1.4.x.
      - driven by changes to OS X 10.14 and Xcode-10 changes
    * change to recognize 1.4.x library

  feldhell
    * C11 compile warning corrections
    * Additional wave shaping for FeldHell
      - 4 msec
      - 2 msec
      - 1 msec
      - no wave shaping

  C-11 fixes
    * fix warnings issued by C-11 compiler

  nano FSK
    * change TTY test for nanoIO on line and set to FSK mode

  Mint-19/Mate
    * fix to missing check box image on gtk+ scheme

  Signal Browser documentation
    * Squelch control
    * Which modems support multi-channel detection

  flrig seg fault
    * fix flrig shutdown seg fault
      - call to GUI update not constrained by Fl::awake(...) usage

Re: fldigi 4.1.00 release

Dave
 

Edit the new file named .../data/SQSO.txt

Sort the SD entries to your hearts content.  They will then appear in sorted order the next time you execute fldigi.

Dave

On 2/2/19 8:03 PM, Randy wrote:
Greetings,
 
I have 2 things to note on the new release of fldigi.
 
The counties in South Dakota do not sort alphabetically in the drop down box. 
 
Configure/UI/Operator includes input for a station callsign and an operator callsign.  Both can go to the log and export from the log and Station callsign transfers to MYCALL in a macro but operator callsign is not available for inclusion in a macro.
 
Randy
-----Original Message-----
From: nbems@groups.io [mailto:nbems@groups.io] On Behalf Of Dave
Sent: Tuesday, January 29, 2019 8:20 AM
To: linuxham@groups.io
Subject: [nbems] fldigi 4.1.00 release

Pushed to Source Forge Project, and GitHub.

Posted at Source Forge download page.
Posted at www.w1hkj.com
Source archive for building on local disk: fldigi-4.1.00.tar.gz
Apple 32 bit disk image for OS-X < 10.14:  fldigi-4.1.00_i386.dmg
Apple 64 bit disk image for OS-X >= 10.13: fldigi-4.1.00_x86_64q.dmg
Apple 64 bit disk image for Motorola CPU:  fldigi-4.1.00_ppc.dmg
Windows set up executable for all Win Ver: fldigi-4.1.00_setup.exe

SHA256 checksum for Windows installation file:

f46763a480f7b2e02356f467374915ab8223c5dd5d7f1af2a085e10166e37804  fldigi-4.1.00_setup.exe

Contains major changes to contest support (see below and on-line contest help).

73, David, W1HKJ

**** Version 4.1.0 Update release ****
  po update
      * update to el.po

  WWV doc
    * Update to WWV calibration procedure

  contest-docs

  arq-override
    * fix --arq-port override flag

  flmsg-dir
    * fix command line parser

  Winkeyer FSK
    * Add Winkeyer USB version 3 FSK module
    * test for WK version 31 or greater for WKFSK support

  Contests
    * Added support / N3FJP support for these contests
      - ARRL Field Day
      - ARRL Winter Field Day
      - ARRL Kids Day
      - ARRL Rookie Roundup
      - ARRL RTTY
      - ARRL School Club Roundup
      - ARRL Jamboree On The Air
      - CQ WPX
      - CQWW Rtty
      - Italian ARI International DX
      - North American QSO Party
      - North American Sprint
      - Sweepstakes
      - State QSO parties
      - Ten Ten
      - Africa International DX
      - VHF
      - Worked All Europe
      - State QSO Parties
    * replace with globally defined uppercase in strutil
    * Change all occurrences of FDCLASS to CLASS
      - allow CLASS to be used generically
    * Change all occurrences of FDSECTION to SECTION
      - allow SECTION to be u sed generically
    * fixed the missing gARRL_RTTY group hide by default
    * contest field validity checks
    * select contest type based on N3FJP logger initialization
    * add user help notes for all contests.
    * Maintain cursor position during edit of log widgets
    * allow user to grab 1, 2, 3, or 4 words by clicking
      on first word
      - left click : 1 word
      - shift-left click : 2 words
      - ctl-left click : 3 words
      - shift-cltl-left click : 4 words
    * add __APPLE__ pragma to avoid change in Fltk 1.3->1.4
      support of Fl_Surface_Device
    * Change surrounding widget from Fl_Pack to Fl_Group
      - Fl_Pack positioning algorithm not working as expected
    * LotW Modes
      - Add LotW export names for all modes
      - Increased max MODE string to 20.
    * Kid's Day
      - separate State / Province capture-entries
    * fix compile warnings
    * use single instance of cboCountyfor all full view logging
    * change all county names with MS$ extended character set
      long hypen with normal hyphen
    * add state field to hawaii
    * IARI contest uses separate fields for fldigi entry
      transfered to spcnum (single field) for n3fjp logger
    * County lists for SQSO, NEQP and 7QP are initialized from
      internal strings.  Written to files:
      - fldigi.files/data/SQSO.txt
      - fldigi.files/data/NEQP.txt
      - fldigi.files/data/7QP.txt
      upon exiting fldigi.
      Subsequent fldigi execution reads data from files.
      Files may be edited by user.  File format compatible with
      ASCII text editor, or spreadsheet program.  Must be saved
      as plain text from editor, or as comma separated value from
      spreadsheet program.
    * text capture remove all leading sub strings such as
      - loc:
      - op:
      - nam:
      - qth:

  fldigi_def.xml
    * removed "-->" from GPIO description string
      - caused xml parse error by mismatching closing element in <!- --> comment pairs

  socket_mods

  wefax
    * disable wefax thread when modem not in use !

  nanoIO
    * fix for TTY interface
    * fix for initialization

  CW SOM table
    * error in entry for 'J'

  flrig: macro
    * correct send string

  Audio adjust docs
    * Change description of setting audio input levels

  Version check
    * Change version check
      - test each string element individually

  Fltk 1.4 mod
    * Change to waterfall widget to accommodate changes in fltk 1.4.x.
      - driven by changes to OS X 10.14 and Xcode-10 changes
    * change to recognize 1.4.x library

  feldhell
    * C11 compile warning corrections
    * Additional wave shaping for FeldHell
      - 4 msec
      - 2 msec
      - 1 msec
      - no wave shaping

  C-11 fixes
    * fix warnings issued by C-11 compiler

  nano FSK
    * change TTY test for nanoIO on line and set to FSK mode

  Mint-19/Mate
    * fix to missing check box image on gtk+ scheme

  Signal Browser documentation
    * Squelch control
    * Which modems support multi-channel detection

  flrig seg fault
    * fix flrig shutdown seg fault
      - call to GUI update not constrained by Fl::awake(...) usage


FLRig & SCU-17

Mark Dallner
 

Been working with the Raspberry Pi build and my SCU 17.

Left the Pi up and running for three days and sending out a short message MT-63 2000L. Then FLRig lost communications with the SCU-17. After rebooting a couple of times, I went into Config>Transceiver and discovered that SerPort was set at NONE. Reset to the serial port and initialized and all is well with the world.

My question is, what happened?

Mark
KD9EEE

FLRIG and TS-990

Nate Kirschman
 

I’m running into a problem with FLRIG v. 1.3.42 and the TS-990.  Previous versions (1.3.26, for example) of FLRIG worked with some difficulty with the TS-990, and continues to do so with the latest version of TS-990 firmware.  The current version of FLRIG doesn’t work at all except for the Tune button.  This problem first appeared with the previous version of the TS-990 firmware and persists with the current TS-990 firmware, just loaded yesterday.
 
I don’t even know where to start.  It doesn’t seem to recognize the virtual com port.  On my PC, the USB com port gets assigned to COM 3.  The native Kenwood ARCP-990 works OK, N3FJP logging software works OK, reads frequency, mode, etc.  But FLRIG notices COM 3 on application start-up, but gives a message: Transceiver not responding!  Check serial (COM) port connection  Open Menu Config/Setup/Transceiver.  Press ‘ser port’ button, reselect port Press ‘init button.
 
I go the Xcvr configuration screen and I see Rig TS-990, Ser Port Com3, and Baud 115200 and 2 StopBits.  PTT via CAT.  From the main screen there’s no interaction with the rig except the Tune button seems to work.  No frequency display, etc.  I push the Ser Port button, and try to select the COM 3.  There is no COM 3 on the list.  I hit the Init button.  I get Not Responding message again, and a bogus frequency display. 
 
I’ve copied, and pasted to this email, the trace log file below.
 
Any help is appreciated.
 
Nate Kirschman, WN3I, 717-434-5842
 
02:56:51.705 : W: init_port_combos: Found serial port COM1
 
02:56:51.705 : W: init_port_combos: Found serial port COM3
 
02:56:52.235 : E: OpenPort: Open Comm port //./COM3 ; hComm = 328
 
02:56:52.245 : E: SetCommunicationTimeouts:
Read Interval Timeout............... -1
Read Total Timeout Multiplier....... -1
Read Total Timeout Constant Timeout. -2
Write Total Timeout Constant........ 0
Write Total Timeout Multiplier...... 0
 
02:56:52.245 : D: startXcvrSerial:
Serial port:
    Port     : COM3
    Baud     : 9
    Stopbits : 2
    Retries  : 2
    Timeout  : 50
    Loop     : 200
    RTSCTS   : 0
    CATptt   : 1
    RTSptt   : 0
    DTRptt   : 0
    RTS+     : 0
    DTR+     : 0
 
 
02:56:52.245 : init_rig()
02:56:52.925 : E:21:56:52: read ex 00100 failed 150 ms
cmd EX00100;
ans
 
02:56:53.305 : E:21:56:53: Read menu 0607 failed 100 ms
cmd EX00607;
ans
 
02:56:53.675 : E:21:56:53: Read menu 0608 failed 100 ms
cmd EX00608;
ans
 
02:56:53.705 : I:21:56:53:  Main band
cmd CB0;
ans
 
02:56:53.715 : I:21:56:53: Rx A, Tx A
cmd MV00;
ans
 
02:56:54.375 : E:21:56:54: check failed 150 ms
cmd FA;
ans
 
03:00:21.359 : lock mutex_service_requests : movFreqA
03:00:21.359 : unlock mutex_service_requests : movFreqA
 
04:09:40.361 : W: init_port_combos: Found serial port COM1
 
04:09:41.567 : W: init_port_combos: Found serial port COM1
 
04:09:49.647 : closeRig()
04:09:49.677 : E: OpenPort: Open Comm port //./COM3 ; hComm = 328
 
04:09:49.685 : E: SetCommunicationTimeouts:
Read Interval Timeout............... -1
Read Total Timeout Multiplier....... -1
Read Total Timeout Constant Timeout. -2
Write Total Timeout Constant........ 0
Write Total Timeout Multiplier...... 0
 
04:09:49.686 : D: startXcvrSerial:
Serial port:
    Port     : COM3
    Baud     : 9
    Stopbits : 2
    Retries  : 2
    Timeout  : 50
    Loop     : 200
    RTSCTS   : 0
    CATptt   : 1
    RTSptt   : 0
    DTRptt   : 0
    RTS+     : 0
    DTR+     : 0
 
 
04:09:49.687 : init_rig()
04:09:50.350 : E:23:09:50: read ex 00100 failed 150 ms
cmd EX00100;
ans
 
04:09:50.717 : E:23:09:50: Read menu 0607 failed 100 ms
cmd EX00607;
ans
 
04:09:51.080 : E:23:09:51: Read menu 0608 failed 100 ms
cmd EX00608;
ans
 
04:09:51.096 : I:23:09:51:  Main band
cmd CB0;
ans
 
04:09:51.101 : I:23:09:51: Rx A, Tx A
cmd MV00;
ans
 
04:09:51.757 : E:23:09:51: check failed 150 ms
cmd FA;
ans
 
04:10:42.663 : closeRig()
04:10:42.671 : E: OpenPort: Open Comm port //./COM3 ; hComm = 328
 
04:10:42.679 : E: SetCommunicationTimeouts:
Read Interval Timeout............... -1
Read Total Timeout Multiplier....... -1
Read Total Timeout Constant Timeout. -2
Write Total Timeout Constant........ 0
Write Total Timeout Multiplier...... 0
 
04:10:42.680 : D: startXcvrSerial:
Serial port:
    Port     : COM3
    Baud     : 9
    Stopbits : 2
    Retries  : 2
    Timeout  : 50
    Loop     : 200
    RTSCTS   : 0
    CATptt   : 1
    RTSptt   : 0
    DTRptt   : 0
    RTS+     : 0
    DTR+     : 0
 
 
04:10:42.681 : init_rig()
04:10:43.344 : E:23:10:43: read ex 00100 failed 150 ms
cmd EX00100;
ans
 
04:10:43.710 : E:23:10:43: Read menu 0607 failed 100 ms
cmd EX00607;
ans
 
04:10:44.071 : E:23:10:44: Read menu 0608 failed 100 ms
cmd EX00608;
ans
 
04:10:44.086 : I:23:10:44:  Main band
cmd CB0;
ans
 
04:10:44.091 : I:23:10:44: Rx A, Tx A
cmd MV00;
ans
 
04:10:44.747 : E:23:10:44: check failed 150 ms
cmd FA;
ans
 

WX macro doesn't work

Dave
 

NOAA has changed it's METAR data service to use https vice http. The change breaks the <WX:...> macro implementation.  fldigi network access code will need changes to implement the secure access negotiation with the NOAA site.

73, David, W1HKJ

Re: WX macro doesn't work

Rick Stanback
 

It looks like they have redirect loop. HTTP redirects to HTTPS and
HTTPS redirects to HTTP?

On Wed, 2019-02-06 at 11:08 -0600, Dave wrote:
NOAA has changed it's METAR data service to use https vice http. The
change breaks the <WX:...> macro implementation. fldigi network
access
code will need changes to implement the secure access negotiation
with
the NOAA site.

73, David, W1HKJ


FLDIGI Disappears About 2 Seconds After Startup

k8grr@...
 

I am working on configuring a new installation of FLDIGI and FLRIG on a Windows 10 PC. I am not sure what I did, but now when I open FLDIGI, the UI disappears after about 2 seconds. This happens even after I uninstalled and reinstalled it FLDIGI (v.4.1.00).

Any suggestions would be appreciated.

Brian, K8GRR

Re: FLDIGI Disappears About 2 Seconds After Startup\

Larry Levesque
 

Two suggestions.

1. Start fldigi from the command line and let us know the results

2 Rename the fldigi.files directory to anything else and start it from the command line

On Wed, Feb 06, 2019 at 10:58:07AM -0800, k8grr@... wrote:
I am working on configuring a new installation of FLDIGI and FLRIG on a Windows 10 PC. I am not sure what I did, but now when I open FLDIGI, the UI disappears after about 2 seconds. This happens even after I uninstalled and reinstalled it FLDIGI (v.4.1.00).

Any suggestions would be appreciated.

Brian, K8GRR


--
Larry Levesque
KA1VGM

Re: FLDIGI Disappears About 2 Seconds After Startup

Oliver K6OLI
 

Brian,
Is your Antivirus quarantining/blocking Fldigi? Check in the AV quarantine, if Fldigi is in there, restore it and create an exception.
73,
Oliver K6oLI

Re: FLDIGI Disappears About 2 Seconds After Startup

Rick Smith
 

This problem occured when I loaded FLdigi 4.0.18 on a new desktop system. After reading the feedback from users it 
appeared the program was not seeing a Speaker/Microphone resource. 
I added a set of speakers and a microphone and restarted FLdigi. Problem solved. 
To confirm, I removed the external Mic & Spkrs..The problem returned.

Rick  k0kex


From: nbems@groups.io <nbems@groups.io> on behalf of k8grr@... <k8grr@...>
Sent: Wednesday, February 6, 2019 12:58 PM
To: nbems@groups.io
Subject: [nbems] FLDIGI Disappears About 2 Seconds After Startup
 
I am working on configuring a new installation of FLDIGI and FLRIG on a Windows 10 PC. I am not sure what I did, but now when I open FLDIGI, the UI disappears after about 2 seconds. This happens even after I uninstalled and reinstalled it FLDIGI (v.4.1.00).

Any suggestions would be appreciated.

Brian, K8GRR

Shortwave Radiogram, 8-10 February 2019

kd9xb
 

Shortwave Radiogram this weekend is in MFSK32 and MFSK64, and a brief  segment in Olivia 64-2000.  If your signal is so bad that you can't hear anything, try the Olivia 64-2000 anyway, at seven minutes into the show, and you might see text printing out.

For details:
http://swradiogram.net/post/182655071787/shortwave-radiogram-8-10-february-2019-digital

Separate from this weekend's normal broadcast, today (Friday) at 1500-1530 UTC there will be special content, including some super-fast modes on WINB's DRM transmitter, 13690 kHz. This will not be the DRM proprietary text mode (I don't have access to a DRM content server), but digital text modes and images decoded from the audio decoded from WINB's DRM signal. This is a convoluted way to receive text and images, but fun when it works. Details via the URL above.

Kim
KD9XB

Roger in Germany provides these images and "sonogram" of last week's show. The horizontal axis is time (the half hour of the broadcast), and the vertical axis is the spectrum, with the 7780 kHz carrier at the center  ...

flrig / Kenwood TS-890s

Dave
 

Added TS-890S class.

Disabled prefs file update if flrig loses serial connection to flrig during program exit.

Please let me know if anyone needs an OS-X dmg.

73, David, W1HKJ


fldigi 4.1.0 - LOTW no upload

Dave
 

view all files @ http://www.w1hkj.com/alpha/fldigi/

Corrects LOTW upload bug.  Tested on OS-X with successful LOTW upload.

73, David, W1HKJ

fldigi 4.1.01.04 alpha posted

Dave
 

To http://www.w1hkj.com/alpha/fldigi/
Alpha 4.1.01.04

  WF only bug fix
    * N1MM waterfall only requirement strikes again :>(

  LotW
    * Adif export missing <MODE:n> <SUBMODE:n>

  Pedantic warnings
    * correct additional gcc warnings

  ADIF submode
    * Add submode support
      - export both MODE and SUBMODE to external loggers iaw ADIF spec 3.04

  QRZ.com
    * change interface to QRZ XML service version 1.33

  SV1GRB test report
    * Corrections based on Haris' testing of 4.1.00
      -  Add "NONE" or "N/A" to State and County pick lists, operator configuration

  SD counties
    * sort South Dakota counties alphabetically

Please be patient.  The transition from 4.0.18 to 4.1.0 was not a trivial change in code or 
functionality.  I am working on the loss of METAR access (weather services).

73, David, W1HKJ