Date   

locked Re: Worked B4 color

JP Tucson, AZ
 

It is listed as: "CQ in Message"; 2nd from last; i.e. GREEN color as default.

73 - John - N7GHZ

On Mon, Mar 23, 2020, 5:18 AM w5ec <bhw5ec@...> wrote:
I have read the User Guide as carefully as I know how and I can't see how to get a "worked B4" warning.
There is no choice to select "Worked B4" in the Colors tab. The worked before box in the General tab is checked.What am I missing?
Bill W5EC


locked Re: Worked B4 color

JP Tucson, AZ
 

The standard color scheme IS: once you've worked them, they turn GREEN!



73 - John - N7GHZ


On Mon, Mar 23, 2020, 5:18 AM w5ec <bhw5ec@...> wrote:
I have read the User Guide as carefully as I know how and I can't see how to get a "worked B4" warning.
There is no choice to select "Worked B4" in the Colors tab. The worked before box in the General tab is checked.What am I missing?
Bill W5EC


locked Re: Worked B4 color

Paul - W1PR
 

Clever scheme, Bob. Thanks for telling us. I'll implement it. Something to do while confined to the house. 73, Paul


locked Re: Worked B4 color

K8BL BOB LIDDY <k8bl@...>
 

Here is how to indicate a "Worked Before" Station. This will only
show up concerning a Station worked before when they call CQ.

I've done it by going to "Colors" in the the "Setup" section and checking the
appropriate boxes for the highlighting I desire. As far as I know, it can only
be done when a Station calls CQ.

Here's what I have checked in this specific order:

- My Call In Message
- New CQ Zone
- New DXCC
- New Grid
- New Call
- New Call On Band
- CQ In Message
- Transmitted Message

You MUST move the selections into the specific order shown above! This is
done by holding down the Right Clicker on your mouse and moving the 
selection up or down as desired.

Each of these are given their OWN specific Color/Background. Be sure the items
are in the order shown which assigns priority. Then, if a decoded Call is not mine
or not "New", it gets highlighted as a CQ of a Station I worked before. EASY!!

Only a CQ from a Station I've never worked gets a highlight since they would be
new. A "Worked Before CQ" gets a very pale background since I don't want it
standing out very much.

I've repeated the important issues for emphasis. The selections MUST be in the order
above. It will only indicate "Worked Before" during their CQ. You need to give them a
unique color so they stand out (very pale would be desired).

I have logged almost 18,000 FT8/4 QSOs and the above scheme works perfectly.

GL/73, Bob K8BL

On Monday, March 23, 2020, 08:20:26 AM EDT, Bill Somerville <g4wjs@...> wrote:





On 23/03/2020 12:17, w5ec wrote:
I have read the User Guide as carefully as I know how and I can't see
how to get a "worked B4" warning.
There is no choice to select "Worked B4" in the Colors tab. The worked
before box in the General tab is checked.What am I missing?
Bill W5EC
Hi Bill,

there is no worked before colour, but there are colours to highlight CQs
from stations you have not worked before on the current band and for
stations you have not worked before on any band. It should be obvious
that this is better than highlighting worked before stations.

73

Bill

G4WJS.


locked Re: Worked B4 color

 

On Mon, Mar 23, 2020 at 12:20 PM, Bill Somerville wrote:


On 23/03/2020 12:17, w5ec wrote:
I have read the User Guide as carefully as I know how and I can't see
how to get a "worked B4" warning.
There is no choice to select "Worked B4" in the Colors tab. The worked
before box in the General tab is checked.What am I missing?
Bill W5EC
Hi Bill,

there is no worked before colour, but there are colours to highlight CQs
from stations you have not worked before on the current band and for
stations you have not worked before on any band. It should be obvious
that this is better than highlighting worked before stations.
In effect there is marking of worked before:

The selection I use is - for CQs:
- Not worked DXCC on any band.
- Not worked DXCC on this band.
- Not worked station before on any band.
- Not worked station before on this band.
- All other CQs (i.e. worked station before on this band)

Phil GM3ZZA

73
Bill
G4WJS.


--
73 Phil GM3ZZA


locked Re: Worked B4 color

Bill Somerville
 

