Hi, first thanks to Joe Taylor, Bill and others who responded to me, and thanks to Philip Gladstone who worked with me on this to try to narrow down the cause. A couple of weeks ago, I cleared the cache, cookies and all Chrome history on the WSJT-X laptop. Since then, WSJT-X and PSK-Reporter are working fine together now. Maybe something lingering in there caused my problems; don't know why, but I'll take success and know what to try if it happens again. 73, Mark KM0A
On Sat, Dec 28, 2019 at 9:38 AM Mark Ammann <markff...@gmail.com> wrote: > Hi all, > I'm writing to you per the suggestion by Philip Gladstone. Philip worked > with me for quite a while on the phone last week trying to diagnose why PSK > reporter is not seeing many of my WSJT decodes on 15m, 10m or 6 meters. > It seems as if WSJT is not making data available for long periods of > time. This is a relatively new development on my end. Same computer, same > OS, etc. Sometimes it will take up to an hour before anything is seen on > port 4739 (using Wireshark), then there will be a few data transmissions, > then nothing again. 10m and 6m are the worst where it can go for hours > with WSJT decodes and nothing is seen on port 4739 or PSK reporter. If I > change bands on WSJT, sometimes it seems like it forces a transmission but > only the last couple of decodes will show up on the PSK map. However, if I > change to 80m, 40m, or 20m, everything starts working fine and the PSK map > starts updating within a few minutes, and things look good as long as I > stay on one of those bands.. > If I run JT Alert (linked to WSJT) and Hamspots, the 15m, 10m and 6m > decodes are seen there. > Any help or suggestions are greatly appreciated! > 73, Mark KM0A > >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
