Date   

locked Worked B-4 does not show in rx window#Important

Rick Wines
 


I am not showing the B-4 tag next to a station in the Band Activity window that I know I have worked, even changing the date in the "ignore" option. 

Rick Wines, W5FKW


locked Worked B-4 status

Rick Wines
 

Is there some documentation on JTAlert? I read the description of Worked B-4 in the JTAlert options, and if that is true, I might have a in house problem because I have not seen anything other than signal reports. I even changed my date to 2018 on the “ignore before” date and still nothing on stations that I KNOW I have worked. Probably just a tic somewhere but I don’t know where!!!!

 

Rick, W5FKW

Round Rock, TX

 

Sent from Mail for Windows 10

 


locked Re: JTAlert Request

Michael Black
 

WSJT-X can do multicast....JTAlert cannot (limit of the language) but rebroadcast is already in JTAlert.


Under Applications/WSJT-X

Inline image

de Mike W9MDB







On Friday, January 18, 2019, 12:17:49 PM CST, markholbrook <markholbrook@...> wrote:


Hello all,

I am in the process of writing a unique logging program for Flex Radio users.   One of the many requests I've had it to integrate with WSJT-X and automate logging.

I am finding that when JTAlert is run and working with WSJT-X that the UDP broadcast sent by WSJT-X on port 2237 is swallowed.  I don't think this is a fault of JTAlert but I believe the broadcast is not multicast so the first subscriber tends to get all of the data.

I would like to request that a rebroadcast feature be added to JTAlert on a different port.  So when JTAlert receives the data from WSJT-X it then rebroadcasts the exact same data on the rebroadcast port.   I think this rebroadcast option should be off by default but allowed to be enabled in the settings dialog of JTAlert.

That would allow a program such as the one I am writing to also receive the full data broadcast from WSJT-X.   I have requested that Joe Taylor change to a multicast but I have not received any response.

The vast majority of my users love the features of JTAlert and do not want to lose them.  So their ideal setup would be WSJT-X, JTAlert and my logging program all working together.

When my program is a little further along I will try to work with JTAlert to have it added as one of the log program options.

Thanks for the consideration!  Please feel free to email me if you have any questions.

--
  Mark R. Holbrook
  markholbrook@...



locked Re: No longer logging automatically to DXKeeper

HamApps Support (VK3AMA)
 

On 19/01/2019 5:30 am, Carlo - IK2RPE wrote:

I'm no longer logging automatically to DXKeeper, anymore, as I used to be .

 

I understood (from a past message of yours) that:

 

“Once DXKeeper logging is enabled in JTAlert, "DXK" will be displayed in the titlebar. If so, then automatic logging will occur, there is nothing else to set”

 

DXK  **IS** in my titlebar  

 Did I miss something else?

 

Thanks in advance

 

 

 

Carlo  IK2RPE

Carlo,

If you have "DXK" showing in the titlebar, than all is set correctly.
The only thing left to do is actually log a QSO in WSJT-X.

de Laurie VK3AMA


locked No longer logging automatically to DXKeeper

Carlo - IK2RPE
 

Hi Laurie,

 

I'm no longer logging automatically to DXKeeper, anymore, as I used to be .

 

I understood (from a past message of yours) that:

 

“Once DXKeeper logging is enabled in JTAlert, "DXK" will be displayed in the titlebar. If so, then automatic logging will occur, there is nothing else to set”

 

DXK  **IS** in my titlebar  

 Did I miss something else?

 

Thanks in advance

 

 

 

Carlo  IK2RPE


locked Re: JTAlert Request

HamApps Support (VK3AMA)
 

On 19/01/2019 3:29 am, markholbrook wrote:
Hello all,

I am in the process of writing a unique logging program for Flex Radio users.   One of the many requests I've had it to integrate with WSJT-X and automate logging.

I am finding that when JTAlert is run and working with WSJT-X that the UDP broadcast sent by WSJT-X on port 2237 is swallowed.  I don't think this is a fault of JTAlert but I believe the broadcast is not multicast so the first subscriber tends to get all of the data.

I would like to request that a rebroadcast feature be added to JTAlert on a different port.  So when JTAlert receives the data from WSJT-X it then rebroadcasts the exact same data on the rebroadcast port.   I think this rebroadcast option should be off by default but allowed to be enabled in the settings dialog of JTAlert.

That would allow a program such as the one I am writing to also receive the full data broadcast from WSJT-X.   I have requested that Joe Taylor change to a multicast but I have not received any response.

