|
locked
Re: audio alerts for "POTA" AND/OR "PARKS" do not work - New JTAlert Build to Test
Only issue I've seen is Directed CQ isn’t available under Settings menu. It is accessible under mF2 menu. Works great thank you!
Wyndell – K5WJF Resistance is NOT futile, it's Voltage divided by Current
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, July 3, 2021 23:38 To: Support@HamApps.groups.io Subject: Re: [HamApps] audio alerts for "POTA" AND/OR "PARKS" do not work - New JTAlert Build to Test
A new JTAlert beta build is available for testing. This build has a new "Directed CQ" Alert.
Note: All JTAlert Betas have an inbuilt expiry date. They cease to function 56 days after their creation date. You can check when it will expire via the Help -> About" menu of the main JTAlert window.
|
|
|
|
locked
Re: Error installing JTAlert
Thks Laurie, that worked.
73 PH7R Ronald
|
|
|
|
locked
Re: Unable to communicate with the WSJT-X process.
Jim Cooper
On 4 Jul 2021 at 9:27, Wayne N4GIL via groups.io wrote:
*IP Address : 127.0.0.1*read the help file on setting up Multicast UDP ... it is written up as a special help file, and available with one click from the Help tab.
|
|
|
|
locked
Unable to communicate with the WSJT-X process.
Wayne N4GIL
I've used WSJT-X and JT Alert since the beginning. However, I'm setting up a laptop for POTA and cannot get JTAlert to communicate with the WSJT-X process.
I get this error...... and I'm not sure what it means. "Unable to communicate with the WSJT-X process. UDP Port : 2237
IP Address : 127.0.0.1
Values read from WSJT-X config file...
C:\Users\D E L L\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Detected Instance...
Process Window Title : WSJT-X v2.4.0 by K1JT, G4WJS, K9AN, and IV3NWV
Process Command Line : "C:\HAMRADIO\WSJTX\bin\wsjtx.exe"
Decode alerts and logging will be unavailable until corrected.
-------------------------------------------------------------------------------------------------- Any recommendations? I'm sure it must be an easy fix us elderly folks don't recognize. :) Thanks / N4GIL / Wayne
|
|
|
|
locked
Re: audio alerts for "POTA" AND/OR "PARKS" do not work - New JTAlert Build to Test
Buddy Spiegel
many thanks to laurie
the Directed CQ alert works perfectly at my location. now, if only the 13 colony peeps would go away, some pota peeps would come out to play. lol.
|
|
|
|
locked
Re: FFMA
You are correct sir Thanks... Baa Sent via the Samsung Galaxy S8+ DX
-------- Original message -------- From: "Joe Subich, W4TV" <lists@...> Date: 7/4/21 10:06 AM (GMT-05:00) To: Support@HamApps.groups.io Subject: Re: [HamApps] FFMA > Looks like I had My QTHID selected for my current QTH only. Remember, like VUCC, FFMA is limited to a to a 200 km (124 mi) diameter (100 km / 62 mi) circle. If any of your QTHs fall outside that circle you will need to deselect them for FFMA consideration. 73, ... Joe, W4TV On 2021-07-04 9:27 AM, Jose Castillo wrote: > OK... Think I am on to my issue. > Looks like I had My QTHID selected for my current QTH only. > I have deselected that option to include all my QTHs and I'll run this for > awhile. > Logically, that makes sense. > > I'll report in a few... > > Thanks > Jose > N4BAA > > On Sat, Jul 3, 2021 at 11:33 PM HamApps Support (VK3AMA) < > vk3ama.ham.apps@...> wrote: > >> On 4/07/2021 12:48 am, Jose Castillo wrote: >> >> Running 2.50.2 with >> WSJT-X v.2.5.0-rc1 >> >> Have window for Alert FFMA Grids but it appears to not be tracking my >> progress (thus needed) correctly. >> >> I have grids options selected for ANY mode and I am only chasing grids on >> 6M. >> Also have LoTW selected since I don't have any 6m QSL confirmations. >> >> Rebuild alert database conducted. >> >> Still shows MANY of the 400 grids I have confirmed via LoTW. >> >> Not sure what else I can check. >> >> Thanks/73 >> Jose >> N4BAA >> >> >> I previously answered the same question from you. I never got any answers >> to the questions I asked or received files for examination. >> >> see https://hamapps.groups.io/g/Support/message/35878 >> >> de Laurie VK3AMA >> >>
|
|
|
|
locked
Re: FFMA
Joe Subich, W4TV
Looks like I had My QTHID selected for my current QTH only.Remember, like VUCC, FFMA is limited to a to a 200 km (124 mi) diameter (100 km / 62 mi) circle. If any of your QTHs fall outside that circle you will need to deselect them for FFMA consideration. 73, ... Joe, W4TV On 2021-07-04 9:27 AM, Jose Castillo wrote: OK... Think I am on to my issue.
|
|
|
|
locked
Re: audio alerts for "POTA" AND/OR "PARKS" do not work - New JTAlert Build to Test
Don Melcher
I was just digging for this function. I’ll give it a try.
-- Don W6CZ DM07
|
|
|
|
locked
Re: FFMA
Jose Castillo
OK... Think I am on to my issue. Looks like I had My QTHID selected for my current QTH only. I have deselected that option to include all my QTHs and I'll run this for awhile. Logically, that makes sense. I'll report in a few... Thanks Jose N4BAA
On Sat, Jul 3, 2021 at 11:33 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
|
|
|
|
locked
audio alerts for "POTA" AND/OR "PARKS" do not work - New JTAlert Build to Test
Thank you sir I've got it loaded and testing
Wyndell – K5WJF Resistance is NOT futile, it's Voltage divided by Current
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, July 3, 2021 23:38 To: Support@HamApps.groups.io Subject: Re: [HamApps] audio alerts for "POTA" AND/OR "PARKS" do not work - New JTAlert Build to Test
A new JTAlert beta build is available for testing. This build has a new "Directed CQ" Alert.
Note: All JTAlert Betas have an inbuilt expiry date. They cease to function 56 days after their creation date. You can check when it will expire via the Help -> About" menu of the main JTAlert window.
|
|
|
|
locked
Re: Marathon Alerts
David Burden
OK thanks Laurie,
I am usure how these stiings got changed. Cheers David VK3BDX
|
|
|
|
locked
Re: audio alerts for "POTA" AND/OR "PARKS" do not work - New JTAlert Build to Test
JTAlert Support (VK3AMA)
A new JTAlert beta build is available for testing. This build has a
new "Directed CQ" Alert.
If your interested in testing the installers can be found here... 64bit (x64) https://dnl.HamApps.com/Beta/JTAlert.2.50.2.build.0002.Beta.Install.X64.exeNote: All JTAlert Betas have an inbuilt expiry date. They cease to function 56 days after their creation date. You can check when it will expire via the Help -> About" menu of the main JTAlert window.  To use the new "Directed CQ" Alert, you need to enter one or more direction words into the word list under the "Alerts -> Directed CQ" section of the main Settings window, like SOTA, POTA, COTA, TEST, VK, etc. Words are limited to 1 to 4 alpha characters only, per the FT8/4 protocol. The Decodes window will also highlight the word under the CQ column if the decode generated a Directed CQ Alert. I don't normally make Beta builds publicly available, please let me know if this works for you de Laurie VK3AMA
|
|
|
|
JTAlert Support (VK3AMA)
On 30/06/2021 6:15 am, Jim N6VH wrote:
And if the Cog is not visible, make the window active by clicking it then use the F2 key. The F2 key is universal across all JTAlert windows for opening the Settings window or Options popups. de Laurie VK3AMA
|
|
|
|
locked
Re: Window 10 magnify
JTAlert Support (VK3AMA)
On 2/07/2021 1:16 pm, heath calhoun -
kb5vai wrote:
So its only one of the JTAlert windows is that correct? Is it the Decodes Window, it is the only one that has File and View menu entries? I just repeated testing, using all 3 modes of the Magnifier, The full screen, the docked view and the floating magnifying view. All worked correctly with JTAlert. Are you perhaps using an old version of JTAlert? I did all my testing with the latest release, 2.50.2 I used the Microsoft Magnifier instructions posted here... https://support.microsoft.com/en-us/topic/setting-up-and-using-magnifier-e1330ccd-8d5c-2b3c-d383-fd202808c71a Sorry, I can't offer any advice on how to fix your problem. de Laurie VK3AMA
|
|
|
|
locked
Re: Error installing JTAlert
JTAlert Support (VK3AMA)
On 4/07/2021 5:48 am, PH7R - Ronald
wrote:
I get 2 red music icons in my toolbar, see pciture. The left one does not open properly, if I click on it than both the screen WSJT-X and callsigns#1 are shown on the screen. The only thing I see is "JTAlert 2.50.2 PH7R[???m,,L". It would appear that the main JTAlert window is off-scree, a common Windows problem. Do a Google Search on "Recover off-screen Window" will bring up many thousands of hits for this common problem. Once you get that window back to your main screen you will be able to access its Settings widow. de Laurie VK3AMA
|
|
|
|
locked
Re: Question
JTAlert Support (VK3AMA)
On 4/07/2021 3:31 am, Neil Foster
wrote:
Some time ago I set JT Alert not to show spots from the USA and I can not remember how that was done. I would like to revert to the setting so that I can see US as well as DX spots in the Decodes. Likely JTAlert is displaying "Filtered" in its title-bar, is that the case? If so, than alter your Continent Filter settings under the "Alerts -> Filters -> Show Continent..." menu.  de Laurie VK3AMA
|
|
|
|
locked
Re: Setting Up Two Individual JT-Alerts, One For Flex, And One IC7300
JTAlert Support (VK3AMA)
On 4/07/2021 6:57 am, philp51 wrote:
Hi, Is there a way to set up 2 individual iterations, not running at the same time, one for one rig, and one for another with different parameters than the first rig. Maybe 2 different shortcuts or 2 different installations? Any help would be appreciated. Thanks, 73..Phil W8PP Setup multiple configurations in WSJT-X, one for each Rig. There is nothing you need to do in JTAlert. When you want to change Rig, switch to that configuration in WSJT-X. JTAlert will automatically detect any changes in WSJT-X so there is no need to restart JTAlert. de Laurie VK3AMA
|
|
|
|
locked
Re: MSDATL3 Issue
JTAlert Support (VK3AMA)
On 4/07/2021 1:03 am, kk5aa_fred via
groups.io wrote:
I get a warning that MSDATL3 This is a problem within Windows itself. It would appear that something is broken within the Database Access components of Windows. I suggest you talk with Microsoft Support to get this resolved. FWIW, in the 10+ years that JTAlert has been available, supporting many Windows versions, this is the first time I have received a report of a MSDATL3 error. Something is broken in Windows that is affecting the JTAlert database code. de Laurie VK3AMA
|
|
|
|
locked
Re: FFMA
JTAlert Support (VK3AMA)
On 4/07/2021 12:48 am, Jose Castillo
wrote:
I previously answered the same question from you. I never got any answers to the questions I asked or received files for examination. see https://hamapps.groups.io/g/Support/message/35878 de Laurie VK3AMA
|
|
|
|
locked
Re: JTalert stops responding
JTAlert Support (VK3AMA)
On 3/07/2021 4:12 am, Brad wrote:
Help I have tried everything I can thing of. as soo as a click on a call JTAlert stops responding. I'm running JTAlert, WSJT-X , HRD and Windows 10. It might work for one or 2 calls then locks up again. If and one can help me with this please respond. or if you can log on to my system and see if my setings are all messed up. Version number of the software would help. Since you mentioned HRD, I expect it is V6.something. A number of HRD 6 users have experienced this type of problem. The exact cause is unknown, but it is related to using an MSAccess log in HRD. The usual fix is to perform an export of your current log, create a new Log in HRD and import the previous export, then switch JTAlert to using that new Log. In a very small number of cases, creating a new HRD MSAccess log didn't correct the behavior, but upgrading to using a MariaDB log did. HRD themselves recommend using MariaDB rather than MSAccess type logs. de Laurie VK3AMA
|
|
|
