What I recall is my friend found the preamp being remembered across bands....not that it randomly turned on. So band switching caused it from the rig's memory.
If the email chain says something else than maybe we need to address it. Mike On Thursday, July 16, 2020, 08:06:10 AM CDT, Topher Petty <[email protected]> wrote: Mike: We've verified this in the past (somewhere around two months ago). You had a friend/acquaintance who was able to reproduce my findings on the 7300. I can pull up the emails and screenshot them for you if you'd like. 73 de AI8W, Chris -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/CM/CC/E/IT/TW d-@ s+:+ !a C++$@ UBLVSCX*++++(on)$>$ P++>$ L+++$ E+@ W++>$ N+++ o+@ K+++ w@ O+@ M-@ V@>$ PS+@ PE@ Y+ PGP++ t+ 5+ X++ R@* tv++ b+>$ DI++ D+ G++ e h r+++ y+++ ------END GEEK CODE BLOCK------ On Thu, Jul 16, 2020 at 8:54 AM <[email protected]> wrote: > IC7300 has worked just fine for me with WSJT Hamlib. No unexpected problems. > Only thing that did surprise me was the auto turn on of it when starting > WSJT. Never happened until one of the 2.2 versions. > > Fred > N2XK > > On Jul 16, 2020 8:32 AM, Black Michael via wsjt-devel > <[email protected]> wrote: >> I can't think of any reason the preamp should randomly turn on. >> I believe the 7300 will remember such settings by band...is that what you're >> seeing maybe? Or is it coming on during normal QSOs on a single band...and >> any idea when? >> >> Mike W9MDB >> >> >> >> >> >> >> >> On Thursday, July 16, 2020, 06:56:34 AM CDT, Topher Petty <[email protected]> >> wrote: >> >> >> >> >> I can verify that the ic-718, ic-7300 (with some bugs such as preamp >> switching on randomly) and ic-7610 are all working at my qth with both the >> latest wsjtx and last year's flrig/fldigi (which does not show the same bugs >> as wsjtx) . My 751A does not currently function so it is impossible to test. >> >> Hope that helps. >> >> de AI8W, c >> >> On Thu, Jul 16, 2020, 06:26 Stephen VK3SIR <[email protected]> wrote: >>> Folks, >>> >>> I am only responding here as I have had a few emails in the background ... >>> and I put this out there to guide learning for some... for many this will >>> be old hat news ! >>> >>> There has been a lot of work take place with Hamlib since R 2.2.2 was >>> released. WSJTX relies heavily on Hamlib. >>> >>> The packages of Hamlib used to compile and release the precompiled versions >>> on release at https://physics.princeton.edu/pulsar/K1JT/wsjtx.html are >>> built to versions of Hamlib that are snapshotted within the source tarball >>> found within the source distribution found at >>> https://physics.princeton.edu/pulsar/K1JT/wsjtx-2.2.2.tgz . >>> >>> Bill G4WJS's maintains a repository at >>> git://git.code.sf.net/u/bsomervi/hamlib that is used to standardise WSJTX >>> development; all documentation within the WSJTX source tarball refers to >>> Bill's repository. Bill's repository may or may not currently be >>> synchronised with the code in the release tarball. Bill may be able to >>> provide further guidance on this for those of us that are developing >>> software. Yet it's a very sound programing practise to base bug-reporting >>> off known snapshots of libraries. >>> >>> The "Master" live development Hamlib repository can be found at >>> https://git.code.sf.net/p/hamlib/code . This is "bleeding edge" code as >>> some would define it. >>> >>> I can foresee that Mike W9MDB and the Hamlib team are aiming to work to >>> slating a formal Hamlib 4.0 release (superseding the 3.3 release around in >>> most places). >>> >>> For WSJTX the preferred repo is that which Bill G4WJS maintains at >>> git://git.code.sf.net/u/bsomervi/hamlib :-) >>> >>> Based on Mike's email (and for ongoing development, debugging, >>> compatibility testing etc.) the "Master " repo should be used. You just >>> replace references referred to in the WSJTX INSTALL readme file that refer >>> to Bill's repo (i.e. git://git.code.sf.net/u/bsomervi/hamlib ) with those >>> for the "Master" repo (i.e. https://git.code.sf.net/p/hamlib/code ). >>> >>> All is easy if you are compiling with Linux and Linux variants ... But for >>> Windows compiles to the latest Hamlib source the simplest way is to use >>> Greg KI7MT's JTSDK's. There is complexity here as there has been no formal >>> maintenance of the Windows JTSDK's for 12 months. >>> >>> The JTSDK 3.0 as delivered/documented on the JTSDK download site (i.e. >>> https://sourceforge.net/projects/jtsdk/ ) should compile a 32-bit Windows >>> wsjtx ... There are some "patches" if you review the posts on >>> [email protected] (Google search that as it is not an email address - i.e. >>> https://groups.io/g/JTSDK ) if you want to compile your own Windows WSJTX >>> using the "Master" repository. >>> >>> JTSDK 3.1 is also available at https://sourceforge.net/projects/jtsdk/ - >>> but in order to "work easily" and "behave" just like the JTSDK 3.0 it needs >>> a series of "experiment" patches posted at [email protected]. The README file >>> attached with the "Experiment" scripts allow for configuration options to >>> be set to be able to pull from the "preferred" WSJTX repo - Bill >>> Somerville's Repository, the "Master" Hamlib Repository or even not to pull >>> from a repository at all (and use the packaged Hamlib snapshot packaged in >>> the WSJTX source). >>> >>> The best guidance for Mike W9MDB and the Hamlib team would be provided from >>> people that are compiling their own Hamlib and WSJTX (and perhaps other >>> software such as the FL-software) and not those using pre-compiled software >>> or standardised library snapshots. >>> >>> Can I recommend that if you are responding to Mike's call please specify if >>> you are using "new" Hamlib source or if you are using packaged WSJTX source >>> and/or distributions? >>> >>> If you need help please ask or post here or respond directly via email. If >>> you need help compiling WSJTX for yourself then please peruse the JTSDK @ >>> GROUPS.IO site at https://groups.io/g/JTSDK first [ Note: as I have been >>> using it as a blog to help as many as I possibly can and to avoid >>> repetition as many cannot post here due to the lack of maintenance at that >>> site ]. >>> >>> HAM - Help All mankind. We are here to help and progress learning. I also >>> hope that the intent of this post is clear and that it is to help. >>> >>> 73 >>> >>> Steve I >>> VK3VM / VK3SIR >>> >>> -----Original Message----- >>> From: Christoph Berg <[email protected]> >>> Sent: Thursday, 16 July 2020 6:43 PM >>> To: Black Michael <[email protected]>; WSJT software development >>> <[email protected]> >>> Subject: Re: [wsjt-devel] Rig verification >>> >>> Re: Black Michael via wsjt-devel >>>> 3009 Icom IC-706 20200614.0 >>>> Untested RIG_MODEL_IC706 >>> >>> My 706 (no mk something) works flawlessly. >>> >>> (I used to get "rig communication problem" popups, but these are rare now >>> and I think the problem is in the USB serial adapter not coping with HF, >>> and not in the rig.) >>> >>> Christoph >>> >>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >>> >>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >> _______________________________________________ >> wsjt-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> _______________________________________________ >> wsjt-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
