hamlib-developer Mailing List for Ham Radio Control Libraries (Page 13)
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
(17) |
Sep
|
Oct
|
Nov
|
Dec
|
|
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. |
|
From: Daniele F. <iu...@gm...> - 2025-04-21 17:10:54
|
Richard wrote: > how exactly does the G command or vfo_op work? For example, I enter G VFOA UP the argument for that command is just the operation; in your example: G UP -- 73 de IU5HKX Daniele |
|
From: Nate B. <n0...@n0...> - 2025-04-21 02:23:02
|
* On 2025 20 Apr 10:48 -0500, Daniele Forsi wrote: > Nate wrote: > > > I invite anyone who chooses to work on an issue to assign themself to > > it. > > I would like to look at the issues related to Python (there are 11 of them): > https://github.com/Hamlib/Hamlib/issues?q=is%3Aissue%20state%3Aopen%20python > > since assigning an issue requires read access to the repository, can > you give read access to user "dforsi"? > Or assign all of them, but I'd prefer to own an issue only if I can work on it I sent you an invitation to the project. Once accepted we'll see what access you have. 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-20 23:15:46
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 864c60b86d2e032470af0b16feec90e91962e00d https://github.com/Hamlib/Hamlib/commit/864c60b86d2e032470af0b16feec90e91962e00d Author: Callum McEwen (VK5MCA) <Cal...@us...> Date: 2025-04-01 (Tue, 01 Apr 2025) Changed paths: M rigs/codan/codan.c Log Message: ----------- Update codan.c Updated ptt command to CICS Commit: 5b85a716fc3e1c38aeeb496ee0b27b6a2ed97cfd https://github.com/Hamlib/Hamlib/commit/5b85a716fc3e1c38aeeb496ee0b27b6a2ed97cfd Author: Callum McEwen (VK5MCA) <Cal...@us...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M rigs/codan/README.codan Log Message: ----------- Update README.codan Commit: 21bf64b7ba3296f8b00512f0f6604ee1f0c45736 https://github.com/Hamlib/Hamlib/commit/21bf64b7ba3296f8b00512f0f6604ee1f0c45736 Author: Callum McEwen (VK5MCA) <Cal...@us...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M rigs/codan/README.codan Log Message: ----------- Add V3.51 firmware comment Commit: a3da9bbe4260d6dcd52ccb342cec056b9ca7e584 https://github.com/Hamlib/Hamlib/commit/a3da9bbe4260d6dcd52ccb342cec056b9ca7e584 Author: Callum McEwen (VK5MCA) <Cal...@us...> Date: 2025-04-21 (Mon, 21 Apr 2025) Changed paths: M rigs/codan/codan.c Log Message: ----------- Update comments on codan_set_ptt Commit: 49af447f27ffd1c481e72293d04e9fa1dd56de53 https://github.com/Hamlib/Hamlib/commit/49af447f27ffd1c481e72293d04e9fa1dd56de53 Author: Nate Bargmann <n0...@n0...> Date: 2025-04-20 (Sun, 20 Apr 2025) Changed paths: M rigs/codan/README.codan M rigs/codan/codan.c Log Message: ----------- Merge pull request #1703 from CallumMcEwen/master Updates to codan_set_ptt command and README.md Compare: https://github.com/Hamlib/Hamlib/compare/071416d0d40c...49af447f27ff To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Richard E. <DO...@ho...> - 2025-04-20 18:37:00
|
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 Am 19.04.2025 um 19:53 schrieb George Baltz: > On 4/17/25 2:11 PM, Stefan Jansen wrote: >> Hi David, hi list, >> >> First, let men introduce myself. I am Stefan, living in Germany and >> developing together with Richard on a piece of software that uses >> hamlib and mainly rigctl. >> >> Now back to the topic if this thread: >> >> David, it is clear that you do not have to query the current >> frequency before setting an arbitrary new value. But what if you want >> to just increase the current frequency by, let’s say, 1kHz? To do so, >> would you query the current frequency with the „f“ command, add 1000 >> to it and set the new value with „F“? Or is there a command to just >> increment or decrement the current frequency by a given step size? >> > See rig_vfo_op(), which does have UP/DOWN operations. Implementation > may depend on what each rig can do. >> Vy 73 de Stefan, DK7STJ >> >> -- >> Stefan Jansen *** E-Mail: DK7STJ@darc.d > > -- > > 73 n3gb > > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer -- 73 Richard, DO9RE |
|
From: Daniele F. <iu...@gm...> - 2025-04-20 15:48:07
|
Nate wrote: > I invite anyone who chooses to work on an issue to assign themself to > it. I would like to look at the issues related to Python (there are 11 of them): https://github.com/Hamlib/Hamlib/issues?q=is%3Aissue%20state%3Aopen%20python since assigning an issue requires read access to the repository, can you give read access to user "dforsi"? Or assign all of them, but I'd prefer to own an issue only if I can work on it thank you -- 73 de IU5HKX Daniele |
|
From: Nate B. <no...@gi...> - 2025-04-20 02:35:53
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: b141c142709c327f58b29fb136119657237c912f https://github.com/Hamlib/Hamlib/commit/b141c142709c327f58b29fb136119657237c912f Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-04-19 (Sat, 19 Apr 2025) Changed paths: M tests/rigctl.c M tests/rigctlcom.c Log Message: ----------- Make help strings more similar Fixes text indent and verbs. Commit: 071416d0d40c42f294064ccd7a3682bdd5a82cbc https://github.com/Hamlib/Hamlib/commit/071416d0d40c42f294064ccd7a3682bdd5a82cbc Author: Nate Bargmann <n0...@n0...> Date: 2025-04-19 (Sat, 19 Apr 2025) Changed paths: M tests/rigctl.c M tests/rigctlcom.c Log Message: ----------- Merge pull request #1699 from dforsi/fix/help-strings Make help strings more similar Compare: https://github.com/Hamlib/Hamlib/compare/1ee8fc9bd18a...071416d0d40c To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Randy R. <ran...@gm...> - 2025-04-19 22:46:01
|
Add: -c 0xA2 to your command line. -c, --civaddr=id Use id as the CI-V address to communicate with the rig. Only useful for Icom and some Ten-Tec rigs. Note: The id is in decimal notation, unless prefixed by 0x, in which case it is hexadecimal. Randy KB0NAV On 4/19/25 19:48, Bob Nazro wrote: > Setting up GPREDICT with my IC-7900. It's communicating, but I get > several errors. Not sure what to do. Are there additional parameters > that I need to add to the command line? > > Radio is setup and COM 7 is 115200 baud.Any help is greatly appreciated. > > > > This is the command line I am running on the Windows desktop > > "C:\Program Files\hamlib-w64-4.6.2\bin\rigctld.exe" -m 3081 -r COM7 -t > 4532 -s 115200 -vvv > > This is what I get when I run it: > > icom_get_powerstat: get freq failed, assuming power is off > > icom_rig_open: rig error getting frequency retry=1, > err=read_string_generic called, rxmax=200 direct=1, expected_len=1 > > read_string_generic(): RX 6 characters, direct=1 > > *****5:frame.c(452):icom_one_transaction returning(-9) Command > rejected by the rig > > Command rejected by the rig > > ****4:frame.c(556):icom_transaction returning(-9) Command rejected by > the rig > > rig_get_freq(2597): freqMainA=0, modeMainA=, widthMainA=0 > > rig_get_freq(2597): freqMainB=0, modeMainB=, widthMainB=0 > > rig_get_freq(2597): freqSubA=0, modeSubA=, widthSubA=0 > > rig_get_freq(2597): freqSubB=0, modeSubB=, widthSubB=0 > > rig_get_cache(328): vfo=currVFO, current_vfo=currVFO > > rig_get_cache(523): vfo=VFOA, freq=0, mode=, width=0 > > rig_set_cache_freq(171): vfo=currVFO, current_vfo=currVFO > > ***3:rig_get_freq: elapsed=0ms > > ***3:rig.c(2714):rig_get_freq returning(-9) Command rejected by the rig > > Command rejected by the rig > > Command rejected by the rig > > icom_rig_open: rig error getting frequency retry=0, > err=read_string_generic called, rxmax=200 direct=1, expected_len=1 > > read_string_generic(): RX 6 characters, direct=1 > > *****5:frame.c(452):icom_one_transaction returning(-9) Command > rejected by the rig > > Command rejected by the rig > > ****4:frame.c(556):icom_transaction returning(-9) Command rejected by > the rig > > rig_get_freq(2597): freqMainA=0, modeMainA=, widthMainA=0 > > rig_get_freq(2597): freqMainB=0, modeMainB=, widthMainB=0 > > rig_get_freq(2597): freqSubA=0, modeSubA=, widthSubA=0 > > rig_get_freq(2597): freqSubB=0, modeSubB=, widthSubB=0 > > rig_get_cache(328): vfo=currVFO, current_vfo=currVFO > > rig_get_cache(523): vfo=VFOA, freq=0, mode=, width=0 > > rig_set_cache_freq(171): vfo=currVFO, current_vfo=currVFO > > ***3:rig_get_freq: elapsed=4ms > > ***3:rig.c(2714):rig_get_freq returning(-9) Command rejected by the rig > > Command rejected by the rig > > Command rejected by the rig > > Opened rig model 3081, 'IC-9700' > > > > > -- > Bob Nazro, W1RPQ > phone: (860) 941-7993 > b <mailto:Jos...@cp...>na...@gm... > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
|
From: Daniele F. <iu...@gm...> - 2025-04-19 22:23:35
|
Hello Richard, you wrote: > I understand that rigctld can host a server that listens on localhost by > default. no, by default it listens on all interfaces with an IPv4 address; if you want to listen on a specific interface you need to use the command line option --listen-addr (the man page has some examples). you asked: > Why is it, that the password command line argument has a ? In front instead a -? the question mark means that the command is available only in interactive mode and when reading from stdin, it must be written with a backslash in front and it can't be given as a command line argument. As for the passwords, that code in Hamlib is unfinished, however as soon as you have a remote PC you will likely need a secure way to do remote maintenance and you could use ssh or a VPN and both would allow you to access also the ports used by the Hamlib tools. -- 73 de IU5HKX Daniele |
|
From: Bob N. <bn...@gm...> - 2025-04-19 19:49:11
|
Setting up GPREDICT with my IC-7900. It's communicating, but I get several errors. Not sure what to do. Are there additional parameters that I need to add to the command line? Radio is setup and COM 7 is 115200 baud. Any help is greatly appreciated. This is the command line I am running on the Windows desktop "C:\Program Files\hamlib-w64-4.6.2\bin\rigctld.exe" -m 3081 -r COM7 -t 4532 -s 115200 -vvv This is what I get when I run it: icom_get_powerstat: get freq failed, assuming power is off icom_rig_open: rig error getting frequency retry=1, err=read_string_generic called, rxmax=200 direct=1, expected_len=1 read_string_generic(): RX 6 characters, direct=1 *****5:frame.c(452):icom_one_transaction returning(-9) Command rejected by the rig Command rejected by the rig ****4:frame.c(556):icom_transaction returning(-9) Command rejected by the rig rig_get_freq(2597): freqMainA=0, modeMainA=, widthMainA=0 rig_get_freq(2597): freqMainB=0, modeMainB=, widthMainB=0 rig_get_freq(2597): freqSubA=0, modeSubA=, widthSubA=0 rig_get_freq(2597): freqSubB=0, modeSubB=, widthSubB=0 rig_get_cache(328): vfo=currVFO, current_vfo=currVFO rig_get_cache(523): vfo=VFOA, freq=0, mode=, width=0 rig_set_cache_freq(171): vfo=currVFO, current_vfo=currVFO ***3:rig_get_freq: elapsed=0ms ***3:rig.c(2714):rig_get_freq returning(-9) Command rejected by the rig Command rejected by the rig Command rejected by the rig icom_rig_open: rig error getting frequency retry=0, err=read_string_generic called, rxmax=200 direct=1, expected_len=1 read_string_generic(): RX 6 characters, direct=1 *****5:frame.c(452):icom_one_transaction returning(-9) Command rejected by the rig Command rejected by the rig ****4:frame.c(556):icom_transaction returning(-9) Command rejected by the rig rig_get_freq(2597): freqMainA=0, modeMainA=, widthMainA=0 rig_get_freq(2597): freqMainB=0, modeMainB=, widthMainB=0 rig_get_freq(2597): freqSubA=0, modeSubA=, widthSubA=0 rig_get_freq(2597): freqSubB=0, modeSubB=, widthSubB=0 rig_get_cache(328): vfo=currVFO, current_vfo=currVFO rig_get_cache(523): vfo=VFOA, freq=0, mode=, width=0 rig_set_cache_freq(171): vfo=currVFO, current_vfo=currVFO ***3:rig_get_freq: elapsed=4ms ***3:rig.c(2714):rig_get_freq returning(-9) Command rejected by the rig Command rejected by the rig Command rejected by the rig Opened rig model 3081, 'IC-9700' -- Bob Nazro, W1RPQ phone: (860) 941-7993 b <Jos...@cp...>na...@gm... |
|
From: George B. <geo...@gm...> - 2025-04-19 17:53:54
|
On 4/17/25 2:11 PM, Stefan Jansen wrote: > Hi David, hi list, > > First, let men introduce myself. I am Stefan, living in Germany and > developing together with Richard on a piece of software that uses > hamlib and mainly rigctl. > > Now back to the topic if this thread: > > David, it is clear that you do not have to query the current frequency > before setting an arbitrary new value. But what if you want to just > increase the current frequency by, let’s say, 1kHz? To do so, would > you query the current frequency with the „f“ command, add 1000 to it > and set the new value with „F“? Or is there a command to just > increment or decrement the current frequency by a given step size? > See rig_vfo_op(), which does have UP/DOWN operations. Implementation may depend on what each rig can do. > Vy 73 de Stefan, DK7STJ > > -- > Stefan Jansen *** E-Mail: DK7STJ@darc.d -- 73 n3gb |
|
From: Richard E. <DO...@ho...> - 2025-04-19 13:13:03
|
Greetings Listers. I am wondering, if there are actually transceivers, for which there is a difference in the lists for get and set_functions, when used with the question mark parameter or in the dump caps list? I ask, because we write toggle scripts for functions in accordance with the list retrived from the output of set_functions ?. So: Do we need to check against the output from get_functions ?, to see, if there is a difference, or can we assume, that every function which can be setted also can be getted and the otherway around? Thanks in advance -- 73 Richard, DO9RE |
33 messages has been excluded from this view by a project administrator.
