Re: [Hamlib-developer] On toward 4.6
Library to control radio transceivers and receivers
Brought to you by:
n0nb
From: Black M. <mdb...@ya...> - 2024-12-03 21:35:40
|
Try this dll -- should behave better. https://www.dropbox.com/scl/fi/q0s2ykjhaz19j7sv84rf6/libhamlib-4.dll?rlkey=m02sjo5hqyfqgquhasdpptals&dl=1 Mike W9MDB On Monday, December 2, 2024 at 01:40:34 AM CST, Sakari Nylund <sak...@ni...> wrote: Hi! There is a problem with IC7300 mode/bandwidth/filter setting: When sending: M CW 1 Meaning to set CW mode with filter #1 Works setting the filter #1 but changes the bandwidth to 50Hz (ic7300 minimum value) If you then send: M CW 2 Meaning to set CW mode with filter #2 it also works, but same way putting bandwidth to 50Hz Same with: M CW 3 After you have run through all these three commands you have every filter's bandwidth set to 50Hz that was not the purpose. If mode CW is replaced with USB it happens in same way (I have not tested LSB but assume the same bug there, too). Using: M CW -1 Works as should leaving bandwidth and filter number untouched and affects only for mode. Higher numbers will set bandwidth by the number given (without touching the filter number): M CW 800 Will put mode CW and bandwidth 800Hz as expected. Instead sending: M CW 801 Will keep the filter untouched but change bandwidth to 900 Not 801 as requested as it does not fit IC7300 BW stepping. Sending : M CW 850 causes: RPRT -1 RPRT -1 And no change to bandwidth. While 850 could be more real request than 801, but does not either fit to IC7300's 100Hz step. Results are still different with values 801 and 850 All this tells something about the bandwidth value checking routine. It should round the bandwidth value to nearest 50Hz, if value is under 500Hz, or to nearest 100Hz if value is over 500Hz And also take account values -1, 1, 2 and 3 with their meanings. [saku@hamtpad ~]$ rigctld --version rigctld Hamlib 4.6~git 2024-11-25T04:29:44Z SHA=dcc7b3 64-bit -- Saku OH1KH Nate Bargmann kirjoitti 1.12.2024 klo 20.04: > Hi All. > > Mike has let me know that he is confident that Hamlib is very close to > the 4.6 release. If anyone has any outstanding patches to include, now > is the time to submit them! Anything such as spelling/grammar > corrections and documentation improvements are welcome at this time as > well. > > On my end I've updated my virtual machine to the latest Debian 11 (I like > to run a release behind on builds just to be sure things work across at > least a few years worth of build tooling) and will be doing some mock > releases I can test on Debian 12 and Arch. Around the end of this week > I plan to create the 4.6 branch and make an RC archive that I'll host at > the daily snapshots page. > > Ordinarily I wouldn't be quite so cautious but since it has been some > time since the last release, I'd like to "shake the bushes" so to speak > before 4.6. > > 73, Nate > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer _______________________________________________ Hamlib-developer mailing list Ham...@li... https://lists.sourceforge.net/lists/listinfo/hamlib-developer |