1. WSJTX | Main
  2. Topics

Locked Meinberg Error #Timesync

Ron
 

Hello all:
I'm a longtime WSJT-X user.

Now I'm setting up WSJT-X on a Windows 10 machine connected to a new ICOM 7300.

The USB connection to the PC and WSJT-X seems to be working fine.

I installed Meinberg NTP, and that's when I ran into problems.

After doing the install, when I click the Finish button, Meinberg tries to connect to an NTP server (other than choosing United States from the drop-down during the install, I let everything else default).

Then it throws the following error:

"It looks like starting the service was not successful. Please check your event log."

When I check the event log, it says:

"unable to bind to wildcard address 0.0.0.0 - another process may be running. "

This lead me to believe that another process or program may be running and using ip address 0.0.0.0.

I immediately thought of windows time, however, I checked it, and it is fully disabled.

I also checked all the TCP & UDP ports and looked for any program that was using port 0.0.0.0 & came up with nothing

Been scratching my head all night on this one.

Figured it was time to call in the cavalry.

Any help would be appreciated.

Ron - KJ5XX
Bob K4RCG
 

I had the same problem; could never get it resolved despite significant
effort to discover the cause. Also, after a Win 10 update my Dimension 4
stopped working as well with similar error and lack of resolution. Gave up
and now use BKT Time Sync. Works a treat. Installed easily and is
consistent.

73 de Bob K4RCG

On Tue, May 31, 2022 at 16:09 Ron <ron@...> wrote:

Hello all:
I'm a longtime WSJT-X user.

Now I'm setting up WSJT-X on a Windows 10 machine connected to a new ICOM
7300.

The USB connection to the PC and WSJT-X seems to be working fine.

I installed Meinberg NTP, and that's when I ran into problems.

After doing the install, when I click the Finish button, Meinberg tries to
connect to an NTP server (other than choosing United States from the
drop-down during the install, I let everything else default).

Then it throws the following error:

"It looks like starting the service was not successful. Please check your
event log."

When I check the event log, it says:

"unable to bind to wildcard address 0.0.0.0 - another process may be
running. "

This lead me to believe that another process or program may be running and
using ip address 0.0.0.0.

I immediately thought of windows time, however, I checked it, and it is
fully disabled.

I also checked all the TCP & UDP ports and looked for any program that was
using port 0.0.0.0 & came up with nothing

Been scratching my head all night on this one.

Figured it was time to call in the cavalry.

Any help would be appreciated.

Ron - KJ5XX
Jim Bacher - WB8VSU
 

Ron, I suspect your firewall is blocking it.

⁣Jim Bacher, WB8VSU
wb8vsu@...
https:\\trc.guru​

On May 31, 2022, 4:09 PM, at 4:09 PM, Ron <ron@...> wrote:
Hello all:
I'm a longtime WSJT-X user.

Now I'm setting up WSJT-X on a Windows 10 machine connected to a new
ICOM 7300.

The USB connection to the PC and WSJT-X seems to be working fine.

I installed Meinberg NTP, and that's when I ran into problems.

After doing the install, when I click the Finish button, Meinberg tries
to connect to an NTP server (other than choosing United States from the
drop-down during the install, I let everything else default).

Then it throws the following error:

"It looks like starting the service was not successful. Please check
your event log."

When I check the event log, it says:

"unable to bind to wildcard address 0.0.0.0 - another process may be
running. "

This lead me to believe that another process or program may be running
and using ip address 0.0.0.0.

I immediately thought of windows time, however, I checked it, and it is
fully disabled.

I also checked all the TCP & UDP ports and looked for any program that
was using port 0.0.0.0 & came up with nothing

Been scratching my head all night on this one.

Figured it was time to call in the cavalry.

Any help would be appreciated.

Ron - KJ5XX
Ron
 

Thanks Bob. That is precisely what happened in my case.

Dim4 was running just fine, no issues at all, until it wasn't. I suspected
a Windows update was the culprit.

So I thought "well, everyone seems to like Meinberg", but as I said, no
joy.

I'm going to try a bit longer to hunt down the gremlin that is causing this
problem, but not much longer.

I'll check out BKT Time Sync.

Thanks!

Ron - KJ5XX

On Tue, May 31, 2022, 3:33 PM Bob K4RCG <bobstohlman@...> wrote:

I had the same problem; could never get it resolved despite significant
effort to discover the cause. Also, after a Win 10 update my Dimension 4
stopped working as well with similar error and lack of resolution. Gave up
and now use BKT Time Sync. Works a treat. Installed easily and is
consistent.

