|
locked
Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)
JTAlert Support (VK3AMA)
On 24/12/2020 11:16 am, Dick Bingham
wrote:
While more memory is always good, CPU usage is the most critical. What is taskmanager telling you when WSJT-X is busy processing decodes at the end of a period? What CPU usage is it indicating? If your hitting 80% or greater than that is a problem, it will cause WSJT-X (and everything else on your PC) to be slowed. The Underline indicates that that Callsign has the Text Messages function of JTAlert enabled and is set to receive messages. de Laurie VK3AMA
|
|
|
|
locked
Re: Feature Request: QSO Pop-up
JTAlert Support (VK3AMA)
On 25/12/2020 6:58 am, John Maguire
AA6ZT wrote:
Use the F3 hotkey to bring up the "Callsign History Window" which is the same as the popup you refer to. It is a standalone window that can be positioned anywhere. It will auto-track the DXCall in WSJT-X. If you have the hotkeys turned off, the "View -> Callsign History Window" menu does the same. de Laurie VK3AMA
|
|
|
|
locked
Feature Request: QSO Pop-up
The QSO Pop-up is a helpful tool. However, it should include:
|
|
|
|
locked
Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)
neil_zampella
Um ... you'll never see the DX in the cell ... you need to set the 'Directed Call' color in the settings which will notify you of that request by a colored band around the cell. I use a RED color to reflect a 'directed' call.
Neil, KN3ILZ
|
|
|
|
locked
Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)
Robert Lorenzini
I can't respond to you're specific problems but you need to
toggle quoted messageShow quoted text
upgrade to the latest (3.4.9) before posting a problem. There have been fixes since 3.5.7. That may not fix your problem but it puts us all on the same page. Happy holidays to you and the group. Bob - wd6dod
On 12/23/2020 4:16 PM, Dick Bingham
wrote:
|
|
|
|
locked
Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)
Hello again I highly suspect my DELL Laptop E6510 W7 with 4G of RAM is the problem. when the following SW is running: - PowerSDR OpenHPSDR mRX PS v3.4.7 - Voicemeeter Banana - WSJT-X v2.2.2 - DXKeeper 15.7.2 - JTAlert 2.16.17 The available free RAM drops below 350MB according to Win Task Manager. I now only click "OK" in the pop-up logging window after my last transmission has cleared. I have a reasonably fast internet connection and use a router to connect with remote computers. JTAlert DOES present a success or failure message after
the logging has finished. Same for the pop-up window associated with the WSJT-X logger. What is the significance of a call displayed as AA7Aw - AZ VS AA7AW - AZ where one 'cell' is underlined and another is not underlined ? 73 Dick/w7wkr at CN97uj
On Wed, Dec 23, 2020 at 2:15 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
|
|
|
|
locked
Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)
Hello Laurie I guess I did not make myself clear . I am decoding call signs OK but when the CQer is sending "CQ DX VK3AMA QF##" I do not see the "DX" part in the 'cell' with the callsign. The State and VE parts display fine. No change when I expand to 4 X 9 display presentation. Once I'm certain what needs to be seen is there, the main window for WSJT-X can be collapsed and only use the JTAlert display. Great software ! How many development MAN-Years does JTTAlert represent ? 73 Dick/w7wkr at CN97uj
On Wed, Dec 23, 2020 at 2:10 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
|
|
|
|
locked
Re: JTAlert works fine but no colored calls in WSJT
N2TK, Tony
Thanks Laurie for the info. Merry Christmas N2TK, Tony
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Wednesday, December 23, 2020 6:30 PM To: Support@HamApps.groups.io Subject: Re: [HamApps] JTAlert works fine but no colored calls in WSJT
On 24/12/2020 10:15 am, N2TK, Tony via groups.io wrote:
Red icon -> JTAlert for WSJT-X
|
|
|
|
locked
Re: JTAlert works fine but no colored calls in WSJT
JTAlert Support (VK3AMA)
On 24/12/2020 10:15 am, N2TK, Tony via
groups.io wrote:
Red icon -> JTAlert for WSJT-X Blue icon -> JTAlert for JTDX Don't bother trying to get the JTDX decodes colored by JTAlert, it is not supported. The relevant code in the original WSJT-X source was stripped by the JTDX people for some reason. de Laurie VK3AMA
|
|
|
|
locked
Re: JTAlert works fine but no colored calls in WSJT
N2TK, Tony
Never mind. I have to use the red musical note shortcut to see the colored callouts in WSJT. Not sure what the colors mean but it is working fine. N2TK, Tony
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of N2TK, Tony via groups.io
Updated JTAlert. Seems to be working fine. But none of the highlighted calls appear highlighted in WSJT. What did I forget to change?
|
|
|
|
locked
JTAlert works fine but no colored calls in WSJT
N2TK, Tony
Updated JTAlert. Seems to be working fine. But none of the highlighted calls appear highlighted in WSJT. What did I forget to change?
I used the blue musical note shortcut. Do I need to use a different color and/or the "X" instead of the musical symbol? Tnx N2TK, Tony
|
|
|
|
locked
Re: JT Alert & WSJT-X interactions
JTAlert Support (VK3AMA)
On 22/12/2020 4:56 am, Mike Turner
wrote:
If you're not getting B4's than likely the log your using with JTAlert has changed or no longer contains your previous QSOs. What log type are you using, does it still contain all your past QSOs? de Laurie VK3AMA
|
|
|
|
locked
Re: NO JTALERT call sign download/fill-in
JTAlert Support (VK3AMA)
On 21/12/2020 9:57 pm, k6vib@q.com
wrote:
The 2 x 7 areas I use to fill in are ok, but the area for a selected call sign to be worked does not fill in the Name, QTH, or Grid. Seems to have the State and/or Country though. It does fill in if it is a call that I have worked on another band or B4. Do I have a setting wrong? The JTAlert log fields area gets populated with Name & QTH data from any previous QSOs in your log for that station or from an XML lookup. Since this was working previously, the likely cause is that your xml subscription has expired. de Laurie VK3AMA
|
|
|
|
locked
Re: JT Alert not displaying all decodes
JTAlert Support (VK3AMA)
On 18/12/2020 11:45 am, Dave LeDuc
wrote:
Since you don't mention your PC specs, it's a guessing game as to whether your PC is the cause of missing decodes. How many cores, installed RAM, speed? How late is WSJT-X showing all the decodes for a period, that is how far into the new period is WSJT-X still presenting decodes from the last period? Do you have any JTAlert Alert filters enabled? de Laurie VK3AMA
|
|
|
|
locked
Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)
JTAlert Support (VK3AMA)
On 24/12/2020 7:38 am, Dick Bingham
wrote:
That indicates that JTAlert is stuck waiting to verify the QSO was actually written to the DXKeeper log. 10's of seconds is excessive, on a moderate PC I would expect that to be under 5 secs depending on what online activities DXKeeper is performing post logging. How reliable/fast is your internet connection? If you have DXKeeper auto-uploading to LoTW or eQSL and those services are down or slow, than delays in DXKeeper writing the QSO to the log file are normal and JTAlert will hang (as will DXKeeper) while it retries reading the log file to confirm the QSO was written. Does JTAlert present you with a success or failure message after the logging? de Laurie VK3AMA
|
|
|
|
locked
Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)
JTAlert Support (VK3AMA)
On 24/12/2020 7:38 am, Dick Bingham
wrote:
You're missing decoded callsigns because your limiting the JTAlert display. The display can go to 4 lines x 9 callsigns. See the View menu. If 36 callsign slots is not enough, you can try restricting the number displayed by using one or more Alert filters. Alternatively, use the Decodes window which will display all the callsigns in a period. de Laurie VK3AMA
|
|
|
|
locked
Re: JTAlert shortcuts on desktop
JTAlert Support (VK3AMA)
On 24/12/2020 8:54 am, N2TK, Tony via
groups.io wrote:
Just installed the update to 2.16.17. Seems to be working fine. How old was the JTAlert version you upgraded from? From the release notes... 2.16.5 (08-May-2020) de Laurie VK3AMA
|
|
|
|
locked
JTAlert shortcuts on desktop
N2TK, Tony
Just installed the update to 2.16.17. Seems to be working fine.
But what about the different colored shortcuts? Did I miss somewhere what they mean? Musical not and also "X" in blue, red, purple. Used to have a green but no longer since I upgraded. Using the blue musical note right now Tnx and Merry Christmas N2TK, Tony
|
|
|
|
locked
Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)
Greeting ALL - Jim and Neil in particular I will respond "Inside" Jim's text space to ensure nothing is left out... Dick/w7wkr ========================================================== Sounds to me like you JTAlert is not linked to DXKeeper, and you are only seeing the contacts in your WSJT-X log. To check this, in DXKeeper banner, you should see how many contacts you have logged. Mine says DXKeeper 15.8.9 [CC,PF] - AF5FH.mdb: 5571 QSOs. Your number of QSOs will be different, of course. On my DXKeeper Banner , I see 900-plus QSOs indicated AND I only see QSO logged in the DXKeeper ..\..\databases\W7WKR.mdb LOG going back to August, 2020. LotW shows I have over 9000 QSO in their database. In a file at c:\DXLab\DXKeeper\Databases\LotW_QSOs_ADI I see 9074 QSOs logged. Is logging being sent to the wrong file ? THEN after some messing-around (unfortunately I did not paper-record each step for later review) the DXKeeper banner displayed (DXKeeper 15.7.2 - w7wkr.mdb : 9883 QSO) Now JTAlert seems to be working much better indicating many CQ's as being worked previously (B4) Next, in JTAlert, click Settings, Rebuild Alert Database, and then click Rebuild All (enabled). A Log Scan - DXLab DXKeeper window should appear, and it will quickly at the top flash Loading xxxx of 5571 QSOs, followed by a series of Scanning Log: Band - xxx messages. The number of QSOs in the Log Scan windows has to exactly match the number of QSOs that DXKeeper has logged. After performing the above steps many times, I now get a match between JTAlert and DXKeeper numbers. Let us know if the numbers of QSOs match. If they do not, verify that Enable DXLab DXKeeper logging is enabled in Settings, Logging, DXLab DXKeeper. Yes, "Enable DXkeeper ...." IS enabled. An important step/steps was/were correctly stumbled upon and now JTAlert works like it was designed to function ! Some issues: - A decoded directed CQ (like "CQ DX W1AW FN##") is not indicated in a 2X8 JTAlert display Cell forcing me to still examine the WSJT-X screen to minimize interfering with the CQer's real interest - Do not know what the difference is between an UNDERLINED callsign (in a 2X8 cell) and one NOT underlined. Multiple reading-passes thru the SETUP selections has not revealed what is implied - IF I click "OK"in the "Confirm QSO Window" while my "73" is being transmitted, the entire system freezes for tens-of-seconds before recovering - being careful to click "OK" after the transmission is completed solves this problem Thank you ALL who responded to my request for assistance. I can live with what is working now and, with more experience, probably refine some settings. 73 Dick/w7wkr at CN97uj 73, Jim AF5FH
On Wed, Dec 23, 2020 at 7:09 AM Jim AF5FH <jkajder@...> wrote:
|
|
|
|
locked
Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)
Jim AC9ZL
Sounds to me like you JTAlert is not linked to DXKeeper, and you are only seeing the contacts in your WSJT-X log.
To check this, in DXKeeper banner, you should see how many contacts you have logged. Mine says DXKeeper 15.8.9 [CC,PF] - AF5FH.mdb: 5571 QSOs. Your number of QSOs will be different, of course. Next, in JTAlert, click Settings, Rebuild Alert Database, and then click Rebuild All (enabled). A Log Scan - DXLab DXKeeper window should appear, and it will quickly at the top flash Loading xxxx of 5571 QSOs, followed by a series of Scanning Log: Band - xxx messages. The number of QSOs in the Log Scan windows has to exactly match the number of QSOs that DXKeeper has logged. Let us know if the numbers of QSOs match. If they do not, verify that Enable DXLab DXKeeper logging is enabled in Settings, Logging, DXLab DXKeeper. 73, Jim AF5FH
|
|
|