hamlib-developer Mailing List for Ham Radio Control Libraries

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 8645a5a95e41dddeeefbf669d1009bbe105bb336
      https://github.com/Hamlib/Hamlib/commit/8645a5a95e41dddeeefbf669d1009bbe105bb336
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-09-03 (Wed, 03 Sep 2025)

  Changed paths:
    M README.coding_style

  Log Message:
  -----------
  Add suggestions regarding Markdown



To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 9bad1d6eb20b91c16d9d88f37a65bae7fd3ddd48
      https://github.com/Hamlib/Hamlib/commit/9bad1d6eb20b91c16d9d88f37a65bae7fd3ddd48
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-09-02 (Tue, 02 Sep 2025)

  Changed paths:
    A ReleaseNotes_4.7.md
    A ReleaseNotes_5.0.md

  Log Message:
  -----------
  Baseline for Release Notes


  Commit: fa7ca3415ded790764b4434dcf6d315b089eb19b
      https://github.com/Hamlib/Hamlib/commit/fa7ca3415ded790764b4434dcf6d315b089eb19b
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-09-02 (Tue, 02 Sep 2025)

  Changed paths:
    M ReleaseNotes_4.7.md
    M ReleaseNotes_5.0.md

  Log Message:
  -----------
  More text for relnote


  Commit: dfad2a788ba2d3863ddbf8f3b3f3cac39ae8c8da
      https://github.com/Hamlib/Hamlib/commit/dfad2a788ba2d3863ddbf8f3b3f3cac39ae8c8da
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-09-02 (Tue, 02 Sep 2025)

  Changed paths:
    M ReleaseNotes_4.7.md
    M ReleaseNotes_5.0.md

  Log Message:
  -----------
  More things filled in

Add links to issues(with URLs)
Add table of structures/include files/macros


  Commit: 50852d43b91dd4762d143c02fdec10389ab2b3b9
      https://github.com/Hamlib/Hamlib/commit/50852d43b91dd4762d143c02fdec10389ab2b3b9
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-09-02 (Tue, 02 Sep 2025)

  Changed paths:
    M ReleaseNotes_4.7.md
    M ReleaseNotes_5.0.md

  Log Message:
  -----------
  Add deprecation/change info


  Commit: 7f8ac191e98eb00ce80318777573d632e40a38f1
      https://github.com/Hamlib/Hamlib/commit/7f8ac191e98eb00ce80318777573d632e40a38f1
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-09-02 (Tue, 02 Sep 2025)

  Changed paths:
    M ReleaseNotes_4.7.md
    M ReleaseNotes_5.0.md

  Log Message:
  -----------
  Bring some things up to date.

Still nowhere close to done.


  Commit: 688b9dba9a51b143b75a33b204932d37cb3b99e6
      https://github.com/Hamlib/Hamlib/commit/688b9dba9a51b143b75a33b204932d37cb3b99e6
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-09-02 (Tue, 02 Sep 2025)

  Changed paths:
    M ReleaseNotes_4.7.md

  Log Message:
  -----------
  Ask for testing of FTX-1


  Commit: f42782c2eac82d326783e5138a9bed860e9f83eb
      https://github.com/Hamlib/Hamlib/commit/f42782c2eac82d326783e5138a9bed860e9f83eb
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-09-03 (Wed, 03 Sep 2025)

  Changed paths:
    M ReleaseNotes_4.7.md

  Log Message:
  -----------
  Fix typo


Compare: https://github.com/Hamlib/Hamlib/compare/f15537f2e690...f42782c2eac8

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

I don't know of any specific plans for the IC-7760. What problems are 
you having, and what version of Hamlib are you using? The current 
release is 4.6.4

73

n3gb

On 9/3/25 11:14 AM, DG7FBB / Pete wrote:
>
> Hi All,
>
> since a few days I am  trying to set my new *IC 7760 for FT8*, which 
> is more difficult than I thought.
>
> Are there any plans to issue the appropriate hamlib file for this 
> gear? And when can it be expected?
>
> /73 / Peter / DG7FBB/
>
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Hi All, 

since a few days I am  trying to set my new IC 7760 for FT8, which is more difficult than I thought. 
Are there any plans to issue the appropriate hamlib file for this gear? And when can it be expected?

73 / Peter / DG7FBB

On 9/2/25 5:11 PM, Daniele Forsi wrote:
> George Baltz:
>
>> Guess I should have looked at the details, not just the description...
> always, especially if there is a bunch of files
>
>> This removes a large part of the prep work already done for the
>> refactoring of include files in 5.0.
> What the reason of unconditionally including files that aren't used?
> How that can be tested?
>
> The fileds modified in src/ are 2 *.h and 23 *.c
>
> Of course these commits can be easily reverted, but you aren't clearly
> talking about errno.h or stdio.h and the like.
>
> Which of the following unused includes should be added back? The
> number is the quantity of lines removed.
>
>       1 -#include "config.h"
>       2 -#include <errno.h>
>       2 -#include <fcntl.h>
>       1 -#include "hamlib/amplifier.h"
>      13 -#include "hamlib/port.h"
The port,h files are conditionally included in rig.h (now). They won't 
be in 5.0.  The entire code base needs to be updated before the includes 
can be tested.
>       3 -#include "hamlib/rig.h"
>       1 -#include "hamlib/rotator.h"
>       3 -#include "iofunc.h"
>       1 -#include "misc.h"
>       1 -#include "rot_conf.h"
>       1 -#include <stdio.h>
>       3 -#include <stdlib.h>
>       8 -#include <string.h>
>       3 -#  include <sys/param.h>
>       4 -#include <sys/stat.h>
>       3 -#include "token.h"
>       8 -#include <unistd.h>
>       1 -#include <unistd.h>  /* UNIX standard function definitions */
>