The vast majority of my users love the features of JTAlert and do not want to lose them.  So their ideal setup would be WSJT-X, JTAlert and my logging program all working together.

When my program is a little further along I will try to work with JTAlert to have it added as one of the log program options.

Thanks for the consideration!  Please feel free to email me if you have any questions.

--
  Mark R. Holbrook
Mark,

A UDP rebroadcast is already available.
See the Settings, Applications -> WSJT-X section.

   

de Laurie VK3AMA


locked JTAlert Request

markholbrook
 

Hello all,

I am in the process of writing a unique logging program for Flex Radio users.   One of the many requests I've had it to integrate with WSJT-X and automate logging.

I am finding that when JTAlert is run and working with WSJT-X that the UDP broadcast sent by WSJT-X on port 2237 is swallowed.  I don't think this is a fault of JTAlert but I believe the broadcast is not multicast so the first subscriber tends to get all of the data.

I would like to request that a rebroadcast feature be added to JTAlert on a different port.  So when JTAlert receives the data from WSJT-X it then rebroadcasts the exact same data on the rebroadcast port.   I think this rebroadcast option should be off by default but allowed to be enabled in the settings dialog of JTAlert.

That would allow a program such as the one I am writing to also receive the full data broadcast from WSJT-X.   I have requested that Joe Taylor change to a multicast but I have not received any response.

The vast majority of my users love the features of JTAlert and do not want to lose them.  So their ideal setup would be WSJT-X, JTAlert and my logging program all working together.

When my program is a little further along I will try to work with JTAlert to have it added as one of the log program options.

Thanks for the consideration!  Please feel free to email me if you have any questions.

--
  Mark R. Holbrook
  markholbrook@...



locked Re: JTAlert 2.12.10 not responding

 

Laurie,

Apparently I outwaited whatever gremlin was at work.  JTAlert is now up and running.  Thanks.

 

__________

Dan – K4SHQ

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Dan Malcolm
Sent: Friday, January 18, 2019 6:57 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.12.10 not responding

 

Tried waiting longer Laurie.  The this popped up:

 

Looking at the WSJT-X Setting -> Reporting page shows the correct UPD ip address (127.0.0.1) and UDP Port (2237).  The check boxes adjacent to those settings are all checked.  I’m going to continue to let it set, but it has been running about 10 minutes at this point.

 

__________

Dan – K4SHQ

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, January 18, 2019 12:27 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.12.10 not responding

 

On 18/01/2019 4:36 pm, Dan Malcolm wrote:

Laurie,

I’m having trouble getting JTAlert to start successfully.  It starts up, I the “Reading Settings Data Standby” notice and a little while later I “Not Responding” in the title bar.  I have tried a warm reboot of the computer (Win10 x64) and a power off reboot, without success.  I have also tried reinstalling.  When I kill the process, it leaves behind  “JTAlert Plugins Helper”.  That may be normal since JTAlert was not shut down normally.  I can shut it down via the red ‘x’ in the upper right corner.

Now I’m wondering if there is an INI file that’s corrupted.  What do you recommend?

__________

Dan – K4SHQ

Dan,

When this occurs, ignore it and wait a couple of minutes. Does JTAlert eventually startup?

de Laurie VK3AMA


--
Dan - K4SHQ


--
Dan - K4SHQ


locked Re: Spots from Jtalert to spotcollector

Ron W3RJW
 

On Wed, Jan 16, 2019 at 08:05 PM, HamApps Support (VK3AMA) wrote:
Auto posting every received decode to the DX Cluster is a very bad idea. I can not envisage a use-case where this would be desirable and accepted by the wider DX Community. What would be the reason for posting thousands of decodes to the DX Cluster? There are already far too many people posting their TU's for each FT8 QSO. The DX Cluster is not some sort of on-line log for posting each QSO (ego spots I call them), nor is it suitable for posting thousands of SWL spots (PSKReporter and HamSpots are available for that).
AMEN and well said !
 
--
73
Ron, W3RJW


locked Re: JTAlert 2.12.10 not responding

Michael Black
 

Sounds like either your firewall is blocking it or WSJT-X is corrupted.

#1 Turn off your firewall to test
#2 Run wsjt-x from a cmd line with a new config "wsjtx -r test", set your rig, audio, and turn on the reporting, restart both WSJT-X and JTAlert.

de Mike W9MDB




On Friday, January 18, 2019, 6:57:27 AM CST, Dan Malcolm <K4SHQ@...> wrote:


