JTAlerts and GridTracker both let you do this.  Yes it does involve a little setup in either, but that's the price one pays for features.

73.
Carl - WC4G

On 4 Jul 2021 at 18:51, N8OFP.DL@... wrote:

I know programs like JTAlert offer
this function but the process to add
or remove a call sign is too time
consuming, and the author doesn't
seem interested in making any such
change..

Where have you been? In JTalert, all you have to do is
right click on the call sign from any of about four or five
different locations and you get a menu allowing you to add
or delete the callfrom the Wanted list or several other
lists. Two clicks and it's done; A total of about 2 seconds.

Don't trash programs unless you are using the latest version
and have read the FAQ and the user guides.

I would like to see a text box added to the main screen of WSJT-X where a user could enter a specific call sign they are watching for. The program would highlight that call sign in some fashion to let the user know that it had been decoded. With the FT8 and FT4 modes becoming more and more popular it is difficult to find a specific call sign. This is especially true during special events or contest (prime example the 13 Colonies Event). The text box would only hold one call sign and the user could copy and paste or type the call sign in. To remove the call sign the user would simply highlight the call and either type over it, or delete it. 

I know programs like JTAlert offer this function but the process to add or remove a call sign is too time consuming, and the author doesn't seem interested in making any such change..

On 5/07/2021 9:15 am, Doug Bates - WB4JPG wrote:

I turned Sound ON and when there's an Alert JTAlert crashes.

When I go to Settings > Wanted Grid > Alert Sound and select Test JTAlert crashes.

Below is the output from Event Viewer > Windows Logs > Application

Faulting application name: JTAlertV2.Manager.exe, version: 2.50.1.0, time stamp: 0x602c44b3

This is due to a regression in the latest NET 5.0.7 Desktop Runtime.
JTAlert 2.50.2 was released to overcome that defect. See the release notes.

de Laurie VK3AMA

You'd do better asking this on the hamapps.groups.io list where JTAlert is supported.

Neil, KN3ILZ

I turned Sound ON and when there's an Alert JTAlert crashes.

When I go to Settings > Wanted Grid > Alert Sound and select Test JTAlert crashes.

Below is the output from Event Viewer > Windows Logs > Application

yes  i am  getting  same   error as Lance w7gj

is that the   solution  because i am  not   saving  either
here is  my error... mostly with  decoded.txt

full error message  and  STILL happening?

On 04/07/2021 15:40, Jim Pennino via groups.io wrote:

Re fake chips: I have no idea and don't care though u-blox might. The only features used by ntp is the output of NMEA sentences so any other capability the u-blox 8 series has is irrelevant to ntp. FYI u-blox makes dozens of different chips with different capabilities all of which identify as u-blox 8.

Hi Jim,

one issue with "fake" u-blox boards (note they usually have real u-blox GPS/GNSS receivers but lack on the rest of the board) is that some have insufficiently sized SPI memory chips and as a result cannot be upgraded to newer firmware versions. That can be annoying if a new satellite constellation needs to be supported, for example.

73
Bil
G4WJS.

On Sun, Jul 4, 2021 at 01:10 AM, Tad Danley wrote:

I downloaded WSJT-X v2.4.0 and configured it to work with my IC-7610 - using my settings for N1MM+ as a guide.  I am able to decode stations using FT8 on 50.313 but the radio will not key the transmitter.  I have Enable TX selected and the button is Red. The right side of the WSJT window shows I am transmitting with my 'transmissions' highlighted in yellow, but the rig does not key. Under Settings and the Radio tab I have the following set:

Rig is IC-7610, Serial port is Com 3, Baud rate is 115200, 8 data bits and 1 stop bit, Handshake is set to hardware, Force control lines are both unselected, PTT method is VOX, Transmit audio source is unselected, Mode is USB, Split is set to Fake it.  Under Soundcard the Input is defaulted to Microphone (USB Audio codec).

I would appreciate any help with what I need to change to get it to TX properly.  Thanks and 73!

I'm not sure if VOX PTT works when you're using the audio codec as the source of the incoming Tx audio; try selecting CAT for the PTT method in WSJT-X.

As has already been mentioned you should also be selecting the 7610's USB-D mode for operation rather than plain ol' USB, and you'll have also have to go into the settings menu and select 'USB' as the DATA1 MOD input (go to Menu -> Connectors -> MOD Input -> DATA1 MOD -> USB).

--
Martin G0HDB

