Date   

locked Re: DT Value Question #Timesync

Bill Somerville
 

Hi Reino,

PTT timing does not affect the time synchronization of the message symbols. This should not be a surprise since late started transmissions are often decoded.

73
Bill
G4WJS.

On 07/08/2021 09:10, Reino Talarmo wrote:

Hi Charles,

The DT values is the time difference between transmitted station timing and your PC timing. As Phil said 0.1 s fine for FT8 and FT4. That time delay DT contains all signal processing delays both in the distant transmitter and your receiver. Delays in analog implementations such as in FT1000MP are small, but in digital signal processing that delay, especially at reception, could be hundreds of milliseconds. It cannot be compensated at the same time both in transmitter and receiver.
I don’t know exactly how PTT delay setting in wsjt-x is affecting to that value. Probably it just delays the timeslot, but it could as well just cut the beginning of the timeslot. I should test that, hi!

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Philip Rose via groups.io
Sent: 7. elokuutata 2021 10:04
To: main@WSJTX.groups.io; wsjtx@groups.io
Subject: Re: [WSJTX] DT Value Question #Timesync

 

Charles,

 

I wouldn’t say a DT of 0.1 is a problem. I see other stations within a range of about +/- 0.3 s. As long as the average DT you see is close to 0 you are OK. And yes you are correct DT is the difference between your timing and the other station’s timing.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: Charles Albert
Sent: 07 August 2021 07:29
To: wsjtx@groups.io
Subject: [WSJTX] DT Value Question #Timesync

 

Greetings, all...

 

There was a recent discussion about how important the time sync is and just when to decide not to mess with the clock and such, but there is one question I did not see addressed in that thread, though with the heavy clipping it's more than possible I may have missed it.

 

Isn't the DT value some sort of combination of your station's time and the receiving station's time?

 

I ask because there is one local station here that always reports my DT value as 0.1 no matter what. At first, when I saw this, I would check my system clock. It was typically within 2 ms of the various standards. No other stations were reporting an issue with my DT, and there seemed to be no problems decoding signals in either direction.

 

I came to the conclusion that it is at least as likely that the station reporting me with a DT of 0.1 is (very) slightly off time as it is that I am off sync.

 

Or am I missing something in this analysis?

 

Take Care & 73

de KC6UFM

Charles

 

 


--
73 Phil GM3ZZA



locked Re: DT Value Question #Timesync

Reino Talarmo
 

Hi Charles,

The DT values is the time difference between transmitted station timing and your PC timing. As Phil said 0.1 s fine for FT8 and FT4. That time delay DT contains all signal processing delays both in the distant transmitter and your receiver. Delays in analog implementations such as in FT1000MP are small, but in digital signal processing that delay, especially at reception, could be hundreds of milliseconds. It cannot be compensated at the same time both in transmitter and receiver.
I don’t know exactly how PTT delay setting in wsjt-x is affecting to that value. Probably it just delays the timeslot, but it could as well just cut the beginning of the timeslot. I should test that, hi!

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Philip Rose via groups.io
Sent: 7. elokuutata 2021 10:04
To: main@WSJTX.groups.io; wsjtx@groups.io
Subject: Re: [WSJTX] DT Value Question #Timesync

 

Charles,

 

I wouldn’t say a DT of 0.1 is a problem. I see other stations within a range of about +/- 0.3 s. As long as the average DT you see is close to 0 you are OK. And yes you are correct DT is the difference between your timing and the other station’s timing.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: Charles Albert
Sent: 07 August 2021 07:29
To: wsjtx@groups.io
Subject: [WSJTX] DT Value Question #Timesync

 

Greetings, all...

 

There was a recent discussion about how important the time sync is and just when to decide not to mess with the clock and such, but there is one question I did not see addressed in that thread, though with the heavy clipping it's more than possible I may have missed it.

 

Isn't the DT value some sort of combination of your station's time and the receiving station's time?

 

I ask because there is one local station here that always reports my DT value as 0.1 no matter what. At first, when I saw this, I would check my system clock. It was typically within 2 ms of the various standards. No other stations were reporting an issue with my DT, and there seemed to be no problems decoding signals in either direction.

 

I came to the conclusion that it is at least as likely that the station reporting me with a DT of 0.1 is (very) slightly off time as it is that I am off sync.

 

Or am I missing something in this analysis?

 

Take Care & 73

de KC6UFM

Charles

 

 


--
73 Phil GM3ZZA


