1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Unix epoch time conversion in EPICS Db |
From: | "Mooney, Tim M." <[email protected]> |
To: | Rod Nussbaumer <[email protected]>, "[email protected]" <[email protected]> |
Date: | Thu, 29 Mar 2018 16:23:25 +0000 |
Hi Rod,
There is "Soft Timestamp" support for the stringin record in base.
There is also Frank Lenksus' fGetDateStr.c (in the autosave/asApp/src directory, among other places), which makes a date string that is sortable alphanumerically, which is good for including in filenames.
Tim Mooney ([email protected]) (630)252-5417
Beamline Controls Group (www.aps.anl.gov) Advanced Photon Source, Argonne National Lab From: [email protected] <[email protected]> on behalf of Rod Nussbaumer <[email protected]>
Sent: Thursday, March 29, 2018 10:14:18 AM To: [email protected] Subject: Unix epoch time conversion in EPICS Db Hi all.
I'm using streamDevice to read string data from a device, and one of the data that it returns is the Unix Epoch time as a floating point value in ASCII string format: TIME_NOW:1522335837.961008 I would like to be able to translate this to a more human readable format. Is there any built-in function in an IOC (3.14.12.5 right now) that I can use to do the conversion? Or, does anyone have a set of reliable CALC record expressions that can be used to get me something like YY:MM:DD-hh:mm:ss in any displayable format? I know the formula to do this has all sorts of quirky exceptions and so on, so I'd like to avoid trying to roll my own if I can avoid it, especially if the facility to do it already exists. Thanks. Rod Nussbaumer TRIUMF Vancouver, Canada. |