George Baltz:

> Guess I should have looked at the details, not just the description...

always, especially if there is a bunch of files

> This removes a large part of the prep work already done for the
> refactoring of include files in 5.0.

What the reason of unconditionally including files that aren't used?
How that can be tested?

The fileds modified in src/ are 2 *.h and 23 *.c

Of course these commits can be easily reverted, but you aren't clearly
talking about errno.h or stdio.h and the like.

Which of the following unused includes should be added back? The
number is the quantity of lines removed.

     1 -#include "config.h"
     2 -#include <errno.h>
     2 -#include <fcntl.h>
     1 -#include "hamlib/amplifier.h"
    13 -#include "hamlib/port.h"
     3 -#include "hamlib/rig.h"
     1 -#include "hamlib/rotator.h"
     3 -#include "iofunc.h"
     1 -#include "misc.h"
     1 -#include "rot_conf.h"
     1 -#include <stdio.h>
     3 -#include <stdlib.h>
     8 -#include <string.h>
     3 -#  include <sys/param.h>
     4 -#include <sys/stat.h>
     3 -#include "token.h"
     8 -#include <unistd.h>
     1 -#include <unistd.h>  /* UNIX standard function definitions */

-- 
73 de IU5HKX Daniele

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 632746cf91c50cdbefce5ba8fbe7e502feef9568
      https://github.com/Hamlib/Hamlib/commit/632746cf91c50cdbefce5ba8fbe7e502feef9568
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-08-30 (Sat, 30 Aug 2025)

  Changed paths:
    M tests/ampctl_parse.c
    M tests/rigctl_parse.c
    M tests/rotctl_parse.c

  Log Message:
  -----------
  Use rig_debug() instead of sending error messages to stdout


  Commit: e4c43821d0b1e53c1b8eebc0b5e9cd2091c9a1f0
      https://github.com/Hamlib/Hamlib/commit/e4c43821d0b1e53c1b8eebc0b5e9cd2091c9a1f0
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-09-02 (Tue, 02 Sep 2025)

  Changed paths:
    M tests/ampctl_parse.c
    M tests/rigctl_parse.c
    M tests/rotctl_parse.c

  Log Message:
  -----------
  Always print error messages to stderr

Do not depend on the debug level set with --verbose


  Commit: f15537f2e690bcf4a705a8976e4327738a18afde
      https://github.com/Hamlib/Hamlib/commit/f15537f2e690bcf4a705a8976e4327738a18afde
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-09-02 (Tue, 02 Sep 2025)

  Changed paths:
    M tests/ampctl_parse.c
    M tests/rigctl_parse.c
    M tests/rotctl_parse.c

  Log Message:
  -----------
  Merge GitHub PR #1875


Compare: https://github.com/Hamlib/Hamlib/compare/3582d8dee09e...f15537f2e690

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

* On 2025 02 Sep 10:05 -0500, Peter Marks wrote:
> rigerror(int errnum) is there but not rigerror2

I just uploaded the 4.7 WIP.  Text for rigerror2():

https://hamlib.sourceforge.net/manuals/4.7/group__rig.html#gadebf1a4529c22f83ccce81c162db91cd

I think this shows that such descriptions could be more verbose.  Oft
times those that know make assumptions that others know.  Such is not
limited to our API documentation either!  Sadly, there is no link to
"errnum" which implies that its definition is not yet documented.  This
is an opportunity for interested parties to get involved, get familiar
with the code base, and submit Pull Requests improving the documentation.

The main page of the current manual:

https://hamlib.sourceforge.net/manuals/4.7/

The final style will likely change as this was generated from the
Doxygen of Debian 12.  Doxygen has been updated for Debian 13 and if I
really want to go cutting edge I can generate it on Arch.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

* On 2025 02 Sep 09:55 -0500, George Baltz wrote:
> You should find it already is in the latest docs - as Nate said, you were
> looking at a very old version.

As I don't know off hand when rig_error2() entered, it's likely that the
4.3 documentation does not include it.

I can easily generate the Doxygen docs as they currently exist and
upload them.  They can be updated for the 4.7.0 release.  Doing so will
also show where updates are needed.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: d596581ecebc12da1c301542b570391a53fca2fa
      https://github.com/Hamlib/Hamlib/commit/d596581ecebc12da1c301542b570391a53fca2fa
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-09-01 (Mon, 01 Sep 2025)

  Changed paths:
    M Makefile.am
    A README.macos
    R README.osx
    M doc/index.doxygen

  Log Message:
  -----------
  Rename README.osx to README.macos

