Date   

locked Re: DT Value Question #Timesync

Bill Somerville
 

Hi Willie,

for a transmitting and receiving pair, both with accurate clocks and analog transceivers, around 100 mS DT values are normal. The delay is a combination of audio buffer latencies at each end plus DSP processing time at the Rx end, and a small contribution from propagation delay. Using SDRs will increase the delay, although the current crop of direct sampling SDR transceivers usually have quite low latencies.

73
Bill
G4WJS.

On 07/08/2021 11:21, William Smith wrote:
Whenever I run my histogram program I find the peak at 0.1s, but I figure it’s just one of those things. 🤷‍♂️

73, Willie N1JBJ


On Aug 7, 2021, at 6:18 AM, Bill Somerville <g4wjs@...> wrote:


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: Hamlib error after power outage #Cat_RigControl

Bill Somerville
 

On 07/08/2021 00:45, Ken Hagler wrote:
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?
Hi Ken,

I suspect the problem is upstream of WSJT-X. What "Settings->Radio" options do you use?

73
Bill
G4WJS.


locked Re: Rig select menu #WSJTX_config #Yaesu

Lloyd K8DiO <k8dio@...>
 

Hi Bill,

I'll check with him and get back to you.
Thanks for your email.

73, Lloyd K8DiO

-----Original Message-----
From: Bill Somerville
Sent: Saturday, August 07, 2021 6:22 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Rig select menu #WSJTX_config #Yaesu

On 07/08/2021 01:44, Lloyd K8DiO wrote:
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
Hi Lloyd,

no one else has reported that issue. What operating system and operating
system version is WSJT-X being run on?

73
Bill
G4WJS.


locked Re: Rig select menu #WSJTX_config #Yaesu

Bill Somerville
 

On 07/08/2021 01:44, Lloyd K8DiO wrote:
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
Hi Lloyd,

no one else has reported that issue. What operating system and operating system version is WSJT-X being run on?

73
Bill
G4WJS.


locked Re: DT Value Question #Timesync

William Smith
 

Whenever I run my histogram program I find the peak at 0.1s, but I figure it’s just one of those things. 🤷‍♂️

73, Willie N1JBJ


On Aug 7, 2021, at 6:18 AM, Bill Somerville <g4wjs@...> wrote:


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

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

9641 - 9660 of 37037