Date   

locked Callsigns RR73/73 Decodes

Barry
 

Is it possible to include all RR73 or 73 not just the ones with your call in them say in panel No-2 ? eg window (Panel) No-2 RR73/73 decodes.
Or is it possible to add more selections, like  All RR73, All 73 and ALL RR73/73.

VK2AHE  Barry.


locked Re: contest reflection

George KF7NN
 

i didnt realize there was a worked before date that i can configure without rebuilding database, too bad it dont have time also. but that works for me.
thanks


locked Re: contest reflection

George KF7NN
 

jtalert B4 database and my dxkeeper log


locked Re: JTALERT message window

dpar65@...
 

THANK YOU!!
73 ve7fxp


locked Edit B4 list

ON4AVJ@...
 

Hey,
How can I delete a call in the B4 list?
73
Jacques ON4AVJ


locked Re: JTAlert Not updating QRZ Logbook

HamApps Support (VK3AMA)
 

On 21/09/2021 2:17 pm, Wes Wingo N4KMG wrote:

I am unable to see the QRZ logbook updated automatically via JTAlert. I have entered the QRZ API Key and checked the Enable Box. Any help would be much appreciated. 73 de N4KMG

For QRZ Log uploads to be accepted you need a valid QRZ XML subscription. This is not a JTAlert requirement, but a QRZ requirement.

Do you have an XML subscription?

de Laurie VK3AMA


locked JTAlert Not updating QRZ Logbook

Wes Wingo N4KMG <wes.wingo@...>
 

Good Morning,

I am unable to see the QRZ logbook updated automatically via JTAlert. I have entered the QRZ API Key and checked the Enable Box. Any help would be much appreciated. 73 de N4KMG


locked Re: contest reflection

HamApps Support (VK3AMA)
 

On 21/09/2021 10:05 am, KF7NN wrote:
wondering if you can make the database time dependent for contests. 
Ie having a "since" button or something similiar in order to only look at qsos since a certain date /time .

right now i have to create a new database in my log and then have jtalert scan it for every contest,
the worst part is i have to import the contest log into my main log afterward and then rescan it.

maybe you have something already set up? as i really only want one log

OM,

What Log type are you using with JTAlert?

You have a three options depending on how you want to approach the contest.
  1. If your contest participation is to work as many stations and multipliers as possible without any regard to you're current JTAlert needs. Start the contest with a new empty log then do a one-off Alert database rebuild which will take a second or two since the log is empty. At the end of the contest if you want to put the contest QSOs in your normal JTAlert log do an import of the contest QSOs. How you do that depends on the log type you're using, followed by an Alert database rebuild operation after switching back to your normal JTAlert log.

  2. If you're in the contest to pick up new ones as well as hand out numbers, set the JTAlert Worked B4 date to the date of the start of the contest. This will ensure that past QSOs before the contest will not be flagged as B4s and you will still be alerted to new ones you need. QSOs logged during the contest will be flagged as B4s. After the contest turn off the Worked B4 date. There is no need for an Alert database rebuild.

  3. If you're in the contest only to pickup new ones without any desire to work as many stations and multipliers as possible, you don't need to make any changes in JTAlert and treat the contest as just another day working the bands.

1. & 2. are essentially the same, except 1. leaves you with a dedicated contest log that you can use for submission and saving.

de Laurie VK3AMA


locked Re: JTALERT message window

HamApps Support (VK3AMA)
 

On 21/09/2021 11:00 am, dpar65@... wrote:
Anyone know how to save messages to be copy/pasted into the jtalert message window?

Right-click an existing message and click the "Save message text for reuse" menu entry. This will place that message into the drop-down control below the Message entry area.

If you don't have an existing message to save, simply send a message to yourself then use the right-click context menu as described above.

de Laurie VK3AMA


locked JTALERT message window

dpar65@...
 

Anyone know how to save messages to be copy/pasted into the jtalert message window?


locked Re: contest reflection

Dave Garber
 

curious, what database, what log in jtalert???

Dave Garber
VE3WEJ / VE3IE


On Mon, Sep 20, 2021 at 8:05 PM KF7NN <george@...> wrote:
wondering if you can make the database time dependent for contests. 
Ie having a "since" button or something similiar in order to only look at qsos since a certain date /time .

right now i have to create a new database in my log and then have jtalert scan it for every contest,
the worst part is i have to import the contest log into my main log afterward and then rescan it.

maybe you have something already set up? as i really only want one log


locked contest reflection

George KF7NN
 

wondering if you can make the database time dependent for contests. 
Ie having a "since" button or something similiar in order to only look at qsos since a certain date /time .

right now i have to create a new database in my log and then have jtalert scan it for every contest,
the worst part is i have to import the contest log into my main log afterward and then rescan it.

maybe you have something already set up? as i really only want one log


locked Re: B4 Behavior

HamApps Support (VK3AMA)
 

On 19/09/2021 10:58 pm, KD7YZ Bob wrote:
Laurie, I was just having this problem. Am using 2.50.6.
Tried setting the "Ignore" to 1900 as you suggested. Saved ..then unchecked "Ignore" then Saved.
 Then I restarted JTAlert and all is OK.
B4 stations now do not appear in "Callsigns#1" as they did before.
thanks tip

Tnx Bob.
Do you recall what the Date was set to before you made the change?

de Laurie VK3AMA


locked Re: B4 Behavior

KD7YZ Bob
 

