Discussion:
[wsjt-devel] wsjt-devel Digest, Vol 41, Issue 198
roger stafford
2017-07-15 21:08:10 UTC
Permalink
hi thanks for the new mode I am also seeing the od bad decode
im running r7894 started 2 rev’s ago
cheers vk3fz

Sent from Windows Mail

From: wsjt-devel-***@lists.sourceforge.net<mailto:wsjt-devel-***@lists.sourceforge.net>
Sent: ‎Sunday‎, ‎July‎ ‎16‎, ‎2017 ‎12‎:‎55‎ ‎AM
To: wsjt-***@lists.sourceforge.net<mailto:wsjt-***@lists.sourceforge.net>

Send wsjt-devel mailing list submissions to
wsjt-***@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-***@lists.sourceforge.net

You can reach the person managing the list at
wsjt-devel-***@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: FT8 Bad Spots (Black Michael)
2. Re: FT8 Bad Spots (Bill Somerville)
3. Re: r7891 Issue (dgb)
4. Re: r7891 Issue (Black Michael)


----------------------------------------------------------------------

Message: 1
Date: Sat, 15 Jul 2017 14:20:43 +0000 (UTC)
From: Black Michael <***@yahoo.com>
To: WSJT software development <wsjt-***@lists.sourceforge.net>
Subject: Re: [wsjt-devel] FT8 Bad Spots
Message-ID: <***@mail.yahoo.com>
Content-Type: text/plain; charset="utf-8"

Hopefully Bill can answer this as do believe he wrote it.I've never examined the pskreporter flow.
de Mike W9MDB
From: Gary McDuffie <***@ag0n.net>
To: Black Michael <***@yahoo.com>; WSJT software development <wsjt-***@lists.sourceforge.net>
Sent: Saturday, July 15, 2017 7:58 AM
Subject: Re: [wsjt-devel] FT8 Bad Spots
You want "Monitor returns to last used frequency" in the general settings under Beahvior and that SHOULD set the frequencies on the rig to match WSTJ-X.
Mike, I?ve wondered the same thing.? If I change bands, how soon is the PSKR data going out?? I?ve worried that when I make the band change, the data will go out marked for the new band, when it was actually decoded just before the switch.? What is the timing of the outgoing report?? Heck, I could even be sending out a burst every morning for FT8 or MSK144 for 3.950MHz!

Gary - AG0N


-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 2
Date: Sat, 15 Jul 2017 15:28:24 +0100
From: Bill Somerville <***@classdesign.com>
To: wsjt-***@lists.sourceforge.net
Subject: Re: [wsjt-devel] FT8 Bad Spots
Message-ID: <39997e2b-45e0-d96c-09ad-***@classdesign.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Hopefully Bill can answer this as do believe he wrote it.
I've never examined the pskreporter flow.
Hi Mike,

I didn't write it but have updated parts of it. I believe there is some
protection from sending spots after a band change where decodes might be
for either old or new band. There may be a hard coded minute somewhere
that needs to be the T/R period.

I am busy with other issues at present but I can look at it later.

73
Bill
G4WJS.

-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 3
Date: Sat, 15 Jul 2017 09:41:11 -0500
From: dgb <***@bayland.net>
To: wsjt-***@lists.sourceforge.net
Subject: Re: [wsjt-devel] r7891 Issue
Message-ID: <fba5c0ca-d69e-f0d7-705f-***@bayland.net>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

I am also seeing this happen.

73 Dwight NS9I
Dear Developers,
I was testing r7891 this morning on FT8 mode. I noticed that the "73"
line in the standard messages sometimes came-up blank when I
double-clicked a call sign to attempt a QSO. This happened on a random
basis, perhaps 10% of the time. I have now moved back to an earlier build.
Ed, K0KC
http://k0kc.us/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 4
Date: Sat, 15 Jul 2017 14:55:21 +0000 (UTC)
From: Black Michael <***@yahoo.com>
To: WSJT software development <wsjt-***@lists.sourceforge.net>
Subject: Re: [wsjt-devel] r7891 Issue
Message-ID: <***@mail.yahoo.com>
Content-Type: text/plain; charset="utf-8"

Can ya'll grab a screen shot when that happens. ?And also Save/Decoded and send the WAV file?
There was a patch to keep the 73 from being overwritten during autoseq and double-click so need to see what's happening.
de Mike W9MDB

From: dgb <***@bayland.net>
To: wsjt-***@lists.sourceforge.net
Sent: Saturday, July 15, 2017 9:45 AM
Subject: Re: [wsjt-devel] r7891 Issue

I am also seeing this happen. 73 Dwight NS9I

On 7/15/2017 7:14 AM, Ed Wilson via wsjt-devel wrote:

Dear Developers,
I was testing r7891 this morning on FT8 mode. I noticed that the "73" line in the standard messages sometimes came-up blank when I double-clicked a call sign to attempt a QSO. This happened on a random basis, perhaps 10% of the time. I have now moved back to an earlier build. ? Ed, K0KC
***@arrl.net http://k0kc.us/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
wsjt-devel mailing list
wsjt-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
wsjt-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

------------------------------

Subject: Digest Footer

_______________________________________________
wsjt-devel mailing list
wsjt-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


------------------------------

End of wsjt-devel Digest, Vol 41, Issue 198
*******************************************
Joe Taylor
2017-07-15 23:55:10 UTC
Permalink
Post by roger stafford
hi thanks for the new mode I am also seeing the od bad decode
im running r7894 started 2 rev’s ago
cheers vk3fz
Did you read the commit log message for r7887?

The open beta release of WSJT-X is v1.8.0-rc1, r7847.

If you choose to build from code in the development branch, you must
know that code there may be unstable, untested, unfinished, possibly
even unworthy of your attention.

If you decode to use the bleeding-edge code anyway, you have an
important responsibility: to document and submit bug reports that will
enable us to reproduce your problem. This may include sending us
relevant *.wav file(s). You'll find some other instructions here:

http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.7.1-devel.html#_bug_reports

-- 73, Joe, K1JT

Loading...