Date   

Re: JT Alert crashes

HamApps Support (VK3AMA)
 

On 10/11/2020 12:19 pm, tomloock@... wrote:
JT Alert would start up but just closed after 1 decode cycle.  I thought it might be a windows update but not sure if that is the problem or not.


--
73 Tom K9VER

If JTAlert is crashing after every startup, the cause is unlikely to be the random memory/cpu pressure issues that have been discussed.

Have you tried downgrading to an earlier version of JTAlert? Try 2.16.14

If you get the same crashing with an earlier version of JTAlert, that may be caused by a corrupt JTAlert config file, but that is very unlikely as I have never seen a corrupt config bring down JTAlert. You can try renaming the config file to say "config.sqlite.save" and then starting JTAlert which will automatically create a new config. If you still get a crash, the likely cause is interference from you PC Protection software. My money is on your Protection software as the culprit.

You config file can be found at %localappdata%\HamApps\K9VER\config\JTAlertX\config.sqlite

de Laurie VK3AMA


Why no JTAlert colors in JTDX?

Gordon Brown
 

Why doesn't JTALert color JTDX decodes like it does with WSJT-X?
WHen are you going to add that for us JTDX users?


Re: JT Alert crashes

tomloock@...
 

I checked the memory utilization and no program is using more than 5% so I don't think that is my problem.  What is confusing about this is that everything was working fine and I have not been on FT8 for about a month and when I tried to go on FT8 that is when JT Alert would start up but just closed after 1 decode cycle.  I thought it might be a windows update but not sure if that is the problem or not.


--
73 Tom K9VER


Re: JTalert with WSJT and ACLog

Terence Taylor <n6mon@...>
 

All of that is correct and how it is set,

On Monday, November 9, 2020, 3:11:39 PM PST, David De Coons <rocketnj@...> wrote:


In WSJT-X Settings/Radio you should have it set to IC-7300 and have mode set to Data/Pkt. Then radio should be in USB Data

Dave wo2x


-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Terence Taylor
Sent: Monday, November 9, 2020 4:56 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTalert with WSJT and ACLog

Answers below

On 11/9/2020 10:49 AM, David De Coons wrote:
>
> In WSJT-X  radio setup do you have the mode set to DATA/PKT? *Yes*
>
> I am using WSJT-X 2.2.2, JTAlert 2.16.15, and AC Log 6.7. The radio is a Flex 6700.
>
> *2.2.0 2.16.14                      6.7*
>
> In AC Log under Settings/Rig Interface use Mode Determined by Rig. The radio should be set to USB data mode. What is your radio?
>
*Yes IC-7300*












Re: JTalert with WSJT and ACLog

David De Coons
 

In WSJT-X Settings/Radio you should have it set to IC-7300 and have mode set to Data/Pkt. Then radio should be in USB Data

Dave wo2x

-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Terence Taylor
Sent: Monday, November 9, 2020 4:56 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTalert with WSJT and ACLog

Answers below

On 11/9/2020 10:49 AM, David De Coons wrote:

In WSJT-X radio setup do you have the mode set to DATA/PKT? *Yes*

I am using WSJT-X 2.2.2, JTAlert 2.16.15, and AC Log 6.7. The radio is a Flex 6700.

*2.2.0 2.16.14 6.7*

In AC Log under Settings/Rig Interface use Mode Determined by Rig. The radio should be set to USB data mode. What is your radio?
*Yes IC-7300*


Re: JTalert with WSJT and ACLog

Terence Taylor <n6mon@...>
 

Answers below

On 11/9/2020 10:49 AM, David De Coons wrote:

In WSJT-X  radio setup do you have the mode set to DATA/PKT? *Yes*

I am using WSJT-X 2.2.2, JTAlert 2.16.15, and AC Log 6.7. The radio is a Flex 6700.

*2.2.0 2.16.14                       6.7*

In AC Log under Settings/Rig Interface use Mode Determined by Rig. The radio should be set to USB data mode. What is your radio?
*Yes IC-7300*


Re: JTalert with WSJT and ACLog

David De Coons
 

 

In WSJT-X  radio setup do you have the mode set to DATA/PKT?

 

I am using WSJT-X 2.2.2, JTAlert 2.16.15, and AC Log 6.7. The radio is a Flex 6700.

 

In AC Log under Settings/Rig Interface use Mode Determined by Rig. The radio should be set to USB data mode. What is your radio?

 

 

 

73

Dave wo2x

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Terence Taylor
Sent: Monday, November 9, 2020 11:00 AM
To: Support@HamApps.groups.io
Subject: [HamApps] JTalert with WSJT and ACLog

 