Laurie, I was just having this problem. Am using 2.50.6.
Tried setting the "Ignore" to 1900 as you suggested. Saved ..then unchecked "Ignore" then Saved.
Then I restarted JTAlert and all is OK.
B4 stations now do not appear in "Callsigns#1" as they did before.
thanks tip


locked Re: Double click decode does not enable TX in WSJX

HamApps Support (VK3AMA)
 

On 18/09/2021 1:37 am, Brian T Schmidt via groups.io wrote:
THX Gary. It is clicked and double click works on WSJTX but not in the JT Alert decodes window. i just did a fresh install of Windows and all my Ham software yesterday and still no double click in Decode window to TX>

VR
NI0P

If you have done a fresh install of your Ham software, it is very likely that WSJTX is still using some or all of the default UDP Server settings. You need to enable the "Accept UDP requests" option in WSJTX otherwise it will ignore all commands from JTAlert, the Callsigns/decode coloring and the Callsign clicks events. This is covered in the JTAlert Help. Use the "Help -> WSJTX UDP Setup" menu to open the help to the relevant section containing very simple 4 step with pictures instructions.

de Laurie VK3AMA


locked Re: B4 Behavior

Laurie, VK3AMA
 

On 17/09/2021 11:41 pm, WB5JJJ - George wrote:
JTAlert is apparently behaving as it should, based on the bad information it gets from WSJTx, even though I think JTAlert should have recognized the entry as a B4 itself.
To be clear, WSJTX does not send bad or good information to JTAlert, it simply sends what was decoded. The extra information about a decoded callsign, like B4 and Wanted status, is determined by WSJTX or JTAlert after examining the decoded callsigns.

You cannot rely on the differences in what JTAlert and WSJTX are reporting as an indication of a problem. The reported status of a Callsign by JTAlert and WSJTX is coming from 2 different log files. WSJTX uses its internal adif file and JTAlert uses the log file of the LOgger you have enabled in JTAlert. Unless you keep both logs in sync, there will be instances of different reporting.

de Laurie VK3AMA


locked Re: B4 Behavior

Laurie, VK3AMA
 

On 18/09/2021 10:57 am, WB5JJJ - George wrote:
To rescan the adif, goto Files >> Settings >> Colors and on the right about 2/3 down is a button to do this.
--
73's
George - WB5JJJ
In addition to Joe's (W4TV) excellent reply here https://HamApps.groups.io/g/Support/message/37188
I will point out that the re-scanning of the WSJTX ADIF will have zero affect on the JTAlert B4. JTAlert does not interrogate the WSJTX adif file, it never has.

de Laurie VK3AMA


locked Re: B4 Behavior

Dave Garber
 

found it , thanks

Dave Garber
VE3WEJ / VE3IE


On Fri, Sep 17, 2021 at 8:57 PM WB5JJJ - George <wb5jjj@...> wrote:
To rescan the adif, goto Files >> Settings >> Colors and on the right about 2/3 down is a button to do this.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: B4 Behavior

WB5JJJ - George
 

To rescan the adif, goto Files >> Settings >> Colors and on the right about 2/3 down is a button to do this.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: B4 Behavior

Joe Subich, W4TV
 

On 2021-09-17 7:10 PM, Dave Garber wrote:
how do you rescan a log in wsjtx
WSJTX rereads the log every time it starts.

On Fri, Sep 17, 2021 at 9:42 AM WB5JJJ - George <wb5jjj@gmail.com
<mailto:wb5jjj@gmail.com>> wrote:
So I'm at a loss as to why WSJTx is sending it on as a wanted
contact.
JTAlert does not use the B4 information from WSJTX. When you use an
external log, JTAlert compares the "received" data to previously
logged data - Callsign, Grid, Band and mode (and date - if you have
have selected "Ignore QSOs B4"). JTAlert reads the log and caches a
copy in memory every time it starts.

If you are not closing JTAlert and your logging program after every
operating session, you risk damage to the cached image of your log
data through sleep/hibernate/shutdown that could cause inaccurate
QSO B4 behavior.

73,

... Joe, W4TV


On 2021-09-17 7:10 PM, Dave Garber wrote:
how do you rescan a log in wsjtx
Dave Garber
VE3WEJ / VE3IE
On Fri, Sep 17, 2021 at 9:42 AM WB5JJJ - George <wb5jjj@gmail.com <mailto:wb5jjj@gmail.com>> wrote:
I have seen this also in recent days/weeks.  I also noticed that
WSJTx does NOT honor a B4 status on some stations, thus triggering
the wanted status on to JTAlert.  Nothing special about the call or
any other information at all.
To test, I disconnected my log (HRD) from JTAlert and logged a fake
QSO in WSJTx for the actual B4 station that I'm currently seeing,
and then forced WSJTx to rescan its adif log.  That seemed to fix
the problem.  In comparing the previous adif log entry for that
non-B4 station and the new fake one, they appear to be identical in
Notepad++.  The next time this happens, I'm going to copy the fake
QSO in place of the original one, delete the fake one and then force
WSJTx to do a rescan.   Will be interesting to see what happens.
So I'm at a loss as to why WSJTx is sending it on as a wanted
contact.  (Reported to the developers group)  JTAlert is apparently
behaving as it should, based on the bad information it gets from
WSJTx, even though I think JTAlert should have recognized the entry
as a B4 itself.
--
73's
George - WB5JJJ
Hamshack Holine #4969

1521 - 1540 of 38444