Date   

locked Re: JTAlert not decoding

dpaschal@...
 

If I click View and then I click any of those with the yellow star beside them or press the function key (F3, etc), I do not get any other window popping up.  Like View, Callsigns Window does not show another window.


locked Re: JTAlert not decoding

Joe Subich, W4TV
 

That is as expected. With 2.50.0 the decoded callsigns have been to a
new "CALLSIGNS" Window. Click "View -> Callsigns Window" to open that
window.

Click Help -> Open JTAlert 2.50 features Help File (F1) for info and
help on all the new windows/features in 2.50.

73,

... Joe, W4TV

On 2021-04-30 10:32 AM, dpaschal@gmail.com wrote:
I have LOG4OM2 and WSJT-X running.  I am able to launch JTAlert but the window is presents has no decoded information in it.  I will link a screenshot.  I think I have it configured correctly but would appreciate a step-through of things to check.  I have attempted to watch some youtube videos on it but the information on getting these three applications working is a bit sparce.
<a href="https://i.imgur.com/s4his7i.png"><img src="https://i.imgur.com/s4his7im.jpg"></a>
-David, WB4IHY


locked Re: Independent audio alert s #FT8

Pat N6PAT
 

That sounds good but I'm looking for real time audio and visual alerts while I'm working on my computer.


locked JTAlert not decoding

dpaschal@...
 

I have LOG4OM2 and WSJT-X running.  I am able to launch JTAlert but the window is presents has no decoded information in it.  I will link a screenshot.  I think I have it configured correctly but would appreciate a step-through of things to check.  I have attempted to watch some youtube videos on it but the information on getting these three applications working is a bit sparce.  

<a href="https://i.imgur.com/s4his7i.png"><img src="https://i.imgur.com/s4his7im.jpg"></a>

-David, WB4IHY


locked Re: unable to launch program

dpaschal@...
 

You can mark this one closed.  After about a day or two of not being on the air with it, I decided to take a day off and launch JTAlert to try and troubleshoot it.  It opened right up.  However, now it is not decoding.  Which is what it was doing before it wouldn't even launch.  So I will open another topic on that.


locked Re: Independent audio alert s #FT8

Michael Black
 

The email alert tells you the band.

Mike W9MDB




On Friday, April 30, 2021, 09:15:41 AM CDT, Pat N6PAT via groups.io <n6pat@...> wrote:


I don't think that would work. I'm looking for the ability to allow independent instance customized audio alerts to indicate which band (instance) is triggering the alert(s). I dedicate each instance to a particular band.


locked Re: Independent audio alert s #FT8

Pat N6PAT
 

I don't think that would work. I'm looking for the ability to allow independent instance customized audio alerts to indicate which band (instance) is triggering the alert(s). I dedicate each instance to a particular band.


locked Re: Independent audio alert s #FT8

Michael Black
 

Have you thought about using the JTAlert email notices?  You can have them sent to your phone too.

I've got a powershell script that is available on my QRZ page that works with numerous email source.

Mike W9MDB





On Friday, April 30, 2021, 08:09:07 AM CDT, Pat N6PAT via groups.io <n6pat@...> wrote:


Laurie,

You mentioned that independent instance profiles would be something in a future release. Would that include independent audio alerts as well?

The reason I ask is that with my Flex 6700 I run many instances simultaneously for different bands. If I could specify custom band specific audio alerts for wanted DX , States, etc. such as "Wanted DX on 10 meters" that would save me having to search each band in WSJT-X for the wanted DX if the time interval elapses and the wanted call sign disappears from the call sign window. 

Thanks, Pat


locked Independent audio alert s #FT8

Pat N6PAT
 

Laurie,

You mentioned that independent instance profiles would be something in a future release. Would that include independent audio alerts as well?

The reason I ask is that with my Flex 6700 I run many instances simultaneously for different bands. If I could specify custom band specific audio alerts for wanted DX , States, etc. such as "Wanted DX on 10 meters" that would save me having to search each band in WSJT-X for the wanted DX if the time interval elapses and the wanted call sign disappears from the call sign window. 

Thanks, Pat


locked MSK144 - Worked before status

John P
 

