hamlib-developer Mailing List for Ham Radio Control Libraries (Page 21)
Library to control radio transceivers and receivers
Brought to you by:
n0nb
Menu
▾
▴
hamlib-developer — hamlib developers forum
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
(20) |
Nov
(41) |
Dec
|
|
From: George B. <geo...@gm...> - 2025-05-02 18:39:15
|
On 5/2/25 2:00 PM, Nate Bargmann wrote: > * On 2025 02 May 12:41 -0500, George Baltz wrote: >> Maybe I'm missing something, but did anybody ask the upstream why they were >> adding human-oriented punctuation to a computer-to-computer communication? >> Formatting should almost always be done at the final user interface, to >> allow for locality based display. > Mike, K7MDL, noted this in the initial report: > > "I first posted this to the WSJT-X dev list but this seems to be a more > proper place to file the bug. Also spoke with N3FJP about maybe removing > the comma on the AC Log side but that API is used with several apps and > could result in breakage, making the change here is the safest." > > https://github.com/Hamlib/Hamlib/issues/1704 > > Just another one of those decisions that becomes painful to fix later > on. You can say that again. Aside from being flat-out wrong for a good portion of the world, it requires special processing on both ends of the connection, and sort of defeats the purpose of XML. Sigh. 73 n3gb > 73, Nate > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
|
From: Nate B. <n0...@n0...> - 2025-05-02 18:01:00
|
* On 2025 02 May 12:41 -0500, George Baltz wrote: > Maybe I'm missing something, but did anybody ask the upstream why they were > adding human-oriented punctuation to a computer-to-computer communication? > Formatting should almost always be done at the final user interface, to > allow for locality based display. Mike, K7MDL, noted this in the initial report: "I first posted this to the WSJT-X dev list but this seems to be a more proper place to file the bug. Also spoke with N3FJP about maybe removing the comma on the AC Log side but that API is used with several apps and could result in breakage, making the change here is the safest." https://github.com/Hamlib/Hamlib/issues/1704 Just another one of those decisions that becomes painful to fix later on. 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-05-02 17:41:01
|
Maybe I'm missing something, but did anybody ask the upstream why they were adding human-oriented punctuation to a computer-to-computer communication? Formatting should almost always be done at the final user interface, to allow for locality based display. On 5/1/25 9:48 PM, Nate Bargmann via Hamlib-developer wrote: > Branch: refs/heads/master > Home: https://github.com/Hamlib/Hamlib > Commit: c8838cd3a6f4ea57ccbde8cb646c5a4fbfd82a3e > https://github.com/Hamlib/Hamlib/commit/c8838cd3a6f4ea57ccbde8cb646c5a4fbfd82a3e > Author: Nate Bargmann <n0...@n0...> > Date: 2025-05-01 (Thu, 01 May 2025) > > Changed paths: > M rigs/dummy/aclog.c > > Log Message: > ----------- > Avoid truncating AC Log frequencies above 1 GHz > > Per GitHub issue #1704, frequencies higher than 1 GHz passed from AC Log > have an embedded comma. Even though sscanf() offers the "'" (single > quote) character as a means of ignoring thousands separator, apparently > it depends on the environment variable LC_NUMERIC being set correctly > and that may not be supported on all platforms. > > This patch just parses through the string while skipping any comma that > may appear and then uses strtold() to convert to a numeric variable. It > is supected that AC Log always uses a comma as a thousands separator. > > > Commit: fe3bb8b84a47ec4e928e65fc5a9a104b89747162 > https://github.com/Hamlib/Hamlib/commit/fe3bb8b84a47ec4e928e65fc5a9a104b89747162 > Author: Nate Bargmann <n0...@n0...> > Date: 2025-05-01 (Thu, 01 May 2025) > > Changed paths: > M rigs/dummy/aclog.c > > Log Message: > ----------- > Merge pull request #1722 from N0NB/aclog_get_freq-thousands_separator > > Avoid truncating AC Log frequencies above 1 GHz > > > Compare: https://github.com/Hamlib/Hamlib/compare/12265fde9ad3...fe3bb8b84a47 > > 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: Nate B. <no...@gi...> - 2025-05-02 01:48:43
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: c8838cd3a6f4ea57ccbde8cb646c5a4fbfd82a3e https://github.com/Hamlib/Hamlib/commit/c8838cd3a6f4ea57ccbde8cb646c5a4fbfd82a3e Author: Nate Bargmann <n0...@n0...> Date: 2025-05-01 (Thu, 01 May 2025) Changed paths: M rigs/dummy/aclog.c Log Message: ----------- Avoid truncating AC Log frequencies above 1 GHz Per GitHub issue #1704, frequencies higher than 1 GHz passed from AC Log have an embedded comma. Even though sscanf() offers the "'" (single quote) character as a means of ignoring thousands separator, apparently it depends on the environment variable LC_NUMERIC being set correctly and that may not be supported on all platforms. This patch just parses through the string while skipping any comma that may appear and then uses strtold() to convert to a numeric variable. It is supected that AC Log always uses a comma as a thousands separator. Commit: fe3bb8b84a47ec4e928e65fc5a9a104b89747162 https://github.com/Hamlib/Hamlib/commit/fe3bb8b84a47ec4e928e65fc5a9a104b89747162 Author: Nate Bargmann <n0...@n0...> Date: 2025-05-01 (Thu, 01 May 2025) Changed paths: M rigs/dummy/aclog.c Log Message: ----------- Merge pull request #1722 from N0NB/aclog_get_freq-thousands_separator Avoid truncating AC Log frequencies above 1 GHz Compare: https://github.com/Hamlib/Hamlib/compare/12265fde9ad3...fe3bb8b84a47 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-05-01 17:18:32
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 5cf875582756aec6c4d5f97267a37374e05541f1 https://github.com/Hamlib/Hamlib/commit/5cf875582756aec6c4d5f97267a37374e05541f1 Author: Nate Bargmann <n0...@n0...> Date: 2025-05-01 (Thu, 01 May 2025) Changed paths: M configure.ac M macros/ax_lua.m4 Log Message: ----------- Update ax_lua.m4 macro file Per GitHub issue #1712, the older macro file was causing bootstrap issues on Fedora 42. Commit: 12265fde9ad35e36ebdf591f0d88421dd08e121c https://github.com/Hamlib/Hamlib/commit/12265fde9ad35e36ebdf591f0d88421dd08e121c Author: Nate Bargmann <n0...@n0...> Date: 2025-05-01 (Thu, 01 May 2025) Changed paths: M configure.ac M macros/ax_lua.m4 Log Message: ----------- Merge pull request #1720 from N0NB/lua_macro Update ax_lua.m4 macro file Compare: https://github.com/Hamlib/Hamlib/compare/7c5c71588881...12265fde9ad3 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-05-01 17:18:12
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: a395b91be6bd19d760e57005ecb8079b15af9ede https://github.com/Hamlib/Hamlib/commit/a395b91be6bd19d760e57005ecb8079b15af9ede Author: Kenji Rikitake <ken...@ac...> Date: 2025-05-01 (Thu, 01 May 2025) Changed paths: M rigs/icom/ic7300.c M rigs/icom/icom.c Log Message: ----------- Add support of setting IC-705 WFM mode On IC-705, setting WFM mode via ICOM CI-V command 0x26 does not work. This patch implements a workaround using CI-V command 0x06 instead via icom_set_mode_without_data for IC-705 setting mode WFM. Commit: 7c5c71588881fe9c81eb9c0ce15544703208db44 https://github.com/Hamlib/Hamlib/commit/7c5c71588881fe9c81eb9c0ce15544703208db44 Author: Nate Bargmann <n0...@n0...> Date: 2025-05-01 (Thu, 01 May 2025) Changed paths: M rigs/icom/ic7300.c M rigs/icom/icom.c Log Message: ----------- Merge pull request #1719 from jj1bdx/jj1bdx-ic705-wfm Add support of setting IC-705 WFM mode Compare: https://github.com/Hamlib/Hamlib/compare/edef6206f7e1...7c5c71588881 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-05-01 17:17:32
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 037c4953ed1f7d3b31b2c09d48dbf9e79210b8b1 https://github.com/Hamlib/Hamlib/commit/037c4953ed1f7d3b31b2c09d48dbf9e79210b8b1 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-30 (Wed, 30 Apr 2025) Changed paths: M simulators/simatd578.c M simulators/simeasycomm.c M simulators/simelecraft.c M simulators/simelecraftk4.c M simulators/simft1000.c M simulators/simft450.c M simulators/simft710.c M simulators/simft736.c M simulators/simft747gx.c M simulators/simft817.c M simulators/simft818.c M simulators/simft847.c M simulators/simft897.c M simulators/simft990.c M simulators/simft991.c M simulators/simftdx101.c M simulators/simftdx1200.c M simulators/simftdx3000.c M simulators/simftdx5000.c M simulators/simic2730.c M simulators/simic275.c M simulators/simic7000.c M simulators/simic705.c M simulators/simic7100.c M simulators/simic7200.c M simulators/simic7300.c M simulators/simic7600.c M simulators/simic7610.c M simulators/simic7700.c M simulators/simic7851.c M simulators/simic905.c M simulators/simic910.c M simulators/simic9100.c M simulators/simic9700.c M simulators/simicgeneric.c M simulators/simicr8600.c M simulators/simid5100.c M simulators/simjupiter.c M simulators/simkenwood.c M simulators/simmicom.c M simulators/simorion.c M simulators/simpmr171.c M simulators/simpowersdr.c M simulators/simqrplabs.c M simulators/simrotorez.c M simulators/simspid.c M simulators/simtmd700.c M simulators/simtmd710.c M simulators/simtrusdx.c M simulators/simts450.c M simulators/simts590.c M simulators/simts890.c M simulators/simts950.c M simulators/simts990.c M simulators/simxiegug90.c M simulators/simxiegux108g.c M simulators/simxiegux6100.c M simulators/simyaesu.c Log Message: ----------- Fix name of function in error messages Fixed with: perl -pe s/pstname/ptsname/ -i *.c Commit: 3448c735b064dccd2aea26d5b15c9a30d06a1650 https://github.com/Hamlib/Hamlib/commit/3448c735b064dccd2aea26d5b15c9a30d06a1650 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-30 (Wed, 30 Apr 2025) Changed paths: M simulators/simatd578.c M simulators/simeasycomm.c M simulators/simelecraft.c M simulators/simelecraftk4.c M simulators/simft1000.c M simulators/simft450.c M simulators/simft710.c M simulators/simft736.c M simulators/simft747gx.c M simulators/simft817.c M simulators/simft818.c M simulators/simft847.c M simulators/simft897.c M simulators/simft990.c M simulators/simft991.c M simulators/simftdx101.c M simulators/simftdx1200.c M simulators/simftdx3000.c M simulators/simftdx5000.c M simulators/simic2730.c M simulators/simic275.c M simulators/simic7000.c M simulators/simic705.c M simulators/simic7100.c M simulators/simic7200.c M simulators/simic7300.c M simulators/simic7600.c M simulators/simic7610.c M simulators/simic7700.c M simulators/simic7851.c M simulators/simic905.c M simulators/simic910.c M simulators/simic9100.c M simulators/simic9700.c M simulators/simicgeneric.c M simulators/simicr8600.c M simulators/simid5100.c M simulators/simjupiter.c M simulators/simkenwood.c M simulators/simmicom.c M simulators/simorion.c M simulators/simpmr171.c M simulators/simpowersdr.c M simulators/simqrplabs.c M simulators/simrotorez.c M simulators/simspid.c M simulators/simtmd700.c M simulators/simtmd710.c M simulators/simtrusdx.c M simulators/simts450.c M simulators/simts590.c M simulators/simts890.c M simulators/simts950.c M simulators/simts990.c M simulators/simxiegug90.c M simulators/simxiegux108g.c M simulators/simxiegux6100.c M simulators/simyaesu.c Log Message: ----------- Remove non-working compilation instructions from comments Some instructions were a copy and paste error, some did not link to Hamlib. Compile all simulators with: make -C simulators check or compile a single simulator replacing "check" with the name of the simulator. Fixed with: perl -pe 's,// gcc.*\n,,' -i *.c perl -pe 's,// On mingw.*\n,,' -i *.c Commit: aeb827a2f1dab1d7a481e873890e8beee0ddb8ab https://github.com/Hamlib/Hamlib/commit/aeb827a2f1dab1d7a481e873890e8beee0ddb8ab Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-30 (Wed, 30 Apr 2025) Changed paths: M bindings/ignore.swg Log Message: ----------- Remove duplicated line Commit: 24eafbd2a4affe66e6cef0af38343652a4a54f09 https://github.com/Hamlib/Hamlib/commit/24eafbd2a4affe66e6cef0af38343652a4a54f09 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-30 (Wed, 30 Apr 2025) Changed paths: M src/rig.c Log Message: ----------- Fix Doxygen comment The description of hamlib_version was attached to hamlib_license and hamlib_license was missing the description. Commit: 8feb174711bcc6756e46547837116499b80e2057 https://github.com/Hamlib/Hamlib/commit/8feb174711bcc6756e46547837116499b80e2057 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-30 (Wed, 30 Apr 2025) Changed paths: M include/hamlib/rig.h M src/debug.c Log Message: ----------- Fix typos Commit: 56b075ab452c92017a9a144c74dcebd5271c5fa3 https://github.com/Hamlib/Hamlib/commit/56b075ab452c92017a9a144c74dcebd5271c5fa3 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-30 (Wed, 30 Apr 2025) Changed paths: M include/hamlib/rig.h Log Message: ----------- Fix Doxygen comment It is about the tpyedef, not the defines. Commit: c1788e2cf86edfad398ff6eb7e7e5389cc58cf66 https://github.com/Hamlib/Hamlib/commit/c1788e2cf86edfad398ff6eb7e7e5389cc58cf66 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-30 (Wed, 30 Apr 2025) Changed paths: M src/misc.c Log Message: ----------- Fix names of parameters in Doxygen comments Commit: bd5ed18bddbef070b893ed278c6e12d6706739f3 https://github.com/Hamlib/Hamlib/commit/bd5ed18bddbef070b893ed278c6e12d6706739f3 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-30 (Wed, 30 Apr 2025) Changed paths: M include/hamlib/rig.h Log Message: ----------- Add documentation for RIG_CONF_END Fixes: warning: explicit link request to 'RIG_CONF_END' could not be resolved Commit: dda30532b512e34d65308c03dd68205de09ba2b8 https://github.com/Hamlib/Hamlib/commit/dda30532b512e34d65308c03dd68205de09ba2b8 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-30 (Wed, 30 Apr 2025) Changed paths: M include/hamlib/rig.h M src/extamp.c M src/rig.c M src/rot_ext.c Log Message: ----------- Add cross references hash mark for Doxygen Commit: edef6206f7e11b74237e927939a5b1ea6ceecfdb https://github.com/Hamlib/Hamlib/commit/edef6206f7e11b74237e927939a5b1ea6ceecfdb Author: Nate Bargmann <n0...@n0...> Date: 2025-05-01 (Thu, 01 May 2025) Changed paths: M bindings/ignore.swg M include/hamlib/rig.h M simulators/simatd578.c M simulators/simeasycomm.c M simulators/simelecraft.c M simulators/simelecraftk4.c M simulators/simft1000.c M simulators/simft450.c M simulators/simft710.c M simulators/simft736.c M simulators/simft747gx.c M simulators/simft817.c M simulators/simft818.c M simulators/simft847.c M simulators/simft897.c M simulators/simft990.c M simulators/simft991.c M simulators/simftdx101.c M simulators/simftdx1200.c M simulators/simftdx3000.c M simulators/simftdx5000.c M simulators/simic2730.c M simulators/simic275.c M simulators/simic7000.c M simulators/simic705.c M simulators/simic7100.c M simulators/simic7200.c M simulators/simic7300.c M simulators/simic7600.c M simulators/simic7610.c M simulators/simic7700.c M simulators/simic7851.c M simulators/simic905.c M simulators/simic910.c M simulators/simic9100.c M simulators/simic9700.c M simulators/simicgeneric.c M simulators/simicr8600.c M simulators/simid5100.c M simulators/simjupiter.c M simulators/simkenwood.c M simulators/simmicom.c M simulators/simorion.c M simulators/simpmr171.c M simulators/simpowersdr.c M simulators/simqrplabs.c M simulators/simrotorez.c M simulators/simspid.c M simulators/simtmd700.c M simulators/simtmd710.c M simulators/simtrusdx.c M simulators/simts450.c M simulators/simts590.c M simulators/simts890.c M simulators/simts950.c M simulators/simts990.c M simulators/simxiegug90.c M simulators/simxiegux108g.c M simulators/simxiegux6100.c M simulators/simyaesu.c M src/debug.c M src/extamp.c M src/misc.c M src/rig.c M src/rot_ext.c Log Message: ----------- Merge pull request #1718 from dforsi/fix/typos Fix/typos Compare: https://github.com/Hamlib/Hamlib/compare/d03cde33b053...edef6206f7e1 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <n0...@n0...> - 2025-04-27 11:57:28
|
All three of those have now been closed/merged. 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-04-27 11:56:13
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 12c538fc1424f8ae5e34d27852cf48e0e9f0a7eb https://github.com/Hamlib/Hamlib/commit/12c538fc1424f8ae5e34d27852cf48e0e9f0a7eb Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-22 (Tue, 22 Apr 2025) Changed paths: M cppcheck.sh Log Message: ----------- Remove duplicated cppcheck suppressions Fixes: cppcheck: error: suppression '*:extra/gnuradio/wfm.h' already exists cppcheck: error: suppression '*:extra/gnuradio/HrAGC.h' already exists Commit: d03cde33b05367231b69309064edae9aef402f5a https://github.com/Hamlib/Hamlib/commit/d03cde33b05367231b69309064edae9aef402f5a Author: Nate Bargmann <n0...@n0...> Date: 2025-04-27 (Sun, 27 Apr 2025) Changed paths: M cppcheck.sh Log Message: ----------- Merge pull request #1714 from dforsi/fix/cppcheck Remove duplicated cppcheck suppressions Compare: https://github.com/Hamlib/Hamlib/compare/4f6c61719cd1...d03cde33b053 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-04-27 11:47:36
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 535fb6e2bd8ae96cd561ee6b7369672234d4bd24 https://github.com/Hamlib/Hamlib/commit/535fb6e2bd8ae96cd561ee6b7369672234d4bd24 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-26 (Sat, 26 Apr 2025) Changed paths: M include/hamlib/rig.h M rigs/codan/README.codan Log Message: ----------- Fix typos Commit: 4f6c61719cd1962f8942f5044e43f868cf54cb26 https://github.com/Hamlib/Hamlib/commit/4f6c61719cd1962f8942f5044e43f868cf54cb26 Author: Nate Bargmann <n0...@n0...> Date: 2025-04-27 (Sun, 27 Apr 2025) Changed paths: M include/hamlib/rig.h M rigs/codan/README.codan Log Message: ----------- Merge pull request #1715 from dforsi/fix/typos Fix typos Compare: https://github.com/Hamlib/Hamlib/compare/5d81ea38bbdf...4f6c61719cd1 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Daniele F. <iu...@gm...> - 2025-04-26 20:40:43
|
Hello, this issue can be closed because the author wrote that it is fixed https://github.com/Hamlib/Hamlib/issues/1449 some of the issues I was looking at where had already a milestone of version 4.7 set by Mike and some other will need some time, so except for my pull requests https://github.com/Hamlib/Hamlib/pull/1714 https://github.com/Hamlib/Hamlib/pull/1715 I have nothing more to push for version 4.6.3 -- 73 de IU5HKX Daniele |
|
From: Daniele F. <iu...@gm...> - 2025-04-25 18:05:12
|
This is the first time that I asked to get an issue assigned, but it's useless because I can't do anything more than a random github user, I can't even get an issue unassigned! The next time I will just comment on an issue to tell that I'm working on it, and ping Nate only if it can be closed. -- 73 de IU5HKX Daniele |
|
From: Nate B. <n0...@n0...> - 2025-04-23 22:06:38
|
* On 2025 23 Apr 16:57 -0500, Daniele Forsi wrote: > Nate wrote: > > > Perhaps if you comment then I can assign you??? > > I commented to this one: > https://github.com/Hamlib/Hamlib/issues/1094 That did the trick as I was able to assign that issue to you. But, I just assigned #1624 to you as well, I just had to type the first letter of your username into the search box and it popped into the selection box. It helps if I pay attention. 🤨 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: Daniele F. <iu...@gm...> - 2025-04-23 21:57:20
|
Nate wrote: > Perhaps if you comment then I can assign you??? I commented to this one: https://github.com/Hamlib/Hamlib/issues/1094 -- 73 de IU5HKX Daniele |
|
From: Nate B. <n0...@n0...> - 2025-04-23 03:20:08
|
* On 2025 22 Apr 15:32 -0500, Daniele Forsi wrote: > Nate wrote: > > > I sent you an invitation to the project. Once accepted we'll see what > > access you have. > > there is no link to assign an issue to myself and no cog icon to list people The Web site shows that you now have read access to the repository but I see nothing for the issues. Perhaps that is only a permission given to the admin? It does show you in the list of possible assignees at the top but I opened issue 1624 and you are not on the list. However, rz4ag is on the list because that user left a comment. Perhaps if you comment then I can assign you??? 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: Daniele F. <iu...@gm...> - 2025-04-22 20:31:18
|
Nate wrote: > I sent you an invitation to the project. Once accepted we'll see what > access you have. there is no link to assign an issue to myself and no cog icon to list people -- 73 de IU5HKX Daniele |
|
From: George B. <geo...@gm...> - 2025-04-22 10:13:56
|
'E' for emulated - the rig does not have that function, but it is computed in Hamlib. On 4/22/25 4:24 AM, Richard Emling wrote: > Hello All. > > > Another of my newbie questions, but what does the E behind certain > caps mean? Yes/No I understand, what does tE mean? > > > Thanks for clarification. > > |
|
From: Richard E. <DO...@ho...> - 2025-04-22 08:24:51
|
Hello All. Another of my newbie questions, but what does the E behind certain caps mean? Yes/No I understand, what does tE mean? Thanks for clarification. -- 73 Richard, DO9RE |
|
From: Nate B. <no...@gi...> - 2025-04-22 03:03:48
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 923a789c29ad81abfbb7149f80cebd51afc6b756 https://github.com/Hamlib/Hamlib/commit/923a789c29ad81abfbb7149f80cebd51afc6b756 Author: Nate Bargmann <n0...@n0...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M rigs/dummy/aclog.c Log Message: ----------- Fix sscanf() truncating input from thousands separator Per Github issue #1704, N3FJP logger sends a string with an embedded comma for frequencies above 1 GHz resulting in such frequencies being truncated. This patch uses the optional apostrophe character in the sscanf() format string to ignore the thousands separator. A possible bug is when the locale of the system on which libhamlib is executing uses a dot for the thousands separator rather than a comma. It is unclear if the N3FJP software obeys such locales or not. If this turns out to be an issue then this fix will need to be reconsidered. Commit: 5d81ea38bbdfd92e680995057b8ed46f53f5a8d8 https://github.com/Hamlib/Hamlib/commit/5d81ea38bbdfd92e680995057b8ed46f53f5a8d8 Author: Nate Bargmann <n0...@n0...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M rigs/dummy/aclog.c Log Message: ----------- Merge pull request #1710 from N0NB/aclog_get_freq-thousands_separator Fix sscanf() truncating input from thousands separator Compare: https://github.com/Hamlib/Hamlib/compare/9aed2637a63a...5d81ea38bbdf To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-04-21 22:28:11
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: ba011462efc37b12d18d5bf59d0e0a7b117fceeb https://github.com/Hamlib/Hamlib/commit/ba011462efc37b12d18d5bf59d0e0a7b117fceeb Author: George Baltz N3GB <Geo...@gm...> Date: 2025-04-20 (Sun, 20 Apr 2025) Changed paths: M NEWS Log Message: ----------- Add dates for recent releases Commit: 8150583541e4230c6b76dc38209b58694f6e6f99 https://github.com/Hamlib/Hamlib/commit/8150583541e4230c6b76dc38209b58694f6e6f99 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-04-20 (Sun, 20 Apr 2025) Changed paths: M tests/ampctl.c M tests/ampctld.c M tests/rigctl.c M tests/rigctld.c M tests/rotctl.c M tests/rotctld.c Log Message: ----------- Drop redundant token lookups. Commit: 1f707ab31ef5ceebd552e1292d541fd9baed55a1 https://github.com/Hamlib/Hamlib/commit/1f707ab31ef5ceebd552e1292d541fd9baed55a1 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-04-20 (Sun, 20 Apr 2025) Changed paths: M tests/rigmem.c M tests/rigswr.c Log Message: ----------- Make local functions static. Commit: 4f3f308d7af83316eb8e3aebe48abb960f9e9e11 https://github.com/Hamlib/Hamlib/commit/4f3f308d7af83316eb8e3aebe48abb960f9e9e11 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M rigs/kenwood/ts890s.c Log Message: ----------- Enable rig_vfo_op for TS-890S Commit: 9aed2637a63abb8b175a21b06942cca5308e7527 https://github.com/Hamlib/Hamlib/commit/9aed2637a63abb8b175a21b06942cca5308e7527 Author: Nate Bargmann <n0...@n0...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M NEWS M rigs/kenwood/ts890s.c M tests/ampctl.c M tests/ampctld.c M tests/rigctl.c M tests/rigctld.c M tests/rigmem.c M tests/rigswr.c M tests/rotctl.c M tests/rotctld.c Log Message: ----------- Merge pull request #1708 from GeoBaltz/fix27 Minor fixes/cleanups for 4.6.3 Compare: https://github.com/Hamlib/Hamlib/compare/8f641b2b6a4f...9aed2637a63a To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-04-21 22:23:48
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: d724f04163d0bfe29717b11efb8f044025204807 https://github.com/Hamlib/Hamlib/commit/d724f04163d0bfe29717b11efb8f044025204807 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M doc/man1/ampctld.1 Log Message: ----------- Remove duplicated text Commit: f890fcf6482c8197b3c29f716cad7370a9806d6b https://github.com/Hamlib/Hamlib/commit/f890fcf6482c8197b3c29f716cad7370a9806d6b Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Fix groff syntax A leading space prevents joining two lines. Commit: cd092fc65421a1494abde9da5c8dbe5b9eed0eb8 https://github.com/Hamlib/Hamlib/commit/cd092fc65421a1494abde9da5c8dbe5b9eed0eb8 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 M include/hamlib/rig.h Log Message: ----------- Fix list of parameters for get_func/set_func Fixes: OVF_STATUS was spelled wrong, SYNC was missing, SLICE is not available. Uses the list returned by \get_func ? sorted alphabetically to be more user friendly and to easily spot any missing item in future. Commit: f9deb43e803a4177440f69a18136e64efe7fd11f https://github.com/Hamlib/Hamlib/commit/f9deb43e803a4177440f69a18136e64efe7fd11f Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Fix list of parameters for get_level/set_level Fixes: BAND_SELECT and COMP_METER were spelled wrong, NB was spelled NQ, USB_AF_INPUT, AGC_TIME, MGL, MGF, MGC, were missing. Uses the list returned by \get_level ? sorted alphabetically to be more user friendly and to easily spot any missing item in future. Commit: 19de592d3ca0a1a1afb52be874b198eb26619c20 https://github.com/Hamlib/Hamlib/commit/19de592d3ca0a1a1afb52be874b198eb26619c20 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Fix list of parameters for get_parm/set_parm Fixes: AFIF_ACC, AFIF_LAN, AFIF_WLAN were missing. Uses the list returned by \get_parm ? sorted alphabetically to be more user friendly and to easily spot any missing item in future. Commit: 69f2c609393437b126d3e620f025a77026d83192 https://github.com/Hamlib/Hamlib/commit/69f2c609393437b126d3e620f025a77026d83192 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M doc/man1/rigctlsync.1 Log Message: ----------- Add missing diagram Commit: 576cfb66b1efd20c9bcd5057a15023de34a0845b https://github.com/Hamlib/Hamlib/commit/576cfb66b1efd20c9bcd5057a15023de34a0845b Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Fix typos Commit: 735d54e318da14309308e9bb0b35ac3b39729335 https://github.com/Hamlib/Hamlib/commit/735d54e318da14309308e9bb0b35ac3b39729335 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Sync text between man rigctl and man rigctld Commit: 0323d3a06a4ebe48c342a86972bb9976949fdde5 https://github.com/Hamlib/Hamlib/commit/0323d3a06a4ebe48c342a86972bb9976949fdde5 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M doc/man1/rigctld.1 Log Message: ----------- Add description for -w/--twiddle_rit Commit: faae6b5405fd24c7f10810d46f6684042ab18bab https://github.com/Hamlib/Hamlib/commit/faae6b5405fd24c7f10810d46f6684042ab18bab Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M tests/rigctld.c Log Message: ----------- Add missing arguments to command line options Commit: 2c0067d51062b7d37f66274e1ecee6a2869b8f5e https://github.com/Hamlib/Hamlib/commit/2c0067d51062b7d37f66274e1ecee6a2869b8f5e Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M tests/rigctld.c Log Message: ----------- Remove unused command line short options -M and -N The long options --multicast-addr and --multicast-port were removed in commit c8c8869a. Commit: cd82f08ec56b153029067be4a616bf0fd136b6a4 https://github.com/Hamlib/Hamlib/commit/cd82f08ec56b153029067be4a616bf0fd136b6a4 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M tests/rigctld.c Log Message: ----------- Add missing command line short option -b for --bind-all Commit: 7f717d520d0e7adbb436f258e03e8ce6105d65f9 https://github.com/Hamlib/Hamlib/commit/7f717d520d0e7adbb436f258e03e8ce6105d65f9 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 M tests/rigctld.c Log Message: ----------- Add that passwords aren't implemented Commit: cee0fcb2cb621deba277fe9e2c4f8283f43b136a https://github.com/Hamlib/Hamlib/commit/cee0fcb2cb621deba277fe9e2c4f8283f43b136a Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M tests/rigctld.c Log Message: ----------- Add -b, --bind-all to --help text Commit: 8f641b2b6a4fabe4d4f3062f4fa591ba2e7a672f https://github.com/Hamlib/Hamlib/commit/8f641b2b6a4fabe4d4f3062f4fa591ba2e7a672f Author: Nate Bargmann <n0...@n0...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M doc/man1/ampctld.1 M doc/man1/rigctl.1 M doc/man1/rigctld.1 M doc/man1/rigctlsync.1 M include/hamlib/rig.h M tests/rigctld.c Log Message: ----------- Merge pull request #1707 from dforsi/fix/manpage Fix/manpage Compare: https://github.com/Hamlib/Hamlib/compare/49af447f27ff...8f641b2b6a4f To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Richard E. <DO...@ho...> - 2025-04-21 19:20:48
|
And, in addition, if there is no command to query the possible values for a given level, would I need to program a separate function for each level, checking if there is an own section in the caps-dump for it? Am 21.04.2025 um 19:51 schrieb Richard Emling: > Hello, > > I have noticed in the dump-caps that the value range is specified > behind each level in the Set Level functions. However, further up, I > see explicit specifications for some levels that contradict those > behind the Set Level indication. For example: > > Preamp: 10dB > Attenuator: 10dB 20dB 30dB > > But further down: > Set level: PREAMP(0..0/0) ATT(0..0/0) ... > > Why are specific numbers given for the value range above, but only > zeros are shown in the Set Level section? > > Additionally, I would like to know: > Using L ?, one can query which levels can be set at all. Is there a > way to interactively query the possible value range for each level, or > do I always have to determine this from the --dump-caps? > > Thank you and best regards. > -- 73 Richard, DO9RE |
|
From: Richard E. <DO...@ho...> - 2025-04-21 17:52:20
|
Hello, I have noticed in the dump-caps that the value range is specified behind each level in the Set Level functions. However, further up, I see explicit specifications for some levels that contradict those behind the Set Level indication. For example: Preamp: 10dB Attenuator: 10dB 20dB 30dB But further down: Set level: PREAMP(0..0/0) ATT(0..0/0) ... Why are specific numbers given for the value range above, but only zeros are shown in the Set Level section? Additionally, I would like to know: Using L ?, one can query which levels can be set at all. Is there a way to interactively query the possible value range for each level, or do I always have to determine this from the --dump-caps? Thank you and best regards. -- 73 Richard, DO9RE |
|
From: Richard E. <DO...@ho...> - 2025-04-21 17:39:12
|
So, may it be, that this feature is just not implemented in the Dummy transceiver and therefore G UP doesn't alter the frequency? In a few days I will be back at home and try with a real radio. But, if the Dummy transceiver doesn't support it, it should. Just for demo purposes at all. Am 21.04.2025 um 19:31 schrieb George Baltz: > > On 4/20/25 2:36 PM, Richard Emling wrote: >> >> Hello. >> >> >> I'm probably too dumb to understand, but how exactly does the G >> command or vfo_op work? For example, I enter G VFOA UP and then check >> the frequency with f, but it hasn't changed. Please explain it to me. >> >> >> Thanks >> >> >> Richard >> > As I said, it's very dependent on what the rig can do. On my TS-890S, > if I give rigctl 'G UP', it will move the frequency up by one 'step', > where step may be different depending on the mode it is in - on CW it > may be 10 Hz, SSB 100 Hz, AM 10 kHz. And there are menu entries that > also can change some tuning step sizes - I'm not sure how they > interact, and I've been using the rig for years. > > > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer > -- 73 Richard, DO9RE |
|
From: George B. <geo...@gm...> - 2025-04-21 17:32:12
|
On 4/20/25 2:36 PM, Richard Emling wrote: > > Hello. > > > I'm probably too dumb to understand, but how exactly does the G > command or vfo_op work? For example, I enter G VFOA UP and then check > the frequency with f, but it hasn't changed. Please explain it to me. > > > Thanks > > > Richard > As I said, it's very dependent on what the rig can do. On my TS-890S, if I give rigctl 'G UP', it will move the frequency up by one 'step', where step may be different depending on the mode it is in - on CW it may be 10 Hz, SSB 100 Hz, AM 10 kHz. And there are menu entries that also can change some tuning step sizes - I'm not sure how they interact, and I've been using the rig for years. |
33 messages has been excluded from this view by a project administrator.