Tried waiting longer Laurie.  The this popped up:

 

Looking at the WSJT-X Setting -> Reporting page shows the correct UPD ip address (127.0.0.1) and UDP Port (2237).  The check boxes adjacent to those settings are all checked.  I’m going to continue to let it set, but it has been running about 10 minutes at this point.

 

__________

Dan – K4SHQ

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, January 18, 2019 12:27 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.12.10 not responding

 

On 18/01/2019 4:36 pm, Dan Malcolm wrote:

Laurie,

I’m having trouble getting JTAlert to start successfully.  It starts up, I the “Reading Settings Data Standby” notice and a little while later I “Not Responding” in the title bar.  I have tried a warm reboot of the computer (Win10 x64) and a power off reboot, without success.  I have also tried reinstalling.  When I kill the process, it leaves behind  “JTAlert Plugins Helper”.  That may be normal since JTAlert was not shut down normally.  I can shut it down via the red ‘x’ in the upper right corner.

Now I’m wondering if there is an INI file that’s corrupted.  What do you recommend?

__________

Dan – K4SHQ

Dan,

When this occurs, ignore it and wait a couple of minutes. Does JTAlert eventually startup?

de Laurie VK3AMA


--
Dan - K4SHQ


locked Re: JTAlert 2.12.10 not responding

 

Tried waiting longer Laurie.  The this popped up:

 

Looking at the WSJT-X Setting -> Reporting page shows the correct UPD ip address (127.0.0.1) and UDP Port (2237).  The check boxes adjacent to those settings are all checked.  I’m going to continue to let it set, but it has been running about 10 minutes at this point.

 

__________

Dan – K4SHQ

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, January 18, 2019 12:27 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.12.10 not responding

 

On 18/01/2019 4:36 pm, Dan Malcolm wrote:

Laurie,

I’m having trouble getting JTAlert to start successfully.  It starts up, I the “Reading Settings Data Standby” notice and a little while later I “Not Responding” in the title bar.  I have tried a warm reboot of the computer (Win10 x64) and a power off reboot, without success.  I have also tried reinstalling.  When I kill the process, it leaves behind  “JTAlert Plugins Helper”.  That may be normal since JTAlert was not shut down normally.  I can shut it down via the red ‘x’ in the upper right corner.

Now I’m wondering if there is an INI file that’s corrupted.  What do you recommend?

__________

Dan – K4SHQ

Dan,

When this occurs, ignore it and wait a couple of minutes. Does JTAlert eventually startup?

de Laurie VK3AMA


--
Dan - K4SHQ


locked Re: One issue and one enquiry

David Gould
 

Laurie,

Thanks for the information.  The pop-up lock-up has not occurred again yet so have not been able to check yet.

Great news about the upcoming enhancements to the decodes history window, will be most useful.

73,

Dave G3UEG


On 17/01/2019 22:28, HamApps Support (VK3AMA) wrote:
On 18/01/2019 4:09 am, David Gould wrote:
I have found JTAlert most helpful in finding new band/slots and new band/states and band/zones.  I have one issue and one enquiry.

Regularly the box that pops up from the top RHS of the main window (pink green and blue) sticks in the extended position and does not retract.  Is there a way to either 1) Force it to retract or 2) disable this pop-up completely as I don't have a use for it. At present I have to close and restart JTALert.

If I leave the system monitoring a band, I use the decode history window to see if I have missed anything while I have been away from the shack.  I am only really interested in any decodes that have an alert set for them.   Is there any other way to see this small subset in a different way, or.. is there a way to limit what goes into the decode history window (eliminating in order, the plain rows, or the the grey rows) or increase the capacity of the file above 2000 which typically fills up in 1-2 hours on a busy band.

Using W7 and V2.12.10 on a fast desktop machine (i7 8GB and SSD)

73,

Dave  G3UEG

Dave,

There is no need to restart JTAlert to get the Band Activity popup to retract, Just move your mouse pointer over the Band Display in the titlebar, then move it off that area, that will cause the popup to retract (normally is should only display while the mouse pointer is hovering over the Band numbers area).

If you don't want the Band Activity displayed, visit the Settings, "Window -> Band Activity Display" and uncheck the enable checkbox (top left of that page).

Regarding filtering of the Decodes History display to remove unwanted decode listings. Sorry, that is not possible. However, the new Decodes History component of JTAlert V3 (still many months from release) does provide that sort of real-time filtering. While JTAlert V3 is a long way off, its Decodes History component is coming to the next JTAlert V2 release. It has been with the Beta testers now for several weeks and I am happy to move it into JTAlert V2, that has been coded and I am now wrapping up the help file for this new Decodes History. I expect to release within the next 2 weeks.