locked Re: DT Value Question #Timesync

 

Charles,

 

I wouldn’t say a DT of 0.1 is a problem. I see other stations within a range of about +/- 0.3 s. As long as the average DT you see is close to 0 you are OK. And yes you are correct DT is the difference between your timing and the other station’s timing.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: Charles Albert
Sent: 07 August 2021 07:29
To: wsjtx@groups.io
Subject: [WSJTX] DT Value Question #Timesync

 

Greetings, all...

 

There was a recent discussion about how important the time sync is and just when to decide not to mess with the clock and such, but there is one question I did not see addressed in that thread, though with the heavy clipping it's more than possible I may have missed it.

 

Isn't the DT value some sort of combination of your station's time and the receiving station's time?

 

I ask because there is one local station here that always reports my DT value as 0.1 no matter what. At first, when I saw this, I would check my system clock. It was typically within 2 ms of the various standards. No other stations were reporting an issue with my DT, and there seemed to be no problems decoding signals in either direction.

 

I came to the conclusion that it is at least as likely that the station reporting me with a DT of 0.1 is (very) slightly off time as it is that I am off sync.

 

Or am I missing something in this analysis?

 

Take Care & 73

de KC6UFM

Charles

 

 


--
73 Phil GM3ZZA


locked UDP Server DNS lookup failed on OS X #macOS #wsjt-x-crashing

barry@...
 

Using Time Machine on the Mac, I replaced WSJT-X.ini with the backed up copy from the day before the file was corrupted.  Everything works as before.  

What I was trying to do was to get WSJT-X, GridTracker and MacLoggerDX working together using multicast 224.0.0.1.  GridTracker and WSJT-X were working great but MacLoggerDX was not responding correctly.


locked Rig select menu #WSJTX_config #Yaesu

Lloyd K8DiO <k8dio@...>
 

Hello,  I am trying to help a local ham set up WSJT-X with his FT-991. 
When he goes to Settings/Radio, to select Rig, the drop down menu is "stuck" on None.
Clicking on the small down arrow will not expand the rig selections. Any ideas on why this is happening?
 
Thanks, Lloyd  K8DIO


locked Re: WSJTX on Debian Buster #linux #install

Alan Blind
 

I am running v2.1.2 on. Ubuntu Linux PC.

In my case I used "Synaptic Package Manager" to do the install.  Per the Synaptic information, it knows and installs all the necessary dependencies.

Alan. WA9WUD


locked Hamlib error after power outage #Cat_RigControl

Ken Hagler
 

I was in the middle of using WSJT-X 2.4.0 on MacOS 11.3.1 with a Flex-6400 when there was a brief power outage. After the power came back and I'd restarted everything, I got this error when I tried to launch WSJT-X:

Hamlib error: IO error

network.c(288):network_open return(-6)

iofunc.c(176):port_open return(-6)

rig.c(773):rig_open return(-6) while opening connection to rig

 

Timestamp: 2021-08-06T23:43:15.349Z


Since I'd been in the middle of using the software when the power went out, I suspect that there's some file somewhere that's supposed to be cleaned up when the app quits but didn't in this case. However, I couldn't figure out where it might be. Moving the WSJT-X folder out of Application Support didn't help.

Does anyone have any idea what I need to do to clear out this state?


locked OS X: Multiple errors when trying to open WSJT #macOS

george.j.white@...
 

WSJT had been running well, but suddenly I received two error messages when opening, or trying to open, the program:
1. "Sub process error. Failed to close jt9 process." I got rid of this (temporarily) by using Activity Monitor to halt the jt9 process.
2. "Unable to send a message to UDP server 224.0.0.1:2237." I edited out 2237 in wsjtx.ini to no avail. Unable to get to "Preferences" in WSJT interface due to continuous stream of error messages.

When I close our the program and re-open it I receive error message 1. I'm at a standstill, any help will be greatly appreciated.

Thanks.


locked #NewUser #raspberryPi #WSPR #NewUser #raspberryPi #WSPR

Lynn Mears
 

I’m a new user.  I’ve successfully logged WSPR receptions using a SDR with a windows server class machine.  I’m interested in setting up a dedicated multi-band WSPR transceiver that uses something smaller than my windows machine. was thinking something like a raspberry Pi with a home brew receiver and transmitter.  I haven’t used a 
raspberry before so I don’t know if it that has any limitations I should be aware of.  Also, without a CAT controlled rig, is there an easy way for the band switching to take place?  I see that WSJT will run scripts, but the documentation also, says they are run after the CAT is successfully executed.  