On 23/03/2020 12:17, w5ec wrote:
I have read the User Guide as carefully as I know how and I can't see how to get a "worked B4" warning.
There is no choice to select "Worked B4" in the Colors tab. The worked before box in the General tab is checked.What am I missing?
Bill W5EC
Hi Bill,

there is no worked before colour, but there are colours to highlight CQs from stations you have not worked before on the current band and for stations you have not worked before on any band. It should be obvious that this is better than highlighting worked before stations.

73
Bill
G4WJS.


locked Re: Worked B4 color

w5ec
 

I have read the User Guide as carefully as I know how and I can't see how to get a "worked B4" warning.
There is no choice to select "Worked B4" in the Colors tab. The worked before box in the General tab is checked.What am I missing?
Bill W5EC


locked Re: Getting Meinberg to work

Arthur Bernstein
 

Thanks to Bob and Jim. I’m now a “Meinberger.”
73,
Art., N2KA..

On Mar 22, 2020, at 7:15 PM, Jim Brown <k9yc@...> wrote:

The simple answer to "is it working" is DT data for your decodes. If nearly all DTs are small (+/- 0.2), with one or two outliers (1-2 sec) your clock is just fine.

73, Jim K9YC

On 3/22/2020 2:14 PM, Bob Lewis wrote:
It looks like it’s working to me.


locked Re: Getting Meinberg to work

Jim Brown
 

The simple answer to "is it working" is DT data for your decodes. If nearly all DTs are small (+/- 0.2), with one or two outliers (1-2 sec) your clock is just fine.

73, Jim K9YC

On 3/22/2020 2:14 PM, Bob Lewis wrote:
It looks like it’s working to me.


locked Re: error, compiling wsjtx from source #linux

Bill Somerville
 

On 22/03/2020 22:49, Fred, DH5FS wrote:
Hi Bill, i have a (old and patched) global hamlib installation, yes. Cmake takes always the global eg. hamlib_INCLUDE_DIRS and not the one defined under CMAKE_PREFIX_PATH. Any way out?

73 Fred
Hi Fred,

CMake always uses CMAKE_PREFIX_PATH ahead of system paths. Are you using the WSJT-X source tarball or a clone from a git repository? The official sources tarball has a special CMake script to build both Hamlib and WSJT-X, there is no need to set CMAKE_PREFIX_PATH with that.

73
Bill
G4WJS.


locked Re: error, compiling wsjtx from source #linux

Fred, DH5FS
 

Hi Bill, i have a (old and patched) global hamlib installation, yes. Cmake takes always the global eg. hamlib_INCLUDE_DIRS and not the one defined under CMAKE_PREFIX_PATH. Any way out?

73 Fred


locked Re: Error opening audio output device #AudioIssues

Bill Somerville
 

On 22/03/2020 22:04, Anthony DeWitt wrote:
I have a Toshiba Laptop running Windows 10. I have an ICOM 7300.
I have never had a problem with WSJT-X running HRD as a front door.
Today I got "error opening audio output device."
I searched the user group and saw the instructions regarding the audio input device.  The USB cable isproperly shielded with multiple ferrite chokes with the cable looped through several.
I reduced power to 4 watts.
I re-installed the USB driver.
I am using the internal sound card on the 7300.
My USB Mod Level is set to 45%
My USB Audio Codec is set to 31%
I have not monkeyed with any of these settings.  The only intervening action I have taken is to install several codeplug software programs for DMR on the same laptop.
This problem arose after the lastest Windows update (God I hate those!)
For whatever reason, I cannot seem to get audio output to the radio, and I must be missing something.

AD0DQ
Hi Anthony,

Windows 10 updates can mess with the USB devices. Try changing to another pair of audio devices in the WSJT-X "Settings->Audio" panel, click OK, then go back and select the audio codec for the IC-7300.

Also check you Tx audio levels, this post has details:

https://groups.io/g/WSJTX/message/5077

73
Bill
G4WJS.


locked Error opening audio output device #AudioIssues

Anthony DeWitt
 