Conform the file name to current system marketing name.


  Commit: 2805dc5ed66412f80e008650169d5d78f2a94cb1
      https://github.com/Hamlib/Hamlib/commit/2805dc5ed66412f80e008650169d5d78f2a94cb1
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-09-01 (Mon, 01 Sep 2025)

  Changed paths:
    M README.betatester
    M README.developer
    M README.md

  Log Message:
  -----------
  Update READMEs

Update for current practices with tips.

Mention both GitHub and SourceForge as "forges".

Format paragraphs to a text width of 80 characters maximum.


  Commit: d76d563857dcc3702d308b70eeb86a9699a14786
      https://github.com/Hamlib/Hamlib/commit/d76d563857dcc3702d308b70eeb86a9699a14786
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-09-01 (Mon, 01 Sep 2025)

  Changed paths:
    M INSTALL

  Log Message:
  -----------
  Update INSTALL to align with current practice


  Commit: a78291ff944a3ae2a6023bd88a7d7ff78739df5d
      https://github.com/Hamlib/Hamlib/commit/a78291ff944a3ae2a6023bd88a7d7ff78739df5d
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-09-01 (Mon, 01 Sep 2025)

  Changed paths:
    M CONTRIBUTING.md

  Log Message:
  -----------
  Update CONTRIBUTING.md to be relevant to Hamlib


  Commit: 3582d8dee09e16c4afd43b6bb696cbfe34ee00a6
      https://github.com/Hamlib/Hamlib/commit/3582d8dee09e16c4afd43b6bb696cbfe34ee00a6
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-09-01 (Mon, 01 Sep 2025)

  Changed paths:
    R README.win32
    A README.windows

  Log Message:
  -----------
  Update information on Windows builds

Rename README.win32 to README.windows

Point to build scripts and mention new MinGW name and Web site.


Compare: https://github.com/Hamlib/Hamlib/compare/7180eb7da629...3582d8dee09e

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

And another one

On 8/31/25 8:20 PM, Nate Bargmann via Hamlib-developer wrote:
>    Branch: refs/heads/master
>    Home:   https://github.com/Hamlib/Hamlib
>    Commit: 39e155efe71f9f2a84f42b5f64f510135173aa85
>        https://github.com/Hamlib/Hamlib/commit/39e155efe71f9f2a84f42b5f64f510135173aa85
>    Author: Daniele Forsi IU5HKX <iu...@gm...>
>    Date:   2025-08-30 (Sat, 30 Aug 2025)
>
>    Changed paths:
>      M lib/precise_time.c
>      M rigs/anytone/anytone.c
>      M rigs/barrett/barrett.c
>      M rigs/dummy/dummy.c
>      M rigs/dummy/flrig.c
>      M rigs/dummy/netrigctl.c
>      M rigs/dummy/quisk.c
>      M rigs/dummy/tci1x.c
>      M rigs/dummy/trxmanager.c
>      M rigs/kit/usrp_impl.cc
>      M rigs/winradio/g313-posix.c
>      M rigs/winradio/linradio/wrg313api.c
>      M rotators/androidsensor/androidsensor.cpp
>      M rotators/grbltrk/grbltrk.c
>      M security/AESStringCrypt.c
>      M src/fifo.c
>      M src/parallel.h
>      M tests/rigtestlibusb.c
>      M tests/rigtestmcastrx.c
>      M tests/testnet.c
>
>    Log Message:
>    -----------
>    Fix include config.h
>
> It should be included, with its path, before any hamlib include
> and before any #ifdef that uses the symbols that it defines.

This is OK as far as it goes, but ignores a very important fact - 
config.h also contains definitions that may be used by any system 
include.  For simple cases (like Hamlib) the *_SOURCE macros are the 
important ones, but for more complex uses(e.g., cross-compilation) it 
can get quite hairy.

If `config.h` is included, it should be before ANY other include.

>
>    Commit: 43b84ee56a66c19844c5efcb63f1217f57fac4c2
>        https://github.com/Hamlib/Hamlib/commit/43b84ee56a66c19844c5efcb63f1217f57fac4c2
>    Author: Nate Bargmann <n0...@n0...>
>    Date:   2025-08-31 (Sun, 31 Aug 2025)
>
>    Changed paths:
>      M lib/precise_time.c
>      M rigs/anytone/anytone.c
>      M rigs/barrett/barrett.c
>      M rigs/dummy/dummy.c
>      M rigs/dummy/flrig.c
>      M rigs/dummy/netrigctl.c
>      M rigs/dummy/quisk.c
>      M rigs/dummy/tci1x.c
>      M rigs/dummy/trxmanager.c
>      M rigs/kit/usrp_impl.cc
>      M rigs/winradio/g313-posix.c
>      M rigs/winradio/linradio/wrg313api.c
>      M rotators/androidsensor/androidsensor.cpp
>      M rotators/grbltrk/grbltrk.c
>      M security/AESStringCrypt.c
>      M src/fifo.c
>      M src/parallel.h
>      M tests/rigtestlibusb.c
>      M tests/rigtestmcastrx.c
>      M tests/testnet.c
>
>    Log Message:
>    -----------
>    Merge GitHub PR #1873
>
>
> Compare: https://github.com/Hamlib/Hamlib/compare/d227444aa60a...43b84ee56a66
>
> To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Hmm.