For a transmitter I may use the QRP labs US3 to leverage the firmware but may do it from scratch.  I’m an EE and done lots or programming so not afraid to take things on. 

Any thoughts on good ways to proceed would be most appreciated!

Thanks in advance!
Lynn, WA4FKX 


locked DT Value Question #Timesync

Charles Albert
 

Greetings, all...
 
There was a recent discussion about how important the time sync is and just when to decide not to mess with the clock and such, but there is one question I did not see addressed in that thread, though with the heavy clipping it's more than possible I may have missed it.
 
Isn't the DT value some sort of combination of your station's time and the receiving station's time?
 
I ask because there is one local station here that always reports my DT value as 0.1 no matter what. At first, when I saw this, I would check my system clock. It was typically within 2 ms of the various standards. No other stations were reporting an issue with my DT, and there seemed to be no problems decoding signals in either direction.
 
I came to the conclusion that it is at least as likely that the station reporting me with a DT of 0.1 is (very) slightly off time as it is that I am off sync.
 
Or am I missing something in this analysis?
 
Take Care & 73
de KC6UFM
Charles
 


locked Re: UDP Server DNS lookup failed on OS X #macOS #wsjt-x-crashing

Bill Somerville
 

On 06/08/2021 07:06, barry@... wrote:
I changed the UDP address from 127.0.0.1 to multicast 224.0.0.1:2237 in the Preferences.
A DNS lookup failed occurs and a popup window is display showing "UDP server DNS lookup failed" and "Network Error".
Preferences is greyed out so I cannot correct the error.
The only thing that can be done is to select "Cancel" on the popup and the program shuts down.

How can I correct this mistake?
Barry,

that field expects a host name or IP address, the port number is in the port spin box below.

The Preferences menu option is disabled because you already have the Preferences open. Just go back to the Preferences dialog and remove the :2237 from the address entry.

73
Bill
G4WJS.


locked Re: #Kenwood #Cat_RigControl #Kenwood #Cat_RigControl

Bill Somerville
 

On 06/08/2021 22:08, Chris wrote:
v 2.4.0
A few months back, WSJT-X stopped controlling my Kenwood TS-450. I didn't have time or patience to trouble shoot at that time.  Now I'm ready to dive into it.

First, I believe this is a problem with the Kenwood library, because the program continues to work fine with my Yaesu FT-817. Also the error message indicates this. Another program (Mixw-4) using the same com ports is able to control the Kenwood fine.

The big mystery is why, when it once worked fine with the Kenwood, it stopped working suddenly.

What I have tried:

Re-installing (more than once)
Trying different com ports (because I had an issue with enumeration of the sound card once before)
Clearing and re configuring the settings.
Refreshing windows 10 with a repair upgrade.

None of this worked.  I could use a hint from someone who really understands how the rig library works and how one can fix or update it.

Chris, AB6QK
Chris,

if you have an issue with an error message from WSJT-X then perhaps you should share that error message with us here. Please include the details as that is where the important diagnostic information is.

73
Bill
G4WJS.


locked Re: UDP Server DNS lookup failed on OS X #macOS #wsjt-x-crashing

Karza
 

Barry,

The file you're looking for is ~/Library/Preferences/WSJT-X.ini,
see https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.4.0.html#_file_locations

73's de Kari, oh2gqc


locked Re: #Kenwood #Cat_RigControl #Kenwood #Cat_RigControl

neil_zampella
 

You can't compare another program with WSJT-X unless its using Hamlib as the interface.   Reinstalling the program doesn't solve anything as this appears to be an configuration issue.

You talk about 'controlling' the rig, but then you mention sound cards, which have nothing to do with it.

Please let us know what you're using to interface the rig with computer for CAT control (if any) and how are you connecting for audio.

Neil, KN3iLZ

On 8/6/2021 4:08 PM, Chris wrote:
v 2.4.0
A few months back, WSJT-X stopped controlling my Kenwood TS-450.  I didn't have time or patience to trouble shoot at that time.  Now I'm ready to dive into it.

First, I believe this is a problem with the Kenwood library, because the program continues to work fine with my Yaesu FT-817.  Also the error message indicates this. Another program (Mixw-4) using the same com ports is able to control the Kenwood fine. 

The big mystery is why, when it once worked fine with the Kenwood, it stopped working suddenly.