Works great in the new call sign window, but in the main window it still shows "First QSO" and when you hover the mouse over the call it shows "New Band" and "*** First MSK144 QSO ***".
--
John P.
WA2FZW


locked Greetings from Japan; Japanese language sound file revision request

shibata.naoki@...
 

Hello, I've been a JTalert user since 2015, and want to say thank you for all development efforts.

Just upgraded my installation from 2.1.xx to 2.50, and found Japanese version sound files.
Tried it and found that announce grade is professional, but the translations for some alerts are completely wrong.

I strongly recommend fixing the translation of, at least, the followings:
CQ: -> (now) Q wo miru (meaning "see Q")  (should be) CQ, or shii kyuu
New State -> (now) atarashii joutai (meaning "new status")  (should be)  atarashii shuu
New VE Prrovince -> (now) atarashii shuu (new state)  (maybe changed to ) atarashii kanada (canada) no shuu
Wanted DXCC -> (now) DX  (maybe) DXCC
Wanted Callsign -> (now) Shimei tehai ("wanted" as in seeking criminals)  (should be)  hoshii kohru(call), or hitsuyou na kooru(call)

please consider revising the Japanese sound file at the next possible opportunity.

73,
NIcky/JH8JNF


locked Re: JT Alert will not run - V 2.50.0 & 2.16.17

W Ramsey <km4jok@...>
 

The only “PC Protection Software” on the PC is the default Windows Defender.  The Window’s Event Log is clear –

 

On executing JT Alert 2.16.17, the error message below is displayed after the “Reading Settings Data – Standby” pop-up box has displayed.  When I click the error box “OK” button JT-Alert crashes.

 

What “undeclared” variable is on Line 41603 of file JTAlert.exe that is causing the crash?  Interestingly, I don’t see the Line 41603 error when running 2.50.0 – instead the program just fails after the “Reading Settings Data – Standby” pop-up is displayed.

 

Is it possible a configuration item in WSJT-X 2.3.1 is causing JT-Alert to crash (not start)?

 



 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Thursday, April 29, 2021 16:29
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JT Alert will not run - V 2.50.0 & 2.16.17

 

On 29/04/2021 2:22 pm, W Ramsey wrote:

I’m on latest updated version of Windows 10 64x Home (20H2).  PC has 32GB memory, Intel i9-10850K CPU and 2TB SSD.  WSJT-X 2.3.1 functions properly.   HamAppSound 2.5.3 and HamAppsDatabases 2021.04.20 were successfully installed.

I’ve tried both JT Alert versions 2.50.0 and 2.16.17.  Both install successfully with no errors.   However each fail to run after the “Reading Settings Data – Standby” pop-up message appears then disappears.  Version 2.16.17 usually shows a Line 41603 error.  Net 5 is installed for version 2.50.0 and is correct version based on confirmation in the CMD window. 

I’ve uninstalled and reinstalled both WSJT-X and JT-Alert versions 2.50.0 and 2.16.17 five (5) times.  I restarted computer after each uninstall and reinstall and the same issue is present – JT-Alert fails to run.

I tried deleting the config.sqlite file and JT Alert still fails to launch.  The only JT Alert process that loads temporarily during program start is the “Audio & Visual Alerts for WSJT-X. (32 bit)” process.  This process starts and then terminates within one second.  

I use N3FJP’s Amateur Contact Log so having JT-Alert functioning really speeds up QSO logging – when JT-Alert is functioning.

Not sure what the issue is but I have successfully used prior versions of WSJT-X and JT-Alert for years without issues.

Ideas appreciated.

Thanks –

William


William,

If repeated installs and different version installs result in an error condition it suggests something common on your PC, that doesn't change with the different installs is likely the cause. One candidate is the JTAlert config file as it doesn't get touched during multiple installs. Since you still received the error after removing the config file, that rules out a corrupt config as the cause.

My best guess is that your PC protection software (what do you use?) has now taken a dislike to JTAlert. Check that it is not now blocking JTAlert. You may have to flag JTAlert as safe to get past its interference.

Worth checking is your Windows Event log, there may be something in there that can provide a clue.

If I was a betting person, I would put my money of Protection software being the issue.

de Laurie VK3AMA


locked Re: F5 Text message operation

HamApps Support (VK3AMA)
 

