hamlib-developer Mailing List for Ham Radio Control Libraries (Page 6)
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
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Daniele F. <iu...@gm...> - 2025-07-06 13:27:49
|
Hello, I have nothing against reverting this commit, but it doesn't work like you said, in fact it also prints TRACE message if you set debug to none and no error happened, but now I see that the reason for my commit is that the old py3test.py used rigerror() instead of rigerror2() so the output of the line print("status(str):\t\t%s" % Hamlib.rigerror(my_rig.error_status)) was unexpected to me. > assert Hamlib.rigerror(my_rig.error_status) == "Command completed successfully\n" E AssertionError: assert 'network.c(16...uccessfully\n' == 'Command comp...uccessfully\n' E E + network.c(1615): not starting multicast publisher E + *1:network.c(1616):network_multicast_publisher_start returning(0) E + *1:network.c(1798):network_multicast_receiver_start entered E + network.c(1810): multicast receiver address=0.0.0.0, port=4532 E + network.c(1816): not starting multicast receiver E + *1:network.c(1817):network_multicast_receiver_start returning(0) ... E E ...Full output truncated (14 lines hidden), use '-vv' to show python/test_startup.py:34: AssertionError I'll revert and also change the test to use rigerror2 -- 73 de IU5HKX Daniele |
From: George B. <geo...@gm...> - 2025-07-04 06:25:40
|
The code removed by this change was working exactly as designed (and desired). It allowed someone to run with debug level set low (ERR or WARN) but still get needed info if an error occurred. Having this info (without wading through megabytes of other messages) is essential for debugging transient or hard-to-reproduce errors. I think this commit should be reverted. On 6/7/25 8:31 AM, dforsi via Hamlib-developer wrote: > Branch: refs/heads/master > Home: https://github.com/Hamlib/Hamlib > Commit: ae9556462a2989b8b97af0d6e320558ffa0e1f3e > https://github.com/Hamlib/Hamlib/commit/ae9556462a2989b8b97af0d6e320558ffa0e1f3e > Author: Daniele Forsi IU5HKX <iu...@gm...> > Date: 2025-06-07 (Sat, 07 Jun 2025) > > Changed paths: > M include/hamlib/rig.h > M src/debug.c > > Log Message: > ----------- > Fix debug messages shown even from disabled levels > > Messages from ENTERFUNC and RETURNFUNC where stored in an internal buffer > even whe debug_level wasn't TRACE and were returned when calling rigerror(). > > > > 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 |
From: dforsi <no...@gi...> - 2025-07-01 20:36:21
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 7acb809eef99b923149a3efa088aba05f3aaffca https://github.com/Hamlib/Hamlib/commit/7acb809eef99b923149a3efa088aba05f3aaffca Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-01 (Tue, 01 Jul 2025) Changed paths: M bindings/amplifier.swg M bindings/rotator.swg Log Message: ----------- Do not try to compile Python code when building other bindings Fixes the issue reported by @dl8fcl https://github.com/Hamlib/Hamlib/commit/f7d38f92cac73fb8b952f5dde3853f40ef910e14#commitcomment-161078321 Commit: 623ff17f61e227d461fca524c60a331c9a897672 https://github.com/Hamlib/Hamlib/commit/623ff17f61e227d461fca524c60a331c9a897672 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-07-01 (Tue, 01 Jul 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Build all language bindings Compare: https://github.com/Hamlib/Hamlib/compare/ca7353abaab7...623ff17f61e2 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Praet K. <on...@gm...> - 2025-06-30 19:05:51
|
G'day mate, Maybe this can help. 73 de ON4CIR, Karel <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virusvrij.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> |
From: Nate B. <no...@gi...> - 2025-06-30 12:57:02
|
Branch: refs/heads/Hamlib-4.6.3 Home: https://github.com/Hamlib/Hamlib Commit: c0d7a320565a50fefb8372571a2f5ab1ff965e00 https://github.com/Hamlib/Hamlib/commit/c0d7a320565a50fefb8372571a2f5ab1ff965e00 Author: Michael Morgan <844...@us...> Date: 2025-06-30 (Mon, 30 Jun 2025) Changed paths: M rigs/flexradio/smartsdr.c M rigs/flexradio/smartsdr_caps.h Log Message: ----------- FlexCW Added the option to send CW using CWX commands on Flex's. (cherry picked from commit b365d988a42ba468bc663f3d59043f75bc245fa2) Commit: 0accc406c836cb56ff2fa165c806f0a21ffd1bc5 https://github.com/Hamlib/Hamlib/commit/0accc406c836cb56ff2fa165c806f0a21ffd1bc5 Author: aa5sh <844...@us...> Date: 2025-06-30 (Mon, 30 Jun 2025) Changed paths: M rigs/flexradio/smartsdr.c Log Message: ----------- Added RetVal (cherry picked from commit 3b6577834eac8f46e6c3d3264509f9401a6f88d2) Commit: e03441d9aed44c556dd0acc45f6438b1e6ad6942 https://github.com/Hamlib/Hamlib/commit/e03441d9aed44c556dd0acc45f6438b1e6ad6942 Author: Nate Bargmann <n0...@n0...> Date: 2025-06-30 (Mon, 30 Jun 2025) Changed paths: M NEWS Log Message: ----------- Update NEWS for Flex CW Compare: https://github.com/Hamlib/Hamlib/compare/8abb5efcf0b3...e03441d9aed4 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-06-30 12:45:49
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: b365d988a42ba468bc663f3d59043f75bc245fa2 https://github.com/Hamlib/Hamlib/commit/b365d988a42ba468bc663f3d59043f75bc245fa2 Author: Michael Morgan <844...@us...> Date: 2025-06-28 (Sat, 28 Jun 2025) Changed paths: M rigs/flexradio/smartsdr.c M rigs/flexradio/smartsdr_caps.h Log Message: ----------- FlexCW Added the option to send CW using CWX commands on Flex's. Commit: 3b6577834eac8f46e6c3d3264509f9401a6f88d2 https://github.com/Hamlib/Hamlib/commit/3b6577834eac8f46e6c3d3264509f9401a6f88d2 Author: aa5sh <844...@us...> Date: 2025-06-28 (Sat, 28 Jun 2025) Changed paths: M rigs/flexradio/smartsdr.c Log Message: ----------- Added RetVal Commit: ca7353abaab701eca3893bdad3f1895d22239b85 https://github.com/Hamlib/Hamlib/commit/ca7353abaab701eca3893bdad3f1895d22239b85 Author: Nate Bargmann <n0...@n0...> Date: 2025-06-30 (Mon, 30 Jun 2025) Changed paths: M rigs/flexradio/smartsdr.c M rigs/flexradio/smartsdr_caps.h Log Message: ----------- Merge GitHun PR #1788 Compare: https://github.com/Hamlib/Hamlib/compare/a6fb8a079a56...ca7353abaab7 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: FVsonar <no...@gi...> - 2025-06-30 12:37:47
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: c9161e2e25d80609d5127ca0c1ebe8e78cb00040 https://github.com/Hamlib/Hamlib/commit/c9161e2e25d80609d5127ca0c1ebe8e78cb00040 Author: 声纳 <159...@qq...> Date: 2025-06-28 (Sat, 28 Jun 2025) Changed paths: M rigs/guohetec/guohetec.c M rigs/guohetec/guohetec.h M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- Improve error handling for GUOHETEC drivers to enhance WSJT-X compatibility - Add graceful degradation for communication errors - Return cached values instead of error codes on failures - Implement unified response validation functions - Add cache return macros for consistent error handling - Maintain backward compatibility while improving stability This change ensures WSJT-X and similar applications continue working even when temporary communication issues occur with GUOHETEC radios. Fixes: WSJT-X compatibility issues with PMR-171 and Q900 drivers Commit: abf6be0b5e80b3d2376ac873ccf2602ad8e8199f https://github.com/Hamlib/Hamlib/commit/abf6be0b5e80b3d2376ac873ccf2602ad8e8199f Author: 声纳 <159...@qq...> Date: 2025-06-28 (Sat, 28 Jun 2025) Changed paths: M rigs/guohetec/guohetec.c M rigs/guohetec/pmr171.c Log Message: ----------- Fix compilation errors in GUOHETEC drivers - Remove duplicate function declarations in pmr171_send - Remove duplicate code blocks in pmr171_set_mode - Remove duplicate pmr171_send calls in pmr171_set_ptt - Add missing from_be function implementation - Fix syntax errors that were causing CI failures Commit: dee29c555f98413486dd7110b601aa403035970d https://github.com/Hamlib/Hamlib/commit/dee29c555f98413486dd7110b601aa403035970d Author: 声纳 <159...@qq...> Date: 2025-06-28 (Sat, 28 Jun 2025) Changed paths: M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- Implement consistent error handling for GUOHETEC drivers - Use unified error handling mechanism in send_cmd2 functions - Always return RIG_OK to prevent WSJT-X errors - Update cache with requested values even when communication fails - Use English comments and debug messages - Ensure graceful degradation with cached values on protocol/timeout errors Commit: 19c2cc03156846d22262536e9cde7f70deff26db https://github.com/Hamlib/Hamlib/commit/19c2cc03156846d22262536e9cde7f70deff26db Author: 声纳 <159...@qq...> Date: 2025-06-28 (Sat, 28 Jun 2025) Changed paths: M rigs/guohetec/guohetec.c Log Message: ----------- Fix duplicate retval variable definition in guohetec.c probe function Commit: a61877a60be23df45439cc607585ecfe55d46395 https://github.com/Hamlib/Hamlib/commit/a61877a60be23df45439cc607585ecfe55d46395 Author: 声纳 <159...@qq...> Date: 2025-06-28 (Sat, 28 Jun 2025) Changed paths: M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- Fix duplicate stdint.h includes in pmr171.c and q900.c Commit: c2d4fbe601c7d6dce463d133634c2458e0489fd3 https://github.com/Hamlib/Hamlib/commit/c2d4fbe601c7d6dce463d133634c2458e0489fd3 Author: 声纳 <159...@qq...> Date: 2025-06-28 (Sat, 28 Jun 2025) Changed paths: M rigs/guohetec/guohetec.c M rigs/guohetec/guohetec.h M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- guohetec: comprehensive code quality improvements - Fix compilation warnings by removing unnecessary dump_hex function calls - Resolve implicit function declaration warnings for validation macros - Remove duplicate GUOHE_MODE_TABLE_MAX definitions across files - Optimize header includes based on IWYU suggestions: * Add iofunc.h (for read_block/write_block functions) * Add riglist.h (for RIG_MODEL_* constants) * Remove unistd.h, misc.h, serial.h (unnecessary includes) - Convert validation macros to functions for better compiler compatibility - Maintain backward compatibility with existing macro definitions - Improve code structure and maintainability - Ensure WSJT-X compatibility with consistent error handling All changes maintain existing functionality while improving code quality and reducing compilation warnings. Commit: 6797ab7646030b93ebffdcb57e8583928d106a5f https://github.com/Hamlib/Hamlib/commit/6797ab7646030b93ebffdcb57e8583928d106a5f Author: 声纳 <159...@qq...> Date: 2025-06-28 (Sat, 28 Jun 2025) Changed paths: M rigs/guohetec/guohetec.c M rigs/guohetec/guohetec.h M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- guohetec: fix cppcheck warnings and improve code quality Based on cppcheck analysis and maintainer feedback: - Fix constParameterPointer warnings: declare reply parameters as const where appropriate - Fix variableScope warnings: reduce reply variable scope to minimum required - Apply IWYU (IncludeWhatYouUse) suggestions for header optimization: * Add iofunc.h (for read_block, write_block functions) * Add riglist.h (for RIG_MODEL_* constants) * Remove unistd.h, misc.h, serial.h (unnecessary includes) - Maintain backward compatibility and existing functionality - Improve code maintainability and reduce compilation warnings All changes follow maintainer recommendations and maintain WSJT-X compatibility. Commit: b95d349bff845a6cc936f838087fdce62aa7194d https://github.com/Hamlib/Hamlib/commit/b95d349bff845a6cc936f838087fdce62aa7194d Author: 声纳 <159...@qq...> Date: 2025-06-30 (Mon, 30 Jun 2025) Changed paths: M rigs/guohetec/guohetec.c M rigs/guohetec/guohetec.h M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- Add LGPLv2.1 license headers to GUOHETEC driver files Commit: a6fb8a079a562014b9948e16a2dd817346fcf4e2 https://github.com/Hamlib/Hamlib/commit/a6fb8a079a562014b9948e16a2dd817346fcf4e2 Author: 声纳 <159...@qq...> Date: 2025-06-30 (Mon, 30 Jun 2025) Changed paths: M rigs/guohetec/guohetec.c M rigs/guohetec/guohetec.h M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- Update copyright to GUOHETEC in license headers for all GUOHETEC driver files Compare: https://github.com/Hamlib/Hamlib/compare/862fda58be87...a6fb8a079a56 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-06-27 12:43:45
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 5eda68367f86a770cae92d0a601ba1c040714597 https://github.com/Hamlib/Hamlib/commit/5eda68367f86a770cae92d0a601ba1c040714597 Author: Mark J. Fine <mar...@fi...> Date: 2025-06-27 (Fri, 27 Jun 2025) Changed paths: M rigs/icom/icom_alt_agc.c Log Message: ----------- Corrected a couple of cppcheck warnings: uninitialize variable and condition always false. Commit: 862fda58be871ce33f9d946c30d61232dd41549c https://github.com/Hamlib/Hamlib/commit/862fda58be871ce33f9d946c30d61232dd41549c Author: Nate Bargmann <n0...@n0...> Date: 2025-06-27 (Fri, 27 Jun 2025) Changed paths: M rigs/icom/icom_alt_agc.c Log Message: ----------- Merge GitHub PR #1786 Compare: https://github.com/Hamlib/Hamlib/compare/9c1873491175...862fda58be87 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-06-27 12:26:16
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 7fe7602a8289fd9bc74a350ea084c72640c319ad https://github.com/Hamlib/Hamlib/commit/7fe7602a8289fd9bc74a350ea084c72640c319ad Author: 声纳 <159...@qq...> Date: 2025-06-27 (Fri, 27 Jun 2025) Changed paths: M rigs/guohetec/guohetec.c M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- Delete redundant functions and structures in guohetec. c, pmr171. c, and q900. c, optimize code structure, fix data length verification logic, and ensure the security and stability of data processing. All cppcheck style warnings have been fixed Commit: cb308819e7c1f65e6b0045fe154446f06376ad7c https://github.com/Hamlib/Hamlib/commit/cb308819e7c1f65e6b0045fe154446f06376ad7c Author: Nate Bargmann <n0...@n0...> Date: 2025-06-27 (Fri, 27 Jun 2025) Changed paths: M rigs/guohetec/guohetec.c M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- Merge GitHub PR #1785 Commit: 9c187349117592a5a3fe21375c0508c11a262c09 https://github.com/Hamlib/Hamlib/commit/9c187349117592a5a3fe21375c0508c11a262c09 Author: Nate Bargmann <n0...@n0...> Date: 2025-06-27 (Fri, 27 Jun 2025) Changed paths: M NEWS Log Message: ----------- Update NEWS for recent merges Compare: https://github.com/Hamlib/Hamlib/compare/36f582222f6a...9c1873491175 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-06-27 11:49:15
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 453e68c6cd6d5b21286cc914773cfdb029ca86c7 https://github.com/Hamlib/Hamlib/commit/453e68c6cd6d5b21286cc914773cfdb029ca86c7 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M bindings/python/test_rig.py M bindings/rig.swg Log Message: ----------- Fix Rig.get_split_vfo() The VFO argument optional with a default of RIG_VFO_CURR. Fixes PR ##1555. Commit: 7223fb0766468fabe2c40b3a3d0e309c9b1abfa1 https://github.com/Hamlib/Hamlib/commit/7223fb0766468fabe2c40b3a3d0e309c9b1abfa1 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M bindings/python/test_rig.py M bindings/rig.swg Log Message: ----------- Fix Rig.get_vfo_info() Commit: 6c399b55ffd9027de2c0958d43b8f5fcb07d4d97 https://github.com/Hamlib/Hamlib/commit/6c399b55ffd9027de2c0958d43b8f5fcb07d4d97 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M bindings/python/test_rig.py Log Message: ----------- Assert the length of sequences instead of the list datatype We only need to check how many values exist. Commit: bf518c06098d68ce5cae6e58812b78ff46d5be05 https://github.com/Hamlib/Hamlib/commit/bf518c06098d68ce5cae6e58812b78ff46d5be05 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-06-26 (Thu, 26 Jun 2025) Changed paths: M bindings/python/test_rig.py M bindings/rig.swg Log Message: ----------- Fix Rig.get_ant() The only supported value for get_ant() in the union of "option" is signed integer. Do the test when the rig is open. Commit: 36f582222f6a460735cf0538990cfc20fd46888e https://github.com/Hamlib/Hamlib/commit/36f582222f6a460735cf0538990cfc20fd46888e Author: Nate Bargmann <n0...@n0...> Date: 2025-06-27 (Fri, 27 Jun 2025) Changed paths: M bindings/python/test_rig.py M bindings/rig.swg Log Message: ----------- Merge GitHub PR #1784 Compare: https://github.com/Hamlib/Hamlib/compare/ef3e27820319...36f582222f6a To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-06-26 18:15:49
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: a09603fdd4e5699a72f509db284f9bbb494f4e10 https://github.com/Hamlib/Hamlib/commit/a09603fdd4e5699a72f509db284f9bbb494f4e10 Author: markjfine <mar...@fi...> Date: 2025-06-23 (Mon, 23 Jun 2025) Changed paths: M rigs/icom/icom_defs.h Log Message: ----------- Correct and update mapping of D_AGC values Ref issue#1775 (part 1) Corrected mapping of D_AGC values to currently enumerated AGC set. Will separately provide alternate mapping, if required, in backends that require it. Commit: 8abe1ec8e4fe08560fc14ebb2965f89105213a18 https://github.com/Hamlib/Hamlib/commit/8abe1ec8e4fe08560fc14ebb2965f89105213a18 Author: markjfine <mar...@fi...> Date: 2025-06-23 (Mon, 23 Jun 2025) Changed paths: M rigs/icom/icom.c Log Message: ----------- Correct mapping of D_AGC values Ref issue#1775 (part 1) Corrected mapping of D_AGC values to currently enumerated AGC set. Will separately provide alternate mapping, if required, in backends that require it. Commit: 6dffee33df0a9b79401a17150d5c431e268b8a64 https://github.com/Hamlib/Hamlib/commit/6dffee33df0a9b79401a17150d5c431e268b8a64 Author: markjfine <mar...@fi...> Date: 2025-06-23 (Mon, 23 Jun 2025) Changed paths: M rigs/icom/icom.c Log Message: ----------- Correct CWPitch set/get for Icom radios Icom has two confusing ways to set/get CW Pitch. The first way is to read/write the knob setting using CI-V command 14 subcommand 9. The second way is just to set/get the actual value via mode command 10. At some point the commands in hamlib changed from the former to the latter, but never adjusted the interpolation code of the former. This commit fixes the set and get routines appropriately. Commit: 82dd540d3a3fc181a81f1c3c3891f4331e770bbd https://github.com/Hamlib/Hamlib/commit/82dd540d3a3fc181a81f1c3c3891f4331e770bbd Author: Mark J. Fine <mar...@fi...> Date: 2025-06-26 (Thu, 26 Jun 2025) Changed paths: M rigs/icom/Makefile.am A rigs/icom/icom_alt_agc.c A rigs/icom/icom_alt_agc.h Log Message: ----------- Part 2 of Issue#1775: Adds optional wrappers for rigs that need to use the alternate AGC mapping originally specified in icom.c. Instructions for employment are provided within icom_alt_agc.c. Commit: ef0b7e30bd6fa770a2bccd27cd5e8b554a7dd764 https://github.com/Hamlib/Hamlib/commit/ef0b7e30bd6fa770a2bccd27cd5e8b554a7dd764 Author: Mark J. Fine <mar...@fi...> Date: 2025-06-26 (Thu, 26 Jun 2025) Changed paths: M rigs/icom/icom.c M rigs/icom/icom_alt_agc.c M rigs/icom/icom_defs.h Log Message: ----------- Reverted CW Pitch value<->knob conversion for non-ICR75 radios. Apparently R75 is the only one using the set mode command. Edited out all non-essential code commenting that was done during local testing. Commit: ef3e2782031967ffb6feeb5176cc47cd2e080f4b https://github.com/Hamlib/Hamlib/commit/ef3e2782031967ffb6feeb5176cc47cd2e080f4b Author: Nate Bargmann <n0...@n0...> Date: 2025-06-26 (Thu, 26 Jun 2025) Changed paths: M rigs/icom/Makefile.am M rigs/icom/icom.c A rigs/icom/icom_alt_agc.c A rigs/icom/icom_alt_agc.h M rigs/icom/icom_defs.h Log Message: ----------- Merge GitHub PR #1776 Compare: https://github.com/Hamlib/Hamlib/compare/31c3c973520e...ef3e27820319 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-06-26 02:43:19
|
Branch: refs/heads/Hamlib-4.6.3 Home: https://github.com/Hamlib/Hamlib Commit: f518c478f2a1a5ac6d23823f5b1b547d20168199 https://github.com/Hamlib/Hamlib/commit/f518c478f2a1a5ac6d23823f5b1b547d20168199 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M rigs/kenwood/ts590.c Log Message: ----------- Restore TS-590S/SG RIG_LEVEL_RFPOWER_METER (cherry picked from commit ec4590df8decc4c47a57e6dc78e92871b92c230e) Commit: 53c30fcf8c0eb3c392c6891a38985200925d311d https://github.com/Hamlib/Hamlib/commit/53c30fcf8c0eb3c392c6891a38985200925d311d Author: George Baltz N3GB <Geo...@gm...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M include/hamlib/rotator.h M src/sprintflst.c Log Message: ----------- Fix rotctl \dump_caps output rot_sprintf_status() was printing items multiple times. Cause of problem noticed by cppcheck. (cherry picked from commit 0b75b96ef160a5d14be39361b8bcf0a59f04982c) Commit: 8abb5efcf0b3eec5e9e7f8d1dac6bc4e10c7f560 https://github.com/Hamlib/Hamlib/commit/8abb5efcf0b3eec5e9e7f8d1dac6bc4e10c7f560 Author: Nate Bargmann <n0...@n0...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M NEWS Log Message: ----------- Update NEWS for TS-590 and rotctl fixes Compare: https://github.com/Hamlib/Hamlib/compare/867fc5886a5a...8abb5efcf0b3 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <no...@gi...> - 2025-06-26 02:37:40
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 4653b8f96c4cf0f489a021e647a7c30d790eee90 https://github.com/Hamlib/Hamlib/commit/4653b8f96c4cf0f489a021e647a7c30d790eee90 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-06-24 (Tue, 24 Jun 2025) Changed paths: M rigs/kenwood/k3.c M rigs/kenwood/tmd710.c M rigs/kenwood/ts480.c M rigs/kenwood/ts890s.c Log Message: ----------- More cppcheck "errors" in rigs/kenwood/* Still mostly cosmetic - currently ignoring syntax cppcheck can't cope with. Commit: ec4590df8decc4c47a57e6dc78e92871b92c230e https://github.com/Hamlib/Hamlib/commit/ec4590df8decc4c47a57e6dc78e92871b92c230e Author: George Baltz N3GB <Geo...@gm...> Date: 2025-06-24 (Tue, 24 Jun 2025) Changed paths: M rigs/kenwood/ts590.c Log Message: ----------- Restore TS-590S/SG RIG_LEVEL_RFPOWER_METER Commit: aa3e6cb6e9a8a45a2b2f627d11155e14f6808b99 https://github.com/Hamlib/Hamlib/commit/aa3e6cb6e9a8a45a2b2f627d11155e14f6808b99 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-06-24 (Tue, 24 Jun 2025) Changed paths: M rigs/icom/ic7300.c M rigs/icom/ic746.c M rigs/icom/icom.c Log Message: ----------- Fix cppcheck "errors" in rigs/icom/*.c Commit: 0b75b96ef160a5d14be39361b8bcf0a59f04982c https://github.com/Hamlib/Hamlib/commit/0b75b96ef160a5d14be39361b8bcf0a59f04982c Author: George Baltz N3GB <Geo...@gm...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M include/hamlib/rotator.h M src/sprintflst.c Log Message: ----------- Fix rotctl \dump_caps output rot_sprintf_status() was printing items multiple times. Cause of problem noticed by cppcheck. Commit: 921a6a9de372adedf68dd57eec620ed7b323c097 https://github.com/Hamlib/Hamlib/commit/921a6a9de372adedf68dd57eec620ed7b323c097 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M NEWS M src/serial.c M tests/hamlibmodels.c M tests/rigfreqwalk.c M tests/rigmatrix.c M tests/rotctl.c Log Message: ----------- Still more cppcheck cleanups Commit: 55b0599b752d5cd5c3e1ec1791624aaf8d8f3dbb https://github.com/Hamlib/Hamlib/commit/55b0599b752d5cd5c3e1ec1791624aaf8d8f3dbb Author: George Baltz N3GB <Geo...@gm...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M include/hamlib/rig.h M include/hamlib/rotator.h M src/sprintflst.c Log Message: ----------- Stop the blithering Commit: e163aa2645d9b7c8ae823edfc5d1066b346ce230 https://github.com/Hamlib/Hamlib/commit/e163aa2645d9b7c8ae823edfc5d1066b346ce230 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M src/sprintflst.c Log Message: ----------- Another reversion Commit: 31c3c973520e8bf87478e17dc6136845351e2e74 https://github.com/Hamlib/Hamlib/commit/31c3c973520e8bf87478e17dc6136845351e2e74 Author: Nate Bargmann <n0...@n0...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M NEWS M include/hamlib/rig.h M rigs/icom/ic7300.c M rigs/icom/ic746.c M rigs/icom/icom.c M rigs/kenwood/k3.c M rigs/kenwood/tmd710.c M rigs/kenwood/ts480.c M rigs/kenwood/ts590.c M rigs/kenwood/ts890s.c M src/serial.c M tests/hamlibmodels.c M tests/rigfreqwalk.c M tests/rigmatrix.c M tests/rotctl.c Log Message: ----------- Merge GitHub PR #1783 Compare: https://github.com/Hamlib/Hamlib/compare/92a077585510...31c3c973520e To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: FVsonar <no...@gi...> - 2025-06-26 02:26:10
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 25487237e907c1cf2525d2efcc9e2e0af79f71c1 https://github.com/Hamlib/Hamlib/commit/25487237e907c1cf2525d2efcc9e2e0af79f71c1 Author: 声纳 <159...@qq...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M include/hamlib/riglist.h A rigs/guohetec/guohetec.c A rigs/guohetec/guohetec.h A rigs/guohetec/pmr171.c A rigs/guohetec/q900.c Log Message: ----------- Added support for PMR171 and Q900 radios Commit: 96ab1b3a3a5782cfd7b0c97a9909fcca30d8aa3b https://github.com/Hamlib/Hamlib/commit/96ab1b3a3a5782cfd7b0c97a9909fcca30d8aa3b Author: 声纳 <159...@qq...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: A rigs/guohetec/Makefile.am M rigs/yaesu/Makefile.am R rigs/yaesu/pmr171.c Log Message: ----------- Migrate PMR171 driver from Yaesu to Guohetec directory Commit: a4904aed6270056d5e25d2462a181eee9797eb3d https://github.com/Hamlib/Hamlib/commit/a4904aed6270056d5e25d2462a181eee9797eb3d Author: 声纳 <159...@qq...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M configure.ac Log Message: ----------- Add Guohetec directory to build system Commit: e9f50226163f33c0cc1c1bca7d766fa5a690f00e https://github.com/Hamlib/Hamlib/commit/e9f50226163f33c0cc1c1bca7d766fa5a690f00e Author: 声纳 <159...@qq...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M rigs/yaesu/ft817.c M rigs/yaesu/yaesu.c M rigs/yaesu/yaesu.h Log Message: ----------- fix: correct PMR171/Q900 definitions in yaesu config Commit: 3d9288d099b06fe0f1395605480ecc3d475f7449 https://github.com/Hamlib/Hamlib/commit/3d9288d099b06fe0f1395605480ecc3d475f7449 Author: 声纳 <159...@qq...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- Change rig_debug and comments to English Commit: d28acc7d60589da1bfa11325f8132d66765a8183 https://github.com/Hamlib/Hamlib/commit/d28acc7d60589da1bfa11325f8132d66765a8183 Author: 声纳 <159...@qq...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M rigs/guohetec/guohetec.c M rigs/guohetec/guohetec.h Log Message: ----------- Change the rig_debug and comments of guohetec.c and guohetec.h to English Commit: 13335aff698c1fc1bac3aeb34cd447803b611080 https://github.com/Hamlib/Hamlib/commit/13335aff698c1fc1bac3aeb34cd447803b611080 Author: 声纳 <159...@qq...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M src/register.c Log Message: ----------- Add the DEFINE-INITRIGBACK macro to guohetec Commit: b1ad6a71122acc640841b4c5f4231fe81ad51faf https://github.com/Hamlib/Hamlib/commit/b1ad6a71122acc640841b4c5f4231fe81ad51faf Author: 声纳 <159...@qq...> Date: 2025-06-25 (Wed, 25 Jun 2025) Changed paths: M src/register.c Log Message: ----------- Add the rig_backend_list to guohetec Commit: 14a81b9ad9eb24e2c92762f94939c5bab4e36087 https://github.com/Hamlib/Hamlib/commit/14a81b9ad9eb24e2c92762f94939c5bab4e36087 Author: 声纳 <159...@qq...> Date: 2025-06-26 (Thu, 26 Jun 2025) Changed paths: M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- Fix q900 and pmr171 compilation warnings Commit: b7388e2fca4382232b71301cef3a625d74b6a2d7 https://github.com/Hamlib/Hamlib/commit/b7388e2fca4382232b71301cef3a625d74b6a2d7 Author: 声纳 <159...@qq...> Date: 2025-06-26 (Thu, 26 Jun 2025) Changed paths: M rigs/guohetec/pmr171.c M rigs/guohetec/q900.c Log Message: ----------- Delete useless variables of pmr171 and q900 Commit: acd4a98cd5eddb7b9f09608d2973d6670fdfcb5d https://github.com/Hamlib/Hamlib/commit/acd4a98cd5eddb7b9f09608d2973d6670fdfcb5d Author: 声纳 <159...@qq...> Date: 2025-06-26 (Thu, 26 Jun 2025) Changed paths: M rigs/guohetec/pmr171.c Log Message: ----------- Modify buffer size to prevent overflow Commit: 92a0775855109aae116f4352139a6d69c5c0ff46 https://github.com/Hamlib/Hamlib/commit/92a0775855109aae116f4352139a6d69c5c0ff46 Author: 声纳 <159...@qq...> Date: 2025-06-26 (Thu, 26 Jun 2025) Changed paths: M rigs/guohetec/q900.c Log Message: ----------- Modify the buffer size of q900. c to prevent overflow Compare: https://github.com/Hamlib/Hamlib/compare/0ddc6bc8f41e...92a077585510 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: George B. <geo...@gm...> - 2025-06-25 13:27:48
|
They're 'extra levels' - look at the lines after the level list in dump_caps. On 6/25/25 05:32, Stefan Jansen wrote: > Hi, > > I compiled hamlib 4.7 out of GitHub and found the following inconsistency, at least it’s one from my point of view. > > When I type: rigctl -m1 —dump-caps > The output for „Set levels“ and „Get levels“ does not contain levels MGF, MGL and MGC. But typing: rigctl -m1 l ? > Lists these levels. > > Why are MGF, MGL and MGC mentioned in the output of „l ?“ But not in „—dump-caps“? > > > 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-06-25 09:33:21
|
Hi, I compiled hamlib 4.7 out of GitHub and found the following inconsistency, at least it’s one from my point of view. When I type: rigctl -m1 —dump-caps The output for „Set levels“ and „Get levels“ does not contain levels MGF, MGL and MGC. But typing: rigctl -m1 l ? Lists these levels. Why are MGF, MGL and MGC mentioned in the output of „l ?“ But not in „—dump-caps“? Vy 73 de Stefan, DK7STJ -- Stefan Jansen *** E-Mail: DK...@da... |
From: Nate B. <n0...@n0...> - 2025-06-24 18:26:57
|
* On 2025 24 Jun 12:16 -0500, "Christoph v. Wüllen" wrote: > > > > The size_t(3) man page states size_t is an unsigned integer and here in > > rig.c the 'needed' variable is of the size_t type. Thus 'u' should be > > correct. > > > This is (only) true for a specific system. What the size_t type > is all about is that it can be different on different systems. Sure, but as I understand from this Stack Overflow thread: https://stackoverflow.com/q/940087 This is exactly the intent of the 'z' length modifier which was introduced in C99. The discussion also concludes that the 'u' conversion specifier is correct for a size_t variable. > Do not draw conclusions for coding from a specific system. > My advice is to use > %ul and type-cast the argument to unsigned long, this should > work (as of now) on any system I know of. That thread gives your example for C90. As I agree with others that it should be standard practice to target C11/C17, I think we simply need to stop coding against C90 and move forward. 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: Christoph v. W. <DL...@da...> - 2025-06-24 17:16:17
|
> > The size_t(3) man page states size_t is an unsigned integer and here in > rig.c the 'needed' variable is of the size_t type. Thus 'u' should be > correct. > This is (only) true for a specific system. What the size_t type is all about is that it can be different on different systems. Do not draw conclusions for coding from a specific system. My advice is to use %ul and type-cast the argument to unsigned long, this should work (as of now) on any system I know of. Yours, DL1YCF. |
From: Nate B. <no...@gi...> - 2025-06-24 13:47:37
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 0ddc6bc8f41e597ba4c21df5256d6970c3d3ee6b https://github.com/Hamlib/Hamlib/commit/0ddc6bc8f41e597ba4c21df5256d6970c3d3ee6b Author: Nate Bargmann <n0...@n0...> Date: 2025-06-24 (Tue, 24 Jun 2025) Changed paths: M src/rig.c Log Message: ----------- Fix MinGW64/MSYS2 w/GCC 15.1 warning As reported by Steve, VK3SIR on the mailing list: On compilation, through a fully up-to-date MinGW64/MSYS2 environment, we receive the following warnings: .... make[3]: Entering directory '/home/sir/src/hamlib/build/src' CC rig.lo ../../src/src/rig.c: In function 'rig_init': ../../src/src/rig.c:624:45: warning: unknown conversion type character 'z' in format [-Wformat=] 624 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_struct\n", needed); | ^ ../../src/src/rig.c:624:32: warning: too many arguments for format [-Wformat-extra-args] 624 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_struct\n", needed); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../src/src/rig.c:657:45: warning: unknown conversion type character 'z' in format [-Wformat=] 657 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_cache\n", needed); | ^ ../../src/src/rig.c:657:32: warning: too many arguments for format [-Wformat-extra-args] 657 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_cache\n", needed); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CC serial.lo .... The '%z' modifier is also found in rigs/icom/icom.c but with a 'u' conversion specifier. Turns out that since 'needed' in this function is of type 'size_t' which is an unsigned integer so the 'u' is required. To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <n0...@n0...> - 2025-06-24 12:35:59
|
* On 2025 24 Jun 04:33 -0500, Stephen VK3SIR wrote: > Hi Nate (and Team), > > On compilation, through a fully up-to-date MinGW64/MSYS2 environment, we receive the following warnings: > > .... > make[3]: Entering directory '/home/sir/src/hamlib/build/src' > CC rig.lo > ../../src/src/rig.c: In function 'rig_init': > ../../src/src/rig.c:624:45: warning: unknown conversion type character 'z' in format [-Wformat=] > 624 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_struct\n", needed); > | ^ > ../../src/src/rig.c:624:32: warning: too many arguments for format [-Wformat-extra-args] > 624 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_struct\n", needed); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ../../src/src/rig.c:657:45: warning: unknown conversion type character 'z' in format [-Wformat=] > 657 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_cache\n", needed); > | ^ > ../../src/src/rig.c:657:32: warning: too many arguments for format [-Wformat-extra-args] > 657 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_cache\n", needed); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > CC serial.lo > .... > > MinGW64/MSYS2 delivers the GCC 15.1 compiler. Hi Steve, I see that "%z" shows up in just four places in the tree. The other two places are in rigs/icom/icom.c at lines 9035 and 9060. There it is followed by "u" in both cases which apparently didn't raise a warning. If you modify the lines in rig.c to match does the warning go away? > If we do not report then things become bigger later one ! All I can think of is that the compiler now enforces the use of an unsigned integer. From the printf(3) man page: z A following integer conversion corresponds to a size_t or ssize_t argument, or a following n conversion corresponds to a pointer to a size_t argument. The size_t(3) man page states size_t is an unsigned integer and here in rig.c the 'needed' variable is of the size_t type. Thus 'u' should be correct. I'll work up a patch for this. Thanks! -- "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: Stephen V. <vk...@ho...> - 2025-06-24 09:33:16
|
Hi Nate (and Team), On compilation, through a fully up-to-date MinGW64/MSYS2 environment, we receive the following warnings: .... make[3]: Entering directory '/home/sir/src/hamlib/build/src' CC rig.lo ../../src/src/rig.c: In function 'rig_init': ../../src/src/rig.c:624:45: warning: unknown conversion type character 'z' in format [-Wformat=] 624 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_struct\n", needed); | ^ ../../src/src/rig.c:624:32: warning: too many arguments for format [-Wformat-extra-args] 624 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_struct\n", needed); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../src/src/rig.c:657:45: warning: unknown conversion type character 'z' in format [-Wformat=] 657 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_cache\n", needed); | ^ ../../src/src/rig.c:657:32: warning: too many arguments for format [-Wformat-extra-args] 657 | rig_debug(RIG_DEBUG_TRACE, "Requesting %zd bytes for rig_cache\n", needed); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CC serial.lo .... MinGW64/MSYS2 delivers the GCC 15.1 compiler. If we do not report then things become bigger later one ! 73 Steve I VK3SIR |
From: Nate B. <no...@gi...> - 2025-06-23 13:20:21
|
Branch: refs/heads/Hamlib-4.6.3 Home: https://github.com/Hamlib/Hamlib Commit: a57e5583fd7903c100b8cc01c286b2a9da9096c6 https://github.com/Hamlib/Hamlib/commit/a57e5583fd7903c100b8cc01c286b2a9da9096c6 Author: markjfine <mar...@fi...> Date: 2025-06-23 (Mon, 23 Jun 2025) Changed paths: M rigs/icom/icr75.c Log Message: ----------- Correct powerstat check The R75 for some reason rejects the powerstat query and returns an error. Commented out .get_powerstat to correct that. Applications should initially assume it's on, then internally track power status, since you can still turn it off. (cherry picked from commit dc12b01aed6b4449e42ff57e71f3687b1b837a20) Commit: 867fc5886a5a9f0bee66be4fd2e5821a9cf0b00d https://github.com/Hamlib/Hamlib/commit/867fc5886a5a9f0bee66be4fd2e5821a9cf0b00d Author: Nate Bargmann <n0...@n0...> Date: 2025-06-23 (Mon, 23 Jun 2025) Changed paths: M NEWS Log Message: ----------- Update NEWS for R75 powerstat fix Compare: https://github.com/Hamlib/Hamlib/compare/b34695aab8dc...867fc5886a5a To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: markjfine <no...@gi...> - 2025-06-23 13:15:45
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: dc12b01aed6b4449e42ff57e71f3687b1b837a20 https://github.com/Hamlib/Hamlib/commit/dc12b01aed6b4449e42ff57e71f3687b1b837a20 Author: markjfine <mar...@fi...> Date: 2025-06-23 (Mon, 23 Jun 2025) Changed paths: M rigs/icom/icr75.c Log Message: ----------- Correct powerstat check The R75 for some reason rejects the powerstat query and returns an error. Commented out .get_powerstat to correct that. Applications should initially assume it's on, then internally track power status, since you can still turn it off. To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Nate B. <n0...@n0...> - 2025-06-22 20:38:42
|
Regarding a feature roadmap of sorts. I have created two new issues and pinned them at the top of the GitHub Issues page. They are #1772 and #1773 for 4.7.0 and 5.0.0 respectively. I figure the Issues page gets more reads than the Wiki does. I added a progress bar link to https://markdone.org/ which can be updated in 5% increments. Of course, that's going to be a guesstimate on everyone's part. As such, I consider the first post in each issue to be a living document. For example, if it is necessary that a feature is deemed unsuitable for a release it can be moved to the later release. Also check marks will be added upon satisfactory completion and progress updated (I'm not sure if that ability is mine alone or not). I also included GitHub usernames for each item which is primarily who made the suggestion and who will likely be the primary contributor as a reference. It's not intended to make that contributor solely responsible, however. Also, I don't want these feature lists to be too large. Right now 4.7.0 has three items and 5.0.0 has four. A couple more in each should be sufficient. Hopefully, this will help maintain focus and center the release discussions, although there is no problem having such discussions here. 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-06-22 19:57:55
|
* On 2025 18 Jun 16:26 -0500, Daniele Forsi wrote: > Nate Bargmann wrote: > > > > * On 2025 18 Jun 10:44 -0500, George Baltz wrote: > > > I don't have any problem with working just from the manual(when there is > > > one), but I don't think the FTX-1 should be the defining feature of 4.7. > > I agree on both points > > > > It is ready when it is ready. > > > > I agree. > > I agree too > > WRT a feature roadmap, I would like to see > * the Python bindings mostly complete and the other languages at least > working for some basic functionality such as set/get frequency (some > time before 5.0) I think this is reasonable for 4.7.0 > * the tests that currently use the Dummy devices working also with the > simulators (and with real hardware where it makes sense) 5.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 |