hamlib-developer — hamlib developers forum

Re: [Hamlib-developer] Hamlib vs Python

[Timothy M. <tm...@mo...>]

Not at the Hamlib API level, but rather via rigctld.  In that case, I just recently created a Python program to provide a *very* basic GUI to control my Icom IC-707.

Tim
AD8JL

Sent from my iPad

On Oct 26, 2024, at 2:53 PM, Alexander Anipkin <ale...@gm...> wrote:


Hello

No answer. :(
OK.
Another question:
Anybody in the mail-list uses python to access hamlib?



Best regards
Alexander



ср, 23 окт. 2024 г. в 18:12, Alexander Anipkin <ale...@gm...<mailto:ale...@gm...>>:
Hello!

Can somebody advise the correct way to call the "get_split_vfo" function from Python?
I always get error:
TypeError: in method 'Rig_get_split_vfo', argument 2 of type 'split_t *'


Best regards
Alexander

_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Re: [Hamlib-developer] Hamlib vs Python

[Alexander A. <ale...@gm...>]

Hello

No answer. :(
OK.
Another question:
*Anybody in the mail-list uses python to access hamlib?*



Best regards
Alexander



ср, 23 окт. 2024 г. в 18:12, Alexander Anipkin <ale...@gm...>:

> Hello!
>
> Can somebody advise the correct way to call the "get_split_vfo" function
> from Python?
> I always get error:
> TypeError: in method 'Rig_get_split_vfo', argument 2 of type 'split_t *'
>
>
> Best regards
> Alexander
>
>

[Hamlib-developer] [Hamlib/Hamlib] aa6d02: Promote IC2730 to stable

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: aa6d028b73934a307aae3b6d8a0cb7ca11f554ef
      https://github.com/Hamlib/Hamlib/commit/aa6d028b73934a307aae3b6d8a0cb7ca11f554ef
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-26 (Sat, 26 Oct 2024)

  Changed paths:
    M rigs/icom/ic2730.c

  Log Message:
  -----------
  Promote IC2730 to stable



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

[Hamlib-developer] [Hamlib/Hamlib] 9b26eb: Fix power_minmax for kenwood

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 9b26eb1684d4be31c71857ae2fcc2d246e680710
      https://github.com/Hamlib/Hamlib/commit/9b26eb1684d4be31c71857ae2fcc2d246e680710
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-22 (Tue, 22 Oct 2024)

  Changed paths:
    M rigs/kenwood/kenwood.c

  Log Message:
  -----------
  Fix power_minmax for kenwood
https://github.com/Hamlib/Hamlib/issues/1622


  Commit: 407a1deabe03e6b3fed17c9ba8288deafd839bd2
      https://github.com/Hamlib/Hamlib/commit/407a1deabe03e6b3fed17c9ba8288deafd839bd2
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-22 (Tue, 22 Oct 2024)

  Changed paths:

  Log Message:
  -----------
  Merge branch 'master' of https://github.com/Hamlib/Hamlib


  Commit: f9d60d6b25d24b66b37b7c48f1afba548a6dd2c5
      https://github.com/Hamlib/Hamlib/commit/f9d60d6b25d24b66b37b7c48f1afba548a6dd2c5
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-22 (Tue, 22 Oct 2024)

  Changed paths:
    M include/hamlib/rig.h

  Log Message:
  -----------
  Remove duplicate parm


  Commit: e3b067307a93bebd3eab6c5d11687f6adc482d27
      https://github.com/Hamlib/Hamlib/commit/e3b067307a93bebd3eab6c5d11687f6adc482d27
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-25 (Fri, 25 Oct 2024)

  Changed paths:
    M rigs/icom/icom.c
    M rigs/icom/icom.h

  Log Message:
  -----------
  Fix icom width filter using 1,2,3 for all modes


Compare: https://github.com/Hamlib/Hamlib/compare/8b0dc0731c34...e3b067307a93

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

Re: [Hamlib-developer] (no subject)

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

* On 2024 23 Oct 19:38 -0500, ABN ali wrote:
> https://www.mankier.com/7/hamlib

Nice HTML conversion.  Thanks.

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] (no subject)

[ABN a. <swr...@gm...>]

https://www.mankier.com/7/hamlib

[Hamlib-developer] Hamlib vs Python

[Alexander A. <ale...@gm...>]

Hello!

Can somebody advise the correct way to call the "get_split_vfo" function
from Python?
I always get error:
TypeError: in method 'Rig_get_split_vfo', argument 2 of type 'split_t *'


Best regards
Alexander

Re: [Hamlib-developer] [Hamlib/Hamlib] 87531d: Fix KEYERTYPE

[George B. <geo...@gm...>]

Wasn't RIG_PARM_KEYERTYPE already in RIG_PARM_STRING_LIST?

On 10/21/24 11:32 PM, Michael Black via Hamlib-developer wrote:
>    Branch: refs/heads/master
>    Home:   https://github.com/Hamlib/Hamlib
>    Commit: 87531d273dd3902e2130c9a7db64da2dbc518cb1
>        https://github.com/Hamlib/Hamlib/commit/87531d273dd3902e2130c9a7db64da2dbc518cb1
>    Author: Mike Black W9MDB <mdb...@ya...>
>    Date:   2024-10-21 (Mon, 21 Oct 2024)
>
>    Changed paths:
>      M include/hamlib/rig.h
>      M tests/rigctl_parse.c
>
>    Log Message:
>    -----------
>    Fix KEYERTYPE
>
>
>
> 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

[Hamlib-developer] [Hamlib/Hamlib] 8b0dc0: Fix power_minmax for kenwood

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 8b0dc0731c34d215d991f1f11b76ee503221ae72
      https://github.com/Hamlib/Hamlib/commit/8b0dc0731c34d215d991f1f11b76ee503221ae72
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-22 (Tue, 22 Oct 2024)

  Changed paths:
    M rigs/kenwood/kenwood.c

  Log Message:
  -----------
  Fix power_minmax for kenwood



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

[Hamlib-developer] [Hamlib/Hamlib] 87531d: Fix KEYERTYPE

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 87531d273dd3902e2130c9a7db64da2dbc518cb1
      https://github.com/Hamlib/Hamlib/commit/87531d273dd3902e2130c9a7db64da2dbc518cb1
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-21 (Mon, 21 Oct 2024)

  Changed paths:
    M include/hamlib/rig.h
    M tests/rigctl_parse.c

  Log Message:
  -----------
  Fix KEYERTYPE



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

[Hamlib-developer] [Hamlib/Hamlib] f6b8bd: Allow 1, 2, 3 width usage for all modes in icom.c

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: f6b8bdabe8fe369249b0f22946a3c417f1368056
      https://github.com/Hamlib/Hamlib/commit/f6b8bdabe8fe369249b0f22946a3c417f1368056
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-20 (Sun, 20 Oct 2024)

  Changed paths:
    M rigs/icom/icom.c
    M rigs/icom/icom.h

  Log Message:
  -----------
  Allow 1,2,3 width usage for all modes in icom.c



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

[Hamlib-developer] [Hamlib/Hamlib] c02cf9: Fix compile warning on icom.c fm_filters

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: c02cf9726f5857e74eb4bd0545a881d8ccc8c112
      https://github.com/Hamlib/Hamlib/commit/c02cf9726f5857e74eb4bd0545a881d8ccc8c112
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-18 (Fri, 18 Oct 2024)

  Changed paths:
    M rigs/icom/icom.c
    M rigs/icom/icom.h

  Log Message:
  -----------
  Fix compile warning on icom.c fm_filters



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

[Hamlib-developer] [Hamlib/Hamlib] 41eb2b: Fix IC7300 set mode FM

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 41eb2b076c370571f9a2c27553aaa45ecc55b034
      https://github.com/Hamlib/Hamlib/commit/41eb2b076c370571f9a2c27553aaa45ecc55b034
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-13 (Sun, 13 Oct 2024)

  Changed paths:
    M NEWS
    M rigs/icom/ic7300.c
    M rigs/icom/icom.c
    M rigs/icom/icom.h

  Log Message:
  -----------
  Fix IC7300 set mode FM
Allow IC7300 to use width of 1,2,3 to select filter


  Commit: c015c3690b7784cd1a17e624ed2c813f8038dc2c
      https://github.com/Hamlib/Hamlib/commit/c015c3690b7784cd1a17e624ed2c813f8038dc2c
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-13 (Sun, 13 Oct 2024)

  Changed paths:
    M doc/man1/rigctl.1

  Log Message:
  -----------
  Update rigctl.1 for IC7300 filter 1,2,3 usage


Compare: https://github.com/Hamlib/Hamlib/compare/327517a881c1...c015c3690b77

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

[Hamlib-developer] rigctld remote exploitation without an open port

[Matt P. <mh...@mi...>]

I'm following the Hamlib Security Policy on GitHub to report this
here. It has my iffy attempt at a patch, and some discussion of the
security problem (which might be non-obvious).

The rigctld man page says "DO NOT leave this TCP port open wide to the
Internet." However, even if there's no connectivity on port 4532 from
the Internet to the computer running rigctld, there's still a risk if
that computer is ever used for web browsing (even with the latest
version of Chrome). An external https web page can use the JavaScript
fetch API to connect to TCP port 4532 on 127.0.0.1, and send a rigctl
command, e.g., a URL ending with /F_28074000 will change the frequency
to 28.074. At least for me, it's 100% reproducible.

It's possible to change rigctld to block this. Although the likelihood
of exploitation may be small, the impact may be catastrophic in some
cases. First, there might be a remote compromise of the computer. As
far as I can tell, the rigctl parser isn't yet robust enough for
arbitrary command input originating from untrusted websites, e.g., the
various unbounded fscanf calls. Second, there may be effects on the
station. The frequency might be surreptitiously moved to one not
allowed by a license, or with a transmitter/antenna mismatch that
damages equipment or conceivably starts a fire. Even if the station
was carefully designed, it still may be possible for rigctld to make
changes more quickly than the operator can react.

For example:
  - Someone compromises a DXpedition website during the expedition, when
    it has many visitors per hour (happened about 6 weeks ago, for example).

  - They insert JavaScript code that automatically causes every visitor's
    web browser to try to send unwanted rigctl commands to 127.0.0.1 port
    4532 (perhaps hasn't happened yet, but is easy, and only a few
    less-used web browsers defend against this).

  - A small percentage of visitors are running rigctld and would face
    either inconvenience or a significant station problem.

I don't know the best way to change rigctld, but I worked with three ideas:
  - It's only necessary to block exactly the type of network traffic that can
    be sent by web browsers, and this is very constrained.

  - The rigctl parser consumes the input stream, often a character at a time,
    and this might make it difficult to apply a set of rules about good input
    versus bad, or to make the changes in rigctld.c instead of the parser.

  - Because exploitation attempts would be uncommon, and avoidable by moving
    off the malicious website, it may be acceptable to shut down rigctld and
    warn the user (i.e., not bother to leave the good input uninterrupted).

(I realize that browsers can't send raw spaces in a URL such as
"F 28074000" and this may have led to a different solution approach if
rigctld doesn't need to support F_28074000 as well.)

(Some web browsers have Private Network Access that solves a different
problem with remote connections to 127.0.0.1, but this doesn't help
rigctld, which executes rigctl commands found in an OPTIONS request.)

More specifically, the approach below tries to:
  - Find the beginning of the browser-sent data (such as "GET /") by looking
    for only two characters (such as "GE"). This helps to ensure the problem
    is detected before rigctld can process the current rigctl command.

  - Recognize that the "/" in "GET /" will always be detected by the parser
    as an invalid command. Detecting at that point is not always soon enough
    to prevent rigctld from processing the current rigctl command.

  - Only disrupt traffic from web browsers to rigctld, and not interfere with
    any other possible integration (nc commands, etc.).

  - Offer a way to turn off this feature if it breaks someone's use case.

  - Also limit string fscanf calls to 30 or 511 characters (not unbounded).

ampctld and rotctld could be updated analogously.

There are much cleaner approaches but they may need deeper code changes.

--- rigctl_parse.c.old	2024-10-13 02:29:04.929230005 +0000
+++ rigctl_parse.c	2024-10-13 02:59:54.250525125 +0000
@@ -82,6 +82,7 @@
 #define STR(S) STR1(S)
 
 #define MAXNAMSIZ 32
+#define MAXFSCANFSIZ 30
 #define MAXNBOPT 100    /* max number of different options */
 #define MAXARGSZ 511
 
@@ -568,7 +569,14 @@
         *(char *)p = 0;
 
 
-        ret = fscanf(fin, format, p);
+        if (!strcmp(format, "%s"))
+        {
+            ret = fscanf(fin, "%" STR(MAXARGSZ) "s", (char *) p);
+        }
+        else
+        {
+            ret = fscanf(fin, format, p);
+        }
 
         if (ret < 0)
         {
@@ -819,7 +827,8 @@
                         return (RIGCTL_PARSE_ERROR);
                     }
 
-                    retcode = fscanf(fin, "%s", ++pcmd);
+                    ++pcmd;
+                    retcode = fscanf(fin, "%" STR(MAXFSCANFSIZ) "s", pcmd);
 
                     if (retcode == 0) { rig_debug(RIG_DEBUG_WARN, "%s: unable to scan %c\n", __func__, *(pcmd - 1)); }
 
@@ -915,6 +924,22 @@
 
         if (!cmd_entry)
         {
+            if (cmd == '/')
+            {
+                if (!getenv("HAMLIB_IGNORE_CTLD_HTTP"))
+                {
+                    fprintf(stderr, "A '/' command, which is not valid in Hamlib, was detected. If this\n");
+                    fprintf(stderr, "occurred during use of any 'ctld' application (ampctld, rigctld, or\n");
+                    fprintf(stderr, "rotctld), it may mean that a Hamlib request was sent by a website,\n");
+                    fprintf(stderr, "presenting a security risk to your computer and station. If that is not\n");
+                    fprintf(stderr, "applicable, or if you intentionally use a web browser to access ctld\n");
+                    fprintf(stderr, "applications, then you can restart any Hamlib application after setting\n");
+                    fprintf(stderr, "the HAMLIB_IGNORE_CTLD_HTTP environment variable. It can be safer\n");
+                    fprintf(stderr, "not to run a web browser (that allows Hamlib requests to be embedded in\n");
+                    fprintf(stderr, "external websites) on the same computer as any ctld application.\n");
+                    exit(1);
+                }
+            }
             if (cmd != ' ')
             {
                 fprintf(stderr, "Command '%c' not found!\n", cmd);
@@ -1035,6 +1060,39 @@
                 arg1[0] = fgetc(fin);
                 arg1[1] = 0;
 
+                if (!getenv("HAMLIB_IGNORE_CTLD_HTTP"))
+                {
+                    char start_of_http_method[3];
+
+                    start_of_http_method[0] = cmd;
+                    start_of_http_method[1] = arg1[0];
+                    start_of_http_method[2] = '\0';
+                    /* Modern web browsers can only use the GET, HEAD, OPTIONS, and POST methods
+                     * unless the web server sends an Access-Control-Allow-Methods HTTP response
+                     * header (the Hamlib 'ctld' programs are not web servers and, of course,
+                     * do not send that header). If HTTP traffic is sent, then the first two
+                     * letters of the method name are available at this point in Hamlib's parsing.
+                     */
+                    if (!strcmp(start_of_http_method, "GE") ||
+                       !strcmp(start_of_http_method, "HE") ||
+                       !strcmp(start_of_http_method, "OP") ||
+                       !strcmp(start_of_http_method, "PO"))
+                    {
+                        fprintf(stderr, "The '%s' command, which is not valid in Hamlib, was detected. If this\n",
+                           start_of_http_method);
+                        fprintf(stderr, "occurred during use of any 'ctld' application (ampctld, rigctld, or\n");
+                        fprintf(stderr, "rotctld), it may mean that a Hamlib request was sent by a website,\n");
+                        fprintf(stderr, "presenting a security risk to your computer and station. If that is not\n");
+                        fprintf(stderr, "applicable, or if you intentionally use a web browser to access ctld\n");
+                        fprintf(stderr, "applications, then you can restart any Hamlib application after setting\n");
+                        fprintf(stderr, "the HAMLIB_IGNORE_CTLD_HTTP environment variable. It can be safer\n");
+                        fprintf(stderr, "not to run a web browser (that allows Hamlib requests to be embedded in\n");
+                        fprintf(stderr, "external websites) on the same computer as any ctld application.\n");
+                        exit(1);
+                    }
+                }
+                
+
                 if (debugflow) { rig_debug(RIG_DEBUG_TRACE, "%s: debug4 arg1=%c\n", __func__, arg1[0]); }
 
                 if (prompt && arg1[0] == 0x0a)
@@ -4037,7 +4095,7 @@
     const chan_t *chan_list;
     channel_t chan;
     int status;
-    char s[16];
+    char s[MAXARGSZ + 1];
 
     ENTERFUNC2;
 
Matt, KA1R

[Hamlib-developer] [Hamlib/Hamlib] 327517: Remote get_ts from ic707.c -- rig does not support it

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 327517a881c127ee91d3dbd7882aa65a8fe62085
      https://github.com/Hamlib/Hamlib/commit/327517a881c127ee91d3dbd7882aa65a8fe62085
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-10 (Thu, 10 Oct 2024)

  Changed paths:
    M rigs/icom/ic707.c

  Log Message:
  -----------
  Remote get_ts from ic707.c -- rig does not support it
https://github.com/Hamlib/Hamlib/issues/1617



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

[Hamlib-developer] Fwd: Icom IC7300 does not set FM

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

OK, List does not like attached zip files, I suppose. Trying without zip 
and modified debug log.



-------- Välitetty viesti / Fwd.Msg --------
Aihe: 	Icom IC7300 does not set FM
Päiväys: 	Thu, 10 Oct 2024 10:27:17 +0300
Lähettäjä: 	Sakari Nylund <sak...@ni...>
Vastausosoite: 	sak...@ni...
Vastaanottaja: 	ham...@li...



Hi!

IC7300 does not set FM mode. All other modes are setting ok. Get_mode 
works also ok.

[saku@hamtpad ~]$ telnet localhost 4532
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
M currVFO FM 2400
RPRT 0
m currVFO
USB
2400

Debug attached.

-- 
Saku
OH1KH

Re: [Hamlib-developer] Ham lib not communicating with Yaesu FT991-A

[Black M. <mdb...@ya...>]

Sounds like the firewall may be blocking it.If you'd like contact me off-group and we can connect up and see what's wrong.
Mike W9MDB

 

    On Wednesday, October 9, 2024 at 08:33:23 AM CDT, Edward Koll <eey...@gm...> wrote:  
 
 Over the weekend I tried switching from OmniRig to Hamlib. I followed the instructions from https://www.drgerg.com/hamlib-et-al.html#hamlib

I have a Yaesu FT-991A. 
COM4 was previously working with OmniRig. I uninstalled the Silicon Labs drivers and started the process of installing and configuring HAMLIB. I can see rigctld working in the TCPView utility. 



Hamlib will not connect to rigctld. When I launch WSJT-X I get the following error when I click the Test CAT button: 



Would appreciate any assistance or troubleshooting you could provide. 
Thanks! 
73,Ed KollK0LLE_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer
  

[Hamlib-developer] [Hamlib/Hamlib] e09642: rigctld show-conf now exits only if no -r argument...

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: e096426ddc8210f298571ad943159f2b3844ddef
      https://github.com/Hamlib/Hamlib/commit/e096426ddc8210f298571ad943159f2b3844ddef
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-09 (Wed, 09 Oct 2024)

  Changed paths:
    M tests/rigctld.c

  Log Message:
  -----------
  rigctld show-conf now exits only if no -r argument is given
https://github.com/Hamlib/Hamlib/issues/1619



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

[Hamlib-developer] [Hamlib/Hamlib] c01e55: Change icom_scan to use vfo argument to set vfo --...

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: c01e55b09b164587f8b7ddfa8d910f39ec60b0ed
      https://github.com/Hamlib/Hamlib/commit/c01e55b09b164587f8b7ddfa8d910f39ec60b0ed
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-09 (Wed, 09 Oct 2024)

  Changed paths:
    M rigs/icom/icom.c

  Log Message:
  -----------
  Change icom_scan to use vfo argument to set vfo -- default VFO_CURR to just switching to vfo mode
https://github.com/Hamlib/Hamlib/issues/1619#issuecomment-2402159608



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

[Hamlib-developer] [Hamlib/Hamlib] 2a7d53: Change icom_scan VFO to just switch to VFO mode in...

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 2a7d5387ee1b4e0e8c8ca5d0bb19d76f7a95d335
      https://github.com/Hamlib/Hamlib/commit/2a7d5387ee1b4e0e8c8ca5d0bb19d76f7a95d335
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-09 (Wed, 09 Oct 2024)

  Changed paths:
    M rigs/icom/icom.c
    M rigs/icom/icom.h

  Log Message:
  -----------
  Change icom_scan VFO to just switch to VFO mode instead of VFOA
https://github.com/Hamlib/Hamlib/issues/1619#issuecomment-2402159608



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

[Hamlib-developer] [Hamlib/Hamlib] 882d22: Add help to N command in rigctl

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 882d22a50ca99f4a2600620844ca4ffb216400fc
      https://github.com/Hamlib/Hamlib/commit/882d22a50ca99f4a2600620844ca4ffb216400fc
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-07 (Mon, 07 Oct 2024)

  Changed paths:
    M src/sprintflst.c
    M src/sprintflst.h
    M tests/rigctl_parse.c

  Log Message:
  -----------
  Add help to N command in rigctl



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

[Hamlib-developer] [Hamlib/Hamlib] 96fc68: Update rigctl.1

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 96fc6855671e046f95da1b9f7b5a765de0b607aa
      https://github.com/Hamlib/Hamlib/commit/96fc6855671e046f95da1b9f7b5a765de0b607aa
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-07 (Mon, 07 Oct 2024)

  Changed paths:
    M doc/man1/rigctl.1

  Log Message:
  -----------
  Update rigctl.1



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

[Hamlib-developer] [Hamlib/Hamlib] ba62ed: Fix simic7300

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: ba62edc51b9b2d390b1c051562c34b06dda909bf
      https://github.com/Hamlib/Hamlib/commit/ba62edc51b9b2d390b1c051562c34b06dda909bf
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-07 (Mon, 07 Oct 2024)

  Changed paths:
    M simulators/simic7300.c

  Log Message:
  -----------
  Fix simic7300


  Commit: baf2897e76b367325a1a2085df7bf4b0459fd862
      https://github.com/Hamlib/Hamlib/commit/baf2897e76b367325a1a2085df7bf4b0459fd862
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-07 (Mon, 07 Oct 2024)

  Changed paths:
    M rigs/icom/ic707.c
    M rigs/icom/icom.c
    M rigs/icom/icom.h

  Log Message:
  -----------
  Add SCAN_VFO to icom.c and fix ic707.c to support correct scan modes


Compare: https://github.com/Hamlib/Hamlib/compare/53a3d8635373...baf2897e76b3

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

[Hamlib-developer] Ham lib not communicating with Yaesu FT991-A

[Edward K. <eey...@gm...>]

Over the weekend I tried switching from OmniRig to Hamlib. I followed the
instructions from
https://www.drgerg.com/hamlib-et-al.html#hamlib

I have a Yaesu FT-991A.

COM4 was previously working with OmniRig. I uninstalled the Silicon Labs
drivers and started the process of installing and configuring HAMLIB.
I can see rigctld working in the TCPView utility.

[image: image.png]

Hamlib will not connect to rigctld. When I launch WSJT-X I get the
following error when I click the Test CAT button:

[image: image.png]

Would appreciate any assistance or troubleshooting you could provide.

Thanks!

73,
Ed Koll
K0LLE

[Hamlib-developer] [Hamlib/Hamlib] 53a3d8: Fix async detection in icom.c

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

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 53a3d8635373124b9b6b93c141673f2ea1c6c814
      https://github.com/Hamlib/Hamlib/commit/53a3d8635373124b9b6b93c141673f2ea1c6c814
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2024-10-05 (Sat, 05 Oct 2024)

  Changed paths:
    M rigs/icom/icom.c
    M rigs/icom/icom.h

  Log Message:
  -----------
  Fix async detection in icom.c



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