Date
1 - 11 of 11
Locked Many incomplete contacts
|
Pat N6PAT
Here's an example that happened early this morning while I was trying to get the VK9NC Norfolk Island DXpedition on their first day.
After 2 hours of trying to get through a huge pileup I finally got them but then all of my RR73 apparently were not working even though he was hearing me at -9 and I was receiving him at -1 to +1. I kept sending RR73 but he wasn't getting them. I lost out on an ATNO. But then I tried a few minutes later and got him (see pic 2). This dropout started after the last upgrade.   |
|
|
|
Possibly because this message is from January and my emails for this group only go back to June or so. I normally don't expect to see answers to 10 month old posts, so I don't go back forever looking for the OP.
toggle quoted message
Show quoted text
I only do emails, I rarely go to the website. I like to stay current. Michael WA7SKG Pat Kane via Groups.Io wrote on 10/17/19 10:36 AM: Mike, |
|
|
|
Pat N6PAT
Mike, This is the original thread I was replying to. I'm not sure why the link didn't show 73 Pat N6PAT
On Thursday, October 17, 2019, 12:13:59 PM EDT, Michael WA7SKG <wa7skg@...> wrote:
Apparently I am not getting all the messages for this group. I cannot -=-=-=-=-=-=-=-=-=-=-=-find the message this user is replying to. It makes it very hard to follow a thread when you only see part of the messages. Especially since many do not include the original message in their reply. Michael WA7SKG Pat Kane via Groups.Io wrote on 10/17/19 1:41 AM: > I am also seeing this same behavior. > > A DX station is calling CQ. I respond. He sends a signal report. I send > send R-signal report. He keeps sending his initial signal report as if > not hearing me even though his initial report to me is good like +10 > > Sometimes after numerous tries the QSO works but many times it does not. > > I will try to disable/enable TX that you've suggested and see if that > works for me. Groups.io Links: You receive all messages sent to this group. View/Reply Online (#4367): https://groups.io/g/WSJTX/message/4367 Mute This Topic: https://groups.io/mt/28948712/1232019 -=-=- Moderated by Andy K3UK and Roger G4HZA -=-=- Group Owner: WSJTX+owner@groups.io Unsubscribe: https://groups.io/g/WSJTX/leave/4120783/358545897/xyzzy [n6pat@...] -=-=-=-=-=-=-=-=-=-=-=- |
|
|
|
The watchdog timer is configurable. I believe it defaults to 6 minutes, but there's nothing keeping people from increasing it to, say, 60 minutes. 73, -- Dave Slotter, W3DJS On Thu, Oct 17, 2019 at 11:42 AM Jim Cooper <JTalert@...> wrote: On 17 Oct 2019 at 1:41, Pat Kane via Groups.Io wrote: |
|
|
|
Erik Plourde <ve2tdt@...>
Watchdog must have been off and robot on.... Le jeu. 17 oct. 2019 à 11:42, Jim Cooper <JTalert@...> a écrit : On 17 Oct 2019 at 1:41, Pat Kane via Groups.Io wrote: |
|
|
|
Svein Henriksen
I think that if you look carefully at the waterfall, the station you are trying to QSO with may look a little bit broader than normal and that it appears that your RX bracket is not centered. I see this all the time. I then simply move my tx bracket a bit to the side ot to another free frequency. In most cases the QSO will then conclude.
toggle quoted message
Show quoted text
The problem being underlying QRM transmitting in the same time slot as the other station so he cannot see it. 73 de Svein LA3PU Sent from my iPad On 17 Oct 2019, at 17:35, Jim Cooper <JTalert@...> wrote:On 17 Oct 2019 at 1:41, Pat Kane via Groups.Io wrote:I had one last night, FT4 on 20m, with |
|
|
|
Apparently I am not getting all the messages for this group. I cannot find the message this user is replying to. It makes it very hard to follow a thread when you only see part of the messages. Especially since many do not include the original message in their reply.
toggle quoted message
Show quoted text
Michael WA7SKG Pat Kane via Groups.Io wrote on 10/17/19 1:41 AM: I am also seeing this same behavior. |
|
|
|
Jim Cooper
On 17 Oct 2019 at 1:41, Pat Kane via Groups.Io wrote:
I am also seeing this same behavior.I had one last night, FT4 on 20m, with a K4 where he kept sending R -07 for TWENTY ONE minutes !! I kept responding with RR73 each time and finally got a 73 ... I've emailed him to ask what was going on, but his sig went all the way up to +04 during that time and -07 is such a bad strength that he reported to me ... It seemed odd that he'd keep sending for that long without the 'watchdog' timing out. w2jc |
|
|
|
Pat N6PAT
I am also seeing this same behavior.
A DX station is calling CQ. I respond. He sends a signal report. I send send R-signal report. He keeps sending his initial signal report as if not hearing me even though his initial report to me is good like +10 Sometimes after numerous tries the QSO works but many times it does not. I will try to disable/enable TX that you've suggested and see if that works for me. |
|
|
|
Ron
I see this and just assume its due to QSB fading. Since it happens to me just as the band is opening or closing most of the time. Same effect I see on SSB or any other mode as the band is changing.
|
|
|
|
Komkit Listisard
Guys, I am having strange issue with my latest WSJT-X. I am starting to notice the issue 3-4 days ago. I will try my very best to explain it. First, I have NTP Meinberg software installed to sync my clock. I have always check it against http://time.is to make sure I am exact. I can monitoring and decoding stations all day long, no problem none whatsoever. Waterfall is coming down nicely, no complain here. Rigs are two Yaesu FT-991A, does not matter which one I was using it. However the issue is starting to show up during or in the middle of the QSO, often causing an incomplete contact. Let me try to explain. Does not matter if the band is pack wall to wall with signals or just the two of us. For example, if I am to answering someone’s CQ it would look like the following..  During each cycle I can see K2GT is trying to come back to me, I see the waterfall is coming down on 1930 Hz and within the middle of the
green division line but unable to decoding it. This often solve by, in this case at 10045 I halted TX or Disabled TX and wait for K2GT to show up. Then I immediately I click on Enable TX and on to complete QSO per screen shot. This is happening regardless of SNR it could be +5 to and from me, does not matter. If this starting to act up I either halt TX or disable TX then I often completed the QSOs that way. Also, the 2nd example, N4XPZ and I were going at it for 3 round until at 001100 after I sent 73 I halted TX, then wait and click on 001115 to sent another 73 until then N4XPZ acknowledged my 73 – QSO completed. I have no idea what is going on, this happened very often just about every 2-3 contacts I made. Any thoughts? Something is out of sync? 73, W3KIT
|
|
|
