Date   

locked Re: DXCC

asobel@...
 

Laurie

 

This is good news

 

Please apply this to Wanted Callsign and Ignored Callsign too. It will be  very useful. For example: I want to QSO an unconfirmed  station on all bands but I get it alarmed on already worked bands.

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, November 16, 2020 8:35 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] DXCC

 

On 16/11/2020 4:03 pm, Michael Black via groups.io wrote:

Is there a way to distinguish new DXCC from new DXCC-on-band?

New DXCC would take priority so would be nice to make it unique.

 

Mike W9MDB


NO. This would require additional ATNO alert lists which would have to be updated by addition log queries (the existing sql queries are not suitable). This atno alerting is however already part of the as yet unreleased JTAlertV3. While I am bringing some JTAlertV3 functionality into JTAlertV2, this is unlikely to be one of them.

From the current JTAlertV3 DXCC Alert settings...


Note the ATNO allows for a different color combination from the non-ATNO. Also the "Flash" checkbox allows for an ATNO alerted callsign to flash (alternate) its colors as an attention-grabbing mechanism, distinguishing it from a non-ATNO alert.

de Laurie VK3AMA


locked Re: DXCC

HamApps Support (VK3AMA)
 

On 16/11/2020 4:03 pm, Michael Black via groups.io wrote:
Is there a way to distinguish new DXCC from new DXCC-on-band?
New DXCC would take priority so would be nice to make it unique.

Mike W9MDB

NO. This would require additional ATNO alert lists which would have to be updated by addition log queries (the existing sql queries are not suitable). This atno alerting is however already part of the as yet unreleased JTAlertV3. While I am bringing some JTAlertV3 functionality into JTAlertV2, this is unlikely to be one of them.

From the current JTAlertV3 DXCC Alert settings...


Note the ATNO allows for a different color combination from the non-ATNO. Also the "Flash" checkbox allows for an ATNO alerted callsign to flash (alternate) its colors as an attention-grabbing mechanism, distinguishing it from a non-ATNO alert.

de Laurie VK3AMA


locked Re: States-Wanted Boxes Auto-Untick?

HamApps Support (VK3AMA)
 

On 16/11/2020 11:29 am, Patrick Hung wrote:
I just began working on my WAS award, and so have ticked the numerous boxes for states that I still need on the States Wanted page of JTAlert.

I had thought that once I complete a QSO with a station from a wanted state, JTAlert would automatically "untick" that box for me, or turn off that specific alert for that particular band, so that stations from the same state won't get highlighted again. To my disappointment, it doesn't do that; I've had to remember the states I just completed, and manually turn off the alert. Is this how it's supposed to work?

Thanks.
--
Patrick - W2TAR

JTAlert, by default, does not automatically remove an alerted entity, like a State, by simply working a Station. For most users, they require some sort of QSL confirmation before they are happy that an  entity is no-longer needed and no-longer alerted. You set the QSL requirements in the Rebuild Alert Database section of the Settings window. Alert types have independent confirmation settings, so you could have Dxcc & State set to require LoTW confirmations while Grid & Prefix alerts set to only require a worked status (no qsl needed).

If your truly want to have a State automatically removed from your Alerts list by simply working a Station, there is no need to run the Rebuild Database operation. You can just set the "Auto clear triggered Alert entity after logging" under settings for the Alert. This is available for all Alert types.

   


de Laurie VK3AMA



locked Re: States-Wanted Boxes Auto-Untick?

Patrick Hung
 

Thanks Dave and Mike - by "confirming", you mean confirming via LOTW? If that's the case, I see how someone could take a while (or never) uploading logs.

Dave mentioned Confirmation in the JTAlert Settings pull-down menu - can you clarify where, exactly?

I'll take a look at LOTWQSL - thanks.

--
Patrick - W2TAR


locked DXCC

Michael Black
 

Is there a way to distinguish new DXCC from new DXCC-on-band?
New DXCC would take priority so would be nice to make it unique.

Mike W9MDB



locked Re: States-Wanted Boxes Auto-Untick?

Michael Black
 

As somebody already said the state (or country) has to be confirmed to not alert.  And some operators are slow about uploading their logs.

