Date   

locked Re: Which U.S. state is it?

Jim Spears
 

FN41 comprises all of RI plus a sliver of eastern CT and a chunk of MA including Cape Cod.  so 3 states in one grid.  there are probably grids that contain pieces of 4 states but none that have 5.

Jim
N1NK


locked Re: Which U.S. state is it?

Michael Black
 

It's up to each user to report their own state correctly -- you have to set up all your locations in TQSL.

Mike W9MDB




On Monday, January 25, 2021, 09:22:17 AM CST, Brian Kassel K7RE <briank7re@...> wrote:


This is an ongoing issue for me. I do a lot of portable out of state operating. Would there be permanent fix
for the user to change the state field to the stations current location?

After all, the ability to enter into one's configuration the current state from which the station is available on many other, if not all, logging programs.


locked Re: Which U.S. state is it?

Paul F6EXV
 

You can create as many locations as you want on LoTW, but it is just impossible for any state database to follow your movements.
So people would know only once they download from LoTW.
73
Paul F6EXV

Le 25/01/2021 à 16:21, Brian Kassel K7RE a écrit :
This is an ongoing issue for me. I do a lot of portable out of state operating. Would there be permanent fix
for the user to change the state field to the stations current location?

After all, the ability to enter into one's configuration the current state from which the station is available on many other, if not all, logging programs.


Garanti sans virus. www.avast.com


locked Re: Which U.S. state is it?

Brian Kassel K7RE
 

This is an ongoing issue for me. I do a lot of portable out of state operating. Would there be permanent fix
for the user to change the state field to the stations current location?

After all, the ability to enter into one's configuration the current state from which the station is available on many other, if not all, logging programs.


locked Re: Which U.S. state is it?

Michael Black
 

Because your QSO partner did their upload with Nevada.

Doesn't matter what state you put in.

Mike W9MDB 




On Monday, January 25, 2021, 08:46:14 AM CST, <hamradiosouth@...> wrote:


Mike,
Then please explain to me how this QSO became "Nevada" in LOTW. Las Vegas is quite a distance from Oregon.
Charlie
W4EBB


locked Re: Which U.S. state is it?

Craig
 

When you log the QSO in LOTW, make sure the location dropdown that you have previously setup correctly shows the location of your QSO.  This could very well be different than what your QRZ record shows and explain why LOTW logs the QSO differently than what you may think...

C

On Mon, Jan 25, 2021 at 9:46 AM <hamradiosouth@...> wrote:
Mike,
Then please explain to me how this QSO became "Nevada" in LOTW. Las Vegas is quite a distance from Oregon.
Charlie
W4EBB


locked Re: Which U.S. state is it?

hamradiosouth@...
 

Mike,
Then please explain to me how this QSO became "Nevada" in LOTW. Las Vegas is quite a distance from Oregon.
Charlie
W4EBB


locked Re: Which U.S. state is it?

Larry Banks
 

My second QTH is in FN43, Maine.  FN43 is also NH.

73 -- Larry -- W1DYJ

 

From: Paul F6EXV
Sent: Monday, January 25, 2021 8:42
Subject: Re: [HamApps] Which U.S. state is it?
 
And I suppose there are MANY example of grids spreading over 2 states (if not more)

Le 25/01/2021 à 14:40, Michael Black via groups.io a écrit :
JTAlert does not use grids for state....LOTW does not use grids for state.  Doing that we would have cheaters all over the place.
 
From LOTW FAQ -- it's up to each one in the QSO to report their own state correctly.
 

I used the same callsign from several different places within the same DXCC entity, without signing "portable". Must I get separate Callsign Certificates for each place?

No, one Callsign Certificate for the callsign you used within the entity is sufficent. Define a Station Location for each of the places from which you operated, and reference the Callsign Certificate in each of these Station Locations. Appropriately naming each Station Location will make it easier to choose the correct one when you submit a group of QSOs made from one place to LoTW.

Back to "Frequently Asked Questions"

 
Mike W9MDB
 
 
 
On Monday, January 25, 2021, 07:24:20 AM CST, hamradiosouth@... mailto:hamradiosouth@... wrote:
 
 
I had a recent instance of a "which state is it" conflict. I was chasing the last few states on 160M needing Oregon as one of the outstanding states. When Oregon popped up on JTAlert I quickly answered and completed the QSO. Then a couple of days later I saw the call sign come thru on my LOTW app so I logged in LOTW and was surprised to see I got credit for Nevada but not Oregon.

Checking things out I saw that contact had a grid in Nevada. Further checking on QRZ showed he was spending the month of January in Las Vegas so I assume he changed his grid to reflect that and that LOTW credits the state based on grid.

Normally, this would likely not be caught and I only did because of the new state.

I am asking - should JTAlert call the state based on the grid?

I searched the forum thinking this must have come up before but did not find anything.
WSJT-X to JTAlert to LOG4OMV2 to LOTW and others

Charlie
W4EBB


Garanti sans virus. www.avast.com


locked Re: Which U.S. state is it?

Paul F6EXV
 

And I suppose there are MANY example of grids spreading over 2 states (if not more)

Le 25/01/2021 à 14:40, Michael Black via groups.io a écrit :
JTAlert does not use grids for state....LOTW does not use grids for state.  Doing that we would have cheaters all over the place.

From LOTW FAQ -- it's up to each one in the QSO to report their own state correctly.

I used the same callsign from several different places within the same DXCC entity, without signing "portable". Must I get separate Callsign Certificates for each place?

No, one Callsign Certificate for the callsign you used within the entity is sufficent. Define a Station Location for each of the places from which you operated, and reference the Callsign Certificate in each of these Station Locations. Appropriately naming each Station Location will make it easier to choose the correct one when you submit a group of QSOs made from one place to LoTW.