I have a Toshiba Laptop running Windows 10. I have an ICOM 7300.
I have never had a problem with WSJT-X running HRD as a front door.
Today I got "error opening audio output device."
I searched the user group and saw the instructions regarding the audio input device.  The USB cable isproperly shielded with multiple ferrite chokes with the cable looped through several.
I reduced power to 4 watts.
I re-installed the USB driver.
I am using the internal sound card on the 7300.
My USB Mod Level is set to 45%
My USB Audio Codec is set to 31%
I have not monkeyed with any of these settings.  The only intervening action I have taken is to install several codeplug software programs for DMR on the same laptop. 
This problem arose after the lastest Windows update (God I hate those!)
For whatever reason, I cannot seem to get audio output to the radio, and I must be missing something.

AD0DQ


locked Re: Getting Meinberg to work

Bob Lewis
 

It looks like it’s working to me.  If you right-click on that “Quick NPT Status” icon you can select “Pin to Start” and it will place a copy of it in your start menu icons at the top so it’ll be easy to find in the future.

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Arthur Bernstein via Groups.Io
Sent: Sunday, March 22, 2020 3:56 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work

 

Well, I followed Bob Lewis’ advice and I’m assuming I’ve gotten Meinberg working. When I click on Meinberg in the Start Menu, I get numerous subfolders. After clicking on Quick NTP Status I’m assuming I’m accessing 3 time servers?

The REACH is 377 on all 3, sometimes a little less on the second one, but all eventually are at 377. The POLL is 128 on all 3.