What I have tried:

Re-installing (more than once)
Trying different com ports (because I had an issue with enumeration of the sound card once before)
Clearing and re configuring the settings.
Refreshing windows 10 with a repair upgrade.

None of this worked.  I could use a hint from someone who really understands how the rig library works and how one can fix or update it.

Chris, AB6QK



locked #Kenwood #Cat_RigControl #Kenwood #Cat_RigControl

Chris
 

v 2.4.0
A few months back, WSJT-X stopped controlling my Kenwood TS-450.  I didn't have time or patience to trouble shoot at that time.  Now I'm ready to dive into it.

First, I believe this is a problem with the Kenwood library, because the program continues to work fine with my Yaesu FT-817.  Also the error message indicates this. Another program (Mixw-4) using the same com ports is able to control the Kenwood fine. 

The big mystery is why, when it once worked fine with the Kenwood, it stopped working suddenly.

What I have tried:

Re-installing (more than once)
Trying different com ports (because I had an issue with enumeration of the sound card once before)
Clearing and re configuring the settings.
Refreshing windows 10 with a repair upgrade.

None of this worked.  I could use a hint from someone who really understands how the rig library works and how one can fix or update it.

Chris, AB6QK


locked WSJTX on Debian Buster #linux #install

Rick Hatton <71topaz@...>
 

Does anyone know of a wsjtx version >=2.1 that will cleanly install on a fully updated Buster distro? I also have the buster-backports repository enabled. I keep getting dependency errors.

wsjtx depends on libc6 (>= 2.29); however:
  Version of libc6:amd64 on system is 2.28-10.
 wsjtx depends on libgcc-s1 (>= 4.0); however:
  Package libgcc-s1 is not installed.
 wsjtx depends on libreadline8 (>= 6.0); however:
  Package libreadline8 is not installed.
 wsjtx depends on libstdc++6 (>= 9); however:
  Version of libstdc++6:amd64 on system is 8.3.0-6.

The highest version available are:
libc6 2.28
libgcc-s1 - not available
libreadline7
libstdc8

Thanks


locked Re: UDP Server DNS lookup failed on OS X #macOS #wsjt-x-crashing

Colin
 

Hi Barry,

You can find it in the %localappdata%\WSJT-X folder

WSJT-X.ini

has all the settings.

Be sure to quit out before editing. Also you might want to use notepad++ or notepad to carefully edit.

Good luck OM.

73 de Colin VE3MSC

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of barry@...
Sent: August 6, 2021 11:58
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] UDP Server DNS lookup failed on OS X #mac #wsjt-x-crashing

 

That's the PROBLEM - The "Preferences" selection under WSJT-X is greyed out.  I have no way of removing the port number from the address.
There needs to be a file that I can erase to allow the program to not quit and allow access to Preferences.

Barry K6ZGW


locked Re: A glitch in WSJT-X #wsjt-x #IssueReport #mainscreen

Dave Garber
 

its been that way as long as I remember.  only jtdx erases left windows first

Dave Garber
VE3WEJ / VE3IE


On Fri, Aug 6, 2021 at 7:05 AM Bobby Chandler <n4au@...> wrote:
JR,

Either hit ERASE twice, or right click in the box and hit ERASE.

Bobby/N4AU

--
n4au@...
   n4au@...





locked Re: UDP Server DNS lookup failed on OS X #macOS #wsjt-x-crashing

barry@...
 

That's the PROBLEM - The "Preferences" selection under WSJT-X is greyed out.  I have no way of removing the port number from the address.
There needs to be a file that I can erase to allow the program to not quit and allow access to Preferences.

Barry K6ZGW


locked Re: UDP Server DNS lookup failed on OS X #macOS #wsjt-x-crashing

Colin
 

Likely it is interpreting that string as a host name, not as an IP address.

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of barry@...
Sent: August 6, 2021 02:06
To: main@WSJTX.groups.io
Subject: [WSJTX] UDP Server DNS lookup failed on OS X #mac #wsjt-x-crashing

 

I changed the UDP address from 127.0.0.1 to multicast 224.0.0.1:2237 in the Preferences.
A DNS lookup failed occurs and a popup window is display showing "UDP server DNS lookup failed" and "Network Error".
Preferences is greyed out so I cannot correct the error.
The only thing that can be done is to select "Cancel" on the popup and the program shuts down.  

How can I correct this mistake?

8101 - 8120 of 35492