73 de Bob K4RCG

On Tue, May 31, 2022 at 16:09 Ron <ron@...> wrote:

Hello all:
I'm a longtime WSJT-X user.

Now I'm setting up WSJT-X on a Windows 10 machine connected to a new ICOM
7300.

The USB connection to the PC and WSJT-X seems to be working fine.

I installed Meinberg NTP, and that's when I ran into problems.

After doing the install, when I click the Finish button, Meinberg tries
to
connect to an NTP server (other than choosing United States from the
drop-down during the install, I let everything else default).

Then it throws the following error:

"It looks like starting the service was not successful. Please check your
event log."

When I check the event log, it says:

"unable to bind to wildcard address 0.0.0.0 - another process may be
running. "

This lead me to believe that another process or program may be running
and
using ip address 0.0.0.0.

I immediately thought of windows time, however, I checked it, and it is
fully disabled.

I also checked all the TCP & UDP ports and looked for any program that
was
using port 0.0.0.0 & came up with nothing

Been scratching my head all night on this one.

Figured it was time to call in the cavalry.

Any help would be appreciated.

Ron - KJ5XX
Bob K4RCG
 

GA Ron, HIHI EXACT same sequence of events and thinking! I finally gave up
and a helpful mate here on the forums recommended BKT….I took the advice
and never looked back. Solid performance.

73
Bob K4RCG

On Tue, May 31, 2022 at 17:07 Ron <ron@...> wrote:

Thanks Bob. That is precisely what happened in my case.

Dim4 was running just fine, no issues at all, until it wasn't. I suspected
a Windows update was the culprit.

So I thought "well, everyone seems to like Meinberg", but as I said, no
joy.

I'm going to try a bit longer to hunt down the gremlin that is causing this
problem, but not much longer.

I'll check out BKT Time Sync.

Thanks!

Ron - KJ5XX

On Tue, May 31, 2022, 3:33 PM Bob K4RCG <bobstohlman@...> wrote:

I had the same problem; could never get it resolved despite significant
effort to discover the cause. Also, after a Win 10 update my Dimension
4
stopped working as well with similar error and lack of resolution. Gave
up
and now use BKT Time Sync. Works a treat. Installed easily and is
consistent.

73 de Bob K4RCG

On Tue, May 31, 2022 at 16:09 Ron <ron@...> wrote:

Hello all:
I'm a longtime WSJT-X user.

Now I'm setting up WSJT-X on a Windows 10 machine connected to a new
ICOM
7300.

The USB connection to the PC and WSJT-X seems to be working fine.

I installed Meinberg NTP, and that's when I ran into problems.

After doing the install, when I click the Finish button, Meinberg tries
to
connect to an NTP server (other than choosing United States from the
drop-down during the install, I let everything else default).

Then it throws the following error:

"It looks like starting the service was not successful. Please check
your
event log."

When I check the event log, it says:

"unable to bind to wildcard address 0.0.0.0 - another process may be
running. "

This lead me to believe that another process or program may be running
and
using ip address 0.0.0.0.

I immediately thought of windows time, however, I checked it, and it is
fully disabled.

I also checked all the TCP & UDP ports and looked for any program that
was
using port 0.0.0.0 & came up with nothing

Been scratching my head all night on this one.

Figured it was time to call in the cavalry.

Any help would be appreciated.

Ron - KJ5XX
Dave KD2SGM
 

Ron,

Did you try stopping and restarting the NTP service in Administrator mode? Sometimes that will help. I run Meinberg and Win10 with no conflicts. I realize ymmv.

Good Luck,
Dave, KD2SGM
Ron
 

No, I've checked that as well. I setup Meinberg to have full access
through the Windows firewall.

Ron - KJ5XX

On Tue, May 31, 2022, 3:51 PM Jim Bacher - WB8VSU <wb8vsu@...> wrote:

Ron, I suspect your firewall is blocking it.

⁣Jim Bacher, WB8VSU
wb8vsu@...
https:\\trc.guru​

On May 31, 2022, 4:09 PM, at 4:09 PM, Ron <ron@...> wrote:
Hello all:
I'm a longtime WSJT-X user.

Now I'm setting up WSJT-X on a Windows 10 machine connected to a new
ICOM 7300.

The USB connection to the PC and WSJT-X seems to be working fine.

I installed Meinberg NTP, and that's when I ran into problems.

