Date   

locked Re: WSJT-X upgrade to v2.5.3 #hamlib

Pierre FK8IH <jb.gallauziaux@...>
 

I'm using Windows 11 with Quisk v4.1.93 and Hermes Lite 2 SDR TCVR with hamlib-w64-4.4.

WSJT-X v2.4.0 worked well and synchronized with Quisk in less than 1 second when initially started and less than 1 second when changing band and frequency.
WSJT-X v2.5.2 takes 15 second to synchronize with Quisk when initially started and then less than 1 second when changing band and frequency, the "?" indicator turns green.
WSJT-X v2.5.3 and 2.5.4 do not synchronize with Quisk using the same hamlib and CAT parameters, The "?" indicator right to the band selector turns orange/red and in the "settings" menu the "Test CAT" button turns RED when actuated.

I already posted twice explaining that. Some members suggested to replace the libhamlib-4.dll file in the program Bin folder, which I did without success, the reason why I reverted to v2.5.2 after testing 2.5.3 and 2.5.4.
73 - Pierre - FK8IH


locked Re: JT65 Submodes in WSJT-X v2.5.4 #JT65

Chet.KG4IYS
 

Try going to settings in wsjtx, select vhf and submodes. That may solve the problem.

73...Chet, KG4IYS

-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Stan Edwards - WA4DYD
Sent: Wednesday, January 5, 2022 5:10 PM
To: main@WSJTX.groups.io
Subject: [WSJTX] JT65 Submodes in WSJT-X v2.5.4 #JT65

I wanted to try and monitor EME activity and just tried to set up receiving for JT65B in WSJT-X v2.5.4. When I select the JT65 mode "JT65" displayed in the mode indicator window but the additional menu to select the submodes did not appear. Am I missing something? According to the on-line manual, it seems that should pop adjacent to the Tx/Rx frequency boxes, but nothing is there and I cannot locate another way to select a submode.

Thanks for the help.

Stan Edwards, WA4DYD


locked JT65 Submodes in WSJT-X v2.5.4 #JT65

Stan Edwards - WA4DYD
 

I wanted to try and monitor EME activity and just tried to set up receiving for JT65B in WSJT-X v2.5.4. When I select the JT65 mode "JT65" displayed in the mode indicator window but the additional menu to select the submodes did not appear. Am I missing something? According to the on-line manual, it seems that should pop adjacent to the Tx/Rx frequency boxes, but nothing is there and I cannot locate another way to select a submode.

Thanks for the help.

Stan Edwards, WA4DYD


locked Re: Something new ? #QSO_practices

Michael Black
 

I've not noticed that.  But at -22 you might lose the message.
Some will send RR73 and not send anything else unless they get another report message.But if you don't see that message and they don't see your 2nd report they may think it's over.You would have to ask one of your QSO partners to ask what they saw.
Mike W9MDB

On Wednesday, January 5, 2022, 03:48:48 PM CST, n4qwf . <n4qwf1@...> wrote:

I have noticed lately that some of the stations I work do not confirm the QSO. I don't know if this is becoming a common practice but it is not a good idea. The software is set up to auto-log when it sees confirmation. i.ie RR73 or 73. I can understand not getting the final response from a -22 station but when the reports are plus in both directions I have to wonder what gives. Is there something in the operating practices to speed up things that I have no heard of? Anyone else notice this of late?

73<<John


locked Something new ? #QSO_practices

n4qwf .
 

I have noticed lately that some of the stations I work do not confirm the QSO. I don't know if this is becoming a common practice but it is not a good idea. The software is set up to auto-log when it sees confirmation. i.ie RR73 or 73. I can understand not getting the final response from a -22 station but when the reports are plus in both directions I have to wonder what gives. Is there something in the operating practices to speed up things that I have no heard of? Anyone else notice this of late?

73<<John


locked Re: UDP datagram parsing/format #decode

Tom M0LTE
 

Hi Joe

Look for NetworkMessage.hpp in the source tree. The comments explain the
structure.

