Date   

locked Re: Decodes window

Michael Black
 

Click the title bar
Press F2
Uncheck the "Size Locked".

You should now be able to resize the window.

Mike W9MDB




On Thursday, September 9, 2021, 05:09:40 PM CDT, richard clare <crrr@...> wrote:


Laurie, the gear icon is in the bottom right of the decodes window. But my decodes window is reduced


locked Re: Decodes window

richard clare
 

Laurie, the gear icon is in the bottom right of the decodes window. But my decodes window is reduced


locked Re: Decodes window

richard clare
 

Only the 2. Alerts Only window of Callsigns #2 is open. Cannot expand to show All Decodes and #1 Callers box to show. Richard wb6ewm


locked Re: Decodes window

HamApps Support (VK3AMA)
 

On 10/09/2021 7:32 am, richard clare wrote:
It is on the screen in the middle of the left panel of wsjtx. The expand window is not highlighted and so I can't expand it top full size or return it to under the JTAlerts window. The gear in the lower right is not shown to make changes to the JTAlerts window.

Sorry, I am not following what your describing. There is no gear icon in the bottom left of the Decodes window. That window pre-dates the 2.50.x introduced windows which all have the gear icon in the lower-left corner of the window.

The WSJTX window is independent of the JTAlert Decodes window. It is not clear to me what you're experiencing. Please post an image showing what your describing.

de Laurie VK3AMA


locked Re: Worked B4 conflicting (some callsigns)

HamApps Support (VK3AMA)
 

On 6/09/2021 11:40 pm, nd2k@... wrote:

I have noticed with a small handful of calls, the Confirmed/Worked Bands Display
will correctly show a callsign worked (e.g. the 20M FT4 worked box is checked)
but the same callsign in the Callsigns Window does not show "B4"; nor is it
"grayed out" in the WSJT Band Activity column (indicating worked B4).

Again, this is only a small handful of callsigns, with not rhyme or reason to them
having anything in common. I rebuilt the database, but still no change.

Any ideas??

Al ND2K

Sounds like you have an ignore B4 date set causing old log entries to not be considered as B4s.

See the "Alerts -> Worked B4" section of the Settings window and turn off the "Ignore QSOs based on log entry date" option.

de Laurie VK3AMA


locked Re: Decodes window

Michael Black
 

Hover over the icon in the task bar.  You should see all windows appear.  Right-click the window and select Maximize.

Mike  W9MDB




On Thursday, September 9, 2021, 04:32:16 PM CDT, richard clare <crrr@...> wrote:


It is on the screen in the middle of the left panel of wsjtx. The expand window is not highlighted and so I can't expand it top full size or return it to under the JTAlerts window. The gear in the lower right is not shown to make changes to the JTAlerts window.


locked Re: Rebuild Alert Data Base

HamApps Support (VK3AMA)
 

On 9/09/2021 9:25 pm, Jim Cary wrote:
How do I change/eliminate the QTH Id Selections?  I tried to eliminate or change it on the "My QTH Lists per wanted alert" but it won't accept changes.

Just click the "X" button to clear any selected myQTH ids. To enable specific ids for an Alert, simply click the id so that it becomes highlighted. A second click to remove the selection highlight.

de Laurie VK3AMA


locked Re: Decodes window

richard clare
 

It is on the screen in the middle of the left panel of wsjtx. The expand window is not highlighted and so I can't expand it top full size or return it to under the JTAlerts window. The gear in the lower right is not shown to make changes to the JTAlerts window.


locked Re: "Sticky" Alert

HamApps Support (VK3AMA)
 

On 9/09/2021 9:52 am, Gavin Bennett wrote:

With a triggered alert, such as a new DXCC/band is there a setting that does not clear the alert, until you can manually clear it?  

The alert may be triggered, but if I don't get to the computer quick enough I may miss it.

Thanks

Gavin
ZL3GAV

See this message posted a couple of days ago where I discuss persisting Callsigns...
https://hamapps.groups.io/g/Support/message/37068

de Laurie VK3AMA


locked Re: V2.505 and worked B4

HamApps Support (VK3AMA)
 

On 8/09/2021 3:50 pm, Jacques F1VEV wrote:
Hello  Hi Bob V31MA is also one of my recuring callsigns despite having worked all bands etc  yet my issue concerns at least 50% of ALL calls that are Worked B4  show up as wanted  so something is amiss in my system . 

 did a quick roll back to 2.50.4 this morning  and all seems ok  for now  still testing   WEIRD 

Thanks Jacques F1VEV

Rolling back JTAlert to 2.50.4 changed the B4 Alerting behavior, it does not have the extended B4 Date ignore options introduced in 2.50.5. From the 2.50.5 release notes...
    - Worked B4 Alert: Ignoreing the B4 status based on the age of QSOs in the Log.
       Selectable in Monthly increments, 1, 2, 3, 6, 9, 12, 24 and 36 Months. The age
       is determinined by the utc Date when the current JTAlert session is started.
       See the Alerts -> Worked B4 section of the main JTAlert window Settings.

Your previous messages indicated that you had the 6 month age option selected which would cause ALL QSOs in your log older than 6 months to not be used for B4 checks and subsequent Alerting. That is why you are seeing Callsigns worked over 6 months ago not being shown as B4s.

See my message here... https://hamapps.groups.io/g/Support/message/37105

de Laurie VK3AMA