I went to https://github.com/Hamlib/Hamlib
Clicked Wiki which took me to: https://github.com/Hamlib/Hamlib/wiki
Clicked Documentation which took me to: https://github.com/Hamlib/Hamlib/wiki/Documentation
Clicked HTML API Reference (v 4.3) which took me to: https://hamlib.sourceforge.net/manuals/4.3/index.html
Clicked Modules to https://hamlib.sourceforge.net/manuals/4.3/modules.html
Clicked "Rig (transceiver) API” to https://hamlib.sourceforge.net/manuals/4.3/group__rig.html
Clicked rig.c to https://hamlib.sourceforge.net/manuals/4.3/rig_8c.html

rigerror(int errnum) is there but not rigerror2

I’m obviously finding the wrong thing but it’s a bit of a puzzle.

Thanks for your help though. Can you give me the link to the documentation page with rigerror2()?

Peter

> On 2 Sep 2025, at 7:06 pm, George Baltz <geo...@gm...> wrote:
> 
> You should find it already is in the latest docs - as Nate said, you were looking at a very old version.
> 
> On 9/1/25 8:30 PM, Peter Marks wrote:
>> Thanks George. You are very kind.
>> 
>> For some reason it has taken me a while to figure out that the SourceForge project is no longer the active one.
>> 
>> I’ll raise a ticket asking that rigerror2 be added to the API reference
>> 
>> 73,
>> 
>> Peter
>> VK3TPM.
>> 
>>> On 2 Sep 2025, at 10:25 am, George Baltz <geo...@gm...> <mailto:geo...@gm...> wrote:
>>> 
>>> Forgot to answer your other comment - the ticketing system(and other admin stuff) was moved from sourceforge to github.com -
>>> 
>>> https://github.com/Hamlib/Hamlib
>>> 
>>> 73, n3gb
>>> 
>>> On 8/31/25 5:58 PM, Peter Marks wrote:
>>>> Dear Hamlib developers,
>>>> 
>>>> I don’t seem to be able to create a feature request ticket on sourceforge. The button is dim.
>>>> 
>>>> When hamlib reports an error, typically a timeout talking to the radio, the error string returned by rigerror() is very detailed and includes a stack trace.
>>>> 
>>>> const char* rigerror <https://hamlib.sourceforge.net/manuals/1.2.15/group__rig.html#ga675d0903517323b2689446d9513fc8db>	(	int 	errnum	)	
>>>> get string describing the error code
>>>> 
>>>> 
>>>> I’m involved in the FreeDV <https://freedv.org/> project which uses hamlib. We show the error string and find that it is intimidating to users. They sometimes report that FreeDV has “crashed”.
>>>> 
>>>> It would be great if there was a second version of the error string with just the bit that the user needs. “Timeout talking to rig” for example.
>>>> 
>>>> Many thanks for your great work.
>>>> 
>>>> Peter
>>>> VK3TPM
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Hamlib-developer mailing list
>>>> Ham...@li... <mailto:Ham...@li...>
>>>> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
>>> _______________________________________________
>>> Hamlib-developer mailing list
>>> Ham...@li... <mailto:Ham...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
>> 

You should find it already is in the latest docs - as Nate said, you 
were looking at a very old version.

On 9/1/25 8:30 PM, Peter Marks wrote:
> Thanks George. You are very kind.
>
> For some reason it has taken me a while to figure out that the 
> SourceForge project is no longer the active one.
>
> I’ll raise a ticket asking that rigerror2 be added to the API reference
>
> 73,
>
> Peter
> VK3TPM.
>
>> On 2 Sep 2025, at 10:25 am, George Baltz <geo...@gm...> wrote:
>>
>> Forgot to answer your other comment - the ticketing system(and other 
>> admin stuff) was moved from sourceforge to github.com -
>>
>> https://github.com/Hamlib/Hamlib
>>
>> 73, n3gb
>>
>> On 8/31/25 5:58 PM, Peter Marks wrote:
>>> Dear Hamlib developers,
>>>
>>> I don’t seem to be able to create a feature request ticket on 
>>> sourceforge. The button is dim.
>>>
>>> When hamlib reports an error, typically a timeout talking to the 
>>> radio, the error string returned by rigerror() is very detailed and 
>>> includes a stack trace.
>>>
>>> const char* rigerror 
>>> <https://hamlib.sourceforge.net/manuals/1.2.15/group__rig.html#ga675d0903517323b2689446d9513fc8db> 
>>> 	( 	int 	/errnum/ 	) 	
>>>
>>> get string describing the error code
>>>
>>>
>>> I’m involved in the FreeDV <https://freedv.org/> project which uses 
>>> hamlib. We show the error string and find that it is intimidating to 
>>> users. They sometimes report that FreeDV has “crashed”.
>>>
>>> It would be great if there was a second version of the error string 
>>> with just the bit that the user needs. “Timeout talking to rig” for 
>>> example.
>>>
>>> Many thanks for your great work.
>>>
>>> Peter
>>> VK3TPM
>>>
>>>
>>> _______________________________________________
>>> Hamlib-developer mailing list
>>> Ham...@li...
>>> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
>> _______________________________________________
>> Hamlib-developer mailing list
>> Ham...@li...
>> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
>

Guess I should have looked at the details, not just the description...