Look at ICOM knowledge base for documentation on digital settings. For the IC 7300 setting power to 100% is recommended then use TF8 slider to set power out to desired. Green ALC is ok, just don’t go into red.  No ALC or little ALC  means no or little power out. Just look at power meter when transmitting. The power control is MAX power out, not a power control. I don’t know if this applies to 7610 but it probably does.

No ALC does not apply to all radios especially since FT8 is a constant power mode so read the manual. 
Ray
W8LYJ

Hello. I have same problem with same library in Ububtu 18. 

I had wsjtx 2.1.2 running fine on ubuntu 18. Then I went to update to 2.3.0 and it just never launched, although icon was there. I did uninstall and try several "tricks" but never launched. In the software center I had weird record saying I had 2.3.0 uninstalled and 2.1.2 installed. I did format my HD and install Ubuntu 18 from scratch to delete any inaccurate license record. Now with a clean fresh updated ubuntu 18, wsjtx 2.4.0 wont install (a bunch of dependency problems).
I have noticed that wsjtx.2.4.0...deb file is i386 for ubuntu 18, 32 bits, when ubuntu 18 is actually 64 bits (intell/amd 64). I am guessing there is the problem. The only wsjtx.2.4.0...deb file amd64 is stated for ubuntu 20, not 18.

I have narrowed down the error on installing wsjtx 2.4.0 on ubuntu 18 to the following:
"Unpacking wsjtx:i386 (2.4.0) ...
dpkg: dependency problems prevent configuration of wsjtx:i386:
wsjtx:i386 depends on libboost-log1.65.1."
This is preventing wsjtx to be completely installed. I do have wsjtx icon and when clicking to start, it just stays in sand-clock for a while and then I get a warning in ubuntu saying I have installed a package with unment dependencies. When I run the "fix" bay means of "partial upgrade" or by "sudo apt-get install -f" it automatically removes wsjtx because it is the problem.
“The following packages will be REMOVED:
wsjtx:i386”
The weird thing is that the libboost-log1.65.1 is actually installed as seen below:

ham@ham-V5-131:~$ apt list libboost-log1*

Listing... Done

libboost-log1.62-dev/bionic 1.62.0+dfsg-5 amd64

libboost-log1.62.0/bionic 1.62.0+dfsg-5 amd64

libboost-log1.65-dev/bionic,now 1.65.1+dfsg-0ubuntu5 amd64 [installed,automatic]

libboost-log1.65.1/bionic,now 1.65.1+dfsg-0ubuntu5 amd64 [installed]

 

ham@ham-V5-131:~$ cd Downloads

ham@ham-V5-131:~/Downloads$ sudo dpkg -i wsjtx_2.4.0_i386.deb

[sudo] password for ham:

Selecting previously unselected package wsjtx:i386.

(Reading database ... 190398 files and directories currently installed.)

Preparing to unpack wsjtx_2.4.0_i386.deb ...

Unpacking wsjtx:i386 (2.4.0) ...

dpkg: dependency problems prevent configuration of wsjtx:i386:

wsjtx:i386 depends on libboost-log1.65.1.

 

dpkg: error processing package wsjtx:i386 (--install):

dependency problems - leaving unconfigured

Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...

Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2) ...

Processing triggers for mime-support (3.60ubuntu1) ...

Processing triggers for man-db (2.8.3-2ubuntu0.1) ...

Errors were encountered while processing:

wsjtx:i386

ham@ham-V5-131:~/Downloads$

Any help? Thanks.

Re time1 vs time2: I am running the latest release of Meinberg and can state time1 does what it is supposed to do. If you are running an older version you should upgrade because many other bugs have been fixed.

Re cables: You can attach the VK-162 to your Pi if you don't have a serial GPS HAT and use it as a ntp server. There is a thumb drive receiver, VK-172, that uses the u-blox 7 chip set which eliminates the cables but isn't generally useful inside a building and has much more jitter than the VK-162.

Re fake chips: I have no idea and don't care though u-blox might. The only features used by ntp is the output of NMEA sentences so any other capability the u-blox 8 series has is irrelevant to ntp. FYI u-blox makes dozens of different chips with different capabilities all of which identify as u-blox 8.

Re Rubidium standard: The price I gave was for a frequency standard only. The price for the box with timekeeping ability is about $870, which should indicate why I haven't already tried one. GNSS-RB GPS GNSS Disciplined  Rubidium BG7TBL Rubidium Atomic Clock on e-bay.

I used HRD for many years(2010 al;l versions) and had no troubles, and none since logging since adding of WSJT-x FT8 and JTAlert a couple of years ago. Use what you like but avoid trashing others!
Bill W2CQ