The issue is that the data is packed according to Qt internals. Fine if
you’re using Qt at the other end, but for the rest of us, a little
inconvenient.

Personally, I’ve open sourced a .NET library for this job. You may use it
or port some of its contents to a language of your choice.

https://github.com/M0LTE/WsjtxUdpLib

Cheers
Tom

On Wed, 5 Jan 2022 at 16:47, Joe <radio.wq6q@...> wrote:

Can someone point me at the documentation that shows how to parse the UDP
datagrams that WSJT-X sends for each line in the Band Activity window (and
any others that it may send)?

thanks in advance!

Joe/WQ6Q






locked Re: UDP datagram parsing/format #decode

Sam Birnbaum
 

Hi,
Here is a link to the UDP messages 
WSJT / WSJT-X / [d28164] /Network/NetworkMessage.hpp
73,

Sam W2JDB

-----Original Message-----
From: Joe <radio.wq6q@...>
To: main@WSJTX.groups.io
Sent: Wed, Jan 5, 2022 11:47 am
Subject: [WSJTX] UDP datagram parsing/format #decode

Can someone point me at the documentation that shows how to parse the UDP datagrams that WSJT-X sends for each line in the Band Activity window (and any others that it may send)?

thanks in advance!

Joe/WQ6Q


locked UDP datagram parsing/format #decode

Joe
 

Can someone point me at the documentation that shows how to parse the UDP datagrams that WSJT-X sends for each line in the Band Activity window (and any others that it may send)?

thanks in advance!

Joe/WQ6Q


locked Italian interface translation.. #mainscreen #TechnicalHelpQuestion

Bruno
 

I think I could help in the translation for italian language.. "Hold Tx Freq" has a wrong translation. It should be " Mantenere Tx Freq"..
Thank you, and HNY
Bruno i3RGH


locked Re: #MSK144 Decoder action #MSK144

steve_k9an
 

Hi Andy,

When interpreting your results, keep in mind that the MSK144 decoder incorporates dupe suppression. Within a Rx interval, a decoded message will be printed only if it's SNR is larger than the previous decode with the same message. For example, in your 10:46:55 interval, the second "G4JNT TESTING" decode was printed because the SNR of +1 dB was larger than the first decode with SNR 0 dB. The same goes for the "TLM DATA ..." decodes within the 10:47:05 interval. Also keep in mind that AGC action in your receiver could cause such SNR variation, especially at the beginning of a transmission when AGC transient response is in play.

73 Steve k9an


locked Re: Wsjt-x no transmit #Windows10

Michael Black
 

How is your PTT set up?
What audio device are you using?
Can you show your rig settings?
Mike W9MDB

On Wednesday, January 5, 2022, 07:12:16 AM CST, jokavilson@... <jokavilson@...> wrote:

Good morning I have a problem I changed from windows 7 to windows 10, in windows 7 I received normal TX I requested the station the same received my signal and we closed the contact but now I receive TX I click on the wsjt-x station sends signal to the radio, but the station I don't receive any signal (I just listen, I don't transmit) my radio Icom 718 I use a cable for Ham Radio Deluxe, and a cable for digital mode wsjt-x asks anyone already gone through this situation.


locked Wsjt-x no transmit #Windows10

jokavilson@...
 

Good morning I have a problem I changed from windows 7 to windows 10, in windows 7 I received normal TX I requested the station the same received my signal and we closed the contact but now I receive TX I click on the wsjt-x station sends signal to the radio, but the station I don't receive any signal (I just listen, I don't transmit) my radio Icom 718 I use a cable for Ham Radio Deluxe, and a cable for digital mode wsjt-x asks anyone already gone through this situation.


locked Re: FT8 Low Signal Reports #FT8

John VK6FD
 

On Wed, Jan 5, 2022 at 06:13 PM, Pietro Molina wrote:


Did you try to route audio output to the default audio device to check if tone
is pure?
And, if it is good, try to connect a headphone instead of the radio to check
if audio output is clean.

Pietro I2OIM
Good idea Pietro.


locked Re: FT8 Low Signal Reports #FT8

