Date   

locked Re: JTAlert Win10 missing menus - offering debug help

HamApps Support (VK3AMA)
 

On 23/07/2019 12:24 pm, Jason Frazier wrote:
I saw that the developers of JTAlert are having trouble identifying how to reproduce the missing menu problem that happens only for a few users.  I am offering my debugging help.  I am a seasoned QA Developer and know my way around code, debugging, and identifying commonalities in rare scenarios.  I have two computers, one with the JTAlert menu issue and one without.  Please have the developers reach out to me if interested in a joint debugging session or other assistance.

73 de Jason W7DM
Jason,

Thanks for the offer, but the JTAlert V2 code doesn't lend itself to contemporary debugging techniques.

AutoIT used to code JTAlert V2 is rather primitive. It doesn't support single-stepping through the code in debug mode, in fact , it doesn't have a debug mode. There is no ability to set breakpoints or watch individual variables. The IDE is a glorified text editor that provides color syntax highlighting, but not much more. There is none of the functionality of a modern IDE, like Visual Studio.

AutoIT doesn't produce debug or release builds, there are no .pdb like files your probably used to when debugging .NET code. Debugging is little more than littering the code with console writes and logging of variable values and that is only useful if you have homed in on the potential offending code. There are no stack-traces to examine.
Basically, an AutoIT executable is not much better than a compiled batch script file.

