hamlib-developer Mailing List for Ham Radio Control Libraries (Page 106)
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
(27) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Michael B. <no...@gi...> - 2022-11-10 23:54:05
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 853806b9785975309c407c1e7d7f2158b50a95b3 https://github.com/Hamlib/Hamlib/commit/853806b9785975309c407c1e7d7f2158b50a95b3 Author: Mike Black W9MDB <mdb...@ya...> Date: 2022-11-10 (Thu, 10 Nov 2022) Changed paths: M rigs/dummy/netrotctl.c M tests/rotctl.c M tests/rotctl_parse.c Log Message: ----------- Fix rotctld dumpcaps to expose client rot_type instead of Other https://github.com/Hamlib/Hamlib/issues/1035 Commit: 9a6d4d761249c553ef71093754213ca72e94eeb9 https://github.com/Hamlib/Hamlib/commit/9a6d4d761249c553ef71093754213ca72e94eeb9 Author: Mike Black W9MDB <mdb...@ya...> Date: 2022-11-10 (Thu, 10 Nov 2022) Changed paths: Log Message: ----------- Merge branch 'master' of https://github.com/Hamlib/Hamlib Compare: https://github.com/Hamlib/Hamlib/compare/fc0fc1c67a53...9a6d4d761249 |
|
From: Michael B. <no...@gi...> - 2022-11-10 23:53:01
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: fc0fc1c67a5332a8ad2b55caddf288f2797a4b4e https://github.com/Hamlib/Hamlib/commit/fc0fc1c67a5332a8ad2b55caddf288f2797a4b4e Author: Mike Black W9MDB <mdb...@ya...> Date: 2022-11-10 (Thu, 10 Nov 2022) Changed paths: M rigs/dummy/netrotctl.c M tests/rotctl.c M tests/rotctl_parse.c Log Message: ----------- Fix rotctld dumpcaps to expose client rot_type instead of Other |
|
From: Michael B. <no...@gi...> - 2022-11-10 22:00:49
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: eeac97c72594b364fc65d760d4ca9d332796d380 https://github.com/Hamlib/Hamlib/commit/eeac97c72594b364fc65d760d4ca9d332796d380 Author: Mike Black W9MDB <mdb...@ya...> Date: 2022-11-10 (Thu, 10 Nov 2022) Changed paths: M NEWS M doc/man1/rigctl.1 M rigs/yaesu/ft991.c M rigs/yaesu/ft991.h M rigs/yaesu/newcat.c M src/idx_builtin.h Log Message: ----------- Fix FT-991 level_gran https://github.com/Hamlib/Hamlib/issues/1144 |
|
From: Black M. <mdb...@ya...> - 2022-11-10 21:25:12
|
Using rigctl or WSJT-X or something else?
Mike W9MDB
On Thursday, November 10, 2022 at 02:52:04 PM CST, Patrick R <kd...@gm...> wrote:
Yeasu 857d is still unable to properly switch between VFOa and VFOb
either with the specific buttons or the A/B button.
The application always reports VFOa though the radio could be on one or
the other.
_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer
|
|
From: Patrick R <kd...@gm...> - 2022-11-10 20:51:42
|
Yeasu 857d is still unable to properly switch between VFOa and VFOb either with the specific buttons or the A/B button. The application always reports VFOa though the radio could be on one or the other. |
|
From: Michael B. <no...@gi...> - 2022-11-10 18:18:47
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 539457f6ce4c178b2141821b89521dfd69ba1875 https://github.com/Hamlib/Hamlib/commit/539457f6ce4c178b2141821b89521dfd69ba1875 Author: Mike Black W9MDB <mdb...@ya...> Date: 2022-11-10 (Thu, 10 Nov 2022) Changed paths: M rigs/yaesu/ftdx10.h Log Message: ----------- Update ftdx10.h power levels |
|
From: Michael B. <no...@gi...> - 2022-11-10 18:17:43
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 27f424dfe2d9922c81c2d371dcee56074715c619 https://github.com/Hamlib/Hamlib/commit/27f424dfe2d9922c81c2d371dcee56074715c619 Author: Mike Black W9MDB <mdb...@ya...> Date: 2022-11-10 (Thu, 10 Nov 2022) Changed paths: M rigs/dummy/flrig.c Log Message: ----------- Add RIG_FUNC_TUNER to flrig.c |
|
From: Nate B. <n0...@n0...> - 2022-11-10 14:19:09
|
* On 2022 10 Nov 06:51 -0600, Greg Troxel wrote: > > It would really help if README (and I mean top level, not some > developer-only one) answered: Historically, the intended audience of the README file is that which received the source tarball. In recent years its scope has expanded, but too much information can be as confusing as too little is frustrating. > What is the authoritative home for hamlib: github, sourceforge, > someplace else? Actually, both SourceForge and GitHub have equal standing as far as versioned releases are concerned. > In each git repo that has any standing (vs mirrors), what do the > branches mean? > > The second can be as brief as "Development happens on master (often by > merging feature branches) and each release has a release branch." This last paragraph sums it up, development occurs in the master branch with feature branches merged in as appropriate. Release branches are named 'Hamlib-M.m[.p]' where M is the major version, m is the minor version, and the optional p is the point release version. Any other branches are likely historical relics from the CVS/SVN days and can be safely ignored. Currently feature branches mostly exist in personal working repositories and then are merged into master. As far as development goes, GitHub is the primary development platform these days. I sync the SourceForge master branch manually on occasion from the GitHub master branch. Unfortunately, this is not done every day and it will sometimes lag by several weeks depending on when I get around to it. Release branches are pushed to each as part of my release procedure. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 |
|
From: Nate B. <n0...@n0...> - 2022-11-10 14:06:05
|
I'm glad you figured out the issue, Greg! Each repository contains checksum files and also there are signature files signed with my GPG key. I realize that GPG is a bear to work with but right now it is the only means by which we can be certain that anything was tampered with after it left this computer. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 |
|
From: Black M. <mdb...@ya...> - 2022-11-10 14:04:39
|
Done.
On Thursday, November 10, 2022 at 06:51:31 AM CST, Greg Troxel <gd...@le...> wrote:
It would really help if README (and I mean top level, not some
developer-only one) answered:
What is the authoritative home for hamlib: github, sourceforge,
someplace else?
In each git repo that has any standing (vs mirrors), what do the
branches mean?
The second can be as brief as "Development happens on master (often by
merging feature branches) and each release has a release branch."
_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer
|
|
From: Michael B. <no...@gi...> - 2022-11-10 14:04:17
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 09d7ed2f196707e68cd24fffad03bebb525184f7 https://github.com/Hamlib/Hamlib/commit/09d7ed2f196707e68cd24fffad03bebb525184f7 Author: Mike Black W9MDB <mdb...@ya...> Date: 2022-11-10 (Thu, 10 Nov 2022) Changed paths: M README.md Log Message: ----------- Improve README.md by adding github and sourceforge info |
|
From: Black M. <mdb...@ya...> - 2022-11-10 13:39:56
|
Many of the levels need to "fixed" to show the range and step size.
I'll do that for the FT-991 this morning. And I'll improve the rigctrl manual to show the units used by the levels.As for the levels you asked about.
Some levels are zero to unity (i.e one) where 0=0% and 1.0=100%RFPOWER NR
Some levels are dB PREAMP STRENGTH
Some values are Hamlib constants -- 32 would be the PO meter and 8 would be the drain currentMETER -- RIG_METER_NONE = 0, /*< No display meter */ RIG_METER_SWR = (1 << 0), /*< Stationary Wave Ratio */ RIG_METER_COMP = (1 << 1), /*< Compression level */ RIG_METER_ALC = (1 << 2), /*< ALC */ RIG_METER_IC = (1 << 3), /*< IC */ RIG_METER_DB = (1 << 4), /*< DB */ RIG_METER_PO = (1 << 5), /*< Power Out */ RIG_METER_VDD = (1 << 6), /*< Final Amp Voltage */ RIG_METER_TEMP = (1 << 7) /*< Final Amp Temperature */
Mike W9MDB
On Thursday, November 10, 2022 at 06:39:27 AM CST, Georgina Joyce <ge...@ge...> wrote:
Hello All,
How do I interpret the levels returned by my radio? For example:
l RFPOWER responds 1.0000.
l METER responds 32 and last night it responded 8 so I thought I had changed something. Not sure what METER is supposed to be.
l STRENGTH responds I assume a DB level.
l NR responds 0.066667 What does this mean?? Is this the noise reduction option?
l PREAMP responds 10, is this off or is there 2 levels as the caps lists 10 and 20.
A lot of these levels have 0.0/0 listed in the caps and initially I thought that meant that that the radio didn't support that level adjustment. But now I am confused because it is not what it is telling me.
How do I adjust the frequency step? In Europe we use 12.5KHz for FM VHF? I am sure I saw some notation about narrow FM somewhere but can't find it now. I think my 818 accepts 9000 as the passband but the 991 does not.
Many thanks for any suggestions.
Georgina
Call: M0EBP
DMR ID: 2346259
Allstar: 52178
Locater: IO83PS
_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer
|
|
From: Greg T. <gd...@le...> - 2022-11-10 13:37:08
|
Sorry for the false alarm. Apaprently I saw > https://github.com/Hamlib/Hamlib/releases/tag/4.5 and just edited the tag into a github-fetching macro, which fetched the auto-generated repo tarball, rather than the actual release. github seems to encourage not having release files, and used to, I think, make it difficult, so I've gotten used to projects not making distfiles and instead using automated source tarballs. It would still be nice to clarify in README the github/sourceforge relationship and if it's expected that the set of files in sourceforge for a release is identical to those on github (except that github also provides repo tarballs, which are missing on sourceforge as they aren't actually release files). 73 de n1dam |
|
From: Greg T. <gd...@le...> - 2022-11-10 13:02:07
|
[following up to my sent copy because my post hasn't arrived on the list yet] I find that the distfile on sourceforge seems ok, relative to 4.3.1 matches what I got before. and that makes me think that maybe I got the distfile from sourceforge. It may just be that github provides a tarball of the repo, which is broken, because that's not the release tarball, which appears generated from 'make dist'. 73 de n1dam |
|
From: Greg T. <gd...@le...> - 2022-11-10 12:56:51
|
Nate Bargmann <n0...@n0...> writes: > After months of work by Mike and many contributors, Hamlib 4.5 is > released to the wild. Downloads are available from: > > https://github.com/Hamlib/Hamlib/releases/tag/4.5 > > https://sourceforge.net/projects/hamlib/files/hamlib/4.5/ I updated the pkgsrc entry for hamlib shortly after the announcement, on November 1. It built and passed tests fine on NetBSD 9 amd64. I probably didn't say anything because it working isn't news. pkgsrc, like many other packaging systems, records checksums for distfiles, so that users will build the same thing the packager tested, and to detect supply chain attacks on upstream. I just received a report that the downloaded distfile failed checksumming. I set aside my copy from before and downloaded again, and indeed it is different. In general, it is not ok for upstreams to modify a distfile once it is posted because of the security concerns around unauthorized modifications and the mechanisms to deal with them. github doesn't really support posting tarballs, but it "modifying distfile" translates to "moving tags". I unpacked both. One has hamlib-4.5 and the other Hamlib-4.5. Accounting for that (which seems like a bug - 4.3.1 is lower case), there are very many differences. I didn't see any announcement about this. So it looks like the 4.5 distfile got broken somehow, and I'm unable to convince myself that this wasn't an attack (even if I would guess that it's much more likely not an attack). Looking at github, the 4.5 tag seems older than my first download. Starting to read the diff from 4.3.1 to my first download of 4.5, it makes sense. The diff from my first download of 4.5 to doing it again today is huge. Is anybody else seeing this? Does anybody else know what's going on? 73 de n1dam Beginning of 4.5-earlier to 4.5-now diff: Only in NEW/hamlib: .editorconfig Only in NEW/hamlib: .github Only in NEW/hamlib: .gitignore Only in NEW/hamlib: Makefile.Windows Only in ORIG/hamlib: Makefile.in Only in NEW/hamlib: README.coding_style Only in NEW/hamlib: README.md Only in NEW/hamlib: README.release Only in NEW/hamlib: README.win32 Only in NEW/hamlib: SECURITY.md Only in NEW/hamlib: Segfault-award Only in NEW/hamlib: VFOs.txt Only in ORIG/hamlib: aclocal.m4 Only in ORIG/hamlib/amplifiers/elecraft: Makefile.in Only in ORIG/hamlib/amplifiers/gemini: Makefile.in Only in ORIG/hamlib/android: Makefile.in Only in ORIG/hamlib/bindings: Makefile.in Only in NEW/hamlib/bindings: csharp Only in NEW/hamlib/bindings: hamlibvb.bas.in Only in NEW/hamlib/bindings: phpdemo.php Only in NEW/hamlib: bootstrap Only in ORIG/hamlib: build-aux Only in ORIG/hamlib/c++: Makefile.in Only in ORIG/hamlib: configure Only in NEW/hamlib: cppcheck.sh Only in ORIG/hamlib/doc: Makefile.in Only in NEW/hamlib/doc: README.man-pages Only in ORIG/hamlib/doc: hamlib.cfg Only in NEW/hamlib/doc: manuals Only in NEW/hamlib/doc: split-man.pl Only in NEW/hamlib: docker-build Only in NEW/hamlib: extra Only in ORIG/hamlib/include: Makefile.in Only in ORIG/hamlib/include/hamlib: config.h Only in ORIG/hamlib/include/hamlib: config.h.in Only in NEW/hamlib/include/hamlib: winpthreads.h Only in ORIG/hamlib/lib: Makefile.in Only in ORIG/hamlib/macros: Makefile.in Only in ORIG/hamlib/macros: libtool.m4 Only in ORIG/hamlib/macros: ltoptions.m4 Only in ORIG/hamlib/macros: ltsugar.m4 Only in ORIG/hamlib/macros: ltversion.m4 Only in ORIG/hamlib/macros: lt~obsolete.m4 Only in NEW/hamlib: perl |
|
From: Greg T. <gd...@le...> - 2022-11-10 12:51:20
|
It would really help if README (and I mean top level, not some developer-only one) answered: What is the authoritative home for hamlib: github, sourceforge, someplace else? In each git repo that has any standing (vs mirrors), what do the branches mean? The second can be as brief as "Development happens on master (often by merging feature branches) and each release has a release branch." |
|
From: Georgina J. <ge...@ge...> - 2022-11-10 12:39:05
|
Hello All, How do I interpret the levels returned by my radio? For example: l RFPOWER responds 1.0000. l METER responds 32 and last night it responded 8 so I thought I had changed something. Not sure what METER is supposed to be. l STRENGTH responds I assume a DB level. l NR responds 0.066667 What does this mean?? Is this the noise reduction option? l PREAMP responds 10, is this off or is there 2 levels as the caps lists 10 and 20. A lot of these levels have 0.0/0 listed in the caps and initially I thought that meant that that the radio didn't support that level adjustment. But now I am confused because it is not what it is telling me. How do I adjust the frequency step? In Europe we use 12.5KHz for FM VHF? I am sure I saw some notation about narrow FM somewhere but can't find it now. I think my 818 accepts 9000 as the passband but the 991 does not. Many thanks for any suggestions. Georgina Call: M0EBP DMR ID: 2346259 Allstar: 52178 Locater: IO83PS |
|
From: Michael B. <no...@gi...> - 2022-11-09 21:27:51
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 36717917ce9347f21708ad391befede96f486d51 https://github.com/Hamlib/Hamlib/commit/36717917ce9347f21708ad391befede96f486d51 Author: Mike Black W9MDB <mdb...@ya...> Date: 2022-11-09 (Wed, 09 Nov 2022) Changed paths: M rigs/yaesu/ftdx10.c Log Message: ----------- Fix 5W level of ftdx10.c based on user testing |
|
From: Dave B <g8k...@go...> - 2022-11-09 11:44:09
|
Try into a dummy load (or at minimum power, and at a lower frequency.) Could be RF getting into where it shouldn't, especially if you have a USB/Serial adapter in the mix somewhere. 73. Dave G8KBV On 09/11/2022 11:33, Co Co wrote: > > Hi, > when connecting wsjtx254 on Raspberry Pi4 to my rig Icom IC-706 MK II > an error occur sometimes(!). > > Frequency on the rig is 28.074 and it's also adjusted in wsjtx, > communication works properly, so changing band or QRG in WSJTX also > changes on my rig. > > But.. When sending, the trx-bar counts up from 1 to 15 and when > reaching the 6 transmit stops and error will be displayed with these > details: > > Hamlib error: Communication bus error > rig_get_freq(1914): freqMainB=21088000,modemainB=AM,widthmainB=2400 > rig_get_freq: elapsed=5427ms > rig.c(1917): rig_get_freq return(-13) Communication bus error > rig_get_freq(1914): freqMainB=21088000,modemainB=AM,widthmainB=2400 > rig_get_freq: elapsed=5427ms > rig_get_freq: elapsed=5427ms while getting current VFO frequency > > Timestamp... > > On 10m this error occurs nearly in each trx-cycle, on 15m nearly never. > > I don't use splitmode on VFOA and VFOB, but VFOB is currently adjusted > to the mentioned QRG 21088... > > Error also occurs, when VCOB is on same values as VCOA in splitmode. > > Enable Tx button is deactivated after this error. > > CAT parameters like Baudrate don't have any effect on this error. > > Any ideas for this weired behavior? > > Rigctl Hamlib 4.5 is on the raspberry > > Cheers and thx > Vy73 de Cornel, DO5CR > > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer -- Created on and sent from a Unix like PC running and using free and open source software: |
|
From: Co Co <slo...@gm...> - 2022-11-09 11:33:57
|
Hi, when connecting wsjtx254 on Raspberry Pi4 to my rig Icom IC-706 MK II an error occur sometimes(!). Frequency on the rig is 28.074 and it's also adjusted in wsjtx, communication works properly, so changing band or QRG in WSJTX also changes on my rig. But.. When sending, the trx-bar counts up from 1 to 15 and when reaching the 6 transmit stops and error will be displayed with these details: Hamlib error: Communication bus error rig_get_freq(1914): freqMainB=21088000,modemainB=AM,widthmainB=2400 rig_get_freq: elapsed=5427ms rig.c(1917): rig_get_freq return(-13) Communication bus error rig_get_freq(1914): freqMainB=21088000,modemainB=AM,widthmainB=2400 rig_get_freq: elapsed=5427ms rig_get_freq: elapsed=5427ms while getting current VFO frequency Timestamp... On 10m this error occurs nearly in each trx-cycle, on 15m nearly never. I don't use splitmode on VFOA and VFOB, but VFOB is currently adjusted to the mentioned QRG 21088... Error also occurs, when VCOB is on same values as VCOA in splitmode. Enable Tx button is deactivated after this error. CAT parameters like Baudrate don't have any effect on this error. Any ideas for this weired behavior? Rigctl Hamlib 4.5 is on the raspberry Cheers and thx Vy73 de Cornel, DO5CR |
|
From: Black M. <mdb...@ya...> - 2022-11-09 04:44:42
|
Looks reasonable.
Mike W9MDB
On Tuesday, November 8, 2022 at 06:08:26 PM CST, George Baltz <geo...@gm...> wrote:
|
|
|
|
|
|
|
|
|
|
|
|
Attached is a set of patches I have been working on to add some functions of hamlib that have not been implemented for the Kenwood TS-890S.
Since this is the first time I've really used git to manage my own code, and the first real C I've written in >15 years, I'd appreciate knowing if I'm on the right track.
These are NOT complete, but should show the direction I'm heading. Please tell me any formatting or style changes needed before I get to a final submission,
73
N3GB
_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer
|
|
From: Michael B. <no...@gi...> - 2022-11-08 21:33:35
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 77ae5ef5c99401d242832fa91f61d1a8483bb1e5 https://github.com/Hamlib/Hamlib/commit/77ae5ef5c99401d242832fa91f61d1a8483bb1e5 Author: Mike Black W9MDB <mdb...@ya...> Date: 2022-11-08 (Tue, 08 Nov 2022) Changed paths: M simulators/simicom9700.c Log Message: ----------- Update simicom9700.c |
|
From: George B. <geo...@gm...> - 2022-11-08 21:14:58
|
Attached is a set of patches I have been working on to add some functions of hamlib that have not been implemented for the Kenwood TS-890S. Since this is the first time I've really used git to manage my own code, and the first real C I've written in >15 years, I'd appreciate knowing if I'm on the right track. These are NOT complete, but should show the direction I'm heading. Please tell me any formatting or style changes needed before I get to a final submission, 73 N3GB |
|
From: Michael B. <no...@gi...> - 2022-11-08 21:10:01
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 2993ca9e62d5eaf2e82ae8f60b85198aa7e1cd3c https://github.com/Hamlib/Hamlib/commit/2993ca9e62d5eaf2e82ae8f60b85198aa7e1cd3c Author: Mike Black W9MDB <mdb...@ya...> Date: 2022-11-08 (Tue, 08 Nov 2022) Changed paths: M rigs/icom/icom.c M simulators/simicom9700.c Log Message: ----------- Fix segfault in icom_get_powerstat |
|
From: Michael B. <no...@gi...> - 2022-11-08 20:59:43
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 1ef362a954647b9ec92da0808963b1de0b0fa7b1 https://github.com/Hamlib/Hamlib/commit/1ef362a954647b9ec92da0808963b1de0b0fa7b1 Author: Mike Black W9MDB <mdb...@ya...> Date: 2022-11-08 (Tue, 08 Nov 2022) Changed paths: M NEWS Log Message: ----------- Fix NEWS |
33 messages has been excluded from this view by a project administrator.