On 8/31/25 8:04 PM, dforsi via Hamlib-developer wrote:
>    Branch: refs/heads/master
>    Home:   https://github.com/Hamlib/Hamlib
>    Commit: 83ed5abeb44e21c1e13a7a57e0f02eb8a1dece6e
>        https://github.com/Hamlib/Hamlib/commit/83ed5abeb44e21c1e13a7a57e0f02eb8a1dece6e
>    Author: Daniele Forsi IU5HKX <iu...@gm...>
>    Date:   2025-08-30 (Sat, 30 Aug 2025)
>
>    Changed paths:
>      M src/amp_conf.c
>      M src/amp_reg.c
>      M src/amplifier.c
>      M src/cm108.c
>      M src/cm108.h
>      M src/conf.c
>      M src/extamp.c
>      M src/gpio.c
>      M src/iofunc.c
>      M src/mem.c
>      M src/network.c
>      M src/parallel.c
>      M src/register.c
>      M src/register.h
>      M src/rig.c
>      M src/rot_conf.c
>      M src/rot_reg.c
>      M src/rot_settings.c
>      M src/rotator.c
>      M src/serial.c
>      M src/settings.c
>      M src/snapshot_data.c
>      M src/sprintflst.c
>      M src/usb_port.c
>      M src/usb_port.h
>
>    Log Message:
>    -----------
>    [src] Remove unused includes
>
> Found by iwyu.

This removes a large part of the prep work already done for the 
refactoring of include files in 5.0.

Yes, there are some duplicate `#include`s, but one of those is 
conditional and will go away.

>
>    Commit: 47f60d4ad7e98fe9c4d2dfe46cd531f8ebf64fe3
>        https://github.com/Hamlib/Hamlib/commit/47f60d4ad7e98fe9c4d2dfe46cd531f8ebf64fe3
>    Author: Daniele Forsi IU5HKX <iu...@gm...>
>    Date:   2025-08-30 (Sat, 30 Aug 2025)
>
>    Changed paths:
>      M simulators/sim.h
>      M simulators/simeasycomm.c
>      M simulators/simelecraft.c
>      M simulators/simelecraftk4.c
>      M simulators/simft1000.c
>      M simulators/simft736.c
>      M simulators/simft747gx.c
>      M simulators/simft817.c
>      M simulators/simft847.c
>      M simulators/simft897.c
>      M simulators/simjupiter.c
>      M simulators/simrotorez.c
>      M simulators/simspid.c
>      M simulators/simtrusdx.c
>      M simulators/simts450.c
>      M simulators/simts890.c
>
>    Log Message:
>    -----------
>    [simulators] Remove unused includes
>
>      Found by iwyu.
>
>
>    Commit: d227444aa60ad7f35e204607d9506e1fab5b14bd
>        https://github.com/Hamlib/Hamlib/commit/d227444aa60ad7f35e204607d9506e1fab5b14bd
>    Author: Daniele Forsi IU5HKX <iu...@gm...>
>    Date:   2025-08-30 (Sat, 30 Aug 2025)
>
>    Changed paths:
>      M src/amp_reg.c
>      M src/rot_reg.c
>
>    Log Message:
>    -----------
>    Fix return values of amp_load_backend() and rot_load_backend()
>
> The value -EINVAL is in the domain of errno.
>
>
> Compare: https://github.com/Hamlib/Hamlib/compare/0a06af1ddef5...d227444aa60a
>
> To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Thanks George. You are very kind.

For some reason it has taken me a while to figure out that the SourceForge project is no longer the active one.

I’ll raise a ticket asking that rigerror2 be added to the API reference

73,

Peter
VK3TPM.

> On 2 Sep 2025, at 10:25 am, George Baltz <geo...@gm...> wrote:
> 
> Forgot to answer your other comment - the ticketing system(and other admin stuff) was moved from sourceforge to github.com -
> 
> https://github.com/Hamlib/Hamlib
> 
> 73, n3gb
> 
> On 8/31/25 5:58 PM, Peter Marks wrote:
>> Dear Hamlib developers,
>> 
>> I don’t seem to be able to create a feature request ticket on sourceforge. The button is dim.
>> 
>> When hamlib reports an error, typically a timeout talking to the radio, the error string returned by rigerror() is very detailed and includes a stack trace.
>> 
>> const char* rigerror <https://hamlib.sourceforge.net/manuals/1.2.15/group__rig.html#ga675d0903517323b2689446d9513fc8db>	(	int 	errnum	)	
>> get string describing the error code
>> 
>> 
>> I’m involved in the FreeDV <https://freedv.org/> project which uses hamlib. We show the error string and find that it is intimidating to users. They sometimes report that FreeDV has “crashed”.
>> 
>> It would be great if there was a second version of the error string with just the bit that the user needs. “Timeout talking to rig” for example.
>> 
>> Many thanks for your great work.
>> 
>> Peter
>> VK3TPM
>> 
>> 
>> 
>> _______________________________________________
>> Hamlib-developer mailing list
>> Ham...@li... <mailto:Ham...@li...>
>> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Forgot to answer your other comment - the ticketing system(and other 
admin stuff) was moved from sourceforge to github.com -

https://github.com/Hamlib/Hamlib

73, n3gb

