Date   

locked Re: What to write in these two boxes

James Shaver (N2ADV)
 

True, Bill :)

On May 2, 2019, at 3:57 PM, g4wjs <bill.8@classdesign.com> wrote:

On 02/05/2019 20:29, James Shaver (N2ADV) wrote:
So best idea is to search for the participation rules for The RTTY RoundUp and for Field Day where the exchange information is outlined in detail.
Hi Jim and anonymous OP,

or you could hover your mouse pointer over the fields for some direct help.

73
Bill
G4WJS.



--
73
Bill
G4WJS.



locked Re: What to write in these two boxes

g4wjs
 

On 02/05/2019 20:29, James Shaver (N2ADV) wrote:
So best idea is to search for the participation rules for The RTTY RoundUp and for Field Day where the exchange information is outlined in detail.
Hi Jim and anonymous OP,

or you could hover your mouse pointer over the fields for some direct help.

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: FT4 on 7047

Radio K0HB
 

I’m not on that list, so missed the thread.

 

In the meantime, waiting until the next release is completely UNSAT.

 

If an operator is competent to test FT4, then (we must hope) that they are competent to turn the VFO to a more appropriate QRG. 

The excuse that we have to wait for the next release is a lame copout, and the digital haters will use it against us for years.

 

73, de Hans, KØHB
"Just a boy and his radio"™

 

From: James Shaver (N2ADV)
Sent: Thursday, May 2, 2019 7:32 PM
To: Support@hamapps.groups.io
Subject: Re: [HamApps] FT4 on 7047

 

There’s a 50+ response thread on this topic in the WSJTX Dev group on this topic and it’s already been noted that the suggested frequency table will be updated with the next release...

On May 2, 2019, at 3:25 PM, HH Brakob <kzerohb@...> wrote:

The selection of 7047 as a test QRG couldn’t be worse for our relationship with other hams.

 

It is smack-dab on top of the W1AW morse bulletins and code practice at 7047.5.  That usage of the QRG goes back to when Hiram was a puppy.

 

This must move NOW, or the digital haters will use it against us forever.

 

73, de Hans, KØHB
"Just a boy and his radio"™

 


--
73, de Hans, K0HB
"Just a Boy and his Radio"™


locked Re: FT4 on 7047

James Shaver (N2ADV)
 

There’s a 50+ response thread on this topic in the WSJTX Dev group on this topic and it’s already been noted that the suggested frequency table will be updated with the next release...


On May 2, 2019, at 3:25 PM, HH Brakob <kzerohb@...> wrote:

The selection of 7047 as a test QRG couldn’t be worse for our relationship with other hams.

 

It is smack-dab on top of the W1AW morse bulletins and code practice at 7047.5.  That usage of the QRG goes back to when Hiram was a puppy.

 

This must move NOW, or the digital haters will use it against us forever.

 

73, de Hans, KØHB
"Just a boy and his radio"™


locked Re: What to write in these two boxes

James Shaver (N2ADV)
 

This is really more suited for the WSJTX group rather than the HamApps group but I’ll copy and paste the response I put on Facebook to your post about this question:

“Nothing unless you’re in contest mode - for Roundup (RU) for US stations it’s their state and for DX it is a serial number (more info can be found in the RTTY RoundUp website which can be found via a brief Google search).  For Field day, nothing again unless you’re participating in field day and are using FT8 - then it would be the appropriate class information (more info is on the ARRL site under Field Day).”

So best idea is to search for the participation rules for The RTTY RoundUp and for Field Day where the exchange information is outlined in detail.  

73,

Jim S. 
N2ADV

On May 2, 2019, at 3:14 PM, f1dsz@... wrote:

What to write in these two boxes
for the contests.
Thank you F1DSZ
<ontest réglages 2.jpg>


locked FT4 on 7047

Radio K0HB
 

The selection of 7047 as a test QRG couldn’t be worse for our relationship with other hams.

 

It is smack-dab on top of the W1AW morse bulletins and code practice at 7047.5.  That usage of the QRG goes back to when Hiram was a puppy.

 