I have ACLog set up and installed JTAlert for WSJTx. The contacts appear in ACLog, the only issue is that the mode gets sent as SSB not JT8 and the signal reports get set as 59 not the WSJTx signal reports (DBm).

 


Re: JTAlert Not Responding When Moving from DX to Local

Robert A Wilson
 

Dave,
Thanks for your response. I wonder if this could be due to some filtering setting. With that said, I'm seeing the US stations on the grid and I'm clicking on them to respond to CQs. If that was set, they shouldn't show up, right?
Robert


On Sun, Nov 8, 2020 at 8:14 PM Dave Garber <ve3wej@...> wrote:
perhaps you have a filter set to not show local  (usa)
Dave Garber
VE3WEJ / VE3IE


On Sun, Nov 8, 2020 at 6:58 PM Robert A Wilson <fishnscout@...> wrote:
Off and on I've had trouble with JTAlert not responding in what I thought was random occurrences. In the last few days with the bands opening a bit and focusing on DX, I've noticed that it doesn't seem to have this issue when working DX stations. As soon as I click on a station in the US, the JTAlert memory jumps up about 10 MBs and the window shows not responding. If I let it sit, it will eventually quickly display what was missed and start functioning again. Does anyone have any ideas as to what might be causing this?
Thanks,
Robert
KN4CNU


Re: JT Alert crashes

Ron / W4MMP
 

Hi Tom,

Start the task manager and check on CPU and memory utilization before starting JTalert.   If you have CPU or memory pressure (more than lets say 80%),  then you need to find what is consuming the resources.   If that is OK, start JTalert and check again.  Some have found that system utilization plays a role in this problem.

73,
Ron / W4MMP
On 11/9/2020 12:29, tomloock@... wrote:

I finally got a chance to try your suggestion and it still does the same thing.  I renamed the HamApps folder and reloaded JT Alert and then set all the settings to where I wanted them and when I saved the settings JT Alert shutdown after 2 decode cycles.

Not sure where to go from here.

--
73 Tom K9VER


Re: JT Alert crashes

tomloock@...
 

I finally got a chance to try your suggestion and it still does the same thing.  I renamed the HamApps folder and reloaded JT Alert and then set all the settings to where I wanted them and when I saved the settings JT Alert shutdown after 2 decode cycles.

Not sure where to go from here.

--
73 Tom K9VER


JTalert with WSJT and ACLog

Terence Taylor <n6mon@...>
 

I have ACLog set up and installed JTAlert for WSJTx. The contacts appear in ACLog, the only issue is that the mode gets sent as SSB not JT8 and the signal reports get set as 59 not the WSJTx signal reports (DBm).



Re: JTAlerts 2.16.15 crashes

Mike N8FRI
 

Yesterday, I had this same warning suddenly show up and shut down JTAlert.  I rebooted the computer, restarted JTAlert and the problem continued.  It would pop up about 1 minute into program start.  Vers .15 has performed flawlessly until yesterday.  The only variable in operation was that I had turned off DXSummit submission. I turned it 
back on but that did not fix the problem.
Finally, I renamed the JTAlert "user" directory to JTAlert-old and reloaded the .15 version.  Of course I had to go in and reconfigure all of the settings but after about 15 minutes (helped by the fact that I use PrntScr to make record of all of the critical settings) I was back up and running.  I ran the program for about an hour with no glitches.  
I am not sure if turning off DXSummit submission may have corrupted the user files or not?
I will not mess with that setting again as I am quite happy to be back up on FT8.
As Mike said, hopefully corrected in a future version.
Mike, N8FRI


Re: Alert For "73" In Standard Message

Patrick Hung
 

Will do. Thank you.

--
Patrick
W2TAR


Re: Alert For "73" In Standard Message

HamApps Support (VK3AMA)
 

On 9/11/2020 4:43 pm, Patrick Hung wrote:
That DID IT, Laurie, thank you thank you!

I have another question, but I'll research it some more and maybe make a new post if still needed.


Best regards,

Patrick Hung
Patrick,

Good to hear.

BTW, there will be some changes to the 73 & RR73 highlighting in the next build. The requirement to have CQ's enabled is being removed.

Yes, please start a new message thread. That avoids your followup message being lost in my threaded inbox display where I have handled and answered message threads collapsed.

de Laurie VK3AMA


Re: Alert For "73" In Standard Message

Patrick Hung
 

That DID IT, Laurie, thank you thank you!

I have another question, but I'll research it some more and maybe make a new post if still needed.


Best regards,

Patrick Hung


On Sun, Nov 8, 2020 at 8:32 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