Back to "Frequently Asked Questions"


Mike W9MDB



On Monday, January 25, 2021, 07:24:20 AM CST, hamradiosouth@... <hamradiosouth@...> wrote:


I had a recent instance of a "which state is it" conflict. I was chasing the last few states on 160M needing Oregon as one of the outstanding states. When Oregon popped up on JTAlert I quickly answered and completed the QSO. Then a couple of days later I saw the call sign come thru on my LOTW app so I logged in LOTW and was surprised to see I got credit for Nevada but not Oregon.

Checking things out I saw that contact had a grid in Nevada. Further checking on QRZ showed he was spending the month of January in Las Vegas so I assume he changed his grid to reflect that and that LOTW credits the state based on grid.

Normally, this would likely not be caught and I only did because of the new state.

I am asking - should JTAlert call the state based on the grid?

I searched the forum thinking this must have come up before but did not find anything.
WSJT-X to JTAlert to LOG4OMV2 to LOTW and others

Charlie
W4EBB


Garanti sans virus. www.avast.com


locked Re: Which U.S. state is it?

Michael Black
 

JTAlert does not use grids for state....LOTW does not use grids for state.  Doing that we would have cheaters all over the place.

From LOTW FAQ -- it's up to each one in the QSO to report their own state correctly.

I used the same callsign from several different places within the same DXCC entity, without signing "portable". Must I get separate Callsign Certificates for each place?

No, one Callsign Certificate for the callsign you used within the entity is sufficent. Define a Station Location for each of the places from which you operated, and reference the Callsign Certificate in each of these Station Locations. Appropriately naming each Station Location will make it easier to choose the correct one when you submit a group of QSOs made from one place to LoTW.

Back to "Frequently Asked Questions"


Mike W9MDB



On Monday, January 25, 2021, 07:24:20 AM CST, hamradiosouth@... <hamradiosouth@...> wrote:


I had a recent instance of a "which state is it" conflict. I was chasing the last few states on 160M needing Oregon as one of the outstanding states. When Oregon popped up on JTAlert I quickly answered and completed the QSO. Then a couple of days later I saw the call sign come thru on my LOTW app so I logged in LOTW and was surprised to see I got credit for Nevada but not Oregon.

Checking things out I saw that contact had a grid in Nevada. Further checking on QRZ showed he was spending the month of January in Las Vegas so I assume he changed his grid to reflect that and that LOTW credits the state based on grid.

Normally, this would likely not be caught and I only did because of the new state.

I am asking - should JTAlert call the state based on the grid?

I searched the forum thinking this must have come up before but did not find anything.
WSJT-X to JTAlert to LOG4OMV2 to LOTW and others

Charlie
W4EBB


locked Which U.S. state is it?

hamradiosouth@...
 

I had a recent instance of a "which state is it" conflict. I was chasing the last few states on 160M needing Oregon as one of the outstanding states. When Oregon popped up on JTAlert I quickly answered and completed the QSO. Then a couple of days later I saw the call sign come thru on my LOTW app so I logged in LOTW and was surprised to see I got credit for Nevada but not Oregon.

Checking things out I saw that contact had a grid in Nevada. Further checking on QRZ showed he was spending the month of January in Las Vegas so I assume he changed his grid to reflect that and that LOTW credits the state based on grid.

Normally, this would likely not be caught and I only did because of the new state.

I am asking - should JTAlert call the state based on the grid?

I searched the forum thinking this must have come up before but did not find anything.
WSJT-X to JTAlert to LOG4OMV2 to LOTW and others

Charlie
W4EBB


locked Re: Membership List

 

OK Michael that did it thanks.
73/tnx
--
DAVE NU4N


locked Re: Membership List

Michael Black
 

Try the Import capability

Inline image





On Sunday, January 24, 2021, 06:42:07 AM CST, Dave Tucker Nu4N <dwtucker19@...> wrote:


hamclubs.info/
What I am trying to do is put the members callsigns of the 30MDG. I work a lot of 30 FT8 and would like the wanted call sign to alert me of a member>
--
DAVE NU4N


locked Re: Membership List

 

hamclubs.info/
What I am trying to do is put the members callsigns of the 30MDG. I work a lot of 30 FT8 and would like the wanted call sign to alert me of a member>
--
DAVE NU4N


locked Re: Membership List

Michael Black
 

And what weblink would that be?

hams.info website is an empty domain.

Mike W9MDB


On Sunday, January 24, 2021, 05:35:34 AM CST, Dave Tucker Nu4N <dwtucker19@...> wrote:


Comes from the hams.info website.
Thanks for the reply Willie.
--
DAVE NU4N


locked Re: Membership List

 

Comes from the hams.info website.
Thanks for the reply Willie.
--
DAVE NU4N


locked Re: Membership List

AB8WD-Willie
 

Need more info what list and what type of file you say csv but not sure where the file is coming from?


locked Membership List

 

How can I load a csv file into JT ALERT?
Is it a csv file or a text file from the Ham Club membership lists ??

--
DAVE NU4N


locked Re: False Alert

Jim Denneny
 

Thanks Mike.  That fixed it - Jim K7EG


locked Re: False Alert

Michael Black
 

Perhaps Settings/Rebuild Alert Database ??

Mike W9MDB



On Friday, January 22, 2021, 10:57:18 AM CST, Jim Denneny <57jndenneny@...> wrote:


Every morning decode of YU7ZZ on 30M FT8, shows up as needed.  I have Serbia confirmed in DXKeeper and LOTW. My only alert setup is DXCC.  What am I missing?

Jim K7EG

4021 - 4040 of 36897