After doing the install, when I click the Finish button, Meinberg tries
to connect to an NTP server (other than choosing United States from the
drop-down during the install, I let everything else default).

Then it throws the following error:

"It looks like starting the service was not successful. Please check
your event log."

When I check the event log, it says:

"unable to bind to wildcard address 0.0.0.0 - another process may be
running. "

This lead me to believe that another process or program may be running
and using ip address 0.0.0.0.

I immediately thought of windows time, however, I checked it, and it is
fully disabled.

I also checked all the TCP & UDP ports and looked for any program that
was using port 0.0.0.0 & came up with nothing

Been scratching my head all night on this one.

Figured it was time to call in the cavalry.

Any help would be appreciated.

Ron - KJ5XX
Joe Subich, W4TV
 

Make sure that Meinberg is set up to use a separate account with
Administrator privileges. Follow the instructions here:
<http://satsignal.eu/ntp/setup.html>

Note, in particular this comment:
Windows-8 and Windows-10 users:
I recommended that you select the SYSTEM account, rather than the special NTP account. NTP will not function otherwise. Leave the other options as suggested. The installer may have been updated
since this was written to use the SYSTEM account.
73,

... Joe, W4TV


On 2022-05-31 7:58 PM, Ron wrote:
No, I've checked that as well. I setup Meinberg to have full access
through the Windows firewall.
Ron - KJ5XX
On Tue, May 31, 2022, 3:51 PM Jim Bacher - WB8VSU <wb8vsu@...> wrote:

Ron, I suspect your firewall is blocking it.

⁣Jim Bacher, WB8VSU
wb8vsu@...
https:\\trc.guru​

On May 31, 2022, 4:09 PM, at 4:09 PM, Ron <ron@...> wrote:
Hello all:
I'm a longtime WSJT-X user.

Now I'm setting up WSJT-X on a Windows 10 machine connected to a new
ICOM 7300.

The USB connection to the PC and WSJT-X seems to be working fine.

I installed Meinberg NTP, and that's when I ran into problems.

After doing the install, when I click the Finish button, Meinberg tries
to connect to an NTP server (other than choosing United States from the
drop-down during the install, I let everything else default).

Then it throws the following error:

"It looks like starting the service was not successful. Please check
your event log."

When I check the event log, it says:

"unable to bind to wildcard address 0.0.0.0 - another process may be
running. "

This lead me to believe that another process or program may be running
and using ip address 0.0.0.0.

I immediately thought of windows time, however, I checked it, and it is
fully disabled.

I also checked all the TCP & UDP ports and looked for any program that
was using port 0.0.0.0 & came up with nothing

Been scratching my head all night on this one.

Figured it was time to call in the cavalry.

Any help would be appreciated.

Ron - KJ5XX
Ron
 

Very good point Joe. I read the installer readme file & it talked about
that. I made sure I selected System Account. I left everything else as
default.

I will read the instructions you provided, thanks.

Ron - KJ5XX

On Tue, May 31, 2022, 7:31 PM Joe Subich, W4TV <lists@...> wrote:


Make sure that Meinberg is set up to use a separate account with
Administrator privileges. Follow the instructions here:
<http://satsignal.eu/ntp/setup.html>

Note, in particular this comment:
Windows-8 and Windows-10 users:

I recommended that you select the SYSTEM account, rather than the
special NTP account. NTP will not function otherwise. Leave the
other options as suggested. The installer may have been updated
since this was written to use the SYSTEM account.
73,

... Joe, W4TV


On 2022-05-31 7:58 PM, Ron wrote:
No, I've checked that as well. I setup Meinberg to have full access
through the Windows firewall.

Ron - KJ5XX

On Tue, May 31, 2022, 3:51 PM Jim Bacher - WB8VSU <wb8vsu@...>
wrote:

Ron, I suspect your firewall is blocking it.

⁣Jim Bacher, WB8VSU
wb8vsu@...
https:\\trc.guru​

On May 31, 2022, 4:09 PM, at 4:09 PM, Ron <ron@...> wrote:
Hello all:
I'm a longtime WSJT-X user.

Now I'm setting up WSJT-X on a Windows 10 machine connected to a new
ICOM 7300.

The USB connection to the PC and WSJT-X seems to be working fine.

I installed Meinberg NTP, and that's when I ran into problems.

After doing the install, when I click the Finish button, Meinberg tries
to connect to an NTP server (other than choosing United States from the
drop-down during the install, I let everything else default).

Then it throws the following error:

"It looks like starting the service was not successful. Please check
your event log."

