hamlib-developer Mailing List for Ham Radio Control Libraries (Page 94)
Library to control radio transceivers and receivers
Brought to you by:
n0nb
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(24) |
Oct
(16) |
Nov
(8) |
Dec
(9) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(49) |
Feb
(17) |
Mar
(3) |
Apr
(7) |
May
(3) |
Jun
(1) |
Jul
(2) |
Aug
(8) |
Sep
(18) |
Oct
(15) |
Nov
(15) |
Dec
(26) |
2002 |
Jan
(46) |
Feb
(14) |
Mar
(44) |
Apr
(3) |
May
(6) |
Jun
(47) |
Jul
(40) |
Aug
(14) |
Sep
(59) |
Oct
(39) |
Nov
(58) |
Dec
(76) |
2003 |
Jan
(82) |
Feb
(66) |
Mar
(37) |
Apr
(56) |
May
(34) |
Jun
(19) |
Jul
(23) |
Aug
(55) |
Sep
(31) |
Oct
(40) |
Nov
(21) |
Dec
(60) |
2004 |
Jan
(57) |
Feb
(110) |
Mar
(41) |
Apr
(17) |
May
(18) |
Jun
(19) |
Jul
(18) |
Aug
(5) |
Sep
(31) |
Oct
(16) |
Nov
(26) |
Dec
(36) |
2005 |
Jan
(69) |
Feb
(26) |
Mar
(62) |
Apr
(120) |
May
(31) |
Jun
(47) |
Jul
(7) |
Aug
(27) |
Sep
(4) |
Oct
(9) |
Nov
(26) |
Dec
(21) |
2006 |
Jan
(13) |
Feb
(26) |
Mar
(38) |
Apr
(31) |
May
(17) |
Jun
(6) |
Jul
(23) |
Aug
(6) |
Sep
(38) |
Oct
(87) |
Nov
(49) |
Dec
(49) |
2007 |
Jan
(52) |
Feb
(19) |
Mar
(20) |
Apr
(5) |
May
(25) |
Jun
(15) |
Jul
(49) |
Aug
(43) |
Sep
(21) |
Oct
(21) |
Nov
(27) |
Dec
(10) |
2008 |
Jan
(23) |
Feb
(20) |
Mar
(25) |
Apr
(39) |
May
(36) |
Jun
(17) |
Jul
(10) |
Aug
(18) |
Sep
(44) |
Oct
(88) |
Nov
(60) |
Dec
(65) |
2009 |
Jan
(99) |
Feb
(91) |
Mar
(49) |
Apr
(34) |
May
(52) |
Jun
(9) |
Jul
(11) |
Aug
(4) |
Sep
(41) |
Oct
(16) |
Nov
(51) |
Dec
(71) |
2010 |
Jan
(43) |
Feb
(79) |
Mar
(59) |
Apr
(55) |
May
(51) |
Jun
(38) |
Jul
(38) |
Aug
(61) |
Sep
(53) |
Oct
(46) |
Nov
(43) |
Dec
(41) |
2011 |
Jan
(74) |
Feb
(96) |
Mar
(41) |
Apr
(42) |
May
(61) |
Jun
(66) |
Jul
(50) |
Aug
(40) |
Sep
(11) |
Oct
(30) |
Nov
(21) |
Dec
(45) |
2012 |
Jan
(59) |
Feb
(4) |
Mar
(52) |
Apr
(19) |
May
(62) |
Jun
(46) |
Jul
(61) |
Aug
(18) |
Sep
(21) |
Oct
(25) |
Nov
(66) |
Dec
(41) |
2013 |
Jan
(36) |
Feb
(64) |
Mar
(37) |
Apr
(24) |
May
(74) |
Jun
(40) |
Jul
(43) |
Aug
(34) |
Sep
(65) |
Oct
(52) |
Nov
(23) |
Dec
(20) |
2014 |
Jan
(18) |
Feb
(29) |
Mar
(13) |
Apr
(41) |
May
(10) |
Jun
(12) |
Jul
(16) |
Aug
(25) |
Sep
(20) |
Oct
(56) |
Nov
(43) |
Dec
(61) |
2015 |
Jan
(36) |
Feb
(38) |
Mar
(92) |
Apr
(42) |
May
(13) |
Jun
(19) |
Jul
(18) |
Aug
(22) |
Sep
(21) |
Oct
(2) |
Nov
(49) |
Dec
(22) |
2016 |
Jan
(55) |
Feb
(144) |
Mar
(40) |
Apr
(98) |
May
(61) |
Jun
(36) |
Jul
(16) |
Aug
(33) |
Sep
(59) |
Oct
(16) |
Nov
(37) |
Dec
(32) |
2017 |
Jan
(70) |
Feb
(71) |
Mar
(14) |
Apr
(43) |
May
(31) |
Jun
(24) |
Jul
(38) |
Aug
(54) |
Sep
(24) |
Oct
(15) |
Nov
(26) |
Dec
(27) |
2018 |
Jan
(22) |
Feb
(24) |
Mar
(109) |
Apr
(12) |
May
(46) |
Jun
(23) |
Jul
(39) |
Aug
(34) |
Sep
(22) |
Oct
(43) |
Nov
(26) |
Dec
(157) |
2019 |
Jan
(102) |
Feb
(51) |
Mar
(63) |
Apr
(60) |
May
(91) |
Jun
(55) |
Jul
(27) |
Aug
(76) |
Sep
(52) |
Oct
(95) |
Nov
(67) |
Dec
(204) |
2020 |
Jan
(311) |
Feb
(148) |
Mar
(230) |
Apr
(122) |
May
(204) |
Jun
(204) |
Jul
(114) |
Aug
(36) |
Sep
(120) |
Oct
(186) |
Nov
(60) |
Dec
(151) |
2021 |
Jan
(182) |
Feb
(171) |
Mar
(202) |
Apr
(153) |
May
(110) |
Jun
(50) |
Jul
(58) |
Aug
(142) |
Sep
(112) |
Oct
(120) |
Nov
(97) |
Dec
(125) |
2022 |
Jan
(175) |
Feb
(147) |
Mar
(54) |
Apr
(73) |
May
(127) |
Jun
(95) |
Jul
(88) |
Aug
(85) |
Sep
(38) |
Oct
(40) |
Nov
(116) |
Dec
(159) |
2023 |
Jan
(175) |
Feb
(55) |
Mar
(83) |
Apr
(70) |
May
(165) |
Jun
(79) |
Jul
(123) |
Aug
(90) |
Sep
(40) |
Oct
(95) |
Nov
(84) |
Dec
(88) |
2024 |
Jan
(105) |
Feb
(60) |
Mar
(52) |
Apr
(43) |
May
(56) |
Jun
(59) |
Jul
(53) |
Aug
(47) |
Sep
(62) |
Oct
(36) |
Nov
(45) |
Dec
(100) |
2025 |
Jan
(52) |
Feb
(45) |
Mar
(30) |
Apr
(97) |
May
(72) |
Jun
(83) |
Jul
(124) |
Aug
(17) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Black M. <mdb...@ya...> - 2023-01-07 16:52:20
|
>From rigctl or rigctld \get_info Or from the library rig_get_info Mike W9MDB On Saturday, January 7, 2023 at 10:47:49 AM CST, Philip Rose - GM3ZZA via Hamlib-developer <ham...@li...> wrote: Is there a way through the hamlib API to find the name of the actual rig when connecting using FLRig? I’ve looked through rig.h and there’s nothing obvious. Regards Phil GM3ZZA Sent from Mail for Windows _______________________________________________ Hamlib-developer mailing list Ham...@li... https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
From: Philip R. - G. <gm...@bt...> - 2023-01-07 16:47:35
|
Is there a way through the hamlib API to find the name of the actual rig when connecting using FLRig? I’ve looked through rig.h and there’s nothing obvious. Regards Phil GM3ZZA Sent from Mail for Windows |
From: Outlook(SV2AGW) <sv...@ou...> - 2023-01-07 14:08:18
|
Hi some test from my sideWhen Link and run with Hamlib version 4 this si the outputCMainFrame::iniRadio> 1 CMainFrame::iniRadio> n_rigmodel=3073 CMainFrame::iniRadio> 2 CMainFrame::iniRadio> rig_init OK CMainFrame::iniRadio> _strCom=\\.\COM9 CMainFrame::iniRadio> rigport=\\.\COM9 CMainFrame::iniRadio> GOTO rig_open CMainFrame::iniRadio> *******************OK RIG READY CMainFrame::iniRadio> freq=21091000.000000 Same Code with version 4.5.3 outputCMainFrame::iniRadio> 1 CMainFrame::iniRadio> n_rigmodel=3073 CMainFrame::iniRadio> 2 CMainFrame::iniRadio> rig_init OK CMainFrame::iniRadio> _strCom=\\.\COM9 CMainFrame::iniRadio> rigport=\\.\COM9 CMainFrame::iniRadio> GOTO rig_open CMainFrame::iniRadio> ************************** rig_open: error = 1:icom.c(623):icom_init entered icom_init: done 1:icom.c(723):icom_init returning(0) 1:rig.c(812):rig_open entered rig_settings_get_path: path=.hamlib_settings rig_settings_load_all: settings_file (.hamlib_settings): No such file or directory rig_open: cwd=C:\MyProjects\HamLibTest\HamLibTest rig_open: C:\MyProjects\HamLibTest\HamLibTest/hamlib_settings does not exist rig_open: async_data_enable=0, async_data_supported=1 serial_open: \\.\COM1 serial_open(229): open failed#1 serial_open(229): open failed#2 serial_open(229): open failed#3 serial_open(229): open failed#4 serial_open: Unable to open \\.\COM1 - Bad file descriptor port_open: serial_open(\\.\COM1) status=-6, err=Bad file descriptor rig_open: rs->comm_state==0?=0 1:rig.c(1018):rig_open returning(-6) IO error IO error =-6 CMainFrame::iniRadio> ************************** rig_open: error =error = 0 73(SV2AGW)George RossopoulosAnakreontos14GR-54250 ThessalonikiGREECEwww.sv2agw.comwww.frinos.comwww.agwtracker.comAGWPE on Facebook----------------------------------------------------------------From: Outlook(SV2AGW)<sv...@ou...>Sent: Σαβ 07Ιαν2023 08:16 To: Subject: Re: [Hamlib-developer] MSVC win32 dll Problem= Hi allthe problem persists!!!Its not just the librarian Please have a look at https://sv2agw.com/beta/hamlibtest.zipThe problem is that cannot pass the parameters to serial port.seems that rig_open reads serialport setting.strcpy_s(_pRig->state.rigport.pathname, \\\\.\\COM9); works on 4 but not on 4.5.3Thank you and 73(SV2AGW)George RossopoulosAnakreontos14GR-54250 ThessalonikiGREECEwww.sv2agw.comwww.frinos.comwww.agwtracker.comAGWPE on Facebook |
From: Outlook(SV2AGW) <sv...@ou...> - 2023-01-07 06:49:37
|
Hi allthe problem persists!!!Its not just the librarian Please have a look at https://sv2agw.com/beta/hamlibtest.zipThe problem is that cannot pass the parameters to serial port.seems that rig_open reads serialport setting.strcpy_s(_pRig->state.rigport.pathname, \\\\.\\COM9); works on 4 but not on 4.5.3Thank you and 73(SV2AGW)George RossopoulosAnakreontos14GR-54250 ThessalonikiGREECEwww.sv2agw.comwww.frinos.comwww.agwtracker.comAGWPE on Facebook |
From: Michael B. <no...@gi...> - 2023-01-07 05:56:56
|
Branch: refs/heads/Hamlib-4.5.4 Home: https://github.com/Hamlib/Hamlib Commit: efc295159987f88d22d2f1c52081a77775bc2293 https://github.com/Hamlib/Hamlib/commit/efc295159987f88d22d2f1c52081a77775bc2293 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-06 (Fri, 06 Jan 2023) Changed paths: M rigs/dummy/netrigctl.c Log Message: ----------- Remove unnecessary check from netrigctl.c https://github.com/Hamlib/Hamlib/issues/1155 Commit: b9ee776e5b58d7225730687b65e548423c241cef https://github.com/Hamlib/Hamlib/commit/b9ee776e5b58d7225730687b65e548423c241cef Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-06 (Fri, 06 Jan 2023) Changed paths: M rigs/yaesu/newcat.c M rigs/yaesu/newcat.h Log Message: ----------- Remove EX039 check from FTDX3000/3000DM https://github.com/Hamlib/Hamlib/issues/1206 Commit: 3e5080ebff5a98a52527c1c2fa4fc3818dbf7558 https://github.com/Hamlib/Hamlib/commit/3e5080ebff5a98a52527c1c2fa4fc3818dbf7558 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-06 (Fri, 06 Jan 2023) Changed paths: M rigs/kenwood/k3.c M simulators/simelecraft.c Log Message: ----------- Fix elecraft power2mW by scaling power to either 15W or 100W based on KPA availability We are ignoring the tx_range values for the Kn series https://github.com/Hamlib/Hamlib/issues/1205 Compare: https://github.com/Hamlib/Hamlib/compare/df8c625cc972...3e5080ebff5a |
From: Michael B. <no...@gi...> - 2023-01-07 05:33:42
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: eb904148b5a35dc1b13d70076370125658671778 https://github.com/Hamlib/Hamlib/commit/eb904148b5a35dc1b13d70076370125658671778 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-06 (Fri, 06 Jan 2023) Changed paths: M rigs/kenwood/k3.c M simulators/simelecraft.c Log Message: ----------- Fix elecraft power2mW by scaling power to either 15W or 100W based on KPA availability We are ignoring the tx_range values for the Kn series https://github.com/Hamlib/Hamlib/issues/1205 |
From: Michael B. <no...@gi...> - 2023-01-07 04:24:28
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 22df154486fa59489d9bc51ff220ab70e2961c66 https://github.com/Hamlib/Hamlib/commit/22df154486fa59489d9bc51ff220ab70e2961c66 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-06 (Fri, 06 Jan 2023) Changed paths: M rigs/yaesu/newcat.c M rigs/yaesu/newcat.h Log Message: ----------- Remove EX039 check from FTDX3000/3000DM https://github.com/Hamlib/Hamlib/issues/1206 |
From: Michael B. <no...@gi...> - 2023-01-06 22:42:38
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 79255fa27cba9ea1884e29df700466ef5f946566 https://github.com/Hamlib/Hamlib/commit/79255fa27cba9ea1884e29df700466ef5f946566 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-06 (Fri, 06 Jan 2023) Changed paths: M rigs/dummy/netrigctl.c Log Message: ----------- Remove unnecessary check from netrigctl.c https://github.com/Hamlib/Hamlib/issues/1155 |
From: Michael B. <no...@gi...> - 2023-01-06 22:27:32
|
Branch: refs/heads/Hamlib-4.5.4 Home: https://github.com/Hamlib/Hamlib Commit: 23e4eb2885809e087cb656a34ae6f9faee13aa7a https://github.com/Hamlib/Hamlib/commit/23e4eb2885809e087cb656a34ae6f9faee13aa7a Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-06 (Fri, 06 Jan 2023) Changed paths: M NEWS M include/hamlib/rig.h M rigs/dummy/netrigctl.c M simulators/simft991.c M src/misc.c M tests/dumpcaps.c Log Message: ----------- Fix rigctld agc level readings -- allow for rig backedn to specify "RIG_AGC_NONE" now for clarity if desired https://github.com/Hamlib/Hamlib/issues/1155 Commit: df8c625cc9723a5200bf8e4cd27fc993687ab656 https://github.com/Hamlib/Hamlib/commit/df8c625cc9723a5200bf8e4cd27fc993687ab656 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-06 (Fri, 06 Jan 2023) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Update man pages to clarify upper/lower case for set/get commands Compare: https://github.com/Hamlib/Hamlib/compare/852440b0fa14...df8c625cc972 |
From: Michael B. <no...@gi...> - 2023-01-06 22:26:32
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 4a487ffdcceb2789930fd1e941810a9f5cd4aaf8 https://github.com/Hamlib/Hamlib/commit/4a487ffdcceb2789930fd1e941810a9f5cd4aaf8 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-06 (Fri, 06 Jan 2023) Changed paths: M NEWS M include/hamlib/rig.h M rigs/dummy/netrigctl.c M simulators/simft991.c M src/misc.c M tests/dumpcaps.c Log Message: ----------- Fix rigctld agc level readings -- allow for rig backedn to specify "RIG_AGC_NONE" now for clarity if desired https://github.com/Hamlib/Hamlib/issues/1155 |
From: Michael B. <no...@gi...> - 2023-01-06 16:31:05
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: db218e9e73e6763dafb7a7137656c4faf11ef360 https://github.com/Hamlib/Hamlib/commit/db218e9e73e6763dafb7a7137656c4faf11ef360 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-06 (Fri, 06 Jan 2023) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Update man pages to clarify upper/lower case for set/get commands |
From: Michael B. <no...@gi...> - 2023-01-06 13:56:41
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 86771a95575116f31f498a8912d36e114f1109bc https://github.com/Hamlib/Hamlib/commit/86771a95575116f31f498a8912d36e114f1109bc Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-06 (Fri, 06 Jan 2023) Changed paths: M simulators/simelecraft.c Log Message: ----------- Update simelecraft.c |
From: Outlook(SV2AGW) <sv...@ou...> - 2023-01-06 05:38:48
|
Hi Mikethe URL is ok. Just copy/paste and you will download the project.BTW the same code works fine with ver 473(SV2AGW)George RossopoulosAnakreontos14GR-54250 ThessalonikiGREECEwww.sv2agw.comwww.frinos.comwww.agwtracker.comAGWPE on Facebook----------------------------------------------------------------From: Black Michael<mdb...@ya...>Sent: Πεμ 05Ιαν2023 21:44 To: Subject: Re: [Hamlib-developer] HamLib and MSVC problems=Your weblink does not work.But it seems you are not setting the COM port path correctly as it is trying to open COM1 instead of COM9.strncpy(my_rig->state.rigport.pathname, rig_file, HAMLIB_FILPATHLEN - 1);Mike W9MDBOn Thursday, January 5, 2023 at 12:23:08 PM CST, Outlook(SV2AGW) wrote: Hi I followed your advise and created the .lib and .exp files for hamlib 4.5.3 and now works (xmmm) not exactly.Seems cannot set the serial port settingsgive it a tryhttps://sv2agw.com/beta/HamLibTest.zip thera are 3 different configurationsDebug_40 with Hamlib 4Debug_453 with hamlib 4.5.3Debug_46 with Hamlib 4.6Needs Visual studio 2022 select debug_453 and press F5 to debug.You will see in the output window what happensCMainFrame::iniRadio> 1CMainFrame::iniRadio> n_rigmodel=3073CMainFrame::iniRadio> 2CMainFrame::iniRadio> rig_init OKCMainFrame::iniRadio> _strCom=\\.\COm9CMainFrame::iniRadio> ************************** rig_open: error = 1:icom.c(623):icom_init enteredicom_init: done1:icom.c(723):icom_init returning(0) 1:rig.c(812):rig_open enteredrig_settings_get_path: path=.hamlib_settingsrig_settings_load_all: settings_file (.hamlib_settings): No such file or directoryrig_open: cwd=C:\MyProjects\HamLibTest\HamLibTestrig_open: C:\MyProjects\HamLibTest\HamLibTest/hamlib_settings does not existrig_open: async_data_enable=0, async_data_supported=1serial_open: \\.\COM1serial_open(229): open failed#1serial_open(229): open failed#2serial_open(229): open failed#3serial_open(229): open failed#4serial_open: Unable to open \\.\COM1 - Bad file descriptorport_open: serial_open(\\.\COM1) status=-6, err=Bad file descriptorrig_open: rs->comm_state==0?=01:rig.c(1018):rig_open returning(-6) IO errorIO error=-6CMainFrame::iniRadio> ************************** rig_open: error =error = 0 CMainFrame::iniRadio> *******************OK RIG READY73(SV2AGW)George RossopoulosAnakreontos14GR-54250 ThessalonikiGREECEwww.sv2agw.comwww.frinos.comwww.agwtracker.comAGWPE on Facebook_______________________________________________Hamlib-developer mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
From: Michael B. <no...@gi...> - 2023-01-06 05:34:15
|
Branch: refs/heads/Hamlib-4.5.4 Home: https://github.com/Hamlib/Hamlib Commit: 990c1768f8d3a2117e94880c213ddfa7ef3c57c6 https://github.com/Hamlib/Hamlib/commit/990c1768f8d3a2117e94880c213ddfa7ef3c57c6 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-05 (Thu, 05 Jan 2023) Changed paths: M src/rig.c Log Message: ----------- Fix rig_getpower2mW so it checks all range lists https://github.com/Hamlib/Hamlib/issues/1205 Commit: 852440b0fa14cb52fef0d84c88522c6fe8dbcb99 https://github.com/Hamlib/Hamlib/commit/852440b0fa14cb52fef0d84c88522c6fe8dbcb99 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-05 (Thu, 05 Jan 2023) Changed paths: M NEWS Log Message: ----------- Update NEWS Compare: https://github.com/Hamlib/Hamlib/compare/5c478c922232...852440b0fa14 |
From: Michael B. <no...@gi...> - 2023-01-06 05:34:01
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: e6c5c15452bad475ddf69c0ae74cd63e6bc347b3 https://github.com/Hamlib/Hamlib/commit/e6c5c15452bad475ddf69c0ae74cd63e6bc347b3 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-05 (Thu, 05 Jan 2023) Changed paths: M NEWS Log Message: ----------- Update NEWS |
From: Michael B. <no...@gi...> - 2023-01-06 05:32:07
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: bbd0f856ca3f26b5d6367c4ca3d8519e58458e08 https://github.com/Hamlib/Hamlib/commit/bbd0f856ca3f26b5d6367c4ca3d8519e58458e08 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-05 (Thu, 05 Jan 2023) Changed paths: M src/rig.c Log Message: ----------- Fix rig_getpower2mW so it checks all range lists https://github.com/Hamlib/Hamlib/issues/1205 |
From: Outlook(SV2AGW) <sv...@ou...> - 2023-01-05 18:22:46
|
Hi I followed your advise and created the .lib and .exp files for hamlib 4.5.3 and now works (xmmm) not exactly.Seems cannot set the serial port settingsgive it a tryhttps://sv2agw.com/beta/HamLibTest.zip thera are 3 different configurationsDebug_40 with Hamlib 4Debug_453 with hamlib 4.5.3Debug_46 with Hamlib 4.6Needs Visual studio 2022 select debug_453 and press F5 to debug.You will see in the output window what happensCMainFrame::iniRadio> 1 CMainFrame::iniRadio> n_rigmodel=3073 CMainFrame::iniRadio> 2 CMainFrame::iniRadio> rig_init OK CMainFrame::iniRadio> _strCom=\\.\COm9 CMainFrame::iniRadio> ************************** rig_open: error = 1:icom.c(623):icom_init entered icom_init: done 1:icom.c(723):icom_init returning(0) 1:rig.c(812):rig_open entered rig_settings_get_path: path=.hamlib_settings rig_settings_load_all: settings_file (.hamlib_settings): No such file or directory rig_open: cwd=C:\MyProjects\HamLibTest\HamLibTest rig_open: C:\MyProjects\HamLibTest\HamLibTest/hamlib_settings does not exist rig_open: async_data_enable=0, async_data_supported=1 serial_open: \\.\COM1 serial_open(229): open failed#1 serial_open(229): open failed#2 serial_open(229): open failed#3 serial_open(229): open failed#4 serial_open: Unable to open \\.\COM1 - Bad file descriptor port_open: serial_open(\\.\COM1) status=-6, err=Bad file descriptor rig_open: rs->comm_state==0?=0 1:rig.c(1018):rig_open returning(-6) IO error IO error =-6 CMainFrame::iniRadio> ************************** rig_open: error =error = 0 CMainFrame::iniRadio> *******************OK RIG READY73(SV2AGW)George RossopoulosAnakreontos14GR-54250 ThessalonikiGREECEwww.sv2agw.comwww.frinos.comwww.agwtracker.comAGWPE on Facebook |
From: Philip R. - G. <gm...@bt...> - 2023-01-05 17:18:32
|
After fixing the problem in the other thread, my major application still wouldn’t run. I had a multi-step compile flow for my project and I must have got the include paths screwed up. It runs now. I’ve also moved to using the $PATH variable for pointing to DLLs rather than copying them into the executable directory. Managing directories in MSVC is a pain in the a**e. Sorry for the trouble. Phil GM3ZZA Sent from Mail for Windows From: Black Michael Sent: 04 January 2023 13:32 To: Hamlib Developers; Philip Rose - GM3ZZA Subject: Re: [Hamlib-developer] Hamlib 4.5.3 release 🎊 Sorry...but I can't help debug an application that doesn't have source code available. Mike W9MDB On Wednesday, January 4, 2023 at 07:13:40 AM CST, Philip Rose - GM3ZZA <gm...@bt...> wrote: Thanks Michael. Yes zzalog.exe is my executable. It now fails in the call to rig_set_debug(), which I now call before the first hamlib API call (rig_load_all_backends()) The only console output is:- rig_set_dcs_sql called The call stack doesn’t show my code where I call this but shows the FLTK scheduler (I think). Phil GM3ZZA Sent from Mail for Windows From: Black Michael via Hamlib-developer Sent: 03 January 2023 22:21 To: Hamlib Developers Subject: Re: [Hamlib-developer] Hamlib 4.5.3 release 🎊 I take zzalog.exe is your executable? If you turn up the debug level it might help. rig_set_debug HAMLIB_PARAMS((enum rig_debug_level_e debug_level)); rig_set_debug(RIG_DEBUG_TRACE) Mike W9MDB On Tuesday, January 3, 2023 at 03:44:51 PM CST, Philip Rose - GM3ZZA via Hamlib-developer <ham...@li...> wrote: Thanks Mike, Nate. I get an exception when I first call a hamlib API. 4.5 was OK, I got a similar fail with 4.5.2. Exception thrown at 0x5D71C5B0 (libhamlib-4.dll) in zzalog.exe: 0xC0000005: Access violation reading location 0x00002819. Not very informative I am afraid. The screenshot doesn’t give many clues either except I am calling rig_get_caps() at the time. 73 Phil GM3ZZA Sent from Mail for Windows From: Nate Bargmann Sent: 01 January 2023 01:09 To: Hamlib Developers Subject: [Hamlib-developer] Hamlib 4.5.3 release 🎊 Hi all. Thanks to the hard work of Mike and contributors, Hamlib 4.5.3 has been released. This is primarily a bug fix and stabilization release with no new models added. From the NEWS file: Version 4.5.3 2022-12-31 * Fix serial.c for hardware flow control on Linux and MacOSx * Add QRPLabs QCX/QDX rig -- not quite a TS480 * Fix QRP QRDX firmware bugs in IF message so PTT works now * FTDX5000 will now remember startup front/read settings and restore it * Fix FTDX5000 write_delay with microham * Fix grep error on MingW build Downloads are available from the usual sources: https://sourceforge.net/projects/hamlib/files/hamlib/4.5.3/ https://github.com/Hamlib/Hamlib/releases/tag/4.5.3 Enjoy and I am wishing everyone a happy and prosperous 2023! 🎉 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 _______________________________________________ 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: Philip R. - G. <gm...@bt...> - 2023-01-05 16:30:47
|
!! RTFM !! Or in my case README.w32-bin.txt! And my not very good notes from when I got 4.5 working. I had to rebuild the .lib. And of course I had to have administrator powers to do it. The magic incantation for MS 2022 (changes from 2019 in bold). PS C:\Program Files (x86)\hamlib-w32-4.5.3\lib\msvc> & 'C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.33.31629\bin\Hostx64\x86\link.exe' /lib /machine:i386 /def:libhamlib-4.def Microsoft (R) Library Manager Version 14.33.31630.0 Copyright (C) Microsoft Corporation. All rights reserved. Creating library libhamlib-4.lib and object libhamlib-4.exp My little test application works as expected – now to try my logger. Phil GM3ZZA Sent from Mail for Windows From: Philip Rose - GM3ZZA via Hamlib-developer Sent: 05 January 2023 13:49 To: Black Michael; ham...@li...; Outlook(SV2AGW) Subject: Re: [Hamlib-developer] MSVC win32 dll Problem Hi Mike, I tried to put together a simple test case for my project – files attached. I now get the error that George encountered – indeed I got it with 4.5.2. I have an inkling that it’s to do with pthreads, as the VCXPROJ file seems to indicate an error with this. This is getting a bit beyond me now. Regards Phil. GM3ZZA Sent from Mail for Windows From: Black Michael via Hamlib-developer Sent: 04 January 2023 22:18 To: ham...@li...; Outlook(SV2AGW) Subject: Re: [Hamlib-developer] MSVC win32 dll Problem Is the code available for me to test? Mike W9MDB On Wednesday, January 4, 2023 at 11:40:41 AM CST, Outlook(SV2AGW) <sv...@ou...> wrote: Hi I am using C++ with MFC and win32. When I link with the offcial release from Github the program does not start and displays (null).dll not Found. When Link with daily snapshots then runs ok but fails the rig_open function because does not understand the serial port parameters. The last working version, which i use, is 4.0 Thnak you for any help (SV2AGW)George Rossopoulos Anakreontos14 GR-54250 Thessaloniki GREECE www.sv2agw.com www.frinos.com www.agwtracker.com AGWPE on Facebook _______________________________________________ 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: Michael B. <no...@gi...> - 2023-01-05 16:03:13
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 31d2939acc21fe58b5f203fa5a1c1e6bebb947c4 https://github.com/Hamlib/Hamlib/commit/31d2939acc21fe58b5f203fa5a1c1e6bebb947c4 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-05 (Thu, 05 Jan 2023) Changed paths: M tests/rigctld.c Log Message: ----------- Fix auto_power_on check in rigctld.c |
From: Philip R. - G. <gm...@bt...> - 2023-01-05 13:49:21
|
Hi Mike, I tried to put together a simple test case for my project – files attached. I now get the error that George encountered – indeed I got it with 4.5.2. I have an inkling that it’s to do with pthreads, as the VCXPROJ file seems to indicate an error with this. This is getting a bit beyond me now. Regards Phil. GM3ZZA Sent from Mail for Windows From: Black Michael via Hamlib-developer Sent: 04 January 2023 22:18 To: ham...@li...; Outlook(SV2AGW) Subject: Re: [Hamlib-developer] MSVC win32 dll Problem Is the code available for me to test? Mike W9MDB On Wednesday, January 4, 2023 at 11:40:41 AM CST, Outlook(SV2AGW) <sv...@ou...> wrote: Hi I am using C++ with MFC and win32. When I link with the offcial release from Github the program does not start and displays (null).dll not Found. When Link with daily snapshots then runs ok but fails the rig_open function because does not understand the serial port parameters. The last working version, which i use, is 4.0 Thnak you for any help (SV2AGW)George Rossopoulos Anakreontos14 GR-54250 Thessaloniki GREECE www.sv2agw.com www.frinos.com www.agwtracker.com AGWPE on Facebook _______________________________________________ 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: Michael B. <no...@gi...> - 2023-01-04 23:34:08
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 589736e8f7e8e8def8f136436a8b9af72c32d31b https://github.com/Hamlib/Hamlib/commit/589736e8f7e8e8def8f136436a8b9af72c32d31b Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: A simulators/simid5100.c Log Message: ----------- Add simid5100.c |
From: Black M. <mdb...@ya...> - 2023-01-04 23:26:11
|
I had an idea that seems to work -- try the latest master. If you provide -C autopower_on=0 on the rigctld line it will not try and open the rig at all during startup. Mike W9MDB On Wednesday, January 4, 2023 at 04:59:03 PM CST, Black Michael <mdb...@ya...> wrote: Any particular reason you can't let rigctld turn the power on and cqrlog can turn it off if it wants? Trying to start rigctld without a powered-on rig would not be a trivial thing for Hamlib to do. Lots of checking during startup. Mike W9MDB On Wednesday, January 4, 2023 at 10:59:36 AM CST, Saku <oh...@sr...> wrote: Saku kirjoitti 3.1.2023 klo 13.49: > Hi ! I return to this subject that I have sent once to Mike @ Jul-2022. There is a problem in rigctld start (delay telnet server to be ready) if rig is powered OFF. ----------------------------------------------------------------------------- Blowing in the wind... Updated and compiled to Hamlib version Jan 3 2023 Still rigctld telnet server opens delayed if rig (IC7300) is powered off. And that is what I did expect. Because of fixed Cqrlog rigControl procedures now if connection to rigctld is refused, like it is when rig power is off, it will retry connection 10 times with one second waiting time. That helps and Cqrlog gets connected after 7 tries. Then another problem arises: 1) If rig is powered during startup everything goes very smoothly, like it has done also before my fix. 2) If rig is not powered, but parameter "-C autopower_on=1" is set at rigctld start, everything runs ok after connection to rigctld is first refused two (2) times. 3rd repeat try opens connection and all works. 3) if parameter "-C autopower_on=0" and I want Cqrlog to set rig power on with command "set_powerstat 1" it goes like follows: Cqrlog sends : Waiting for rigctld 7 @ 127.0.0.1:4532 Connected to rigctld Sending: +\chk_vfo Msg from rig:|CHKVFO: 0| "--vfo" checked:0 Sending: +\dump_caps Msg from rig:|DUMP_CAPS: CAPS DUMP FOR MODEL: 3073 ... text removed here ... CAN GET MW2POWER: Y OVERALL BACKEND WARNINGS: 0 RPRT 0| Cqrlog can get VFO: FALSE Cqrlog can switch power: TRUE Cqrlog can send Morse: TRUE Sending: +\set_powerstat Then problems start. It takes several seconds before rig power is switched on.Several times longer than when it is done by "-C autopower_on=1" Finally the response returns, how ever it is: Msg from rig:|SET_POWERSTAT: 1 RPRT -5| Power on, start polling Poll Sending: +f +m +v Msg from rig:|GET_FREQ: RPRT -9| Msg from rig:|GET_MODE: MODE: PASSBAND: 0 RPRT 0| Msg from rig:|GET_VFO: RPRT -11| Poll Sending: +f +m +v Msg from rig:|GET_FREQ: RPRT -9| Msg from rig:|GET_MODE: MODE: LSB PASSBAND: 2400 RPRT 0| Msg from rig:|GET_VFO: RPRT -11| And because SET_POWERSTAT went to state RPRT -5 Then GET_FREQ always reports RPRT -9 no matter how long I wait ! I have loaded to my Google drive two debug files that have combined Cqrlog and rigctld debugs (mixed). First with succeeded (rig was powered at start), and second failed (rig power was OFF at start) startups. Start_with_rig_powered_mixed_debug_Cqrlog_and_rigctld.pdf https://drive.google.com/file/d/1Lh7YWQsmEPk0WvWaKpE51NDVbOrE5VCA/view?usp=sharing Start_with_rig_NOT_powered_mixed_debug_Cqrlog_and_rigctld.pdf https://drive.google.com/file/d/1hlormcoPf8i8TIdmXCeu7mWRi3ZGvVid/view?usp=sharing When Cqrlog sends +\set_powerstat it stops and waits until it gets response. After that it waits a second and then starts polling rig ("Power on, start polling" show in debug) So it can not fill rigctld's TCP receiving buffer before response to set_powerstat is received. I do not know what I should send to rigctld to make it happy and stop sending RPRT -9 ! Possible bug? P.S. Adding rigctld start parameter "--vfo" changes rig polling to: Poll Sending: +f currVFO +m currVFO +v Msg from rig:|GET_FREQ: CURRVFO RPRT -9| But has no effect to this problem. -- Saku OH1KH _______________________________________________ Hamlib-developer mailing list Ham...@li... https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
From: Michael B. <no...@gi...> - 2023-01-04 23:25:20
|
Branch: refs/heads/Hamlib-4.5.4 Home: https://github.com/Hamlib/Hamlib Commit: 9e74696a427d3b455c78cade2ea8b49d258c896e https://github.com/Hamlib/Hamlib/commit/9e74696a427d3b455c78cade2ea8b49d258c896e Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M tests/rigctld.c Log Message: ----------- Allow rigctld to start with autopower_on=0 and avoid timeouts at startup Commit: 5c478c922232eb30fadc50854c1a6e65f75a63d3 https://github.com/Hamlib/Hamlib/commit/5c478c922232eb30fadc50854c1a6e65f75a63d3 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M NEWS Log Message: ----------- Update NEWS Compare: https://github.com/Hamlib/Hamlib/compare/41ad82139f95...5c478c922232 |
From: Michael B. <no...@gi...> - 2023-01-04 23:24:08
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 6dbd2cff5e1b5be4aefeb463f00391e5d05d89a5 https://github.com/Hamlib/Hamlib/commit/6dbd2cff5e1b5be4aefeb463f00391e5d05d89a5 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M NEWS Log Message: ----------- Update NEWS |