On 30/04/2021 10:10 am, WB5JJJ - George wrote:
I've been caught by this a couple of times.  

I start typing a response to an F5 message while calling CQ.  When a NEW station calls me back, their call replaces the call in the DX Call (WSJTx) and also in the F5 message window.  So, when I click send, it goes to the NEW call and not the one I was actually responding to.  So far they have gone to non-users, but I have to retype the message and make sure it goes to the right person.  

Two things as suggestions.  1)  Be able to copy and paste in the F5 window and 2) keep the original call as the recipient until after send is clicked.  

In the mean time, I just have to NOT be calling CQ or hopefully nobody will just call me out of the blue, from their history and make double sure I'm sending to the right person before I hit send.  

Still adjust to the new Callsign window, but getting there.  
--
73's
George - WB5JJJ

Copy and Paste is already supported by the message edit field. You can even call up previously saved messages via the selector below that edit field.

From the release notes of the next release, 2.50.1, due in a few days...
    - Messaging window: WSJT-X DX Call changes now no longer auto populate the
       Callsign field if a message is already being composed. That is if the
       message field contains text, the DX Call change is ignored.

de Laurie VK3AMA



locked F5 Text message operation

WB5JJJ - George
 

I've been caught by this a couple of times.  

I start typing a response to an F5 message while calling CQ.  When a NEW station calls me back, their call replaces the call in the DX Call (WSJTx) and also in the F5 message window.  So, when I click send, it goes to the NEW call and not the one I was actually responding to.  So far they have gone to non-users, but I have to retype the message and make sure it goes to the right person.  

Two things as suggestions.  1)  Be able to copy and paste in the F5 window and 2) keep the original call as the recipient until after send is clicked.  

In the mean time, I just have to NOT be calling CQ or hopefully nobody will just call me out of the blue, from their history and make double sure I'm sending to the right person before I hit send.  

Still adjust to the new Callsign window, but getting there.  
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: Issues Relating to Recently-Installed v2.50.0

HamApps Support (VK3AMA)
 

My answers inline...

On 30/04/2021 2:18 am, Paul wrote:

I recently installed JTAlert 2.50.0 and I love the new, flexible callsigns display.  That is a great enhancement.  Thank you for a fabulous upgrade.

However, I am running into some issues, namely:

  • When logging a completed contact, the instant the ‘logging successful’ confirmation window pops up, the Callsigns window goes blank, and I have not found any way to prevent this.  In the past, I was able to select the next station to be contacted while the logging was occurring.  Now I have to wait a full cycle and relocate the station of interest within all the callsigns displayed.
Turn off the "Clear Callsigns display after logging" option in the main JTAlert Settings window, "Logging" section. Look under the "Logging Options". You will need to scroll the list of settings down to reveal the required checkbox.


  • For some reason I am also getting a large Decodes window opening whenever I launch the app, and I have tried but failed to get that to stop. I have to manually close the window every time. (my computer screen is not large, and I cannot accommodate any ‘extra’ windows)
Turn off the "Restore window when JTAlert is started" option in the main JTAlert Setting window. "Window -> Decodes" section.


  • FYI, I have seen your recommendation to use UDP Server address 239.255.0.0 in WSJT-X and, of course, the downloaded newest WSJT-X release installed with those settings but, unless I changed that back to 127.0.0.1, my JTAlert Callsigns window always remained blank – nothing was being displayed.
Very likely you didn't perform the required change in JTAlert when switching WSJT-X to use multicast. Make sure the "Settings -> WSJT-X UDP Multicast on Loopback" menu of the main JTAlert window is ticked. The Help file (not the 2.50 features help) has instructions for the correct setup. See the "WSJT-X UDP Setup" topic (its at the root level) in that help.


  • I had thought that callsign clicking actions are dictated by WSJT-X.  Is that correct?  I ask because I am finding the double-click on a callsign for some reason behaves differently when done within the WSJT-X Band Activity window or within the JTAlert Callsigns window.  Double-clicking a decoded callsign in WSJT-X moves the RX frequency focus and enables TX.  Double-clicking a displayed callsign within the JTAlert moves the RX frequency focus but does not enable TX.  Is that correct/as-designed?