If you're working WAS you might have some fun with my LOTWQSL program that you'll find on my QRZ page.  It's easy to see the LOTW updates and if you need to update your log and JTAlert and it shows maps and a grid view of your status.  It also tracks DXCC and DXCC Mixed numbers.

Mike W9MDB




On Sunday, November 15, 2020, 06:30:03 PM CST, Patrick Hung <pathung@...> wrote:


I just began working on my WAS award, and so have ticked the numerous boxes for states that I still need on the States Wanted page of JTAlert.

I had thought that once I complete a QSO with a station from a wanted state, JTAlert would automatically "untick" that box for me, or turn off that specific alert for that particular band, so that stations from the same state won't get highlighted again. To my disappointment, it doesn't do that; I've had to remember the states I just completed, and manually turn off the alert. Is this how it's supposed to work?

Thanks.
--
Patrick - W2TAR


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Roger,


I finally worked him just now on 10.131 but I was NOT in f/h mode, although he is in f/h mode, unless he switched on the fly, go figure??

Called him at 1500 and he did not call me to his freq but we exchanged reports and got a RR73 from him..


73,

W9RF - Joe








On Sunday, November 15, 2020, 6:52:45 PM CST, Roger M via groups.io <ac6bw@...> wrote:


Joe,
OK, fair enough. Yes, it does seem strange.
All I can suggest is keep trying. Are you using WSJT-X, or JTDX? I recently switched over to JTDX, because it has better decode sensitivity, as well as some other features that I like. If you have both programs installed, perhaps you can try one or the other in F/H mode, and see if that makes a difference.
Also, it's possible that something is not configured correctly on the Fox end, but I wouldn't know exactly what. There are a lot of settings that the Fox can enable.
--
73,
Roger
AC6BW


locked Re: States-Wanted Boxes Auto-Untick?

Patrick Hung
 

Mike and Alfred,

Thanks to you both for your input.

I do have JTAlert logging successfully, as a dialog box pops up to let me know of that after each QSO.

I think that Alfred may be right in the need to run a "Rebuild" - I'll test that and report back.
--
Patrick - W2TAR


locked Re: States-Wanted Boxes Auto-Untick?

Dave (NK7Z)
 

The contact needs to confirm, AND, you need to rebuild the database... Only then will it count...Both commands are in the pull down under settings.

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 11/15/20 4:29 PM, Patrick Hung wrote:
I just began working on my WAS award, and so have ticked the numerous boxes for states that I still need on the States Wanted page of JTAlert.
I had thought that once I complete a QSO with a station from a wanted state, JTAlert would automatically "untick" that box for me, or turn off that specific alert for that particular band, so that stations from the same state won't get highlighted again. To my disappointment, it doesn't do that; I've had to remember the states I just completed, and manually turn off the alert. Is this how it's supposed to work?
Thanks.
--
Patrick - W2TAR


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Mike,


working them is not a problem, I have them worked on 15 cw, 20 cw, 40 cw and 20 ssb, it's just FT8 F/H that doesn't work for me.



73,

W9RF - Joe








On Sunday, November 15, 2020, 6:37:04 PM CST, Michael Aust via groups.io <ava622@...> wrote:


Worked them on CW on 40m and 20m
Mike
WB6DJI 


Sent from AOL Mobile Mail
Get the new AOL app: mail.mobile.aol.com

On Sunday, November 15, 2020, ray cathode via groups.io <ray_cathode1@...> wrote:

Roger,


it seems very strange that they would call at the 0-500 slot when I do.
That doesn't explain why other calls are verified.


9 Times total 6 last night and 3 so far today, that's not coincidence

My time is set every 30 minutes with D4, always well withing .2 seconds, besides I don't think they would call me if they couldn't decode me above 1000.


73,

W9RF - Joe







On Sunday, November 15, 2020, 4:00:52 PM CST, Roger M via groups.io <ac6bw@...> wrote:


Joe,
Like Bjorn said, the LIDS who don't know how to operate F/H mode see you working (or attempting to work) the DX in the 0 - 500 Hz slot, after the Fox has pushed you down in frequency. Then, they decide to call him in that same frequency slot, which creates QRM. After 3 tries, the Fox gives up.You say that you got dropped 6 times, so this may be a long shot answer, but it's certainly something to consider. I see these kinds of problems occur in every F/H operation. It can become a big mess.

