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
(58) |
Oct
|
Nov
|
Dec
|
From: Michael B. <no...@gi...> - 2024-09-22 15:31:51
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: f63b60a86644e9d0cf4af1c6c4b5891974a80129 https://github.com/Hamlib/Hamlib/commit/f63b60a86644e9d0cf4af1c6c4b5891974a80129 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-22 (Sun, 22 Sep 2024) Changed paths: M rigs/icom/icom.c M rigs/icom/icom.h Log Message: ----------- Ensure satmode flag is set in icom.c To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-22 14:53:37
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 4613f7d9331686ab5d75a424aebaa05e52b30d32 https://github.com/Hamlib/Hamlib/commit/4613f7d9331686ab5d75a424aebaa05e52b30d32 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-22 (Sun, 22 Sep 2024) Changed paths: M src/network.c Log Message: ----------- Reduce WARN to VERBOSE in network.c To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-22 14:48:30
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: e24617a4fe22a134701a8c800c8170fa80b72220 https://github.com/Hamlib/Hamlib/commit/e24617a4fe22a134701a8c800c8170fa80b72220 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-22 (Sun, 22 Sep 2024) Changed paths: M rigs/kenwood/ts480.c Log Message: ----------- Add get/set clock for QRPLabs QMX To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-22 03:46:01
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 56eda7a76c6fea9504cc70ea895a82b8f2d6699a https://github.com/Hamlib/Hamlib/commit/56eda7a76c6fea9504cc70ea895a82b8f2d6699a Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-21 (Sat, 21 Sep 2024) Changed paths: M src/rig.c Log Message: ----------- Do not start multicast routines -- defer to 4.7 when client software may be available Was causing some problems during auto_power_on To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-22 03:36:26
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: b0afbd22e6b56893ad86bec181423f26cff4bb32 https://github.com/Hamlib/Hamlib/commit/b0afbd22e6b56893ad86bec181423f26cff4bb32 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-21 (Sat, 21 Sep 2024) Changed paths: M NEWS Log Message: ----------- Update NEWS Commit: 96bd1367fb84754c16e7429e16963fe01287555e https://github.com/Hamlib/Hamlib/commit/96bd1367fb84754c16e7429e16963fe01287555e Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-21 (Sat, 21 Sep 2024) Changed paths: M rigs/yaesu/ft736.c Log Message: ----------- Add get_mode to FT736 Compare: https://github.com/Hamlib/Hamlib/compare/55f83b1647aa...96bd1367fb84 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-21 22:49:38
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 4efdf1dffdf2053f509eba8138d1f9cdfa4900d0 https://github.com/Hamlib/Hamlib/commit/4efdf1dffdf2053f509eba8138d1f9cdfa4900d0 Author: MarcFontaine <Mar...@us...> Date: 2024-09-22 (Sun, 22 Sep 2024) Changed paths: M include/hamlib/riglist.h M rigs/rs/Makefile.am M rigs/rs/rs.c A rigs/rs/xk852.c A rigs/rs/xk852.h Log Message: ----------- Add support for the Rhode&Schwarz XK852 transceiver. Working: * Set and get frequency * Set and get mode * Set and get RFPOWER level * PTT On/Off Setting the transmission power level: Rig command: L RFPOWER 0.0 => Receive only Rig command: L RFPOWER 0.05 => TX low power Rig command: L RFPOWER 0.15 => TX mid power Rig command: L RFPOWER 0.55 => TX high power Commit: 55f83b1647aa43fc6cd0a946e57f2fd81287d075 https://github.com/Hamlib/Hamlib/commit/55f83b1647aa43fc6cd0a946e57f2fd81287d075 Author: Michael Black <mdb...@ya...> Date: 2024-09-21 (Sat, 21 Sep 2024) Changed paths: M include/hamlib/riglist.h M rigs/rs/Makefile.am M rigs/rs/rs.c A rigs/rs/xk852.c A rigs/rs/xk852.h Log Message: ----------- Merge pull request #1615 from MarcFontaine/master Add support for the Rhode&Schwarz XK852 transceiver. Compare: https://github.com/Hamlib/Hamlib/compare/73cdd0b214f6...55f83b1647aa To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-21 22:49:07
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 73cdd0b214f6cb7dd2e2199c0c13a9e26bfeb5be https://github.com/Hamlib/Hamlib/commit/73cdd0b214f6cb7dd2e2199c0c13a9e26bfeb5be Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-21 (Sat, 21 Sep 2024) Changed paths: M rotators/gs232a/gs232.c Log Message: ----------- Fix gs232.c for a clean run on AF6SA WRC -- hopefully that firmware will get fixed to provide CR/LF like it should To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-21 20:22:14
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 4b05884fd7ee40c3a0869b89bed3d40fa3661ffa https://github.com/Hamlib/Hamlib/commit/4b05884fd7ee40c3a0869b89bed3d40fa3661ffa Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-21 (Sat, 21 Sep 2024) Changed paths: M rotators/gs232a/gs232.c Log Message: ----------- Fix gs232.c to allow C2 reponse to time out as long as we still get 10 chars it's good This fixes usage tieh AF6SA WRC Wifi Rotator Controller To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael M. <cmo...@gm...> - 2024-09-21 16:33:38
|
Mike, I am trying to use rotctl with one of my computer controlled rotor boxes. It is put out by AF6SA (WRC - Wifi Rotator Controller). It is supposed to be Yaesu GS-232 compatible and works ok with PST Rotator using a network connection with IP/Port. When I try to use it with rotctl I am getting errors. It appears to be connecting and getting a response but rotctl don’t like it. I ran it at command line with trace option on: michaelmorgan@Michaels-Mac-mini ~ % rotctl -vvvvv -m 602 -r 192.168.4.90:23 p rotctl Hamlib 4.6~git 2024-08-23T13:40:16Z SHA=846a56 64-bit Report bugs to <ham...@li...> rot_init called initrots4_gs232a called rot_register (601) rot_register (609) rot_register (610) rot_register (602) rot_register (603) rot_register (611) rot_register (612) rot_register (604) rot_register (605) rot_register (606) rot_register (607) rot_register (608) rot_open called rot_open: using network address 192.168.4.90:23:TCP network_open: TCP connect network_open: hoststr=192.168.4.90, portstr=23 network_open: client port=63937 Opened rot model 602, 'GS-232 Generic' Backend version: 20220109.0, Status: Stable rot_get_position called gs232_rot_get_position called network_flush called write_block(): TX 3 bytes 0000 43 32 0d C2. 0000 2b 30 30 34 33 2b 30 30 34 33 +0043+0043 network_flush called write_block(): TX 3 bytes 0000 43 32 0d C2. 0000 2b 30 30 34 33 2b 30 30 34 33 +0043+0043 network_flush called write_block(): TX 3 bytes 0000 43 32 0d C2. 0000 2b 30 30 34 33 2b 30 30 34 33 +0043+0043 network_flush called write_block(): TX 3 bytes 0000 43 32 0d C2. 0000 2b 30 30 34 33 2b 30 30 34 33 +0043+0043 get_pos: error = read_string_generic(): Timed out 0.452 seconds after 10 chars, direct=1 network_flush called write_block(): TX 3 bytes 0000 43 32 0d C2. read_string_generic called, rxmax=32 direct=1, expected_len=1 0000 2b 30 30 34 33 2b 30 30 34 33 +0043+0043 read_string_generic(): Timed out 0.448 seconds after 10 chars, direct=1 network_flush called write_block(): TX 3 bytes 0000 43 32 0d C2. read_string_generic called, rxmax=32 direct=1, expected_len=1 0000 2b 30 30 34 33 2b 30 30 34 33 +0043+0043 read_string_generic(): Timed out 0.449 seconds after 10 chars, direct=1 network_flush called write_block(): TX 3 bytes 0000 43 32 0d C2. read_string_generic called, rxmax=32 direct=1, expected_len=1 0000 2b 30 30 34 33 2b 30 30 34 33 +0043+0043 read_string_generic(): Timed out 0.452 seconds after 10 chars, direct=1 Communication timed out rot_close called network_close: close socket ret=0 rot_cleanup called michaelmorgan@Michaels-Mac-mini ~ % |
From: Michael B. <no...@gi...> - 2024-09-21 16:12:47
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 1d45224e8a58ada49f449fd378c7b416162cfd27 https://github.com/Hamlib/Hamlib/commit/1d45224e8a58ada49f449fd378c7b416162cfd27 Author: George Baltz N3GB <Geo...@gm...> Date: 2024-09-20 (Fri, 20 Sep 2024) Changed paths: M rigs/kenwood/kenwood.c Log Message: ----------- Fix command lengths for TS-890S set/get_antenna. Still doesn't report RX/TX antenna rerouting. Commit: c37fb872cdd20cf4af355544aed105f0b9f95d54 https://github.com/Hamlib/Hamlib/commit/c37fb872cdd20cf4af355544aed105f0b9f95d54 Author: George Baltz N3GB <Geo...@gm...> Date: 2024-09-20 (Fri, 20 Sep 2024) Changed paths: M simulators/simts890.c Log Message: ----------- Still more tweaks to simts890.c Remove some bogus commands Add meters and antenna control Commit: c4f7cf35f9286acd9eb5405b0b7304452be490a9 https://github.com/Hamlib/Hamlib/commit/c4f7cf35f9286acd9eb5405b0b7304452be490a9 Author: George Baltz N3GB <Geo...@gm...> Date: 2024-09-21 (Sat, 21 Sep 2024) Changed paths: M simulators/simts890.c Log Message: ----------- Replace raw write() calls with macro So they can be aggregated for multiple commands in one message Commit: 88bb2e63c25b931094476cbfa783f47c01a4c193 https://github.com/Hamlib/Hamlib/commit/88bb2e63c25b931094476cbfa783f47c01a4c193 Author: Michael Black <mdb...@ya...> Date: 2024-09-21 (Sat, 21 Sep 2024) Changed paths: M rigs/kenwood/kenwood.c M simulators/simts890.c Log Message: ----------- Merge pull request #1614 from GeoBaltz/fix19 Fix TS-890S set_ant/get_ant Compare: https://github.com/Hamlib/Hamlib/compare/48398dd3d46e...88bb2e63c25b To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-19 15:13:28
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 5fd100f06e56e62e0b4ee73773a615ac5b914ad1 https://github.com/Hamlib/Hamlib/commit/5fd100f06e56e62e0b4ee73773a615ac5b914ad1 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-19 (Thu, 19 Sep 2024) Changed paths: M simulators/simic910.c Log Message: ----------- Fix simic910.c Commit: 48398dd3d46ed071a52a285797060ad62fbeeecb https://github.com/Hamlib/Hamlib/commit/48398dd3d46ed071a52a285797060ad62fbeeecb Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-19 (Thu, 19 Sep 2024) Changed paths: M rigs/kenwood/kenwood.c M rigs/kenwood/kenwood.h M rigs/kenwood/ts480.c Log Message: ----------- Some fixes for QRPLabs rigs Compare: https://github.com/Hamlib/Hamlib/compare/31b625df2bed...48398dd3d46e To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-18 13:01:57
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 31b625df2bed7080ea2faecce0a309f9b176a6b6 https://github.com/Hamlib/Hamlib/commit/31b625df2bed7080ea2faecce0a309f9b176a6b6 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-18 (Wed, 18 Sep 2024) Changed paths: M include/hamlib/rig.h Log Message: ----------- Fix winsock2 warning To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-16 04:59:47
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 9236b778ae05b9642b12000c8412c88e0855c9a8 https://github.com/Hamlib/Hamlib/commit/9236b778ae05b9642b12000c8412c88e0855c9a8 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-15 (Sun, 15 Sep 2024) Changed paths: M rigs/yaesu/ft891.c Log Message: ----------- Allow split off with ft891 Commit: 76a1a589c900fe1d7b7e0b3ba7dc3ea6a9c70925 https://github.com/Hamlib/Hamlib/commit/76a1a589c900fe1d7b7e0b3ba7dc3ea6a9c70925 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-15 (Sun, 15 Sep 2024) Changed paths: M rigs/icom/icom.c Log Message: ----------- Fix icom_power2mW to use the rig's max_power for the band/mode Commit: 2a47377243cb89ef7607b162b83d3534772f3ca7 https://github.com/Hamlib/Hamlib/commit/2a47377243cb89ef7607b162b83d3534772f3ca7 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-15 (Sun, 15 Sep 2024) Changed paths: M doc/man1/rigctl.1 M rigs/kenwood/kenwood.c M simulators/simts890.c Log Message: ----------- Merge branch 'master' of https://github.com/Hamlib/Hamlib Compare: https://github.com/Hamlib/Hamlib/compare/76c3cd15bb72...2a47377243cb To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-15 20:38:49
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 8a6a500ccdfbc63b98b31b0ebb6d854bcbe0097f https://github.com/Hamlib/Hamlib/commit/8a6a500ccdfbc63b98b31b0ebb6d854bcbe0097f Author: George Baltz N3GB <Geo...@gm...> Date: 2024-09-14 (Sat, 14 Sep 2024) Changed paths: M simulators/simts890.c Log Message: ----------- Tweaks to simts890.c Don't include trailing null byte in responses Zero fill response data Filter a few commands - not complete coverage yet Still no simulated clock. Commit: 496d8fde316c24572576b58bce9fc5bed52fd418 https://github.com/Hamlib/Hamlib/commit/496d8fde316c24572576b58bce9fc5bed52fd418 Author: George Baltz N3GB <Geo...@gm...> Date: 2024-09-15 (Sun, 15 Sep 2024) Changed paths: M rigs/kenwood/kenwood.c Log Message: ----------- Fix negative fractional UTC offsets Bizarro utc_offset encoding does not play well with arithmetic. Commit: d81726e72452aa6d8150ad6f0468d86070440e51 https://github.com/Hamlib/Hamlib/commit/d81726e72452aa6d8150ad6f0468d86070440e51 Author: George Baltz N3GB <Geo...@gm...> Date: 2024-09-15 (Sun, 15 Sep 2024) Changed paths: M doc/man1/rigctl.1 M rigs/kenwood/kenwood.c Log Message: ----------- Implement kenwood_set_clock Add warning to man page about NTP use and aux clock display. Commit: 76c3cd15bb72d6f2b83758b558e5368875baf125 https://github.com/Hamlib/Hamlib/commit/76c3cd15bb72d6f2b83758b558e5368875baf125 Author: Michael Black <mdb...@ya...> Date: 2024-09-15 (Sun, 15 Sep 2024) Changed paths: M doc/man1/rigctl.1 M rigs/kenwood/kenwood.c M simulators/simts890.c Log Message: ----------- Merge pull request #1612 from GeoBaltz/fix18 Add kenwood_set_clock Compare: https://github.com/Hamlib/Hamlib/compare/fc849732c0c1...76c3cd15bb72 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Black M. <mdb...@ya...> - 2024-09-14 19:57:43
|
Maybe we can define two constants #define RIG_CLOCK_UTC -1 #define RIG_CLOCK_LOCAL -2 Then in set_clock if you pass in those for the utc_offset you get utc or local time set respectively. Either that or we make another set_clock call. Thoughts? Once that's done I can probably get Uwe to add that to WSJT-X and make UTC the default to be overriden in hamlib_settings.json for LOCAL time. Mike W9MDB On Saturday, September 14, 2024 at 01:49:34 PM CDT, George Baltz <geo...@gm...> wrote: On 9/10/24 5:27 PM, Black Michael wrote: > You can look at ic7300.c for ic7300_set_clock. > I didn't bother to try and figure out too much and just set based on whatever gets passed in but only gets set if hour >= 0. > Command will likely fail if bogus data is sent. Thanks for the pointer. I had looked through icom.c and newcat.c and found nothing. Should've done a full grep. I wish I had the flexibility to set either time or date but that's one big command; at least the offset is separate. What I will probably do is to set the offset first, then the time&date. That way if the time is locked onto NTP, I can bail and the TZ will still be set to what the app wanted. It still bothers me to give a RIG_OK when something couldn't be accomplished, but I don't see any way to report partial success. > > In rigctl I allow this: > > set_clock 'DateTime' > Set 'DateTime' > > > Sets rig clock -- note that some rigs do not handle seconds or milliseconds. If you try to set sec/msec and rig does > not support it you will get a debug warning message. Format is ISO8601, > Formats accepted allow for 2-digit or 4-digit time zone > YYYY-MM-DDTHH:MM:SS.SSS+ZZ (where +ZZ is either -/+ UTC offset HH) > YYYY-MM-DDTHH:MM:SS.SSS+ZZZZ (where +ZZZZ is either -/+ UTC offset HHMM) > YYYY-MM-DDTHH:MM:SS+ZZ > YYYY-MM-DDTHH:MM:SS+ZZZZ > YYYY-MM-DDTHH:MM+ZZ > YYYY-MM-DDTHH:MM+ZZZZ > YYYY-MM-DD (sets date only) > local (sets both clocks to local time) > utc (sets both clocks to utc time) > Note: Icom rigs expect you to set local time and the hours off to UTC. > So...4PM EST example would be 2021-12-01T16:00:00+0500 > But...if you want to display GMT you must set the clock for GMT with zero UTC offset. > Hopefully Icom will allow displaying either clock in the future EST is -0500. Will fix when I add the Kenwood notes. > > > > > > > > > > > On Tuesday, September 10, 2024 at 03:41:30 PM CDT, George Baltz <geo...@gm...> wrote: > > > > > > I have been working on implementing rig_{get|set}_clock for the Kenwood > TS-890S/990S and need some advice on handling a quirk in the way the > clock interacts with other functions. > > The rigs each have two clocks, called the local clock and auxiliary > clock (or secondary.) Common practice is to set the local clock to > local time and the aux to UTC. Only the local clock is directly > settable; it looks like the rig subtracts the local TZ offset to find > UTC, then uses the aux offset (in this case zero) to set the aux. Both > offsets are settable. > > The two rigs are network-capable, and when connected they have the > option to sync the base clock(UTC) via NTP. When this is enabled the > clock setting function is disabled, both by CAT and the menu system; > only the offsets can be changed. > > The problem I have is what to do with the single rig_set_clock() call. > I can't set the clock, but I'd like to set the offset (at least twice a > year). Do I just fail the whole thing? Do I ignore the clock if all of > YMDhms = 0? Set the offset first and bail if clock setting is > disabled? And what kind of result/status do I report? Any way to say > this worked, but that didn't? > > Any suggestions or wisdom welcomed, or any guidelines buried in the > history of Hamlib. > > > 73 > > n3gb > > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
From: George B. <geo...@gm...> - 2024-09-14 18:49:44
|
On 9/10/24 5:27 PM, Black Michael wrote: > You can look at ic7300.c for ic7300_set_clock. > I didn't bother to try and figure out too much and just set based on whatever gets passed in but only gets set if hour >= 0. > Command will likely fail if bogus data is sent. Thanks for the pointer. I had looked through icom.c and newcat.c and found nothing. Should've done a full grep. I wish I had the flexibility to set either time or date but that's one big command; at least the offset is separate. What I will probably do is to set the offset first, then the time&date. That way if the time is locked onto NTP, I can bail and the TZ will still be set to what the app wanted. It still bothers me to give a RIG_OK when something couldn't be accomplished, but I don't see any way to report partial success. > > In rigctl I allow this: > > set_clock 'DateTime' > Set 'DateTime' > > > Sets rig clock -- note that some rigs do not handle seconds or milliseconds. If you try to set sec/msec and rig does > not support it you will get a debug warning message. Format is ISO8601, > Formats accepted allow for 2-digit or 4-digit time zone > YYYY-MM-DDTHH:MM:SS.SSS+ZZ (where +ZZ is either -/+ UTC offset HH) > YYYY-MM-DDTHH:MM:SS.SSS+ZZZZ (where +ZZZZ is either -/+ UTC offset HHMM) > YYYY-MM-DDTHH:MM:SS+ZZ > YYYY-MM-DDTHH:MM:SS+ZZZZ > YYYY-MM-DDTHH:MM+ZZ > YYYY-MM-DDTHH:MM+ZZZZ > YYYY-MM-DD (sets date only) > local (sets both clocks to local time) > utc (sets both clocks to utc time) > Note: Icom rigs expect you to set local time and the hours off to UTC. > So...4PM EST example would be 2021-12-01T16:00:00+0500 > But...if you want to display GMT you must set the clock for GMT with zero UTC offset. > Hopefully Icom will allow displaying either clock in the future EST is -0500. Will fix when I add the Kenwood notes. > > > > > > > > > > > On Tuesday, September 10, 2024 at 03:41:30 PM CDT, George Baltz <geo...@gm...> wrote: > > > > > > I have been working on implementing rig_{get|set}_clock for the Kenwood > TS-890S/990S and need some advice on handling a quirk in the way the > clock interacts with other functions. > > The rigs each have two clocks, called the local clock and auxiliary > clock (or secondary.) Common practice is to set the local clock to > local time and the aux to UTC. Only the local clock is directly > settable; it looks like the rig subtracts the local TZ offset to find > UTC, then uses the aux offset (in this case zero) to set the aux. Both > offsets are settable. > > The two rigs are network-capable, and when connected they have the > option to sync the base clock(UTC) via NTP. When this is enabled the > clock setting function is disabled, both by CAT and the menu system; > only the offsets can be changed. > > The problem I have is what to do with the single rig_set_clock() call. > I can't set the clock, but I'd like to set the offset (at least twice a > year). Do I just fail the whole thing? Do I ignore the clock if all of > YMDhms = 0? Set the offset first and bail if clock setting is > disabled? And what kind of result/status do I report? Any way to say > this worked, but that didn't? > > Any suggestions or wisdom welcomed, or any guidelines buried in the > history of Hamlib. > > > 73 > > n3gb > > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
From: Michael B. <no...@gi...> - 2024-09-13 16:34:08
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: fc849732c0c1dfdbccc0d7666f46952eeee4c731 https://github.com/Hamlib/Hamlib/commit/fc849732c0c1dfdbccc0d7666f46952eeee4c731 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-13 (Fri, 13 Sep 2024) Changed paths: M src/rig.c Log Message: ----------- Clean up some debug warnings To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Black M. <mdb...@ya...> - 2024-09-13 15:03:43
|
The real problem it addresses is reviewing the Mac build for real warnings and errors. All the bogus ones get in the way of viewing the output. That's why we clear up all warnings on all platforms. On Friday, September 13, 2024 at 09:43:06 AM CDT, George Baltz <geo...@gm...> wrote: On 9/10/24 11:13 PM, Black Michael wrote: > Sorry you think it's a waste of time to clear up compiler warnings. I disagree. > I have no problem clearing up compiler warnings if - They address real problems - They make my life simpler, as programmer or maintainer - They reduce the probability of future problems These changes don't seem to help any of those. 1) The warning is bogus. Setting a baseline or default for any value and then overriding that in specific or localized instances is a pretty fundamental way we build, configure or execute programs. Do you get a warning for adding a CLI option to override a program default? Or when a .rc file changes a default to what >you< want? Do you have to rebuild a program, removing the default before adding your own choice? I don't think so. Stigmatizing that hierarchy of settings doesn't seem like a good idea to me. 2) So far it's taken about 400 lines of code(LoC). That's 400 more to maintain. And it changes simple one-liners into changes in multiple places, possibly multiple files. Simplify, simplify. 3) It makes the code much more fragile; instead of making a data change in one place, you need to sync three. And there's no default to fall back on, just by removing the override. Again, multiple actions instead of one. Sorry, but this doesn't look like progress to me. YMMV. 73 n3gb |
From: George B. <geo...@gm...> - 2024-09-13 14:43:12
|
On 9/10/24 11:13 PM, Black Michael wrote: > Sorry you think it's a waste of time to clear up compiler warnings. I disagree. > I have no problem clearing up compiler warnings if - They address real problems - They make my life simpler, as programmer or maintainer - They reduce the probability of future problems These changes don't seem to help any of those. 1) The warning is bogus. Setting a baseline or default for any value and then overriding that in specific or localized instances is a pretty fundamental way we build, configure or execute programs. Do you get a warning for adding a CLI option to override a program default? Or when a .rc file changes a default to what >you< want? Do you have to rebuild a program, removing the default before adding your own choice? I don't think so. Stigmatizing that hierarchy of settings doesn't seem like a good idea to me. 2) So far it's taken about 400 lines of code(LoC). That's 400 more to maintain. And it changes simple one-liners into changes in multiple places, possibly multiple files. Simplify, simplify. 3) It makes the code much more fragile; instead of making a data change in one place, you need to sync three. And there's no default to fall back on, just by removing the override. Again, multiple actions instead of one. Sorry, but this doesn't look like progress to me. YMMV. 73 n3gb |
From: Michael B. <no...@gi...> - 2024-09-13 12:24:06
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 711089f25269e26e23bbe139d8f53fd4c45c6ca5 https://github.com/Hamlib/Hamlib/commit/711089f25269e26e23bbe139d8f53fd4c45c6ca5 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-13 (Fri, 13 Sep 2024) Changed paths: M src/conf.c M src/multicast.c Log Message: ----------- Turn off multicast by default -- need to set multicast_data_addr to 224.0.0.1 or such to enable Also disable multicast_cmd_addr by default Commit: 99d008a664fa2381d12e47741a645350800a1418 https://github.com/Hamlib/Hamlib/commit/99d008a664fa2381d12e47741a645350800a1418 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-13 (Fri, 13 Sep 2024) Changed paths: M rigs/tentec/jupiter.c Log Message: ----------- Allow jupiter to do retries -- and also check freq after setting it https://github.com/Hamlib/Hamlib/issues/1607 Compare: https://github.com/Hamlib/Hamlib/compare/2b3000c21de9...99d008a664fa To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-12 22:53:42
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 2b3000c21de924a5d9ad78586b3d2959a54c07ee https://github.com/Hamlib/Hamlib/commit/2b3000c21de924a5d9ad78586b3d2959a54c07ee Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-12 (Thu, 12 Sep 2024) Changed paths: M include/hamlib/rig.h Log Message: ----------- Suppress warnings when include winsock2 that windows.h must be included first To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-12 14:08:02
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: c58d46cfbec8982169f3b007f61f23a8b27cc4eb https://github.com/Hamlib/Hamlib/commit/c58d46cfbec8982169f3b007f61f23a8b27cc4eb Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-12 (Thu, 12 Sep 2024) Changed paths: M rigs/kenwood/ts570.c Log Message: ----------- Fix the other TS570 model too To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Michael B. <no...@gi...> - 2024-09-12 13:59:21
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: e09dd84bc25a1650b32ff1bc7fed26a4d50135f7 https://github.com/Hamlib/Hamlib/commit/e09dd84bc25a1650b32ff1bc7fed26a4d50135f7 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-12 (Thu, 12 Sep 2024) Changed paths: M src/register.c Log Message: ----------- Fix compile warning Commit: 0eca80281fe8ebf9c2bb9c57608e15fd4bff4ebc https://github.com/Hamlib/Hamlib/commit/0eca80281fe8ebf9c2bb9c57608e15fd4bff4ebc Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-12 (Thu, 12 Sep 2024) Changed paths: M rigs/kenwood/ts570.c Log Message: ----------- Fix TS570 to use hardware flow control -- been wrong for 23 years Compare: https://github.com/Hamlib/Hamlib/compare/b9b4d44f4f95...0eca80281fe8 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
From: Black M. <mdb...@ya...> - 2024-09-12 11:28:28
|
The error code doesn't tell you any more than what you have now. Could be some extra time is needed for remote operation. The default timeout is 1000ms. So...save this in hamlib_settings.json in the same location as WSJT-X.ini and let's bump up the timeout to 3000ms. { "config": { "timeout": "3000"\ } } Mike W9MDB On Thursday, September 12, 2024 at 03:36:50 AM CDT, David Owen <djm...@gm...> wrote: Hi Using WSJT-X 2.7.0 rc5 with Hamlib 4.6 "git 2024-06-23T11:53:09Z". I have been trying a remotely controlled Icom IC-R8600 using the Icom Remote Utility with WSJT-X 2.7.0 rc5 Most of the time it works but occasionally there is a Hamlib Protocol Error type "-8" when reading the VFO frequency (see attached screenshot). What does a Hamlib error "-8" actually mean? Is there some way to find out more about what has gone wrong? "Protocol Error" by itself could mean lots of things such as an "FA" CIV reply or a reply to a different command or no reply at all. Direct control (usb connection) of the IC-R8600 from WSJT-X always works without any errors. Regards David Owen GM1OXB _______________________________________________ Hamlib-developer mailing list Ham...@li... https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
From: Michael B. <no...@gi...> - 2024-09-11 15:22:45
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: b9b4d44f4f9539626119c5c34c9e13b156d2e290 https://github.com/Hamlib/Hamlib/commit/b9b4d44f4f9539626119c5c34c9e13b156d2e290 Author: Mike Black W9MDB <mdb...@ya...> Date: 2024-09-11 (Wed, 11 Sep 2024) Changed paths: M rigs/yaesu/ft3000.c Log Message: ----------- Fix ft3000.c To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |