hamlib-developer Mailing List for Ham Radio Control Libraries (Page 47)
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
(83) |
Sep
(84) |
Oct
(14) |
Nov
|
Dec
|
From: Michael B. <no...@gi...> - 2024-04-28 16:34:11
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 92e82a25d2ebbbf776c4f9aa58a37dde8fc15554 https://github.com/Hamlib/Hamlib/commit/92e82a25d2ebbbf776c4f9aa58a37dde8fc15554 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-26 (Fri, 26 Apr 2024) Changed paths: M src/misc.c Log Message: ----------- Fix possible null argument in rig_test_2038 Commit: 2638eeb774ed5c162c6ab492cb3af3328cec1402 https://github.com/Hamlib/Hamlib/commit/2638eeb774ed5c162c6ab492cb3af3328cec1402 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-28 (Sun, 28 Apr 2024) Changed paths: M rigs/motorola/micom.c Log Message: ----------- Fix ptt type for Micom 2/3 and change from Motorola to Micom Compare: https://github.com/Hamlib/Hamlib/compare/fe0d47acef9d...2638eeb774ed To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-24 17:33:51
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: fe0d47acef9dd5a7401e4a4162fc5195e6f7a0c7 https://github.com/Hamlib/Hamlib/commit/fe0d47acef9dd5a7401e4a4162fc5195e6f7a0c7 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-24 (Wed, 24 Apr 2024) Changed paths: M rigs/motorola/Makefile.am Log Message: ----------- Fix motorola Makefile.am To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-24 17:22:13
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 86afa90739b3b4427646a555670c431683bc1bc8 https://github.com/Hamlib/Hamlib/commit/86afa90739b3b4427646a555670c431683bc1bc8 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-24 (Wed, 24 Apr 2024) Changed paths: A rigs/motorola/Android.mk Log Message: ----------- Add Android.mk for motorola To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-24 17:07:53
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: e9a9424eedd44ed4f8b908dfb23e3e7899bf1eb5 https://github.com/Hamlib/Hamlib/commit/e9a9424eedd44ed4f8b908dfb23e3e7899bf1eb5 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-24 (Wed, 24 Apr 2024) Changed paths: M configure.ac M include/hamlib/riglist.h M src/register.c Log Message: ----------- Adding motorola rig Commit: d7e0b214f7bcea8855f0b5570d48b06a69bf5a7e https://github.com/Hamlib/Hamlib/commit/d7e0b214f7bcea8855f0b5570d48b06a69bf5a7e Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-24 (Wed, 24 Apr 2024) Changed paths: A rigs/motorola/micom.c Log Message: ----------- Add fake freq set/get for micom Commit: 25f58afb72e993e2c51435c47ba0126d50971317 https://github.com/Hamlib/Hamlib/commit/25f58afb72e993e2c51435c47ba0126d50971317 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-24 (Wed, 24 Apr 2024) Changed paths: A rigs/motorola/Makefile.am A rigs/motorola/README.txt A rigs/motorola/motorola.c A rigs/motorola/motorola.h Log Message: ----------- Update motorola Compare: https://github.com/Hamlib/Hamlib/compare/93bd44c3d56a...25f58afb72e9 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-23 16:20:06
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 93bd44c3d56ac7d406ef0d90dc47ace1d813fec9 https://github.com/Hamlib/Hamlib/commit/93bd44c3d56ac7d406ef0d90dc47ace1d813fec9 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-23 (Tue, 23 Apr 2024) Changed paths: M simulators/simts890.c Log Message: ----------- Update simts890.c To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-23 03:47:59
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: b182ca2d51740d5dcaa126b52d4f208003b9cc86 https://github.com/Hamlib/Hamlib/commit/b182ca2d51740d5dcaa126b52d4f208003b9cc86 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-22 (Mon, 22 Apr 2024) Changed paths: M rigs/kachina/kachina.c Log Message: ----------- Fix kachina set_ptt To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-22 22:50:36
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 6a98b0b9cb8128c09ecf4cf7374bbefd09170aaf https://github.com/Hamlib/Hamlib/commit/6a98b0b9cb8128c09ecf4cf7374bbefd09170aaf Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-22 (Mon, 22 Apr 2024) Changed paths: M rigs/icom/frame.c M rigs/icom/ic7300.c Log Message: ----------- Rest of commit -- if setting FM width to other than 7000/10000/15000 cache will show requested width until next poll https://github.com/Hamlib/Hamlib/issues/1533 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-22 22:34:21
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 2b275531559f2158a2aaf5e7534b352dac708ec8 https://github.com/Hamlib/Hamlib/commit/2b275531559f2158a2aaf5e7534b352dac708ec8 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-22 (Mon, 22 Apr 2024) Changed paths: M src/rig.c Log Message: ----------- Make rig_flush_force in rig.c timeout immediately https://github.com/Hamlib/Hamlib/issues/1541 Commit: f8a67d716e54ed9ea816920f25fefbea3594571f https://github.com/Hamlib/Hamlib/commit/f8a67d716e54ed9ea816920f25fefbea3594571f Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-22 (Mon, 22 Apr 2024) Changed paths: M rigs/barrett/4100.c M rigs/barrett/barrett.c M rigs/barrett/barrett.h Log Message: ----------- Some progress getting SB4100 to work https://github.com/Hamlib/Hamlib/issues/1541 Commit: c70502ea34fd319f41d6f4d9c4ee22e30b3db846 https://github.com/Hamlib/Hamlib/commit/c70502ea34fd319f41d6f4d9c4ee22e30b3db846 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-22 (Mon, 22 Apr 2024) Changed paths: M rigs/icom/icom.c M rigs/icom/icom.h Log Message: ----------- Fix IC7300/9700 FM filter set -- now honors FM widths of 7000,10000, and 15000 Compare: https://github.com/Hamlib/Hamlib/compare/08aac883775c...c70502ea34fd To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Black M. <mdb...@ya...> - 2024-04-21 03:32:17
|
No one has tried. I can't seem to find a programming manual for either one of those rigs. The manuals don't mention anything more than setting baud rate. If there's a CAT protocol you know of please provide a reference and it can probably be implemented. Mike W9MDB On Saturday, April 20, 2024 at 07:40:03 PM CDT, George Csahanin <ge...@w2...> wrote: Didn't find any other way to pose this question so hope y'all don't mind...but has anyone tried to have a Motorola Micom-2 or 3 included in hamlib? Thanks George Csahanin W2DB Crowley, TX _______________________________________________ Hamlib-developer mailing list Ham...@li... https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
From: Michael B. <no...@gi...> - 2024-04-20 20:09:57
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: d9b57bc7a8a5cf0f93c6792a58f7db1273992199 https://github.com/Hamlib/Hamlib/commit/d9b57bc7a8a5cf0f93c6792a58f7db1273992199 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-19 (Fri, 19 Apr 2024) Changed paths: M rigs/dummy/dummy.c Log Message: ----------- Align dummy rigs Commit: c31497918f8511ad01e1dd749e7df94a00332db2 https://github.com/Hamlib/Hamlib/commit/c31497918f8511ad01e1dd749e7df94a00332db2 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-19 (Fri, 19 Apr 2024) Changed paths: M tests/rigmatrix.c Log Message: ----------- Add VFO Ops to rigmatrix.c and colorize things a bit Commit: 08aac883775c8cd89d682682f2e3b49d796e2a35 https://github.com/Hamlib/Hamlib/commit/08aac883775c8cd89d682682f2e3b49d796e2a35 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-20 (Sat, 20 Apr 2024) Changed paths: M rigs/kachina/505dsp.c M rigs/kachina/kachina.c M rigs/kachina/kachina.h Log Message: ----------- Add set_ptt for kachina 505dsp Compare: https://github.com/Hamlib/Hamlib/compare/90545a192e94...08aac883775c To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: George C. <ge...@w2...> - 2024-04-20 13:35:05
|
Didn't find any other way to pose this question so hope y'all don't mind...but has anyone tried to have a Motorola Micom-2 or 3 included in hamlib? Thanks George Csahanin W2DB Crowley, TX |
From: Michael B. <no...@gi...> - 2024-04-19 15:35:09
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 90545a192e94ebb01021c05273f5c3d8e196c2be https://github.com/Hamlib/Hamlib/commit/90545a192e94ebb01021c05273f5c3d8e196c2be Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-19 (Fri, 19 Apr 2024) Changed paths: M rigs/barrett/4100.c Log Message: ----------- Hopefully fix Barrett 4100 protocol To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-18 16:29:18
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: dce80d264a5cd093707c0e6720e18dff77f68665 https://github.com/Hamlib/Hamlib/commit/dce80d264a5cd093707c0e6720e18dff77f68665 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-18 (Thu, 18 Apr 2024) Changed paths: M rigs/dummy/flrig.c Log Message: ----------- Update FLRig version To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-18 16:23:29
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: d9b589d25499ca823777130a854768b4533cc0a6 https://github.com/Hamlib/Hamlib/commit/d9b589d25499ca823777130a854768b4533cc0a6 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-18 (Thu, 18 Apr 2024) Changed paths: M rigs/dummy/netrigctl.c Log Message: ----------- Fix unflushed data in get_lock Commit: 4c111da0d1b7206050ca719a9ff3c97e84aaa260 https://github.com/Hamlib/Hamlib/commit/4c111da0d1b7206050ca719a9ff3c97e84aaa260 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-18 (Thu, 18 Apr 2024) Changed paths: M rigs/dummy/flrig.c Log Message: ----------- Add small delay when setting VFO in FLRig to allow GUI to catch up Compare: https://github.com/Hamlib/Hamlib/compare/95b0af114f10...4c111da0d1b7 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-15 19:50:33
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 95b0af114f10defbcfbb4f1b1d9b97c7f99ee5b8 https://github.com/Hamlib/Hamlib/commit/95b0af114f10defbcfbb4f1b1d9b97c7f99ee5b8 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-15 (Mon, 15 Apr 2024) Changed paths: M tests/rigmatrix.c Log Message: ----------- Fix rigmatrix.c with new non-const rig_caps To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-15 17:47:37
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 9e42ca2052d6b3ade2d30400b952ed8c34147aa7 https://github.com/Hamlib/Hamlib/commit/9e42ca2052d6b3ade2d30400b952ed8c34147aa7 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-15 (Mon, 15 Apr 2024) Changed paths: M rigs/icom/icom.c M rigs/icom/icom.h Log Message: ----------- Add IC756 IC756PROII and IC756PROIII to execeptions on get/set_mode To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-14 10:10:55
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 331143fa173eb7bd1bd44aae60544155fcd97a1f https://github.com/Hamlib/Hamlib/commit/331143fa173eb7bd1bd44aae60544155fcd97a1f Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-13 (Sat, 13 Apr 2024) Changed paths: M rigs/kenwood/kenwood.c Log Message: ----------- Change TS890 to use SF command for mode get/set To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Black M. <mdb...@ya...> - 2024-04-14 03:55:26
|
Show me how you are running rigctl. I suspect without the --vfo switch. I just committed a change to use the SF command....see if behaves better. My simulator shows rigctl -m 2041 -r /dev/pts/4 -vvvvv --vfo m VFOA write_block(): TX 4 bytes 0000 53 46 30 3b SF0; read_string_generic(): RX 16 characters, direct=1 0000 53 46 30 30 30 30 31 34 30 37 34 30 30 30 33 3b SF0000140740003; m VFOB write_block(): TX 4 bytes 0000 53 46 31 3b SF1; read_string_generic(): RX 16 characters, direct=1 0000 53 46 31 30 30 31 34 30 37 33 35 30 30 30 32 3b SF1001407350002; M VFOA CW -1 0000 53 46 30 3b SF0; read_string_generic(): RX 16 characters, direct=1 0000 53 46 30 30 30 30 31 34 30 37 34 30 30 30 32 3b SF0000140740002; kenwood_transaction: read_string len=16 'SF0000140740002;' kenwood_transaction: returning RIG_OK, retval=0 kenwood.c(689):kenwood_transaction returning2(0) kenwood_transaction called cmd=SF0000140740003 kenwood_transaction: cmdstr = SF0000140740003 write_block(): TX 16 bytes 0000 53 46 30 30 30 30 31 34 30 37 34 30 30 30 33 3b SF0000140740003; // you only see this if mode needs to change write_block(): TX 3 bytes 0000 49 44 3b ID; read_string_generic(): RX 6 characters, direct=1 0000 49 44 30 32 34 3b ID024; Mike W9MDB On Saturday, April 13, 2024 at 06:47:22 PM CDT, George Baltz <geo...@gm...> wrote: Lets try again - no need for all those pixels. On 4/13/24 4:56 PM, Black Michael wrote: > #1 Yes -- fixed OK > #2 Yes -- for the TS990 only OK, the vfo machinations are still voodoo to me. > #3 I'll check on my simulator May be caused by #5 > #4 My mistake -- SF is only for the 890 -- not the 990 OK > #5 No guarantees when VFO is switched right now. This is definitely a regression. The attached shows my normal TS-890S front panel, with VFO A somewhere in the phone band, and VFO B down in CW/FT8 territory. It's this way about 50% of the time, as I can switch back and forth with one button (A<>B). And yes, the rigctl 'm' command shows the mode as FM, not USB-DATA. > > On Saturday, April 13, 2024 at 02:02:12 PM CDT, George Baltz <geo...@gm...> wrote: > > > > > > > Better, but... > > 1) Shouldn't line kenwood.c:2475 use vfo, not curr_vfo > > 2) kenwood_get_mode() still calls kenwood_get_vfo_main_sub() > > 3) Somehow these changes have made my rig announce the mode (morse "UD") every time wsjtx switches from RX to TX and back. > > 4) Can't you use SF on the 890 also? > > 5) It still looks like kenwood_get_mode will be confused by vfo B on the left. > > > On 4/13/24 8:15 AM, Black Michael via Hamlib-developer wrote: > > >> > > Try this DLL. Looks like some more changes are need for the TS890/990 to get the correct VFO under all conditions (namely Split VFOB/VFOA instead of just Split VFOA/VFOB). > > But that can wait as it's a rare situation when somebody wants to do reverse split (as in nobody has ever asked for it). > > > > > https://www.dropbox.com/scl/fi/ccchzrdd9u35jguwbhhxo/libhamlib-4.dll?rlkey=dnpxz9fb6eci696uextmwja8o&dl=0 > > > > > > Just to give you an idea of what's going on. > > > > > #1 We need to determine the current VFO -- but that depends on transmit status and split status So we need FR/FT and then transmit status to figure out what "OM" is answering with. > > #2 Then we have set mode -- the 890 cannot set mode on B directly...have to make VFOB the active vfo with FR1;, set mode with OM, then set FR0; back. But this also depends on which way split is being done which I haven't implemented yet for reverse split. The TS990 looks like we can use the SF command to set freq/mode on either VFO which I'll have to implement. > > > > > Mike W9MDB > > > > > > > > > > > > > > > > > > > > On Friday, April 12, 2024 at 07:14:08 AM CDT, Brian Morrison via Hamlib-developer <ham...@li...> wrote: > > > > > > > > > On Fri, 12 Apr 2024 05:23:09 -0400 > George Baltz <geo...@gm...> wrote: > >> This commit breaks TS-890S operation. The TS-990 code path calls >> kenwood_get_vfo_main_sub(), which is TS-990 specific - it uses the >> "CB" command which does not exist on the TS-890S. So >> kenwood_get_mode() fails, and thing go downhill fast. >> >> It also does not handle correctly the somewhat bizarre function of >> the 890 OM command - vfo B does not always mean P1 = 1. > Thanks for confirming what I am seeing George, just goes to show that > Kenwood firmware is a variable feast. > |
From: George B. <geo...@gm...> - 2024-04-13 23:47:27
|
Lets try again - no need for all those pixels. On 4/13/24 4:56 PM, Black Michael wrote: > #1 Yes -- fixed OK > #2 Yes -- for the TS990 only OK, the vfo machinations are still voodoo to me. > #3 I'll check on my simulator May be caused by #5 > #4 My mistake -- SF is only for the 890 -- not the 990 OK > #5 No guarantees when VFO is switched right now. This is definitely a regression. The attached shows my normal TS-890S front panel, with VFO A somewhere in the phone band, and VFO B down in CW/FT8 territory. It's this way about 50% of the time, as I can switch back and forth with one button (A<>B). And yes, the rigctl 'm' command shows the mode as FM, not USB-DATA. > > On Saturday, April 13, 2024 at 02:02:12 PM CDT, George Baltz <geo...@gm...> wrote: > > > > > > > Better, but... > > 1) Shouldn't line kenwood.c:2475 use vfo, not curr_vfo > > 2) kenwood_get_mode() still calls kenwood_get_vfo_main_sub() > > 3) Somehow these changes have made my rig announce the mode (morse "UD") every time wsjtx switches from RX to TX and back. > > 4) Can't you use SF on the 890 also? > > 5) It still looks like kenwood_get_mode will be confused by vfo B on the left. > > > On 4/13/24 8:15 AM, Black Michael via Hamlib-developer wrote: > > >> > > Try this DLL. Looks like some more changes are need for the TS890/990 to get the correct VFO under all conditions (namely Split VFOB/VFOA instead of just Split VFOA/VFOB). > > But that can wait as it's a rare situation when somebody wants to do reverse split (as in nobody has ever asked for it). > > > > > https://www.dropbox.com/scl/fi/ccchzrdd9u35jguwbhhxo/libhamlib-4.dll?rlkey=dnpxz9fb6eci696uextmwja8o&dl=0 > > > > > > Just to give you an idea of what's going on. > > > > > #1 We need to determine the current VFO -- but that depends on transmit status and split status So we need FR/FT and then transmit status to figure out what "OM" is answering with. > > #2 Then we have set mode -- the 890 cannot set mode on B directly...have to make VFOB the active vfo with FR1;, set mode with OM, then set FR0; back. But this also depends on which way split is being done which I haven't implemented yet for reverse split. The TS990 looks like we can use the SF command to set freq/mode on either VFO which I'll have to implement. > > > > > Mike W9MDB > > > > > > > > > > > > > > > > > > > > On Friday, April 12, 2024 at 07:14:08 AM CDT, Brian Morrison via Hamlib-developer <ham...@li...> wrote: > > > > > > > > > On Fri, 12 Apr 2024 05:23:09 -0400 > George Baltz <geo...@gm...> wrote: > >> This commit breaks TS-890S operation. The TS-990 code path calls >> kenwood_get_vfo_main_sub(), which is TS-990 specific - it uses the >> "CB" command which does not exist on the TS-890S. So >> kenwood_get_mode() fails, and thing go downhill fast. >> >> It also does not handle correctly the somewhat bizarre function of >> the 890 OM command - vfo B does not always mean P1 = 1. > Thanks for confirming what I am seeing George, just goes to show that > Kenwood firmware is a variable feast. > |
From: Michael B. <no...@gi...> - 2024-04-13 21:42:12
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: a6ad5f0928b23a0717426e708dd4d1fe3b8a9592 https://github.com/Hamlib/Hamlib/commit/a6ad5f0928b23a0717426e708dd4d1fe3b8a9592 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-13 (Sat, 13 Apr 2024) Changed paths: M rigs/kenwood/kenwood.c Log Message: ----------- Fix TS890 set_vfo in set_mode To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Black M. <mdb...@ya...> - 2024-04-13 20:56:45
|
#1 Yes -- fixed #2 Yes -- for the TS990 only #3 I'll check on my simulator #4 My mistake -- SF is only for the 890 -- not the 990 #5 No guarantees when VFO is switched right now. On Saturday, April 13, 2024 at 02:02:12 PM CDT, George Baltz <geo...@gm...> wrote: Better, but... 1) Shouldn't line kenwood.c:2475 use vfo, not curr_vfo 2) kenwood_get_mode() still calls kenwood_get_vfo_main_sub() 3) Somehow these changes have made my rig announce the mode (morse "UD") every time wsjtx switches from RX to TX and back. 4) Can't you use SF on the 890 also? 5) It still looks like kenwood_get_mode will be confused by vfo B on the left. On 4/13/24 8:15 AM, Black Michael via Hamlib-developer wrote: > Try this DLL. Looks like some more changes are need for the TS890/990 to get the correct VFO under all conditions (namely Split VFOB/VFOA instead of just Split VFOA/VFOB). But that can wait as it's a rare situation when somebody wants to do reverse split (as in nobody has ever asked for it). https://www.dropbox.com/scl/fi/ccchzrdd9u35jguwbhhxo/libhamlib-4.dll?rlkey=dnpxz9fb6eci696uextmwja8o&dl=0 Just to give you an idea of what's going on. #1 We need to determine the current VFO -- but that depends on transmit status and split status So we need FR/FT and then transmit status to figure out what "OM" is answering with. #2 Then we have set mode -- the 890 cannot set mode on B directly...have to make VFOB the active vfo with FR1;, set mode with OM, then set FR0; back. But this also depends on which way split is being done which I haven't implemented yet for reverse split. The TS990 looks like we can use the SF command to set freq/mode on either VFO which I'll have to implement. Mike W9MDB On Friday, April 12, 2024 at 07:14:08 AM CDT, Brian Morrison via Hamlib-developer <ham...@li...> wrote: On Fri, 12 Apr 2024 05:23:09 -0400 George Baltz <geo...@gm...> wrote: > This commit breaks TS-890S operation. The TS-990 code path calls > kenwood_get_vfo_main_sub(), which is TS-990 specific - it uses the > "CB" command which does not exist on the TS-890S. So > kenwood_get_mode() fails, and thing go downhill fast. > > It also does not handle correctly the somewhat bizarre function of > the 890 OM command - vfo B does not always mean P1 = 1. Thanks for confirming what I am seeing George, just goes to show that Kenwood firmware is a variable feast. -- Brian G8SEZ _______________________________________________ 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 _______________________________________________ Hamlib-developer mailing list Ham...@li... https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
From: George B. <geo...@gm...> - 2024-04-13 19:01:52
|
Better, but... 1) Shouldn't line kenwood.c:2475 use vfo, not curr_vfo 2) kenwood_get_mode() still calls kenwood_get_vfo_main_sub() 3) Somehow these changes have made my rig announce the mode (morse "UD") every time wsjtx switches from RX to TX and back. 4) Can't you use SF on the 890 also? 5) It still looks like kenwood_get_mode will be confused by vfo B on the left. On 4/13/24 8:15 AM, Black Michael via Hamlib-developer wrote: > Try this DLL. Looks like some more changes are need for the TS890/990 > to get the correct VFO under all conditions (namely Split VFOB/VFOA > instead of just Split VFOA/VFOB). > But that can wait as it's a rare situation when somebody wants to do > reverse split (as in nobody has ever asked for it). > > https://www.dropbox.com/scl/fi/ccchzrdd9u35jguwbhhxo/libhamlib-4.dll?rlkey=dnpxz9fb6eci696uextmwja8o&dl=0 > <https://www.dropbox.com/scl/fi/ccchzrdd9u35jguwbhhxo/libhamlib-4.dll?rlkey=dnpxz9fb6eci696uextmwja8o&dl=0> > > Just to give you an idea of what's going on. > > #1 We need to determine the current VFO -- but that depends on > transmit status and split status So we need FR/FT and then transmit > status to figure out what "OM" is answering with. > #2 Then we have set mode -- the 890 cannot set mode on B > directly...have to make VFOB the active vfo with FR1;, set mode with > OM, then set FR0; back. But this also depends on which way split is > being done which I haven't implemented yet for reverse split. The > TS990 looks like we can use the SF command to set freq/mode on either > VFO which I'll have to implement. > > Mike W9MDB > > > > > On Friday, April 12, 2024 at 07:14:08 AM CDT, Brian Morrison via > Hamlib-developer <ham...@li...> wrote: > > > On Fri, 12 Apr 2024 05:23:09 -0400 > George Baltz <geo...@gm...> wrote: > > > This commit breaks TS-890S operation. The TS-990 code path calls > > kenwood_get_vfo_main_sub(), which is TS-990 specific - it uses the > > "CB" command which does not exist on the TS-890S. So > > kenwood_get_mode() fails, and thing go downhill fast. > > > > It also does not handle correctly the somewhat bizarre function of > > the 890 OM command - vfo B does not always mean P1 = 1. > > Thanks for confirming what I am seeing George, just goes to show that > Kenwood firmware is a variable feast. > > -- > > Brian G8SEZ > > > > _______________________________________________ > 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...> - 2024-04-13 14:56:03
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: b42aa75dd8251721345e89926e0bd4140fa2accb https://github.com/Hamlib/Hamlib/commit/b42aa75dd8251721345e89926e0bd4140fa2accb Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-13 (Sat, 13 Apr 2024) Changed paths: M rigs/kenwood/kenwood.c Log Message: ----------- astyle kenwood.c To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-04-13 12:26:14
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 6cfdb9d4eddf8b135a3961e5d41912a6c1152348 https://github.com/Hamlib/Hamlib/commit/6cfdb9d4eddf8b135a3961e5d41912a6c1152348 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-04-13 (Sat, 13 Apr 2024) Changed paths: M rigs/kenwood/kenwood.c M rigs/kenwood/kenwood.h Log Message: ----------- Fix TS890 set_mode To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Black M. <mdb...@ya...> - 2024-04-13 12:16:01
|
Try this DLL. Looks like some more changes are need for the TS890/990 to get the correct VFO under all conditions (namely Split VFOB/VFOA instead of just Split VFOA/VFOB).But that can wait as it's a rare situation when somebody wants to do reverse split (as in nobody has ever asked for it). https://www.dropbox.com/scl/fi/ccchzrdd9u35jguwbhhxo/libhamlib-4.dll?rlkey=dnpxz9fb6eci696uextmwja8o&dl=0 Just to give you an idea of what's going on. #1 We need to determine the current VFO -- but that depends on transmit status and split status So we need FR/FT and then transmit status to figure out what "OM" is answering with. #2 Then we have set mode -- the 890 cannot set mode on B directly...have to make VFOB the active vfo with FR1;, set mode with OM, then set FR0; back. But this also depends on which way split is being done which I haven't implemented yet for reverse split. The TS990 looks like we can use the SF command to set freq/mode on either VFO which I'll have to implement. Mike W9MDB On Friday, April 12, 2024 at 07:14:08 AM CDT, Brian Morrison via Hamlib-developer <ham...@li...> wrote: On Fri, 12 Apr 2024 05:23:09 -0400 George Baltz <geo...@gm...> wrote: > This commit breaks TS-890S operation. The TS-990 code path calls > kenwood_get_vfo_main_sub(), which is TS-990 specific - it uses the > "CB" command which does not exist on the TS-890S. So > kenwood_get_mode() fails, and thing go downhill fast. > > It also does not handle correctly the somewhat bizarre function of > the 890 OM command - vfo B does not always mean P1 = 1. Thanks for confirming what I am seeing George, just goes to show that Kenwood firmware is a variable feast. -- Brian G8SEZ _______________________________________________ Hamlib-developer mailing list Ham...@li... https://lists.sourceforge.net/lists/listinfo/hamlib-developer |