hamlib-developer Mailing List for Ham Radio Control Libraries (Page 95)
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: Michael B. <no...@gi...> - 2023-01-04 23:23:28
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 902be172c1613d97bcba8f90e9199100c0578b0b https://github.com/Hamlib/Hamlib/commit/902be172c1613d97bcba8f90e9199100c0578b0b 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 |
|
From: Black M. <mdb...@ya...> - 2023-01-04 22:59:16
|
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: Black M. <mdb...@ya...> - 2023-01-04 22:18:07
|
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 |
|
From: Michael B. <no...@gi...> - 2023-01-04 21:51:13
|
Branch: refs/heads/Hamlib-4.5.4 Home: https://github.com/Hamlib/Hamlib Commit: 4b5719506907205daa38ff11fcc9f7fe5bf4eb2d https://github.com/Hamlib/Hamlib/commit/4b5719506907205daa38ff11fcc9f7fe5bf4eb2d Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-03 (Tue, 03 Jan 2023) Changed paths: M rigs/icom/icom.c M rigs/icom/icom.h Log Message: ----------- Another attempt to fix get/set freq for ID5100 ID4100 ID31 ID51 https://github.com/Hamlib/Hamlib/issues/1202 https://github.com/Hamlib/Hamlib/issues/1200 Commit: 711b7c9d7ecb32c0972677c89f2489abff7e0ca9 https://github.com/Hamlib/Hamlib/commit/711b7c9d7ecb32c0972677c89f2489abff7e0ca9 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-03 (Tue, 03 Jan 2023) Changed paths: M rigs/icom/icom.c Log Message: ----------- Fix units for get freq for ID5100 ID4100 ID31 ID51 https://github.com/Hamlib/Hamlib/issues/1200 Commit: f8657f0d4d96700233d27bf155461883ef8280fb https://github.com/Hamlib/Hamlib/commit/f8657f0d4d96700233d27bf155461883ef8280fb Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/icom/icom.c M rigs/icom/icom.h M rigs/icom/id5100.c Log Message: ----------- Fix ID5100 get/set_mode Remove ID rigs freq_len check as civ_731 setting should cover it https://github.com/Hamlib/Hamlib/issues/1204 Commit: 247c3670f939c4152bd391e76fe0f19171c0c89c https://github.com/Hamlib/Hamlib/commit/247c3670f939c4152bd391e76fe0f19171c0c89c Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/yaesu/ft1000mp.c Log Message: ----------- Add PKTUSB to ft1000mp rigs Commit: c20c63c7528a67d5e5eeddfe9e18aff770f67c29 https://github.com/Hamlib/Hamlib/commit/c20c63c7528a67d5e5eeddfe9e18aff770f67c29 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/icom/id4100.c M rigs/icom/id5100.c Log Message: ----------- Remove XONXOFF flow control from ID5100 and ID4100 -- Firmware E8 is not working correclty that flow control https://github.com/Hamlib/Hamlib/issues/1202 Commit: 2f4993cdac75a3ecb918d1332095111126fbff3e https://github.com/Hamlib/Hamlib/commit/2f4993cdac75a3ecb918d1332095111126fbff3e Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/icom/icom.c Log Message: ----------- Make 3-byte Icom ID rigs show error message Commit: 720085873567ce616cfe30c7149e3473dbe7c3a8 https://github.com/Hamlib/Hamlib/commit/720085873567ce616cfe30c7149e3473dbe7c3a8 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/dummy/netrigctl.c Log Message: ----------- Get dummy rig to work with grig by disallowing empty "u" calls Commit: 41ad82139f954913090aa83d2e322a6e58412542 https://github.com/Hamlib/Hamlib/commit/41ad82139f954913090aa83d2e322a6e58412542 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/icom/icom.c M rigs/icom/id4100.c M rigs/icom/id5100.c M simulators/Makefile.am Log Message: ----------- Update ID5100 and ID4100 Promote ID5100 to stable https://github.com/Hamlib/Hamlib/issues/1204 https://github.com/Hamlib/Hamlib/issues/1202 https://github.com/Hamlib/Hamlib/issues/1202 Compare: https://github.com/Hamlib/Hamlib/compare/780872ed84f7...41ad82139f95 |
|
From: Michael B. <no...@gi...> - 2023-01-04 21:46:42
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: f1b6d322ba549a245ff9e488b3e02b755512e1aa https://github.com/Hamlib/Hamlib/commit/f1b6d322ba549a245ff9e488b3e02b755512e1aa Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M NEWS Log Message: ----------- Update NEWS |
|
From: Michael B. <no...@gi...> - 2023-01-04 21:42:49
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 87cc9a8c3d133ab18a6f4b9758e98836bd0fd101 https://github.com/Hamlib/Hamlib/commit/87cc9a8c3d133ab18a6f4b9758e98836bd0fd101 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/icom/icom.c M rigs/icom/id4100.c M rigs/icom/id5100.c M simulators/Makefile.am M tests/rigctltcp.c Log Message: ----------- Update ID5100 and ID4100 Promote ID5100 to stable https://github.com/Hamlib/Hamlib/issues/1204 https://github.com/Hamlib/Hamlib/issues/1202 https://github.com/Hamlib/Hamlib/issues/1202 |
|
From: Michael B. <no...@gi...> - 2023-01-04 21:40:02
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 383c95b9c4cfce2cc7b3ad243c997953b716994c https://github.com/Hamlib/Hamlib/commit/383c95b9c4cfce2cc7b3ad243c997953b716994c Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/dummy/netrigctl.c Log Message: ----------- Get dummy rig to work with grig by disallowing empty "u" calls |
|
From: Outlook(SV2AGW) <sv...@ou...> - 2023-01-04 17:40:27
|
HiI 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.0Thnak you for any help(SV2AGW)George RossopoulosAnakreontos14GR-54250 ThessalonikiGREECEwww.sv2agw.comwww.frinos.comwww.agwtracker.comAGWPE on Facebook |
|
From: Saku <oh...@sr...> - 2023-01-04 16:59:21
|
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 |
|
From: Michael B. <no...@gi...> - 2023-01-04 16:49:03
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: cceffce4a50bf4413dfcca0e1ba3d2ada7aa48a6 https://github.com/Hamlib/Hamlib/commit/cceffce4a50bf4413dfcca0e1ba3d2ada7aa48a6 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/icom/id4100.c M rigs/icom/id5100.c Log Message: ----------- Remove XONXOFF flow control from ID5100 and ID4100 -- Firmware E8 is not working correclty that flow control https://github.com/Hamlib/Hamlib/issues/1202 Commit: af9a7a6938f0f7a7ea7c329b110241480f474577 https://github.com/Hamlib/Hamlib/commit/af9a7a6938f0f7a7ea7c329b110241480f474577 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/icom/icom.c Log Message: ----------- Make 3-byte Icom ID rigs show error message Compare: https://github.com/Hamlib/Hamlib/compare/0404b43bd822...af9a7a6938f0 |
|
From: Black M. <mdb...@ya...> - 2023-01-04 13:32:25
|
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: Michael B. <no...@gi...> - 2023-01-04 13:24:32
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 0404b43bd8225608d443dab3a48f1161b12b2486 https://github.com/Hamlib/Hamlib/commit/0404b43bd8225608d443dab3a48f1161b12b2486 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/yaesu/ft1000mp.c Log Message: ----------- Add PKTUSB to ft1000mp rigs |
|
From: Philip R. - G. <gm...@bt...> - 2023-01-04 13:13:49
|
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: Michael B. <no...@gi...> - 2023-01-04 12:58:35
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 138795668f66c472bcaf16f3b1eb7076dfad88ba https://github.com/Hamlib/Hamlib/commit/138795668f66c472bcaf16f3b1eb7076dfad88ba Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-04 (Wed, 04 Jan 2023) Changed paths: M rigs/icom/icom.c M rigs/icom/icom.h M rigs/icom/id5100.c Log Message: ----------- Fix ID5100 get/set_mode Remove ID rigs freq_len check as civ_731 setting should cover it https://github.com/Hamlib/Hamlib/issues/1204 |
|
From: Michael B. <no...@gi...> - 2023-01-03 23:55:24
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 9c5809ffba8712c314a78dcadcfe8ae75a1beaa7 https://github.com/Hamlib/Hamlib/commit/9c5809ffba8712c314a78dcadcfe8ae75a1beaa7 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-03 (Tue, 03 Jan 2023) Changed paths: M rigs/icom/icom.c Log Message: ----------- Fix units for get freq for ID5100 ID4100 ID31 ID51 https://github.com/Hamlib/Hamlib/issues/1200 |
|
From: Black M. <mdb...@ya...> - 2023-01-03 22:21:11
|
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 |
|
From: Philip R. - G. <gm...@bt...> - 2023-01-03 21:00:23
|
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
|
|
From: Michael B. <no...@gi...> - 2023-01-03 18:19:26
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 1b6b78f54a98f9450a621895fd759d89435fb060 https://github.com/Hamlib/Hamlib/commit/1b6b78f54a98f9450a621895fd759d89435fb060 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-03 (Tue, 03 Jan 2023) Changed paths: M rigs/icom/icom.c M rigs/icom/icom.h Log Message: ----------- Another attempt to fix get/set freq for ID5100 ID4100 ID31 ID51 https://github.com/Hamlib/Hamlib/issues/1202 https://github.com/Hamlib/Hamlib/issues/1200 |
|
From: Saku <oh...@sr...> - 2023-01-03 11:50:08
|
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. ----------------------------------------------------------------------------- Setup here is as follows: Fedora 36, Icom IC7300 connected with USB A/B cable. CI-V Link to [REMOTE] CI-V Baud rate 19200 CI-V Tranceive OFF rigctld --version: rigctl Hamlib 4.6~git Mo Dec 12 05:18:38 2022 +0000 SHA=df8b88 ----------------------------------------------------------------------------- Preface: Cqrlog uses rigctld by sending text commands via telnet (localhost:4532). Most common way is that Cqrlog starts rigctld when it is starting. Cqrlog expects that rigctld will accept connections to localhost:4532 right after it has started that. How ever if rig, here Icom IC7300, is powered off during Cqrlog start (but having power supply ON) rigctld does not open telnet service immediately. If rig is already powered on using power button at rig front face rigctld responses immediately to telnet connect request. ----------------------------------------------------------------------------- Problem: Script to reproduce telnet server startup delay: [saku@hamtpad tmp]$ cat ./tst.sh #!/bin/bash echo "Starting /usr/local/bin/rigctld" echo "parameters: -m 3073 -r /dev/icom7300 -t 4532 -s 19200 -C auto_power_on=0 --vfo &" /usr/local/bin/rigctld -m 3073 -r /dev/icom7300 -t 4532 -s 19200 -C auto_power_on=0 --vfo & SECONDS=0 while [ 1 -gt 0 ] do telnet localhost 4532 echo "Time passed since rigctld was started: "$SECONDS" sec" sleep 1 done ----------------------------------------------------------------------------- *1) Result when IC7300 has power supply ON, but NOT powered by it's Power button:* [saku@hamtpad tmp]$ ./tst.sh Starting /usr/local/bin/rigctld parameters: -m 3073 -r /dev/icom7300 -t 4532 -s 19200 -C auto_power_on=0 --vfo & Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused Time passed since rigctld was started: 0 sec Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused Time passed since rigctld was started: 1 sec Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused Time passed since rigctld was started: 2 sec Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused Time passed since rigctld was started: 3 sec Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused Time passed since rigctld was started: 4 sec Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused Time passed since rigctld was started: 5 sec Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused Time passed since rigctld was started: 6 sec Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. *It takes 7 seconds before rigctld's telnet server accepts connections when ic7300 powered OFF* ----------------------------------------------------------------------------- *2) Result when IC7300 has power supply ON, and powered ON by it's Power button:* [saku@hamtpad tmp]$ ./tst.sh Starting /usr/local/bin/rigctld parameters: -m 3073 -r /dev/icom7300 -t 4532 -s 19200 -C auto_power_on=0 --vfo & Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused Time passed since rigctld was started: 0 sec Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. *rigctld's telnet server immediately accepts connections when ic7300 powered ON* ----------------------------------------------------------------------------- That is the bottle neck. Rigtcld does not open TCP service immediately. I think it tries to catch rig for some time and after run to timeout (perhaps?) it opens TCP telnet service. That came in to my mind because when *auto_power_on=1 then at the time 2 sec passed rig turns ON but telnet still does not get connected*. So rigctld must be working with rig and has not opend telnet socket yet even rig is already powered on by ci-v command. * * *That means NO command can be sent during 7sec waiting time* because we do not have any telnet connection. It also means that if rigctld is started at same time with the client program (maybe inside from client like Cqrlog do), while rig is powered off, client will fail to get connected to rigctld. *Suggestion:** *** ** *TCP telnet service should open immediately and after that rigctld should start seeking is there a rig with user stated "-m" model and stack commands received via telnet while doing that. * ----------------------------------------------------------------------------- File with debug texts Start_with_rig_power_off_and_vvvvv.txt (over 500 lines) can be found from my Google drive: https://drive.google.com/file/d/1fY5Mbhz5feWkggWTnlqBi9nN6Gvqivdc/view?usp=sharing -- Saku OH1KH |
|
From: Michael B. <no...@gi...> - 2023-01-03 05:30:41
|
Branch: refs/heads/Hamlib-4.5.4 Home: https://github.com/Hamlib/Hamlib Commit: 780872ed84f700cddd9c8057ee185f2531cf4ffa https://github.com/Hamlib/Hamlib/commit/780872ed84f700cddd9c8057ee185f2531cf4ffa Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-02 (Mon, 02 Jan 2023) Changed paths: M rigs/icom/icom.c Log Message: ----------- Convert Icom 3-byte frequency to Hz from KHz https://github.com/Hamlib/Hamlib/issues/1200 |
|
From: Michael B. <no...@gi...> - 2023-01-03 05:05:54
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 4c09344f32cff0eb27333b904db017324aef4be7 https://github.com/Hamlib/Hamlib/commit/4c09344f32cff0eb27333b904db017324aef4be7 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-02 (Mon, 02 Jan 2023) Changed paths: M rigs/icom/icom.c Log Message: ----------- Convert Icom 3-byte frequency to Hz from KHz https://github.com/Hamlib/Hamlib/issues/1200 |
|
From: Michael B. <no...@gi...> - 2023-01-02 17:39:59
|
Branch: refs/heads/Hamlib-4.5.4 Home: https://github.com/Hamlib/Hamlib Commit: f8de5c52ce0b5ac6946177c25c5b7d9e82afb151 https://github.com/Hamlib/Hamlib/commit/f8de5c52ce0b5ac6946177c25c5b7d9e82afb151 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-02 (Mon, 02 Jan 2023) Changed paths: M tests/Makefile.am Log Message: ----------- Remove rigctltcp from tests/Makefile.am |
|
From: Michael B. <no...@gi...> - 2023-01-02 17:38:55
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 9f0bd7b310e7d21c857052cb6249d6210caabd61 https://github.com/Hamlib/Hamlib/commit/9f0bd7b310e7d21c857052cb6249d6210caabd61 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-02 (Mon, 02 Jan 2023) Changed paths: A tests/rigctltcp.c Log Message: ----------- Add rigctltcp.c -- not working yet |
|
From: Michael B. <no...@gi...> - 2023-01-02 17:33:12
|
Branch: refs/heads/Hamlib-4.5.4 Home: https://github.com/Hamlib/Hamlib Commit: 1199dc2b6ba503e1762dc0e346e8b22e62486cb8 https://github.com/Hamlib/Hamlib/commit/1199dc2b6ba503e1762dc0e346e8b22e62486cb8 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-02 (Mon, 02 Jan 2023) Changed paths: M include/hamlib/rig.h M rigs/icom/icom.c M rigs/icom/icom.h M rigs/icom/id31.c M rigs/icom/id4100.c M rigs/icom/id51.c M src/rig.c M tests/Makefile.am Log Message: ----------- Fix ID5100 ID4100 ID31 ID51 get/set freq Remove get_powerstat from ID4100 ID31 ID51 as it they are not capable Add new rig_is_model function to help with Icom rig identification checks https://github.com/Hamlib/Hamlib/issues/1202 https://github.com/Hamlib/Hamlib/issues/1200 Commit: 7dae16a1456914c681ededc849f6b4ca23151180 https://github.com/Hamlib/Hamlib/commit/7dae16a1456914c681ededc849f6b4ca23151180 Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-02 (Mon, 02 Jan 2023) Changed paths: M NEWS Log Message: ----------- Update NEWS Compare: https://github.com/Hamlib/Hamlib/compare/b22db1cf34b1...7dae16a14569 |
|
From: Michael B. <no...@gi...> - 2023-01-02 17:32:37
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 0b2f0873b036b339f5f65412cc17a464cc2ef3ba https://github.com/Hamlib/Hamlib/commit/0b2f0873b036b339f5f65412cc17a464cc2ef3ba Author: Mike Black W9MDB <mdb...@ya...> Date: 2023-01-02 (Mon, 02 Jan 2023) Changed paths: M NEWS Log Message: ----------- Update NEWS |
33 messages has been excluded from this view by a project administrator.
