hamlib-developer — hamlib developers forum

Re: [Hamlib-developer] IC7300 output power

[<gm...@bt...>]

Right, I can see the issue:


  1.
The IC-7300 PO meter display %age of maximum power. So 50% max power is displayed as 50%.
  2.
The CI-V returns PO meter reading.
  3.
Both Hamlib and Flrig convert this value to Watts using similar look-up tables. Basically they both follow the display on the rig.
  4.
So for 50% max power gets displayed as 50 W, rather than 25W.

Unfortunately I don't have an RF Power meter that covers 70 MHz. My 144/432 meter reads 8W at 50% max power on 70 MHz.

Interesting asides:

The code for IC-9700 (IIRC in icom.c) divides the calculated power by 10 for the 10 GHz.
The IC-705 when operating on battery (max power = 5W) displays 100% max power, but only returns 50% on CI-V, so both Hamlib and Flrig. Obviously the CAT software doesn't know it's running on battery, so it makes sense for the Icom to handle that change.

I can implement similar code for IC-7300 on 70 MHz that is there for IC-9700 on 10 GHz.

I've not tested AM.

Phil GM3ZZA.


________________________________
From: gm...@bt... <gm...@bt...>
Sent: 29 May 2025 2:04 PM
To: Nate Bargmann <n0...@n0...>; ham...@li... <ham...@li...>
Subject: Re: [Hamlib-developer] IC7300 output power

Hi Nate,

I can have a look at this. I've got a European model IC-7300 which has 4 metres. I can't do this remotely as I have no way of keying the rig using hamlib. So I'll see if I can get some time in the shack later today.

My usual means of keying the rig when remote is flrig and that appears to give the correct power (just over 20 W on 50% drive).

73
________________________________
From: Nate Bargmann <n0...@n0...>
Sent: 29 May 2025 1:35 PM
To: ham...@li... <ham...@li...>
Subject: Re: [Hamlib-developer] IC7300 output power

* On 2025 29 May 05:20 -0500, Sakari Nylund wrote:
> Opps!
>
> Forgot to mention:  rigctld Hamlib 4.7~git 2025-03-12T17:49:17Z SHA=f8740d
> 64-bit

That's rather old, but the code in question appears to have been in
place since February 2021:

https://github.com/Hamlib/Hamlib/commit/660fd9496263abe5a663dae7496a6efee3a002ed

I'll have to leave it to an Icom expert to figure out why 4m is off.

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

Re: [Hamlib-developer] IC7300 output power

[Sakari N. <sak...@ni...>]

Yep!

I have not updated Hamlib for a while as all I need has been working.
This power output came out to view after I wrote CqrlogAlpha to show 
output power while transmitting.

I tested quickly with flrig (2.0.04) and 70.170MHz keeping key down. My 
Diamond SX-1000 shows the same around 50Watts while
flrig power meter (100W scale) shows also full 100W output. It climbs up 
with steps (~1 sec each) 20-40-60-80-100 and stays then on full 100.

With AM and same frequency power meter has red mark at 20W and bar 
climbs up with same kind of stepping until 20W is reached.
Power meter shows ~15W. So that is near the truth as I have antenna 
connected, not pure resistive load.

But how ever it seems that flrig fails same way with CW (USB-D, FM) 
showing full power 100W on 70MHz.

-- 
Saku
OH1KH

Nate Bargmann kirjoitti 29.5.2025 klo 15.35:
> That's rather old, but the code in question appears to have been in
> place since February 2021:

Re: [Hamlib-developer] IC7300 output power

[<gm...@bt...>]

Hi Nate,

I can have a look at this. I've got a European model IC-7300 which has 4 metres. I can't do this remotely as I have no way of keying the rig using hamlib. So I'll see if I can get some time in the shack later today.

My usual means of keying the rig when remote is flrig and that appears to give the correct power (just over 20 W on 50% drive).

73
________________________________
From: Nate Bargmann <n0...@n0...>
Sent: 29 May 2025 1:35 PM
To: ham...@li... <ham...@li...>
Subject: Re: [Hamlib-developer] IC7300 output power

* On 2025 29 May 05:20 -0500, Sakari Nylund wrote:
> Opps!
>
> Forgot to mention:  rigctld Hamlib 4.7~git 2025-03-12T17:49:17Z SHA=f8740d
> 64-bit