John VK6FD
 

On Wed, Jan 5, 2022 at 09:09 AM, Jim Brown wrote:

I've not followed this thread, but the obvious question -- Into what
antenna? What feedline? What's the SWR in bypass mode?

I never take FT8 signal reports seriously, because as others have noted,
it's signal to noise ratio. My QTH is relatively quiet most of the time
on most bands, I run legal limit on 160M, 60M, and 6M, (the only bands
where I run FT8). In all cases, my objective is to work difficult paths
-- EU from NorCal on 160 and 60, double and triple hop Es on 6M. And I
regularly receive signal reports 10-15dB weaker than what I give.
Considering that I get mostly stateside responses to CQs on 160 and 60,
that strongly suggests that most hams live where they can't hear.

73, Jim K9YC
Jim, I use inverted V dipoles for HF 80m, 40m & 20m and a 5 element LFA for 6m. All have very good SWRs, 1.1 or less. I use iCom7610 barefoot.


locked Re: FT8 Low Signal Reports #FT8

Mike GM3PPE
 

John, I live in a very quiet location in the Scottish Borders and I find the same 10 to 15dB difference in signal reports. I have spoken to other stations in rural locations, and they find the same. As many have said, it all to do with local S/N ratio. Occasionally I will work another station, also in a quiet location, and we give each other similar reports!

73, Mike GM3PPE


locked Re: FT8 Low Signal Reports #FT8

Pietro Molina
 

Did you try to route audio output to the default audio device to check if tone is pure?
And, if it is good, try to connect a headphone instead of the radio to check if audio output is clean.

Pietro I2OIM


locked Re: WSJT-X upgrade to v2.5.3 #hamlib

neil_zampella
 

What rig are you running? What are you using for an operating system? How are you connected for CAT control ?

Just saying "I have the same problem" really doesn't tell us much.

Neil, KN3ILZ


locked Re: WSJT-X upgrade to v2.5.3 #hamlib

Pierre FK8IH <jb.gallauziaux@...>
 

I had the same problem with v2.5.4 and returned to v2.5.2
73 - Pierre - FK8IH


locked Re: FT8 Low Signal Reports #FT8

Jim Brown
 

On 1/4/2022 1:53 PM, John wrote:
As I mentioned, an external SWR confirms 100w going up the mast.
I've not followed this thread, but the obvious question -- Into what antenna? What feedline? What's the SWR in bypass mode?

I never take FT8 signal reports seriously, because as others have noted, it's signal to noise ratio. My QTH is relatively quiet most of the time on most bands, I run legal limit on 160M, 60M, and 6M, (the only bands where I run FT8). In all cases, my objective is to work difficult paths -- EU from NorCal on 160 and 60, double and triple hop Es on 6M. And I regularly receive signal reports 10-15dB weaker than what I give. Considering that I get mostly stateside responses to CQs on 160 and 60, that strongly suggests that most hams live where they can't hear.

73, Jim K9YC


locked Re: WSJTX bug with K3 #WSJTX_config

Ron / W4MMP
 

Hello,

My set up is reporting Kenwood warnings.  It is the same repeating warning.

