Date   

locked 32 bit (x86) JTAlert 2.50.0 beta build available for testing.

HamApps Support (VK3AMA)
 

Users running 32 bit (x86) Windows please try this new 32 bit specific build of JTAlert 2.50.0

This build has been successfully run by one of the Test Team with no observed problems. We need to get more 32 bit eyes on this build so am making it publicly available.

Note: This is a Beta build, as such it has an inbuilt expiry date after which it will cease functioning. The expiry is 56 days after the date of the build, not the install date. It will expire June 17.

https://dnl.HamApps.com/Beta/JTAlert.2.50.0.build.0004.Beta.Install.X86.exe <https://dnl.HamApps.com/Beta/JTAlert.2.50.0.build.0004.Beta.Install.X86.exe>

Please report your experiences with this build, good and bad. Post your messages to this topic thread.

de Laurie VK3AMA


locked Re: JTAlert 2.5 not able to TX with double click on Call in window.

Everett N4CY
 

Thank you LaurieūüėÉ

Everett N4CY

On Thursday, April 22, 2021, 3:50 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 23/04/2021 6:31 am, Everett N4CY via groups.io wrote:
JTAlert 2.5 not able to TX with double click on Call in window. I am using 2.3.0 WSJT-X, but am not able to start TX with a double click on a call in JTAlet call sine window.

Everett N4CY

WSJT-X going into TX is controlled by WSJT-X itself. JTAlert does not control the auto-TX behavior,. Likely you're double-clicking a callsign that corresponded to a non-CQ decode. In that situation WSJT-X will setup for the QSO but not enable TX.

If WSJT-X is not populating the DXCall in response to a callsign click event from JTAlert, that will be due to not having the "Accept UDP requests" setting unchecked. This setting is in the WSJT-X settings, reporting Tab.

de Laurie VK3AMA


locked Re: JTAlert 2.5 not able to TX with double click on Call in window.

HamApps Support (VK3AMA)
 

On 23/04/2021 6:31 am, Everett N4CY via groups.io wrote:
JTAlert 2.5 not able to TX with double click on Call in window. I am using 2.3.0 WSJT-X, but am not able to start TX with a double click on a call in JTAlet call sine window.

Everett N4CY

WSJT-X going into TX is controlled by WSJT-X itself. JTAlert does not control the auto-TX behavior,. Likely you're double-clicking a callsign that corresponded to a non-CQ decode. In that situation WSJT-X will setup for the QSO but not enable TX.

If WSJT-X is not populating the DXCall in response to a callsign click event from JTAlert, that will be due to not having the "Accept UDP requests" setting unchecked. This setting is in the WSJT-X settings, reporting Tab.

de Laurie VK3AMA


locked Re: JTAlert 2.5 not able to TX with double click on Call in window.

Joe Subich, W4TV
 

Callsign window -> Settings -> callsigns ... to what is "WSJTX Reply"
set?


73,

... Joe, W4TV

On 2021-04-22 4:31 PM, Everett N4CY via groups.io wrote:
JTAlert 2.5 not able to TX with double click on Call in window. I am using 2.3.0 WSJT-X, but am not able to start TX with a double click on a call in JTAlet call sine window.
Everett N4CY


locked JTAlert 2.5 not able to TX with double click on Call in window.

Everett N4CY
 

JTAlert 2.5 not able to TX with double click on Call in window. I am using 2.3.0 WSJT-X, but am not able to start TX with a double click on a call in JTAlet call sine window.

Everett N4CY
 


locked Re: Error Messages on loading New Version 2.50.0 - need Help

Joe Subich, W4TV
 

Yes, there is an issue with 32 bit and Net 5.0 Framework.

Laurie is testing a separate 32 bit executable of 2.50.0 with
some members of the beta team now. QRX for news in a few days.
In the meantime, drop back to the last version (pre NET 5.0).
73,

... Joe, W4TV

On 2021-04-22 10:33 AM, David Simms wrote:
Same error issues here with Windows 10 - 32 bit.
--
Thanks,
David - N4IW


locked Re: Error Messages on loading New Version 2.50.0 - need Help

David Simms
 

