hamlib-developer Mailing List for Ham Radio Control Libraries (Page 26)
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
(83) |
Sep
(84) |
Oct
(20) |
Nov
(46) |
Dec
|
|
From: Daniele F. <iu...@gm...> - 2025-03-17 20:59:11
|
George Baltz > This has changed some of the references to 'rigctld' to 'rigctl' in the > rigctld.1 man page. Is that what was wanted? no, that was by mistake repeated with copy and paste! thanks for reporting it, -- 73 de IU5HKX Daniele |
|
From: George B. <geo...@gm...> - 2025-03-17 09:59:24
|
This has changed some of the references to 'rigctld' to 'rigctl' in the rigctld.1 man page. Is that what was wanted? On 3/16/25 6:11 PM, Michael Black via Hamlib-developer wrote: > Branch: refs/heads/master > Home: https://github.com/Hamlib/Hamlib > Commit: e109fe355d0fb4f1da9fc0dcb3dc5a304f08a771 > https://github.com/Hamlib/Hamlib/commit/e109fe355d0fb4f1da9fc0dcb3dc5a304f08a771 > Author: Daniele Forsi IU5HKX <iu...@gm...> > Date: 2025-03-16 (Sun, 16 Mar 2025) > > Changed paths: > M doc/man1/rigctl.1 > M doc/man1/rigctld.1 > > Log Message: > ----------- > Fix typos > > > Commit: cb0196875b1580cdef6cd8748eed8f84b305a173 > https://github.com/Hamlib/Hamlib/commit/cb0196875b1580cdef6cd8748eed8f84b305a173 > Author: Daniele Forsi IU5HKX <iu...@gm...> > Date: 2025-03-16 (Sun, 16 Mar 2025) > > Changed paths: > M doc/man1/rigctl.1 > M doc/man1/rigctld.1 > > Log Message: > ----------- > Fix underline and italics > > > Commit: 2da07e484c5162a8ed8e3be2395452c2b21a0bcb > https://github.com/Hamlib/Hamlib/commit/2da07e484c5162a8ed8e3be2395452c2b21a0bcb > Author: Daniele Forsi IU5HKX <iu...@gm...> > Date: 2025-03-16 (Sun, 16 Mar 2025) > > Changed paths: > M doc/man1/rigctld.1 > > Log Message: > ----------- > Escape literal \n > > Otherwise it isn't rendered correctly. > > > Commit: cd72187a7cc99c0168f6150de7cb21dbed7801d5 > https://github.com/Hamlib/Hamlib/commit/cd72187a7cc99c0168f6150de7cb21dbed7801d5 > Author: Daniele Forsi IU5HKX <iu...@gm...> > Date: 2025-03-16 (Sun, 16 Mar 2025) > > Changed paths: > M doc/man1/rigctl.1 > M doc/man1/rigctld.1 > > Log Message: > ----------- > Fix usage of .EX > > Add missing .EE and remove some .EE that were out of place. > > > Commit: 0e1e794cfa569c8994ab98a75d133a1fb6b3fbb3 > https://github.com/Hamlib/Hamlib/commit/0e1e794cfa569c8994ab98a75d133a1fb6b3fbb3 > Author: Daniele Forsi IU5HKX <iu...@gm...> > Date: 2025-03-16 (Sun, 16 Mar 2025) > > Changed paths: > M doc/man1/rigctl.1 > M doc/man1/rigctld.1 > > Log Message: > ----------- > Set parameter keywords bold, not their descriptions > > > Commit: d9545845b01b830f4aa5470e842e754ca023484a > https://github.com/Hamlib/Hamlib/commit/d9545845b01b830f4aa5470e842e754ca023484a > Author: Daniele Forsi IU5HKX <iu...@gm...> > Date: 2025-03-16 (Sun, 16 Mar 2025) > > Changed paths: > M doc/man1/rigctld.1 > > Log Message: > ----------- > Add bold > > > Commit: c6a30081cbc3752ef1c904512ff4bbf8b2fe9e03 > https://github.com/Hamlib/Hamlib/commit/c6a30081cbc3752ef1c904512ff4bbf8b2fe9e03 > Author: Michael Black <mdb...@ya...> > Date: 2025-03-16 (Sun, 16 Mar 2025) > > Changed paths: > M doc/man1/rigctl.1 > M doc/man1/rigctld.1 > > Log Message: > ----------- > Merge pull request #1682 from dforsi/fix/manpages > > Fix manpages > > > Compare: https://github.com/Hamlib/Hamlib/compare/0f519185acd7...c6a30081cbc3 > > To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
|
From: Michael B. <no...@gi...> - 2025-03-16 22:11:23
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: e109fe355d0fb4f1da9fc0dcb3dc5a304f08a771 https://github.com/Hamlib/Hamlib/commit/e109fe355d0fb4f1da9fc0dcb3dc5a304f08a771 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-03-16 (Sun, 16 Mar 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Fix typos Commit: cb0196875b1580cdef6cd8748eed8f84b305a173 https://github.com/Hamlib/Hamlib/commit/cb0196875b1580cdef6cd8748eed8f84b305a173 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-03-16 (Sun, 16 Mar 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Fix underline and italics Commit: 2da07e484c5162a8ed8e3be2395452c2b21a0bcb https://github.com/Hamlib/Hamlib/commit/2da07e484c5162a8ed8e3be2395452c2b21a0bcb Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-03-16 (Sun, 16 Mar 2025) Changed paths: M doc/man1/rigctld.1 Log Message: ----------- Escape literal \n Otherwise it isn't rendered correctly. Commit: cd72187a7cc99c0168f6150de7cb21dbed7801d5 https://github.com/Hamlib/Hamlib/commit/cd72187a7cc99c0168f6150de7cb21dbed7801d5 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-03-16 (Sun, 16 Mar 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Fix usage of .EX Add missing .EE and remove some .EE that were out of place. Commit: 0e1e794cfa569c8994ab98a75d133a1fb6b3fbb3 https://github.com/Hamlib/Hamlib/commit/0e1e794cfa569c8994ab98a75d133a1fb6b3fbb3 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-03-16 (Sun, 16 Mar 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Set parameter keywords bold, not their descriptions Commit: d9545845b01b830f4aa5470e842e754ca023484a https://github.com/Hamlib/Hamlib/commit/d9545845b01b830f4aa5470e842e754ca023484a Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-03-16 (Sun, 16 Mar 2025) Changed paths: M doc/man1/rigctld.1 Log Message: ----------- Add bold Commit: c6a30081cbc3752ef1c904512ff4bbf8b2fe9e03 https://github.com/Hamlib/Hamlib/commit/c6a30081cbc3752ef1c904512ff4bbf8b2fe9e03 Author: Michael Black <mdb...@ya...> Date: 2025-03-16 (Sun, 16 Mar 2025) Changed paths: M doc/man1/rigctl.1 M doc/man1/rigctld.1 Log Message: ----------- Merge pull request #1682 from dforsi/fix/manpages Fix manpages Compare: https://github.com/Hamlib/Hamlib/compare/0f519185acd7...c6a30081cbc3 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Ben Z en de r. <hoo...@gm...> - 2025-03-13 09:29:35
|
I solved this by upgrading hablib to version 4.5.4 on the Satnogs Pi libhamlib, libhamlib-dev and libhamlib0utils, after which also python3-hamlib needed to be updated. Now all works great ! Op do 6 mrt 2025 om 09:27 schreef Ben Z en de rest <hoo...@gm... >: > Hi, > I am updating some Arduino rotor control software with feedback of AZ and > EL values when called (GS232 protocol, sending on C2 command sent by > rotctld Pi to Arduino. > > So far, so good. Running rotctld on the rotor controlling Pi , and > Gpredict on the remote PC it nicely tracks the satellites and shows the > reported values of AZ and EL in the Gpredict window. > > Time to check the same controlling the remote Pi from my Satnogs Pi, which > is going to control the AZ ./ EL motor. > > I run : > rotctl -m 2 -r 192.168.0.186:4533 -vvvvvvvvvv > > > I get in return, as values: > > 0000 5c 64 75 6d 70 5f 73 74 61 74 65 0a \dump_state. > read_string called, rxmax=64 > read_string(): RX 2 characters > 0000 31 0a 1. > read_string called, rxmax=64 > read_string(): RX 4 characters > 0000 36 30 32 0a 602. > read_string called, rxmax=64 > read_string(): RX 19 characters > 0000 6d 69 6e 5f 61 7a 3d 2d 31 38 30 2e 30 30 30 30 > min_az=-180.0000 > 0010 30 30 0a 00. > read_string called, rxmax=64 > read_string(): RX 18 characters > 0000 6d 61 78 5f 61 7a 3d 34 35 30 2e 30 30 30 30 30 > max_az=450.00000 > 0010 30 0a 0. > read_string called, rxmax=64 > read_string(): RX 16 characters > 0000 6d 69 6e 5f 65 6c 3d 30 2e 30 30 30 30 30 30 0a > min_el=0.000000. > read_string called, rxmax=64 > read_string(): RX 18 characters > 0000 6d 61 78 5f 65 6c 3d 31 38 30 2e 30 30 30 30 30 > max_el=180.00000 > 0010 30 0a 0. > Opened rot model 2, 'NET rotctl' > Backend version: 20200528.0, Status: Stable > > > So, at rotator command prompt I enter p (to get position) which results in > > rot_get_position: got az=135.00, el=29.00 > Azimuth: 135.00 > Elevation: 29.00 > > So, now trying to send the AZ EL to 50 50 with P 50 50 which results in > > rotctl_parse: input_line: P 50 50 > rot_set_position called az=50.00 el=50.00 > rot_set_position: south_zero=0 > rot_set_position: range problem az=50.00(min=0.00,max=0.00), > el=50.000000(min=0.00,max=0.000000) > set_pos: error = Invalid parameter > > > So, the first report when starting tells me I can set AZ and EL within > certain ranges, but when setting it says de min and max values are zero ? > > Terminating the rotctl connection on that pi, and sending: > > pi@raspberrypi:~ $ echo "\set_pos 50.0 50.0" | nc -w 1 192.168.0.186 4533 > > starts setting the AZ and EL of the motor to the requested problems. > > What am I possibly overlooking ? > > Thanks, > Ben > > > > > > |
|
From: Michael B. <no...@gi...> - 2025-03-13 04:10:53
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 5caa22b79a5532b2848a8e6689e0be2b36a94fde https://github.com/Hamlib/Hamlib/commit/5caa22b79a5532b2848a8e6689e0be2b36a94fde Author: George Baltz N3GB <Geo...@gm...> Date: 2025-03-04 (Tue, 04 Mar 2025) Changed paths: M src/rig.c Log Message: ----------- Add locking to rig_stop_morse and rig_wait_morse Commit: 9b2904c0b676dc4ed57bd09e300b6a1e81b930c8 https://github.com/Hamlib/Hamlib/commit/9b2904c0b676dc4ed57bd09e300b6a1e81b930c8 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-03-04 (Tue, 04 Mar 2025) Changed paths: M rigs/kenwood/kenwood.c Log Message: ----------- Fix timeout in kenwood_stop_morse Add "KY0" to exceptions. Commit: a3e23e79cd97b4c48ea56cc2776b68d86db61a08 https://github.com/Hamlib/Hamlib/commit/a3e23e79cd97b4c48ea56cc2776b68d86db61a08 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-03-04 (Tue, 04 Mar 2025) Changed paths: M src/rig.c Log Message: ----------- Minor cleanups/fixes Return status from rig_send_morse Remove duplicate include and some dead code Avoid future NULL dereference in error cases Commit: 0f519185acd7861412cb320e423145984ba05ab9 https://github.com/Hamlib/Hamlib/commit/0f519185acd7861412cb320e423145984ba05ab9 Author: Michael Black <mdb...@ya...> Date: 2025-03-12 (Wed, 12 Mar 2025) Changed paths: M rigs/kenwood/kenwood.c M src/rig.c Log Message: ----------- Merge pull request #1676 from GeoBaltz/fix26a More fixes for send_morse sync Compare: https://github.com/Hamlib/Hamlib/compare/1049dc2457f2...0f519185acd7 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Michael B. <no...@gi...> - 2025-03-12 17:50:27
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: f8740ddd2899388f86bc3098afc0ae9d05f297a7 https://github.com/Hamlib/Hamlib/commit/f8740ddd2899388f86bc3098afc0ae9d05f297a7 Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-03-12 (Wed, 12 Mar 2025) Changed paths: M rigs/yaesu/ftdx101.c M rigs/yaesu/ftdx101.h Log Message: ----------- Fix FTDX101D/MP ALC scale Commit: 1049dc2457f2c90d47012da376836803b7c19dea https://github.com/Hamlib/Hamlib/commit/1049dc2457f2c90d47012da376836803b7c19dea Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-03-12 (Wed, 12 Mar 2025) Changed paths: M rotators/skywatcher/skywatcher.h Log Message: ----------- Merge branch 'master' of github.com:Hamlib/Hamlib Compare: https://github.com/Hamlib/Hamlib/compare/ed52875c3d69...1049dc2457f2 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Michael B. <no...@gi...> - 2025-03-10 14:25:31
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: c2d3202ffb0f4c51431b982ca023a586fcdbafc0 https://github.com/Hamlib/Hamlib/commit/c2d3202ffb0f4c51431b982ca023a586fcdbafc0 Author: gereta <355...@us...> Date: 2025-03-10 (Mon, 10 Mar 2025) Changed paths: M rotators/skywatcher/skywatcher.h Log Message: ----------- Update skywatcher.h - Added coordinates for parking position Added coordinates for parking position Commit: ed52875c3d6988917b84cae6f96f2440063453e3 https://github.com/Hamlib/Hamlib/commit/ed52875c3d6988917b84cae6f96f2440063453e3 Author: Michael Black <mdb...@ya...> Date: 2025-03-10 (Mon, 10 Mar 2025) Changed paths: M rotators/skywatcher/skywatcher.h Log Message: ----------- Merge pull request #1679 from gereta/patch-3 Update skywatcher.h - Added coordinates for parking position Compare: https://github.com/Hamlib/Hamlib/compare/43f8afa6a4f1...ed52875c3d69 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Michael B. <no...@gi...> - 2025-03-10 14:24:54
|
Branch: refs/heads/Hamlib-4.6.2 Home: https://github.com/Hamlib/Hamlib Commit: 845a3ac1d1b75e0b9ea7c4dea8770a1bc54f2497 https://github.com/Hamlib/Hamlib/commit/845a3ac1d1b75e0b9ea7c4dea8770a1bc54f2497 Author: gereta <355...@us...> Date: 2025-03-10 (Mon, 10 Mar 2025) Changed paths: M rotators/skywatcher/skywatcher.c Log Message: ----------- Update skywatcher.c - park rotator, improved rotator movement Added function to park the rotator. Changed behavior for incoming requests to change position. If the motor is moving, the requests are silently ignored. Stopping the motor movement before each request to change position caused the movement from point A to point B to take a very long time because tracking applications send the dynamic position of the tracked object (e.g. satellite) in regular short intervals and in case the rotator was on the opposite side, by the time the rotator reached the position of the object, the object had traveled a considerable distance. Commit: c5d4baef5366481fca28e7887de06f8396714f46 https://github.com/Hamlib/Hamlib/commit/c5d4baef5366481fca28e7887de06f8396714f46 Author: Michael Black <mdb...@ya...> Date: 2025-03-10 (Mon, 10 Mar 2025) Changed paths: M rotators/skywatcher/skywatcher.c Log Message: ----------- Merge pull request #1680 from gereta/patch-2 Update skywatcher.c - park rotator, improved rotator movement Compare: https://github.com/Hamlib/Hamlib/compare/73a2f2fa4617...c5d4baef5366 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Michael B. <no...@gi...> - 2025-03-08 15:51:38
|
Branch: refs/heads/Hamlib-4.6.2 Home: https://github.com/Hamlib/Hamlib Commit: f54e52342d3f785ffc09c159adaa2626fcca624b https://github.com/Hamlib/Hamlib/commit/f54e52342d3f785ffc09c159adaa2626fcca624b Author: gereta <355...@us...> Date: 2025-03-08 (Sat, 08 Mar 2025) Changed paths: M rotators/skywatcher/skywatcher.c Log Message: ----------- Update skywatcher.c Probably by mistake the call to read data from the serial port was left twice. Therefore, controlling Skywatcher mounts does not work and ends with a timeout. Otherwise, excellent work - since all Skywatcher mounts use the same motor controller firmware, it is possible to control not only Allview but all mounts from this manufacturer. Commit: 73a2f2fa4617a9c887fc7e2344fe4fbd6be78c86 https://github.com/Hamlib/Hamlib/commit/73a2f2fa4617a9c887fc7e2344fe4fbd6be78c86 Author: Michael Black <mdb...@ya...> Date: 2025-03-08 (Sat, 08 Mar 2025) Changed paths: M rotators/skywatcher/skywatcher.c Log Message: ----------- Merge pull request #1677 from gereta/patch-1 Update skywatcher.c Compare: https://github.com/Hamlib/Hamlib/compare/8703647c8cb2...73a2f2fa4617 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Ben Z en de r. <hoo...@gm...> - 2025-03-06 08:27:45
|
Hi, I am updating some Arduino rotor control software with feedback of AZ and EL values when called (GS232 protocol, sending on C2 command sent by rotctld Pi to Arduino. So far, so good. Running rotctld on the rotor controlling Pi , and Gpredict on the remote PC it nicely tracks the satellites and shows the reported values of AZ and EL in the Gpredict window. Time to check the same controlling the remote Pi from my Satnogs Pi, which is going to control the AZ ./ EL motor. I run : rotctl -m 2 -r 192.168.0.186:4533 -vvvvvvvvvv I get in return, as values: 0000 5c 64 75 6d 70 5f 73 74 61 74 65 0a \dump_state. read_string called, rxmax=64 read_string(): RX 2 characters 0000 31 0a 1. read_string called, rxmax=64 read_string(): RX 4 characters 0000 36 30 32 0a 602. read_string called, rxmax=64 read_string(): RX 19 characters 0000 6d 69 6e 5f 61 7a 3d 2d 31 38 30 2e 30 30 30 30 min_az=-180.0000 0010 30 30 0a 00. read_string called, rxmax=64 read_string(): RX 18 characters 0000 6d 61 78 5f 61 7a 3d 34 35 30 2e 30 30 30 30 30 max_az=450.00000 0010 30 0a 0. read_string called, rxmax=64 read_string(): RX 16 characters 0000 6d 69 6e 5f 65 6c 3d 30 2e 30 30 30 30 30 30 0a min_el=0.000000. read_string called, rxmax=64 read_string(): RX 18 characters 0000 6d 61 78 5f 65 6c 3d 31 38 30 2e 30 30 30 30 30 max_el=180.00000 0010 30 0a 0. Opened rot model 2, 'NET rotctl' Backend version: 20200528.0, Status: Stable So, at rotator command prompt I enter p (to get position) which results in rot_get_position: got az=135.00, el=29.00 Azimuth: 135.00 Elevation: 29.00 So, now trying to send the AZ EL to 50 50 with P 50 50 which results in rotctl_parse: input_line: P 50 50 rot_set_position called az=50.00 el=50.00 rot_set_position: south_zero=0 rot_set_position: range problem az=50.00(min=0.00,max=0.00), el=50.000000(min=0.00,max=0.000000) set_pos: error = Invalid parameter So, the first report when starting tells me I can set AZ and EL within certain ranges, but when setting it says de min and max values are zero ? Terminating the rotctl connection on that pi, and sending: pi@raspberrypi:~ $ echo "\set_pos 50.0 50.0" | nc -w 1 192.168.0.186 4533 starts setting the AZ and EL of the motor to the requested problems. What am I possibly overlooking ? Thanks, Ben |
|
From: <geo...@gm...> - 2025-03-05 21:13:19
|
On Wednesday, March 5, 2025 2:51:36 PM Eastern Standard Time Stephen Gabelich wrote: > I’m having trouble getting rigctld to work > > I’m running DragonOS and I currently have hamlib version 4.7 installed and > my rig is a TX-500 > > rigctl -m 2050 -r /dev/ttyUSB0 <all commands> work > rigctld -m 2050 -r /dev/ttyUSB0 nothing works; it hangs, i.e., does not That's what it is supposed to do. To use rigctld, start it as a background task, like: rigctld -m 2050 -r /dev/ttyUSB0 & Then, in your application(s), use "hamlib dummy" (model 2) and "localhost" to connect to rigctld Maybe even easier - some of the logging apps will start rigctld for you. I start it from cqrlog, and then other apps (wsjt, etc) can use the same rigctld. > return to the command prompt > > sudo systemctl restart rigctld gave me this error (: Unit rigctld.service > not found) > > I created the following a file (someone else’s idea), which didn’t help > /etc/systemd/system/rigctld.service > [Unit] > Description=rigctld Hamradio rig controler > After=syslog.target network.target > [Service] > Type=simple > ExecStart=/usr/bin/rigctld -m 2050 -r /dev/ttyUSB0 > User=rigctld > Group=rigctld > [Install] > WantedBy=multi-user.target > I’m not a Linux expert and I’m out of ideas > Thanx > Steve AJ6TL -- 73 N3GB |
|
From: Stephen G. <ste...@gm...> - 2025-03-05 19:52:08
|
I’m having trouble getting rigctld to work I’m running DragonOS and I currently have hamlib version 4.7 installed and my rig is a TX-500 rigctl -m 2050 -r /dev/ttyUSB0 <all commands> work rigctld -m 2050 -r /dev/ttyUSB0 nothing works; it hangs, i.e., does not return to the command prompt sudo systemctl restart rigctld gave me this error (: Unit rigctld.service not found) I created the following a file (someone else’s idea), which didn’t help /etc/systemd/system/rigctld.service [Unit] Description=rigctld Hamradio rig controler After=syslog.target network.target [Service] Type=simple ExecStart=/usr/bin/rigctld -m 2050 -r /dev/ttyUSB0 User=rigctld Group=rigctld [Install] WantedBy=multi-user.target I’m not a Linux expert and I’m out of ideas Thanx Steve AJ6TL |
|
From: Michael B. <no...@gi...> - 2025-03-04 20:44:26
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 43f8afa6a4f13fbfb96c2ec75f25ddfb5da9a8e2 https://github.com/Hamlib/Hamlib/commit/43f8afa6a4f13fbfb96c2ec75f25ddfb5da9a8e2 Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-03-04 (Tue, 04 Mar 2025) Changed paths: M simulators/Makefile.am A simulators/simicr8600.c Log Message: ----------- Add simicr8600 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Michael B. <no...@gi...> - 2025-03-04 20:43:14
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 6b11c7e970ba9f7a348ba4836d94bfcf177f2ece https://github.com/Hamlib/Hamlib/commit/6b11c7e970ba9f7a348ba4836d94bfcf177f2ece Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-03-01 (Sat, 01 Mar 2025) Changed paths: M rigs/codan/codan.c Log Message: ----------- Remove ptt from CODAN NGS -- does not have it Commit: 3dbb7011d1a2c14cc0f2351c321b66787d51e9f3 https://github.com/Hamlib/Hamlib/commit/3dbb7011d1a2c14cc0f2351c321b66787d51e9f3 Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-03-01 (Sat, 01 Mar 2025) Changed paths: M rigs/codan/codan.c Log Message: ----------- Fix NGT caps name Commit: 701d6bf477f784192684c8035cd874d10966a5e6 https://github.com/Hamlib/Hamlib/commit/701d6bf477f784192684c8035cd874d10966a5e6 Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-03-04 (Tue, 04 Mar 2025) Changed paths: M rigs/codan/codan.c M rigs/codan/codan.h M src/rig.c Log Message: ----------- Hopefully fix CODAN NGS set_freq/get_freq Commit: 7269ba62647a613ba7b63fc6ddbd2070ba7f9db5 https://github.com/Hamlib/Hamlib/commit/7269ba62647a613ba7b63fc6ddbd2070ba7f9db5 Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-03-04 (Tue, 04 Mar 2025) Changed paths: M include/hamlib/rig.h M src/rig.c Log Message: ----------- Merge branch 'master' of github.com:Hamlib/Hamlib Compare: https://github.com/Hamlib/Hamlib/compare/f2f947c51d45...7269ba62647a To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: George B. <geo...@gm...> - 2025-02-28 15:15:11
|
I was really only trying to get github CI to check the build on windows(hence the PR title) - I don't know if the win pthread implementation supports the PTHREAD_MUTEX_RECURSIVE attribute type. Anyway, if it compiles it should work at least as well as the current code, except for one big gotcha - if somewhere deep in the bowels of hamlib I/O error handling tries to do rig_close()/rig_open() for recovery, all bets are off. rig_close() will try to terminate all threads, some of which may be waiting on a mutex. That's not a new problem, but this code may make the problem more evident. On 2/28/25 07:14, Michael Black via Hamlib-developer wrote: > Branch: refs/heads/master > Home: https://github.com/Hamlib/Hamlib > Commit: 439bd96b5d01ddbaf811a1e1df98c08a1caff406 > https://github.com/Hamlib/Hamlib/commit/439bd96b5d01ddbaf811a1e1df98c08a1caff406 > Author: George Baltz N3GB <Geo...@gm...> > Date: 2025-02-27 (Thu, 27 Feb 2025) > > Changed paths: > M src/rig.c > > Log Message: > ----------- > Fix the easy parts of missing thread locks > > - Fix depth initialization so LOCK() at least calls rig_lock() > - Add message showing why rig_lock() does nothing > - Add missing LOCK(0)s > > > Commit: 0147da5a3ca8dc0f874d2a43ff5a2e702bbc4f41 > https://github.com/Hamlib/Hamlib/commit/0147da5a3ca8dc0f874d2a43ff5a2e702bbc4f41 > Author: George Baltz N3GB <Geo...@gm...> > Date: 2025-02-28 (Fri, 28 Feb 2025) > > Changed paths: > M include/hamlib/rig.h > M src/rig.c > > Log Message: > ----------- > Replace rs->multicast->mutex with a dedicated mutex for the API. > > Use PTHREAD_MUTEX_RECURSIVE and change LOCK() to always call rig_lock(). > Still needs a reliable way to determine availability. > > > Commit: f2f947c51d45f5596afd0b8b3c8df7c3d88d93dd > https://github.com/Hamlib/Hamlib/commit/f2f947c51d45f5596afd0b8b3c8df7c3d88d93dd > Author: Michael Black <mdb...@ya...> > Date: 2025-02-28 (Fri, 28 Feb 2025) > > Changed paths: > M include/hamlib/rig.h > M src/rig.c > > Log Message: > ----------- > Merge pull request #1675 from GeoBaltz/fix26 > > DO NOT MERGE! > > > Compare: https://github.com/Hamlib/Hamlib/compare/3d46647808dc...f2f947c51d45 > > To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
|
From: Michael B. <no...@gi...> - 2025-02-28 12:14:14
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 439bd96b5d01ddbaf811a1e1df98c08a1caff406 https://github.com/Hamlib/Hamlib/commit/439bd96b5d01ddbaf811a1e1df98c08a1caff406 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-02-27 (Thu, 27 Feb 2025) Changed paths: M src/rig.c Log Message: ----------- Fix the easy parts of missing thread locks - Fix depth initialization so LOCK() at least calls rig_lock() - Add message showing why rig_lock() does nothing - Add missing LOCK(0)s Commit: 0147da5a3ca8dc0f874d2a43ff5a2e702bbc4f41 https://github.com/Hamlib/Hamlib/commit/0147da5a3ca8dc0f874d2a43ff5a2e702bbc4f41 Author: George Baltz N3GB <Geo...@gm...> Date: 2025-02-28 (Fri, 28 Feb 2025) Changed paths: M include/hamlib/rig.h M src/rig.c Log Message: ----------- Replace rs->multicast->mutex with a dedicated mutex for the API. Use PTHREAD_MUTEX_RECURSIVE and change LOCK() to always call rig_lock(). Still needs a reliable way to determine availability. Commit: f2f947c51d45f5596afd0b8b3c8df7c3d88d93dd https://github.com/Hamlib/Hamlib/commit/f2f947c51d45f5596afd0b8b3c8df7c3d88d93dd Author: Michael Black <mdb...@ya...> Date: 2025-02-28 (Fri, 28 Feb 2025) Changed paths: M include/hamlib/rig.h M src/rig.c Log Message: ----------- Merge pull request #1675 from GeoBaltz/fix26 DO NOT MERGE! Compare: https://github.com/Hamlib/Hamlib/compare/3d46647808dc...f2f947c51d45 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Michael B. <no...@gi...> - 2025-02-27 04:29:44
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 2a9634d7053c2fa9d125473f9d285c32bcca24fb https://github.com/Hamlib/Hamlib/commit/2a9634d7053c2fa9d125473f9d285c32bcca24fb Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-02-23 (Sun, 23 Feb 2025) Changed paths: M rigs/icom/icr8600.c Log Message: ----------- Revert "Remove set_vfo from ICR8600 -- doesn't have any" This reverts commit fb145e873b63adf3c640292efb336783a97117bd. Commit: 9de6fe2400cff5489cd487e71af299758a4ee567 https://github.com/Hamlib/Hamlib/commit/9de6fe2400cff5489cd487e71af299758a4ee567 Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-02-24 (Mon, 24 Feb 2025) Changed paths: M rigs/icom/icr8500.c Log Message: ----------- Fix name of IC-R8500 Commit: 3d46647808dc9dde14106d259aebefa85042cd43 https://github.com/Hamlib/Hamlib/commit/3d46647808dc9dde14106d259aebefa85042cd43 Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-02-26 (Wed, 26 Feb 2025) Changed paths: M rigs/codan/codan.c Log Message: ----------- Change CODAN NGT to CR Compare: https://github.com/Hamlib/Hamlib/compare/fb145e873b63...3d46647808dc To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Brian D. <br...@ar...> - 2025-02-26 17:37:06
|
Hey everyone, I’m working with the county OEM to get several Codan NGT radios working with VarAC (and the commercial version in the case of the EOC). I’ve programmed all VarAC call and slot frequencies into channel memory. I can talk to the radio via PuTTY and it will happily receive commands. I have the latest rigctl running 4.6, and 34002 is set as my rig. I’m signed in as admin and I have the freetune feature, so I’m open TX between 1.6 and 30 MHz. (It's like the amateur feature, but with zero band restrictions.) If I start the radio and leave echo on, when I issue a command through rigctl (let’s say ‘f’ to query frequency), it shows that it sent the radio the ‘freq’ command and the rigctl sees the radio echo ‘freq’ as the response, which is obviously not gonna work. Then, if I turn echo off, when I issue the ‘f’ command, rigctl yells and then says it timed out and then prompts me for another command. I’m SO close to having this perfect and there’s just something in the syntax that rigctl doesn’t seem to like about the radio’s reply. Please help! I’d gladly donate a chunk of change to get this fixed. Regards, Brian Daugherty | KF5WCW Ark River Radio Services Office: +1.719.881.0785 Cell: +1.512.605.7926 |
|
From: Black M. <mdb...@ya...> - 2025-02-24 15:34:54
|
ALC is scaled 0-1. So 0.1 and such is valid too.
STRENGHT is using a lookup table and should match dB levels.
#define FTDX101D_STR_CAL { 12, \
{ \
{ 0, -60 }, /* S0 */ \
{ 17, -54 }, /* S0 */ \
{ 25, -48 }, \
{ 34, -42 }, \
{ 51, -36 }, \
{ 68, -30 }, \
{ 85, -24 }, \
{ 102, -18 }, \
{ 119, -12 }, \
{ 136, -6 }, \
{ 160, 0 }, /* S9 */ \
{ 255, 60 }, /* +60 */ \
} }
On Sunday, February 23, 2025 at 11:23:11 PM CST, Michael Morgan <cmo...@gm...> wrote:
I have started using rigctld to interface between my applications (QLog, WSJTX, etc). I also have a custom app for me shack that get the frequency to adjust my Steppir, SPE Amplifier, and Antenna Switch. One thing I wish was easier on the Yaseu was a way to see all the meters so I can easily see Power, SWR, ALC etc. So I decided to add that to my station controller app. Most make sense and align well. I do have two questions though:
- ALC it seems to only show values from 0 to 1. So as soon as I have some ALC action it goes to a 1 and that’s it. Not sure if that is normal.
- S-Meter I am guessing I should use the Strength option but it doesn't really seem to align to db so wasn’t sure how to convert it.
Thanks for any guidance.
Michael, AA5SH
_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer
|
|
From: Michael M. <cmo...@gm...> - 2025-02-24 05:20:04
|
I have started using rigctld to interface between my applications (QLog, WSJTX, etc). I also have a custom app for me shack that get the frequency to adjust my Steppir, SPE Amplifier, and Antenna Switch. One thing I wish was easier on the Yaseu was a way to see all the meters so I can easily see Power, SWR, ALC etc. So I decided to add that to my station controller app. Most make sense and align well. I do have two questions though: - ALC it seems to only show values from 0 to 1. So as soon as I have some ALC action it goes to a 1 and that’s it. Not sure if that is normal. - S-Meter I am guessing I should use the Strength option but it doesn't really seem to align to db so wasn’t sure how to convert it. Thanks for any guidance. Michael, AA5SH |
|
From: Michael B. <no...@gi...> - 2025-02-23 22:05:37
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: beea87c2aece53f04a6ac8ae10a43f456136e31d https://github.com/Hamlib/Hamlib/commit/beea87c2aece53f04a6ac8ae10a43f456136e31d Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-02-19 (Wed, 19 Feb 2025) Changed paths: M bindings/rig.swg Log Message: ----------- Suppress 451 warning in rig.swg Commit: fb145e873b63adf3c640292efb336783a97117bd https://github.com/Hamlib/Hamlib/commit/fb145e873b63adf3c640292efb336783a97117bd Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-02-23 (Sun, 23 Feb 2025) Changed paths: M rigs/icom/icr8600.c Log Message: ----------- Remove set_vfo from ICR8600 -- doesn't have any Compare: https://github.com/Hamlib/Hamlib/compare/98a0184680a7...fb145e873b63 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: <gm...@bt...> - 2025-02-23 16:33:14
|
Hi, I'm having a look again at connecting to WFVIEW to connect with my IC-705 over WiFi. I have set hamlib debug level 5. And can see where it times out, the response to the command "s" appears to be taking 20 s or so. The second time it does it, it reports the timeout to my app which then closes the connection. This is evident in the attachment ...excert.txt. The first time the time out is displayed but not reported back to my app. It was still taking over 20s but a few ms less. The full log is the other file. When I captured this I am sure that the response for the "s" command was printed immediately "0". And 20 seconds later the timeout was displayed. 73 Phil GM3ZZA. |
|
From: (SV2AGW) G. R. <sv...@ya...> - 2025-02-21 07:19:58
|
Hi The default settings for Kenwood TS950SDX serial interface should be 4800BPS, 1start bit, 8 character bits,parity none, 2 stop bits. it still works with 1 stop bit but receives a frame and then the next is lost because the startbit is receives as the second stop bit. 73 SV2AGW) George Rossopoulos Anakreontos 14 GR-54250 Thessaloniki GREECE www.sv2agw.com www.frinos.com www.agwtracker.com unsubscribe |
|
From: George B. <geo...@gm...> - 2025-02-19 10:28:41
|
Won't make a difference to the operation. The root problem is that there is NO locking between morse_data_handler() and the rest of hamlib. LOCK() will never call rig_lock(), and even if it did rs->multicast is always NULL. rig_init() sets rs->depth to 1. Since ENTERFUNC increments depth, the test in the LOCK macro will never succeed, so rig_lock() isn't called. Initializing rs->depth to 0 at least calls rig_lock(), which then does nothing, as the multicast buffer is never allocated. It should be set in multicast_init(), but there is only one call to it in the code base, and that is in the '#ifdef TEST' part of multicast.c. As I said, multithreading in hamlib needs re-working. On 2/18/25 5:10 PM, Black Michael wrote: > In kenwood.c try changing this line > > case RIG_MODEL_TS890S: > SNPRINTF(morsebuf, sizeof morsebuf, "KY2%s", m2); > > Change the 2 to a space. > SNPRINTF(morsebuf, sizeof morsebuf, "KY %s", m2); > > > > > > > > > > > On Monday, February 17, 2025 at 07:24:36 PM CST, George Baltz <geo...@gm...> wrote: > > > > > > Still doesn't work with multicast turned on. Today's testing done via > rigctl. > > Two attachments - debugging patch+fix for gcc error(needs upper case W), > and STDERR output from: > > rigctl -m 2041 -r /dev/pts/2 -vvvvvv > --setconf=multicast_data_addr=224.0.0.1 2>/tmp/err_verb.txt > > Near the bottom of the trace it shows both calls to rig_lock() (around > the call to kenwood_send_morse()) took the early return. > > > On 2/17/25 6:21 PM, Black Michael wrote: >> --set-conf=multicast_data_addr=224.0.0.1 >> >> So does it work when multicast is turned on? >> >> How are you sending data to hamlib? >> >> Mike W9MDB >> >> >> >> >> >> >> >> >> >> On Monday, February 17, 2025 at 01:11:31 PM CST, George Baltz <geo...@gm...> wrote: >> >> >> >> >> >> Last weekend was the ARRL DX CW weekend, and I fired up my >> peanut-whistle to try for a couple of new ones on 10M. Used tlf and >> latest 4.7-git hamlib. It worked for a while, then it started >> missing/dropping messages, timeouts, rig link errors, or hard lockups. >> Restarting the program was the only way back to operational. My >> condolences to any station I left hanging. >> >> This morning I started investigating, using simts890. Was not happy >> with what I found. Somehow, in turning off multicast, rig_lock() (and >> hence LOCK()) was turned into a NOP. It bailed out in the first >> conditional - rs->multicast == NULL. So no coordination at all between >> morse_data_handler() and the rest of the world, resulting in clobbered >> messages, untimely rig_flush(), etc. >> >> How should this be fixed? Having m_d_h() use a lock added by multicast >> may be expedient, but hardly intuitive. And it really doesn't help with >> the multi-threaded application problem. >> >> The whole threading approach in hamlib needs to be analyzed, both for >> internal and external threads. There are at least 4 mutexes for various >> interactions, some of which are really only used on one side, and none >> of them cover the whole range of possible conflicts. >> >> Comments and advice, please. >> |
|
From: Michael B. <no...@gi...> - 2025-02-18 15:11:16
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 98a0184680a70aa4943ea2ba7dbcf8ca03bebf1f https://github.com/Hamlib/Hamlib/commit/98a0184680a70aa4943ea2ba7dbcf8ca03bebf1f Author: Michael Black W9MDB <mdb...@ya...> Date: 2025-02-18 (Tue, 18 Feb 2025) Changed paths: M bindings/Makefile.am M src/rig.c Log Message: ----------- Remote -w451 flag -- not available in all versions of gcc To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
33 messages has been excluded from this view by a project administrator.