When I check the event log, it says:

"unable to bind to wildcard address 0.0.0.0 - another process may be
running. "

This lead me to believe that another process or program may be running
and using ip address 0.0.0.0.

I immediately thought of windows time, however, I checked it, and it is
fully disabled.

I also checked all the TCP & UDP ports and looked for any program that
was using port 0.0.0.0 & came up with nothing

Been scratching my head all night on this one.

Figured it was time to call in the cavalry.

Any help would be appreciated.

Ron - KJ5XX
Gilbert Baron
 

Nettime and other apps are so much easier to use. Meinberg has always been nothing but a nightmare. 99.9999% do not need some of the fancy control and most could even get away with that of Widows itself if they have good internet.

Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb

-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Joe Subich, W4TV
Sent: Tuesday, May 31, 2022 7:32 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Meinberg Error #Timesync


Make sure that Meinberg is set up to use a separate account with Administrator privileges. Follow the instructions here:
<http://satsignal.eu/ntp/setup.html>

Note, in particular this comment:
Windows-8 and Windows-10 users:

I recommended that you select the SYSTEM account, rather than the
special NTP account. NTP will not function otherwise. Leave the
other options as suggested. The installer may have been updated since
this was written to use the SYSTEM account.
73,

... Joe, W4TV


On 2022-05-31 7:58 PM, Ron wrote:
No, I've checked that as well. I setup Meinberg to have full access
through the Windows firewall.

Ron - KJ5XX

On Tue, May 31, 2022, 3:51 PM Jim Bacher - WB8VSU <wb8vsu@...> wrote:

Ron, I suspect your firewall is blocking it.

⁣Jim Bacher, WB8VSU
wb8vsu@...
https:\\trc.guru​

On May 31, 2022, 4:09 PM, at 4:09 PM, Ron <ron@...> wrote:
Hello all:
I'm a longtime WSJT-X user.

Now I'm setting up WSJT-X on a Windows 10 machine connected to a new
ICOM 7300.

The USB connection to the PC and WSJT-X seems to be working fine.

I installed Meinberg NTP, and that's when I ran into problems.

After doing the install, when I click the Finish button, Meinberg
tries to connect to an NTP server (other than choosing United States
from the drop-down during the install, I let everything else default).

Then it throws the following error:

"It looks like starting the service was not successful. Please check
your event log."

When I check the event log, it says:

"unable to bind to wildcard address 0.0.0.0 - another process may be
running. "

This lead me to believe that another process or program may be
running and using ip address 0.0.0.0.

I immediately thought of windows time, however, I checked it, and it
is fully disabled.

I also checked all the TCP & UDP ports and looked for any program
that was using port 0.0.0.0 & came up with nothing

Been scratching my head all night on this one.

Figured it was time to call in the cavalry.

Any help would be appreciated.

Ron - KJ5XX









--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop
Carl - WC4H
 

HI Gilbert.
The Windows time works but I make 2 changes:
1. I change the server to one closer by and known to me. In my case University of Florida or Georgia Tech.
2. I change the polling setting to poll every 10 minutes. The Windows default is something like two weeks (or worse). It is expressed in seconds so you just have to make it 600 for 10 minutes.n This is a Registry entry so one should be careful.

Tell it to Sync Now the do a reboot.

73.
Carl.
Ron
 

Not sure who Gilbert is, but thanks for replying to my question. I'll check
this out.

Thanks!

Ron - KJ5XX

On Wed, Jun 1, 2022, 10:47 AM Carl - WC4H via groups.io <wc4h.dx=
yahoo.com@groups.io> wrote:

HI Gilbert.
The Windows time works but I make 2 changes:
1. I change the server to one closer by and known to me. In my case
University of Florida or Georgia Tech.
2. I change the polling setting to poll every 10 minutes. The Windows
default is something like two weeks (or worse). It is expressed in seconds
so you just have to make it 600 for 10 minutes.n This is a Registry entry
so one should be careful.

Tell it to Sync Now the do a reboot.

73.
Carl.
Graham (ZL1CE)
 

Hi all

The following is mostly a quote from a post I made on another group where users had the same issues with D4 & Meinberg

I have successfully used this method on XP, W7, W8 & W10 for many years. Before the internet days (DOS, W3.1, 98 etc ) I used an early version of Dimension 4.(which needed to be manually calibrated against time signals over several weeks) on my customers computers, but the newer versions of D4 no longer seem to play well with my current W10 version (21H2)


