Re: [wsjt-devel] Sudden call replacement
Hi Phil, this happens to me 2 or 3 times in a session. To be specific, all message boxes are always correctly filled with the my own and my qso partners callsigns. When the problem occurs, the message appears in the "rx frequency" window with the qso partners callsign replaced with someone elses. Sometimes this completely prevents calling a particular station as the "wrong" callsign goes out right from the start in message 1. Other times the switch occurs mid qso and usually causes the qso to get stuck in an endless exchange of messages. It is what I described as "callsign hijacking" in my email of 24th January this year. I have found the only reliable way to escape the condition is abandon the qso and stop trying to work that station as the condition recurs if you come back some time later for another try. On one occasion I was able to complete the qso by editing the outgoing message 5 box to swap the angle brackets <> from the affected callsign to the other. 73 Paul VK2/G3NJV Sent from my Samsung Galaxy smartphone. Original message From: t...@gmx.fr Date: 07/02/2019 03:53 (GMT+10:00) To: wsjt devel list Subject: [wsjt-devel] Sudden call replacement Hi, I was having QSO with 3G3G. All of a sudden the call 3G3G was replaced by IV3ONZ on the same frequency. I tried to restore the proper call sign by clicking on the call sign in the Rx Frequency box. No ways! Strangely, just after I did it, <3G3G> ZS1/F5FDV RRR appeared in the Tx4 box but it was ZS1/F5FDV RRR that was displayed in the Rx Frequency box. Screen copy attached. 73 Phil F5FDV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Flex hamlib crash
On 06/02/2019 20:51, Al wrote:
This is from the SSDR CAT log for the TCP port leading up to the
event with TX inhibited..
19-02-06 14:28:05.123 TCP 26001 [sent]: ZZFI01;
2019-02-06 14:28:05.123 TCP 26001 [rcvd]: IF;
2019-02-06 14:28:05.125 TCP 26001 [sent]:
IF7074010+0009000;
2019-02-06 14:28:35.788 TCP 26001 [rcvd]: TX;
2019-02-06 14:28:35.790 TCP 26001 [rcvd]: ID;
2019-02-06 14:28:35.791 TCP 26001 [sent]: ID909;
2019-02-06 14:28:36.646 TCP 26001 [rcvd]: RX;
2019-02-06 14:28:36.647 TCP 26001 [rcvd]: ID;
2019-02-06 14:28:37.246 TCP 26001 [rcvd]: RX;
2019-02-06 14:28:37.246 TCP 26001 [rcvd]: ID;
2019-02-06 14:28:37.717 TCP 26001 [sent]: ID909;
2019-02-06 14:28:37.718 TCP 26001 [sent]: ID909;
At this point the only recourse is to kill WSJT-X with the task
manager and restart. I a normal situation the ID; following the first
RX, receives an ID909; response in 100msec and the second RX is not sent.
AL, K0VM
Hi Al,
that's interesting and surprising. The whole point of the ID commands is
to know that the "rig" has completed the prior command. Because the
Kenwood style CAT protocol that is used by SmartSDR, Elecraft and Yaesu
as well these days, has no acknowledgement of set commands; we have no
way of telling when it is safe to send another command. The ID command
is used because it is very fast and changes nothing at the rig, it is
effectively a no-op with an acknowledgement for when the prior command
has been processed.
Hard to say without a trace from WSJT-X, but I would guess that the RX
command is taking some time and the timeout is too short so it is being
retried.
So I have to wonder why SSDR and the Flex are taking more than one
second to respond to the command sequence "RX;ID;", that's glacial!
You can temporarily adjust the Hamlib timeout by creating a text file in
the WSJT-X log files directory ("Menu->File->Open log file directory")
called hamlib_settings.json and put the following into it:
{
"config": {
"timeout": "2000"
}
}
That will adjust the command timeout to 2 seconds (the default command
timeout for the Flex6xxx driver is 600 mS). Please give it a try and see
if that stops the hang up problem?
73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Flex hamlib crash
This has been reported before ... Maybe you've already fixed it; If WSJT-X is configured to use the FlexRadio 6xxx rig interface method then at random intervals WSJT-X will cease to function correctly. Various different features cease to work each time and the CPU usage will increase to about 10 times normal. I have discovered a method of causing the same symptoms to occur on demand which should assist in debugging this condition. If the Flex has TX inhibit set to inhibit then toggling WSJT-X into transmit ( Tune off>on>off ) will duplicate the symptoms resulting from of the random event. The random event appears to likely be the result of a delayed handshake (ID;) response from the radio. This is from the SSDR CAT log for the TCP port leading up to the event with TX inhibited.. 19-02-06 14:28:05.123 TCP 26001 [sent]: ZZFI01; 2019-02-06 14:28:05.123 TCP 26001 [rcvd]: IF; 2019-02-06 14:28:05.125 TCP 26001 [sent]: IF7074010+0009000; 2019-02-06 14:28:35.788 TCP 26001 [rcvd]: TX; 2019-02-06 14:28:35.790 TCP 26001 [rcvd]: ID; 2019-02-06 14:28:35.791 TCP 26001 [sent]: ID909; 2019-02-06 14:28:36.646 TCP 26001 [rcvd]: RX; 2019-02-06 14:28:36.647 TCP 26001 [rcvd]: ID; 2019-02-06 14:28:37.246 TCP 26001 [rcvd]: RX; 2019-02-06 14:28:37.246 TCP 26001 [rcvd]: ID; 2019-02-06 14:28:37.717 TCP 26001 [sent]: ID909; 2019-02-06 14:28:37.718 TCP 26001 [sent]: ID909; At this point the only recourse is to kill WSJT-X with the task manager and restart. I a normal situation the ID; following the first RX, receives an ID909; response in 100msec and the second RX is not sent. AL, K0VM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Question on Cocumentation of MessageTypes
On 06/02/2019 19:22, Roger Rehr W3SZ wrote: However, in type 2 messages the documentation says that "Mode" is to be sent in UTF8, so I expected to see in type 2 messages what I see sent for Mode in the Type 1 messages, e.g for FT8 "03 46 54 38" which is of course just the size index "03" followed by the ascii bytes for "FT8". Instead, in the type 2 messages I see for example for FT8 "01 7E" in the byte array, 01 being the size index and 7E being the payload, which is the extended ascii code for "~". For each of the modes that I checked I see as the mode designation in type 2 messages: Hi Roger, the Mode field in the Decode (2) message is the one or two character mode (and sync) indicator as shown on the WSJT-X decodes window. ISCAT decodes are rather different from the other modes since ISCAT is basically a stream protocol rather than a block protocol. If you have a specific need to receive ISCAT deocdes via the UDP protocol then that can be sorted out. For JT4 I am not sure why it is not working but again if you have a specific need to receive JT4 decodes it can be sorted out. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Question on Cocumentation of MessageTypes
Hi All, Thanks for the great and always improving software! This is a report being made in case the behavior that I have observed is not what the developers intended. It is not a complaint and it is not a request for any changes to be made in the WJSTX code. I am working with the UDP message facility and v 2.0.0 and all is going well without issues. The "message types" references below relalte to the message types of UDP messages as defined in the document "NetworkMessage.hpp" and have nothing to do with the type designations relating to callsign/compound callsign structure. My question regards the documentation and implementation of the message structure for Type 2 messages asd defined in that document. For the most part, the documentation in NetworkMessage.hpp regarding message structure matches with what I have found. However, in type 2 messages the documentation says that "Mode" is to be sent in UTF8, so I expected to see in type 2 messages what I see sent for Mode in the Type 1 messages, e.g for FT8 "03 46 54 38" which is of course just the size index "03" followed by the ascii bytes for "FT8". Instead, in the type 2 messages I see for example for FT8 "01 7E" in the byte array, 01 being the size index and 7E being the payload, which is the extended ascii code for "~". For each of the modes that I checked I see as the mode designation in type 2 messages: With HF Settings: FT8: 01 7E JT4: - JT9: 01 40 JT65: 01 23 MSK144: 01 26 ISCAT: - QRA64 02 3A 2A With VHF Settings: FT8: 01 7E JT4: - JT9: 01 40 (all submodes, fast and slow) JT65: 02 23 2A (all submodes) MSK144: 01 26 ISCAT: (01 2D) QRA64 02 3A 2A (all submodes) Also, I do not see any evidence of type 2 messages being sent with successful decodes of JT4 or ISCAT messages with HF settings, and have only once seen an ISCAT type 2 message sent with VHF settings, after giving the GUI a heavy workout, and I have not been able to reproduce that condition where I did see an ISCAT type 2 message. As is the case with HF, I never see any type 2 message being sent after successful JT4 decodes. Is all of this (mode designations differing between type 2 and type 3 messages, and the lack of sending of type 2 messages for JT4 and ISCAT decodes) expected and desired behavior? Thanks in advance for the info, and 73, Roger Rehr W3SZ ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Audio dropouts or missing decodes
I have experienced this behavior also. I initially ran FT8 on a old HP 32-bit Pentium computer running Windows 10 and there would be spells where there was a waterfall but Decode would not light up. Then I noticed that this only seemed to happen when Microsoft Edge was also running. I used Task Manager to see what was going on and found that Edge was running in a hog mode where it was using 50% of the CPU time and over 1 Gig of memory. I tested IE and Chrome and found that they could also get into a hog mode doing a lot of something - I don't know what. I wanted to be able to connect to QRZ to do real time logging so I looked for another solution. My solution was to buy a refurbished computer from Walmart for about $135. This was an HP with an Intel Core 2 Duo E8500, 3.16 Ghz, 4 Gb RAM, 64-bits with Windows 10 installed on it. This pretty much fixed the problem, but I did have an episode last week, but I knew that to fix the problem I only needed to close Edge and then restart it and everything would be fine again. 73, Roy, W7IDM On Wed, Feb 6, 2019 at 7:27 AM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Wireless is not a good choice for SDRs via ethernetnot surprised you > have problems. > > Can you try your Pro 5 with a USB network adapter and see if behaves on a > wired connection to your LAN? > > And are you running SmartSDR with 48kHz sampling? Or you doing something > higher than that? > > de Mike W9MDB > > > > > On Wednesday, February 6, 2019, 8:11:47 AM CST, Bill Barrett < > w2pky...@gmail.com> wrote: > > > Hello Mike- > I have the FLEX 6700 on a small dedicated LAN with Win7 Pro I7 computer > and wireless router that works just fine. > I also have a Surface Pro 5 running Win10 Pro that can access the 6700 > through FLEX DAX & CAT apps over the wireless LAN. > Recently started DAX, CAT and WSJT-X 2.0.0 on the SP 5, saw activity on > DAX Panel and WSJT-X volume monitor but no decodes. > The short of it, turned on "Listen" in the Sound > Recording > DAX Audio > channel 1 and heard total distortion and dropouts. > Rebooted the SP5 and audio cleared up but occasionally there would be > multiple 1 second dropouts [3 or 4 in a row]. > Had Process Hacker running and AUDIODG.exe would be the top CPU process > when the dropouts occurred. > Normally DAX is the top CPU process followed by AUDIODG.exe. > Noted even when the priority of DAX and AUDIODG.exe were elevated to > REALTIME the dropouts still interrupted the audio stream. > There so either AUDIODG.exe is in a loop or something "undiscoverable" is > holding up that process. > Would like to have your test version. > Thanks; > Bill W2PKY > > > > > On Wed, Feb 6, 2019 at 8:17 AM Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > If any of you are seeing one of these symptoms. > > #1 No decodes when signals are present on the waterfall...decode button > will just "flash". This indicates no WAV file was saved. > #2 During decode having to click Enable Tx or such to get decodes to start > working. > #3 Any audio glitches or other behavior that indicates audio problems. > > Please contact me for some testing...been doing a lot of audio testing and > finding different solutions...no one solution seems to be in hand yet. > > But...I've got a test version of WSJT-X that should tell you when you have > audio problems. First step is recognizing you have a problem :-) > > de Mike W9MDB > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Audio dropouts or missing decodes
Wireless is not a good choice for SDRs via ethernetnot surprised you have problems. Can you try your Pro 5 with a USB network adapter and see if behaves on a wired connection to your LAN? And are you running SmartSDR with 48kHz sampling? Or you doing something higher than that? de Mike W9MDB On Wednesday, February 6, 2019, 8:11:47 AM CST, Bill Barrett wrote: Hello Mike-I have the FLEX 6700 on a small dedicated LAN with Win7 Pro I7 computer and wireless router that works just fine.I also have a Surface Pro 5 running Win10 Pro that can access the 6700 through FLEX DAX & CAT apps over the wireless LAN.Recently started DAX, CAT and WSJT-X 2.0.0 on the SP 5, saw activity on DAX Panel and WSJT-X volume monitor but no decodes.The short of it, turned on "Listen" in the Sound > Recording > DAX Audio channel 1 and heard total distortion and dropouts.Rebooted the SP5 and audio cleared up but occasionally there would be multiple 1 second dropouts [3 or 4 in a row].Had Process Hacker running and AUDIODG.exe would be the top CPU process when the dropouts occurred.Normally DAX is the top CPU process followed by AUDIODG.exe.Noted even when the priority of DAX and AUDIODG.exe were elevated to REALTIME the dropouts still interrupted the audio stream.There so either AUDIODG.exe is in a loop or something "undiscoverable" is holding up that process.Would like to have your test version. Thanks;Bill W2PKY On Wed, Feb 6, 2019 at 8:17 AM Black Michael via wsjt-devel wrote: If any of you are seeing one of these symptoms. #1 No decodes when signals are present on the waterfall...decode button will just "flash". This indicates no WAV file was saved.#2 During decode having to click Enable Tx or such to get decodes to start working.#3 Any audio glitches or other behavior that indicates audio problems. Please contact me for some testing...been doing a lot of audio testing and finding different solutions...no one solution seems to be in hand yet. But...I've got a test version of WSJT-X that should tell you when you have audio problems. First step is recognizing you have a problem :-) de Mike W9MDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Audio dropouts or missing decodes
Hello Mike- I have the FLEX 6700 on a small dedicated LAN with Win7 Pro I7 computer and wireless router that works just fine. I also have a Surface Pro 5 running Win10 Pro that can access the 6700 through FLEX DAX & CAT apps over the wireless LAN. Recently started DAX, CAT and WSJT-X 2.0.0 on the SP 5, saw activity on DAX Panel and WSJT-X volume monitor but no decodes. The short of it, turned on "Listen" in the Sound > Recording > DAX Audio channel 1 and heard total distortion and dropouts. Rebooted the SP5 and audio cleared up but occasionally there would be multiple 1 second dropouts [3 or 4 in a row]. Had Process Hacker running and AUDIODG.exe would be the top CPU process when the dropouts occurred. Normally DAX is the top CPU process followed by AUDIODG.exe. Noted even when the priority of DAX and AUDIODG.exe were elevated to REALTIME the dropouts still interrupted the audio stream. There so either AUDIODG.exe is in a loop or something "undiscoverable" is holding up that process. Would like to have your test version. Thanks; Bill W2PKY On Wed, Feb 6, 2019 at 8:17 AM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > If any of you are seeing one of these symptoms. > > #1 No decodes when signals are present on the waterfall...decode button > will just "flash". This indicates no WAV file was saved. > #2 During decode having to click Enable Tx or such to get decodes to start > working. > #3 Any audio glitches or other behavior that indicates audio problems. > > Please contact me for some testing...been doing a lot of audio testing and > finding different solutions...no one solution seems to be in hand yet. > > But...I've got a test version of WSJT-X that should tell you when you have > audio problems. First step is recognizing you have a problem :-) > > de Mike W9MDB > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Audio dropouts or missing decodes
If any of you are seeing one of these symptoms. #1 No decodes when signals are present on the waterfall...decode button will just "flash". This indicates no WAV file was saved.#2 During decode having to click Enable Tx or such to get decodes to start working.#3 Any audio glitches or other behavior that indicates audio problems. Please contact me for some testing...been doing a lot of audio testing and finding different solutions...no one solution seems to be in hand yet. But...I've got a test version of WSJT-X that should tell you when you have audio problems. First step is recognizing you have a problem :-) de Mike W9MDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