On 8/31/25 5:58 PM, Peter Marks wrote:
> Dear Hamlib developers,
>
> I don’t seem to be able to create a feature request ticket on 
> sourceforge. The button is dim.
>
> When hamlib reports an error, typically a timeout talking to the 
> radio, the error string returned by rigerror() is very detailed and 
> includes a stack trace.
>
> const char* rigerror 
> <https://hamlib.sourceforge.net/manuals/1.2.15/group__rig.html#ga675d0903517323b2689446d9513fc8db> 
> 	( 	int 	/errnum/ 	) 	
>
> get string describing the error code
>
>
> I’m involved in the FreeDV <https://freedv.org> project which uses 
> hamlib. We show the error string and find that it is intimidating to 
> users. They sometimes report that FreeDV has “crashed”.
>
> It would be great if there was a second version of the error string 
> with just the bit that the user needs. “Timeout talking to rig” for 
> example.
>
> Many thanks for your great work.
>
> Peter
> VK3TPM
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 80281719f4aaee97e2fbcbfccc52c428a807005d
      https://github.com/Hamlib/Hamlib/commit/80281719f4aaee97e2fbcbfccc52c428a807005d
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-08-31 (Sun, 31 Aug 2025)

  Changed paths:
    M src/conf.c
    M src/rig.c

  Log Message:
  -----------
  Fix twiddle_timeout

Fixes the definition of config parameter "twiddle_timeout" and
the description of rig_set_twiddle().


  Commit: 7180eb7da6297eb436a43c309151170580cc06d9
      https://github.com/Hamlib/Hamlib/commit/7180eb7da6297eb436a43c309151170580cc06d9
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-09-01 (Mon, 01 Sep 2025)

  Changed paths:
    M src/conf.c
    M src/rig.c

  Log Message:
  -----------
  Merge GitHub PR #1879


Compare: https://github.com/Hamlib/Hamlib/compare/4c520571dfb1...7180eb7da629

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 9f4755cf70e0a556bff61f433dbaab5e6e20f269
      https://github.com/Hamlib/Hamlib/commit/9f4755cf70e0a556bff61f433dbaab5e6e20f269
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-08-24 (Sun, 24 Aug 2025)

  Changed paths:
    M README.developer
    M configure.ac

  Log Message:
  -----------
  Add requirement for POSIX threads (pthreads)

I wrote this one-liner, and then realized I couldn't test it - I have
no systems that do not have pthreads as an integral part - does anybody?
Since <pthread.h> has been a de facto requirement since 4.5, the point may
be moot.
(Update: quick '# mv pthread.h pthread2.h' and it fails)

And are the URLs in README.developer correct? Should they point to github?


  Commit: df65ceee67bc11d6f6daba9bce3142ef55a082c5
      https://github.com/Hamlib/Hamlib/commit/df65ceee67bc11d6f6daba9bce3142ef55a082c5
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-08-24 (Sun, 24 Aug 2025)

  Changed paths:
    M include/hamlib/rig.h
    M include/hamlib/rig_state.h
    M rigs/anytone/anytone.c
    M rigs/dummy/rot_pstrotator.c
    M rigs/dummy/rot_pstrotator.h
    M rigs/flexradio/smartsdr.c
    M rigs/icom/icom.c
    M rigs/tentec/orion.h
    M src/fifo.c

  Log Message:
  -----------
  Start removing conditional pthreads use.

We can treat HAVE_PTHREAD and HAVE_PTHREAD_H as equivalent. But using
_PTHREAD_H is a real kludge.


  Commit: 9a90745ba693767a4c29caaabb406a3feb943982
      https://github.com/Hamlib/Hamlib/commit/9a90745ba693767a4c29caaabb406a3feb943982
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-08-24 (Sun, 24 Aug 2025)

  Changed paths:
    M rotators/ars/ars.c
    M rotators/ars/ars.h
    M src/event.c
    M src/mutex.h
    M src/network.c
    M src/rig.c

  Log Message:
  -----------
  More conditional pthread usage unleashed

