hamlib-developer Mailing List for Ham Radio Control Libraries (Page 10)
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
(10) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <gm...@bt...> - 2025-05-29 19:27:12
|
Thanks Sakari. The only testing I did was on get_level RFPOWER_METER_WATTS on 70 MHz CW/FM. I didn't consider AM and Emergency Mode. I'll need to do some more testing, and looking through the code, but that will probably be tomorrow now. Phil GM3ZZA. ________________________________ From: Sakari Nylund <sak...@ni...> Sent: 29 May 2025 7:16 PM To: ham...@li... <ham...@li...> Subject: Re: [Hamlib-developer] IC7300 output power Ok! Let's see what happens after compiled the latest one. Power commands were a bit complicated to understand in first place (from man page), but various tests showed up that: mW2power 'Power mW' 'Frequency' 'Mode' --- returns the setting of IC7300 power knob 0.0-1.0 I.E. 0-100% power2mW 'Power [0.0..1.0]' 'Frequency' 'Mode' --- returns the expected power output with power(knob) value %0-100 on used band/mode That is expected power. I.E. when running for example FT8 with low audio feed to rig you will get less power out than power2mW says. Value is stable, not depending on PTT state. You get always same result. I.E. just using given power knob % and converting it to mW. get_level RFPOWER_METER_WATTS --- returns the current output power. If PTT is off resut is 0W, if PTT is on result is the measured output power. While having RF power knob at 100% but driving side band modulation with low audio level the resulting output power is less than power% and RFPOWER_METER_WATTS can really show that when using "normal" Ham bands. Except 70MHz that is added afterwards and with used components can offer just half of rig's nominal max power. (Compare that to emergency mode! (menu/set/others/emergency/tuner) It would be interesting to test what power values then would be shown!) Without diving into C, that is not so familiar to me, I guess the measured RFPOWER_METER_WATTS conversion does not take on account 'Frequency' 'Mode' combination in all cases I.E. on 70MHz where the max output is only half, just like using emergency mode. -- Saku OH1KH gm3zza--- via Hamlib-developer kirjoitti 29.5.2025 klo 18.47: PS. I applied that patch to the pull I took this morning. ________________________________ From: Philip Rose via Hamlib-developer <ham...@li...><mailto:ham...@li...> Sent: 29 May 2025 4:36 PM To: ham...@li...<mailto:ham...@li...> <ham...@li...><mailto:ham...@li...> Subject: Re: [Hamlib-developer] IC7300 output power Hi Nate, Quickly tested - seems OK. Phil On 29/05/2025 16:22, Nate Bargmann wrote: > * On 2025 29 May 09:39 -0500, gm3zza--- via Hamlib-developer wrote: >> Right, I can see the issue: >> >> >> 1. >> The IC-7300 PO meter display %age of maximum power. So 50% max power is displayed as 50%. >> 2. >> The CI-V returns PO meter reading. >> 3. >> Both Hamlib and Flrig convert this value to Watts using similar look-up tables. Basically they both follow the display on the rig. >> 4. >> So for 50% max power gets displayed as 50 W, rather than 25W. >> >> Unfortunately I don't have an RF Power meter that covers 70 MHz. My 144/432 meter reads 8W at 50% max power on 70 MHz. >> >> Interesting asides: >> >> The code for IC-9700 (IIRC in icom.c) divides the calculated power by 10 for the 10 GHz. >> The IC-705 when operating on battery (max power = 5W) displays 100% max power, but only returns 50% on CI-V, so both Hamlib and Flrig. Obviously the CAT software doesn't know it's running on battery, so it makes sense for the Icom to handle that change. >> >> I can implement similar code for IC-7300 on 70 MHz that is there for IC-9700 on 10 GHz. > Please do. Sakari can probably test it. > > 73, Nate > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li...<mailto:Ham...@li...> > https://lists.sourceforge.net/lists/listinfo/hamlib-developer _______________________________________________ Hamlib-developer mailing list Ham...@li...<mailto:Ham...@li...> https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
|
From: Sakari N. <sak...@ni...> - 2025-05-29 18:16:21
|
Ok! Let's see what happens after compiled the latest one. Power commands were a bit complicated to understand in first place (from man page), but various tests showed up that: *mW2power 'Power mW' 'Frequency' 'Mode' * --- returns the setting of IC7300 power knob 0.0-1.0 I.E. 0-100% *power2mW 'Power [0.0..1.0]' 'Frequency' 'Mode'* --- returns the *expected* power output with power(knob) value %0-100 on used band/mode That is *expected* *power*. I.E. when running for example FT8 with low audio feed to rig you will get *less power* out than power2mW says. Value is stable, not depending on PTT state. You get always same result. I.E. just using given power knob % and converting it to mW. *get_level RFPOWER_METER_WATTS* --- returns the current output power. If PTT is off resut is 0W, if PTT is on result is the measured output power. While having RF power knob at 100% but driving side band modulation with low audio level the resulting output power is less than power% and *RFPOWER_METER_WATTS *can really show that**when using "normal" Ham bands. Except 70MHz that is added afterwards and with used components can offer just half of rig's nominal max power. (Compare that to emergency mode! (menu/set/others/emergency/tuner) It would be interesting to test what power values then would be shown!) Without diving into C, that is not so familiar to me, I guess the measured *RFPOWER_METER_WATTS *conversion does not take on account *'Frequency' 'Mode'* combination in all cases I.E. on 70MHz where the max output is only half, just like using emergency mode. -- Saku OH1KH gm3zza--- via Hamlib-developer kirjoitti 29.5.2025 klo 18.47: > PS. I applied that patch to the pull I took this morning. > ------------------------------------------------------------------------ > *From:* Philip Rose via Hamlib-developer > <ham...@li...> > *Sent:* 29 May 2025 4:36 PM > *To:* ham...@li... > <ham...@li...> > *Subject:* Re: [Hamlib-developer] IC7300 output power > Hi Nate, > > > Quickly tested - seems OK. > > > Phil > > > On 29/05/2025 16:22, Nate Bargmann wrote: > > * On 2025 29 May 09:39 -0500, gm3zza--- via Hamlib-developer wrote: > >> Right, I can see the issue: > >> > >> > >> 1. > >> The IC-7300 PO meter display %age of maximum power. So 50% max > power is displayed as 50%. > >> 2. > >> The CI-V returns PO meter reading. > >> 3. > >> Both Hamlib and Flrig convert this value to Watts using similar > look-up tables. Basically they both follow the display on the rig. > >> 4. > >> So for 50% max power gets displayed as 50 W, rather than 25W. > >> > >> Unfortunately I don't have an RF Power meter that covers 70 MHz. My > 144/432 meter reads 8W at 50% max power on 70 MHz. > >> > >> Interesting asides: > >> > >> The code for IC-9700 (IIRC in icom.c) divides the calculated power > by 10 for the 10 GHz. > >> The IC-705 when operating on battery (max power = 5W) displays 100% > max power, but only returns 50% on CI-V, so both Hamlib and Flrig. > Obviously the CAT software doesn't know it's running on battery, so it > makes sense for the Icom to handle that change. > >> > >> I can implement similar code for IC-7300 on 70 MHz that is there > for IC-9700 on 10 GHz. > > Please do. Sakari can probably test it. > > > > 73, Nate > > > > > > > > _______________________________________________ > > Hamlib-developer mailing list > > Ham...@li... > > https://lists.sourceforge.net/lists/listinfo/hamlib-developer > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
|
From: GeoBaltz <no...@gi...> - 2025-05-29 17:40:40
|
Branch: refs/heads/Hamlib-4.6.3 Home: https://github.com/Hamlib/Hamlib Commit: 59ab35248703d5b492817c1d1e2511da41ede88e https://github.com/Hamlib/Hamlib/commit/59ab35248703d5b492817c1d1e2511da41ede88e Author: George Baltz N3GB <Geo...@gm...> Date: 2025-05-29 (Thu, 29 May 2025) Changed paths: M rigs/kenwood/kenwood.c M rigs/kenwood/kenwood.h Log Message: ----------- Fix out of sequence merge for issue #1634 Still undetermined if fix is needed for TS-590SG (cherry picked from commit a4b6ef4fd73dce67de5cb859f111d819d40313ed) Commit: 6150ee94c703b8d02d200ed685c497408394fc2a https://github.com/Hamlib/Hamlib/commit/6150ee94c703b8d02d200ed685c497408394fc2a Author: George Baltz N3GB <Geo...@gm...> Date: 2025-05-29 (Thu, 29 May 2025) Changed paths: M rigs/yaesu/ft857.c Log Message: ----------- Fix backward frequency tests in ft857.c Found by cppcheck.sh (cherry picked from commit 00d285576cae5c5db3cdac03f3b9abc13508a964) Compare: https://github.com/Hamlib/Hamlib/compare/8f919a5a54d7...6150ee94c703 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: GeoBaltz <no...@gi...> - 2025-05-29 17:37:07
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: a4b6ef4fd73dce67de5cb859f111d819d40313ed https://github.com/Hamlib/Hamlib/commit/a4b6ef4fd73dce67de5cb859f111d819d40313ed Author: George Baltz N3GB <Geo...@gm...> Date: 2025-05-29 (Thu, 29 May 2025) Changed paths: M rigs/kenwood/kenwood.c M rigs/kenwood/kenwood.h Log Message: ----------- Fix out of sequence merge for issue #1634 Still undetermined if fix is needed for TS-590SG Commit: 9f43659831c22fa210732b8fd6a88d11fd6aa603 https://github.com/Hamlib/Hamlib/commit/9f43659831c22fa210732b8fd6a88d11fd6aa603 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-05-29 (Thu, 29 May 2025) Changed paths: M simulators/simts890.c M simulators/simts990.c Log Message: ----------- Fix gain controls in simts890.c And a couple of other hiccups found by cppcheck Commit: 0a6d07a1adaec907facee2fd8e3428fded978672 https://github.com/Hamlib/Hamlib/commit/0a6d07a1adaec907facee2fd8e3428fded978672 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-05-29 (Thu, 29 May 2025) Changed paths: M rigs/kenwood/ts2000.c M rigs/kenwood/ts480.c M rigs/kenwood/ts570.c M rigs/kenwood/ts590.c M rigs/kenwood/ts870s.c Log Message: ----------- Make a few more functions static All rig-specific overrides should only be used in one file. Keep the definitions local. Commit: 00d285576cae5c5db3cdac03f3b9abc13508a964 https://github.com/Hamlib/Hamlib/commit/00d285576cae5c5db3cdac03f3b9abc13508a964 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-05-29 (Thu, 29 May 2025) Changed paths: M rigs/yaesu/ft857.c Log Message: ----------- Fix backward frequency tests in ft857.c Found by cppcheck.sh Commit: b74bd31b408369ddb1e09de52036b8b3d9002385 https://github.com/Hamlib/Hamlib/commit/b74bd31b408369ddb1e09de52036b8b3d9002385 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-05-29 (Thu, 29 May 2025) Changed paths: M .gitignore M rigs/dummy/dummy.c M rigs/flexradio/dttsp.c M rigs/icom/ic7100.c M rigs/icom/ic7200.c M rigs/kenwood/ts890s.c M rigs/yaesu/ft3000.c M rigs/yaesu/pmr171.c M src/sprintflst.c Log Message: ----------- Quiet a few more cppcheck gripes. Making these functions static also reduces the possibilities of collisions with app names and may shorten load time. And I can finally make meter_type1 and meter_type2 const, like I tried to do in the beginning. Commit: cccee9b7916548c2c48a1bfd55116fded3d3a6ed https://github.com/Hamlib/Hamlib/commit/cccee9b7916548c2c48a1bfd55116fded3d3a6ed Author: George Baltz N3GB <Geo...@gm...> Date: 2025-05-29 (Thu, 29 May 2025) Changed paths: M amplifiers/elecraft/kpa.c M include/hamlib/rig.h M rigs/kenwood/xg3.c M rigs/tentec/jupiter.c M security/aes.c M security/aes.h M security/md5.c M security/sha256.c Log Message: ----------- Still more cppcheck complaints dealt with. Compare: https://github.com/Hamlib/Hamlib/compare/9fdf8f201ce7...cccee9b79165 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: <gm...@bt...> - 2025-05-29 15:47:51
|
PS. I applied that patch to the pull I took this morning. ________________________________ From: Philip Rose via Hamlib-developer <ham...@li...> Sent: 29 May 2025 4:36 PM To: ham...@li... <ham...@li...> Subject: Re: [Hamlib-developer] IC7300 output power Hi Nate, Quickly tested - seems OK. Phil On 29/05/2025 16:22, Nate Bargmann wrote: > * On 2025 29 May 09:39 -0500, gm3zza--- via Hamlib-developer wrote: >> Right, I can see the issue: >> >> >> 1. >> The IC-7300 PO meter display %age of maximum power. So 50% max power is displayed as 50%. >> 2. >> The CI-V returns PO meter reading. >> 3. >> Both Hamlib and Flrig convert this value to Watts using similar look-up tables. Basically they both follow the display on the rig. >> 4. >> So for 50% max power gets displayed as 50 W, rather than 25W. >> >> Unfortunately I don't have an RF Power meter that covers 70 MHz. My 144/432 meter reads 8W at 50% max power on 70 MHz. >> >> Interesting asides: >> >> The code for IC-9700 (IIRC in icom.c) divides the calculated power by 10 for the 10 GHz. >> The IC-705 when operating on battery (max power = 5W) displays 100% max power, but only returns 50% on CI-V, so both Hamlib and Flrig. Obviously the CAT software doesn't know it's running on battery, so it makes sense for the Icom to handle that change. >> >> I can implement similar code for IC-7300 on 70 MHz that is there for IC-9700 on 10 GHz. > Please do. Sakari can probably test it. > > 73, Nate > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
|
From: Philip R. <gm...@bt...> - 2025-05-29 15:36:59
|
Hi Nate, Quickly tested - seems OK. Phil On 29/05/2025 16:22, Nate Bargmann wrote: > * On 2025 29 May 09:39 -0500, gm3zza--- via Hamlib-developer wrote: >> Right, I can see the issue: >> >> >> 1. >> The IC-7300 PO meter display %age of maximum power. So 50% max power is displayed as 50%. >> 2. >> The CI-V returns PO meter reading. >> 3. >> Both Hamlib and Flrig convert this value to Watts using similar look-up tables. Basically they both follow the display on the rig. >> 4. >> So for 50% max power gets displayed as 50 W, rather than 25W. >> >> Unfortunately I don't have an RF Power meter that covers 70 MHz. My 144/432 meter reads 8W at 50% max power on 70 MHz. >> >> Interesting asides: >> >> The code for IC-9700 (IIRC in icom.c) divides the calculated power by 10 for the 10 GHz. >> The IC-705 when operating on battery (max power = 5W) displays 100% max power, but only returns 50% on CI-V, so both Hamlib and Flrig. Obviously the CAT software doesn't know it's running on battery, so it makes sense for the Icom to handle that change. >> >> I can implement similar code for IC-7300 on 70 MHz that is there for IC-9700 on 10 GHz. > Please do. Sakari can probably test it. > > 73, Nate > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
|
From: Nate B. <n0...@n0...> - 2025-05-29 15:22:31
|
* On 2025 29 May 09:39 -0500, gm3zza--- via Hamlib-developer wrote: > Right, I can see the issue: > > > 1. > The IC-7300 PO meter display %age of maximum power. So 50% max power is displayed as 50%. > 2. > The CI-V returns PO meter reading. > 3. > Both Hamlib and Flrig convert this value to Watts using similar look-up tables. Basically they both follow the display on the rig. > 4. > So for 50% max power gets displayed as 50 W, rather than 25W. > > Unfortunately I don't have an RF Power meter that covers 70 MHz. My 144/432 meter reads 8W at 50% max power on 70 MHz. > > Interesting asides: > > The code for IC-9700 (IIRC in icom.c) divides the calculated power by 10 for the 10 GHz. > The IC-705 when operating on battery (max power = 5W) displays 100% max power, but only returns 50% on CI-V, so both Hamlib and Flrig. Obviously the CAT software doesn't know it's running on battery, so it makes sense for the Icom to handle that change. > > I can implement similar code for IC-7300 on 70 MHz that is there for IC-9700 on 10 GHz. Please do. Sakari can probably test it. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 |
|
From: <gm...@bt...> - 2025-05-29 14:38:43
|
Right, I can see the issue: 1. The IC-7300 PO meter display %age of maximum power. So 50% max power is displayed as 50%. 2. The CI-V returns PO meter reading. 3. Both Hamlib and Flrig convert this value to Watts using similar look-up tables. Basically they both follow the display on the rig. 4. So for 50% max power gets displayed as 50 W, rather than 25W. Unfortunately I don't have an RF Power meter that covers 70 MHz. My 144/432 meter reads 8W at 50% max power on 70 MHz. Interesting asides: The code for IC-9700 (IIRC in icom.c) divides the calculated power by 10 for the 10 GHz. The IC-705 when operating on battery (max power = 5W) displays 100% max power, but only returns 50% on CI-V, so both Hamlib and Flrig. Obviously the CAT software doesn't know it's running on battery, so it makes sense for the Icom to handle that change. I can implement similar code for IC-7300 on 70 MHz that is there for IC-9700 on 10 GHz. I've not tested AM. Phil GM3ZZA. ________________________________ From: gm...@bt... <gm...@bt...> Sent: 29 May 2025 2:04 PM To: Nate Bargmann <n0...@n0...>; ham...@li... <ham...@li...> Subject: Re: [Hamlib-developer] IC7300 output power Hi Nate, I can have a look at this. I've got a European model IC-7300 which has 4 metres. I can't do this remotely as I have no way of keying the rig using hamlib. So I'll see if I can get some time in the shack later today. My usual means of keying the rig when remote is flrig and that appears to give the correct power (just over 20 W on 50% drive). 73 ________________________________ From: Nate Bargmann <n0...@n0...> Sent: 29 May 2025 1:35 PM To: ham...@li... <ham...@li...> Subject: Re: [Hamlib-developer] IC7300 output power * On 2025 29 May 05:20 -0500, Sakari Nylund wrote: > Opps! > > Forgot to mention: rigctld Hamlib 4.7~git 2025-03-12T17:49:17Z SHA=f8740d > 64-bit That's rather old, but the code in question appears to have been in place since February 2021: https://github.com/Hamlib/Hamlib/commit/660fd9496263abe5a663dae7496a6efee3a002ed I'll have to leave it to an Icom expert to figure out why 4m is off. 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: Sakari N. <sak...@ni...> - 2025-05-29 14:06:08
|
Yep! I have not updated Hamlib for a while as all I need has been working. This power output came out to view after I wrote CqrlogAlpha to show output power while transmitting. I tested quickly with flrig (2.0.04) and 70.170MHz keeping key down. My Diamond SX-1000 shows the same around 50Watts while flrig power meter (100W scale) shows also full 100W output. It climbs up with steps (~1 sec each) 20-40-60-80-100 and stays then on full 100. With AM and same frequency power meter has red mark at 20W and bar climbs up with same kind of stepping until 20W is reached. Power meter shows ~15W. So that is near the truth as I have antenna connected, not pure resistive load. But how ever it seems that flrig fails same way with CW (USB-D, FM) showing full power 100W on 70MHz. -- Saku OH1KH Nate Bargmann kirjoitti 29.5.2025 klo 15.35: > That's rather old, but the code in question appears to have been in > place since February 2021: |
|
From: <gm...@bt...> - 2025-05-29 13:05:01
|
Hi Nate, I can have a look at this. I've got a European model IC-7300 which has 4 metres. I can't do this remotely as I have no way of keying the rig using hamlib. So I'll see if I can get some time in the shack later today. My usual means of keying the rig when remote is flrig and that appears to give the correct power (just over 20 W on 50% drive). 73 ________________________________ From: Nate Bargmann <n0...@n0...> Sent: 29 May 2025 1:35 PM To: ham...@li... <ham...@li...> Subject: Re: [Hamlib-developer] IC7300 output power * On 2025 29 May 05:20 -0500, Sakari Nylund wrote: > Opps! > > Forgot to mention: rigctld Hamlib 4.7~git 2025-03-12T17:49:17Z SHA=f8740d > 64-bit That's rather old, but the code in question appears to have been in place since February 2021: https://github.com/Hamlib/Hamlib/commit/660fd9496263abe5a663dae7496a6efee3a002ed I'll have to leave it to an Icom expert to figure out why 4m is off. 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-05-29 12:36:07
|
* On 2025 29 May 05:20 -0500, Sakari Nylund wrote: > Opps! > > Forgot to mention: rigctld Hamlib 4.7~git 2025-03-12T17:49:17Z SHA=f8740d > 64-bit That's rather old, but the code in question appears to have been in place since February 2021: https://github.com/Hamlib/Hamlib/commit/660fd9496263abe5a663dae7496a6efee3a002ed I'll have to leave it to an Icom expert to figure out why 4m is off. 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: Sakari N. <sak...@ni...> - 2025-05-29 10:19:43
|
Opps! Forgot to mention: rigctld Hamlib 4.7~git 2025-03-12T17:49:17Z SHA=f8740d 64-bit -- Saku OH1KH Sakari Nylund kirjoitti 29.5.2025 klo 13.17: > Hi! > > While 4m opening just noticed that '+\get_level RFPOWER_METER_WATTS' > gives false reading on 70MHz. > USB-D with full pwr setting it gives ~90W while power meter shows just > 50W that is known to max output of IC7300 on 70MHz. > > Perhaps there is an error in "power2mW" table (or 70MHz totally > missing?). |
|
From: Sakari N. <sak...@ni...> - 2025-05-29 10:17:32
|
Hi! While 4m opening just noticed that '+\get_level RFPOWER_METER_WATTS' gives false reading on 70MHz. USB-D with full pwr setting it gives ~90W while power meter shows just 50W that is known to max output of IC7300 on 70MHz. Perhaps there is an error in "power2mW" table (or 70MHz totally missing?). -- Saku OH1KH |
|
From: dforsi <no...@gi...> - 2025-05-29 08:14:01
|
Branch: refs/heads/Hamlib-4.6.3 Home: https://github.com/Hamlib/Hamlib Commit: 8f919a5a54d7318afea557790d34ddb74c1c6b56 https://github.com/Hamlib/Hamlib/commit/8f919a5a54d7318afea557790d34ddb74c1c6b56 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-05-29 (Thu, 29 May 2025) Changed paths: M macros/Makefile.am Log Message: ----------- Fix list of dependecies of aclocal.m4 Adds missing ax_lib_readline.m4 and ax_lua.m4 to the list of MACROS. Also sorts the list. (cherry picked from commit 9fdf8f201ce78a2c3b8b0a245bdd2cacf17cbb68) To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: dforsi <no...@gi...> - 2025-05-29 08:09:51
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 9fdf8f201ce78a2c3b8b0a245bdd2cacf17cbb68 https://github.com/Hamlib/Hamlib/commit/9fdf8f201ce78a2c3b8b0a245bdd2cacf17cbb68 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-05-27 (Tue, 27 May 2025) Changed paths: M macros/Makefile.am Log Message: ----------- Fix list of dependecies of aclocal.m4 Adds missing ax_lib_readline.m4 and ax_lua.m4 to the list of MACROS. Also sorts the list. To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Daniele F. <iu...@gm...> - 2025-05-28 22:24:43
|
Hello, > There's a problem with Hamlib w64-4.6.2. The serial port is recognized but not working. I get this message: > > > > C:\Program Files\hamlib-w64-4.6.2\bin>rotctld.exe -m 202 -r COM4 -s 9600 -T 127.0.0.1 -t 4533 -vvv > > serial_setup: tcsetattr failed: No error Are you using the version released at https://github.com/Hamlib/Hamlib/releases or did you compile it? Do you have other software that works with those settings? I just run your command line both on 4.6.2 from link above and on 4.6.3-rc1 from https://n0nb.users.sourceforge.net/rc/ and both open my COM1 -- 73 de IU5HKX Daniele |
|
From: Daniele F. <iu...@gm...> - 2025-05-27 20:54:35
|
Hello Stefan, > Sorry for my maybe stupid question. it isn't a stupid question but it is unclear what you want to do, why can't you use "set_mode"? the man pages or the documentation generated on a local machine with Doxygen and also available online should contain all information, but some parts may be undocumented -- 73 de IU5HKX Daniele |
|
From: Nate B. <n0...@n0...> - 2025-05-26 18:37:12
|
After a few additional cherry-picks I've created an ~rc1 tarball and Windows binaries. They are available at: https://n0nb.users.sourceforge.net/rc/ 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: GeoBaltz <no...@gi...> - 2025-05-26 16:18:06
|
Branch: refs/heads/Hamlib-4.6.3 Home: https://github.com/Hamlib/Hamlib Commit: 53d2eed741d36fd87622a601590d8e860f048bc3 https://github.com/Hamlib/Hamlib/commit/53d2eed741d36fd87622a601590d8e860f048bc3 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-05-26 (Mon, 26 May 2025) Changed paths: M src/settings.c Log Message: ----------- Add locking around get/set levels (cherry picked from commit b5df48d8d9839460e13201765b278c6a32741158) To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-05-26 16:15:39
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: b5df48d8d9839460e13201765b278c6a32741158 https://github.com/Hamlib/Hamlib/commit/b5df48d8d9839460e13201765b278c6a32741158 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-05-24 (Sat, 24 May 2025) Changed paths: M src/settings.c Log Message: ----------- Add locking around get/set levels Commit: 717d720a3605745a47812908b088117580e4e10c https://github.com/Hamlib/Hamlib/commit/717d720a3605745a47812908b088117580e4e10c Author: Nate Bargmann <n0...@n0...> Date: 2025-05-26 (Mon, 26 May 2025) Changed paths: M src/settings.c Log Message: ----------- Merge GitHub PR #1744 Compare: https://github.com/Hamlib/Hamlib/compare/43017b38f08c...717d720a3605 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: dforsi <no...@gi...> - 2025-05-26 15:53:52
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 3034631b2f99f32680e2939035f45019a2fc38c3 https://github.com/Hamlib/Hamlib/commit/3034631b2f99f32680e2939035f45019a2fc38c3 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-05-26 (Mon, 26 May 2025) Changed paths: M rigs/dummy/amp_dummy.c Log Message: ----------- Fix typo Commit: 43017b38f08c6ed75fa9c5a4d88bdb0875e7c15a https://github.com/Hamlib/Hamlib/commit/43017b38f08c6ed75fa9c5a4d88bdb0875e7c15a Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-05-26 (Mon, 26 May 2025) Changed paths: M doc/man1/rotctld.1 Log Message: ----------- Fix typo Add closing tag for example text. Compare: https://github.com/Hamlib/Hamlib/compare/f459eea516a3...43017b38f08c To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: dforsi <no...@gi...> - 2025-05-26 15:51:48
|
Branch: refs/heads/Hamlib-4.6.3 Home: https://github.com/Hamlib/Hamlib Commit: ffb61c29a5aa0eca95d4cf62e3cb15c610a223ce https://github.com/Hamlib/Hamlib/commit/ffb61c29a5aa0eca95d4cf62e3cb15c610a223ce Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-05-26 (Mon, 26 May 2025) Changed paths: M rigs/dummy/amp_dummy.c Log Message: ----------- Fix typo (cherry picked from commit 3034631b2f99f32680e2939035f45019a2fc38c3) Commit: f0ac83bcba5b7bf0a6a2db18d31069bbd118cd41 https://github.com/Hamlib/Hamlib/commit/f0ac83bcba5b7bf0a6a2db18d31069bbd118cd41 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-05-26 (Mon, 26 May 2025) Changed paths: M doc/man1/rotctld.1 Log Message: ----------- Fix typo Add closing tag for example text. (cherry picked from commit 43017b38f08c6ed75fa9c5a4d88bdb0875e7c15a) Compare: https://github.com/Hamlib/Hamlib/compare/e641162a6be7...f0ac83bcba5b To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <n0...@n0...> - 2025-05-26 02:33:06
|
Astute observers will have noticed that I updated the NEWS file, created the Hamlib-4.6.3 branch, and updated its configure.ac to version 4.6.3~rc1. I plan to generate an rc1 tarball and Windows binaries and put them in a temporary directory on the daily snapshots page for testing. While I wanted to get to this about a month earlier, real life had other ideas! I've set a target release date of 10 June which should give a change to shake down this branch and get a good solid release out while opening up 'master' to development for 4.7.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 |
|
From: Nate B. <no...@gi...> - 2025-05-26 02:23:47
|
Branch: refs/heads/Hamlib-4.6.3 Home: https://github.com/Hamlib/Hamlib Commit: e641162a6be7570a20b6e0189a53063cdbca1a39 https://github.com/Hamlib/Hamlib/commit/e641162a6be7570a20b6e0189a53063cdbca1a39 Author: Nate Bargmann <n0...@n0...> Date: 2025-05-25 (Sun, 25 May 2025) Changed paths: M configure.ac Log Message: ----------- Advance to 4.6.3~rc1 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-05-26 01:53:01
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: f459eea516a3e5c9b74c72dd4a430fcde1764f71 https://github.com/Hamlib/Hamlib/commit/f459eea516a3e5c9b74c72dd4a430fcde1764f71 Author: Nate Bargmann <n0...@n0...> Date: 2025-05-25 (Sun, 25 May 2025) Changed paths: M NEWS Log Message: ----------- Update NEWS for 4.6.3 release To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
33 messages has been excluded from this view by a project administrator.
