Hi Bill – The 2.1.x versions of wsjt-x decoding works well, both fast and normal decode. The fast decode is a little quicker on 2.1.x, but both can be used without an issue.
Using a 2.2.x version, decoding on a busy band has the following behavior: first decode in cycle picks up a few messages, second decode a few, then the third decode runs a long time (well into the next cycle) and the majority of messages get decoded on that third decode. Switching between fast and slow does not help, since the poor decode is already unusable with the fast decode, so hard to tell if normal is much slower. Radio being used is Yaeusu FT-991. Same problem reported by others using the FT-991A, FT-867D, and TS-590SG. See (https://groups.io/g/RigPi/topic/74694393). Thanks for your reply, AE0AU - Tony From: wsjt-devel-requ...@lists.sourceforge.net Sent: Tuesday, June 9, 2020 3:36 AM To: wsjt-devel@lists.sourceforge.net Subject: wsjt-devel Digest, Vol 76, Issue 93 Send wsjt-devel mailing list submissions to wsjt-devel@lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/wsjt-devel or, via email, send a message with subject or body 'help' to wsjt-devel-requ...@lists.sourceforge.net You can reach the person managing the list at wsjt-devel-ow...@lists.sourceforge.net When replying, please edit your Subject line so it is more specific than "Re: Contents of wsjt-devel digest..." Today's Topics: 1. Re: WSJTX/Ras-pi/gpio (Bill Somerville) 2. Re: WSJT-X 2.2.x decode performance on RigPi (Bill Somerville) 3. Drop down band-selector list problem (Bill Mullin) 4. Re: v2.1.2 Radio On/Off CAT Problem? (Alan Groups) ---------------------------------------------------------------------- Message: 1 Date: Tue, 9 Jun 2020 01:07:11 +0100 From: Bill Somerville <g4...@classdesign.com> To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJTX/Ras-pi/gpio Message-ID: <bef0d86e-72af-4847-d1d1-126bf6218...@classdesign.com> Content-Type: text/plain; charset="windows-1252"; Format="flowed" On 09/06/2020 01:02, Mark Sheffield wrote: > > Just to close out this topic and perhaps save a future ham some > frustration, the solution for me turned out to be: > > rigctld-wsjtx -m 2004 -r /dev/ttyUSB0 -s 9600 -P GPIO*N* -p 17 > > using the *negated* strobe. > > Thanks for the help, Bill ? you put me onto the path of righteousness. > > Rgds ? Mark/K4LFL > Hi Mark, thanks for the update, glad you have it working. Did you have an inverting switching transistor between the GPIO pin and the rig PTT? 73 Bill G4WJS. -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 2 Date: Tue, 9 Jun 2020 01:11:11 +0100 From: Bill Somerville <g4...@classdesign.com> To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJT-X 2.2.x decode performance on RigPi Message-ID: <6c3c33c2-e398-d002-a2ea-1cad5b60b...@classdesign.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" On 09/06/2020 01:03, Tony wrote: > > From my post to a RigPi forum: > > ?Has anyone else tried running the latest WSJT-X 2.2.0 on a RigPi (3B+)? > > The upgrade was straight forward and everything worked, but I found > right away on a crowded band that the new decode method that splits > things up during the 15 second cycle results in many decodes happening > very late into the next 15 second cycle (as late as 10 seconds, which > makes Tx response virtually impossible for those received > transmissions). Tried with "Fast" and "Normal" decode and found that > made no difference. > > Ended up reverting back to 2.1.0, which works fine (even on a busy > band).? I suspect WSJT-X 2.2.0 may be saving its results when doing > multiple decodes to disk, and the microSD is not a really fast storage > device.? Just a guess ... could be something else.? > > This problem was confirmed by two other RigPi users and on different > radio types using the RigPi. > > ?73 > > AE0AU ? Tony > Hi Tony, disk i/o is not the issue, probably just more CPU resource required. "Menu->Decode->Fast" should be making a significant difference. What is the receiver? I ask because SDRs with high latency do not get the full benefit of the earliest decoding attempts. 73 Bill G4WJS. -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 3 Date: Mon, 8 Jun 2020 18:20:19 -0700 From: Bill Mullin <mrb...@aa4m.com> To: wsjt-devel@lists.sourceforge.net Subject: [wsjt-devel] Drop down band-selector list problem Message-ID: <4b0d5136-88da-e0bc-9221-db2030ded...@aa4m.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" I posted this in another forum but got no answer, so I thought I'd try here. This problem is difficult to describe!? From the new WSJT-X 2.2.1 user's manual: "On a trial basis, and in response to numerous suggestions from around the world, we have added a second set of suggested dial frequencies for FT8 on three HF bands and also on 6 meters. The new suggested dial frequencies are 7.071, 10.133, 14.071, and 50.310 MHz.? These frequencies will appear in your drop-down band-selector list after you go to the "Settings | Frequencies" tab, right-click on the frequency table, and select "Reset".? Alternatively, you can add the new FT8 frequencies manually." I tried adding the new frequencies both using the menus and then manually.? In both cases the FT8 portion of the drop down band-selector list become somewhat truncated.? The list is still usable so this should be considered a cosmetic problem only. Note that I'd include a picture of the scrambled menu if I thought the group accepted attachments.? Note also the the FT4 menu is not affected by additions to the FT8 menu. 73, Bill - AA4M -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 4 Date: Tue, 9 Jun 2020 09:36:19 +0100 From: Alan Groups <al...@alangroups.plus.com> To: WSJT software development <wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] v2.1.2 Radio On/Off CAT Problem? Message-ID: <c7e3f41f-7cd5-c72c-3d13-dbb503d6c...@alangroups.plus.com> Content-Type: text/plain; charset="windows-1252"; Format="flowed" Hi, I've just checked my Kenwood: * Turned the rig on and changed the frequency from that last used with WSJT-X 2.2.1 * Turned rig off at it's power button but leaving PSU on * Started WSJT-X 2.2.1 * Rig turned on and WSJT-X changed to the new frequency, rig beeped * Closed WSJT-X, rig stayed on * Turned rig off at it's power button but leaving PSU on * Started WSJT-X 2.2.1 * Rig turned on, no change in frequency and no beep Alan G0TLK On 09/06/2020 00:39, Al Pawlowski wrote: > No. That box is unchecked in my setup. > > > > Al Pawlowski, K6AVP > Los Osos, CA USA > > > >> On Jun 8, 2020, at 16:31, wsjt-devel-requ...@lists.sourceforge.net >> <mailto:wsjt-devel-requ...@lists.sourceforge.net> wrote: >> >> Do you have "Monitor returns to last used frequency" turned on? >> That will cause the rig to wake up as it has to get the frequency. >> Mike W9MDB > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ ------------------------------ Subject: Digest Footer _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------ End of wsjt-devel Digest, Vol 76, Issue 93 ******************************************
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