Anybody know what sync_callback() is supposed to do? Currently
unused, very broken, and not even a header comment.


  Commit: 002677e48c2d5218254421472cefa6a354f54e84
      https://github.com/Hamlib/Hamlib/commit/002677e48c2d5218254421472cefa6a354f54e84
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-08-27 (Wed, 27 Aug 2025)

  Changed paths:
    M src/microham.c
    M src/misc.h
    M src/settings.c
    M tests/ampctl_parse.c
    M tests/rigctltcp.c
    M tests/rotctl_parse.c
    M tests/rotctld.c

  Log Message:
  -----------
  Still more pthread conditional code cleanup


  Commit: 1c0de2107c4061f2cd79958dc4e362a34f03a6c3
      https://github.com/Hamlib/Hamlib/commit/1c0de2107c4061f2cd79958dc4e362a34f03a6c3
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-08-30 (Sat, 30 Aug 2025)

  Changed paths:
    M tests/ampctld.c
    M tests/rigctld.c

  Log Message:
  -----------
  Remove conditionals based on HAVE_PTHREAD


  Commit: e09007a543f707cd833bbd1b199a804cb84c3b32
      https://github.com/Hamlib/Hamlib/commit/e09007a543f707cd833bbd1b199a804cb84c3b32
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-08-31 (Sun, 31 Aug 2025)

  Changed paths:
    M NEWS

  Log Message:
  -----------
  Update NEWS


  Commit: 4c520571dfb13cc04c42120e751d09af6f2ef0e6
      https://github.com/Hamlib/Hamlib/commit/4c520571dfb13cc04c42120e751d09af6f2ef0e6
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-08-31 (Sun, 31 Aug 2025)

  Changed paths:
    M NEWS
    M README.developer
    M configure.ac
    M include/hamlib/rig.h
    M include/hamlib/rig_state.h
    M rigs/anytone/anytone.c
    M rigs/dummy/rot_pstrotator.c
    M rigs/dummy/rot_pstrotator.h
    M rigs/flexradio/smartsdr.c
    M rigs/icom/icom.c
    M rigs/tentec/orion.h
    M rotators/ars/ars.c
    M rotators/ars/ars.h
    M src/event.c
    M src/fifo.c
    M src/microham.c
    M src/misc.h
    M src/mutex.h
    M src/network.c
    M src/rig.c
    M src/settings.c
    M tests/ampctl_parse.c
    M tests/ampctld.c
    M tests/rigctld.c
    M tests/rigctltcp.c
    M tests/rotctl_parse.c
    M tests/rotctld.c

  Log Message:
  -----------
  Merge GitHub PR #1876


Compare: https://github.com/Hamlib/Hamlib/compare/9123d08a6c95...4c520571dfb1

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 8f343197e0926ca422c3b6aeb66b39b1b43c6a6b
      https://github.com/Hamlib/Hamlib/commit/8f343197e0926ca422c3b6aeb66b39b1b43c6a6b
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-08-29 (Fri, 29 Aug 2025)

  Changed paths:
    M src/misc.c

  Log Message:
  -----------
  Replace a printf() with rig_debug()

The bug is that we don't know why the string is invalid.

Test case:
before
tests/rigctl -r "invalid:123:port" -m 2
Unhandled host=invalid:123:port
Unhandled host=invalid:123:port

after:
tests/rigctl -r "invalid:123:port" -m 2
(no output)
tests/rigctl -r "invalid:123:port" -m 2 -v
parse_hoststr: Unhandled host=invalid:123:port
parse_hoststr: Unhandled host=invalid:123:port


  Commit: 341a5201c6748bf17f0caa003fce2a7b87530bc2
      https://github.com/Hamlib/Hamlib/commit/341a5201c6748bf17f0caa003fce2a7b87530bc2
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-08-29 (Fri, 29 Aug 2025)

  Changed paths:
    M src/misc.c

  Log Message:
  -----------
  Replace literal constant with defined symbol


  Commit: 9123d08a6c95a59214a01da6551fd9c887939ce8
      https://github.com/Hamlib/Hamlib/commit/9123d08a6c95a59214a01da6551fd9c887939ce8
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-08-31 (Sun, 31 Aug 2025)

  Changed paths:
    M src/misc.c

  Log Message:
  -----------
  Merge GitHub PR #1874


Compare: https://github.com/Hamlib/Hamlib/compare/43b84ee56a66...9123d08a6c95

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 39e155efe71f9f2a84f42b5f64f510135173aa85
      https://github.com/Hamlib/Hamlib/commit/39e155efe71f9f2a84f42b5f64f510135173aa85
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-08-30 (Sat, 30 Aug 2025)

  Changed paths:
    M lib/precise_time.c
    M rigs/anytone/anytone.c
    M rigs/barrett/barrett.c
    M rigs/dummy/dummy.c
    M rigs/dummy/flrig.c
    M rigs/dummy/netrigctl.c
    M rigs/dummy/quisk.c
    M rigs/dummy/tci1x.c
    M rigs/dummy/trxmanager.c
    M rigs/kit/usrp_impl.cc
    M rigs/winradio/g313-posix.c
    M rigs/winradio/linradio/wrg313api.c
    M rotators/androidsensor/androidsensor.cpp
    M rotators/grbltrk/grbltrk.c
    M security/AESStringCrypt.c
    M src/fifo.c
    M src/parallel.h
    M tests/rigtestlibusb.c
    M tests/rigtestmcastrx.c
    M tests/testnet.c

  Log Message:
  -----------
  Fix include config.h

It should be included, with its path, before any hamlib include
and before any #ifdef that uses the symbols that it defines.


  Commit: 43b84ee56a66c19844c5efcb63f1217f57fac4c2
      https://github.com/Hamlib/Hamlib/commit/43b84ee56a66c19844c5efcb63f1217f57fac4c2
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-08-31 (Sun, 31 Aug 2025)

  Changed paths:
    M lib/precise_time.c
    M rigs/anytone/anytone.c
    M rigs/barrett/barrett.c
    M rigs/dummy/dummy.c
    M rigs/dummy/flrig.c
    M rigs/dummy/netrigctl.c
    M rigs/dummy/quisk.c
    M rigs/dummy/tci1x.c
    M rigs/dummy/trxmanager.c
    M rigs/kit/usrp_impl.cc
    M rigs/winradio/g313-posix.c
    M rigs/winradio/linradio/wrg313api.c
    M rotators/androidsensor/androidsensor.cpp
    M rotators/grbltrk/grbltrk.c
    M security/AESStringCrypt.c
    M src/fifo.c
    M src/parallel.h
    M tests/rigtestlibusb.c
    M tests/rigtestmcastrx.c
    M tests/testnet.c

  Log Message:
  -----------
  Merge GitHub PR #1873