The single-threaded, non-object-oriented, synchronous (blocking) code produced is not fit for purpose any longer (and hasn't been for a number of years). It was adequate when JTAlert was first coded as a quick proof-of-concept, but has long out-lived its usefulness. The code is now littered with hacks & workarounds. The code, in particular the code for handling title-bar display of menus and band-activity, involves hooks into many of the standard Windows message queues and many api calls into standard Windows dlls, mimicking C+ code functionality.

JTAlert is currently undergoing a ground-up rewrite, using a modern object oriented language, .NET C#, which is allowing me to easily produce very fast (compared to AutoIT) multi-threaded, asynchronous code.

Any time spent trying to debug JTAlert V2 would be a waste, IMO.

I'll keep you in mind if I need access to someone with you skill set.

de Laurie VK3AMA



locked Re: Blocage JTAlert

HamApps Support (VK3AMA)
 

On 25/07/2019 7:49 pm, f8nhf wrote:
 I have JTAlert blockages  I use as software JTDS RC139, JTAlert 2.13.10, luxury radio ham and WIN10 

I contact a jtdx station and ask me to log it "click OK" until everything is OK so I validate and I receive an error message "qso no logged" screenshot and JTAlert is blocked "no answer" I click on ok of the error message, the QSO is registered in HRD the error message disappears jJTAlert remains blocked still about 1 minute it restarts alone the qso in question was not marked in B4 on jtalert on jTDX it is marked B4 then everything is normal some QSO later the block starts again Grrr  I had the hrd Hot linen everything is fine for the PC because still under garie everything is fine also it is an I3 3.60 Mhz 16 GB of memory I have reset the PC to factory settings as the radio software 

That's the problem.

hoping to have solutions

73' Denis F8NHF 
Denis,

Your error image shows that JTAlert never received a response from HRDLogBook after the TCPIP Logging command was sent.

   

Normally the response received from HRDLogbook is similar to this...
Ham Radio Deluxe Version RELEASE 6.6.0.237
[c] Found 38 Valid Fields...
Added 52 Fields to My Logbook...
[c] [c] 

I received your support files. They confirm the non-response from HRDLogbook, but they also show that many QSO are being logged successfully.  The non-logging is random. If there was a configuration/settings error, I would expect every QSO logged would fail, not a small subset of the QSOs.

Your HRDLogbook.trace file shows the last QSO logged failed, with 8 previous QSOs logged successfully. I am seeing far more success loggings than failures.

Adjusting the "Check QSO time" setting in JTAlert, as advised by Mike W9MDB, will not correct this problem.

Unfortunately, I have no idea what the problem could be. For some reason, intermittently, either HRDLogbook is not receiving the TCP command from JTAlert, or it is not responding to the command, there is no way of knowing.

Sorry, I don't have an answer for you.

de Laurie VK3AMA
 


locked Re: JTAlert not Keeping up

John Petrocelli
 

Hello,
 
    Just tonight I installed the newest version. 
   YES it is all there now.

   Thanks & God Bless for all your GREAT work !
John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 7/25/2019 10:23 PM, HamApps Support (VK3AMA) wrote:
On 24/07/2019 12:46 pm, John Petrocelli via Groups.Io wrote:
   Normally on the left side of the JTAlert display it may indicate "New Band" (for example) for a particular callsign.  After working that station I would expect to see it change to "Worked B4" after the logging.  However, it does not change when using FT4.  Yet at the top the "shading" will reflect the "B4" status along with a "B4" after the station's callsign.  It does not seem how long I wait.

When running FT8 the status will change from "New Band" to "Worked B4".
Wondering if this is an anomaly.
John,

This is due to the partial FT4 support in the version of JTAlert your running. At the end of logging, JTAlert queries the log for an updated Bands/Mode confirmed/worked lists. Until full FT4 support is implemented, that query does not include FT4 (only JT65, JT9 & FT8) causing the resulting Bands/Modes worked/confirmed status to be incorrect and always show new band.

The good news is that full FT4 support is now available with JTAlert 2.14.0 just today released.

de Laurie VK3AMA




Virus-free. www.avast.com


locked Re: Auto Start not working with WSJT X 2.1

roond59
 

Laurie,

Thanks for the tips. It was WSJT-X set as administrator that was hanging it up. I unticked admin and away she goes!!

Thanks a million...GREAT program!


locked Re: JTAlert not Keeping up

HamApps Support (VK3AMA)
 

On 24/07/2019 12:46 pm, John Petrocelli via Groups.Io wrote:
   Normally on the left side of the JTAlert display it may indicate "New Band" (for example) for a particular callsign.  After working that station I would expect to see it change to "Worked B4" after the logging.  However, it does not change when using FT4.  Yet at the top the "shading" will reflect the "B4" status along with a "B4" after the station's callsign.  It does not seem how long I wait.

When running FT8 the status will change from "New Band" to "Worked B4".
Wondering if this is an anomaly.
John,

This is due to the partial FT4 support in the version of JTAlert your running. At the end of logging, JTAlert queries the log for an updated Bands/Mode confirmed/worked lists. Until full FT4 support is implemented, that query does not include FT4 (only JT65, JT9 & FT8) causing the resulting Bands/Modes worked/confirmed status to be incorrect and always show new band.

The good news is that full FT4 support is now available with JTAlert 2.14.0 just today released.

de Laurie VK3AMA


locked Re: Multiple Grids per QSO - Grid boundaries and corners. #DXLAB

HamApps Support (VK3AMA)
 

On 25/07/2019 10:19 am, Robert Wright wrote:
Bill, G4WJS:  You are correct.  We are just talking about JTAlert's scanning of the DXKeeper log.
That's correct. I will only add multiple grids per qso support to the Log Scanning function.

There is no intention at this time to add multiple grid logging as multiple grids are not conveyed using WSJT-X and as Bill pointed out unlikely to happen with the current protocols.
It will be left to the user to manually add any additional grids to the logged QSO if that station was operating from multiple grids.

de Laurie VK3AMA



locked Re: Auto Start not working with WSJT X 2.1

HamApps Support (VK3AMA)
 

On 25/07/2019 12:07 am, roond59 wrote:
As soon as I upgraded to version 2.1 my Auto Start function stopped working. Auto Start has been working great in previous versions of WSJT X.  I have the correct path in the JTAlert autostart tab and still no joy. Any tips or tricks would be greatly appreciated. TIA! 73 de Dan KG0AQ

Dan,

The most common cause for auto-start to fail is that Windows itself is preventing the action due to mismatch privilege levels between JTAlert and WSJT-X. Typically this is due to having WSJT-X set to run as Administrator. There is normally no need to run WSJT-X elevated.

Another possibility is that the WSJT-X executable path recorded in JTAlert is now incorrect. Try updating the wsjt-x entry in your auto-start section.

If you still can't get this to work, Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: no data is displayed

HamApps Support (VK3AMA)
 

On 24/07/2019 9:19 am, mosrite599@... wrote:
In my previous version when I hovered over right top of JTAlert title bar a box showing all active stations by band would appear. With 2.13.10 this box does not populate. What have I done wrong?
The window is displayed but no data is displayed.
The "Last Update" message at the bottom of the window is "Pending". There is no indication of UTC date and time.
Since "pending", testing the connection in the "Web Services-> TCPIP Network Port" section of the JTAlert configuration is OK
windows10   WSJT-X &JTDX

73   JH2NXM Ron
Ron,

Very likely your virus/malware protection is interfering with the "JTAlertBandData.Plugin" file which is responsible for downloading the data. Try temporarily disabling your protection software or add an exclusion for the
"JTAlertBandData.Plugin" file, located in the "plugins" directory under the install location of JTAlert.

Another possibility is that your internet connection is slow or dropping packets and the band data download (only ~150 bytes file size) is not completing before hitting the connection timeout.

Also worth checking is the "banddata.error" file using notepad or similar, its a simple text file, and may provide some clues as to what is happening.
It is located at %localappdata%l\HamApps\YOUR_CALLSIGN\session\JTAlertX\

Let me know what you find.
If you still can't resolve the issue, send me direct your public IP address (use whatsmyip.org) and I will check the Server logs to see if there is anything recorded for your IP.

de Laurie VK3AMA


locked New JTAlert 2.14.0 available - Full FT4 support. JT65-HF, HB9HQX & MixW no longer supported. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The Latest JTAlert version 2.14.0 is now available @ https://HamApps.com

Important Note: U
sers of MixW, JT65-HF or HB9HQX should NOT upgrade to this version as none of those applications are supported in 2.14.0 (and later). JTAlert 2.13.10 is the LAST version to support working with these applications. This is a permanent change. Removal of the support for these applications was previously announced on this group here and here.

The Release Notes...
  New Features:
    - FT4 mode is now fully supported. FT4 Alert tracking for all Alert types.
       The Bands worked/confirmed display now supports FT4. The BandActivity
       includes FT4 rx/tx counts.

  Changes:
    - MixW logging no longer available.
    - JT65-HF support no longer available.
    - HB9HQX JT65-HF edition support no longer available.
    - Minor cosmetic changes to accommodate FT4.
    - Band Activity now includes 2200m, 630m, 4m & 2m. Note: these additional
       Bands are visible in the status bar of the "Alternate Layout" build of
       JTAlert only. All Bands regardless of JTAlert build are shown in the popup.


de Laurie VK3AMA


locked Call sign field blank

Jim Austin
 

Win 7 user - Upgraded to WSJT-X 2.1.024FCDZ (the 64 bit version) and recently downloaded and installed JT-Alert 2.13.10 - I don't save the decode history so no files were deleted from my computer - I checked all the settings and ports - opened and closed the programs - rebooted the computer, restarted all programs (WSJT-X, JT Alert, Log4OM in that order) however, the call sign fields in JT Alert never populate. The band activity popup window is working and if I click on a call sign, the QSO box will populate with that call sign. The call sign history window and the worked B4 are both working so it seems there is communication between the programs. The updated version of JT-Alert will log to Log4OM. Everything else seems to be working. Anyone have a suggestion to populate the call sign fields?


locked Re: Blocage JTAlert

f8nhf
 

Thanks Mike for your help.

73's Denis F8NHF


locked Re: Blocage JTAlert

Michael Black
 

You can turn it off unless you're trying to record a problem.




On Thursday, July 25, 2019, 11:13:54 AM CDT, f8nhf <f8nhf@...> wrote:


support contacted
should I leave the recorder running?
Denis F8NHF


locked Re: Blocage JTAlert

f8nhf
 

support contacted
should I leave the recorder running?
Denis F8NHF


locked Re: JTAlert not Keeping up

Ham Radio
 

Consider leaving callsign clearing for FT4 at 15 seconds.  Seems to work fine as is.  

Maybe highlighting  latest FT4 decodes in bold font?

Great program!

--
73, Bernie, VE3FWF


locked Re: Blocage JTAlert

Michael Black
 


JTAlert automatically sends the needed files.



On Thursday, July 25, 2019, 10:54:26 AM CDT, f8nhf <f8nhf@...> wrote:


Mike

where the recording file is located

thank-you


locked Re: Blocage JTAlert

f8nhf
 

Mike

where the recording file is located

thank-you


locked Re: Blocage JTAlert

f8nhf
 

Thank you, Mike

Okay, I'm doing the manipulation.
I'm with the alternative version

 73' Denis F8NHF


locked Re: Blocage JTAlert

Michael Black
 

You need to turn on debug and submit a bug report.

Settings/Enable Debug Recording -- restart JTAlert and duplicate the problem.
Then Help/Contact Support (or I think it's ? on the non-alternate layout version).

de Mike W9MDB




On Thursday, July 25, 2019, 09:24:55 AM CDT, f8nhf <f8nhf@...> wrote:


Thank you Mike 

I made the time modification ,I put 9  nothing has changed the presence of the blockage all the time

73's Denis F8NHF


locked Re: Blocage JTAlert

f8nhf
 

Thank you Mike 

I made the time modification ,I put 9  nothing has changed the presence of the blockage all the time

73's Denis F8NHF


locked Re: Auto Start not working with WSJT X 2.1

roond59
 

I have uninstalled and reinstalled both programs and still no joy.  I'm using Windows 10 1903 and MS just sent a large update with .NET Framework to my machine. Could that have had an effect on JTAlert?  TIA!

8441 - 8460 of 33231