Talk:IRIG timecode

suggestion 2

Reference to IRIG-J-1x and 2x seems to be missing. Apparently these formats are structurally different and covered by a separate standard 212-00. ASCII expression: <SOH>DDD:HH:MM:SS.S<CR><LF>. Unfortunately my level of expertise (and English knowledge) does not allow me to integrate this "missing item" into the existing article. Anyone feel like to fill this gap ? Thanks for the wikipedians.

Pierre from Belgium--212.68.214.146 (talk) 09:23, 6 April 2011 (UTC)[reply]

From Rairden

Good article guys, nice one. TiHead 14:53, 11 January 2007 (UTC)[reply]

This reference appears to be stale, or password protected.

IRIG standard 200-04 (PDF)

http://www.jcte.jcs.mil/RCC/manuals/200-04/TT-45.pdf

Rairden 07:18, 31 January 2007 (UTC)[reply]

suggestion

I would suggest starting the article with a brief description of what IRIG time codes are, i.e. a dummed down description of what they are and what are they used for and stuff, before writing the history of them. Most people, including myself, search terms in wikipedia to get a quick idea of what those sort of technical terms mean. If needed, one can read on further to get more detail.

... my 2 cents.

I agree - I came here because I read the term in a document and wanted to know what it means. I scanned through this article and still have no idea what IRIG-B is used for or where.

Fishtrousers (talk) 15:24, 25 May 2012 (UTC)[reply]

correction

A list of "... recognized combinations ..." is listed. IMHO the writer was probably referring to an earlier version of the standard.
Table 4-1 of the new IRIG 200-04 standard permits other formats!
For example, Table 4.3 there specifically shows B124 to B127 examples, none of these listed in the "... recognized combinations ..." here.

more on combinations

B002 is a common combination. In fact, several IRIG clocks use B002 as a valid combination.

--207.232.27.5 (talk) 10:34, 19 February 2008 (UTC)[reply]

Another ASCII IRIG Code: CS-5

[I'm not sure if this belongs here with the other IRIG codes, or if it is too specialized, since it is used primarily by NASA, and US military missile ranges.]

There is another ASCII IRIG code, IRIG CS-5, defined in IRIG Standard 215-12, "Asynchronous ASCII Event Count Status Codes" (https://apps.dtic.mil/sti/pdfs/ADA628275.pdf). It is used in missile and space launches to distribute the time till launch (e.g., "T minus 10 minutes, 13 seconds and counting"). There are four basic versions. The second digit indicates the resolution:

1 - 1 second resolution
2 - 0.1 second resolution

The following codes are defined:

CS-511z: <SOH>I ±DDD HH:MM:SS #<CR><LF>
CS-522z: <SOH>I ±DDD HH:MM:SS.S #<CR><LF>
CS-513z: <SOH>I ±DDD HH:MM:SS # ddd hh:mm:ss.sss &<CR><LF>
CS-524z: <SOH>I ±DDD HH:MM:SS.S # ddd hh:mm:ss.sss &<CR><LF>

where:

<SOH> is an ASCII Start-Of-Header character.
I is an identification character, usually blank.
± is the sign, minus before launch, plus afterwards.
DDD is days to/from launch.
HH is hours to/from launch.
MM is minutes to/from launch.
SS or SS.S is seconds to/from launch.
# is the count status: "H" if holding, blank otherwise.
ddd is the predicted or actual day of launch.
hh is the predicted/actual hour of launch.
mm is the predicted/actual minute of launch.
ss.sss is the predicted/actual seconds of launch.
& is "P" for predicted launch time, "A" for actual launch time.
<CR> is ASCII carriage return.
<LF> is ASCII linefeed.

The last digit of the code designation, z, indicates the baud rate:

2 - 300
3 - 600
4 - 1200
5 - 2400
6 - 4800
7 - 9600
8 - 19200
9 - 38400

IRIG CS-5259 is a multiplexed, eight-channel version of IRIG CS-524 transmitted at 38400 baud.

[There is another IRIG event count status code called IRIG CS-3, defined in IRIG Standard 209-90, "Event Count Status Code Formats" (https://www.trmc.osd.mil/wiki/download/attachments/113019844/209-90.pdf?version=1&modificationDate=1623181164780&api=v2). The first half looks almost like IRIG-B, except the time runs backwards until launch, and forwards afterwards. The second half is almost a duplicate of the first, and is zero until the time of launch, after which it holds the launch time. If there is any interest, I would be happy to do a write up on it.] — Preceding unsigned comment added by SXandR (talk • contribs) 01:05, 3 October 2023 (UTC)[reply]