de Laurie VK3AMA




locked Re: JTAlert 2.12.10 not responding

HamApps Support (VK3AMA)
 

On 18/01/2019 4:36 pm, Dan Malcolm wrote:

Laurie,

I’m having trouble getting JTAlert to start successfully.  It starts up, I the “Reading Settings Data Standby” notice and a little while later I “Not Responding” in the title bar.  I have tried a warm reboot of the computer (Win10 x64) and a power off reboot, without success.  I have also tried reinstalling.  When I kill the process, it leaves behind  “JTAlert Plugins Helper”.  That may be normal since JTAlert was not shut down normally.  I can shut it down via the red ‘x’ in the upper right corner.

Now I’m wondering if there is an INI file that’s corrupted.  What do you recommend?

__________

Dan – K4SHQ

Dan,

When this occurs, ignore it and wait a couple of minutes. Does JTAlert eventually startup?

de Laurie VK3AMA


locked JTAlert 2.12.10 not responding

 

Laurie,

I’m having trouble getting JTAlert to start successfully.  It starts up, I the “Reading Settings Data Standby” notice and a little while later I “Not Responding” in the title bar.  I have tried a warm reboot of the computer (Win10 x64) and a power off reboot, without success.  I have also tried reinstalling.  When I kill the process, it leaves behind  “JTAlert Plugins Helper”.  That may be normal since JTAlert was not shut down normally.  I can shut it down via the red ‘x’ in the upper right corner.

 

Now I’m wondering if there is an INI file that’s corrupted.  What do you recommend?

 

__________

Dan – K4SHQ

 


--
Dan - K4SHQ


locked Re: Missing or invalid call sign program will now exit #FT8 #HRD

Renato PY8WW
 

Thanks . Problem Solved .

73

PY8WW

Em qui, 17 de jan de 2019 às 07:47, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> escreveu:

On 17/01/2019 8:06 pm, Renato PY8WW via Groups.Io wrote:
I'm trying to install jtalert on a new machine with windows 10, I get the following message: Missing or invalid call sign program will now exit, I already tried to edit the registry with regedti, but the same error persists, can anyone help me?

73
PY8WW

OM,

If JTAlert was installed correctly, there should be no need to edit the Registry.
What Registry entry did you edit?

Check your Registry is correct. Look under the "\HKEY_CURRENT_USER\Software\HamApps" key. There should be a string value for your callsign.

eg...

   

de Laurie VK3AMA


locked Re: NULL Country for TO7D

HamApps Support (VK3AMA)
 

On 18/01/2019 8:17 am, Michael Black via Groups.Io wrote:
TO7D comes up with an empty country for some reason.

From the FCC database shows

INSERT INTO "data" VALUES('TO7D',NULL,'Y','N','20180404');

So been around a while.

de MIke W9MDB
That FCC database entry is perfectly valid. If you examine the schema, the second column in the above sql command is labelled "state". It holds the US State returned from the initial FCC data dump that is used to populate the fcc_lotw_eqsl.sqlite file. A null state for TO7D is valid.

The reason that JTAlert doesn't show a DXCC name for TO7D is not related to the fcc_lotw_eqsl.sqlite file, it is due to the Callsign not identifying the Country of issue. While most Callsigns identify their Country due to the Callsign naming and the ITU assignments. That is not possible for "TO" callsigns, there can be in a number of different DXCC Entities. Put TO7D into DXLab DXView and you will see that it also doesn't identify the Country.

The only way to identify the operating Country of the "TO" callsigns (and of some special event callsigns where the Country cannot be determined from the structure of the Callsign) is through Callsign overrides. JTAlert, like WSJT-X and many other applications use the cty.dat file for these overrides. TO7D is not included in that file.

As I type this, these are the current "TO" callsign overrides in the cty.dat file.

   

Note from the above three different Entities (FG,FM,FY) being used by "TO" Callsigns.

While the cty.dat file doesn't contain a TO7D callsign override,  the JTAlert version of cty.dat (a much faster lookup sqlite build) now includes the override. If you install the latest HamApps Callsigns Database, JTAlert will start identifying that TO7D as in Guadeloupe. If you don't use the Callsign database, than when you will need to wait for the next JTAlert release (All JTAlert releases include internally an updated build of the cty.dat file)

de Laurie VK3AMA


