Locked Re: WSJT-X (or my PC) not reporting to PSK Reporter

Mark Ammann

Jim, Markku ,Bill, many thanks for your replies. 
Jim, I've started playing with JT Alert and Hamspots and will see how that compares to PSK Reporter.  Thanks.
Markku, I'm looking at port 4739 with Wireshark for data but haven't changed any firewall settings yet.  Thanks for the tip.  It's the higher bands that are problems (data not being sent via that port), but will look at the firewall settings.  On 40m and 20m data is sent via that port reliably as far as I can tell.
Bill, I was referring to "new ones" as far as PSK Reporter is concerned; i.e, how far back will it look before posting a station again to the map if reported previously in the past few hours.  
Thanks guys for your help and suggestions!
Mark  KM0A

On Thu, Dec 26, 2019 at 6:34 AM Bill Somerville <g4wjs@...> wrote:
On 23/12/2019 19:48, Mark Ammann wrote:
> Using Wireshark software at my end to watch the data being sent from
> WSJT to Philip's address, we found that WSJT-X (or my PC) for long
> periods will not transmit any data even though new unique callsigns
> are being seen by WSJT.

Hi Mark,

reading the rest of your post I think you understand that decodes
including a grid square are posted as spots to PSKReport, but just in
case, just checking.

Calls do not have to be new ones, WSJT-X spots any call decoded in a
standard message including their grid square. There is a randomized
delay of less that a minute to try and even the load on the PSKReporter


Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#5045): https://groups.io/g/WSJTX/message/5045
Mute This Topic: https://groups.io/mt/69237970/4055657
Moderated by Andy K3UK and Roger G4HZA
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/7345162/809903622/xyzzy  [markffma4@...]

Join {main@WSJTX.groups.io to automatically receive all group messages.