Compare: https://github.com/Hamlib/Hamlib/compare/d227444aa60a...43b84ee56a66

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 83ed5abeb44e21c1e13a7a57e0f02eb8a1dece6e
      https://github.com/Hamlib/Hamlib/commit/83ed5abeb44e21c1e13a7a57e0f02eb8a1dece6e
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-08-30 (Sat, 30 Aug 2025)

  Changed paths:
    M src/amp_conf.c
    M src/amp_reg.c
    M src/amplifier.c
    M src/cm108.c
    M src/cm108.h
    M src/conf.c
    M src/extamp.c
    M src/gpio.c
    M src/iofunc.c
    M src/mem.c
    M src/network.c
    M src/parallel.c
    M src/register.c
    M src/register.h
    M src/rig.c
    M src/rot_conf.c
    M src/rot_reg.c
    M src/rot_settings.c
    M src/rotator.c
    M src/serial.c
    M src/settings.c
    M src/snapshot_data.c
    M src/sprintflst.c
    M src/usb_port.c
    M src/usb_port.h

  Log Message:
  -----------
  [src] Remove unused includes

Found by iwyu.


  Commit: 47f60d4ad7e98fe9c4d2dfe46cd531f8ebf64fe3
      https://github.com/Hamlib/Hamlib/commit/47f60d4ad7e98fe9c4d2dfe46cd531f8ebf64fe3
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-08-30 (Sat, 30 Aug 2025)

  Changed paths:
    M simulators/sim.h
    M simulators/simeasycomm.c
    M simulators/simelecraft.c
    M simulators/simelecraftk4.c
    M simulators/simft1000.c
    M simulators/simft736.c
    M simulators/simft747gx.c
    M simulators/simft817.c
    M simulators/simft847.c
    M simulators/simft897.c
    M simulators/simjupiter.c
    M simulators/simrotorez.c
    M simulators/simspid.c
    M simulators/simtrusdx.c
    M simulators/simts450.c
    M simulators/simts890.c

  Log Message:
  -----------
  [simulators] Remove unused includes

    Found by iwyu.


  Commit: d227444aa60ad7f35e204607d9506e1fab5b14bd
      https://github.com/Hamlib/Hamlib/commit/d227444aa60ad7f35e204607d9506e1fab5b14bd
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-08-30 (Sat, 30 Aug 2025)

  Changed paths:
    M src/amp_reg.c
    M src/rot_reg.c

  Log Message:
  -----------
  Fix return values of amp_load_backend() and rot_load_backend()

The value -EINVAL is in the domain of errno.


Compare: https://github.com/Hamlib/Hamlib/compare/0a06af1ddef5...d227444aa60a

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

Ha. Thanks.

Sent from Gmail Mobile


On Mon, 1 Sep 2025 at 9:12 am, Nate Bargmann <n0...@n0...> wrote:

> * On 2025 31 Aug 18:08 -0500, Peter Marks wrote:
> > Ha. Sorry. That’s what Google found.
>
> I guess we need to buy Search Engine Optimization.  🤣
>
> Here is a link I should have posted in my previous mail:
>
> https://github.com/Hamlib/Hamlib/wiki/Documentation
>
> 73, Nate
>
> --
> "The optimist proclaims that we live in the best of all
> possible worlds.  The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
>

* On 2025 31 Aug 18:08 -0500, Peter Marks wrote:
> Ha. Sorry. That’s what Google found.

I guess we need to buy Search Engine Optimization.  🤣

Here is a link I should have posted in my previous mail:

https://github.com/Hamlib/Hamlib/wiki/Documentation

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Ha. Sorry. That’s what Google found.

Sent from Gmail Mobile


On Mon, 1 Sep 2025 at 9:06 am, Nate Bargmann <n0...@n0...> wrote:

> * On 2025 31 Aug 16:59 -0500, Peter Marks wrote:
> > const char* rigerror <
> https://hamlib.sourceforge.net/manuals/1.2.15/group__rig.html#ga675d0903517323b2689446d9513fc8db>
>      (       int     errnum  )
> > get string describing the error code
>
> Yikes!  That's old enough to be turning gray!
>
> This version is a bit more up to date:
>
> https://hamlib.sourceforge.net/manuals/4.3/index.html
>
> Hopefully, we will have a better manual when 4.7.0 is released later
> this year.
>
> 73, Nate
>
> --
> "The optimist proclaims that we live in the best of all
> possible worlds.  The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
>

* On 2025 31 Aug 16:59 -0500, Peter Marks wrote:
> const char* rigerror <https://hamlib.sourceforge.net/manuals/1.2.15/group__rig.html#ga675d0903517323b2689446d9513fc8db>	(	int 	errnum	)	
> get string describing the error code

Yikes!  That's old enough to be turning gray!

This version is a bit more up to date:

https://hamlib.sourceforge.net/manuals/4.3/index.html

Hopefully, we will have a better manual when 4.7.0 is released later
this year.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819