I am running the latest version. I have been using Dimension as may time syn for years.Today I am getting Double decoding ?? I am making contacts. My computer has enuf horsepower to decode quickly. Any thoughts ??

Hi Dave,
What you mean by double decoding. Do you mean exactly the same message, but on two different frequencies? If so are those two messages with a frequency difference 120 Hz or a multiple of 120 Hz? Is there a large difference at S/N of those decodes? Do you have a waterfall or .wav file on those instances to share?
In earlier versions of wsjt-x that was quite ‘normal’, at least v2.3.1 is difficult encourage to decode clear 120 Hz (or 100 Hz in Europe) next to the main transmit frequency, it prefers strongly the correct one.
73, Reino OH3mA

Hi Mike

There is an app for PC, and for mobile phone (at least for Android type phones), which is able to decipher a number of digital modes. It is called «SignalID» for «Automatic Radio Signal Identification».

SignalID can at this time recognize the following digital modes:

RTTY (85 Hz, 170 Hz, 450 Hz, 850 Hz, and amateur 170 Hz).

STANAG 4285 (GEN, SYS3000 FEC, 8PSK, TFC, IDLE, SYS3000).

FT4

FT8

The authors of this app are working to include more kinds of digital modes.

And there may be other apps doing this digital deciphering also?

https://github.com/Neosama/SignalID

or

https://apkpure.com/signalid-automatic-radio-signal-identification/com.tortillum.signalid

When you start the app, you will see a button labeled «0 – 30 MHz», hence it is set for HF and frequencies below.

If you press that button, the SignalID app will work for modes used from 30 MHz and upwards in frequency.

You get more info by pressing the «+» button in the upper left corner of the screen.

See the copy of the screen in the picture below.

73 and good luck from Tom, LA4LN

This may be a stupid question - But in scouring the bands I hear so many data signals and I look for a possible decode based on what I think they sound like. As Im predominately a 2M up and we've already removed modes from WSJT-X (JT6M FSK441 for example but not in MSHV) and there are limited modes I struggle to identify them and as some are meteor pings its hard to go back over the recording if one was made and replay and decode it.

So my question is - is it possible to have a receive only system that will run through all the modes and give a predicted match. I understand that all the protocols and code is probably available but today my programming skills are diminishing (too old) so lets see if anyone out there can provide a solution Id like to help in any way I can.

Mike
GD6ICR

Hello Martin, you answered the important difference to many other operators, hi! So only some will know grid by just double clicking, I assume.

As reminded in the text in the User Guide “reasonably stable”, I take it that they don’t change their locator often.
Actually I made a mistake, I should have referred to wsjtx_log.adi not all.txt, hi!

73, Reino OH3mA

Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta Martin G0HDB
Lähetetty: 22 May 2021 20:19
Vastaanottaja: main@WSJTX.groups.io
Aihe: Re: VS: [WSJTX] Calling with TX2 #FT8

On Sat, May 22, 2021 at 05:16 PM, Reino Talarmo wrote:

Martin,

Do you always Add a new call into your CALL3.TXT, when you have QSO?
Most of us don’t use that feature at all,  only ALL.TXT.

73, Reino OH3mA

Hello Reino, whenever I work a new station, and often when I've copied a new one but haven't yet worked it, I use the 'Add' button to put the station's callsign and grid into the 'database' which is described thus in the WSJT-X User Guide:

"The program can maintain a database of callsigns and locators for future reference. Click Add to insert the present call and locator in the database; click Lookup to retrieve the locator for a previously stored call. This feature is mainly useful for situations in which the number of active stations is modest and reasonably stable, such as EME (Earth-Moon-Earth) communication. The callsign file name is CALL3.TXT."

I believe the ALL.TXT file is essentially a journal of the decodes of incoming signals and all the outgoing transmissions and, as far as I'm aware, isn't read by the s/ware for any 'database' purposes (but I expect Bill etc will correct me on that if necessary!).  Certainly, when I rename the ALL.TXT file, typically at the end of each month, so that a completely new one is created when WSJT-X is next started I don't lose all the callsign and locator details of stations previously added to the database because they're held in CALL3.TXT.

73
--
Martin G0HDB