Same error issues here with Windows 10 - 32 bit.  
--
Thanks,
David - N4IW


locked Re: dB Alert

Joe Subich, W4TV
 

Callsigns Window -> Settings -> Callsigns and click/check dB.
Note, you must be displaying "country" (the second line) for
dB to be available.

73,

... Joe, W4TV

On 2021-04-22 2:26 PM, Neil Foster wrote:
I have searched the help and recall the old format in JT Alert would display the dB in the window. I am not seeing that on the new format. Is it possible to enable that on the new program? I have not found how to activate it if it is possible...TNX and stay well all    Neil   N4FN


locked dB Alert

Neil Foster
 

I have searched the help and recall the old format in JT Alert would display the dB in the window. I am not seeing that on the new format. Is it possible to enable that on the new program? I have not found how to activate it if it is possible...TNX and stay well all    Neil   N4FN


locked Re: Line 10385

Gabriel - M0JHV
 
Edited


Long story short. Back in time, I have encountered a sound issue starting with two previous JTAlert versions. I restrained the issue by suspecting there is something related to Logging with HRD V5/V6. I have on my HRDLogbook two databases, one is 5.2x and another one is 6.3+. When I was disabling the logging, everything worked (is working fine). Same thing for Logging with HRD V5. But when II chose to log with V6(6.3) - my M0JHV being linked to a 6.3 database, the things are going bad (only when the sound is ON). Every test for sound (of course on the laptop speakers), or a JTAlert generated sound makes the program shutdown (sometimes with some errors line, sometimes with no error).
The situation with 2.50.0 is quite similar - I hoped that I'll solve this issue by upgrading JTAlert - the crashes are now present with line 10385. As advised I removed (moved in another folder all config.sqlite files) and a new config.sqlite was generated (added) by JTAlert. So far so good, I made sound tests with success. Obviously with the default configuration, NO LOG. When I chose to log with HRD V5/V6 and I select the v6.3+ database, the same thing is happening - crash with line 10385. So, in my opinion, it's something related between sound on and HRD v.6.3. If you still consider it necessary I can send the config.sqlite.
 
73, de Gabriel M0JHV


locked Re: Line 10385

Gabriel - M0JHV
 

Hi Laurie,

Yes, the line is always the same, but If I'm turning the monitor off, the error does not appear anymore. When I turned the monitor on again, another line (10376 instead of 10385 as far as I remember) appeared.
I'll check soon to start JTAlert without a config file and I come up with the results and I'll send the file directly to you.

Thanks again, Gabriel M0JHV


locked Re: Error Messages on loading New Version 2.50.0 - need Help

 

Yes, 32 bit.  Tnx you.  Older version is just fine.

Glenn


locked Re: JT Alert 2.50.0 stopped by FrameworkCheck

Ed Wilson
 

Laurie,

I am experiencing the same problems with 32-bit Windows 10 so the issue is not limited to Windows 7 32-bit.

Ed, K0KC


locked Re: B4 bad decoding

HamApps Support (VK3AMA)
 

On 22/04/2021 6:07 pm, Jacques Corbu wrote:
HI Laurie  did you get the  ADIF export from Denis

I have same issue  9G5FI  keeps coming up i.e. I have worked him on multiple bands yet 20M ft8 keeps showing as wanted even though confirmed LoTW etc ?

He is in the wsjtx log as well as HRD lV6.7.   SQL log (mariaDB)   and in the  B4logV2 on JTAlert v2.5

I do not want to put him on ignored callsign  as need that country on some bands since ignored cannot be selected by band 

Thanks Jacques F1VEV  great work on 2.50

Yes, I have the adif file and your support request. It has been a bit busy today. I will look at them tomorrow.

de Laurie VK3AMA


locked Re: B4 bad decoding

Jacques F1VEV
 

HI Laurie  did you get the  ADIF export from Denis

I have same issue  9G5FI  keeps coming up i.e. I have worked him on multiple bands yet 20M ft8 keeps showing as wanted even though confirmed LoTW etc ?

He is in the wsjtx log as well as HRD lV6.7.   SQL log (mariaDB)   and in the  B4logV2 on JTAlert v2.5

