I have only seen this behavior with WSJT-X, and only when changing bands
via ci-v/cat. I have been unable to reproduce this in FLDigi or FLRig.
SKCClogger only reads freq and does not provide for any form of rig
control.

73 de AI8W, Chris

On Wed, Jun 10, 2020, 00:06 Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> I was able to test with a friend that has an IC-7300 and we could
> duplicate this problem -- but it's not easily reproducible.
>
> Has nothing to do with WSJT-X or hamlib.  Appears to be some sort of bug
> in the IC-7300 where changing bands and quickly transmitting is causing
> some sort of burp that turns on the preamp randomly
>
> Mike W9MDB
>
>
> On Sunday, June 7, 2020, 07:54:55 AM CDT, Topher Petty <ai8...@gmail.com>
> wrote:
>
>
> Bill:
> You seem to be under the impression that I run these programs
> simultaneously. Let me clear this up...
> I do not.
> I quit SKCCLogger when working in WSJT-X. I quit WSJT-X when working CW
> (and using SKCCLogger to log my contacts). FLDIGI only has its HAMlib rig
> control activated when I'm working PSK or RTTY, and I usually close
> SKCCLogger when I'm doing that, because I log THOSE contacts in FLDIGI.
> Both SKCCLogger and FLDIGI had issues reading and writing to the rig while
> WSJT-X 2.1.x was installed, EVEN THOUGH WSJT-X WAS NOT RUNNING AT THE TIME.
> Simply having WSJT-X 2.1.x installed meant that I had to play the "unplug
> the cable, plug it back in, start up FLRig, start [SKCCLogger|FLDIGI] close
> FLRig, cross fingers" game every time I wanted to utilize either of those
> programs.
> This is why I asked for a version that isn't statically linked.
> Again, I'm done, here. You're smarter than everyone in the room.
> Everything I assert is rubbish. You can figure it out, or not, at
> your convenience. I lost all desire to work with you when the insults
> started to fly. If I feel the desire to work FT8, I'll just put up with
> whatever odd symptoms exist, and restart udev/play the cable game every
> time I feel like switching to another mode, or logging a CW contact.
>
> 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 Sun, Jun 7, 2020 at 8:38 AM Bill Somerville <g4...@classdesign.com>
> wrote:
>
> On 07/06/2020 13:27, Topher Petty wrote:
> > Better than a screenshot, I present to you my config file.
> >
> > This entire exchange has felt like the time when Yaesu called me
> > everything except a HAM radio operator because their bad sourcing of
> > finals in their FT-100Ds caused repeated failures of the final
> > amplifier ICs. I never did get my money back, or an apology from Yaesu
> > for their "customer service" personnel's behavior both on the
> > telephone and in email, and they lost a customer for life because of it.
> >
> > So, rather than being accused of spreading more rubbish, this will be
> > my last communication regarding this on this list. My email address is
> > good on QRZ if you need any more information.
> >
> > 73 de AI8W, Chris
>
> Chris,
>
> does SKCCLogger emulate the Hamlib rigctld rig server, I ask because it
> appears to be talking directly to the rig. That would mean that no other
> application could get CAT control of the rig due to the serial port
> being unavailable.
>
> 73
> Bill
> G4WJS.
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to