Date   

locked DEFECT - Logging using JT65-Comfort 4.0.0 by DL4OCE

Laurie, VK3AMA <groups05@...>
 

I can confirm a defect with JTAlert failing to detect newly logged QSOs from JT65-Comfort 4.0.0 by DL4OCE

This Comfort version is still regarded as Alpha quality by the author (not yet Beta).

At this time, I suggest that an alternate version of JT65HF be used for your JT65A operations as it is unclear when this defect will be resolved.

de Laurie VK3AMA


locked Re: [Ham-Apps] Start JTAlert from NULL

Laurie, VK3AMA <groups05@...>
 

Hi Sandro,

JT65A contacts logged while running JTAlert will not be synchronised with the JT65A contacts logged while running JTAlert-X with WSJT-X.

You should choose only one JTAlert operating mode for you JT65A QSOs. Either JTAlert for JT65-HF or JTAlert-X for WSJT-X

Running JTAlert produces completely separate configuration and session files from running JTAlert-X so there will be 2 different directory structures. Similar if yuu are using different Callsigns. The JTAlert configuration and associated files are invisible to JTAlert-X, as are the JTAlert-X files invisible to JTAlert.
C:\Users\Sandro\AppData\Local\Ham-Apps\JTAlert\IW3RAB\logs
C:\Users\Sandro\AppData\Local\Ham-Apps\JTAlert-X\IW3RAB\logs

de Laurie VK3AMA

On 31/07/2013 6:54 AM, iw3rab wrote:
Hello all,

In this mounth  I try some experiments on my PC Windows 7.
I uninstall all JT65  software and install Windows WSJT-X software.

I have also update JTAler-X to 2.4.1

This operations put me in several troubles.
The function B4 of JTAlert not work. (CALLSIGN - B4 not reported)

/*****
I use from many years this very nice program with a worked / not worked base
The setup use ADIF + B4
ADIF lines are imported in other programs without problems
****/

In the game I have seen that C:\Users\Sandro\AppData\Local\Ham-Apps\JTAlert-X\IW3RAB\logs\B4log.mdb is near empty, with only 2 entries.
I write the missed records (callsign + (band + mode)) but no results.

OK, I write also an ADIF with requested fiels and put in  C:\Users\Sandro\AppData\Local\Ham-Apps\JTAlert-X\IW3RAB\logs\log.adi

Now "callSign - B4" work.
"Scan Log and Update" work.
OK the problem is near resolved.

Now I have 2 directories that contains database:
C:\Users\Sandro\AppData\Local\Ham-Apps\JTAlert\IW3RAB\logs
C:\Users\Sandro\AppData\Local\Ham-Apps\JTAlert-X\IW3RAB\logs

each contain:

adiflog.sqlite // data from log.adi
B4log.mdb // only callsign + band/mode 
log.adi // the default file when I add a QSO

The data are not sincronized, so if I start to use other JT65 program I have to syncronize data. No problem.

Today I update to version 2.4.4 and B4 continue to work with WSJT-X v1.1.r3496 by K1JT

Tomorrow I will try to install some JT65-Comfort series on a XP pc starting with last version of JT-Alert.

As I can import my old ADIF in correct mode ?
This problem is also with a new installation of JT-Alert with ADIF from other log programs.

Can someone help me tidy up my brain?

73 de Sandro IW3RAB






------------------------------------

Yahoo!7 Groups Links

<*> To visit your group on the web, go to:
    http://au.groups.yahoo.com/group/Ham-Apps/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://au.groups.yahoo.com/group/Ham-Apps/join
    (Yahoo! ID required)

<*> To change settings via email:
    Ham-Apps-digest@... 
    Ham-Apps-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    Ham-Apps-unsubscribe@...

<*> Your use of Yahoo!7 Groups is subject to:
    http://au.docs.yahoo.com/info/terms/




locked Re: [Ham-Apps] New - JTAlert 2.4.4 available - JT65-Comfort Support

Laurie, VK3AMA <groups05@...>
 

Hi John,

At this time, it is unlikely that I will extend JTAlert to support
JT65-HB9HQX.
Persistent errors with JT65-HB9HQX while trying to log a simple test QSO have prevented me from completing the most basic of the tests I need.

Sorry.
de Laurie VK3AMA

On 31/07/2013 2:46 AM, John Cranfield wrote:
Hi Laurie
 
Many thanks indeed for the upgrade. Nice to see that you have included the two DL comfort version in JT Alerts. Would you please consider including Beat’s excellent JT65-HB9HQX Edition into JT Alerts??? I think Beat has done an excellent job on this software. You can find the software on Sourceforge website.
 
Vy 73 de John ZD7JC
St. Helena Island
 


locked Start JTAlert from NULL

Alessandro Gorobey
 

Hello all,

In this mounth I try some experiments on my PC Windows 7.
I uninstall all JT65 software and install Windows WSJT-X software.

I have also update JTAler-X to 2.4.1

This operations put me in several troubles.
The function B4 of JTAlert not work. (CALLSIGN - B4 not reported)

/*****
I use from many years this very nice program with a worked / not worked base
The setup use ADIF + B4
ADIF lines are imported in other programs without problems
****/

In the game I have seen that C:&#92;Users&#92;Sandro&#92;AppData&#92;Local&#92;Ham-Apps&#92;JTAlert-X&#92;IW3RAB&#92;logs&#92;B4log.mdb is near empty, with only 2 entries.
I write the missed records (callsign + (band + mode)) but no results.

OK, I write also an ADIF with requested fiels and put in C:&#92;Users&#92;Sandro&#92;AppData&#92;Local&#92;Ham-Apps&#92;JTAlert-X&#92;IW3RAB&#92;logs&#92;log.adi

Now "callSign - B4" work.
"Scan Log and Update" work.
OK the problem is near resolved.

Now I have 2 directories that contains database:
C:&#92;Users&#92;Sandro&#92;AppData&#92;Local&#92;Ham-Apps&#92;JTAlert&#92;IW3RAB&#92;logs
C:&#92;Users&#92;Sandro&#92;AppData&#92;Local&#92;Ham-Apps&#92;JTAlert-X&#92;IW3RAB&#92;logs

each contain:

adiflog.sqlite // data from log.adi
B4log.mdb // only callsign + band/mode
log.adi // the default file when I add a QSO

The data are not sincronized, so if I start to use other JT65 program I have to syncronize data. No problem.

Today I update to version 2.4.4 and B4 continue to work with WSJT-X v1.1.r3496 by K1JT

Tomorrow I will try to install some JT65-Comfort series on a XP pc starting with last version of JT-Alert.

As I can import my old ADIF in correct mode ?
This problem is also with a new installation of JT-Alert with ADIF from other log programs.

Can someone help me tidy up my brain?

73 de Sandro IW3RAB


locked Re: [Ham-Apps] Logging to DXKeeper

AI9T
 

I had not entered the band in JT65-HF when the logging Pop-up came up.

Human Error!!

Just started using your App. It is nice program.

Thanks for your work!!!

73

Steve
On 7/30/2013 4:46 PM, Laurie, VK3AMA wrote:
 

Steve,

What was the problem?

I checked my code. JTAlert doesn't send Band data as part of the DXKeeper logging command, only Frequencies are sent, leaving it to DXKeeper to record the Band.

de Laurie VK3AMA

On 31/07/2013 6:27 AM, Steve AI9T wrote:
I figured out my problem. Operator error!!

sorry for the bandwidth

73
Steve AI9T
On 7/30/2013 3:14 PM, dj9bk wrote:
 

Hello

I am using JT-Alert 2.4.1 to log my JT65-HF QSO's to DXKeeper 11.2.9. The QSO is logging OK but it is leaving the Band Blank. Am I missing something in the setup?

Thanks & 73
Steve AI9T




-- 
73

Steve AI9T

http://www.ai9t.com

AI9T DX Cluster

Version 4 AI9T   Telnet: dxc.ai9t.com port 7300
Version 6 AI9T-2 Telnet: dxc.ai9t.com port 7373 (CW + Skimmer)


locked Re: [Ham-Apps] Logging to DXKeeper

Laurie, VK3AMA <groups05@...>
 

Steve,

What was the problem?

I checked my code. JTAlert doesn't send Band data as part of the DXKeeper logging command, only Frequencies are sent, leaving it to DXKeeper to record the Band.

de Laurie VK3AMA

On 31/07/2013 6:27 AM, Steve AI9T wrote:
I figured out my problem. Operator error!!

sorry for the bandwidth

73
Steve AI9T
On 7/30/2013 3:14 PM, dj9bk wrote:
 

Hello

I am using JT-Alert 2.4.1 to log my JT65-HF QSO's to DXKeeper 11.2.9. The QSO is logging OK but it is leaving the Band Blank. Am I missing something in the setup?

Thanks & 73
Steve AI9T




locked Re: [Ham-Apps] Logging to DXKeeper

AI9T
 

I figured out my problem. Operator error!!

sorry for the bandwidth

73
Steve AI9T
On 7/30/2013 3:14 PM, dj9bk wrote:
 

Hello

I am using JT-Alert 2.4.1 to log my JT65-HF QSO's to DXKeeper 11.2.9. The QSO is logging OK but it is leaving the Band Blank. Am I missing something in the setup?

Thanks & 73
Steve AI9T


-- 
73

Steve AI9T

http://www.ai9t.com

AI9T DX Cluster

Version 4 AI9T   Telnet: dxc.ai9t.com port 7300
Version 6 AI9T-2 Telnet: dxc.ai9t.com port 7373 (CW + Skimmer)


locked Logging to DXKeeper

AI9T
 

Hello

I am using JT-Alert 2.4.1 to log my JT65-HF QSO's to DXKeeper 11.2.9. The QSO is logging OK but it is leaving the Band Blank. Am I missing something in the setup?

Thanks & 73
Steve AI9T


locked Re: [Ham-Apps] Re: New - JTAlert 2.4.4 available - JT65-Comfort Support

John Cranfield <zd7jc@...>
 

Hi OM
You can find the download sites for the two DL comfort versions of JT65-HF at the very bottom of the JT Alerts website.
 
Hope this helps.
 
Vy 73 de John ZD7JC
St. Helena Island
 

From: wa4mit
Sent: Tuesday, July 30, 2013 1:11 PM
Subject: [Ham-Apps] Re: New - JTAlert 2.4.4 available - JT65-Comfort Support
 
 


Where is the Comfort 4.0 download. Link?

It is not showing up on the site I have used in the past for Comfort downloads.

73 WA4MIT


locked Re: [Ham-Apps] New - JTAlert 2.4.4 available - JT65-Comfort Support

John Cranfield <zd7jc@...>
 

Hi Laurie
 
Many thanks indeed for the upgrade. Nice to see that you have included the two DL comfort version in JT Alerts. Would you please consider including Beat’s excellent JT65-HB9HQX Edition into JT Alerts??? I think Beat has done an excellent job on this software. You can find the software on Sourceforge website.
 
Vy 73 de John ZD7JC
St. Helena Island
 

Sent: Tuesday, July 30, 2013 6:31 AM
Subject: [Ham-Apps] New - JTAlert 2.4.4 available - JT65-Comfort Support
 
 

JTAlert 2.4.4 is available for download.

From the Release Notes...

  New Features:
    - Works with JT65-Comfort 4.0.0 by DL4OCE (Alpha release).
    - Works with JT65-Comfort 3.6 by DL3VCO. NOTE: JTAlert logging only supports
       Comfort internal log types adif and MixW only.
    - German Language File.

  Changes:
    - JT65-HF JT65A decodes now spotted using the true DF offset from the QRG
       rather than DF zero = 1250Hz as traditionally reported by JT65-HF.

Visit the Ham-Apps.com web page for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.
  • virusscan.jotti.org : 100% pass against 22 engines. Results
  • virustotal.com : 100% pass against 43 engines. Results
de Laurie VK3AMA




locked Re: New - JTAlert 2.4.4 available - JT65-Comfort Support

Morris WA4MIT
 

Where is the Comfort 4.0 download. Link?

It is not showing up on the site I have used in the past for Comfort downloads.

73 WA4MIT


locked Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

Ed Wilson
 

Laurie,

Actually, I am not sure whether they are showing-up or not (I will check later this morning). I thought that you had said that this was one of the fixes in 2.4.3, so I assumed that any JT65 contacts that I had previously made with WSJT-X and JTAlert-X 2.4.1 would not show-up as worked B4. If this is not correct, then it is a non-issue.

JT65 contacts made since the upgrade are definitely showing as worked B4...I remember that from yesterday.

I just log the contacts via WSJT-X.
 
Ed, K0KC


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Monday, July 29, 2013 9:50 PM
Subject: Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

 
Hi Ed,

If previously worked JT65 stations under wsjt-x are not showing as B4 then something is wrong and I will need to look at your config file.
Are you using logging or just relying on the internal B4Log.mdb file?

Please use the "Settings -> Contact Support" menu to send me your Configuration and Session files for analysis.

de Laurie VK3AMA


On 29/07/2013 9:15 PM, Ed Wilson wrote:
Actually, Laurie, I was wondering about any JT65 stations that I may have worked with WSJT-X not showing-up as worked B4.
 
Ed, K0KC





locked New - JTAlert 2.4.4 available - JT65-Comfort Support

Laurie, VK3AMA <groups05@...>
 

JTAlert 2.4.4 is available for download.

From the Release Notes...
  New Features:
    - Works with JT65-Comfort 4.0.0 by DL4OCE (Alpha release).
    - Works with JT65-Comfort 3.6 by DL3VCO. NOTE: JTAlert logging only supports
       Comfort internal log types adif and MixW only.
    - German Language File.

  Changes:
    - JT65-HF JT65A decodes now spotted using the true DF offset from the QRG
       rather than DF zero = 1250Hz as traditionally reported by JT65-HF.

Visit the Ham-Apps.com web page for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.
  • virusscan.jotti.org : 100% pass against 22 engines. Results
  • virustotal.com : 100% pass against 43 engines. Results
de Laurie VK3AMA




locked Re: [Ham-Apps] jt9 mode bug? when logging to DXKeeper

Sam Morgan
 

You were correct, my DXKeeper version was 1120
after updating it's now version 1129

I had been starting the DXLabs pgms individually instead of with the Launcher so I wasn't getting the update notices <--op error agn (sigh)

and I had edited the C:&#92;DXLab&#92;DXKeeper&#92;Databases&#92;DefaultModes.txt file
saving it as C:&#92;DXLab&#92;DXKeeper&#92;Databases&#92;Modes.txt

as suggested months back using the info found here:
http://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Defining or Eliminating Modes

I think my problem was, I had added these lines:

JT9-1, DXCC_DIGI, WAZ_Digital, WPX_Digital
JT9-2, DXCC_DIGI, WAZ_Digital, WPX_Digital
JT9-5, DXCC_DIGI, WAZ_Digital, WPX_Digital
JT9-10, DXCC_DIGI, WAZ_Digital, WPX_Digital
JT9-30, DXCC_DIGI, WAZ_Digital, WPX_Digital


but just now I edited it again and added this line:

JT9, DXCC_DIGI, WAZ_Digital, WPX_Digital

now DXKeeper has both as choices in the QSO Mode drop down window

once again thanks for your help and great software!

On 7/29/2013 8:55 PM, Laurie, VK3AMA wrote:
Sam,

How old is your DXKeeper version?

I seem to recall that there is a file that can be edited to extend the list of
mode names.
Three of my DXKeeper installs all show JT9 and JT9-1 as being available in the
mode dropdown.
Two of those installs are just using defaults (for testing purposes) and I
didn't have to edit any files.
Perhaps a DXK upgrade will be the quickest solution.

de Laurie VK3AMA


On 29/07/2013 10:55 PM, Sam Morgan wrote:
When I hit Log QSO in WSJTX (r3496)
JTAlert (2.4.3) logs the QSO to DXKeeper just fine
*except*
the blank field where you enter the mode is blank

If I look at the DXKeeper Log listings of contacts
it shows as JT9
not as JT9-1

but up in the QSO field where I can edit the log entry
it still shows the MODE field as empty

I don't know if this is due to something in JTAlert
or if I messed something up in my DXKeeper?
--

GB & 73
K5OAI
Sam Morgan


locked Re: [Ham-Apps] jt9 mode bug? when logging to DXKeeper

Joe Subich, W4TV
 

Either add the following lines to DXKeeper&#92;Databases&#92;Modes.txt

JT9, DXCC_RTTY, WAZ_Digital, WPX_Digital
JT9-1, DXCC_RTTY, WAZ_Digital, WPX_Digital
JT9-2, DXCC_RTTY, WAZ_Digital, WPX_Digital
JT9-5, DXCC_RTTY, WAZ_Digital, WPX_Digital
JT9-10, DXCC_RTTY, WAZ_Digital, WPX_Digital
JT9-30, DXCC_RTTY, WAZ_Digital, WPX_Digital

or configure JTAlert-X to log only the mode (JT9) and not sub-mode
(JT9-1).

73,

... Joe, W4TV

On 7/29/2013 9:55 PM, Laurie, VK3AMA wrote:


Sam,

How old is your DXKeeper version?

I seem to recall that there is a file that can be edited to extend the list of
mode names.
Three of my DXKeeper installs all show JT9 and JT9-1 as being available in the
mode dropdown.
Two of those installs are just using defaults (for testing purposes) and I
didn't have to edit any files.
Perhaps a DXK upgrade will be the quickest solution.

de Laurie VK3AMA


On 29/07/2013 10:55 PM, Sam Morgan wrote:
When I hit Log QSO in WSJTX (r3496)
JTAlert (2.4.3) logs the QSO to DXKeeper just fine
*except*
the blank field where you enter the mode is blank

If I look at the DXKeeper Log listings of contacts
it shows as JT9
not as JT9-1

but up in the QSO field where I can edit the log entry
it still shows the MODE field as empty

I don't know if this is due to something in JTAlert
or if I messed something up in my DXKeeper?



locked Re: [Ham-Apps] jt9 mode bug? when logging to DXKeeper

Laurie, VK3AMA <groups05@...>
 

Sam,

How old is your DXKeeper version?

I seem to recall that there is a file that can be edited to extend the list of mode names.
Three of my DXKeeper installs  all show JT9 and JT9-1 as being available in the mode dropdown.
Two of those installs are just using defaults (for testing purposes) and I didn't have to edit any files.
Perhaps a DXK upgrade will be the quickest solution.

de Laurie VK3AMA


On 29/07/2013 10:55 PM, Sam Morgan wrote:
When I hit Log QSO in WSJTX (r3496)
JTAlert (2.4.3) logs the QSO to DXKeeper just fine
*except*
the blank field where you enter the mode is blank

If I look at the DXKeeper Log listings of contacts
it shows as JT9
not as JT9-1

but up in the QSO field where I can edit the log entry
it still shows the MODE field as empty

I don't know if this is due to something in JTAlert
or if I messed something up in my DXKeeper?



locked Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

Laurie, VK3AMA <groups05@...>
 

Hi Ed,

If previously worked JT65 stations under wsjt-x are not showing as B4 then something is wrong and I will need to look at your config file.
Are you using logging or just relying on the internal B4Log.mdb file?

Please use the "Settings -> Contact Support" menu to send me your Configuration and Session files for analysis.

de Laurie VK3AMA


On 29/07/2013 9:15 PM, Ed Wilson wrote:
Actually, Laurie, I was wondering about any JT65 stations that I may have worked with WSJT-X not showing-up as worked B4.
 
Ed, K0KC



locked jt9 mode bug? when logging to DXKeeper

Sam Morgan
 

When I hit Log QSO in WSJTX (r3496)
JTAlert (2.4.3) logs the QSO to DXKeeper just fine
*except*
the blank field where you enter the mode is blank

If I look at the DXKeeper Log listings of contacts
it shows as JT9
not as JT9-1

but up in the QSO field where I can edit the log entry
it still shows the MODE field as empty

I don't know if this is due to something in JTAlert
or if I messed something up in my DXKeeper?

--

GB & 73
K5OAI
Sam Morgan


locked Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

Ed Wilson
 

Actually, Laurie, I was wondering about any JT65 stations that I may have worked with WSJT-X not showing-up as worked B4.
 
Ed, K0KC


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Monday, July 29, 2013 6:36 AM
Subject: Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

 
Hi Ed,

No need for the log scan, unless you want to update your Wanted Lists.
Existing wanted lists are maintained during the 2.4.3 upgrade.

With 2.4.0, there was a fundamental change in how the lists were internally maintained and named that was not compatible with versions pre 2.4.0 so pre 2.4.0 lists couldn't be upgraded. Thus the special requirement to do a Log Scan or manual update.

I need to update the Ham-Apps site to better explain this.

de Laurie VK3AMA

On 29/07/2013 7:18 PM, Ed Wilson wrote:
Laurie,

With this new version, do we have to do a log scan to pick-up the JT65 calls that were not recorded (as worked B4) under WSJT-X?

If so, is it normal that I lose all of my wanted state information after a log scan and need to re-enter it manually; this was the case for the last upgrade that required a log scan.
 
Ed, K0KC


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Monday, July 29, 2013 4:01 AM
Subject: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

 
JTAlert 2.4.3 is available for download.

This release fixes the defect introduced in 2.4.2 where JTMacros when set to auto-start would always start in
"wsjtx" mode resulting in missing macros and non-docking when started for JT65-HF

Visit the Ham-Apps.com web page for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.

virusscan.jotti.org :
100% pass against 22 engines. Results

virustotal.com : 100% pass against 46 engines. Results

de Laurie VK3AMA





locked Re: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

Laurie, VK3AMA <groups05@...>
 

Hi Ed,

No need for the log scan, unless you want to update your Wanted Lists.
Existing wanted lists are maintained during the 2.4.3 upgrade.

With 2.4.0, there was a fundamental change in how the lists were internally maintained and named that was not compatible with versions pre 2.4.0 so pre 2.4.0 lists couldn't be upgraded. Thus the special requirement to do a Log Scan or manual update.

I need to update the Ham-Apps site to better explain this.

de Laurie VK3AMA

On 29/07/2013 7:18 PM, Ed Wilson wrote:
Laurie,

With this new version, do we have to do a log scan to pick-up the JT65 calls that were not recorded (as worked B4) under WSJT-X?

If so, is it normal that I lose all of my wanted state information after a log scan and need to re-enter it manually; this was the case for the last upgrade that required a log scan.
 
Ed, K0KC


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Monday, July 29, 2013 4:01 AM
Subject: [Ham-Apps] New - JTAlert 2.4.3 available - Fixes JTMacros auto-start

 
JTAlert 2.4.3 is available for download.

This release fixes the defect introduced in 2.4.2 where JTMacros when set to auto-start would always start in
"wsjtx" mode resulting in missing macros and non-docking when started for JT65-HF

Visit the Ham-Apps.com web page for the direct download link.

This release has been run through two online scanners. Results can be viewed using the links below.

virusscan.jotti.org :
100% pass against 22 engines. Results

virustotal.com : 100% pass against 46 engines. Results

de Laurie VK3AMA