Date   

locked Re: TCP QSO Data transfer Socket Operation: Timed out #JTDX #HRD

Bob Davet
 

Got it fixed.
I mistyped one of the TCP server numbers.

Bob


locked Re: New JTAlert 2.13.0 Enhanced Decodes History. A charm.

Peter Butler
 

I heartily agree 2.13.0 is very helpful!
With FT8, the speed of my human response has increased with the number of clickable choices.

It appears that FT8 contesting has begun. I expect that the program may have to change to respond to even wider bandwidths. I set my bandwidth to 4 KHz, but I predict that the RF would have to change by 4 Khz.

That will likely set off howls of protests, especially with other digital modes and SSB. However fox/hounds have created secondary channels.

Such is life in the fast lane!

Peter
W1UU


On Mar 9, 2019, at 5:15 AM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 9/03/2019 8:55 pm, Mark W2OR via Groups.Io wrote:
2.13 is terrific.  So versatile, searchable, easily modified.  

Thank you very much.
Glad you like it.

I was just reviewing the help file and realised there were a number of useful features that I failed to document. If I get time tomorrow I post a suitable message to the Group about those. In the interim, try a single mouse click on a decode line, it should automatically setup WSJT-X and if the decode is a CQ start transmitting.

de Laurie VK3AMA


locked Re: New JTAlert 2.13.0 Enhanced Decodes History. A charm.

HamApps Support (VK3AMA)
 

On 9/03/2019 8:55 pm, Mark W2OR via Groups.Io wrote:
2.13 is terrific.  So versatile, searchable, easily modified.  

Thank you very much.
Glad you like it.

I was just reviewing the help file and realised there were a number of useful features that I failed to document. If I get time tomorrow I post a suitable message to the Group about those. In the interim, try a single mouse click on a decode line, it should automatically setup WSJT-X and if the decode is a CQ start transmitting.

de Laurie VK3AMA


locked New JTAlert 2.13.0 Enhanced Decodes History. A charm.

Mark W2OR
 

2.13 is terrific.  So versatile, searchable, easily modified.  

Thank you very much.


locked Re: Decodes History V3 - no data showing

HamApps Support (VK3AMA)
 

On 9/03/2019 8:40 pm, Graham Alston wrote:
I knew it would be something simple....never used it until now. All good now thanks.

73
Thanks for the update.
I have been using the New Decodes History for at least 3 months now before it got integrated into the V2 series of JTAlert that some things got missed in documenting and setup.

de Laurie VK3AMA


locked Re: Decodes History V3 - no data showing

Graham Alston
 

I knew it would be something simple....never used it until now. All good now thanks.

73


locked Re: Decodes History V3 - no data showing

HamApps Support (VK3AMA)
 

On 9/03/2019 6:40 pm, Graham Alston wrote:
Hi Laurie,

I must be missing something, I get no data in the decodes history window. What I am I missing?

73 Graham VK3GA
Graham,

Did you use the Decodes History in previous versions? If not, then you will need to enable its use. Open the Settings Window to the "Window -> Decodes History" section and tick the check box, top left corner. After enabling restart JTAlert.

If you still get no decodes, use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis.

de Laurie VK3AMA



locked Decodes History V3 - no data showing

Graham Alston
 

Hi Laurie,

I must be missing something, I get no data in the decodes history window. What I am I missing?

73 Graham VK3GA

BTW The new callsign colouring in WSJT-X is fantastic!

WSJT-X v2.0.1
JTAlert 2.13.0
Windows 7 Pro SP1


locked Re: Version 2.13.0, cannot scan log after upgrade

Dany VE2EBK
 

Hi Laurie

I reinstalled the new version 2.13.0 and all is OK for me.

Thanks for your great job

73 de Dany VE2EBK


locked Re: Version 2.13.0, cannot scan log after upgrade

HamApps Support (VK3AMA)
 

On 9/03/2019 12:37 pm, Dany VE2EBK wrote:
Same problem here with WSJT-X. The path is correct.

I reinstalled version 2.12.10 and I'm back in business for the week-end.

Dany VE2EBK
Dany,

I have identified & corrected the issue and confirmed in Testing the ADIF import is now working.
Please download 2.13.0 again

de Laurie VK3AMA


locked Re: Version 2.13.0, cannot scan log after upgrade

HamApps Support (VK3AMA)
 

On 9/03/2019 12:38 pm, Dragan Djordjevic 4O4A wrote:
Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis.

OK, in the meantime I reverted back to 2.12.10, and it works OK.

I will install new version again and send files for analysis.

Thanks,
Dragan, 4O4A

Dragan,

I have identified & corrected the issue and confirmed in Testing the ADIF import is now working.
Please download 2.13.0 again

de Laurie VK3AMA


locked Re: Version 2.13.0, cannot scan log after upgrade

Dragan Djordjevic 4O4A
 

On Sat, Mar 9, 2019 at 02:28 AM, HamApps Support (VK3AMA) wrote:
Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis.

OK, in the meantime I reverted back to 2.12.10, and it works OK.

I will install new version again and send files for analysis.

Thanks,
Dragan, 4O4A


locked Re: Version 2.13.0, cannot scan log after upgrade

Dany VE2EBK
 

Same problem here with WSJT-X. The path is correct.

I reinstalled version 2.12.10 and I'm back in business for the week-end.

Dany VE2EBK


locked Re: Version 2.13.0, cannot scan log after upgrade

HamApps Support (VK3AMA)
 

On 9/03/2019 12:22 pm, Dragan Djordjevic 4O4A wrote:
Path is correct, the same for last 3-4 versions, the file is same (about 8k QSOs).
ADIF is located within C:/Logger32 directory. The same happens if I relocate ADIF (and restart) file on dekstop.
After upgrade it doesn't work neither with JTDX nor with WSJT-X.
OS is Windows 7 32-bit, SP1. I didn't notice any problem during work with 2.12.0 version.

Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: Version 2.13.0, cannot scan log after upgrade