Clock Synchronization using Windows built in time synchronisation

Synchronizing the clock of your PC is normally enabled by default except for networked computers that are domain members. Obviously, this synchronization is not possible for PCs that are not connected (whether permanently or not) to the Internet ...

To activate or check that this function is enabled, you must go to Control Panel | Regional Options, Date and Time | Change date and time and click the Internet Time tab.

Synchronization occurs every 604,800 seconds, or every 7 days. You can increase or decrease this time by editing the registry:

Go to the key: HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ W32Time \ TimeProviders \ NtpClient

Locate and change the value: SpecialPollInterval

Assign a value in seconds. e.g. 3600 will give you an update interval of 60 minutes or 600 will give an update every 10 minutes etc ...

Restart the PC for the changes to take effect. (Source: MSKB Q297227)
--
After comment: I am back trialing Meinberg on my new computer (W10 21H2) but my other computers are all using the built in Windows time sync with a 1 hour update interval (3600 in the appropriate registry key). Also tried D4 recently but it seemed to be flaky

73 Graham
ZL1CE
QTH: RF73jc

View/Reply Online | Reply To Group | Reply To Sender | Mute Topic | Top ^ | New Topic
nm1a@...
 

Hello Group,

Graham ZL1ce has really great instructions!!

I came across a small program that is FREE yes FREE and provides D4, Meinberg, NTP functionality in a concise package.

It is NetTime and can be found at https://www.timesynctool.com/

Simple to use and configure, I use it with the set as a service option and it has been flawless on w7 and currently w10.

73 Art
NM1A
Reino Talarmo
 

Hi Art,

Just a minor correction. NetTime does not provide the same functionality as Meinberg or any other program that supports full NTP protocol.

Extract from Accuracy Notes:
The vast majority of users should find that NetTime more than meets their needs, however if you have specific requirements for very accurate time, I recommend that you investigate installing a full NTP client. Although you can set NetTime to sync more frequently to compensate for an inaccurate system clock, this isn't really recommended because of the greater strain that it puts onto the public NTP servers. A full NTP client has extra features to ensure better time accuracy (normally well below 10 milliseconds even between time syncs) by adjusting the rate that the system clock runs at.

73, Reino OH3mA

-----Original Message-----
....
I came across a small program that is FREE yes FREE and provides D4, Meinberg, NTP functionality in a concise package.
....
Martin G0HDB <marting0hdb@...>
 

On Thu, Jun 2, 2022 at 06:19 PM, Reino Talarmo wrote:

Hi Art,

Just a minor correction. NetTime does not provide the same functionality as
Meinberg or any other program that supports full NTP protocol.

Extract from Accuracy Notes:
The vast majority of users should find that NetTime more than meets their
needs, however if you have specific requirements for very accurate time, I
recommend that you investigate installing a full NTP client. Although you can
set NetTime to sync more frequently to compensate for an inaccurate system
clock, this isn't really recommended because of the greater strain that it
puts onto the public NTP servers. A full NTP client has extra features to
ensure better time accuracy (normally well below 10 milliseconds even between
time syncs) by adjusting the rate that the system clock runs at.
Hi Reino (and all), one factor that shouldn't be overlooked when deciding which time-sync'ing app to use on a PC is the effect of using an app such as D4 (and also NetTime?) that is based on the SNTP protocol rather than the full NTP protocol implemented by the Meinberg app.

An SNTP app doesn't adjust the clock smoothly, as the Meinberg app does, but can cause step-changes (in either direction); the effect of these is described perfectly and succinctly by the late, much-missed Bill Somerville G4WJS:

"What is sure is that a step adjustment to the PC clock during a receive period will cause an audio stream discontinuity, and that in turn may disrupt all decoding for that period. "

In other words, if you use an SNTP-based app then you can expect to suffer from missed decodes in any Rx period in which a step-change of the PC clock occurs. This missed-decode effect has been observed and verified in practice.

73
--
Martin G0HDB
Gilbert Baron
 

Yeaah but so what. Once a day sync is more than good enough for most and you MAY miss ONE decode, you will never know.

Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb

-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Martin G0HDB
Sent: Thursday, June 2, 2022 2:21 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Meinberg Error #Timesync

On Thu, Jun 2, 2022 at 06:19 PM, Reino Talarmo wrote:

Hi Art,

Just a minor correction. NetTime does not provide the same
functionality as Meinberg or any other program that supports full NTP protocol.