The decision to go into transmit in response to a callsign click event is controlled by WSJT-X. JTAlert cannot control that behavior. There is no mechanism in the command sent to WSJT-X to tell it to go into transmit. JTAlert simply tells WSJT-X this Callsign of a specific decode was clicked. This is how the WSJT-X API is designed, there is no support within the API to instruct WSJT-X to go into transmit in response to a callsign click.


Related to that last item, I would very much like to have actions for both single- and double-click, whereby a single-click on a station of interest focusses the RX frequency accordingly, and a double-click both focusses the RX frequency and enables TX.  There are many times when I merely wish to observe a station for a brief period before calling – usually to wait until his current contact is finishing before calling.  If, as I had thought, clicking actions are controlled solely by WSJT-X, then I will make my suggestion/request with that group.

See my previous comment about API limitations in WSJT-X.

73, and thanks again for all your efforts…  Paul (VE3PS)


73
de Laurie VK3AMA


locked Re: JT Alert will not run - V 2.50.0 & 2.16.17

HamApps Support (VK3AMA)
 

On 29/04/2021 2:22 pm, W Ramsey wrote:

I’m on latest updated version of Windows 10 64x Home (20H2).  PC has 32GB memory, Intel i9-10850K CPU and 2TB SSD.  WSJT-X 2.3.1 functions properly.   HamAppSound 2.5.3 and HamAppsDatabases 2021.04.20 were successfully installed.

 

I’ve tried both JT Alert versions 2.50.0 and 2.16.17.  Both install successfully with no errors.   However each fail to run after the “Reading Settings Data – Standby” pop-up message appears then disappears.  Version 2.16.17 usually shows a Line 41603 error.  Net 5 is installed for version 2.50.0 and is correct version based on confirmation in the CMD window. 

 

I’ve uninstalled and reinstalled both WSJT-X and JT-Alert versions 2.50.0 and 2.16.17 five (5) times.  I restarted computer after each uninstall and reinstall and the same issue is present – JT-Alert fails to run.

 

I tried deleting the config.sqlite file and JT Alert still fails to launch.  The only JT Alert process that loads temporarily during program start is the “Audio & Visual Alerts for WSJT-X. (32 bit)” process.  This process starts and then terminates within one second.  

 

I use N3FJP’s Amateur Contact Log so having JT-Alert functioning really speeds up QSO logging – when JT-Alert is functioning.

 

Not sure what the issue is but I have successfully used prior versions of WSJT-X and JT-Alert for years without issues.

 

Ideas appreciated.

 

Thanks –

 

William


William,

If repeated installs and different version installs result in an error condition it suggests something common on your PC, that doesn't change with the different installs is likely the cause. One candidate is the JTAlert config file as it doesn't get touched during multiple installs. Since you still received the error after removing the config file, that rules out a corrupt config as the cause.

My best guess is that your PC protection software (what do you use?) has now taken a dislike to JTAlert. Check that it is not now blocking JTAlert. You may have to flag JTAlert as safe to get past its interference.

Worth checking is your Windows Event log, there may be something in there that can provide a clue.

If I was a betting person, I would put my money of Protection software being the issue.

de Laurie VK3AMA



locked Re: Issues Relating to Recently-Installed v2.50.0

Paul
 

Laurie,

I apologize for emailing you, but I have been unable to figure out how to post a reply within any thread I read.  There is no Reply ‘button’ as there is with other groups I belong to.

I recently installed JTAlert 2.50.0 and I love the new, flexible callsigns display.  That is a great enhancement.  Thank you for a fabulous upgrade.

However, I am running into some issues, namely:

  • When logging a completed contact, the instant the ‘logging successful’ confirmation window pops up, the Callsigns window goes blank, and I have not found any way to prevent this.  In the past, I was able to select the next station to be contacted while the logging was occurring.  Now I have to wait a full cycle and relocate the station of interest within all the callsigns displayed.
  • For some reason I am also getting a large Decodes window opening whenever I launch the app, and I have tried but failed to get that to stop. I have to manually close the window every time. (my computer screen is not large, and I cannot accommodate any ‘extra’ windows)
  • FYI, I have seen your recommendation to use UDP Server address 239.255.0.0 in WSJT-X and, of course, the downloaded newest WSJT-X release installed with those settings but, unless I changed that back to 127.0.0.1, my JTAlert Callsigns window always remained blank – nothing was being displayed.
  • I had thought that callsign clicking actions are dictated by WSJT-X.  Is that correct?  I ask because I am finding the double-click on a callsign for some reason behaves differently when done within the WSJT-X Band Activity window or within the JTAlert Callsigns window.  Double-clicking a decoded callsign in WSJT-X moves the RX frequency focus and enables TX.  Double-clicking a displayed callsign within the JTAlert moves the RX frequency focus but does not enable TX.  Is that correct/as-designed?