[RIGCTRL][2022-01-05 00:51:49.521545][00:12:00.337522][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:51:50.525580][00:12:01.340960][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:51:51.531626][00:12:02.347819][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:51:52.526868][00:12:03.342460][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:51:53.536263][00:12:04.351840][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:51:54.529231][00:12:05.344543][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:51:55.537283][00:12:06.353164][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:51:56.527217][00:12:07.342622][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:51:57.532347][00:12:08.347429][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:51:58.521293][00:12:09.336979][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:51:59.515247][00:12:10.330539][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:52:00.537629][00:12:11.353241][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:52:01.532469][00:12:12.347874][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:52:02.528483][00:12:13.343352][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:52:03.537503][00:12:14.352974][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:52:04.517561][00:12:15.332655][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:52:05.526484][00:12:16.341199][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None
[RIGCTRL][2022-01-05 00:52:06.517934][00:12:17.332871][warning]
kenwood_get_split_vfo_if(1583): unknown rxVFO=None

The warning is not effecting operations, simply growing the log file.


Windows 10 (home)
WSJT-X v2.5.4

73,
Ron / W4MMP

On 1/4/2022 18:55, alanbh@... wrote:
Version ver 2.4 to version now 2.5.2 prducing the below lines in the syslog.log The problem has increased dramatically. As far as Elecraft using the Kenwood command set I don't know. The syslog.log was never created in versions 2.2.2 and back. A syslog.log creation indicates something is not correct per WSJTx site.
Below is an example of my club call on one of the comouters. All call signs are doing the same thing. It appears to be a same gorup of lines being repeated over and over.
The below set of lines is now being produced after the syslog.log has been deleted from the AppData/Local etc folder. This is a fresh created syslog.log on the next start up!

[SYSLOG][2022-01-03 04:03:42.029358][00:00:00.001639][info] Log Start
[SYSLOG][2022-01-03 04:03:42.029358][00:00:00.001798][info] WSJT-X - K3PAX v2.5.2 68dc11 by K1JT, G4WJS, K9AN, and IV3NWV - Program startup
[SYSLOG][2022-01-03 04:03:42.044984][00:00:00.015609][info] locale: language: English script: Latin country: United States ui-languages: en-US
[SYSLOG][2022-01-03 04:03:42.044984][00:00:00.016106][info] Loaded Qt translations for current locale from resources
[SYSLOG][2022-01-03 04:03:42.044984][00:00:00.016190][info] Loaded WSJT-X base translation file from :/Translations based on language en
[SYSLOG][2022-01-03 04:03:42.044984][00:00:00.016303][info] Loaded WSJT-X translations for current locale from resources
[SYSLOG][2022-01-03 04:03:42.091858][00:00:00.066014][info] shmem size: 48275456
[RIGCTRL][2022-01-03 04:03:42.138736][00:00:00.110989][info] Hamlib version: Hamlib 4.4~git Wed Nov 03 20:00:38 2021 +0000 SHA=e75306
[RIGCTRL][2022-01-03 04:03:45.197538][00:00:03.163775][warning] serial_flush: flush string:IF00007047500 -000000 0002000011 ;IF00007047500 -000000 0002000011 ;
[RIGCTRL][2022-01-03 04:03:45.282184][00:00:03.249520][error] kenwood_transaction: wrong reply IF for command K2
[RIGCTRL][2022-01-03 04:03:45.282184][00:00:03.249552][error] kenwood_transaction: retry_read=0, rs->rigport.retry=5
[RIGCTRL][2022-01-03 04:03:45.313435][00:00:03.279769][error] kenwood_transaction: wrong reply K2 for command K3
[RIGCTRL][2022-01-03 04:03:45.313435][00:00:03.279799][error] kenwood_transaction: retry_read=0, rs->rigport.retry=5
[RIGCTRL][2022-01-03 04:03:45.344684][00:00:03.311022][error] kenwood_transaction: wrong reply K3 for command RV
[RIGCTRL][2022-01-03 04:03:45.344684][00:00:03.311051][error] kenwood_transaction: retry_read=0, rs->rigport.retry=5
[RIGCTRL][2022-01-03 04:03:45.382456][00:00:03.348863][error] kenwood_transaction: Command is not correctly terminated 'RVM05.'
[RIGCTRL][2022-01-03 04:03:45.398083][00:00:03.364184][warning] serial_flush: flush string:67;
[RIGCTRL][2022-01-03 04:03:45.413706][00:00:03.379815][warning] serial_flush: flush string:AI2;
[RIGCTRL][2022-01-03 04:03:45.498355][00:00:03.464473][warning] serial_flush: flush string:IF00007047500 -000000 0002000011 ;
[RIGCTRL][2022-01-03 04:03:46.748470][00:00:04.714531][warning] serial_flush: flush string:IF00007047500 -000000 0002000011 ;IF00007047500 -000000 0002000011

7141 - 7160 of 38088