I went back and examined the code to see if there is another potential
cause for the loss of "73" highlighting. There is, the CQ Alert needs to
be enabled.

 From the release notes...
> 2.16.8 (19-Jun-2020)
>
>   New Features:
>
>     - WSJT-X decode highlighting: If the JTAlert CQ Alert is enabled
> than WSJT-X
>        decodes ending in "73" or "RR73", indicating that the DX
> station has ended
>        their QSO, will have the "73" or "RR73" colored with the CQ
> Alert colors.

de Laurie VK3AMA







--
Patrick
W2TAR


Re: Alert For "73" In Standard Message

HamApps Support (VK3AMA)
 

I went back and examined the code to see if there is another potential cause for the loss of "73" highlighting. There is, the CQ Alert needs to be enabled.

From the release notes...
2.16.8 (19-Jun-2020)

  New Features:

    - WSJT-X decode highlighting: If the JTAlert CQ Alert is enabled than WSJT-X
       decodes ending in "73" or "RR73", indicating that the DX station has ended
       their QSO, will have the "73" or "RR73" colored with the CQ Alert colors.
de Laurie VK3AMA


Re: Republic of North Macedonia

HamApps Support (VK3AMA)
 

On 9/11/2020 11:15 am, Ron W3RJW via groups.io wrote:
I guess the point I was trying to make was that only the letter N. showed in the callsign display box.   There was nothing else.  Perhaps it's because I have 9 boxes across ? I am reporting what is perhaps a formatting problem where there is not room for N. Macedonia so only the N. shows ?
--
73
Ron, W3RJW

RRR, Understood.

It's your 9 callsign slot display that is the problem. There is insufficient room to display the already truncated "N. Macedonia".
When you get this type of excessive truncation, hover your mouse over the Callsign, the resulting tooltip shows the full non truncated Country name.

Measuring the length of a display string taking into consideration the current display resolution, display pixel density, and the amount of area available to display the string is not difficult, but would add additional CPU overhead affecting decode display speed. I will not be adding that to the current V2 series of JTAlert. Having said that, the new unlimited callsigns display of JTAlertV3 which is coming to JTAlertV2 in the near future doesn't suffer from Country name truncation. See this previous post for some screen-shots of the new display.

de Laurie VK3AMA


Re: Alert For "73" In Standard Message

HamApps Support (VK3AMA)
 

On 9/11/2020 1:47 pm, Patrick Hung wrote:
Within the last few days, I noticed that all decodes with "73" in the text were being highlighted in green, with white fonts; this was extremely useful to me, as tailing a 73 works well for me in completing QSOs. Unfortunately, this stopped working after I quit out of the program for a short break. Can someone tell me how I can turn it back on?

By the way, I'm assuming that this is a JTAlert, and not a WSJT-X feature.

Thanks for any help.

Patrick
W2TAR

Two places to look, but neither should change without user-intervention.
  1. JTAlert Settings window, "Applications -> WSJT-X/JTDX" section.


  2. WSJT-X Settings. Reporting Tab make sure "Accept UDP requests" is ticked.

If both these settings are correct, then try a Windows restart.

FYI, Decode coloring only works with WSJT-X. JTDX does not support coloring of decodes by 3rd party applications like JTAlert. The JTDX people chose to remove that functionality from the original WSJT-X code.

de Laurie VK3AMA


Alert For "73" In Standard Message

Patrick Hung
 

I'm fairly new to JTAlert, and am just learning the wealth of features in the software.

Within the last few days, I noticed that all decodes with "73" in the text were being highlighted in green, with white fonts; this was extremely useful to me, as tailing a 73 works well for me in completing QSOs. Unfortunately, this stopped working after I quit out of the program for a short break. Can someone tell me how I can turn it back on?

By the way, I'm assuming that this is a JTAlert, and not a WSJT-X feature.

Thanks for any help.

Patrick
W2TAR


Re: JTAlert Not Responding When Moving from DX to Local

Dave Garber
 

perhaps you have a filter set to not show local  (usa)
Dave Garber
VE3WEJ / VE3IE


On Sun, Nov 8, 2020 at 6:58 PM Robert A Wilson <fishnscout@...> wrote:
Off and on I've had trouble with JTAlert not responding in what I thought was random occurrences. In the last few days with the bands opening a bit and focusing on DX, I've noticed that it doesn't seem to have this issue when working DX stations. As soon as I click on a station in the US, the JTAlert memory jumps up about 10 MBs and the window shows not responding. If I let it sit, it will eventually quickly display what was missed and start functioning again. Does anyone have any ideas as to what might be causing this?
Thanks,
Robert
KN4CNU