I do not want to put him on ignored callsign  as need that country on some bands since ignored cannot be selected by band 

Thanks Jacques F1VEV  great work on 2.50


locked Re: Messaging window callsign editing

K9MK
 

Regarding "What is the issue you want to resolve by removing callsigns?", my issue was I had about 10 DX stations message me Sunday, all their calls stayed for the duration of the session. Note: I seldom turn off the station or reboot things. I wanted to message the one or two hams that I frequently SMS between but I had to keep pointing back at their calls within the long list of "one and done" messages.  I was looking for a way to edit-delete them out without closing and reopening the App.

On the Message Options window, I found that option box and made the adjustment, thanks.

73  Mike  K9MK


locked Re: JT Alert 2.50.0 stopped by FrameworkCheck

Laurie, VK3AMA
 

On 22/04/2021 9:41 am, Eric Alchowiak wrote:

Here's a capture of FrameworkCheck which might be a clue.

Eric A
KO0V

Eric,

I know it is premature, and I may regret the post in the future, but this is what I posted to the JTAlert Test group today after an initial test of 2.50.0 on a 32bit Win10 PC that had been recently failing with the same results as you.

   

This was not an exhaustive test, but it is significant progress IMO.

de Laurie VK3AMA


locked Re: JT Alert 2.50.0 update and now nothing works on JT Alert app

HamApps Support (VK3AMA)
 

On 19/04/2021 11:18 pm, Bryan Downes wrote:
Many thanks for the extra bits Laurie and whilst a bit small for my old eyes they are readable on my 27" 5k iMac.

All the new windows are zoomable. If the text is too small zoom the window, the max is 300%.
Instructions are in the 2.50.0 features help file or look under the help view of the Options popup (click the gear icon).

de Laurie VK3AMA


locked Re: DT explanation request

HamApps Support (VK3AMA)
 

On 21/04/2021 8:57 am, Alessandro Gorobey via groups.io wrote:
thanks for the quick response, but the value is always +1,0 (one comma zero) and never change.

now my clock is off 0.294ms and there is over 20 decodes per cycle

last 100 DT are
 -2.2  -1.0  -0.6  -0.6  -0.6  -0.4  -0.2  -0.2  -0.2  -0.2  -0.1  -0.1  -0.1  -0.1  -0.1  -0.1  -0.0   0.0   0.0  -0.0  -0.0   0.0   0.0   0.0   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.2   0.2   0.2   0.2   0.2   0.2   0.2   0.2   0.2   0.3   0.3   0.3   0.3   0.3   0.3   0.4   0.4   0.5   0.6   0.6   0.6   0.6   0.7   0.7   0.8   0.8   0.8   0.9   0.9   1.0   1.2

the media give me a value of about 0.1 as expected

Compliments again


73 Sandro IW3RAB

RRR, I'll take a closer look at the code.
Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: 2.5.0 -- AutoIt Error

HamApps Support (VK3AMA)
 

On 21/04/2021 11:25 am, David Merchant - K1DLM wrote:
I'm getting an AutoIT error every time I try to launch JTAlert 2.50.  Specifically, the error says "Line 6817 (File C:\Program Files(x86)\HamApps\JTAlert\JTAlert.exe)  Error: Subscript used on non-accessible variable.

I was able to get it to load initially and was using the software.  However, it wouldn't let me select a station for my next QSO, so I tried restarting it.  That's when the error occured.

Any suggestions?

Thanks & 73,

Dave
K1DLM

Try starting JTAlert without a config file. There may be something in the config that is tripping up JTAlert. See the JTAlert Help file (not the 2.50.0 features help), "Troubleshooting -> Setting Changes Not Remembered" topic. It explains where to find the config file. It may be worth trying to restore an old backup of the config.sqlite file first, explained in that help topic, before proceeding to starting JTAlert without a config file.

If starting JTAlert without a config file corrects the problem, I would greatly appreciate it if you could send me the problem config.sqlite file for examination. send it direct (not via this group) to VK3AMA.Ham.Apps [at] gmail.com

let me know your results.

de Laurie VK3AMA

4081 - 4100 of 38444