Date
1 - 7 of 7
Locked WSJT-X (or my PC) not reporting to PSK Reporter
|
Mark Ammann
Hi All, Philip Gladstone was kind to work with me for quite a while a few evenings ago trying to diagnose my problems with WSJT-X FT8 decodes not getting reported to PSK Reporter, and am wondering if anyone else has experienced this. I'll list some of the symptoms below. 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. I'm using Windows 10 and WSJT-X v2.1.2, 0068f9. I've tried deleting/uninstalling WSJT and re-downloaded, and tried both the 32 and 64 bit versions but no change in performance is seen. I thought I might be having firewall or other Windows issues, however the behavior described below doesn't seem to hint at that. This all started a month or so ago, as previously it had been working fine. Only changes to the PC since would be some Windows updates. Also, I was not transmitting any RF during these tests, so there's no RF feedback issues. 1. The problem is most prevalent on 15m, 10m and 6m. Sometimes WSJT will begin transmitting data only after about an hour of monitoring on 15m, even though many stations were decoded. Then it will send a few times, then stop. While on the phone with Philip, 20m data was being sent fine every 5 minutes, but then just suddenly stopped being sent even though new stations were being decoded. I made sure that these stations had not been seen by WSJT going back 12 hours on that band. 2. On 6m, while monitoring MSK144 for several hours and on several days, and decoding several stations with grid squares in the exchange, no transmissions are being sent from WSJT (or my PC). 3. In almost all cases after long periods of no WSJT data being sent, if I switch to either 40m or 80m, WSJT will begin sending data after a few minutes and data is sent reliably as long as I stay on those bands. This is repeatable. 4. If I change bands after a period of no data sent, WSJT will sometimes make a transmission at the band change instance, but only the stations seen in the last FT8 sequence are sent. Any help or suggestions are greatly appreciated! 73, Mark, KM0A |
|
|
|
Jim Bacher - WB8VSU
Mark, I looked at my information in pskreporter, but do not see big gaps. It however is not reporting a significant amount of what I am hearing. I wonder if anti virus software is impacting it?
toggle quoted message
Show quoted text
If you are running jtalert, set it to report to hamspots. Jtalert implies in its set up that Hamspots is more reliable than pskreporter. I looked a few minutes ago and Hamspots has over twice as many calls my station heard and reported than pskreporter has. Jim Bacher, WB8VSU wb8vsu@... https://trc.guru
|
|
|
|
Markku Oksanen
Hi
Have you opened the outgoing port 4739 on the windows firewall? Markku OH2RA |
|
|
|
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 server. 73 Bill G4WJS. |
|
|
|
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: |
|
|
|
On 26/12/2019 14:33, Mark Ammann wrote:
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.Hi Mark, I can't say for sure, only Philip can, but my experience is that spots are "refreshed" on the map whenever a new spot is received. 73 Bill G4WJS. |
|
|
|
Mark Ammann
I have udp port 4739 now allowed through the Windows firewall, but no improvements. Just had WSJT-X running for 45 minutes on 15 meters with many stations decoded, and no traffic on port 4739 (watching vial Wireshark) and no updates to the PSK reporter. As soon as I switch to 20 meters, all returns to normal and reports start being sent again via port 4739 and PSK Reporter is picking them up. Mark On Thu, Dec 26, 2019 at 8:48 AM Bill Somerville <g4wjs@...> wrote: On 26/12/2019 14:33, Mark Ammann wrote: |
|
|