This must move NOW, or the digital haters will use it against us forever.

 

73, de Hans, KØHB
"Just a boy and his radio"™

_._,_._,_

 


--
73, de Hans, K0HB
"Just a Boy and his Radio"™


locked Re: FT4

davidg7hjx@...
 

I hear them too, I think its coming from WSJT-X, I hear it using FT4 with or without JTAlert.


locked What to write in these two boxes

Jean-Claude F1DSZ
 

What to write in these two boxes
for the contests.
Thank you F1DSZ


locked Odp: [HamApps] New JTAlert 2.13.4 available.

Henryk SP4L
 

So, but I think about ver 2.11.5. I use it and works good (but not decode only FT4 call).
 
 
Henryk
SP4L
 

Data: 2 maja 2019 07:09
Temat: Odp: [HamApps] New JTAlert 2.13.4 available.

Laurie,
 
what do you think about the new version (FT4 mode) for old Windows XP?
 
Many radiohams still use use this.
 
Henryk
SP4L
 

 


locked Re: JTAlert 2nd or 3rd instance does not start if WSJT-X and JTDX are running in parallel

Uwe, DG2YCB
 

Thanks Laurie.
Further question: Does JTAlert support multiple instances of JTDX (without wsjtx) in parallel)? I've tried to run 2 instances of JTDX and started JTAlert for them. The 2 instances of JTDX work, but when trying to open the 2nd instace of JTAlert it comes the following error message: (The instances of JTDX are using separate UDP server port numbers)


73 de Uwe, DG2YCB


locked Re: Odp: [HamApps] New JTAlert 2.13.4 available.

Michael Black
 

FT4 is minimally supported in 2.13.14

You may as well upgrade your machine as even WSJT-X is going to be incompatible with WinXP in the future.  The 64-bit version already isn't compatible...and it's notably faster during decode than the 32-bit version.

Trying to support older OS's that can't use newer software tools just holds back everything.  WSJT-X, for example, is having to upgrade the Qt library due to a bug in current MacOS so the upgrade path is mandatory to support newer systems and let the old ones just stay with what they have.

de Mike W9MDB




On Thursday, May 2, 2019, 12:09:42 AM CDT, Henryk Skalimowski <sp4l@...> wrote:


Laurie,
 
what do you think about the new version (FT4 mode) for old Windows XP?
 
Many radiohams still use use this.
 
Henryk
SP4L
 


locked Re: FT4

Neil Foster
 

Now that makes sense Laurie....sometimes the simple things are obvious and we just do not see it.
Thanks
Neil   N4FN


locked Re: JTAlert 2nd or 3rd instance does not start if WSJT-X and JTDX are running in parallel

JTAlert Support (VK3AMA)
 

On 2/05/2019 8:55 pm, Uwe wrote:
I am currently doing some tests where I am running WSJT-X and JTDX in parallel. Works well, however I have troubles starting JTAlert for all of them in parallel. Once WSJT-X is running, JTDX is not recognized as running. When JTDX is running alone JTAlert is working together with it in a normal way. Of course I am starting JTAlert for WSJT-X via "WSJT-X - JTAlertX" and JTAlert for JTDX via "JTDX - JTAlert" link, and under settings I ensured that both are using separate UDP server port numbers (see screenshot).
What am I doing wrong?
73 de Uwe, DG2YCB

Running multiple instances of JTAlert against both WSJT-X and JTDX simultaneously is not supported

From the 2.10.0 (21-JUL-2017) release notes
    - The multi-instance support has also been changed. Running multiple copies
       of JTAlert against both WSJT-X and JTDX simultaneously is not supported.
       You can run multiple instances of JTAlert against either WSJT-X OR JTDX
       only. Both types of applications can be running simultaneously on the PC,
       but only one JTAlert operating mode (against WSJT-X or JTDX) is allowed.

de Laurie VK3AMA


locked JTAlert 2nd or 3rd instance does not start if WSJT-X and JTDX are running in parallel

Uwe, DG2YCB
 

