Call Search
     

New to Ham Radio?
My Profile

Community
Articles
Forums
News
Reviews
Friends Remembered
Strays
Survey Question

Operating
Contesting
DX Cluster Spots
Propagation

Resources
Calendar
Classifieds
Ham Exams
Ham Links
List Archives
News Articles
Product Reviews
QSL Managers

Site Info
eHam Help (FAQ)
Support the site
The eHam Team
Advertising Info
Vision Statement
About eHam.net

   Home   Help Search  
Pages: [1]   Go Down
  Print  
Author Topic: Date used in log  (Read 3612 times)
KK4EOF
Member

Posts: 11




Ignore
« on: June 14, 2014, 03:44:15 PM »

HI all.
I am not sure what date to use in my log.  I always use UTC time, but do I use the local date or the date in Greenwich, England?  What about international contacts, do you use the date in the country you have contacted or your own local date?  Or does it even matter?  I am assuming that the software that checks qsos for LOTW or whatever will invalidate a contact if the dates are different by a day.  That could screw up getting credit for DXCC or other awards.  What does automatic logging software do, use the os system date, or does it adjust based on the DX entity you're logging?
Logged
AA4PB
Member

Posts: 12985




Ignore
« Reply #1 on: June 14, 2014, 03:57:20 PM »

Use the UTC time and date. It is the same everywhere in the world.
Logged
KA5PIU
Member

Posts: 446




Ignore
« Reply #2 on: June 14, 2014, 06:36:26 PM »

Hello.

As a rule, you use UTC or YOUR local time.
Stay consistent.
Some prefer UTC as it solves the problem with daylight savings time.
Thank you.
Logged
KS2G
Member

Posts: 436




Ignore
« Reply #3 on: June 14, 2014, 06:43:28 PM »

As AA4BP said ... use UTC time and date.

Be sure you take Daylight Saving Time into account when you do the conversion from local time to UTC.

In your case (being located in Florida) -- UTC is 5 hours ahead of Eastern Standard Time (the date changes at 7pm your local time) and 4 hours ahead of Eastern Daylight Time (the date changes at 8pm your local time).
Logged
KG4RUL
Member

Posts: 2749


WWW

Ignore
« Reply #4 on: June 14, 2014, 06:54:50 PM »

As AA4BP said ... use UTC time and date.

Be sure you take Daylight Saving Time into account when you do the conversion from local time to UTC.

In your case (being located in Florida) -- UTC is 5 hours ahead of Eastern Standard Time (the date changes at 7pm your local time) and 4 hours ahead of Eastern Daylight Time (the date changes at 8pm your local time).


OR

Maintain a station clock that is set to UTC
Logged
KS2G
Member

Posts: 436




Ignore
« Reply #5 on: June 14, 2014, 08:16:57 PM »


OR

Maintain a station clock that is set to UTC

And don't change it when Daylight time starts/ends.  Wink
Logged
K7KBN
Member

Posts: 2825




Ignore
« Reply #6 on: June 14, 2014, 09:35:56 PM »

HI all.
I always use UTC time, but do I use the local date or the date in Greenwich, England? 

Think...if you're using UTC, and it's midnight UTC, does the date in Greenwich change?
Logged

73
Pat K7KBN
CWO4 USNR Ret.
KI6LZ
Member

Posts: 601




Ignore
« Reply #7 on: June 14, 2014, 09:41:49 PM »

Time and date are referenced to UTC. This avoids the problem of every country having different local times and dates. And yes, all logging should be in UTC date and time. I've had some that use local and it messes me up.

Don't know why the underline for all. Oh well.
Logged
M6GOM
Member

Posts: 993




Ignore
« Reply #8 on: June 15, 2014, 03:39:30 AM »

Decent logging software should do it all for you regardless, automatically converting all logs to UTC from local.
Logged
N0IU
Member

Posts: 1350


WWW

Ignore
« Reply #9 on: June 15, 2014, 07:08:38 AM »

Hello.

As a rule, you use UTC or YOUR local time.
Stay consistent.
Some prefer UTC as it solves the problem with daylight savings time.
Thank you.

With all due respect, this is really, really BAD information!

Remember, the "U" in UTC stands for "universal". If you send the other station a paper card with your local time, they will send it back to you with the comment "NIL" (not in log) if you are lucky. Most likely, they will just throw it away. If you use an electronic confirmation service like LoTW or eQSL, you won't get a confirmation since the times must match +/- 30 minutes.

ALWAYS use UTC!
Logged
WA7PRC
Member

Posts: 276


WWW

Ignore
« Reply #10 on: June 15, 2014, 09:05:00 PM »

As a rule, you use UTC or YOUR local time.
With all due respect, this is really, really BAD information!
...
ALWAYS use UTC!
Ditto.
Logged
K1PJR
Member

Posts: 148




Ignore
« Reply #11 on: June 16, 2014, 05:18:45 AM »

Your log should automatically enter the date based on UTC.  At first i would enter the date manually until I received an email from an op saying I had the wrong date on my QSL card.  Always use UTC and date.
Logged
KB2WIG
Member

Posts: 120




Ignore
« Reply #12 on: June 16, 2014, 07:06:34 AM »

time.gov   is nice... Just click the arrow until you c utc.

WWV/
WWVH/
WWVB/
MSF/
JJY
CHU

or

http://www.lownoiserecords.com/wwv_the_tick.html


klc
Logged
N3QE
Member

Posts: 2358




Ignore
« Reply #13 on: June 16, 2014, 07:35:35 AM »

UTC date and time. Never anything else. When it rolls over to 0000Z in our evening, it is "tomorrow" UTC date.

Rules for LOTW matching:
Quote
What constitutes a QSO "match?"

To match, the two QSO records (yours and the other station's) must have:

Call of each QSO matches own call of the other (including portable identifiers)
The modes are in the same mode group (e.g., SSB and PHONE match because both are PHONE)
The date/time values are the same within 30 minutes (all times are UTC)
Logged
KB2FCV
Member

Posts: 1298


WWW

Ignore
« Reply #14 on: June 16, 2014, 10:08:21 AM »

UTC date and time. Never anything else. When it rolls over to 0000Z in our evening, it is "tomorrow" UTC date.


Exactly this.. as other posters stated.. if you have the wrong date, you'll get a NIL most likely if you send a QSL. It's pretty much standard that UTC is used for time in date in terms of logging, etc.
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!