Date   

Re: Subscribe problem

Neil Foster
 

Hi Dan
TNX for the reply. That was a typo on my "olde" fingers. I meant to type JT Alert...sorry about that.
Neil


A giant step up !

Jim Cooper
 

Gotta do a bit of bragging tonight !!

For a year, I've had my FT8 setup software
running on one of the square black desktop PCs
like we have a the club.  A year ago it was doing
fairly well with the FT8 load; but both WSJT-X
and JTAlert have been constantly adding more
and more features and still expecting everything
to be processed in less then 2 or 3 seconds at the
end of each FT8 cycle. 

I was seeing a lot of receive cycles being DROPPED
and watching the waterfall I could actually see the
pauses, where the cpu choked and so nothing was
processed in that gulp.  So it was becoming more and
more frustrating, especially while in a QSO and the
receive cycle blanked so another Tx of the same info
and eventually a good receive cycle.

And fairly recently I upgraded the PC I've been using
for my webinar recording gigs to one with better video
processing and a really good cpu -- which left the
previous recording PC, which is not so bad on processing,
open for new applications ...  like maybe FT8!!

Long story, shortened a bit here ...  after a few frustrations
like no audio to the Tx ... and JTalert not talking/receiving
with WSJT-X, etc.  everything finally came together ...
and what a difference!!!    Have not seen a receive cycle
skipped all night, and everything is perky sweet.   ;))

Then I decided that since I have a monitor screen with
several different inputs, selectable by a menu, why not put
the big screen on FT8 along with the other two screens that
were already on the PC ...  so now I have THREE monitors
and lots of room for all the FT8 windows -- including the new experimental Callsign window in JTalert.

And here's what it looks like, except now I have
"Simon's Gray Line World Map" on the left half of the
upper screen, which is the 'hamapps' "my call spotted"
chart on the right.

graphic

And a really big, awesome load of thanks to the generous hams who spend much of their life supporting and enhancing these two software packages ...  WSJT-X and JTalert ---
especially to Laurie in Australia who must have no other life
but helping users with their JTalert problems, while he is
constantly adding and improving features.  THANKS Guys.

Jim  W2JC


  


Re: Subscribe problem

d_ziolkowski
 

Neil

wrong group. That said you can log in your gmail from any computer, you don't need another email. 

Dan KC2STA

On Mon, Oct 26, 2020 at 5:26 PM Neil Foster <archernf@...> wrote:

  Laurie,
I have a new second PC and I am trying to subscribe to WSJT reflector with a different email address. I am subscribed on my other PC with a different email and want to keep that as is. I have been unable to do so under this email  n4fn.g0nbj@.... What could I be doing wrong?
Thanks Neil  G0NBJ

 



--
Dan Ziolkowski KC2STA
SKCC #4290T
Ubuntu LINUX


Subscribe problem

Neil Foster
 


  Laurie,
I have a new second PC and I am trying to subscribe to WSJT reflector with a different email address. I am subscribed on my other PC with a different email and want to keep that as is. I have been unable to do so under this email  n4fn.g0nbj@.... What could I be doing wrong?
Thanks Neil  G0NBJ

 


Re: unable to communicate with the WSJT-x Process

HamApps Support (VK3AMA)
 

On 27/10/2020 7:40 am, John Wiener wrote:
here is the error message:
Unable to communicate with the wsjt-x.  UDP port 2237, IP address: 192.168.200.233
Values read from wsjt-x config file...
C:\Users\Dr.John\AppData\local\wsjt-x/ini
wsjt-x detected instance...
Process window tgitle: wsjt-x v2.2.2
Process command line: 'c:\wsjt\wsjtx\bin\wsjtx.exe
It worked yesterday   Hmmm. AFAIK, nothing has changed
Thanks!
John

Likely a PC Protection software update is blocking the comms. A PC restart may help, especially if your running Win10

Since JTAlert requires WSJT-X to be running on the same PC, try changing the UDP Server address to "127.0.0.1" or better still change to using a multicast address like "239.255.0.0"

de Laurie VK3AMA


unable to communicate with the WSJT-x Process

John Wiener
 