Hi,
I am currently doing some tests where I am running WSJT-X and JTDX in parallel. Works well, however I have troubles starting JTAlert for all of them in parallel. Once WSJT-X is running, JTDX is not recognized as running. When JTDX is running alone JTAlert is working together with it in a normal way. Of course I am starting JTAlert for WSJT-X via "WSJT-X - JTAlertX" and JTAlert for JTDX via "JTDX - JTAlert" link, and under settings I ensured that both are using separate UDP server port numbers (see screenshot).
What am I doing wrong?
73 de Uwe, DG2YCB

Btw. In my head-to-head comparison JTDX wins the race in terms of decoding sensitivity.


locked Re: Odp: [HamApps] New JTAlert 2.13.4 available.

g4wjs
 

On 02/05/2019 06:09, Henryk Skalimowski wrote:
Laurie,
 
what do you think about the new version (FT4 mode) for old Windows XP?
 
Many radiohams still use use this.
 
Henryk
SP4L

Henryk,

WSJT-X will be dropping support for Windows XP and Vista soon, the new 64-bit version for Windows has already dropped XP support. The tools that Laurie is using for new development do not support them either, continuing to support obsolete operating system versions is counter productive and reduces functionality and quality for those that feel insecure operating systems should be replaced.


--
73
Bill
G4WJS.


locked Odp: [HamApps] New JTAlert 2.13.4 available.

Henryk SP4L
 

Laurie,
 
what do you think about the new version (FT4 mode) for old Windows XP?
 
Many radiohams still use use this.
 
Henryk
SP4L
 


locked Re: FT4

JTAlert Support (VK3AMA)
 

On 1/05/2019 9:32 am, Neil wrote:
I have downloaded the new version of JTAlert (.4) and I have only listened to FT4 and not tried to TX. I notice a periodic tone  happening and wonder if this is generated by JTAlert or is it from WSJT-X? I never had that before
Thanks Laurie for a great program addition and support
Neil   N4FN
The easiest way to test if it is JTAlert generated audio is turn mute the sound in JTAlert. Repeatedly click the "Sound ..." menu in the title bar until it says "Sound OFF". If the tone persists it is not coming from JTAlert.

de Laurie VK3AMA


locked Re: TX not enabled

JTAlert Support (VK3AMA)
 

On 2/05/2019 6:55 am, Michael Wheatley wrote:
I'm running JTAlertX 2.13.4, which I start after WSIT-X has been started.  Often, if I click a call sign displayed by JTAlertX, it is not enabled for TX in WSIT-X.  If I restart JTAlertX, the correct behavior is restored.

Any suggestions to fix this?

Michael -- KM6LHD

There is no fix because there is nothing to fix.

Enabling TX within WSJT-X is the exclusive responsibility of WSJT-X. The WSJT-X api doesn't allow for third party applications like JTAlert to enable TX. If the WSJT-X DX Call is changing in response to a Callsign click in JTAlert then all is working as it should.

Internally WSJT-X makes the decision as to whether TX should be enabled depending on the decode type and I believe the operating mode (I am not certain on that last part however).

de Laurie VK3AMA


locked New jt-alert

SEAN MURDOCH <sean195@...>
 

Great job Laurie , new update. Fast. Just need eqsl to catch up.  You deserve a medal 🥉. Love jt alert   Thanks again for your hard work. 😁 


locked Re: New JTAlert 2.13.4 available.

John
 

Laurie,

Never give in to pressure from your fans, it's ready when it is ready and not
before.
They'll wait... because they have to wait.

John
VE3KKQ

---------- Original Message ----------
From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@gmail.com>
Date: May 1, 2019 at 5:12 PM


On 1/05/2019 11:49 pm, Michael Black via Groups.Io wrote:
It appears the CQ "*" and "#" indicators are not working for FT4.

de Mike W9MDB
Mike,

That's a defect.
This is what happens when, in an effort to appease the clamouring
masses, a release is fast-tracked without adequate testing.

This is now corrected for the next release.

de Laurie VK3AMA



15941 - 15960 of 39949