I assume that your time is set accurately. I was working 7Q7RU today, and his time looked accurate on my end.
--
73,
Roger
AC6BW


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Roger,


I'm using WSJT-X, always have and have never had a problem with F/H mode.

It's not a huge problem, I already have 7Q confirmed on 6 bands, it's just very strange I can't get a confirmation when they have called me down 9 times with very good signal reports.

Was going to try tonight but I see there are no spots other than some say power outage and other say software problems.



73's es tnx fer the help..



W9RF - Joe



On Sunday, November 15, 2020, 6:52:45 PM CST, Roger M via groups.io <ac6bw@...> wrote:


Joe,
OK, fair enough. Yes, it does seem strange.
All I can suggest is keep trying. Are you using WSJT-X, or JTDX? I recently switched over to JTDX, because it has better decode sensitivity, as well as some other features that I like. If you have both programs installed, perhaps you can try one or the other in F/H mode, and see if that makes a difference.
Also, it's possible that something is not configured correctly on the Fox end, but I wouldn't know exactly what. There are a lot of settings that the Fox can enable.
--
73,
Roger
AC6BW


locked Re: unsuccessful contacts with 7q7ru

Roger- AC6BW
 

Joe,
OK, fair enough. Yes, it does seem strange.
All I can suggest is keep trying. Are you using WSJT-X, or JTDX? I recently switched over to JTDX, because it has better decode sensitivity, as well as some other features that I like. If you have both programs installed, perhaps you can try one or the other in F/H mode, and see if that makes a difference.
Also, it's possible that something is not configured correctly on the Fox end, but I wouldn't know exactly what. There are a lot of settings that the Fox can enable.
--
73,
Roger
AC6BW


locked Re: States-Wanted Boxes Auto-Untick?

Alfred Reeves
 

I think you have to run "Rebuild Alert Database" to have the box  "untick"


locked Re: States-Wanted Boxes Auto-Untick?

Mike Rhodes
 

Thinking that doesn't happen until that state is confirmed. You are linked to your log aren't you?

Mike / W8DN

On 11/15/2020 7:29 PM, Patrick Hung wrote:
I just began working on my WAS award, and so have ticked the numerous boxes for states that I still need on the States Wanted page of JTAlert.

I had thought that once I complete a QSO with a station from a wanted state, JTAlert would automatically "untick" that box for me, or turn off that specific alert for that particular band, so that stations from the same state won't get highlighted again. To my disappointment, it doesn't do that; I've had to remember the states I just completed, and manually turn off the alert. Is this how it's supposed to work?

Thanks.
--
Patrick - W2TAR


locked Re: unsuccessful contacts with 7q7ru

Michael Aust
 

Worked them on CW on 40m and 20m
Mike
WB6DJI 


Sent from AOL Mobile Mail
Get the new AOL app: mail.mobile.aol.com

On Sunday, November 15, 2020, ray cathode via groups.io <ray_cathode1@...> wrote:

Roger,


it seems very strange that they would call at the 0-500 slot when I do.
That doesn't explain why other calls are verified.


9 Times total 6 last night and 3 so far today, that's not coincidence

My time is set every 30 minutes with D4, always well withing .2 seconds, besides I don't think they would call me if they couldn't decode me above 1000.


73,

W9RF - Joe







On Sunday, November 15, 2020, 4:00:52 PM CST, Roger M via groups.io <ac6bw@...> wrote:


Joe,
Like Bjorn said, the LIDS who don't know how to operate F/H mode see you working (or attempting to work) the DX in the 0 - 500 Hz slot, after the Fox has pushed you down in frequency. Then, they decide to call him in that same frequency slot, which creates QRM. After 3 tries, the Fox gives up.You say that you got dropped 6 times, so this may be a long shot answer, but it's certainly something to consider. I see these kinds of problems occur in every F/H operation. It can become a big mess.

I assume that your time is set accurately. I was working 7Q7RU today, and his time looked accurate on my end.
--
73,
Roger
AC6BW


locked States-Wanted Boxes Auto-Untick?

Patrick Hung
 

I just began working on my WAS award, and so have ticked the numerous boxes for states that I still need on the States Wanted page of JTAlert.

I had thought that once I complete a QSO with a station from a wanted state, JTAlert would automatically "untick" that box for me, or turn off that specific alert for that particular band, so that stations from the same state won't get highlighted again. To my disappointment, it doesn't do that; I've had to remember the states I just completed, and manually turn off the alert. Is this how it's supposed to work?