Hi.  I know this has been addressed before but I didn't understand the solution. I am running JTAlert 2.16.14
here is the error message:
Unable to communicate with the wsjt-x.  UDP port 2237, IP address: 192.168.200.233
Values read from wsjt-x config file...
C:\Users\Dr.John\AppData\local\wsjt-x/ini
wsjt-x detected instance...
Process window tgitle: wsjt-x v2.2.2
Process command line: 'c:\wsjt\wsjtx\bin\wsjtx.exe
It worked yesterday   Hmmm. AFAIK, nothing has changed
Thanks!
John

 


Re: JTAlert seems to be in a loop

docdga@...
 

Thank you very much that did the trick.


 Dawson Andrews 

KI5IMY

 


Re: Request for callsign to be changed #HamSpots

Antony
 

Congratulations Graham! 73, Antony G4CUS


Re: JTAlert seems to be in a loop

HamApps Support (VK3AMA)
 

On 26/10/2020 1:19 pm, docdga@... wrote:
I have   wsjt-x  gridtracker and JTalert running on my machine. JTalert lets me know that I have a wanted contact. I click on the contact in JTalert that initiates a transmit  in wsjt-x. Once the contact is confirmed and wsjt-x prompts me to log when I click OK JTalert starts telling me that it successfully logged the contact multiple times and seems to be in a loop I have to kill JTalert.. I have wsjt-x logging to Ham Radio Deluxe  JTalert is  logging to standard Adif file. Also there are nine or 10 incomplete  entries in Ham Radio Deluxe. There is one complete entry.

OM (Name? Callsign?)

WSJT-X doesn't log to HRD and if you have JTAlert logging to an ADIF file than the HRD logging must be coming from GridTracker.
You will likely find that your ADIF file also contains duplicate entries.

It sounds like you have JTAlert set to resend UDP packets to the same port that WSJT-X is sending to, which is the port JTAlert is listening to, so you have JTAlert resending UDP packets back to itself, thus the looping.

Turn off the "Resend WSJT-X UDP ..." setting in JTAlert will fix your issue.

   

If you use this Resend function for GridTracker than set it to a port DIFFERENT from the UDP Server port set in WSJT-X.

de Laurie VK3AMA


JTAlert seems to be in a loop

docdga@...
 

I have   wsjt-x  gridtracker and JTalert running on my machine. JTalert lets me know that I have a wanted contact. I click on the contact in JTalert that initiates a transmit  in wsjt-x. Once the contact is confirmed and wsjt-x prompts me to log when I click OK JTalert starts telling me that it successfully logged the contact multiple times and seems to be in a loop I have to kill JTalert.. I have wsjt-x logging to Ham Radio Deluxe  JTalert is  logging to standard Adif file. Also there are nine or 10 incomplete  entries in Ham Radio Deluxe. There is one complete entry.

 


Re: Request for callsign to be changed #HamSpots

Laurie, VK3AMA
 

Done.

de Laurie VK3AMA


On 26/10/2020 12:23 am, Graham Bevan via groups.io wrote:
Hi,
Could you please changed the callsign for my HamSpots account from M7MAK to 2E0YCX?

Kind Regards,
Graham


Request for callsign to be changed #HamSpots

Graham Bevan
 

Hi,
Could you please changed the callsign for my HamSpots account from M7MAK to 2E0YCX?

Kind Regards,
Graham


locked Re: #FT8/JTAlert

Dave Garber
 

glad to help...


Dave Garber
VE3WEJ / VE3IE


On Sun, Oct 25, 2020 at 11:19 AM Wes Elton <wes@...> wrote:

 

Thanks Dave, I’d misunderstood Laurie’s instructions!

All working well now.

73,

Wes.

GW3RIH

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Dave Garber
Sent: 24 October 2020 22:32
To: Support@hamapps.groups.io
Subject: Re: [HamApps] #FT8/JTAlert

 

follow the order of opening 

call up the settings, then manage settings.

 

scroll down the the + window.  do not click on the + symbol.  extended display options is on the right side, near the top

 

see image attached. 

keep in mind, this is from version 2.16.14

 

 

Dave Garber

VE3WEJ / VE3IE

 

 