Dragan Djordjevic 4O4A
 

On Sat, Mar 9, 2019 at 02:10 AM, HamApps Support (VK3AMA) wrote:
Check that the path to your ADIF file is set correctly and that the file contains data. A very brief appearance of the ADIF importing messages suggests that ADIF file doesn't contain any entries (or very few).

Path is correct, the same for last 3-4 versions, the file is same (about 8k QSOs).
ADIF is located within C:/Logger32 directory. The same happens if I relocate ADIF (and restart) file on dekstop.
After upgrade it doesn't work neither with JTDX nor with WSJT-X.
OS is Windows 7 32-bit, SP1. I didn't notice any problem during work with 2.12.0 version.


locked Re: Version 2.13.0, cannot scan log after upgrade

HamApps Support (VK3AMA)
 

On 9/03/2019 11:56 am, Dragan Djordjevic 4O4A wrote:

I upgraded to 2.13.0 from 2.12.0 and now I cannot scan & rebuild database.
I'm using standard adif file for logging.
During the start of 2.13.0, popup window with message about importing log appears just briefly, but there is no progress bar activity like it was before, in version 2.12.0.
Restart, clean installation didn't help.

Regards,
Dragan, 4O4A

Check that the path to your ADIF file is set correctly and that the file contains data. A very brief appearance of the ADIF importing messages suggests that ADIF file doesn't contain any entries (or very few).

There were no changes to ADIF log file handling or Scanning.

de Laurie VK3AMA


locked Version 2.13.0, cannot scan log after upgrade

Dragan Djordjevic 4O4A
 

Hi,

I upgraded to 2.13.0 from 2.12.0 and now I cannot scan & rebuild database.
I'm using standard adif file for logging.
During the start of 2.13.0, popup window with message about importing log appears just briefly, but there is no progress bar activity like it was before, in version 2.12.0.
Restart, clean installation didn't help.

Regards,
Dragan, 4O4A


locked New JTAlert 2.13.0 available. Enhanced Decodes History. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

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

This release has a new Decodes History interface, part of the under-development JTAlertV3. The new Decodes History database is significantly different and is not compatible with the old version database. It will start with an empty database, there is no option for migrating old data across to the new version.

The usage and features of the new Decodes History are documented in a standalone help file, not part of the main JTAlert help file, use the "Help" menu of the DH window.

Settings for the new Decodes History are also contained in a standalone window, not part of the main JTAlert Settings window, use the "File -> Settings" menu of the DH window.

The Release Notes...
  New Features:
    - New Decodes History (part of the under development JTAlertV3).
    - Callsign highlighting within the WSJT-X Band Activity panel. Callsigns are
      coloured, matching the alert color for the Callsign in the main JTAlert window.
       (Default: ON, Window: Settings, Section: Applications, WSJT-X).
    - N3FJP Contest Logs no longer require the mode override being set.
       JTAlert now shows the correct Callsign/DXCC/State Bands worked status for
       the current WSJT-X DXCall.
    - Option to enable logging of WSJT-X sent and received Contest exchanges.
       (Default: OFF, Window: Settings, Section: Logging. "Log WSJT-X Contest
        Exchanges" checkbox under Logging Options).
       (Note: DXKeeper does log these Contest exchanges, but does not use them
        when creating its Cabrillo file. It is recommnded that DXKeeper is not
        used for Contest logging via JTAlert. HRD and Log4OM have not been
        tested to see if they exhibit the same behaviuour as DXKeeper)

  Changes:
    - WSJT-X sent and received Contest exchanges (SRX_STRING & STX_STRING)
       are no longer automatically logged to DXKeeper, HRD V5/V6 or Log4OM.
       ACLog, ADIF & N3FJP Contest Logs are not affected by this.
       See the New Features above for a description of the applicable setting.
    - N3FJP RTTY Roundup Contest Log enabled status in JTAlert title text
      changed from "RCL" to "RRCL".
    - Last QSO ADIF UDP transmission can now be disabled.

  Fixes:
    - WSJT-X 2.0.0 Special Operation Mode status incorrectly shown in JTAlert
       titlebar text when running against JTDX.
    - Setup not showing install path selection page if JTAlert already installed.
    - QSL flags/stripes not painted for some callsigns. This was typically seen
       on busy bands when JTAlert was set for multiple callsign display lines
       with less than 9 callsigns per line.
    - Marathon Scan Log randomly not identifying previosuly worked WAE Countries
       like IT9 Sicily.
    - Blocked Spotting popup message showing incorrect non-https web link.

de Laurie VK3AMA


locked Unable to download the source of wsjt-x

Jean-Claude F1DSZ
 

Hello
 

Unable to download the source of wsjt-x
 
I use"" Git Bash"".

Could you guide me through the process.
 

   Thank you very much.   
 
   Jean-Claude F1DSZ


locked Re: TCP QSO Data transfer Socket Operation: Timed out #JTDX #HRD

HamApps Support (VK3AMA)
 

On 8/03/2019 2:12 am, Bob Davet wrote:
Just set up JTDX and JTAlertX.
Everything seems to be working as it should. The only issue I am having is the above error when I go to log the contact.
I hit OK and it goes away. The contact gets logged.

I'm using the most current version of JTDX and JTAlertX. I an logging into HRD (most current version)

I'm sure that I have just missed a check box. But which one??

Thanks

Bob
W8RID

Which application is generating the error message, JTAlert, JTDX or HRD?

Post a screen-capture of the error message (the message window only, not your entire desktop).

de Laurie VK3AMA

13421 - 13440 of 36910