Date   

Indonesia

Paul Milward <nu4c@...>
 

I just worked YB8MAN Badrin in Indonesia from Florida. 2035utc
I was so surprised I almost forgot to respond.
Its a big deal for me.
14.070 up about 1.3
Go get him
73
Paul NU4C #824



Re: LoTW

Steve W3HF
 

> As many others I log the start and finish times...

Gary -

The issue isn't whether you log start or finish times (or both). The problem comes when your logging program creates ADIF from a log entry and it's not clear which definition you are using.

Suppose your logging program just has "QSO Time" as a field to fill in. Or it auto-populates the time field when you make an entry. Do you know whether the exported ADIF uses the <time_on> or <time_off> tag when it exports? Unless you pay attention to that, you might have entered the wrong time in the "QSO Time" field.

Or maybe your logger actually DOES call it "QSO Start Time", and you figure it doesn't matter. And it probably doesn't matter if the QSO is short. But it could lead to bad habits that could cause problems with long QSOs.

Steve
W3HF



Re: LoTW

Jerry N9AVY
 

Gary:

Sorry to hear that it seems to be a worldwide problem. At first, I thought I was imagining the lack of knowledge, but when other agree maybe tis true.   Guess it's up to those who know to teach who will listen until  "they"  come out with a pill to bring others up to speed.

Jerry


 

 
     

"The lack of knowledge that is shown on various internet media and on the radio itself is incredible.
The problem isn't just limited to the states."




Re: LoTW

Gary GM7USC
 

As many others I log the start and finish times. Thankfully the LoTW does give you a 30 minute window.
Our Foundation licence (M6xxx calls) standard is aimed at the lowest level. Not all of them but a significant number.
The lack of knowledge that is shown on various internet media and on the radio itself is incredible.
The problem isn't just limited to the states.


Re: LoTW

Jerry N9AVY
 

Dan:

The 30 minute window is correct.

The problem is that some PSK operators use the sign off time as the time of QSO  which is probably incorrect in the eyes of most hams, but then we get into a philosophical discussion which is not worth pursuing.

You should probably run that stations call to see if he has uploaded anything to LoTW. There are some/many who do not use LoTW for whatever reasons. 

In the "old days" when log keeping was an FCC requirement and not debatable,  you entered the times you called
"CQ", "TEST"  and the actual start time of a QSO. That's all ancient history now with the FCC  relaxing rules over the past few decades. 

I doubt that few newer hams have ever read or even comprehend FCC Part 97...  IMHO.  Think it might have something to do with the lack of "Elmering" (mentoring) and the FCC  trying to make their job easier by simplifying rules; along with lack of enforcement. Add to the mess the ARRL's desire for greater numbers in ham population and those "ham cram" test sessions and you get a bunch of newbies who might not even know how to do basics like assemble a station and antenna.

Back to question :   Unless it's a contact you need for an award (WAS/DXCC) just forget about it.  If someone sends you a wrong time, just send them the time you have for QSO  and let them figure it out  ! 

Jerry






From: "Dan Morris dbmorris315@... [070]" <070@...>
To: 070 List Service 070 List Service <070@...>
Sent: Tuesday, April 25, 2017 7:52 AM
Subject: [070] LoTW

 
OK all you LoTW smart ones. I’m a bit confused and cannot find anything in the help file at LoTW about a contact not being confirmed.

I logged a contact and I found that what I logged and what the other station logged is 21 minutes different. Not sure why, although I have noticed that “MOST” stations log their contacts when they finish the QSO. I always thought that we were supposed to log a contact when it begins. Most of the time no problem as a lot of contacts don’t last but a couple of minutes. But some can be rag chews as this one was so our times differed slightly. I think eQSL gives a 30 minute window but not sure what LoTW gives to be able to confirm a contact. Evidently less than 21 minutes though.

Anyone have any comments on this??

Thanks

Dan Morris KZ3T 070-1065
dbmorris315@...