On Fri, Oct 23, 2020 at 8:20 AM Wes Elton <wes@...> wrote:

Hi Jim,

Thanks for the info. Laurie has told me the same thing but within the window/decode settings there is no Extended Display/show db option!

I'm  clearly missing something and have  asked Laurie for further advice.

Stay sake OM.
73,
Wes.
GW3RIH

-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Jim N6VH
Sent: 22 October 2020 20:52
To: Support@HamApps.groups.io
Subject: Re: [HamApps] #FT8/JTAlert


On 10/22/2020 12:42 PM, Wes Elton wrote:
> Hi All,
> Can someone please advise where I can find the settings info that will
> enable received signal strength to appear beneath calls in the
> callsign display lines.
> I've searched the help files but see anything relevant.
>
> Cheers,
>
> Wes.
> GW3RIH.

Wes,

Go to Settings/Window. Click Show db (DXCC Name)

73,

Jim N6VH












locked #FT8/JTAlert

Wes Elton
 

 

Thanks Dave, I’d misunderstood Laurie’s instructions!

All working well now.

73,

Wes.

GW3RIH

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Dave Garber
Sent: 24 October 2020 22:32
To: Support@hamapps.groups.io
Subject: Re: [HamApps] #FT8/JTAlert

 

follow the order of opening 

call up the settings, then manage settings.

 

scroll down the the + window.  do not click on the + symbol.  extended display options is on the right side, near the top

 

see image attached. 

keep in mind, this is from version 2.16.14

 

 

Dave Garber

VE3WEJ / VE3IE

 

 

On Fri, Oct 23, 2020 at 8:20 AM Wes Elton <wes@...> wrote:

Hi Jim,

Thanks for the info. Laurie has told me the same thing but within the window/decode settings there is no Extended Display/show db option!

I'm  clearly missing something and have  asked Laurie for further advice.

Stay sake OM.
73,
Wes.
GW3RIH

-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Jim N6VH
Sent: 22 October 2020 20:52
To: Support@HamApps.groups.io
Subject: Re: [HamApps] #FT8/JTAlert


On 10/22/2020 12:42 PM, Wes Elton wrote:
> Hi All,
> Can someone please advise where I can find the settings info that will
> enable received signal strength to appear beneath calls in the
> callsign display lines.
> I've searched the help files but see anything relevant.
>
> Cheers,
>
> Wes.
> GW3RIH.

Wes,

Go to Settings/Window. Click Show db (DXCC Name)

73,

Jim N6VH












locked Re: Strange UI phenomenon

Björn SM7IUN
 

Great! Thank you Laurie.

Björn

Den sön 25 okt. 2020 kl 05:49 skrev HamApps Support (VK3AMA) <vk3ama.ham.apps@...>:

On 22/10/2020 7:31 pm, Björn SM7IUN wrote:
From time to time I find the "Help" menu replaced by the name of a newly connected audio device.

Is this intentional? I assume not.

Also, JTAlert seems to suffer from the inability to handle UTF-8 in device names of which some are 
created by default in non-English Windows. The different effects of this have been reported previously.

Björn SM7IUN

Björn,

FYI, these problems have now been resolved. Newly added Sound Device names no longer replace the "Help" menu and UTF-8 encoded Sound Device names are correctly handled. eg.
   

Check your email, I have sent you a link to this new build to test.

de Laurie VK3AMA



locked Re: Strange UI phenomenon

HamApps Support (VK3AMA)
 

On 22/10/2020 7:31 pm, Björn SM7IUN wrote:
From time to time I find the "Help" menu replaced by the name of a newly connected audio device.

Is this intentional? I assume not.

Also, JTAlert seems to suffer from the inability to handle UTF-8 in device names of which some are 
created by default in non-English Windows. The different effects of this have been reported previously.

Björn SM7IUN

Björn,

FYI, these problems have now been resolved. Newly added Sound Device names no longer replace the "Help" menu and UTF-8 encoded Sound Device names are correctly handled. eg.
   

Check your email, I have sent you a link to this new build to test.

de Laurie VK3AMA



locked Re: Strange UI phenomenon

