Hi Reino, yes that's what I'm running to monitor the time server.  if you go to the website you suggested and look at the screenshots  and compare them with mine shown here, I appear to be running

New hamlib for installation directions #1 Shut down WSJTX/JTDX #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but

Got it to allow me to reset the profile. I am now getting hamlib errors, command reject by rig.Does that help. I changed nothing but the program...

I did an upgrade from 2.5.1 to the latest. I lost rig control, then when I tell wsjtx to close, it leaves it running in the background. Windows 10, been running WSJT for a long time on this

I tried to upload some screenshots of what I see while running Meinberg's  NTP Time Server Monitor APP. but the message  didn't make it. So the system time updates every 10 minutes and all is good,

Not sure exactly what yiu are looking for, but considering that Meinberg is nothing more that a compile of stock ntp code (it already supports Windows, just no installer . . . ) you might check the

I think that that is to monitor thier hardware devices . . . . "ntpq" is included in the base package, which gives typical stats (called as "quick monitor" from the menus, and gives data for me on

Hi Jeff, Have you also installed https://www.meinbergglobal.com/english/sw/ntp-server-monitor.htm ? That may be what you want. 73, Reino OH3mA

I'm running  Meinberg 1.04 here  on a WIN10 machine and it seems to be working, but I  don't collect any statistics even after running over 24 hours. Is this normal. if not, how do I turn the

I was trying to work 3D2RRR last week before the contest and a Puerto Rico station starting calling me over & over & over for at least 25 times, maybe more. I checked my log and found I had worked

Around 2200z Satuday, I called normal CQ 20m FT4 and worked several contesters while they were in contest mode with no problems. I gladly made contacts even though there is no report received in my

That could certainly be it.. I've just never seen it so prevalent as it was today.

Hi Jon Maybe this (copied from User Guide): For operation at 144 MHz or above you may find it helpful to use short-format *Sh* messages for Tx3, Tx4, and Tx5. These messages are 20 ms long, compared

Any ideas on what it means when I see decodes like this, with no callsigns? WSJT-X 2.5.2, MSK144, SWL box checked. 135530 9 11.7 1570 & <1096> R+06 135600 8 1.3 1461 & <1883> R+00 135630 5

Not so true. If I'lm in Qso whit, say, i1xxx and at the end I receive a call I2OIM I2YYY JN45 I can't be sure that I2YYY has stored my maidenhead. I would have a CQ TX in the middle, to be

I never had the problem when using FT8 because it is on a completely different contest frequency. But the FT4 contest mode is on the standard FT4 frequency where a lot of people have normal QSOs. I

In just the short time I have been doing this new contest I find way too many just typed "TEST" in their CQ (TX6) or are using the wrong contest software. It's a new contest format and will take a

Thank you, Karza. That did it. Changed from USB to COM3 and I am back in business. 73, Tad -- *Listen for K7RA/B CW beacon on 28.2833 MHz.* *Tad Cook - K7RA* *Seattle, WA* *k7ra@...

Hi David, Were you on the contest frequency too? Or on the std. freq.? If you stay on the contest freq's, most folks not in the contest probably won't even be there.

I will add that his recommendation is correct - as per the ARRL contest director. NA VHF uses the correct exchange, lists "TEST" in the CQ (TX6) line, and has been verified to work correctly.