That's rather old, but the code in question appears to have been in
place since February 2021:

https://github.com/Hamlib/Hamlib/commit/660fd9496263abe5a663dae7496a6efee3a002ed

I'll have to leave it to an Icom expert to figure out why 4m is off.

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

Re: [Hamlib-developer] IC7300 output power

[Nate B. <n0...@n0...>]

* On 2025 29 May 05:20 -0500, Sakari Nylund wrote:
> Opps!
> 
> Forgot to mention:  rigctld Hamlib 4.7~git 2025-03-12T17:49:17Z SHA=f8740d
> 64-bit

That's rather old, but the code in question appears to have been in
place since February 2021:

https://github.com/Hamlib/Hamlib/commit/660fd9496263abe5a663dae7496a6efee3a002ed

I'll have to leave it to an Icom expert to figure out why 4m is off.

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

Re: [Hamlib-developer] IC7300 output power

[Sakari N. <sak...@ni...>]

Opps!

Forgot to mention:  rigctld Hamlib 4.7~git 2025-03-12T17:49:17Z 
SHA=f8740d 64-bit

-- 
Saku
OH1KH

Sakari Nylund kirjoitti 29.5.2025 klo 13.17:
> Hi!
>
> While 4m opening just noticed that '+\get_level RFPOWER_METER_WATTS' 
> gives false reading on 70MHz.
> USB-D with full pwr setting it gives ~90W while power meter shows just 
> 50W that is known to max output of IC7300 on 70MHz.
>
> Perhaps there is an error in "power2mW" table (or 70MHz totally 
> missing?).

[Hamlib-developer] IC7300 output power

[Sakari N. <sak...@ni...>]

Hi!

While 4m opening just noticed that '+\get_level RFPOWER_METER_WATTS' 
gives false reading on 70MHz.
USB-D with full pwr setting it gives ~90W while power meter shows just 
50W that is known to max output of IC7300 on 70MHz.

Perhaps there is an error in "power2mW" table (or 70MHz totally missing?).

-- 
Saku
OH1KH

[Hamlib-developer] [Hamlib/Hamlib] 8f919a: Fix list of dependecies of aclocal.m4

[dforsi <no...@gi...>]

  Branch: refs/heads/Hamlib-4.6.3
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 8f919a5a54d7318afea557790d34ddb74c1c6b56
      https://github.com/Hamlib/Hamlib/commit/8f919a5a54d7318afea557790d34ddb74c1c6b56
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-29 (Thu, 29 May 2025)

  Changed paths:
    M macros/Makefile.am

  Log Message:
  -----------
  Fix list of dependecies of aclocal.m4

Adds missing ax_lib_readline.m4 and ax_lua.m4 to the list of MACROS.
Also sorts the list.

(cherry picked from commit 9fdf8f201ce78a2c3b8b0a245bdd2cacf17cbb68)



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

[Hamlib-developer] [Hamlib/Hamlib] 9fdf8f: Fix list of dependecies of aclocal.m4

[dforsi <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 9fdf8f201ce78a2c3b8b0a245bdd2cacf17cbb68
      https://github.com/Hamlib/Hamlib/commit/9fdf8f201ce78a2c3b8b0a245bdd2cacf17cbb68
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-27 (Tue, 27 May 2025)

  Changed paths:
    M macros/Makefile.am

  Log Message:
  -----------
  Fix list of dependecies of aclocal.m4

Adds missing ax_lib_readline.m4 and ax_lua.m4 to the list of MACROS.
Also sorts the list.



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

Re: [Hamlib-developer] serial_setup: tcsetattr failed: No error

[Daniele F. <iu...@gm...>]

Hello,

> There's a problem with Hamlib w64-4.6.2. The serial port is recognized but not working. I get this message:
>
>
>
> C:\Program Files\hamlib-w64-4.6.2\bin>rotctld.exe -m 202 -r COM4 -s 9600 -T 127.0.0.1 -t 4533 -vvv
>
> serial_setup: tcsetattr failed: No error

Are you using the version released at
https://github.com/Hamlib/Hamlib/releases or did you compile it?

Do you have other software that works with those settings?

I just run your command line both on 4.6.2 from link above and on
4.6.3-rc1 from https://n0nb.users.sourceforge.net/rc/ and both open my
COM1

-- 
73 de IU5HKX Daniele

Re: [Hamlib-developer] Bandwidths and Filters

[Daniele F. <iu...@gm...>]

Hello Stefan,

> Sorry for my maybe stupid question.

it isn't a stupid question but it is unclear what you want to do, why
can't you use "set_mode"?

the man pages or the documentation generated on a local machine with
Doxygen and also available online should contain all information, but
some parts may be undocumented




--
73 de IU5HKX Daniele

Re: [Hamlib-developer] 4.6.3 and 4.7.0 releases plan

[Nate B. <n0...@n0...>]

After a few additional cherry-picks I've created an ~rc1 tarball and
Windows binaries.  They are available at:

https://n0nb.users.sourceforge.net/rc/

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] [Hamlib/Hamlib] 53d2ee: Add locking around get/set levels