Thanks.
--
Patrick - W2TAR


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Roger,


it seems very strange that they would call at the 0-500 slot when I do.
That doesn't explain why other calls are verified.


9 Times total 6 last night and 3 so far today, that's not coincidence

My time is set every 30 minutes with D4, always well withing .2 seconds, besides I don't think they would call me if they couldn't decode me above 1000.


73,

W9RF - Joe







On Sunday, November 15, 2020, 4:00:52 PM CST, Roger M via groups.io <ac6bw@...> wrote:


Joe,
Like Bjorn said, the LIDS who don't know how to operate F/H mode see you working (or attempting to work) the DX in the 0 - 500 Hz slot, after the Fox has pushed you down in frequency. Then, they decide to call him in that same frequency slot, which creates QRM. After 3 tries, the Fox gives up.You say that you got dropped 6 times, so this may be a long shot answer, but it's certainly something to consider. I see these kinds of problems occur in every F/H operation. It can become a big mess.

I assume that your time is set accurately. I was working 7Q7RU today, and his time looked accurate on my end.
--
73,
Roger
AC6BW


locked Erroneous error message !

Paul F6EXV
 

Hi all
Strange behaviour...
Using Log4OM latest version, JTDX v2.2.0-rc152 and JTAlert 2.16.15 on Windows 10.
I am getting the attached error message when logging a QSO onto Log4OM.
But the QSO is indeed logged...

I have :
Enable transmission of last QSO ticked, on port 2333 in the "Last QSO API" setup
Enable Standard ADIF file logging unticked in the Standard ADIF file setup
Enable Log4OM V2 logging tocked, UDP connections on IP 127.0.0.1 on ADIF message port #2236
When I ask JTAlert to show Log Fields, the screen expands, but remains grey.
The headline says "JTAlert 2.16.15 F6EXV {80m,FT8,LogV2,#1}

If I untick "Enable Log4OM Logging", then I do not have access to "View log fields", and the expanded grey screen disappears, and the header will now show "NO LOG".
 And the QSO IS logged onto Log4OM, without any success message....

1/ How can I get access to the log fields below the display lines ?
2/ The "NO LOG" indication makes reference to which log ?
3/ How do I get a logging success message ?

Thanks + 73
Paul F6EXV



--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked Re: unsuccessful contacts with 7q7ru

Roger- AC6BW
 

Joe,
Like Bjorn said, the LIDS who don't know how to operate F/H mode see you working (or attempting to work) the DX in the 0 - 500 Hz slot, after the Fox has pushed you down in frequency. Then, they decide to call him in that same frequency slot, which creates QRM. After 3 tries, the Fox gives up.You say that you got dropped 6 times, so this may be a long shot answer, but it's certainly something to consider. I see these kinds of problems occur in every F/H operation. It can become a big mess.

I assume that your time is set accurately. I was working 7Q7RU today, and his time looked accurate on my end.
--
73,
Roger
AC6BW


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Bjorn,

I fail to see what that has to do with my situation, I always call above 1000 and don't hear anyone from 500-1000 except for the ones they throw up there, and that's only for a couple of passes.

So how does that explain my problem?







On Sunday, November 15, 2020, 3:39:50 PM CST, Björn SM7IUN <bjorn@...> wrote:


Likely since LIDS are repeatedly calling him below 1000Hz. 
The Fox will not respond to them, they just QRM. 

Björn SM7IUN

Den sön 15 nov. 2020 kl 22:05 skrev ray cathode via groups.io <ray_cathode1=yahoo.com@groups.io>:
Good afternoon group.


Since yesterday evening 7q7ru has heard my call and called me down to his frequency (Fox/Hound) 9 times with out a successfully confirmation.

After a few back and forth with the signal report (which has been very good reports) they throw me up to a higher frequency and leave me there and go on calling other calls or calling CQ.

Are they running a different software that is not compatible with JTAlert/WSJT-X?
or is it possible a setting has been changed with my software?

I tested my software by making other contacts (not Fox/Hound) so unless the problem id something with Fox/Hound my software is working..


Thanks for any help..


73,

W9RF - Joe


5721 - 5740 of 37815