Re: YANFCQ [Yet Another Non-FastCode Question]: TDateTime -> uSec resolution

From: "John Herbster" <herb-sci1_AT_sbcglobal.net>
Date: Thu, 28 Jul 2005 18:49:02 -0500

"Kristofer Skaug" <nospam@xxxxxxxxx> wrote

> In the space industry there's the "CCSDS Unsegmented time Code" (CUC)
as
> well as "CCSDS Day-Segmented time code" (CDS) which are both strictly
> integer based:

Thx for info.
Back when I was tracking stuff, we used IRIG standards.
Rgds, JohnH

.

References:
- YANFCQ [Yet Another Non-FastCode Question]: TDateTime -> uSec resolution
  - From: Kristofer Skaug
- Re: YANFCQ [Yet Another Non-FastCode Question]: TDateTime -> uSec resolution
  - From: Lord Crc
- Re: YANFCQ [Yet Another Non-FastCode Question]: TDateTime -> uSec resolution
  - From: Kristofer Skaug
- Re: YANFCQ [Yet Another Non-FastCode Question]: TDateTime -> uSec resolution
  - From: Lord Crc
- Re: YANFCQ [Yet Another Non-FastCode Question]: TDateTime -> uSec resolution
  - From: Kristofer Skaug

Prev by Date: Re: YANFCQ [Yet Another Non-FastCode Question]: TDateTime -> uSec resolution
Next by Date: Re: YANFCQ [Yet Another Non-FastCode Question]: TDateTime -> uSec resolution
Previous by thread: Re: YANFCQ [Yet Another Non-FastCode Question]: TDateTime -> uSec resolution
Next by thread: Re: YANFCQ [Yet Another Non-FastCode Question]: TDateTime -> uSec resolution
Index(es):
- Date
- Thread