locked Re: V2.505 and worked B4

HamApps Support (VK3AMA)
 

On 7/09/2021 6:28 pm, Jacques F1VEV wrote:
 This is what I tried last as I would have thought it was the most restrictive  but some still show  despite last QSO was over 18 months ago  Cheers  Jacques 
--
F1VEV

Based on your settings, an 18 month old QSO in your log will not be flagged as B4 because you have the "6 months" age setting enabled for the "Ignore QSOs based on log entry date". By setting an ignore date as you have, any callsign decoded that was previously logged more than 6 months in the past will not show the B4 in the Callsigns window and will generate alerts.

If you don't want old QSO being ignored for the B4 testing, don't use the "Ignore QSOs based on log entry date", un-tick the checkbox.

de Laurie VK3AMA


locked Re: Decodes window

HamApps Support (VK3AMA)
 

On 10/09/2021 6:52 am, richard clare wrote:
Help! Decodes window minimized. Can't get it to maximize! Richard wb6ewm

Google "Recover off screen window" and use one of the many millions of hits returned for recovering an off-screen window, a very common Windows problem.

de Laurie VK3AMA


locked Decodes window

richard clare
 

Help! Decodes window minimized. Can't get it to maximize! Richard wb6ewm


locked Re: Rebuild Alert Data Base

Jim Cary
 

How do I change/eliminate the QTH Id Selections?  I tried to eliminate or change it on the "My QTH Lists per wanted alert" but it won't accept changes.


locked Re: "Sticky" Alert

Michael Black
 

There's a script on my QRZ page that will work with JTAlert's "Miscellaneous Alerts/User Alert" and will email/text to wherever you want.

Mike W9MDB




On Wednesday, September 8, 2021, 06:52:50 PM CDT, Gavin Bennett <gavin@...> wrote:


Firstly, I apologise if the solution is within the forum, I could not find it (-;

With a triggered alert, such as a new DXCC/band is there a setting that does not clear the alert, until you can manually clear it?  

The alert may be triggered, but if I don't get to the computer quick enough I may miss it.

Thanks

Gavin
ZL3GAV


locked Re: No respons from JTDX when I dblclick in the Calsingn Window

HamApps Support (VK3AMA)
 

On 8/09/2021 9:11 pm, ON4AVJ@... wrote:
In JTalert "double click" is activated to send the call sending CQ (or other message) to WSJT+ or JTDX.
But nothing happens in JTDX. Are there other configuration settings needed in JTAlert or JTDX?
73
Jacques ON4AVJ

You need to enable "Accept UDP Requests" for the UDP Server settings in JTDX, just like the WSJTX setup.

de Laurie VK3AMA


locked Re: dual instances issues

HamApps Support (VK3AMA)
 

On 8/09/2021 10:06 pm, KF7NN wrote:
thanks i was changing the wrong port, i changed the 2333 to 2334 but in reality i tried the 2237 to 2238 and it works good now

FYI,

There is no need to use different UDP ports for each WSJTX instance if you use multicast UDP. The port can be the same for each instance, see the JTAlert "Help -> WSJTX UDP Setup" menu. Unique ports are only needed when using unicast UDP. 127.0.0.1 is a unicast address.

de Laurie VK3AMA
 


locked Re: Rebuild Alert Data Base

HamApps Support (VK3AMA)
 

On 9/09/2021 7:34 am, Jim Cary wrote:
I feel real stupid raising this issue.  I've looked through all of the posts and responses on the above subject, and still can't get the alert database tables to update.  I am using DXKeeper and the Log function shows that.  But for some reason, the alert tables are not updating when I do Data Base rebuild.  I have tracking  by any band for any WSJT-X mode.  And the results are the same whether I ask for all tracking to be updated, or only for one band.

It is so simple it should work but........

Thanks,

Jim
W2SM

Sounds like you have one or more DXKeeper myQTH Ids set for the different Alerts which directly affects what QSOs in the DXKeeper Log are used for the rebuild operation. See the "Logging -> DXLab DXKeeper -> my QTH Id Selections" section of the main Settings window.

de Laurie VK3AMA


locked Re: Rebuild Alert Data Base

Michael Black
 

Hi Jim

Give me a call and we can connect up and see about figuring out what's wrong.
I help a lot of people.

217-960-0233

Mike W9MDB






On Wednesday, September 8, 2021, 04:34:06 PM CDT, Jim Cary <jimlcary@...> wrote:


Laurie,

I feel real stupid raising this issue.  I've looked through all of the posts and responses on the above subject, and still can't get the alert database tables to update.  I am using DXKeeper and the Log function shows that.  But for some reason, the alert tables are not updating when I do Data Base rebuild.  I have tracking  by any band for any WSJT-X mode.  And the results are the same whether I ask for all tracking to be updated, or only for one band.

It is so simple it should work but........

Thanks,

Jim
W2SM


locked Rebuild Alert Data Base

Jim Cary
 

Laurie,

I feel real stupid raising this issue.  I've looked through all of the posts and responses on the above subject, and still can't get the alert database tables to update.  I am using DXKeeper and the Log function shows that.  But for some reason, the alert tables are not updating when I do Data Base rebuild.  I have tracking  by any band for any WSJT-X mode.  And the results are the same whether I ask for all tracking to be updated, or only for one band.

It is so simple it should work but........

Thanks,

Jim
W2SM

1701 - 1720 of 38532