The 3 sites are in this order: +140.82.50.15 (1 47.187.174.51, the next one: +static-72-87-88 129.5.15.20, and the last one is: +NTP-3.jonlight 55.220.9.122.

 

Not exactly sure what these I.P.s are, perhaps 3 time servers??

 

You said to right click on Quick NTP Status to put it into Pin at Start. Correct?? I was able to make a Desktop Icon out of this to bring up Quick NTP Status. Correct??

 

Does it look like it’s working? It is exactly (to the best of my auditory skills) in Sync with WWV at 10.000 Mhz for the second consecutive day and the Quick NTP Status is holding.

 

Many thanks to Bob, AA4PB and others who have dragged this semi illiterate digital idiot through.

 

73,

 

Art., N2KA..

 

From: Bob Lewis

Sent: Saturday, March 21, 2020 5:24 PM

Subject: Re: [WSJTX] Getting Meinberg to work

 

In the quick check NTP status the [offset] tells you how many mS you clock was off from UTC. After running for a while, the [reach] should be 377.  The [poll] should start at about 64 seconds and should start significantly increasing after a day or so. The [poll] is the number of seconds between interrogation of the NTP servers. As your clock error decreases, Meinberg automatically checks the servers less often. If this is happening then you know that its working properly.

 

Meinberg automatically shows up in my W10 start menu. If you expand that you will find “quick check”. I right-clicked it and selected pin to start and now quick check shows up in the start panel where it’s easy to get to.

 

If you downloaded the Setup on Windows document there is a section on Checking it’s working that will give you all the details.

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of David Piersall
Sent: Saturday, March 21, 2020 4:51 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work

 

Meinberg starts up when I boot up the computer. A reboot does the same. But you don't have to do a reboot. Right-click on the "Restart NTP Service" icon and select "Run as Administrator." I dragged that icon to my desktop so it's always readily available. If I've previously closed the lid of my laptop, putting it in sleep mode, Meinberg doesn't work again until I right-click on the "Restart NTP Service" icon and click "Run as Administrator."

 

At the moment, TIME.IS shows my computer's time being off by .016 second, well within the error bars of TIME.IS.

 

Dave Piersall, N6ORB

 

On Saturday, March 21, 2020, 12:04:51 PM PDT, Arthur Bernstein via Groups.Io <n2ka@...> wrote:

 

 

Well, after reading a literal library of information regarding how to get Meinberg to work, I followed the instructions. I’m not sure if it’s working. Downloaded the latest version for Win 10 as well as the Visual Studio Redistributable Package (whatever that is.) I do not have a desktop icon for Meinberg, but going into Windows Programs, Meinberg is there with numerous sub files. Here’s what I found: Quick Check NTP Status: It is Autorefreshing every 10 seconds and the time exactly coincides (as best as I can tell) with WWV at 10.000 Mhz and with the computer’s clock.  When I try to “Start NTP Service” I get “system error, access is denied, press any key to continue.” Something similar happens when I try “Restart NTP Service”—access denied. Wait 10 seconds before restart. When I select “Stop NTP Service” I get Access denied.

 

The question I have is this, is Meinberg working and running in the background to keep the clock accurate?

 

I do notice on FT8 the time differential is generally very close to 0, perhaps +/- decimal place. I think this was why I wasn’t decoding messages before.

 

So what say? Thanks,

73,

Art., N2KA..

 

From: Bob Lewis

Sent: Friday, March 20, 2020 8:42 PM

Subject: Re: [WSJTX] Getting Meinberg to work

 

You all convinced me. I downloaded and installed Meinberg. Following the instructions everything went fine but it wouldn’t start. I rebooted the computer and it came up running – everything looks good thus far. It might be that when I uninstalled D4 it left something running in the background and the reboot cleared it.

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Nc8q-mesh@...
Sent: Friday, March 20, 2020 1:37 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work

 

On 3/20/20 5:53 AM, Bill Somerville wrote:

Hi Bob,

 

WSJT-X uses the PC clock to synchronize audio, its not just the overall T/R period lengths that need an accurate PC clock but at he millisecond level. Any period where there is a clock discontinuity is likely to not be successfully decoded.

 

73
Bill
G4WJS.

 


 


 


locked Re: Getting Meinberg to work

Nicholas Shaxted
 

Are you sure you have the time servers listed in the configuration file ?

 

You may find these pages interesting a relevant.

Take a read of https://www.satsignal.eu/ntp/setup.html

 

 

Nick – g4ogi

 

From: WSJTX@groups.io On Behalf Of Arthur Bernstein via Groups.Io
Sent: Sunday, March 22, 2020 7:56 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work

 

Well, I followed Bob Lewis’ advice and I’m assuming I’ve gotten Meinberg working. When I click on Meinberg in the Start Menu, I get numerous subfolders. After clicking on Quick NTP Status I’m assuming I’m accessing 3 time servers?

The REACH is 377 on all 3, sometimes a little less on the second one, but all eventually are at 377. The POLL is 128 on all 3.

The 3 sites are in this order: +140.82.50.15 (1 47.187.174.51, the next one: +static-72-87-88 129.5.15.20, and the last one is: +NTP-3.jonlight 55.220.9.122.

 

Not exactly sure what these I.P.s are, perhaps 3 time servers??

 

You said to right click on Quick NTP Status to put it into Pin at Start. Correct?? I was able to make a Desktop Icon out of this to bring up Quick NTP Status. Correct??

 

Does it look like it’s working? It is exactly (to the best of my auditory skills) in Sync with WWV at 10.000 Mhz for the second consecutive day and the Quick NTP Status is holding.

 

Many thanks to Bob, AA4PB and others who have dragged this semi illiterate digital idiot through.

 

73,

 

Art., N2KA..

 

From: Bob Lewis

Sent: Saturday, March 21, 2020 5:24 PM

Subject: Re: [WSJTX] Getting Meinberg to work

 

In the quick check NTP status the [offset] tells you how many mS you clock was off from UTC. After running for a while, the [reach] should be 377.  The [poll] should start at about 64 seconds and should start significantly increasing after a day or so. The [poll] is the number of seconds between interrogation of the NTP servers. As your clock error decreases, Meinberg automatically checks the servers less often. If this is happening then you know that its working properly.

 

Meinberg automatically shows up in my W10 start menu. If you expand that you will find “quick check”. I right-clicked it and selected pin to start and now quick check shows up in the start panel where it’s easy to get to.

 

If you downloaded the Setup on Windows document there is a section on Checking it’s working that will give you all the details.

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of David Piersall
Sent: Saturday, March 21, 2020 4:51 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work

 

Meinberg starts up when I boot up the computer. A reboot does the same. But you don't have to do a reboot. Right-click on the "Restart NTP Service" icon and select "Run as Administrator." I dragged that icon to my desktop so it's always readily available. If I've previously closed the lid of my laptop, putting it in sleep mode, Meinberg doesn't work again until I right-click on the "Restart NTP Service" icon and click "Run as Administrator."

 

At the moment, TIME.IS shows my computer's time being off by .016 second, well within the error bars of TIME.IS.

 

Dave Piersall, N6ORB

 

On Saturday, March 21, 2020, 12:04:51 PM PDT, Arthur Bernstein via Groups.Io <n2ka@...> wrote:

 

 

Well, after reading a literal library of information regarding how to get Meinberg to work, I followed the instructions. I’m not sure if it’s working. Downloaded the latest version for Win 10 as well as the Visual Studio Redistributable Package (whatever that is.) I do not have a desktop icon for Meinberg, but going into Windows Programs, Meinberg is there with numerous sub files. Here’s what I found: Quick Check NTP Status: It is Autorefreshing every 10 seconds and the time exactly coincides (as best as I can tell) with WWV at 10.000 Mhz and with the computer’s clock.  When I try to “Start NTP Service” I get “system error, access is denied, press any key to continue.” Something similar happens when I try “Restart NTP Service”—access denied. Wait 10 seconds before restart. When I select “Stop NTP Service” I get Access denied.

 

The question I have is this, is Meinberg working and running in the background to keep the clock accurate?

 

I do notice on FT8 the time differential is generally very close to 0, perhaps +/- decimal place. I think this was why I wasn’t decoding messages before.

 

So what say? Thanks,

73,

Art., N2KA..

 

From: Bob Lewis

Sent: Friday, March 20, 2020 8:42 PM

Subject: Re: [WSJTX] Getting Meinberg to work

 

You all convinced me. I downloaded and installed Meinberg. Following the instructions everything went fine but it wouldn’t start. I rebooted the computer and it came up running – everything looks good thus far. It might be that when I uninstalled D4 it left something running in the background and the reboot cleared it.

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Nc8q-mesh@...
Sent: Friday, March 20, 2020 1:37 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work

 

On 3/20/20 5:53 AM, Bill Somerville wrote:

Hi Bob,

 

WSJT-X uses the PC clock to synchronize audio, its not just the overall T/R period lengths that need an accurate PC clock but at he millisecond level. Any period where there is a clock discontinuity is likely to not be successfully decoded.

 

73
Bill
G4WJS.

 


 


 


locked Re: Getting Meinberg to work

Monty Wilson, NR0A
 

You can also check your computer clock with this web site.

 

https://time.is/

 

Monty Wilson, NR0A

 

From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Arthur Bernstein via Groups.Io
Sent: Sunday, March 22, 2020 02:56 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work

 

Well, I followed Bob Lewis’ advice and I’m assuming I’ve gotten Meinberg working. When I click on Meinberg in the Start Menu, I get numerous subfolders. After clicking on Quick NTP Status I’m assuming I’m accessing 3 time servers?

The REACH is 377 on all 3, sometimes a little less on the second one, but all eventually are at 377. The POLL is 128 on all 3.

The 3 sites are in this order: +140.82.50.15 (1 47.187.174.51, the next one: +static-72-87-88 129.5.15.20, and the last one is: +NTP-3.jonlight 55.220.9.122.

 

Not exactly sure what these I.P.s are, perhaps 3 time servers??

 

You said to right click on Quick NTP Status to put it into Pin at Start. Correct?? I was able to make a Desktop Icon out of this to bring up Quick NTP Status. Correct??

 

Does it look like it’s working? It is exactly (to the best of my auditory skills) in Sync with WWV at 10.000 Mhz for the second consecutive day and the Quick NTP Status is holding.

 

Many thanks to Bob, AA4PB and others who have dragged this semi illiterate digital idiot through.

 

73,

 

Art., N2KA..

 

From: Bob Lewis

Sent: Saturday, March 21, 2020 5:24 PM

Subject: Re: [WSJTX] Getting Meinberg to work

 

In the quick check NTP status the [offset] tells you how many mS you clock was off from UTC. After running for a while, the [reach] should be 377.  The [poll] should start at about 64 seconds and should start significantly increasing after a day or so. The [poll] is the number of seconds between interrogation of the NTP servers. As your clock error decreases, Meinberg automatically checks the servers less often. If this is happening then you know that its working properly.

 

Meinberg automatically shows up in my W10 start menu. If you expand that you will find “quick check”. I right-clicked it and selected pin to start and now quick check shows up in the start panel where it’s easy to get to.

 

If you downloaded the Setup on Windows document there is a section on Checking it’s working that will give you all the details.

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of David Piersall
Sent: Saturday, March 21, 2020 4:51 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work

 

Meinberg starts up when I boot up the computer. A reboot does the same. But you don't have to do a reboot. Right-click on the "Restart NTP Service" icon and select "Run as Administrator." I dragged that icon to my desktop so it's always readily available. If I've previously closed the lid of my laptop, putting it in sleep mode, Meinberg doesn't work again until I right-click on the "Restart NTP Service" icon and click "Run as Administrator."

 

At the moment, TIME.IS shows my computer's time being off by .016 second, well within the error bars of TIME.IS.

 

Dave Piersall, N6ORB

 

On Saturday, March 21, 2020, 12:04:51 PM PDT, Arthur Bernstein via Groups.Io <n2ka@...> wrote:

 

 

Well, after reading a literal library of information regarding how to get Meinberg to work, I followed the instructions. I’m not sure if it’s working. Downloaded the latest version for Win 10 as well as the Visual Studio Redistributable Package (whatever that is.) I do not have a desktop icon for Meinberg, but going into Windows Programs, Meinberg is there with numerous sub files. Here’s what I found: Quick Check NTP Status: It is Autorefreshing every 10 seconds and the time exactly coincides (as best as I can tell) with WWV at 10.000 Mhz and with the computer’s clock.  When I try to “Start NTP Service” I get “system error, access is denied, press any key to continue.” Something similar happens when I try “Restart NTP Service”—access denied. Wait 10 seconds before restart. When I select “Stop NTP Service” I get Access denied.

 

The question I have is this, is Meinberg working and running in the background to keep the clock accurate?

 

I do notice on FT8 the time differential is generally very close to 0, perhaps +/- decimal place. I think this was why I wasn’t decoding messages before.

 

So what say? Thanks,

73,

Art., N2KA..

 

From: Bob Lewis

Sent: Friday, March 20, 2020 8:42 PM

Subject: Re: [WSJTX] Getting Meinberg to work

 

You all convinced me. I downloaded and installed Meinberg. Following the instructions everything went fine but it wouldn’t start. I rebooted the computer and it came up running – everything looks good thus far. It might be that when I uninstalled D4 it left something running in the background and the reboot cleared it.

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Nc8q-mesh@...
Sent: Friday, March 20, 2020 1:37 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work

 

On 3/20/20 5:53 AM, Bill Somerville wrote:

Hi Bob,

 

WSJT-X uses the PC clock to synchronize audio, its not just the overall T/R period lengths that need an accurate PC clock but at he millisecond level. Any period where there is a clock discontinuity is likely to not be successfully decoded.

 

73
Bill
G4WJS.

 


 


 


locked Re: Getting Meinberg to work

Arthur Bernstein
 

Well, I followed Bob Lewis’ advice and I’m assuming I’ve gotten Meinberg working. When I click on Meinberg in the Start Menu, I get numerous subfolders. After clicking on Quick NTP Status I’m assuming I’m accessing 3 time servers?
The REACH is 377 on all 3, sometimes a little less on the second one, but all eventually are at 377. The POLL is 128 on all 3.
The 3 sites are in this order: +140.82.50.15 (1 47.187.174.51, the next one: +static-72-87-88 129.5.15.20, and the last one is: +NTP-3.jonlight 55.220.9.122.
 
Not exactly sure what these I.P.s are, perhaps 3 time servers??
 
You said to right click on Quick NTP Status to put it into Pin at Start. Correct?? I was able to make a Desktop Icon out of this to bring up Quick NTP Status. Correct??
 
Does it look like it’s working? It is exactly (to the best of my auditory skills) in Sync with WWV at 10.000 Mhz for the second consecutive day and the Quick NTP Status is holding.
 
Many thanks to Bob, AA4PB and others who have dragged this semi illiterate digital idiot through.
 
73,
 
Art., N2KA..
 

From: Bob Lewis
Sent: Saturday, March 21, 2020 5:24 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work
 

In the quick check NTP status the [offset] tells you how many mS you clock was off from UTC. After running for a while, the [reach] should be 377.  The [poll] should start at about 64 seconds and should start significantly increasing after a day or so. The [poll] is the number of seconds between interrogation of the NTP servers. As your clock error decreases, Meinberg automatically checks the servers less often. If this is happening then you know that its working properly.

 

Meinberg automatically shows up in my W10 start menu. If you expand that you will find “quick check”. I right-clicked it and selected pin to start and now quick check shows up in the start panel where it’s easy to get to.

 

If you downloaded the Setup on Windows document there is a section on Checking it’s working that will give you all the details.

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of David Piersall
Sent: Saturday, March 21, 2020 4:51 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work

 

Meinberg starts up when I boot up the computer. A reboot does the same. But you don't have to do a reboot. Right-click on the "Restart NTP Service" icon and select "Run as Administrator." I dragged that icon to my desktop so it's always readily available. If I've previously closed the lid of my laptop, putting it in sleep mode, Meinberg doesn't work again until I right-click on the "Restart NTP Service" icon and click "Run as Administrator."

 

At the moment, TIME.IS shows my computer's time being off by .016 second, well within the error bars of TIME.IS.

 

Dave Piersall, N6ORB

 

On Saturday, March 21, 2020, 12:04:51 PM PDT, Arthur Bernstein via Groups.Io <n2ka@...> wrote:

 

 

Well, after reading a literal library of information regarding how to get Meinberg to work, I followed the instructions. I’m not sure if it’s working. Downloaded the latest version for Win 10 as well as the Visual Studio Redistributable Package (whatever that is.) I do not have a desktop icon for Meinberg, but going into Windows Programs, Meinberg is there with numerous sub files. Here’s what I found: Quick Check NTP Status: It is Autorefreshing every 10 seconds and the time exactly coincides (as best as I can tell) with WWV at 10.000 Mhz and with the computer’s clock.  When I try to “Start NTP Service” I get “system error, access is denied, press any key to continue.” Something similar happens when I try “Restart NTP Service”—access denied. Wait 10 seconds before restart. When I select “Stop NTP Service” I get Access denied.

 

The question I have is this, is Meinberg working and running in the background to keep the clock accurate?

 

I do notice on FT8 the time differential is generally very close to 0, perhaps +/- decimal place. I think this was why I wasn’t decoding messages before.

 

So what say? Thanks,

73,

Art., N2KA..

 

From: Bob Lewis

Sent: Friday, March 20, 2020 8:42 PM

To: WSJTX@groups.io

Subject: Re: [WSJTX] Getting Meinberg to work

 

You all convinced me. I downloaded and installed Meinberg. Following the instructions everything went fine but it wouldn’t start. I rebooted the computer and it came up running – everything looks good thus far. It might be that when I uninstalled D4 it left something running in the background and the reboot cleared it.

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Nc8q-mesh@...
Sent: Friday, March 20, 2020 1:37 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Getting Meinberg to work

 

On 3/20/20 5:53 AM, Bill Somerville wrote:

Hi Bob,

 

WSJT-X uses the PC clock to synchronize audio, its not just the overall T/R period lengths that need an accurate PC clock but at he millisecond level. Any period where there is a clock discontinuity is likely to not be successfully decoded.

 

73
Bill
G4WJS.

 


 




locked Transmit noise using FT8

RC Ringers
 

To Dave VE3WEJ, John N7GHZ, Hasan N0AN and anyone I forgot,
 
Problem resolved! I found the Transmit Monitor control right next to the phone jack on the front panel.
It has settings from off to 0-10. Perfect. Transmit noise gone!
 
Thanks to all!
 
Roge K2RRB

--
Roger Ringers


locked Re: TS-440

JP Tucson, AZ
 

Hi Michael,

Is that for a TS-440 OR... 440S(AT)?

I have the latter & trying to get it to work on Win10 & WSJT-X!



73 - John - N7GHZ


On Sun, Mar 22, 2020, 10:40 AM Michael Black via Groups.Io <mdblack98=yahoo.com@groups.io> wrote:
Is there a TS-440 owner out there that can be a beta tester for some hamlib rig changes?

de Mike W9MDB




locked TS-440

Michael Black
 

Is there a TS-440 owner out there that can be a beta tester for some hamlib rig changes?

de Mike W9MDB