Related to that last item, I would very much like to have actions for both single- and double-click, whereby a single-click on a station of interest focusses the RX frequency accordingly, and a double-click both focusses the RX frequency and enables TX.  There are many times when I merely wish to observe a station for a brief period before calling – usually to wait until his current contact is finishing before calling.  If, as I had thought, clicking actions are controlled solely by WSJT-X, then I will make my suggestion/request with that group.

73, and thanks again for all your efforts…  Paul (VE3PS)


locked CHat support without WSJTx

Frank
 
Edited

HI All

Of JTalert I also gladly use his CHAT that with F5 makes me reach the correspondent to pass him some info.

SUPER!
 
But I can use the JTalert CHAT only if I have activated WSJTx first, then I start JTalert and finally close the WSJTx for to run use another FT8 app which is not wsjtx

Would it be possible to start the JTalert (CHAT) without WSJTx or do I always have to first start WSJTx, then JTalert and then close Wsjtx for to open the other FT soft ??
 
I don't always use WSJTx and I often use another one for FT8/4 which unfortunately does not want to make udp compatible with the excellent JTalert. :-(

Thanks for info
Franco


locked Re: JTAlert X - HRD log scan careened past 1085 records and hit a brick wall in memory crashed and burned

Ron W3RJW
 
Edited

Let me add a few things:

I have a Microsoft Access log with 23,000 contacts and it works just fine. Many people have much bigger logs.

The biggest problem is that many of us have/had really old Access drivers. The act of creating a new log and importing old QSO's, as Laurie describes, forces the system to update those drivers.  This fixes a lot of problems, but maybe will not fix yours.

A comprehensive discussion on the HRD web site describes the details, including how to check your drivers:
https://www.hamradiodeluxe.com/blog/The-Problem-With-Microsoft-Access.html


If you really feel the need to change to MySQLdatabase, there is an instruction link on the page above.

Just let me say that updating HRD will not fix driver problems.It's a separate issue.

--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0 rc4, JTAlert 2.50.0, HRD Deluxe v6.7.0.323
FTdx-3000, SignaLink USB


locked JT Alert will not run - V 2.50.0 & 2.16.17

W Ramsey <km4jok@...>
 

I’m on latest updated version of Windows 10 64x Home (20H2).  PC has 32GB memory, Intel i9-10850K CPU and 2TB SSD.  WSJT-X 2.3.1 functions properly.   HamAppSound 2.5.3 and HamAppsDatabases 2021.04.20 were successfully installed.

 

I’ve tried both JT Alert versions 2.50.0 and 2.16.17.  Both install successfully with no errors.   However each fail to run after the “Reading Settings Data – Standby” pop-up message appears then disappears.  Version 2.16.17 usually shows a Line 41603 error.  Net 5 is installed for version 2.50.0 and is correct version based on confirmation in the CMD window. 

 

I’ve uninstalled and reinstalled both WSJT-X and JT-Alert versions 2.50.0 and 2.16.17 five (5) times.  I restarted computer after each uninstall and reinstall and the same issue is present – JT-Alert fails to run.

 

I tried deleting the config.sqlite file and JT Alert still fails to launch.  The only JT Alert process that loads temporarily during program start is the “Audio & Visual Alerts for WSJT-X. (32 bit)” process.  This process starts and then terminates within one second.  

 

I use N3FJP’s Amateur Contact Log so having JT-Alert functioning really speeds up QSO logging – when JT-Alert is functioning.

 

Not sure what the issue is but I have successfully used prior versions of WSJT-X and JT-Alert for years without issues.

 

Ideas appreciated.

 

Thanks –

 

William

 

 

3321 - 3340 of 37815