[GeoBaltz <no...@gi...>]

  Branch: refs/heads/Hamlib-4.6.3
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 53d2eed741d36fd87622a601590d8e860f048bc3
      https://github.com/Hamlib/Hamlib/commit/53d2eed741d36fd87622a601590d8e860f048bc3
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-05-26 (Mon, 26 May 2025)

  Changed paths:
    M src/settings.c

  Log Message:
  -----------
  Add locking around get/set levels

(cherry picked from commit b5df48d8d9839460e13201765b278c6a32741158)



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

[Hamlib-developer] [Hamlib/Hamlib] b5df48: Add locking around get/set levels

[Nate B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: b5df48d8d9839460e13201765b278c6a32741158
      https://github.com/Hamlib/Hamlib/commit/b5df48d8d9839460e13201765b278c6a32741158
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2025-05-24 (Sat, 24 May 2025)

  Changed paths:
    M src/settings.c

  Log Message:
  -----------
  Add locking around get/set levels


  Commit: 717d720a3605745a47812908b088117580e4e10c
      https://github.com/Hamlib/Hamlib/commit/717d720a3605745a47812908b088117580e4e10c
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-05-26 (Mon, 26 May 2025)

  Changed paths:
    M src/settings.c

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


Compare: https://github.com/Hamlib/Hamlib/compare/43017b38f08c...717d720a3605

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

[Hamlib-developer] [Hamlib/Hamlib] 303463: Fix typo

[dforsi <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 3034631b2f99f32680e2939035f45019a2fc38c3
      https://github.com/Hamlib/Hamlib/commit/3034631b2f99f32680e2939035f45019a2fc38c3
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-26 (Mon, 26 May 2025)

  Changed paths:
    M rigs/dummy/amp_dummy.c

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


  Commit: 43017b38f08c6ed75fa9c5a4d88bdb0875e7c15a
      https://github.com/Hamlib/Hamlib/commit/43017b38f08c6ed75fa9c5a4d88bdb0875e7c15a
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-26 (Mon, 26 May 2025)

  Changed paths:
    M doc/man1/rotctld.1

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

Add closing tag for example text.


Compare: https://github.com/Hamlib/Hamlib/compare/f459eea516a3...43017b38f08c

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

[Hamlib-developer] [Hamlib/Hamlib] ffb61c: Fix typo

[dforsi <no...@gi...>]

  Branch: refs/heads/Hamlib-4.6.3
  Home:   https://github.com/Hamlib/Hamlib
  Commit: ffb61c29a5aa0eca95d4cf62e3cb15c610a223ce
      https://github.com/Hamlib/Hamlib/commit/ffb61c29a5aa0eca95d4cf62e3cb15c610a223ce
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-26 (Mon, 26 May 2025)

  Changed paths:
    M rigs/dummy/amp_dummy.c

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

(cherry picked from commit 3034631b2f99f32680e2939035f45019a2fc38c3)


  Commit: f0ac83bcba5b7bf0a6a2db18d31069bbd118cd41
      https://github.com/Hamlib/Hamlib/commit/f0ac83bcba5b7bf0a6a2db18d31069bbd118cd41
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-26 (Mon, 26 May 2025)

  Changed paths:
    M doc/man1/rotctld.1

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

Add closing tag for example text.

(cherry picked from commit 43017b38f08c6ed75fa9c5a4d88bdb0875e7c15a)


Compare: https://github.com/Hamlib/Hamlib/compare/e641162a6be7...f0ac83bcba5b

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

Re: [Hamlib-developer] 4.6.3 and 4.7.0 releases plan

[Nate B. <n0...@n0...>]

Astute observers will have noticed that I updated the NEWS file, created
the Hamlib-4.6.3 branch, and updated its configure.ac to version
4.6.3~rc1.  I plan to generate an rc1 tarball and Windows binaries and
put them in a temporary directory on the daily snapshots page for
testing.

While I wanted to get to this about a month earlier, real life had other
ideas!  I've set a target release date of 10 June which should give a
change to shake down this branch and get a good solid release out while
opening up 'master' to development for 4.7.0.

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] [Hamlib/Hamlib] e64116: Advance to 4.6.3~rc1

[Nate B. <no...@gi...>]

  Branch: refs/heads/Hamlib-4.6.3
  Home:   https://github.com/Hamlib/Hamlib
  Commit: e641162a6be7570a20b6e0189a53063cdbca1a39
      https://github.com/Hamlib/Hamlib/commit/e641162a6be7570a20b6e0189a53063cdbca1a39
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-05-25 (Sun, 25 May 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Advance to 4.6.3~rc1



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

[Hamlib-developer] [Hamlib/Hamlib] f459ee: Update NEWS for 4.6.3 release

[Nate B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: f459eea516a3e5c9b74c72dd4a430fcde1764f71
      https://github.com/Hamlib/Hamlib/commit/f459eea516a3e5c9b74c72dd4a430fcde1764f71
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-05-25 (Sun, 25 May 2025)

  Changed paths:
    M NEWS

  Log Message:
  -----------
  Update NEWS for 4.6.3 release



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

[Hamlib-developer] Issue with simultaneous access to rigctld by multiple TCP clients - Probable Low Priority

[Stephen P. <st...@bi...>]

Hi,

I have several programs that interrogate rigctld simultaneously which 
among other things request various radio parameters from my IC-7300 
every second. With just one rigctld client program running I have no 
issue, but I have discovered a number of issues that the developers may 
or may not consider worth of rectification, when multiple rigctld 
clients request radio parameters more of less simultaneously.

I can work around these issues, but nevertheless, I think they are worth 
of reporting.

Hamlib version is  -  hamlib-w64-4.6.2

Windows (10) DOS Command to start rigctld is as follows: “rigctld -m 
3073 -r COM4 -s 115200 -vvv”

These issues are probably all related or indeed have the same cause, but 
I’ll list separately.

1 – Two Python programs are requesting the ptt status of the radio every 
second. There is no synchronization between the two programs, so whether 
or not they request the ptt status at the same time is hard to say. The 
programs also request the frequency and mode of the radio.

Both programs request the ptt status using the “extended” method, ie the 
TCP message is (in Python code). I’m using the optional ‘|’ separator as 
can be seen from the code snippet

     sentBytes = rigctldSock.sendall(b'|t\n')
     response = rigctldSock.recv(1024)

The response should be                         b'get_ptt:|PTT: 0|RPRT 0\n'
however, every now and again, the response is of the form 
b'get_ptt:\nPTT: 0\nRPRT 0\n'

which causes my parsing to fail. The response looks like the result as 
if the ‘+’ separator was used, however this is not the case. Perhaps I 
can avoid this by using the ‘+’ separator, but it shouldn’t be necessary.

2- Running the commercial LOG4OM program which is configured to use the 
“Hamlib NET rigctl Stable” rig model, and one of my Python programs has 
a similar effect as described in issue 1 above. I don’t of course know 
the exact command that LOG4OM is using other than it is communicating to 
rigctld on port 4532.

Also, the issue arises with multiple parameters. Once again, my program 
uses the ‘|’ separator character. I don’t know what LOG4OM uses, or 
indeed if it uses the “extended” or “default” method.

As before, expected responses are of the form ( for get_ptt and get_mode 
commands)

     b'get_ptt:|PTT: 0|RPRT 0\n'
     b'get_mode:|Mode: LSB|Passband: 2400|RPRT 0\n'

however, occasionally the responses are

     b'get_ptt:\nPTT: 0\nRPRT 0\n'
     b'get_mode:\nMode: LSB\nPassband: 2400\nRPRT 0\n'

which fails my parsing due to the LF char unexpectedly replacing the ‘|’ 
char.

The cause is no doubt the same as in issue one. It may or may not matter 
if two programs accessing rigctld use the same separator character.

3 – A similar issue arises if one rigctld TCP client is using the 
“default” protocol and other the “extended” protocol more of less 
simultaneously.

For example, I have one Python program accessing rig frequency using the 
“extended” protocol which results in a response of this form

     b'get_freq:|Frequency: 1424840|RPRT 0\n'

at the same approximate time, the second client program uses the 
“default” protocol which results in a response of this form

     b'1424840\n'

however, every once in a while, the response to the “default” protocol 
results in this response

     b'1424840|\n'

It appears that the “default” response has been “infected” by the 
separation character of the “extended” response due to the other client.

Of course, maybe I shouldn’t allow mixing of the two types of request, 
but of course I have no easy way of knowing what any other arbitrary 
program might be using that may simultaneously request radio parameters.

In summary, I feel these issues which probably all have the same root 
cause may warrant looking at, but I will totally understand if it is 
regarded as low priority or not worth fixing. In my case, I’ll probably 
alter my programs to use the ‘+’ separator character that results in 
‘\n’ characters separating the fields as I suspect this is what is 
usually used.

Thanks for reading.
Rgds
Steve
VK3SPX

[Hamlib-developer] [Hamlib/Hamlib] 0fd094: Fix issue where Hamlib attempts to use memory retu...

[Mooneer S. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 0fd094f4765737c00f852838c739c702a2e7376f
      https://github.com/Hamlib/Hamlib/commit/0fd094f4765737c00f852838c739c702a2e7376f
  Author: Mooneer Salem <mo...@gm...>
  Date:   2025-05-22 (Thu, 22 May 2025)

  Changed paths:
    M include/num_stdio.h

  Log Message:
  -----------
  Fix issue where Hamlib attempts to use memory returned by setlocale() after being freed.



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

[Hamlib-developer] [Hamlib/Hamlib] 84376c: Use the variable with the version number in the ex...

[Nate B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 84376c45616d0a50023815f10b89eafe6f45e02a
      https://github.com/Hamlib/Hamlib/commit/84376c45616d0a50023815f10b89eafe6f45e02a
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-22 (Thu, 22 May 2025)

  Changed paths:
    M scripts/build-w32.sh
    M scripts/build-w64.sh

  Log Message:
  -----------
  Use the variable with the version number in the example path


  Commit: 4109d606b598a8ca84ebdbe6d06b740928b4e5bf
      https://github.com/Hamlib/Hamlib/commit/4109d606b598a8ca84ebdbe6d06b740928b4e5bf
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-22 (Thu, 22 May 2025)

  Changed paths:
    M rigs/aor/ar7030.c
    M rigs/dummy/aclog.c
    M rigs/dummy/flrig.c
    M rigs/dummy/tci1x.c
    M rigs/elad/elad.c
    M rigs/icom/frame.c
    M rigs/icom/ic746.c
    M rigs/icom/ic756.c
    M rigs/icom/ic820h.c
    M rigs/icom/ic821h.c
    M rigs/icom/icom.c
    M rigs/jrc/jrc.c
    M rigs/kenwood/kenwood.c
    M rigs/kenwood/tmv7.c
    M rigs/kenwood/ts870s.c
    M rigs/kit/drt1.c
    M rigs/kit/elektor507.c
    M rigs/kit/pcrotor.c
    M rigs/uniden/uniden.c
    M rigs/uniden/uniden_digital.c
    M rigs/wj/wj8888.c
    M rigs/yaesu/ft757gx.c
    M rigs/yaesu/ft817.c
    M rigs/yaesu/ft857.c
    M rigs/yaesu/ft891.c
    M rigs/yaesu/ft897.c
    M rigs/yaesu/pmr171.c
    M rigs/yaesu/vr5000.c
    M rigs/yaesu/vx1700.c
    M rotators/celestron/celestron.c
    M rotators/gs232a/gs232.c
    M rotators/gs232a/gs232a.c
    M rotators/gs232a/gs232b.c
    M rotators/ioptron/rot_ioptron.c
    M rotators/m2/rc2800.c
    M rotators/meade/meade.c
    M rotators/prosistel/prosistel.c
    M rotators/spid/spid.c
    M simulators/simts890.c
    M tests/dumpmem.c
    M tests/rigctl_parse.c
    M tests/test2038.c

  Log Message:
  -----------
  Fix typos


  Commit: 87311035ea67d73a1a02d99e55b2a522486bead7
      https://github.com/Hamlib/Hamlib/commit/87311035ea67d73a1a02d99e55b2a522486bead7
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-22 (Thu, 22 May 2025)

  Changed paths:
    M README.md
    M scripts/build-w32.sh
    M scripts/build-w64.sh

  Log Message:
  -----------
  Also mention amplifiers


  Commit: dbe89b2092f808e4fe3d7286b6459a9803cd5361
      https://github.com/Hamlib/Hamlib/commit/dbe89b2092f808e4fe3d7286b6459a9803cd5361
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-22 (Thu, 22 May 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Remove duplicated comment


  Commit: 9570d9963b44a4ee2ad8d2a6befb982fd4dcb6fc
      https://github.com/Hamlib/Hamlib/commit/9570d9963b44a4ee2ad8d2a6befb982fd4dcb6fc
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-05-22 (Thu, 22 May 2025)

  Changed paths:
    M README.md
    M configure.ac
    M rigs/aor/ar7030.c
    M rigs/dummy/aclog.c
    M rigs/dummy/flrig.c
    M rigs/dummy/tci1x.c
    M rigs/elad/elad.c
    M rigs/icom/frame.c
    M rigs/icom/ic746.c
    M rigs/icom/ic756.c
    M rigs/icom/ic820h.c
    M rigs/icom/ic821h.c
    M rigs/icom/icom.c
    M rigs/jrc/jrc.c
    M rigs/kenwood/kenwood.c
    M rigs/kenwood/tmv7.c
    M rigs/kenwood/ts870s.c
    M rigs/kit/drt1.c
    M rigs/kit/elektor507.c
    M rigs/kit/pcrotor.c
    M rigs/uniden/uniden.c
    M rigs/uniden/uniden_digital.c
    M rigs/wj/wj8888.c
    M rigs/yaesu/ft757gx.c
    M rigs/yaesu/ft817.c
    M rigs/yaesu/ft857.c
    M rigs/yaesu/ft891.c
    M rigs/yaesu/ft897.c
    M rigs/yaesu/pmr171.c
    M rigs/yaesu/vr5000.c
    M rigs/yaesu/vx1700.c
    M rotators/celestron/celestron.c
    M rotators/gs232a/gs232.c
    M rotators/gs232a/gs232a.c
    M rotators/gs232a/gs232b.c
    M rotators/ioptron/rot_ioptron.c
    M rotators/m2/rc2800.c
    M rotators/meade/meade.c
    M rotators/prosistel/prosistel.c
    M rotators/spid/spid.c
    M scripts/build-w32.sh
    M scripts/build-w64.sh
    M simulators/simts890.c
    M tests/dumpmem.c
    M tests/rigctl_parse.c
    M tests/test2038.c

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


Compare: https://github.com/Hamlib/Hamlib/compare/9b177cd8b3bc...9570d9963b44

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

[Hamlib-developer] [Hamlib/Hamlib] 5fe81c: Fix compilation errors and warnings and link failure

[Nate B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 5fe81cdef4fcceff52c7cedc0eac6788c2f64881
      https://github.com/Hamlib/Hamlib/commit/5fe81cdef4fcceff52c7cedc0eac6788c2f64881
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-17 (Sat, 17 May 2025)

  Changed paths:
    M rigs/kit/usrp.c
    M rigs/kit/usrp_impl.cc

  Log Message:
  -----------
  Fix compilation errors and warnings and link failure

Compile-tested with commit 8ea3f0e (tag: 3.4.10)
from https://github.com/osmocom/libusrp

Fixes:
usrp_impl.cc:33:10: fatal error: usrp_standard.h: No such file or directory
usrp_impl.cc:49:63: error: expected '(' before 'malloc'
usrp_impl.cc:49:100: error: expected ')' before ';' token
usrp_impl.cc:72:39: error: invalid 'static_cast' from type 'rig_state*' to type 'usrp_priv_data*'
usrp_impl.cc:86:39: error: invalid 'static_cast' from type 'rig_state*' to type 'usrp_priv_data*'
usrp_impl.cc:104:39: error: invalid 'static_cast' from type 'rig_state*' to type 'usrp_priv_data*'
usrp_impl.cc:129:45: error: invalid 'static_cast' from type 'rig_state*' to type 'usrp_priv_data*'
usrp_impl.cc:151:45: error: invalid 'static_cast' from type 'rig_state*' to type 'usrp_priv_data*'
usrp_impl.cc:169:45: error: invalid 'static_cast' from type 'rig_state*' to type 'usrp_priv_data*'

usrp_impl.cc:114:37: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
usrp_impl.cc:139:38: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]

/usr/bin/ld: ../src/.libs/libhamlib.so: undefined reference to `usrp_caps'


  Commit: 9b177cd8b3bcbc47126961377e6b14c689918af2
      https://github.com/Hamlib/Hamlib/commit/9b177cd8b3bcbc47126961377e6b14c689918af2
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-05-22 (Thu, 22 May 2025)

  Changed paths:
    M rigs/kit/usrp.c
    M rigs/kit/usrp_impl.cc

  Log Message:
  -----------
  Merge GitHub PR #1739.


Compare: https://github.com/Hamlib/Hamlib/compare/91a4d914d9dd...9b177cd8b3bc

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

[Hamlib-developer] [Hamlib/Hamlib] 57e5db: Make usage texts more similar

[Nate B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 57e5dba438cd01adb9ccca1024a74d2665cfd914
      https://github.com/Hamlib/Hamlib/commit/57e5dba438cd01adb9ccca1024a74d2665cfd914
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-14 (Wed, 14 May 2025)

  Changed paths:
    M tests/ampctl.c
    M tests/ampctld.c
    M tests/rigctl.c
    M tests/rigctld.c
    M tests/rigctltcp.c
    M tests/rigmem.c
    M tests/rigsmtr.c
    M tests/rigswr.c
    M tests/rotctl.c
    M tests/rotctld.c

  Log Message:
  -----------
  Make usage texts more similar


  Commit: dc3a71da1b826099f7c1586f7fc451bf3c842571
      https://github.com/Hamlib/Hamlib/commit/dc3a71da1b826099f7c1586f7fc451bf3c842571
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-14 (Wed, 14 May 2025)

  Changed paths:
    M tests/ampctl.c
    M tests/rigctl.c
    M tests/rotctl.c

  Log Message:
  -----------
  Document existing option to read commands from stdin


  Commit: e34ae180a23a99f4dcff3e6b67310029189f04e9
      https://github.com/Hamlib/Hamlib/commit/e34ae180a23a99f4dcff3e6b67310029189f04e9
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-14 (Wed, 14 May 2025)

  Changed paths:
    M tests/rigctld.c

  Log Message:
  -----------
  Remove unused definition of -z command line option


  Commit: 55cae893f02455a2a00491f9b8f165996e672ee3
      https://github.com/Hamlib/Hamlib/commit/55cae893f02455a2a00491f9b8f165996e672ee3
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-14 (Wed, 14 May 2025)

  Changed paths:
    M tests/rigctlsync.c

  Log Message:
  -----------
  Fix definition of -B/--mapa2b command line option

It doesn't accept an argument.


  Commit: b03dea99b5ad2183f3cf30032794c991b0995d28
      https://github.com/Hamlib/Hamlib/commit/b03dea99b5ad2183f3cf30032794c991b0995d28
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-14 (Wed, 14 May 2025)

  Changed paths:
    M tests/rigctlsync.c

  Log Message:
  -----------
  Allow to give the command lines options --list or --version


  Commit: 91a4d914d9dd1a8aed8822e185109cacc143057c
      https://github.com/Hamlib/Hamlib/commit/91a4d914d9dd1a8aed8822e185109cacc143057c
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-05-22 (Thu, 22 May 2025)

  Changed paths:
    M tests/ampctl.c
    M tests/ampctld.c
    M tests/rigctl.c
    M tests/rigctld.c
    M tests/rigctlsync.c
    M tests/rigctltcp.c
    M tests/rigmem.c
    M tests/rigsmtr.c
    M tests/rigswr.c
    M tests/rotctl.c
    M tests/rotctld.c

  Log Message:
  -----------
  Merge branch 'fix/usage-texts' of github.com:dforsi/Hamlib into dforsi-fix/usage-texts

>From GitHub PR #1735.


Compare: https://github.com/Hamlib/Hamlib/compare/73607aeb5414...91a4d914d9dd

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

[Hamlib-developer] [Hamlib/Hamlib] daa5c8: Fix --enable-winradio[=yes] being considered =no

[Nate B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: daa5c83a82f12fe397c8a553cb4940bb7b4a72b5
      https://github.com/Hamlib/Hamlib/commit/daa5c83a82f12fe397c8a553cb4940bb7b4a72b5
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-13 (Tue, 13 May 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Fix --enable-winradio[=yes] being considered =no


  Commit: 50462e65644056efd43de533798eda5b23097b7f
      https://github.com/Hamlib/Hamlib/commit/50462e65644056efd43de533798eda5b23097b7f
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-13 (Tue, 13 May 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Fix --enable-parallel[=yes] being considered =no


  Commit: 5370bbd32e0d5d212357b2d0f9f4d608eb242b21
      https://github.com/Hamlib/Hamlib/commit/5370bbd32e0d5d212357b2d0f9f4d608eb242b21
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-13 (Tue, 13 May 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Fix --enable-html-matrix[=yes] being considered =no


  Commit: 9aee8f8343812a0e671f7b1fa330ba6a8f25da26
      https://github.com/Hamlib/Hamlib/commit/9aee8f8343812a0e671f7b1fa330ba6a8f25da26
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-13 (Tue, 13 May 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Fix --with-readline[=yes] being considered =no


  Commit: ce95b034c65251999c931403ba1228dbef252cf6
      https://github.com/Hamlib/Hamlib/commit/ce95b034c65251999c931403ba1228dbef252cf6
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-13 (Tue, 13 May 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Fix --with-libusb[=yes] being considered =no


  Commit: 435a354ee072f9e6fe033add021b5fe44a92b19d
      https://github.com/Hamlib/Hamlib/commit/435a354ee072f9e6fe033add021b5fe44a92b19d
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-17 (Sat, 17 May 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Fix --with-indi[=no] being considered =yes


  Commit: 94bf1d717aaa29678a98cf50455648a6410df795
      https://github.com/Hamlib/Hamlib/commit/94bf1d717aaa29678a98cf50455648a6410df795
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2025-05-17 (Sat, 17 May 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Fix failure of ./configure --with-tcl-binding --with-xml-support

If pkg-config has found tcl.pc, then tclConfig.sh is not executed
and $TCL_INCLUDE_SPEC is empty so the test for tcl.h fails.
This patch moves the test inside the "else" case where the variable
is always defined.
The is a bug exposed by the fact that --with-xml-support redefines
the macro PKG_CHECK_MODULES.
Fix verified moving aside /usr/lib/x86_64-linux-gnu/pkgconfig/tcl.pc

Fixes:
configure: error: Unable to find Tcl headers


  Commit: 73607aeb5414c90e63f2c1f92ece65c550d76895
      https://github.com/Hamlib/Hamlib/commit/73607aeb5414c90e63f2c1f92ece65c550d76895
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-05-22 (Thu, 22 May 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Merge branch 'dforsi-fix/ac_arg_enable'

Reference GitHub PR #1731.


Compare: https://github.com/Hamlib/Hamlib/compare/ad824fa85e42...73607aeb5414

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

Re: [Hamlib-developer] Moving rig_cache out of rig_state into private storage

[Mikael N. <mik...@fa...>]

Hi!

Writing down my 2 cents here, as I've developed parts of the caching code (+ UDP packet updates when cached data changes, incl. waterfall data streaming).

The rig_cache struct and everything related to caching should indeed be completely internal to Hamlib. It's great to have the public API of Hamlib cleaned up.

73,
Mikael OH3BHX

On Sat, May 17, 2025, at 19:45, George Baltz wrote:
> On 5/17/25 4:44 AM, Daniele Forsi wrote:
>> Hello,
>>
>>> I think the rig_cache structure should be completely internal to Hamlib, and not visible to the calling application.
>> that's a good thing
>
>                 ^
>
>              very
>
>>
>>> I hope there's no big use of this data elsewhere.
>> how external software would be using the current cache API?
> Strange are the ways of application programmers
>>
>> I grepped for "rig_cache" in the sources that I have locally (mostly
>> from Debian) and I found it only in Hamlib
>>
>> I searched on github for
>> language:C symbol:rig_cache NOT (path:rig.h OR path:cache.h OR path:cache.c)
>>
>> and found 15 results unrelated to Hamlib; a search that doesn't
>> exclude the files above returns more than 3000 results, including
>> various copies of Hamlib
>
> Given that there were no other responses, I'll go ahead and finish 
> tidying up the code, and create a PR for master.
>
>
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer