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?

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?

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?

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

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

Some interesting new features and a couple of good fixes, thanks.

 

But something went wrong here, during the upgrade. JT-macros 2.4.2 seems to have lost my favorite (custom) macros, and is no longer docked to JT65-HF.

 

And even though "enable RB" and "enable PSKR" boxes are checked, nothing seems to get reported at all. Both counters are still at "0", after an hour or so.

 

What did I mess up?

73,

 

Erik - K5WW

 

----- Original Message -----

From: Laurie, VK3AMA

To: Ham-Apps@...

Sent: Sunday, July 28, 2013 6:46 PM

Subject: [Ham-Apps] New - JTAlert 2.4.2 available - Fixes and changes

 

A new version, 2.4.2 of JTAlert is available.

If you encounter any problems post a message to the Ham-Apps Yahoo group using a subject line related to the issue.
Please DON'T just reply to this email. It doesn't help users doing message archive searches of specific issues.

From the Release Notes...

  New Features:
    - Option to instruct DXKeeper to upload a new QSO to eQSL.
       (Default: OFF, Window: Settings, Section: Logging->DXLab DXKeeper).

  Changes:
    - JTAlert-X will exit if unable to determine WSJT-X installation directory.
    - Minimum autostart delay for WSJT-X is now 2000ms. This is the amount of
       time JTAlert-X will pause while waiting for WSJT-X to finish starting.
    - Create Station shortcut extended to automatically create both JT65-HF and
       WSJT-X shortcuts regardless of current JTAlert operating mode.
    - ADIF log sqlite cache file is now automatically deleted and recreated at
       startup, rather than only adding newer QSOs since last time log used.
    - Text Message (via HotKey) auto-filled with current QSO partner Callsign.

  Fixes:
    - Not detecting Standard ADIF file was same as WSJT-X default adi log file.
    - Create Station desktop shortcut not adding /wsjtx parameter of WSJT-X mode.
    - B4Log.mdb file ADIF import not importing JT65 QSOs for dual-mode WSJT-X.
    - LotW and eQSL flgs not showing on 2nd row of Callsign display slots.

Visit the Ham-Apps.com webpage 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

----- Original Message -----

From: Laurie, VK3AMA

To: Ham-Apps@...

Sent: Sunday, July 28, 2013 6:46 PM

Subject: [Ham-Apps] New - JTAlert 2.4.2 available - Fixes and changes

 

A new version, 2.4.2 of JTAlert is available.

If you encounter any problems post a message to the Ham-Apps Yahoo group using a subject line related to the issue.
Please DON'T just reply to this email. It doesn't help users doing message archive searches of specific issues.

From the Release Notes...

  New Features:
    - Option to instruct DXKeeper to upload a new QSO to eQSL.
       (Default: OFF, Window: Settings, Section: Logging->DXLab DXKeeper).

  Changes:
    - JTAlert-X will exit if unable to determine WSJT-X installation directory.
    - Minimum autostart delay for WSJT-X is now 2000ms. This is the amount of
       time JTAlert-X will pause while waiting for WSJT-X to finish starting.
    - Create Station shortcut extended to automatically create both JT65-HF and
       WSJT-X shortcuts regardless of current JTAlert operating mode.
    - ADIF log sqlite cache file is now automatically deleted and recreated at
       startup, rather than only adding newer QSOs since last time log used.
    - Text Message (via HotKey) auto-filled with current QSO partner Callsign.

  Fixes:
    - Not detecting Standard ADIF file was same as WSJT-X default adi log file.
    - Create Station desktop shortcut not adding /wsjtx parameter of WSJT-X mode.
    - B4Log.mdb file ADIF import not importing JT65 QSOs for dual-mode WSJT-X.
    - LotW and eQSL flgs not showing on 2nd row of Callsign display slots.

Visit the Ham-Apps.com webpage 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

 

A new version, 2.4.2 of JTAlert is available.

If you encounter any problems post a message to the Ham-Apps Yahoo group using a subject line related to the issue.
Please DON'T just reply to this email. It doesn't help users doing message archive searches of specific issues.

From the Release Notes...

  New Features:
    - Option to instruct DXKeeper to upload a new QSO to eQSL.
       (Default: OFF, Window: Settings, Section: Logging->DXLab DXKeeper).

  Changes:
    - JTAlert-X will exit if unable to determine WSJT-X installation directory.
    - Minimum autostart delay for WSJT-X is now 2000ms. This is the amount of
       time JTAlert-X will pause while waiting for WSJT-X to finish starting.
    - Create Station shortcut extended to automatically create both JT65-HF and
       WSJT-X shortcuts regardless of current JTAlert operating mode.
    - ADIF log sqlite cache file is now automatically deleted and recreated at
       startup, rather than only adding newer QSOs since last time log used.
    - Text Message (via HotKey) auto-filled with current QSO partner Callsign.

  Fixes:
    - Not detecting Standard ADIF file was same as WSJT-X default adi log file.
    - Create Station desktop shortcut not adding /wsjtx parameter of WSJT-X mode.
    - B4Log.mdb file ADIF import not importing JT65 QSOs for dual-mode WSJT-X.
    - LotW and eQSL flgs not showing on 2nd row of Callsign display slots.

Visit the Ham-Apps.com webpage 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

---

From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Sunday, July 28, 2013 3:36 PM
Subject: Re: [Ham-Apps] Audio Alert on Text Message?

 

Hi Don,

No, there is no audio alert for text messages. Text messages accidentally got released while it was still a "proof of concept" I was testing and some features, like audio alert and reply button, were not completed or available at that time.

It is on the todo list.

de Laurie VK3AMA

On 28/07/2013 2:26 PM, Don AA5AU wrote:

I did not see where there is an alert for receiving a text message. Is there an audible alert for that?

Thanks,

Don AA5AU

Speaking of "wish" lists, would it be difficult to include a "Reply" button on the text message window?

Ed, K0KC

---

From: Sam Morgan
To: Ham-Apps@...
Sent: Saturday, July 27, 2013 7:11 AM
Subject: [Ham-Apps] JTAlert Txt MSG request(s)

 

Low priority, but .......
Would it be possible to add a 'toggle' to log text messages sent?
Date, Time, Station sent to, Message content.

if it's a case of to much already happening at the end (50-60 sec mark)
perhaps right after the band map is populated and b4 the decodes come in?
or any time during the cycle for that matter
just so there is a log of what was sent.

also sometimes I fear what was sent may have been lost, not received,
and want to repeat the message, but don't rem exactly how I worded it,
or things are so busy I don't have time to retype it.

A drop down menu with the last 2-3 previous messages sent
and a resend button would be really nice.

--

GB & 73
K5OAI
Sam Morgan