LoTW

Dan Morris - KZ3T
 

Thanks so much for all the replies. I corrected and resubmitted the contact. All should be good now.

Dan Morris KZ3T
dbmorris315@...


Re: LoTW

Steve W3HF
 




---In 070@..., <wa4mit@...> wrote :

>Dan I believe the LOTW window is +/- 15 minutes so that makes a 30 min. total window

Morris -

I can't find it in the ARRL pages, but the DXLab help page says it differently: "the dates and times in each uploaded QSO are within 30 minutes of each other"

Steve
W3HF


Re: LoTW

Steve W3HF
 

Dan -


1. I think the time period is 30 minutes, so I would have thought that a 21-minute difference would have been good enough. Are you sure that everything else in the log entry is the same?


2. You can't actually "correct" a log entry in LoTW. What you can do is upload a new log entry. LoTW does not let you view your uploads directly (though you can download them), and there's no editing possible. If an entry does not match, you can upload an additional entry with changes (or additions) in the QSO information that can either allow a confirmation that previously did not match, or add other info to the confirmation (like grid square or IOTA). But the original entry is still there, and is typically referred to as a zombie.


Steve

W3HF


Re: LoTW

Dan Morris - KZ3T
 

Thanks Morris.

Dan Morris







On Apr 25, 2017, at 9:28 AM, Morris Wideman wa4mit@... [070] <070@...> wrote:


Dan I believe the LOTW window is +/- 15 minutes so that makes a 30 min. total window and you can not correct or change a uploaded QSO you have to change it then upload again. If you use eQSL look at the same QSO and see what your partner used and use that time in your new upload.While on the subject of LotW don`t remember if its been mentioned on here or not but recently ARRL and Club Log have formed a new partnership in that Clublog confirmed QSO`S are now accepted for LOTW credit and same the other way.  Hope that helps 73 Morris wa4mit.



On Tuesday, April 25, 2017 8:10 AM, "Dan Morris dbmorris315@... [070]" <070@...> wrote:


 
One more question. How do I correct a contact in LoTW. It says I can correct a contact but does not say how I go about doing that???

Dan Morris KZ3T
dbmorris315@...






Re: LoTW

Rick - N7WE
 

Dan-

In addition to David's reply, this from LoTW ARRL:

  • both QSO descriptions specify start times within 30 minutes of each other

Rick - N7WE
070 - #1602


Re: LoTW

Dan Morris - KZ3T
 

Thanks David for the info.  Funny how LoTW in their help file says we can correct a QSO but does not say how unless what they mean is to resubmit.  that is what I will do though.

Dan Morris  KZ3T





On Apr 25, 2017, at 9:20 AM, David Rock david@... [070] <070@...> wrote:


On Apr 25, 2017, at 08:03, Dan Morris dbmorris315@... [070] <070@...> wrote:

One more question. How do I correct a contact in LoTW. It says I can correct a contact but does not say how I go about doing that???


You can’t correct it in the way you are thinking.  All you can do re-upload the corrected information; the original incorrect QSO will always be there, but never be matched.  It’s “corrected” in the sense that the new info will match, but the old one will not be removed.



David, K9DWR
#1604 LONP #255
david@...



Re: LoTW

Morris WA4MIT
 

Dan I believe the LOTW window is +/- 15 minutes so that makes a 30 min. total window and you can not correct or change a uploaded QSO you have to change it then upload again. If you use eQSL look at the same QSO and see what your partner used and use that time in your new upload.While on the subject of LotW don`t remember if its been mentioned on here or not but recently ARRL and Club Log have formed a new partnership in that Clublog confirmed QSO`S are now accepted for LOTW credit and same the other way.  Hope that helps 73 Morris wa4mit.



On Tuesday, April 25, 2017 8:10 AM, "Dan Morris dbmorris315@... [070]" <070@...> wrote:


 
One more question. How do I correct a contact in LoTW. It says I can correct a contact but does not say how I go about doing that???

