hamlib-developer Mailing List for Ham Radio Control Libraries (Page 11)
Library to control radio transceivers and receivers
Brought to you by:
n0nb
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(24) |
Oct
(16) |
Nov
(8) |
Dec
(9) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(49) |
Feb
(17) |
Mar
(3) |
Apr
(7) |
May
(3) |
Jun
(1) |
Jul
(2) |
Aug
(8) |
Sep
(18) |
Oct
(15) |
Nov
(15) |
Dec
(26) |
2002 |
Jan
(46) |
Feb
(14) |
Mar
(44) |
Apr
(3) |
May
(6) |
Jun
(47) |
Jul
(40) |
Aug
(14) |
Sep
(59) |
Oct
(39) |
Nov
(58) |
Dec
(76) |
2003 |
Jan
(82) |
Feb
(66) |
Mar
(37) |
Apr
(56) |
May
(34) |
Jun
(19) |
Jul
(23) |
Aug
(55) |
Sep
(31) |
Oct
(40) |
Nov
(21) |
Dec
(60) |
2004 |
Jan
(57) |
Feb
(110) |
Mar
(41) |
Apr
(17) |
May
(18) |
Jun
(19) |
Jul
(18) |
Aug
(5) |
Sep
(31) |
Oct
(16) |
Nov
(26) |
Dec
(36) |
2005 |
Jan
(69) |
Feb
(26) |
Mar
(62) |
Apr
(120) |
May
(31) |
Jun
(47) |
Jul
(7) |
Aug
(27) |
Sep
(4) |
Oct
(9) |
Nov
(26) |
Dec
(21) |
2006 |
Jan
(13) |
Feb
(26) |
Mar
(38) |
Apr
(31) |
May
(17) |
Jun
(6) |
Jul
(23) |
Aug
(6) |
Sep
(38) |
Oct
(87) |
Nov
(49) |
Dec
(49) |
2007 |
Jan
(52) |
Feb
(19) |
Mar
(20) |
Apr
(5) |
May
(25) |
Jun
(15) |
Jul
(49) |
Aug
(43) |
Sep
(21) |
Oct
(21) |
Nov
(27) |
Dec
(10) |
2008 |
Jan
(23) |
Feb
(20) |
Mar
(25) |
Apr
(39) |
May
(36) |
Jun
(17) |
Jul
(10) |
Aug
(18) |
Sep
(44) |
Oct
(88) |
Nov
(60) |
Dec
(65) |
2009 |
Jan
(99) |
Feb
(91) |
Mar
(49) |
Apr
(34) |
May
(52) |
Jun
(9) |
Jul
(11) |
Aug
(4) |
Sep
(41) |
Oct
(16) |
Nov
(51) |
Dec
(71) |
2010 |
Jan
(43) |
Feb
(79) |
Mar
(59) |
Apr
(55) |
May
(51) |
Jun
(38) |
Jul
(38) |
Aug
(61) |
Sep
(53) |
Oct
(46) |
Nov
(43) |
Dec
(41) |
2011 |
Jan
(74) |
Feb
(96) |
Mar
(41) |
Apr
(42) |
May
(61) |
Jun
(66) |
Jul
(50) |
Aug
(40) |
Sep
(11) |
Oct
(30) |
Nov
(21) |
Dec
(45) |
2012 |
Jan
(59) |
Feb
(4) |
Mar
(52) |
Apr
(19) |
May
(62) |
Jun
(46) |
Jul
(61) |
Aug
(18) |
Sep
(21) |
Oct
(25) |
Nov
(66) |
Dec
(41) |
2013 |
Jan
(36) |
Feb
(64) |
Mar
(37) |
Apr
(24) |
May
(74) |
Jun
(40) |
Jul
(43) |
Aug
(34) |
Sep
(65) |
Oct
(52) |
Nov
(23) |
Dec
(20) |
2014 |
Jan
(18) |
Feb
(29) |
Mar
(13) |
Apr
(41) |
May
(10) |
Jun
(12) |
Jul
(16) |
Aug
(25) |
Sep
(20) |
Oct
(56) |
Nov
(43) |
Dec
(61) |
2015 |
Jan
(36) |
Feb
(38) |
Mar
(92) |
Apr
(42) |
May
(13) |
Jun
(19) |
Jul
(18) |
Aug
(22) |
Sep
(21) |
Oct
(2) |
Nov
(49) |
Dec
(22) |
2016 |
Jan
(55) |
Feb
(144) |
Mar
(40) |
Apr
(98) |
May
(61) |
Jun
(36) |
Jul
(16) |
Aug
(33) |
Sep
(59) |
Oct
(16) |
Nov
(37) |
Dec
(32) |
2017 |
Jan
(70) |
Feb
(71) |
Mar
(14) |
Apr
(43) |
May
(31) |
Jun
(24) |
Jul
(38) |
Aug
(54) |
Sep
(24) |
Oct
(15) |
Nov
(26) |
Dec
(27) |
2018 |
Jan
(22) |
Feb
(24) |
Mar
(109) |
Apr
(12) |
May
(46) |
Jun
(23) |
Jul
(39) |
Aug
(34) |
Sep
(22) |
Oct
(43) |
Nov
(26) |
Dec
(157) |
2019 |
Jan
(102) |
Feb
(51) |
Mar
(63) |
Apr
(60) |
May
(91) |
Jun
(55) |
Jul
(27) |
Aug
(76) |
Sep
(52) |
Oct
(95) |
Nov
(67) |
Dec
(204) |
2020 |
Jan
(311) |
Feb
(148) |
Mar
(230) |
Apr
(122) |
May
(204) |
Jun
(204) |
Jul
(114) |
Aug
(36) |
Sep
(120) |
Oct
(186) |
Nov
(60) |
Dec
(151) |
2021 |
Jan
(182) |
Feb
(171) |
Mar
(202) |
Apr
(153) |
May
(110) |
Jun
(50) |
Jul
(58) |
Aug
(142) |
Sep
(112) |
Oct
(120) |
Nov
(97) |
Dec
(125) |
2022 |
Jan
(175) |
Feb
(147) |
Mar
(54) |
Apr
(73) |
May
(127) |
Jun
(95) |
Jul
(88) |
Aug
(85) |
Sep
(38) |
Oct
(40) |
Nov
(116) |
Dec
(159) |
2023 |
Jan
(175) |
Feb
(55) |
Mar
(83) |
Apr
(70) |
May
(165) |
Jun
(79) |
Jul
(123) |
Aug
(90) |
Sep
(40) |
Oct
(95) |
Nov
(84) |
Dec
(88) |
2024 |
Jan
(105) |
Feb
(60) |
Mar
(52) |
Apr
(43) |
May
(56) |
Jun
(59) |
Jul
(53) |
Aug
(47) |
Sep
(62) |
Oct
(36) |
Nov
(45) |
Dec
(100) |
2025 |
Jan
(52) |
Feb
(45) |
Mar
(30) |
Apr
(97) |
May
(72) |
Jun
(83) |
Jul
(124) |
Aug
(83) |
Sep
(84) |
Oct
|
Nov
|
Dec
|
From: Nate B. <n0...@n0...> - 2025-07-18 16:01:28
|
* On 2025 14 Jul 08:29 -0500, Adrian wrote: > Nate, However I also have this from Reino after the previous; Still, the output from: rigctl -m 1001 -vvvvv would help us immensely. Looking at the history of ft847.c there are seven commits since the release of 4.5.5 and 4.6.0. It appears there are two made by Mike a couple of weeks after 4.5.5's release that may be the culprits here: https://github.com/Hamlib/Hamlib/commit/1f98f0d34770fd94aabc58100295bb1b525402fc This one links to GitHub issue 1286: https://github.com/Hamlib/Hamlib/issues/1286#issuecomment-1545971701 https://github.com/Hamlib/Hamlib/commit/1f98f0d34770fd94aabc58100295bb1b525402fc which also links to GitHub issue 1286. I don't have this radio to test. There may be a real problem if there is a serial number break that requires this "fixed" code to work properly. We have the situation where one that worked now doesn't and where that didn't now apparently does. If Reino can run the command above and get the output to the list, we can likely get this fixed but it may be more difficult as we may need to get the reporter of GitHub issue 1286 involved as well. 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 |
From: Nate B. <n0...@n0...> - 2025-07-18 16:01:17
|
It so happened that I looked and see that today, 18 July, is Hamlib's official birthday. Frank Singleton made the first commit on 2000-07-18 at 20:55 +0000. The project has certainly evolved over that time and continues to grow and change as needs and practices dictate. My thanks to all contributors and testers. This project only continues because of your interest and effort. Thank you! BTW, this project is of, by, and for radio hobbyists and even amateur astronomers who find it useful. Here's to many more years of Hamlib development. 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 |
From: George B. <geo...@gm...> - 2025-07-18 15:25:16
|
> I'm not sure if they were present on Day One from Frank or added later > by Stephane. The complete commit history has been preserved from the > very first commit 25 years ago today! You can browse it. Wow! Happy Birthday, Hamlib! |
From: Nate B. <n0...@n0...> - 2025-07-18 11:57:05
|
* On 2025 17 Jul 13:25 -0500, Stefan Jansen wrote: > Hi George, > > Thanks for your reply. Well, I understand the concept of extra > functions/levels/parameters in general and I see that it is a great > possibility to access additional controls of a rig. > > My question was more related especially to the CHECKBUTTON levels. As > the type CHECKBUTTON suggests to me, these levels are more like > something you turn on and off. So I was asking myself why CHECKBUTTON > levels should not better be modeled as extra functions. Functions also > have an on/off mental model behind. > > And maybe as an additional question: What is the conceptual idea > bhindd parameters? What makes them different from levels and why > weren’t they just built into hamlib as levels? As George notes, these are historical. I'm not sure if they were present on Day One from Frank or added later by Stephane. The complete commit history has been preserved from the very first commit 25 years ago today! You can browse it. There are also the mailing list archives via GMANE as noted at https://hamlib.github.io/#mailing-list The SourceForge archives aren't the easiest to navigate, IMO, but exist at https://sourceforge.net/p/hamlib/mailman/hamlib-developer/ 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 |
From: George B. <geo...@gm...> - 2025-07-17 19:01:18
|
Hello, Stefan On 7/17/25 2:24 PM, Stefan Jansen wrote: > Hi George, > > Thanks for your reply. Well, I understand the concept of extra > functions/levels/parameters in general and I see that it is a great > possibility to access additional controls of a rig. > > My question was more related especially to the CHECKBUTTON levels. As > the type CHECKBUTTON suggests to me, these levels are more like > something you turn on and off. So I was asking myself why CHECKBUTTON > levels should not better be modeled as extra functions. Functions also > have an on/off mental model behind. > > And maybe as an additional question: What is the conceptual idea > bhindd parameters? What makes them different from levels and why > weren’t they just built into hamlib as levels? > > That question I can't answer; they were in Hamlib long before I even knew it existed. If I had to guess, the answer would be flexibility again. If a backend is setting only off/on values, it can model everything as a function. If it is setting levels, it can model an oddball on/off value as a CHECKBOX level. Remember, these operations are for tweaking unique features - they need as much wiggle room as the manufacturers have in designing them. 73 n3gb > Vy 73 de Stefan, DK7STJ > > -- > Stefan Jansen *** E-Mail: DK...@da... > >> Am 16.07.2025 um 03:34 schrieb George Baltz <geo...@gm...>: >> >> Why? Flexibility. The dummy rig has examples of the types of >> controls that can be implemented by any backend(i.e., the rig handler >> itself) for whatever reason it may have. Those extra >> controls/functions/levels are meant to be as general as possible so >> any type of data can be passed, for whatever needs that may arise. >> They may be unique to a single model, or to a set of models, but they >> are not generally available. >> >> 73 >> >> n3gb >> >> On 7/15/25 5:10 PM, Stefan Jansen wrote: >>> Hi dear hamlib project team, >>> >>> When reviewing the output of —dump-caps of some rigs, also the dummy >>> rig has this, I saw that there are sometimes extra levels of type >>> CHECKBUTTON. Thosr can, as far as I understand, have just values 0 >>> and 1. >>> >>> If the above is true, then I do not understand why someone would >>> implement such a 0-1-level, as there are already extra functions >>> that have exactly that states, namely 0 or 1, off and on. >>> >>> Could you please explain the idea behind having those kind of >>> CHECKBUTTON extra levels and not implementing them just as extra >>> functions? >>> >>> >>> Vy 73 de Stefan, DK7STJ >>> >>> -- >>> Stefan Jansen *** E-Mail: DK...@da... >>> >>> >>> >>> _______________________________________________ >>> 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 > |
From: Stefan J. <DK...@da...> - 2025-07-17 18:24:32
|
Hi George, Thanks for your reply. Well, I understand the concept of extra functions/levels/parameters in general and I see that it is a great possibility to access additional controls of a rig. My question was more related especially to the CHECKBUTTON levels. As the type CHECKBUTTON suggests to me, these levels are more like something you turn on and off. So I was asking myself why CHECKBUTTON levels should not better be modeled as extra functions. Functions also have an on/off mental model behind. And maybe as an additional question: What is the conceptual idea bhindd parameters? What makes them different from levels and why weren’t they just built into hamlib as levels? Vy 73 de Stefan, DK7STJ -- Stefan Jansen *** E-Mail: DK...@da... > Am 16.07.2025 um 03:34 schrieb George Baltz <geo...@gm...>: > > Why? Flexibility. The dummy rig has examples of the types of controls that can be implemented by any backend(i.e., the rig handler itself) for whatever reason it may have. Those extra controls/functions/levels are meant to be as general as possible so any type of data can be passed, for whatever needs that may arise. They may be unique to a single model, or to a set of models, but they are not generally available. > > 73 > > n3gb > > On 7/15/25 5:10 PM, Stefan Jansen wrote: >> Hi dear hamlib project team, >> >> When reviewing the output of —dump-caps of some rigs, also the dummy rig has this, I saw that there are sometimes extra levels of type CHECKBUTTON. Thosr can, as far as I understand, have just values 0 and 1. >> >> If the above is true, then I do not understand why someone would implement such a 0-1-level, as there are already extra functions that have exactly that states, namely 0 or 1, off and on. >> >> Could you please explain the idea behind having those kind of CHECKBUTTON extra levels and not implementing them just as extra functions? >> >> >> Vy 73 de Stefan, DK7STJ >> >> -- >> Stefan Jansen *** E-Mail: DK...@da... >> >> >> >> _______________________________________________ >> 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 |
From: George B. <geo...@gm...> - 2025-07-16 01:34:38
|
Why? Flexibility. The dummy rig has examples of the types of controls that can be implemented by any backend(i.e., the rig handler itself) for whatever reason it may have. Those extra controls/functions/levels are meant to be as general as possible so any type of data can be passed, for whatever needs that may arise. They may be unique to a single model, or to a set of models, but they are not generally available. 73 n3gb On 7/15/25 5:10 PM, Stefan Jansen wrote: > Hi dear hamlib project team, > > When reviewing the output of —dump-caps of some rigs, also the dummy rig has this, I saw that there are sometimes extra levels of type CHECKBUTTON. Thosr can, as far as I understand, have just values 0 and 1. > > If the above is true, then I do not understand why someone would implement such a 0-1-level, as there are already extra functions that have exactly that states, namely 0 or 1, off and on. > > Could you please explain the idea behind having those kind of CHECKBUTTON extra levels and not implementing them just as extra functions? > > > Vy 73 de Stefan, DK7STJ > > -- > Stefan Jansen *** E-Mail: DK...@da... > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
From: Stefan J. <DK...@da...> - 2025-07-15 21:10:53
|
Hi dear hamlib project team, When reviewing the output of —dump-caps of some rigs, also the dummy rig has this, I saw that there are sometimes extra levels of type CHECKBUTTON. Thosr can, as far as I understand, have just values 0 and 1. If the above is true, then I do not understand why someone would implement such a 0-1-level, as there are already extra functions that have exactly that states, namely 0 or 1, off and on. Could you please explain the idea behind having those kind of CHECKBUTTON extra levels and not implementing them just as extra functions? Vy 73 de Stefan, DK7STJ -- Stefan Jansen *** E-Mail: DK...@da... |
From: Michael M. <no...@gi...> - 2025-07-15 19:28:59
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 5c06f66aa831c586bf4504007289675cb5e148ff https://github.com/Hamlib/Hamlib/commit/5c06f66aa831c586bf4504007289675cb5e148ff Author: Michael Morgan <844...@us...> Date: 2025-07-15 (Tue, 15 Jul 2025) Changed paths: M rotators/gs232a/gs232.c Log Message: ----------- Update gs232.c I don't use that so I added a line to void it to suppress the warning. Hope that is ok. To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Adrian <vk...@gm...> - 2025-07-14 13:29:00
|
Nate, However I also have this from Reino after the previous; _ Reino Talarmo_<https://wsjtx.groups.io/g/main/topic/oob_and_frequency_shifted_on/113834442?page=2#> Jul 11#56511 // <https://wsjtx.groups.io/g/main/message/56511> I answer myself: a bit more information about the system, where the hamlib to version 4.5.5.5 is working, but Hamlib Version 4.6.1 is generating the OOB after some time. Setup consists of a Yaesu FT-847 and a Mag Loop Controller by TF3LJ / VE2LJX using USB serial CAT with CAT pass-through. OS either Windows 10 or 11 and WSJT-X v2.7.0 as far as I know. 73 vk4tux On 14/7/25 22:17, Nate Bargmann wrote: > * On 2025 07 Jul 05:35 -0500, Adrian wrote: >> Developers, FYI concerning an issue with FT-847 selection in wsjtx, which is >> problematic, vs fine operation in MSHV, which does not use hamlib. > So far no one has shown a bug we can fix. I'll hold off on 4.6.4 one > more day and if no reply I am going to release it. > > 73, Nate > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
From: Nate B. <n0...@n0...> - 2025-07-14 13:15:46
|
* On 2025 07 Jul 05:35 -0500, Adrian wrote: > Developers, FYI concerning an issue with FT-847 selection in wsjtx, which is > problematic, vs fine operation in MSHV, which does not use hamlib. So far no one has shown a bug we can fix. I'll hold off on 4.6.4 one more day and if no reply I am going to release it. 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 |
From: Nate B. <no...@gi...> - 2025-07-14 12:22:17
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 02179e0a93d7eeea9214ed7dcbdb52d7e94364d3 https://github.com/Hamlib/Hamlib/commit/02179e0a93d7eeea9214ed7dcbdb52d7e94364d3 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-10 (Thu, 10 Jul 2025) Changed paths: M include/Makefile.am A include/hamlib/amp_state.h A include/hamlib/port.h A include/hamlib/rig_state.h A include/hamlib/rot_state.h Log Message: ----------- Basic infrastructure for moving internal structures out of rig.h Create breakout files, add them to Makefile.am manifest. Commit: 0148378ed9adb70c9342542e11c0bb03370298e5 https://github.com/Hamlib/Hamlib/commit/0148378ed9adb70c9342542e11c0bb03370298e5 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-10 (Thu, 10 Jul 2025) Changed paths: M src/amp_conf.c M src/amp_settings.c M src/amplifier.c M src/cache.c M src/conf.c M src/event.c M src/mem.c M src/misc.c M src/multicast.c M src/network.c M src/rig.c M src/rot_conf.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/tones.c Log Message: ----------- Add needed new includes in src/*.c Commit: 1efaacb5ab5a8856fe56ad0cc197504906beebd9 https://github.com/Hamlib/Hamlib/commit/1efaacb5ab5a8856fe56ad0cc197504906beebd9 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-10 (Thu, 10 Jul 2025) Changed paths: M include/hamlib/port.h M include/hamlib/rig.h M tests/example.c Log Message: ----------- Move port definition(s) to include/hamlib/port.h Add some ghost structs and typedefs Make example.c compile on gcc15 and with new includes Commit: f03fefe1cd1028310bb63d482e538808ddd40938 https://github.com/Hamlib/Hamlib/commit/f03fefe1cd1028310bb63d482e538808ddd40938 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-10 (Thu, 10 Jul 2025) Changed paths: M include/hamlib/rig.h M include/hamlib/rig_state.h Log Message: ----------- Move rig_state definition(s) from rig.h to include/hamlib/rig_state.h Compiling with NO_OLD_INCLUDES still won't work until the state structure(s) are moved out of rig_struct, but at least I get the right compiler errors. Commit: cc4b1ce7db096309d36f0381d93152f35901e8f0 https://github.com/Hamlib/Hamlib/commit/cc4b1ce7db096309d36f0381d93152f35901e8f0 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-10 (Thu, 10 Jul 2025) Changed paths: M include/hamlib/amp_state.h M include/hamlib/amplifier.h M include/hamlib/rig.h Log Message: ----------- Move amp_state definition to include/hamlib/amp_state.h Commit: 9991f46e58b937e6034f26245d6d1ab60cb7eff5 https://github.com/Hamlib/Hamlib/commit/9991f46e58b937e6034f26245d6d1ab60cb7eff5 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-10 (Thu, 10 Jul 2025) Changed paths: M include/hamlib/rig.h M include/hamlib/rot_state.h M include/hamlib/rotator.h Log Message: ----------- Move rotator state definition to include/hamlib/rot_state.h Commit: 213e7751bf751d69111fe6bdc722f9ec73a93a71 https://github.com/Hamlib/Hamlib/commit/213e7751bf751d69111fe6bdc722f9ec73a93a71 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-10 (Thu, 10 Jul 2025) Changed paths: M rotators/amsat/if100.c M rotators/androidsensor/androidsensor.cpp M rotators/apex/apex.c M rotators/apex/sharedloop.c M rotators/ars/ars.c M rotators/celestron/celestron.c M rotators/easycomm/easycomm.c M rotators/ether6/ether6.c M rotators/flir/flir.c M rotators/fodtrack/fodtrack.c M rotators/grbltrk/grbltrk.c M rotators/gs232a/gs232.c M rotators/gs232a/gs232a.c M rotators/gs232a/gs232b.c M rotators/heathkit/hd1780.c M rotators/ioptron/rot_ioptron.c M rotators/m2/rc2800.c M rotators/meade/meade.c M rotators/prosistel/prosistel.c M rotators/radant/radant.c M rotators/rotorez/rotorez.c M rotators/saebrtrack/saebrtrack.c M rotators/sartek/sartek.c M rotators/satel/satel.c M rotators/skywatcher/skywatcher.c M rotators/spid/spid.c M rotators/ts7400/ts7400.c Log Message: ----------- Add needed includes of new files to rotators/*/* Commit: e90cc5fb0ecf2bdbf3b5468e3bad73e7546e2b12 https://github.com/Hamlib/Hamlib/commit/e90cc5fb0ecf2bdbf3b5468e3bad73e7546e2b12 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-10 (Thu, 10 Jul 2025) Changed paths: M amplifiers/elecraft/kpa.c M amplifiers/elecraft/kpa1500.c M amplifiers/expert/expert.c M amplifiers/gemini/dx1200.c M amplifiers/gemini/gemini.c Log Message: ----------- Add includes to amplifiers/*/*.c Commit: 80cfadadb0e63555dd4ace00a4b6326da86976db https://github.com/Hamlib/Hamlib/commit/80cfadadb0e63555dd4ace00a4b6326da86976db Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-10 (Thu, 10 Jul 2025) Changed paths: M include/hamlib/amp_state.h M include/hamlib/port.h M include/hamlib/rig_state.h M include/hamlib/rot_state.h Log Message: ----------- Update copyright lines Commit: f3e9a859ed22c7e5362eccb4fe93ef971ea15a02 https://github.com/Hamlib/Hamlib/commit/f3e9a859ed22c7e5362eccb4fe93ef971ea15a02 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-10 (Thu, 10 Jul 2025) Changed paths: M amplifiers/elecraft/kpa1500.c M amplifiers/gemini/dx1200.c M include/hamlib/port.h M include/hamlib/rig.h M rotators/amsat/if100.c M rotators/apex/apex.c M rotators/apex/sharedloop.c M rotators/ars/ars.c M rotators/easycomm/easycomm.c M rotators/ether6/ether6.c M rotators/fodtrack/fodtrack.c M rotators/ioptron/rot_ioptron.c M rotators/radant/radant.c M rotators/saebrtrack/saebrtrack.c M rotators/satel/satel.c M src/gpio.c M src/iofunc.c M src/network.c M src/parallel.c M src/usb_port.c Log Message: ----------- Move ???PORT() macro definitions back to rig.h Many (most?) of the uses of the port structures in Hamlib are to pass through to the basic I/O routines (rig_flush(), write_block(), read_string()), without referencing any of the structure data. Don't bother including port.h if it won't be used. The ???PORT macros are independent of actual hamlib_port_t data use. Commit: 3952f030d4e3f0c394a47b0214777ef4ed4cd266 https://github.com/Hamlib/Hamlib/commit/3952f030d4e3f0c394a47b0214777ef4ed4cd266 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-11 (Fri, 11 Jul 2025) Changed paths: M include/hamlib/amp_state.h M include/hamlib/port.h M include/hamlib/rig_state.h M include/hamlib/rot_state.h M simulators/simts890.c Log Message: ----------- More copyright updates Commit: b8c1d80626bc2cc0a8537d748aa490adff3a61bf https://github.com/Hamlib/Hamlib/commit/b8c1d80626bc2cc0a8537d748aa490adff3a61bf Author: George Baltz N3GB <Geo...@gm...> Date: 2025-07-11 (Fri, 11 Jul 2025) Changed paths: M bindings/python/test_Hamlib_class.py Log Message: ----------- Add required noise Commit: 3f7c18eb52bb2cdcbf4a1ef5abbdf73ddeae96bd https://github.com/Hamlib/Hamlib/commit/3f7c18eb52bb2cdcbf4a1ef5abbdf73ddeae96bd Author: Nate Bargmann <n0...@n0...> Date: 2025-07-14 (Mon, 14 Jul 2025) Changed paths: M amplifiers/elecraft/kpa.c M amplifiers/expert/expert.c M amplifiers/gemini/dx1200.c M amplifiers/gemini/gemini.c M bindings/python/test_Hamlib_class.py M include/Makefile.am A include/hamlib/amp_state.h M include/hamlib/amplifier.h A include/hamlib/port.h M include/hamlib/rig.h A include/hamlib/rig_state.h A include/hamlib/rot_state.h M include/hamlib/rotator.h M rotators/amsat/if100.c M rotators/androidsensor/androidsensor.cpp M rotators/ars/ars.c M rotators/celestron/celestron.c M rotators/easycomm/easycomm.c M rotators/ether6/ether6.c M rotators/flir/flir.c M rotators/fodtrack/fodtrack.c M rotators/grbltrk/grbltrk.c M rotators/gs232a/gs232.c M rotators/gs232a/gs232a.c M rotators/gs232a/gs232b.c M rotators/heathkit/hd1780.c M rotators/m2/rc2800.c M rotators/meade/meade.c M rotators/prosistel/prosistel.c M rotators/rotorez/rotorez.c M rotators/sartek/sartek.c M rotators/skywatcher/skywatcher.c M rotators/spid/spid.c M rotators/ts7400/ts7400.c M simulators/simts890.c M src/amp_conf.c M src/amp_settings.c M src/amplifier.c M src/cache.c M src/conf.c M src/event.c M src/gpio.c M src/iofunc.c M src/mem.c M src/misc.c M src/multicast.c M src/network.c M src/parallel.c M src/rig.c M src/rot_conf.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/tones.c M src/usb_port.c M tests/example.c Log Message: ----------- Merge GitHub PR #1802 Compare: https://github.com/Hamlib/Hamlib/compare/79c812ff4db8...3f7c18eb52bb To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-07-14 11:52:57
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 69d203fd1c2e209cda74a000977cc0b7464dc43a https://github.com/Hamlib/Hamlib/commit/69d203fd1c2e209cda74a000977cc0b7464dc43a Author: jeremybox <gi...@je...> Date: 2025-07-11 (Fri, 11 Jul 2025) Changed paths: M include/hamlib/riglist.h M rigs/yaesu/Makefile.am A rigs/yaesu/ftx1.c A rigs/yaesu/ftx1.h M rigs/yaesu/newcat.c M rigs/yaesu/yaesu.c M rigs/yaesu/yaesu.h Log Message: ----------- Add FTX-1 radio support to Hamlib - Add FTX-1 rig model (ID 840) to riglist.h - Create ftx1.c and ftx1.h with FTX-1 implementation - Add FTX-1 to Yaesu Makefile.am - Integrate FTX-1 into newcat.c command validation system - Update yaesu.c and yaesu.h for FTX-1 support - Based on FT-991A CAT protocol compatibility Commit: 7ce9d60aa68af334bc680a42a28ca5194d71ecde https://github.com/Hamlib/Hamlib/commit/7ce9d60aa68af334bc680a42a28ca5194d71ecde Author: Nate Bargmann <n0...@n0...> Date: 2025-07-14 (Mon, 14 Jul 2025) Changed paths: M include/hamlib/riglist.h M rigs/yaesu/Makefile.am A rigs/yaesu/ftx1.c A rigs/yaesu/ftx1.h M rigs/yaesu/newcat.c M rigs/yaesu/yaesu.c M rigs/yaesu/yaesu.h Log Message: ----------- Merge GitHub PR #1801 Commit: 79c812ff4db84d44eca7414aa4f2f5f81f7ce3e1 https://github.com/Hamlib/Hamlib/commit/79c812ff4db84d44eca7414aa4f2f5f81f7ce3e1 Author: Nate Bargmann <n0...@n0...> Date: 2025-07-14 (Mon, 14 Jul 2025) Changed paths: M NEWS Log Message: ----------- Update NEWS for FTX-1 new model support Compare: https://github.com/Hamlib/Hamlib/compare/0db57035d508...79c812ff4db8 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: George B. <geo...@gm...> - 2025-07-13 15:54:38
|
Yes, it is currently broken in hamlib-4.6.3. You can use the current daily build of Hamlib, or wait until 4.6.4 is released. See https://github.com/Hamlib/Hamlib/issues/1767 On 7/12/25 7:14 PM, Daniel Boggiano via Hamlib-developer wrote: > Hello, I am trying to use hamlib and a THD74 and a microsoft surface > computer. Bluetooth and the computer works fine with the 74 but not > when i use hamlib with the command line. Winlink and yaac work fine as > well as hamlib and fldigi. When I use hamlib from the command line it > connects bluetooth mementarilly and then quits immediately. > > I ran in -vvvv modeto get this information and am passing it to you. > If there is anything else I can do to help, please let me know. > > FYI, I am an appliance operator so you'd need to speak to me in very > simple language. > > Thank you > Danny > > > Report bugs to <ham...@li...>. > > c:\Program Files\hamlib-w64-4.6.3\bin>rigctl -m 2042 -r COM9 -vvvv > rigctl.c(532) Startup: rigctl -m 2042 -r COM9 -vvvv > rigctl Hamlib 4.6.3 2025-06-10T00:52:44Z SHA=371db9 64-bit > Report bugs to <ham...@li...> > > rig_test_2038: MSVCRT 2038 test = 0xf0000000:Mon Aug 05 05:04:00 2097 > rig_init: 2038 time test passed > rig_init: rig_model=Kenwood TH-D74 20250515.3 > rig_init: rig has VFO_A > rig_init: rig has VFO_B > kenwood_init called, version 20250515/20250515.3 > kenwood.c(899):kenwood_init returning2(0) > rig_set_conf called > rig_confparam_lookup called for rig_pathname > rig_set_conf: rig_pathname='COM9' > rig.c(970):rig_open entered > serial_open: serial port COM9 is OK > serial_open: COM9 > rig_open: 00000000027d744c rs->comm_state==1?=1 > *1:kenwood.c(921):kenwood_open entered > **2:kenwood.c(1206):kenwood_get_id entered > kenwood_transaction called cmd=ID > kenwood_transaction: Command is not correctly terminated 'ID TH-D74' > kenwood.c(713):kenwood_transaction returning2(-8) Protocol error > > **2:kenwood.c(1213):kenwood_get_id returning(-8) Protocol error > > **2:kenwood.c(1206):kenwood_get_id entered > kenwood_transaction called cmd=ID > kenwood_transaction: Command is not correctly terminated 'ID TH-D74' > kenwood.c(713):kenwood_transaction returning2(-8) Protocol error > > **2:kenwood.c(1213):kenwood_get_id returning(-8) Protocol error > > kenwood_open: no response to get_id from rig...continuing anyway > kenwood_open: cannot get identification > *1:kenwood.c(1051):kenwood_open returning(-8) Protocol error > > ser_close: restoring options > rig.c(1479):rig_open returning2(-8) Protocol error > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
From: Daniele F. <iu...@gm...> - 2025-07-13 11:57:57
|
Daniel wrote: > Hello, I am trying to use hamlib and a THD74 and a microsoft surface computer. Bluetooth and the computer works fine with the 74 > but not when i use hamlib with the command line. Winlink and yaac work fine as well as hamlib and fldigi. what are the Hamlib versions used by the software that work? I mean the version of libhamlib-4.dll that can be found from the Properties of the file in the Details page -- 73 de IU5HKX Daniele |
From: Daniel B. <kd...@ic...> - 2025-07-12 23:14:15
|
Hello, I am trying to use hamlib and a THD74 and a microsoft surface computer. Bluetooth and the computer works fine with the 74 but not when i use hamlib with the command line. Winlink and yaac work fine as well as hamlib and fldigi. When I use hamlib from the command line it connects bluetooth mementarilly and then quits immediately. I ran in -vvvv modeto get this information and am passing it to you. If there is anything else I can do to help, please let me know. FYI, I am an appliance operator so you'd need to speak to me in very simple language. Thank you Danny Report bugs to < ham...@li... >. c:\Program Files\hamlib-w64-4.6.3\bin>rigctl -m 2042 -r COM9 -vvvv rigctl.c(532) Startup: rigctl -m 2042 -r COM9 -vvvv rigctl Hamlib 4.6.3 2025-06-10T00:52:44Z SHA=371db9 64-bit Report bugs to < ham...@li... > rig_test_2038: MSVCRT 2038 test = 0xf0000000:Mon Aug 05 05:04:00 2097 rig_init: 2038 time test passed rig_init: rig_model=Kenwood TH-D74 20250515.3 rig_init: rig has VFO_A rig_init: rig has VFO_B kenwood_init called, version 20250515/20250515.3 kenwood.c(899):kenwood_init returning2(0) rig_set_conf called rig_confparam_lookup called for rig_pathname rig_set_conf: rig_pathname='COM9' rig.c(970):rig_open entered serial_open: serial port COM9 is OK serial_open: COM9 rig_open: 00000000027d744c rs->comm_state==1?=1 *1:kenwood.c(921):kenwood_open entered **2:kenwood.c(1206):kenwood_get_id entered kenwood_transaction called cmd=ID kenwood_transaction: Command is not correctly terminated 'ID TH-D74' kenwood.c(713):kenwood_transaction returning2(-8) Protocol error **2:kenwood.c(1213):kenwood_get_id returning(-8) Protocol error **2:kenwood.c(1206):kenwood_get_id entered kenwood_transaction called cmd=ID kenwood_transaction: Command is not correctly terminated 'ID TH-D74' kenwood.c(713):kenwood_transaction returning2(-8) Protocol error **2:kenwood.c(1213):kenwood_get_id returning(-8) Protocol error kenwood_open: no response to get_id from rig...continuing anyway kenwood_open: cannot get identification *1:kenwood.c(1051):kenwood_open returning(-8) Protocol error ser_close: restoring options rig.c(1479):rig_open returning2(-8) Protocol error |
From: Daniele F. <iu...@gm...> - 2025-07-10 17:20:10
|
I agree with the general ideas stated by NAte, however the LICENSE file differs because it says: "The 'AUTHORS' file lists contributors known as the The Hamlib Group." "The frontend library source code files and associated backend library source code files are licensed and released under the Lesser GNU Public License (LGPL)" "Various other supplied program source files and example source files are licensed and released under the GNU Public License (GPL)" Since the simulators aren't frontend code I think that they are under the GPL. This doesn't prevent individual files or directories from having different licenses. I think that the examples being under the GPL is strange because the LGPL allows linking to closed source software, while I think that the GPL is appropriate for rigctl and similar. The tests that I have written are so basic that I didn't think of adding a license, but I think that they are part of the backend so they may fall under the LGPL. -- 73 de IU5HKX Daniele |
From: Nate B. <no...@gi...> - 2025-07-10 02:22:30
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 0db57035d50880893305d45ef5adbd538f0c401e https://github.com/Hamlib/Hamlib/commit/0db57035d50880893305d45ef5adbd538f0c401e Author: Nate Bargmann <n0...@n0...> Date: 2025-07-09 (Wed, 09 Jul 2025) Changed paths: M NEWS Log Message: ----------- Update NEWS for AF6SA WRC rotator backend To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-07-10 02:04:39
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: e4716be3666d7bf0ca07489cfdc5a42fe1478487 https://github.com/Hamlib/Hamlib/commit/e4716be3666d7bf0ca07489cfdc5a42fe1478487 Author: Michael Morgan <844...@us...> Date: 2025-07-09 (Wed, 09 Jul 2025) Changed paths: M include/hamlib/rotlist.h M rotators/gs232a/gs232.c M rotators/gs232a/gs232a.c M rotators/gs232a/gs232a.h Log Message: ----------- Added AF6SA WRC It uses non-standard W command. Commit: 6ae7e5986f1e19747a4ed6692f9c8052629868e2 https://github.com/Hamlib/Hamlib/commit/6ae7e5986f1e19747a4ed6692f9c8052629868e2 Author: Michael Morgan <844...@us...> Date: 2025-07-09 (Wed, 09 Jul 2025) Changed paths: M bindings/python/test_Hamlib_class.py Log Message: ----------- Update test_Hamlib_class.py Commit: c2a8ceab2b1cd45c2a38fa921521c6b059783440 https://github.com/Hamlib/Hamlib/commit/c2a8ceab2b1cd45c2a38fa921521c6b059783440 Author: Michael Morgan <844...@us...> Date: 2025-07-09 (Wed, 09 Jul 2025) Changed paths: M rotators/gs232a/gs232.c Log Message: ----------- Removed Redundant IF Commit: 48e7bd734a6aaedd5fd74e214426dc3347835f48 https://github.com/Hamlib/Hamlib/commit/48e7bd734a6aaedd5fd74e214426dc3347835f48 Author: Nate Bargmann <n0...@n0...> Date: 2025-07-09 (Wed, 09 Jul 2025) Changed paths: M bindings/python/test_Hamlib_class.py M include/hamlib/rotlist.h M rotators/gs232a/gs232.c M rotators/gs232a/gs232a.c M rotators/gs232a/gs232a.h Log Message: ----------- Merge GitHub PR #1800 Compare: https://github.com/Hamlib/Hamlib/compare/275d01c54500...48e7bd734a6a To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-07-10 01:48:55
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 275d01c5450079a1dd164204eab7d9b19260fd58 https://github.com/Hamlib/Hamlib/commit/275d01c5450079a1dd164204eab7d9b19260fd58 Author: Nate Bargmann <n0...@n0...> Date: 2025-07-09 (Wed, 09 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Attempt to quell Ubuntu CI error Ubuntu CI is generating the following error: E: Failed to fetch https://security.ubuntu.com/ubuntu/pool/main/u/util-linux/uuid-dev_2.39.3-9ubuntu6.2_amd64.deb 404 Not Found [IP: 52.252.163.49 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Error: Process completed with exit code 100. This patch updates the repository cache. To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <n0...@n0...> - 2025-07-10 01:32:04
|
* On 2025 09 Jul 04:07 -0500, George Baltz wrote: > Thanks for that, Nate. On a related matter, what about the simulators? > Right now they're not copyrighted/licensed at all. Would GPL 2.1 or later be > appropriate for one I've done a lot of work on? That's a good question. I presume Mike did a lot of work on them and I know he had no qualms licensing under the LGPL 2.1. I hope that we can safely license them as LGPL 2.1 posthumously. As you work on them, adding your copyright and license header should be fine. 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 |
From: Nate B. <no...@gi...> - 2025-07-09 16:01:44
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 407d3f669b636f57990a095bb63f448f5b77dfdf https://github.com/Hamlib/Hamlib/commit/407d3f669b636f57990a095bb63f448f5b77dfdf Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-06 (Sun, 06 Jul 2025) Changed paths: M include/hamlib/rig.h M src/debug.c Log Message: ----------- Revert "Fix debug messages shown even from disabled levels" This reverts commit ae9556462a2989b8b97af0d6e320558ffa0e1f3e. Commit: 61ad3cda1098411fa8636b4347a791fd975ffa55 https://github.com/Hamlib/Hamlib/commit/61ad3cda1098411fa8636b4347a791fd975ffa55 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-06 (Sun, 06 Jul 2025) Changed paths: M bindings/python/test_startup.py Log Message: ----------- Use Hamlib.rigerror2() to get the error message for the given error number Commit: 64babdb3615f71c92dcd341161fc0b2fcdde45e3 https://github.com/Hamlib/Hamlib/commit/64babdb3615f71c92dcd341161fc0b2fcdde45e3 Author: Nate Bargmann <n0...@n0...> Date: 2025-07-09 (Wed, 09 Jul 2025) Changed paths: M bindings/python/test_startup.py M include/hamlib/rig.h M src/debug.c Log Message: ----------- Merge GitHub PR #1797 Compare: https://github.com/Hamlib/Hamlib/compare/b5ba3f45b8de...64babdb3615f To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-07-09 15:42:12
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 83168860635dfba5bbb227a2a7dbe57b91b46d6a https://github.com/Hamlib/Hamlib/commit/83168860635dfba5bbb227a2a7dbe57b91b46d6a Author: Mark J. Fine <mar...@fi...> Date: 2025-06-29 (Sun, 29 Jun 2025) Changed paths: M rigs/drake/Makefile.am M rigs/drake/drake.c M rigs/drake/drake.h A rigs/drake/r8.c Log Message: ----------- Adds a backend for the Drake R8 for non-intrusive testing. Module contains copies of parts of drake.c because several routines are significantly different than R8a/b. Resopnses will be different. Test rig includes better debugging of message transfers, that replace nulls, CRs and LFs with token strings so they can be properly seen and counted as part of the sending and receiving messages. Commit: f94ec6a47b3b06f166a19d74cf34148342a9bea2 https://github.com/Hamlib/Hamlib/commit/f94ec6a47b3b06f166a19d74cf34148342a9bea2 Author: Mark J. Fine <mar...@fi...> Date: 2025-06-30 (Mon, 30 Jun 2025) Changed paths: M rigs/drake/drake.c M rigs/drake/drake.h M rigs/drake/r8.c Log Message: ----------- Changes to smooth out the transaction process for all Drakes, and more test edits for the R8. Commit: 03bf68c45925999af7aaf31af8f7cb01d1397f89 https://github.com/Hamlib/Hamlib/commit/03bf68c45925999af7aaf31af8f7cb01d1397f89 Author: Mark J. Fine <mar...@fi...> Date: 2025-06-30 (Mon, 30 Jun 2025) Changed paths: M rigs/drake/drake.c M rigs/drake/r8.c Log Message: ----------- Removed redundant timout-specific error block. Commit: e1562e675feb19b302c445363af0fe791dd6b748 https://github.com/Hamlib/Hamlib/commit/e1562e675feb19b302c445363af0fe791dd6b748 Author: Mark J. Fine <mar...@fi...> Date: 2025-07-01 (Tue, 01 Jul 2025) Changed paths: M rigs/drake/drake.h M rigs/drake/r8.c Log Message: ----------- Organized most of the redundant rig freq, mode, mem, and all reporting into their individual routines that decode and pool most of the 'get' settings into the private data area. Commit: 3b8a24179ee06a6dabc262284ad40fda805ef930 https://github.com/Hamlib/Hamlib/commit/3b8a24179ee06a6dabc262284ad40fda805ef930 Author: Mark J. Fine <mar...@fi...> Date: 2025-07-02 (Wed, 02 Jul 2025) Changed paths: M rigs/drake/r8.c Log Message: ----------- Fixed issue in comms loop where receive buffer was too small, causing buffer overflow crashes. Also, added buffer initialization in case some receive errors are not handled properly. Fixed potential C99 stdbool error. Commit: d32d605be67f46d75fd1185224ebb9606324ad6c https://github.com/Hamlib/Hamlib/commit/d32d605be67f46d75fd1185224ebb9606324ad6c Author: Mark J. Fine <mar...@fi...> Date: 2025-07-02 (Wed, 02 Jul 2025) Changed paths: M rigs/drake/drake.c Log Message: ----------- Fix crashing when attempting to receive data on 'set' actions... helps if the receive buffer is appropriately sized. Also, added intialization to the receive buffer in the comms loop. Commit: 3ff4bc99cc843a014ff8bc55aba5be9653ca87a5 https://github.com/Hamlib/Hamlib/commit/3ff4bc99cc843a014ff8bc55aba5be9653ca87a5 Author: Mark J. Fine <mar...@fi...> Date: 2025-07-02 (Wed, 02 Jul 2025) Changed paths: M rigs/drake/drake.c M rigs/drake/drake.h M rigs/drake/r8.c Log Message: ----------- Moved all r8's command debug routines over to drake.c and out of the r8-specifc backend. Removed the r8-specific transaction routine and repointed it to the revised common one in drake.c. Commit: db863a69212291ea6acbb93eaff54d349a9b0cc1 https://github.com/Hamlib/Hamlib/commit/db863a69212291ea6acbb93eaff54d349a9b0cc1 Author: Mark J. Fine <mar...@fi...> Date: 2025-07-02 (Wed, 02 Jul 2025) Changed paths: M rigs/drake/drake.c Log Message: ----------- Added stdbool.h for c99 compilers in drake.c Commit: 48405744b534fbef90db88f63cf08fd09bd47a2f https://github.com/Hamlib/Hamlib/commit/48405744b534fbef90db88f63cf08fd09bd47a2f Author: Mark J. Fine <mar...@fi...> Date: 2025-07-02 (Wed, 02 Jul 2025) Changed paths: M rigs/drake/r8.c Log Message: ----------- Silence uninitiated variable warning in vfo_op on C99 compuler. Commit: 6ac3dd596be40f5b2ea20d6316394fcf25a5f948 https://github.com/Hamlib/Hamlib/commit/6ac3dd596be40f5b2ea20d6316394fcf25a5f948 Author: Mark J. Fine <mar...@fi...> Date: 2025-07-03 (Thu, 03 Jul 2025) Changed paths: M rigs/drake/r8.c Log Message: ----------- Fixed squelch detection to use an asterisk instead of a hash (like in the manual). Also fixed setting of meter based on the status of RIG_DCD_ON/OFF instead of true/false. Commit: 7a975784769b2b45605f7ecde22f4d49d15d40ba https://github.com/Hamlib/Hamlib/commit/7a975784769b2b45605f7ecde22f4d49d15d40ba Author: Mark J. Fine <mar...@fi...> Date: 2025-07-03 (Thu, 03 Jul 2025) Changed paths: M rigs/drake/r8.c Log Message: ----------- Fixed error in get_mem(), which was reading mode, not memory channel. Adusted Report All to decode memory status AFTER mode, so VFO_MEM wouldn't get squashed. Commit: cb0646c7275eebe254b3da857b1f5791a59995d6 https://github.com/Hamlib/Hamlib/commit/cb0646c7275eebe254b3da857b1f5791a59995d6 Author: Mark J. Fine <mar...@fi...> Date: 2025-07-04 (Fri, 04 Jul 2025) Changed paths: M rigs/drake/drake.c M rigs/drake/drake.h M rigs/drake/r8.c Log Message: ----------- Merged all R8 testing routines (except set/get memory channel) into their equivalents within drake. Will do the same with memory channel routines once they are better tested. Commit: 49b01e196874961d64a60136cfe44c29c5c7ebd8 https://github.com/Hamlib/Hamlib/commit/49b01e196874961d64a60136cfe44c29c5c7ebd8 Author: Mark J. Fine <mar...@fi...> Date: 2025-07-04 (Fri, 04 Jul 2025) Changed paths: M rigs/drake/drake.c Log Message: ----------- Removed EOM from set_mem's "Cxx" command because it was leaving an extra LF in the receive queue, messing up the response to any subsequent command. Commit: ec0a04669c3dd658d5b7fbe57ffc1af642a48552 https://github.com/Hamlib/Hamlib/commit/ec0a04669c3dd658d5b7fbe57ffc1af642a48552 Author: Mark J. Fine <mar...@fi...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M rigs/drake/drake.c M rigs/drake/drake.h M rigs/drake/r8.c Log Message: ----------- Merged remaining R8 set/get memory channel routines over to drake.c Cleaned up comments and added interface documentation to newly added routines Added TODO notes for things yet to be handled on R8A/B, such as channel name Commit: 22636be85e7a33e42077860112b858ecdac79449 https://github.com/Hamlib/Hamlib/commit/22636be85e7a33e42077860112b858ecdac79449 Author: Mark J. Fine <mar...@fi...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M rigs/drake/drake.c Log Message: ----------- Commented out the embedded debugging (WARN level) that echoes all transaction data. Commit: 256037296f3d6785a74e8f6877d78afa9b6da7f9 https://github.com/Hamlib/Hamlib/commit/256037296f3d6785a74e8f6877d78afa9b6da7f9 Author: Mark J. Fine <mar...@fi...> Date: 2025-07-07 (Mon, 07 Jul 2025) Changed paths: M rigs/drake/drake.c M rigs/drake/r8.c Log Message: ----------- Fixed typos and copyright attribution on drake.c and r8.c Commit: f0b1c5bde2148c70f35eecec0e671e76e1fa8cd3 https://github.com/Hamlib/Hamlib/commit/f0b1c5bde2148c70f35eecec0e671e76e1fa8cd3 Author: Nate Bargmann <n0...@n0...> Date: 2025-07-09 (Wed, 09 Jul 2025) Changed paths: M rigs/drake/Makefile.am M rigs/drake/drake.c M rigs/drake/drake.h A rigs/drake/r8.c Log Message: ----------- Merge GitHub PR #1796 Commit: b5ba3f45b8de53866d160a86911672812627ee1e https://github.com/Hamlib/Hamlib/commit/b5ba3f45b8de53866d160a86911672812627ee1e Author: Nate Bargmann <n0...@n0...> Date: 2025-07-09 (Wed, 09 Jul 2025) Changed paths: M NEWS Log Message: ----------- Update NEWS for R8 backend Compare: https://github.com/Hamlib/Hamlib/compare/6fade7fa33f3...b5ba3f45b8de To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-07-09 15:16:06
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: d065bcb8ef0311ab21f85c8a7d1aec83db2c6cb1 https://github.com/Hamlib/Hamlib/commit/d065bcb8ef0311ab21f85c8a7d1aec83db2c6cb1 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-03 (Thu, 03 Jul 2025) Changed paths: M Makefile.am Log Message: ----------- Sort SUBDIRS and DIST_SUBDIRS and fix them "security" was added twice to SUBDIRS and BACKEND_LIST is not set by configure. Commit: f4cebd5339ce813ab2eba541bc5eca835db240c1 https://github.com/Hamlib/Hamlib/commit/f4cebd5339ce813ab2eba541bc5eca835db240c1 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-03 (Thu, 03 Jul 2025) Changed paths: M Makefile.am M configure.ac Log Message: ----------- Do not compile rigs/winradio if disabled in configure To disable: ./configure --disable-winradio Commit: e7daf11d5cdd05d6299fedbc8d18b40b6bfacf48 https://github.com/Hamlib/Hamlib/commit/e7daf11d5cdd05d6299fedbc8d18b40b6bfacf48 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M Makefile.am M configure.ac Log Message: ----------- Do not compile rotators/indi if disabled in configure To disable: ./configure --without-indi Commit: 55805c90c91dbcab9270bf73616c9d9cd19afd23 https://github.com/Hamlib/Hamlib/commit/55805c90c91dbcab9270bf73616c9d9cd19afd23 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Do the configure step with everything "no", then with "yes" Shared and static libraries are built in both cases. The usrp driver is "no" in both cases because it's in an external repository. Commit: bdde43f175692144e436e3d3bf1b23fd4c648925 https://github.com/Hamlib/Hamlib/commit/bdde43f175692144e436e3d3bf1b23fd4c648925 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Execute make with less verbosity for better readability This replaces the lines "Entering directory {DIRECTORY}" / "Leaving directory {DIRECTORY}" with just "Making {TARGET} {DIRECTORY}" and hides other output. Warning and errors are shown anyway. Commit: 6a9f93a89e166fc3b293f18ba440986be40e6f43 https://github.com/Hamlib/Hamlib/commit/6a9f93a89e166fc3b293f18ba440986be40e6f43 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Remove trailing newline from YAML multiline strings Commit: 6433447e913eb865e655ab30a144363fcd04bbf7 https://github.com/Hamlib/Hamlib/commit/6433447e913eb865e655ab30a144363fcd04bbf7 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Install TCL for macOS in the CI Commit: 419cb02dd5998c937fb6df3bd180b3d6c3dce00c https://github.com/Hamlib/Hamlib/commit/419cb02dd5998c937fb6df3bd180b3d6c3dce00c Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Install Lua for macOS in the CI Install the latest version available. Commit: 585d23ae5b25844c49e492eda21338d56ed5141b https://github.com/Hamlib/Hamlib/commit/585d23ae5b25844c49e492eda21338d56ed5141b Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Temporarily disable building Lua bindings on macOS Commit: b73d4a5cefda6f35331d39295e5c0263f7aa3576 https://github.com/Hamlib/Hamlib/commit/b73d4a5cefda6f35331d39295e5c0263f7aa3576 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Install SWIG for macOS in the CI Install the latest version available. Commit: f68c48aac54210e2bd1ee7ee2fd15401e8a201d2 https://github.com/Hamlib/Hamlib/commit/f68c48aac54210e2bd1ee7ee2fd15401e8a201d2 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M src/Makefile.am Log Message: ----------- Add dependency to hamlibdatetime.h Fixes a race during parallel builds: rig.c:74:10: fatal error: 'hamlibdatetime.h' file not found Occurred in https://github.com/Hamlib/Hamlib/actions/runs/16087329208/job/45400068817 Commit: e5e4ef84fe0b6811ac8bd6bc5307aa36c8a0c512 https://github.com/Hamlib/Hamlib/commit/e5e4ef84fe0b6811ac8bd6bc5307aa36c8a0c512 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M simulators/Makefile.am Log Message: ----------- Remove redundant rule for make clean All built files are deleted automatically. Commit: b96afa9372433735235895b4a2dddbedc2f54a74 https://github.com/Hamlib/Hamlib/commit/b96afa9372433735235895b4a2dddbedc2f54a74 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M simulators/Makefile.am Log Message: ----------- Remove redundant rule for make make knows how to build an excutable from a single source file. Commit: 3706f365a545aa67ec4147cf9aa146ec40ace871 https://github.com/Hamlib/Hamlib/commit/3706f365a545aa67ec4147cf9aa146ec40ace871 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Temporarily disable parallel builds Commit: 98489501fe80c32cf456c4bf962f628a4dc175ca https://github.com/Hamlib/Hamlib/commit/98489501fe80c32cf456c4bf962f628a4dc175ca Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M Makefile.am Log Message: ----------- Revert "Sort SUBDIRS and DIST_SUBDIRS and fix them" This reverts commit d065bcb8ef0311ab21f85c8a7d1aec83db2c6cb1. Conflicts: Makefile.am Commit: 2fc0b8eef5e85cccf00c449c95a5405a78617038 https://github.com/Hamlib/Hamlib/commit/2fc0b8eef5e85cccf00c449c95a5405a78617038 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M Makefile.am Log Message: ----------- Fix make distcheck again Commit: 633cee04d2b78053c470c5d78ca92d2722ea4fbe https://github.com/Hamlib/Hamlib/commit/633cee04d2b78053c470c5d78ca92d2722ea4fbe Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Install INDI development packages for Linux in the CI Commit: 8c94897208b2197c3fd2ec3eef138f66306065d4 https://github.com/Hamlib/Hamlib/commit/8c94897208b2197c3fd2ec3eef138f66306065d4 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Install development package for rigmatrix for Linux in the CI Commit: 54c2eb89a2fe75103c942596a6f81dbb71b4a0fc https://github.com/Hamlib/Hamlib/commit/54c2eb89a2fe75103c942596a6f81dbb71b4a0fc Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-05 (Sat, 05 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Revert "Temporarily disable parallel builds" This reverts commit 3706f365a545aa67ec4147cf9aa146ec40ace871. Commit: 976bfb42767019de50c8d29aebdbfdb933a88b01 https://github.com/Hamlib/Hamlib/commit/976bfb42767019de50c8d29aebdbfdb933a88b01 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-06 (Sun, 06 Jul 2025) Changed paths: M doc/manuals/OTRSP_Protocol.pdf M rigs/yaesu/FT-817CAT.pdf M rigs/yaesu/FT-817MemoryMap.pdf M rotators/grbltrk/Makefile.am M security/AESStringCrypt.h M security/Makefile.nt M security/aes.h M security/password.h M security/sha256.h M src/Makefile.am M src/version_dll.rc Log Message: ----------- Remove the executable bit from data files Commit: 84799e2f6c3da704a0877465b77cd3d9bc1dfe15 https://github.com/Hamlib/Hamlib/commit/84799e2f6c3da704a0877465b77cd3d9bc1dfe15 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-06 (Sun, 06 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Revert "Install Lua for macOS in the CI" This reverts commit 419cb02dd5998c937fb6df3bd180b3d6c3dce00c. Conflicts: .github/workflows/c-cpp.yml Commit: 6fade7fa33f306150d707d577b06e151b09d3e2d https://github.com/Hamlib/Hamlib/commit/6fade7fa33f306150d707d577b06e151b09d3e2d Author: Nate Bargmann <n0...@n0...> Date: 2025-07-07 (Mon, 07 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml M Makefile.am M configure.ac M doc/manuals/OTRSP_Protocol.pdf M rigs/yaesu/FT-817CAT.pdf M rigs/yaesu/FT-817MemoryMap.pdf M rotators/grbltrk/Makefile.am M security/AESStringCrypt.h M security/Makefile.nt M security/aes.h M security/password.h M security/sha256.h M simulators/Makefile.am M src/Makefile.am M src/version_dll.rc Log Message: ----------- Merge GitHub PR #1795 Compare: https://github.com/Hamlib/Hamlib/compare/0c94ba468ac1...6fade7fa33f3 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: George B. <geo...@gm...> - 2025-07-09 09:06:21
|
Thanks for that, Nate. On a related matter, what about the simulators? Right now they're not copyrighted/licensed at all. Would GPL 2.1 or later be appropriate for one I've done a lot of work on? On 7/7/25 2:25 PM, Nate Bargmann wrote: > * On 2025 07 Jul 12:50 -0500, George Baltz wrote: >> I'm in the process of moving some data structures out of rig.h into separate >> include files, mostly with cut&paste. While setting up the headers and >> looking at other files, I wondered if there is an *official* name for >> generic Hamlib development for the copyright declaration. Not to get into >> general license questions, but I'd at least like to get this in the right >> form. > I'd say that if it is a significant amount of your original work then > you should note yourself as the copyright holder and licensed under the > LGPL 2.1 as the rest of the library. > > In some cases I've used the name of "The Hamlib Group" which is not a > formal entity and so probably really can't claim copyright but I mainly > limited that to things like README files and the like where a long list > of copyright holders isn't readable. > > As Hamlib is not a formal entity, each contributor should assign > themselves as the copyright holder or add oneself to the list in the > cases of a significant amount of contribution to existing files. As I > see it, we're a collection of hobbyists contributing source code for the > use of the greater radio hobby. > > 73, Nate > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |