Date   

locked VS: [WSJTX] #GeneralGroupInfo Problem Decoding. #GeneralGroupInfo

Reino Talarmo
 

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


locked Re: Problem with SCU 17 CAT control on FT450D #Cat_RigControl

NR4U Bob AFMARS
 

Hello Austin,
Saturday, May 22, 2021, 1:39:38 PM, you wrote:
----------------------------------------------------
My settings are as follows:
Rig: Yaesu FT450
Serial Port: /dev/tty.SLAB_USBtoUART
Baud: 38400
Data Bits: 8
Stop Bits: 1
Handshake: Default
PTT: CAT
Mode: Data/Pkt
Split: None
----------------------------------------------------
Hi Austin.
I also have an active FT450 working with wsjtx

though I am using FLRig as "Radio" in the WSJTx settings ....

My settings are RTS not CAT, as the FT450 seems to like RTS

And I have Data/Pkt as-well-as Fake-It for the split.

Am also using the SCU-17 happily with the FT-450.

I just tested a few QRG changes inside the WSJTx pull-down and didn't see any jump from A->B->A

--
Best regards,
Bob KD7YZ



--
--
Bob KD7YZ in NE Kentucky


locked #GeneralGroupInfo Problem Decoding. #GeneralGroupInfo

 

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 ??
--
Thanks 73's de NU4N/Dave


locked Re: Receive only decoder #general

Tom V. Segalstad
 

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?

 

The SignalID app can be downloaded from «Google Play» or from the following web sites:

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

 

SignalID for Android - APK Download

 

 

Fra: Mike
Sendt: søndag 23. mai 2021 kl. 12.17
Til: main@WSJTX.groups.io
Emne: [WSJTX] Receive only decoder #general

 

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

 


--
Tom (LA4LN)


locked Re: #JT4 and now #Q65 Decoding of very high S/N #JT4 #Q65

Andy Talbot
 

And now, having just modded the PIC code to generate Q65
Pure tones, no noise - NO DECODING whatsoever, ever, never,  to the extent I was pointlessly chasing up errors in the code and wasted over an hour of my life :-(

Add in some noise and straight decodes,
So the Q65 decoder, unlike the JT4 one,  needs background noise.



On Sat, 22 May 2021 at 17:09, Andy Talbot <andy.g4jnt@...> wrote:
Update
If I add noise the frequency measurement works properly.
But the S/N doesn't

Is S/N reporting supposed to be implemented in JT4 wider modes?
I do very vaguely seem to recall a comment once that it was not done at all.



On Sat, 22 May 2021 at 16:41, Andy Talbot <andy.g4jnt@...> wrote:
I've been testing a new JT4G beacon source , a single PIC chip generating quadrature audio tones for directly feeding a quad-upconverter.  Testing by feeding the tone output directly into the soundcard, running Ver 2.4.0 RC4

In the past, with earlier versions of WSJT-X,  the JT4 decoder hasn't always been very happy with pure tones and very high S/N. and would often miss decodes.  The situation resolved itself when the S/N was degraded by deliberately adding in noise from an audio noise generator

Now, though, with the latest decoder behaviour with a pure tone input is different.    Decoding is always successful - there are no missed decodes - but the frequency estimation and  the S/N reported are way-out.   I use exactly 1000Hz for tone 0 , but the decoder reports a spread from 914 to 1050 at least, and S/N is reported as -15 or so, when it is really a very high positive value.

Getting the S/N wrong I can understand why it may be happening, with the S/N estimation going off scale with no noise to measure, but the random value of frequency reporting is a new one.   Why is this ?

See the  attached screen shots


locked Receive only decoder #general

Mike
 

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


locked Cannot use /P in callsign when using JT65 and JT9 modes #JT65 #JT9 #IssueReport

Haris SV1GRB
 

Hello to all, I would like to mention a strange behavior regarding the use of a specific type 1 suffix in the callsign.

The list of type 1 suffixes indicates that /P is a valid type 1 suffix:
image.png
When /P is used in callsign on JT65 and JT9 modes, the /P suffix is present in all generated messages so there is no room for the third word (reports,  RRR and 73) to be transmitted.
image.png
The Tx1 is transmitted normally as G1ABC SV1GRB/P
The Tx2 instead of G1ABC SV1GRB -15 is transmitted as G1ABC SV1GRB/P
The Tx3 instead of G1ABC SV1GRB R -15 is transmitted as G1ABC SV1GRB/P
The Tx4 instead of G1ABC SV1GRB RRR is transmitted as G1ABC SV1GRB/P
The Tx5 instead of G1ABC SV1GRB 73 is transmitted as G1ABC SV1GRB/P
The Tx6 is transmitted normally as CQ SV1GRB/P

When using another type 1 suffix such as /3, the suffix is correctly present only in TX1 and TX6 and everything is transmitted FB.
image.png

Currently using version is 2.3.1.

73
Haris
SV1GRB


locked Cannot use /P in callsign when using JT65 and JT9 modes #JT65 #JT9 #IssueReport

Haris SV1GRB
 

Hello to all, I would like to mention a strange behavior regarding the use of a specific type 1 suffix in the callsign.

The list of type 1 suffixes indicates that /P is a valid type 1 suffix:
image.png
When /P is used in callsign on JT65 and JT9 modes, the /P suffix is present in all generated messages so there is no room for the third word (reports,  RRR and 73) to be transmitted.
image.png
The Tx1 is transmitted normally as G1ABC SV1GRB/P
The Tx2 instead of G1ABC SV1GRB -15 is transmitted as G1ABC SV1GRB/P
The Tx3 instead of G1ABC SV1GRB R -15 is transmitted as G1ABC SV1GRB/P
The Tx4 instead of G1ABC SV1GRB RRR is transmitted as G1ABC SV1GRB/P
The Tx5 instead of G1ABC SV1GRB 73 is transmitted as G1ABC SV1GRB/P
The Tx6 is transmitted normally as CQ SV1GRB/P

When using another type 1 suffix such as /3, the suffix is correctly present only in TX1 and TX6 and everything is transmitted FB.
image.png

Currently using version is 2.3.1.

73
Haris
SV1GRB


locked Re: Intl. WSPR Beacon Project #Beacons

Bob K4RCG
 

RR Martin.  It is an interesting project.

73 de Bob
K4RCG

On Sun, May 23, 2021 at 1:44 AM Roland <roland@...> wrote:
Thanks Bob, currently reaching out to HAM Radio Clubs around the world to draw some interest and to promote the new Project. I already made a post on the Wsprnet.org forum.
Much appreciated if you could spread the message to anyone who is interested. The Project website can be found here https://github.com/HB9VQQ/WSPRBeacon just as a reminder.

73 fer now
Roland



locked Re: Calling with TX2 #FT8

Jim Shorney
 

OK, time for this discussion to END.

73

-Jim
NU0C

On Sun, 23 May 2021 02:48:42 +0000 (UTC)
"K8BL BOB LIDDY" <k8bl@...> wrote:

it's selfish andinconsiderate


locked Re: Calling with TX2 #FT8

K8BL BOB LIDDY <k8bl@...>
 

Bill,

Thanks for pointing those things out. Yes, there are many helpful
and often necessary things provided when an answering Station is
gracious enough to provide their Grid. That's why it's selfish and
inconsiderate to answer merely with TX2 to save themselves a few
seconds of turnaround.

73,   Bob  K8BL


On Saturday, May 22, 2021, 10:17:28 PM EDT, Bill, WB6JJJ <bill@...> wrote:


The grid allows WSJT-X to show their beam heading so I can turn the antenna.  Also, JTAlert will quickly / automatically provide their name and grid.  But the grid displayed in JTAlert (from QRZ.com) isn’t always their correct grid…

Bill
WB6JJJ 



On May 22, 2021, at 6:41 PM, K8BL BOB LIDDY <k8bl@...> wrote:


IMHO...  I consider it rude and inconsiderate to purposely avoid using the proper
 protocol that was specifically designed to provide the Grid to the station you are
 calling just to save a few seconds of turnaround between timeslots. The software
 was designed such that CQ'ing Stations call using TX6 and answering Stations
 respond with TX1, including their Grid. If you answer someone's CQ by using
 improper protocol, you are purposely refusing to provide them with info that they
 may be seeking by being on the radio in the first place. You are refusing to tell
 them your Grid, which they may be collecting for various Awards, and you are
 refusing to give them an indication of your location, which would tell them where
 their signal is reaching. You might as well give them a crude gesture at the same
 time. In many instances, that forces the CQ Station to look up your info on-line
 before they'll log it in WSJT and/or their Station Log. That effort takes more time
 than the 15 seconds saved by NOT  providing your Grid when rudely calling by
 using TX2! After reading all the comments here about using TX2 to call Stations
 and all the lame/weak excuses for doing so, I'm seriously considering NOT logging
 QSOs that call using TX2. I'll work them, but I think I won't Log them. That would
 be just as rude and inconsiderate.

GL/73,   Bob  K8BL               (Let the flaming begin. 3...2...1)



On Saturday, May 22, 2021, 04:54:00 PM EDT, Reino Talarmo <reino.talarmo@...> wrote:









locked Re: Calling with TX2 #FT8

Bill, WB6JJJ
 

The grid allows WSJT-X to show their beam heading so I can turn the antenna.  Also, JTAlert will quickly / automatically provide their name and grid.  But the grid displayed in JTAlert (from QRZ.com) isn’t always their correct grid…

Bill
WB6JJJ 



On May 22, 2021, at 6:41 PM, K8BL BOB LIDDY <k8bl@...> wrote:


IMHO...  I consider it rude and inconsiderate to purposely avoid using the proper
 protocol that was specifically designed to provide the Grid to the station you are
 calling just to save a few seconds of turnaround between timeslots. The software
 was designed such that CQ'ing Stations call using TX6 and answering Stations
 respond with TX1, including their Grid. If you answer someone's CQ by using
 improper protocol, you are purposely refusing to provide them with info that they
 may be seeking by being on the radio in the first place. You are refusing to tell
 them your Grid, which they may be collecting for various Awards, and you are
 refusing to give them an indication of your location, which would tell them where
 their signal is reaching. You might as well give them a crude gesture at the same
 time. In many instances, that forces the CQ Station to look up your info on-line
 before they'll log it in WSJT and/or their Station Log. That effort takes more time
 than the 15 seconds saved by NOT  providing your Grid when rudely calling by
 using TX2! After reading all the comments here about using TX2 to call Stations
 and all the lame/weak excuses for doing so, I'm seriously considering NOT logging
 QSOs that call using TX2. I'll work them, but I think I won't Log them. That would
 be just as rude and inconsiderate.

GL/73,   Bob  K8BL               (Let the flaming begin. 3...2...1)



On Saturday, May 22, 2021, 04:54:00 PM EDT, Reino Talarmo <reino.talarmo@...> wrote:






locked Re: Intl. WSPR Beacon Project #Beacons

Roland
 

Thanks Bob, currently reaching out to HAM Radio Clubs around the world to draw some interest and to promote the new Project. I already made a post on the Wsprnet.org forum.
Much appreciated if you could spread the message to anyone who is interested. The Project website can be found here https://github.com/HB9VQQ/WSPRBeacon just as a reminder.

73 fer now
Roland


locked Re: Calling with TX2 #FT8

K8BL BOB LIDDY <k8bl@...>
 

IMHO...  I consider it rude and inconsiderate to purposely avoid using the proper
 protocol that was specifically designed to provide the Grid to the station you are
 calling just to save a few seconds of turnaround between timeslots. The software
 was designed such that CQ'ing Stations call using TX6 and answering Stations
 respond with TX1, including their Grid. If you answer someone's CQ by using
 improper protocol, you are purposely refusing to provide them with info that they
 may be seeking by being on the radio in the first place. You are refusing to tell
 them your Grid, which they may be collecting for various Awards, and you are
 refusing to give them an indication of your location, which would tell them where
 their signal is reaching. You might as well give them a crude gesture at the same
 time. In many instances, that forces the CQ Station to look up your info on-line
 before they'll log it in WSJT and/or their Station Log. That effort takes more time
 than the 15 seconds saved by NOT  providing your Grid when rudely calling by
 using TX2! After reading all the comments here about using TX2 to call Stations
 and all the lame/weak excuses for doing so, I'm seriously considering NOT logging
 QSOs that call using TX2. I'll work them, but I think I won't Log them. That would
 be just as rude and inconsiderate.

GL/73,   Bob  K8BL               (Let the flaming begin. 3...2...1)



On Saturday, May 22, 2021, 04:54:00 PM EDT, Reino Talarmo <reino.talarmo@...> wrote:



locked Re: Calling with TX2 #FT8

K8BL BOB LIDDY <k8bl@...>
 

Lance... Vy Cool! TNX for sharing. Drive Safe!  de  Bob K8BL

On Saturday, May 22, 2021, 02:35:39 PM EDT, Lance Collister, W7GJ <w7gj@...> wrote:


I am on a month long road trip across the country on 6m from the car, and I always call CQ with my current grid. Funny how many people answer me ignoring my grid and assuming I am still in Montana!  But I always show where I am.  Right now I am on the road to eastern MASS. I sure have been impressed with some of the 6m Es openings to EU and AF that I have gotten in on with my 150w and roof mounted Squalo! FT8 is very handy to use when driving (especially when XYL is behind the wheel- HI!). GL and VY 73, Lance

On 5/21/2021 21:55, Larry Banks via groups.io wrote:


locked VS: VS: [WSJTX] Calling with TX2 #FT8

Reino Talarmo
 

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


locked Problem with SCU 17 CAT control on FT450D #Cat_RigControl

Austin 2E0MNV
 

Hi,
Wondering if someone can help.  I packed all my gear away for three months and recently set it back up.
Now when I change frequency band in WSJT-X using cat control, the rig momentarily flickers between VFO A and B before settling on VFO A. It never used to do this before and none of my settings have changed.  I've tried a re-install, but I can't seem to re-install cleanly (an additional problem).  It remembers all my settings after a new install.  (This is not the primary issue however.  My issue is the flickering between VFO's)

My settings are as follows:

Rig: Yaesu FT450
Serial Port: /dev/tty.SLAB_USBtoUART
Baud: 38400
Data Bits: 8
Stop Bits: 1
Handshake: Default
PTT: CAT
Mode: Data/Pkt
Split: None

It never used to happen and none of my settings have been changed, neither on the radio or the rig and it only happens in WSJT-X. It doesn't happen in Fldigi, JS8call, or JTDX.  It's getting on my nerves as it won't change frequency cleanly, always with flickering of the relays in the rig and only on WSJTX.  

Anyone encountered this and know a solution?

--
Austin
2E0MNV


locked Re: Calling with TX2 #FT8

Lance Collister, W7GJ
 

I am on a month long road trip across the country on 6m from the car, and I always call CQ with my current grid. Funny how many people answer me ignoring my grid and assuming I am still in Montana!  But I always show where I am.  Right now I am on the road to eastern MASS. I sure have been impressed with some of the 6m Es openings to EU and AF that I have gotten in on with my 150w and roof mounted Squalo! FT8 is very handy to use when driving (especially when XYL is behind the wheel- HI!). GL and VY 73, Lance

On 5/21/2021 21:55, Larry Banks via groups.io wrote:
Hi Kai,
 
You haven’t been following this thread.  This is exactly what I said: The grid transmitted is the real one.

73 -- Larry -- W1DYJ

 
From: Kai-KE4PT
Sent: Friday, May 21, 2021 17:42
Subject: Re: [WSJTX] Calling with TX2 #FT8
 
Larry,
You QSO'd with the station, not with QRX.com!
Simply log the QSO as sent/received on LOTW. His LOTW signing should contain his true grid that he is signing from.
73,
Kai, KE4PT

On 5/21/2021 13:04, Larry Banks via groups.io wrote:
Hi Bob,
 
How do you handle a station that is in a different grid (vacation, etc.) than what is in QRZ?  The grid transmitted is the real one.

73 -- Larry -- W1DYJ

 
Sent: Friday, May 21, 2021 12:24
Subject: Re: [WSJTX] Calling with TX2 #FT8
 
It's so quick and easy to look it up on QRZ . com or QRZCQ . com
 
If one doesn't have it, the other one usually will. Why waste a QSO?
 
de   Bob  K8BL
 
 
On Friday, May 21, 2021, 11:55:58 AM EDT, mailto:careyfisher@... wrote:
 
 
Why not?
 
On Fri, May 21, 2021 at 10:36 AM Pat via groups.io <n7uvh=yahoo.com@groups.io> wrote:
I do not log qso,s with no grid information 


 
 
--
Carey Fisher
 

--
73, Carey, WB4HXE
















-- 
Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, FO/W7GJ, TX7MB)
P.O. Box 73
Frenchtown, MT   59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL: http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11/6m DXCC #815

Interested in 6m EME?  Ask me about subscribing to the Magic Band EME
email group, or just fill in the request box at the bottom of my web
page (above)!


locked Re: VS: [WSJTX] Calling with TX2 #FT8

Martin G0HDB
 

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


locked Re: #BugReport DIGU Changes to DIGL in V 2.3.1 #IssueReport

Stan K4SBZ
 

Hi Bill,

Switched to Mode->None. Works.

Thanks.

73,
--
Stan, K4SBZ

11881 - 11900 of 36834