HamApps Support (VK3AMA)
 

On 25/10/2020 8:25 am, g4wjs wrote:
On 24/10/2020 21:41, HamApps Support (VK3AMA) wrote:
As for the UTF-8 naming issue, I am investigating why that is occurring. The underlying code that retrieves all the audio endpoints defined on the PC fully supports UTF-8. Something is being lost in getting that data over to the main JTAlert executable.

de Laurie VK3AMA

Hi Laurie,

this may not be relevant and your comment above just be using incorrect terminology, but wide-strings in Windows are not utf-8, they are 16-bit characters encoded with utf-16 little-edian Unicode values. You might convert them to multi-byte Unicode strings, utf-8 for example, to send over the network, store in a file, or other space constrained media.


--
73
Bill
G4WJS.
Tnx Bill,

My head starts hurting every-time I have to start thinking about ANSI, ASCII, UTF-8, Unicode, codepages, multi-byte versus single-byte strings, etc, etc.

With respect to this sound device name problem. The strings returned from enumerating the endpoints are variable-length encoded UTF-8, but it was getting those strings over to JTAlert that was the issue. The AutoIT based string comparison routines
of JTAlert were not UTF-8 compatible, combined with legacy XP era winmm.dll calls conspired to bring on a migraine! Its my own fault for clinging onto the old AutoIT code base for so long and trying to be clever integrating .NET code. Code refactoring is currently underway

de Laurie VK3AMA


locked Re: 8-character Gridsquare

onaka@...
 

Thank you Laurie.
WSJT-X and JTDX can set 8 characters on the grid.
In PSKReporter, if there are local stations with the same grid, the icon display will overlap, so I set it to 8 characters so that the icons do not overlap.
PSKReportr can display a grid of up to 10 characters.
JA4JOE


JTAlert Wanted Callsigns in Decodes window

iain macdonnell - N6ML
 


During ES season, I accumulated a list of callsigns known to be operating 6m from FFMA grids that I still need (that set of grids is getting smaller), hoping to get a jump on them if they showed up, perhaps before JTAlert knows what grid they're operating from.

Unfortunately "Wanted Callsign" is not band-specific (AFAIK?), so on returning to HF, I was getting a lot of alerts for those callsigns, but I don't need them on the HF bands. It'd be great if itcould be made band-specific, but that seems like it'd be a fair amount of development work.

So I turned off "Enable Wanted Callsign Alert", which stopped the alerts, but....

I use the "Decodes" window with Filter including "Show only Alerts" as a way to observe if anything that I need has been decoded recently (I often leave the decoder running while I do other things)...

... but those pesky "Wanted callsigns" still appear in the Decodes window! The "Alert" column is empty, yet they get though the filter. They clutter the decodes window quite a bit.

I could empty out my "Wanted callsigns" list, but I'd quite like to keep them for later, and this seems like a bug?

73,

    ~iain / N6ML


locked Re: #FT8/JTAlert

Dave Garber
 

follow the order of opening 
call up the settings, then manage settings.

scroll down the the + window.  do not click on the + symbol.  extended display options is on the right side, near the top

see image attached. 
keep in mind, this is from version 2.16.14


Dave Garber
VE3WEJ / VE3IE


On Fri, Oct 23, 2020 at 8:20 AM Wes Elton <wes@...> wrote:
Hi Jim,

Thanks for the info. Laurie has told me the same thing but within the window/decode settings there is no Extended Display/show db option☹!

I'm  clearly missing something and have  asked Laurie for further advice.

Stay sake OM.
73,
Wes.
GW3RIH

-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Jim N6VH
Sent: 22 October 2020 20:52
To: Support@HamApps.groups.io
Subject: Re: [HamApps] #FT8/JTAlert


On 10/22/2020 12:42 PM, Wes Elton wrote:
> Hi All,
> Can someone please advise where I can find the settings info that will
> enable received signal strength to appear beneath calls in the
> callsign display lines.
> I've searched the help files but see anything relevant.
>
> Cheers,
>
> Wes.
> GW3RIH.

Wes,

Go to Settings/Window. Click Show db (DXCC Name)

73,

Jim N6VH