Yes and no . . . Meinberg is simply a Windows compile of open source NTP code that runs on multiple platforms, couples with a Wimdows installler. It is *NOT* a unique,mor Wimdows-centric codebase!

I've been following the latest round of Time Sync posts. Most of the posts make very good points. Martin made reference to the much missed Bill Sommerville, and I would like to second that

Try this DLL.  It has a new FT990UNI entry that will use the cached value for get_freq. Should solve your problem.  Only think with UNI mode is that WSJT-X will not follow manual freq changes on the

That last thing you want is a user app controlling the time. That's a completely independent operation and why you won't see that built into anything.  My TimeFudge program (on my QRZ page) allows

The FT-990 older ROM v1.2 sends back the whole 1492 bytes of its memory which takes 3.8s with Rigctl and almost 20s with WSJT-X. FYI - I've created modified ft990.c and ft990.h files to handle the

The one thought that I think is pertinent to this discussion is this: Were the basic split/management functions for ALL.txt be added to WSJTX, then it would be a truly portable solution. As it is,

Tim, NTP is included in later Windows. I still use Meinberg but the Windows NTP requires configuration, the default is for "normal"

WSJTX is a cross-platform app, Windows, Linux & MacOS. Meinberg is Windows only. de Laurie VK3AMA

Grrr . . . fat fingers! That should be "... if the issues with Meinberg . . . xould be resolven, then it could be included with WSJTX . . - Tim -- Sent from my Android device with K-9 Mail.

Frankly, if the issues with Meinberg (actually, that is nothing more than a compile of open source NTP code . . . ) could be included with WSJTX for Windows, it would be the ideal solution. Those

Thanks for letting me know. I was thinking of something very simple with no bells and whistles and works on any size ALL.TXT file. So it's good to know that you have already cracked that nut. I

Agreed. I find the dancing on the head of a pin about this silly. I've used nothing but Net Time since the earliest days of WSJT, almost 15 years, and average DT values are always quite small. Over

Phil, With a non-standard callsign, you can not send the grid. I've seen other non-standard callsign users substitute a free text message <CALLSIGN> <GRID> for the CQ message periodically. The

So either fix the OS, go to an OS that actually works, or learn how to properly deploy the 3rd party tools that solve the problem . . . -- Sent from my Android device with K-9 Mail. Please excuse

Agree , but many here say the OS is not really doing a good job of it. Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb

Exactly! If time synchronization was implemented in WSJTX and the user shutdown WSJTX they then loose any time synchronization. To maintain accurate time keeping would require that WSJTX is kept

Because timekeeping is an OS task, not part of any app . . . -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

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

Hi Gene, Check the program AllText.exe that I wrote and that is available for free at ProgramsByW2JDB@groups.io. It does what you mentioned and more. The All.txt file size does not matter. It does