locked Re: One issue and one enquiry

HamApps Support (VK3AMA)
 

On 18/01/2019 4:09 am, David Gould wrote:
I have found JTAlert most helpful in finding new band/slots and new band/states and band/zones.  I have one issue and one enquiry.

Regularly the box that pops up from the top RHS of the main window (pink green and blue) sticks in the extended position and does not retract.  Is there a way to either 1) Force it to retract or 2) disable this pop-up completely as I don't have a use for it. At present I have to close and restart JTALert.

If I leave the system monitoring a band, I use the decode history window to see if I have missed anything while I have been away from the shack.  I am only really interested in any decodes that have an alert set for them.   Is there any other way to see this small subset in a different way, or.. is there a way to limit what goes into the decode history window (eliminating in order, the plain rows, or the the grey rows) or increase the capacity of the file above 2000 which typically fills up in 1-2 hours on a busy band.

Using W7 and V2.12.10 on a fast desktop machine (i7 8GB and SSD)

73,

Dave  G3UEG

Dave,

There is no need to restart JTAlert to get the Band Activity popup to retract, Just move your mouse pointer over the Band Display in the titlebar, then move it off that area, that will cause the popup to retract (normally is should only display while the mouse pointer is hovering over the Band numbers area).

If you don't want the Band Activity displayed, visit the Settings, "Window -> Band Activity Display" and uncheck the enable checkbox (top left of that page).

Regarding filtering of the Decodes History display to remove unwanted decode listings. Sorry, that is not possible. However, the new Decodes History component of JTAlert V3 (still many months from release) does provide that sort of real-time filtering. While JTAlert V3 is a long way off, its Decodes History component is coming to the next JTAlert V2 release. It has been with the Beta testers now for several weeks and I am happy to move it into JTAlert V2, that has been coded and I am now wrapping up the help file for this new Decodes History. I expect to release within the next 2 weeks.

de Laurie VK3AMA




locked NULL Country for TO7D

Michael Black
 

TO7D comes up with an empty country for some reason.

From the FCC database shows

INSERT INTO "data" VALUES('TO7D',NULL,'Y','N','20180404');

So been around a while.

de MIke W9MDB



locked Re: One issue and one enquiry

Joe - W9RF
 

David,


If you are talking about the "Unique Call Signs TX/RX per Band" pop up window

Just mouse over the row of bands on top of the popup

160 80 60 40 ,ect

That is supposed to close it..



73,

W9RF - Joe



From: David Gould <dave@...>
To: Support@HamApps.groups.io
Sent: Thursday, January 17, 2019 11:09 AM
Subject: [HamApps] One issue and one enquiry

I have found JTAlert most helpful in finding new band/slots and new
band/states and band/zones.  I have one issue and one enquiry.

Regularly the box that pops up from the top RHS of the main window (pink
green and blue) sticks in the extended position and does not retract. 
Is there a way to either 1) Force it to retract or 2) disable this
pop-up completely as I don't have a use for it. At present I have to
close and restart JTALert.

If I leave the system monitoring a band, I use the decode history window
to see if I have missed anything while I have been away from the shack. 
I am only really interested in any decodes that have an alert set for
them.   Is there any other way to see this small subset in a different
way, or.. is there a way to limit what goes into the decode history
window (eliminating in order, the plain rows, or the the grey rows) or
increase the capacity of the file above 2000 which typically fills up in
1-2 hours on a busy band.

Using W7 and V2.12.10 on a fast desktop machine (i7 8GB and SSD)

73,

Dave  G3UEG







Virus-free. www.avg.com


locked One issue and one enquiry

David Gould
 

I have found JTAlert most helpful in finding new band/slots and new band/states and band/zones.  I have one issue and one enquiry.

Regularly the box that pops up from the top RHS of the main window (pink green and blue) sticks in the extended position and does not retract.  Is there a way to either 1) Force it to retract or 2) disable this pop-up completely as I don't have a use for it. At present I have to close and restart JTALert.

If I leave the system monitoring a band, I use the decode history window to see if I have missed anything while I have been away from the shack.  I am only really interested in any decodes that have an alert set for them.   Is there any other way to see this small subset in a different way, or.. is there a way to limit what goes into the decode history window (eliminating in order, the plain rows, or the the grey rows) or increase the capacity of the file above 2000 which typically fills up in 1-2 hours on a busy band.

Using W7 and V2.12.10 on a fast desktop machine (i7 8GB and SSD)

73,

Dave  G3UEG

14121 - 14140 of 37225