Dan Morris KZ3T
dbmorris315@...




Re: LoTW

David, K9DWR
 

On Apr 25, 2017, at 08:03, Dan Morris dbmorris315@... [070] <070@...> wrote:

One more question. How do I correct a contact in LoTW. It says I can correct a contact but does not say how I go about doing that???
You can’t correct it in the way you are thinking. All you can do re-upload the corrected information; the original incorrect QSO will always be there, but never be matched. It’s “corrected” in the sense that the new info will match, but the old one will not be removed.



David, K9DWR
#1604 LONP #255
david@...


LoTW

Dan Morris - KZ3T
 

One more question. How do I correct a contact in LoTW. It says I can correct a contact but does not say how I go about doing that???

Dan Morris KZ3T
dbmorris315@...


LoTW

Dan Morris - KZ3T
 

OK all you LoTW smart ones. I’m a bit confused and cannot find anything in the help file at LoTW about a contact not being confirmed.

I logged a contact and I found that what I logged and what the other station logged is 21 minutes different. Not sure why, although I have noticed that “MOST” stations log their contacts when they finish the QSO. I always thought that we were supposed to log a contact when it begins. Most of the time no problem as a lot of contacts don’t last but a couple of minutes. But some can be rag chews as this one was so our times differed slightly. I think eQSL gives a 30 minute window but not sure what LoTW gives to be able to confirm a contact. Evidently less than 21 minutes though.

Anyone have any comments on this??

Thanks

Dan Morris KZ3T 070-1065
dbmorris315@...


Re: 6M STARTING TO OPEN

Brian (N2MLP)
 

Happen live as sent

Call sign in e-mail

 

From: 070@... [mailto:070@...]
Sent: Saturday, April 22, 2017 11:51 PM
To: 070@...
Subject: [070] Re: 6M STARTING TO OPEN

 

 

Please put the UTC  Zulu time on these reports.  And where you are, too.  Thanks.  I'm just too challenged to figure out when this was when it's posted as Pacific time.  

David Hardy   

KB3RAN

 


Re: Member List

boat.anchor@...
 


Bingo

TU Steve

Barry


---In 070@..., <w3hf@...> wrote :

Barry -

I think Rick mentioned this, but #1982 is the last member that appears UNTIL you scroll the listing. This isn't your browser's scroll bar--it's a second scroll bar that's within the web page.

Just to the right of #1982 there's a downward-pointing triangle. That's the bottom of the page's internal scroll bar. Click-and-hold on that and you should see the higher-numbered members. Or click just above it to move a page at a time.

Steve
W3HF 
 

On 04/12/17, boat.anchor@... [070]<070@...> wrote:
 


The really weird thing is I see same result (1982) on a different computer
Barry



Re: 6M STARTING TO OPEN

DAVE KB3RAN 1692/381
 

Please put the UTC  Zulu time on these reports.  And where you are, too.  Thanks.  I'm just too challenged to figure out when this was when it's posted as Pacific time.  

David Hardy   
KB3RAN
 


Re: 6M STARTING TO OPEN

Brian (N2MLP)
 

 

 

========================

         de N2MLP Brian

       Monroe County PA

 

 

========================

 

 


Re: CE1ANF cq'n on 20m at 00:00 zulu

Jerry N9AVY
 

Jeff:

Thanks for the heads up ! Got 'em !   Had very long day at work and came home exhausted.  This was highlight of the day ! Thanks !

Jerry  n9avy



From: "JEFF WALSH jeffwalsh1644@... [070]" <070@...>
To: Yahoogroups <070@...>
Sent: Wednesday, April 19, 2017 7:02 PM
Subject: [070] CE1ANF cq'n on 20m at 00:00 zulu

 
 
JEFF WALSH
W3WMU
#1673
BUBBAWOOD
WORLDWIDE HEADQUARTERS
STURGIS, MS.


19361 - 19380 of 70221