Extract from Accuracy Notes:
The vast majority of users should find that NetTime more than meets
their needs, however if you have specific requirements for very
accurate time, I recommend that you investigate installing a full NTP
client. Although you can set NetTime to sync more frequently to
compensate for an inaccurate system clock, this isn't really
recommended because of the greater strain that it puts onto the public
NTP servers. A full NTP client has extra features to ensure better
time accuracy (normally well below 10 milliseconds even between time syncs) by adjusting the rate that the system clock runs at.
Hi Reino (and all), one factor that shouldn't be overlooked when deciding which time-sync'ing app to use on a PC is the effect of using an app such as D4 (and also NetTime?) that is based on the SNTP protocol rather than the full NTP protocol implemented by the Meinberg app.

An SNTP app doesn't adjust the clock smoothly, as the Meinberg app does, but can cause step-changes (in either direction); the effect of these is described perfectly and succinctly by the late, much-missed Bill Somerville G4WJS:

"What is sure is that a step adjustment to the PC clock during a receive period will cause an audio stream discontinuity, and that in turn may disrupt all decoding for that period. "

In other words, if you use an SNTP-based app then you can expect to suffer from missed decodes in any Rx period in which a step-change of the PC clock occurs. This missed-decode effect has been observed and verified in practice.

73
--
Martin G0HDB








--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop
Tim Dawson
 

Sad, considering that full NTP is so simple and trivial to configure on more advanced platforms (IE, yet one more thing MS got wrong).

Not using the right tool simply because an app or platform makes it a bit more challenging frankly confuses me . . . there has to be a way for Win users to hit the fairly low hanging target without making excuses or compromise!

On June 2, 2022 2:54:53 PM CDT, Gilbert Baron <w0mn00@...> wrote:
Yeaah but so what. Once a day sync is more than good enough for most and you MAY miss ONE decode, you will never know.

Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb


-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Martin G0HDB
Sent: Thursday, June 2, 2022 2:21 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Meinberg Error #Timesync

On Thu, Jun 2, 2022 at 06:19 PM, Reino Talarmo wrote:

Hi Art,

Just a minor correction. NetTime does not provide the same
functionality as Meinberg or any other program that supports full NTP protocol.

Extract from Accuracy Notes:
The vast majority of users should find that NetTime more than meets
their needs, however if you have specific requirements for very
accurate time, I recommend that you investigate installing a full NTP
client. Although you can set NetTime to sync more frequently to
compensate for an inaccurate system clock, this isn't really
recommended because of the greater strain that it puts onto the public
NTP servers. A full NTP client has extra features to ensure better
time accuracy (normally well below 10 milliseconds even between time syncs) by adjusting the rate that the system clock runs at.
Hi Reino (and all), one factor that shouldn't be overlooked when deciding which time-sync'ing app to use on a PC is the effect of using an app such as D4 (and also NetTime?) that is based on the SNTP protocol rather than the full NTP protocol implemented by the Meinberg app.

An SNTP app doesn't adjust the clock smoothly, as the Meinberg app does, but can cause step-changes (in either direction); the effect of these is described perfectly and succinctly by the late, much-missed Bill Somerville G4WJS:

"What is sure is that a step adjustment to the PC clock during a receive period will cause an audio stream discontinuity, and that in turn may disrupt all decoding for that period. "

In other words, if you use an SNTP-based app then you can expect to suffer from missed decodes in any Rx period in which a step-change of the PC clock occurs. This missed-decode effect has been observed and verified in practice.

73
--
Martin G0HDB








--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
nm1a@...
 

Hello Reino,

Agreed as your point regarding Meinberg.

My input on this topic was for "quick and dirty" one stop shopping program adequate for most ham digital modes.

I'm sure the EME folks may disagree ;)

I take into consideration to the numbers of hams who are fearful of unknown settings or registry changes.

Thank you Reino
73 Art NM1A
Gilbert Baron
 

I wonder? If this time sync thing is so important then why not include it in the digital software and take the burden off the user. or maybe the burden does not really exist and we are just seeing the mountain out of mole hill thing. 😊



Outlook LT Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of nm1a@...
Sent: Thursday, June 2, 2022 3:35 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Meinberg Error #Timesync



Hello Reino,



Agreed as your point regarding Meinberg.



My input on this topic was for "quick and dirty" one stop shopping program adequate for most ham digital modes.



I'm sure the EME folks may disagree ;)



I take into consideration to the numbers of hams who are fearful of unknown settings or registry changes.



Thank you Reino

73 Art NM1A













--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

1 - 20 of 69