Key Features
- Generation of IRIG-B or AFNOR time
codes
- 2 time-trigger-inputs
- 2 TTL inputs for status
information
- PCI LOCAL BUS interface,
3.3V or 5V, 33MHz or 66MHz,
PCI-X compatible
- Plug and play
- Pulses per second and per
minute
- RS232 interface
- Status LEDs
- Reception of time code formats IRIG A/B
or AFNOR
- Configurabel time zone
- Driver software for all popular
operating systems
- Optional optical input and/or output
for time codes
- Optional DDS frequency
synthesizer
Description
The board TCR167PCI has been designed to receive and
to generate IRIG and AFNOR time codes.
It is used in applications like data aquisition,
standalone computer time synchronization (for systems
without a network connection or higher accuracy
requirements) or as an IRIG converter device.
Receiver: the module provides two input
channels for decoding of modulated and unmodulated
time codes in IRIG-A/B or AFNOR format. The
receiver's automatic gain control (AGC) allows the
reception of modulated IRIG signals within an
amplitude range from 600 mVpp to 8 Vpp. In addition,
the TCR167PCI provides an optocoupler input for
decoding unmodulated codes with TTL- or RS-422 level
for example. The board can be delivered with an
optical input for unmodulated codes
optionally.
The decoded date and time can be read via the
PCI/PCI-X bus interface and is also transmitted via
the board's RS-232 port. A buffered real time clock
keeps time and date after power down.
Generator: the board TCR167PCI can generate
time codes in IRIG-B or AFNOR format. These signals
are provided as modulated (3 Vpp/1 Vpp into 50 ohm)
and unmodulated (TTL into 50 ohm and RS-422) time
codes. An optical output for unmodulated codes is
available on request.
The independent configuration of the time code and
its offset to UTC of the receiver and the generator
allows the use of TCR167PCI for time code conversion
applications.
The drivers package for Windows contains a
time adjustment service which runs in the background
and adjusts the Windows system time continously and
smoothly. A monitor program is also included which
lets the user check the status of the device and the
time adjustment service, and can be used to modify
configurable parameters.
The driver package for Linux contains a
kernel driver which allows the board to be used as a
reference time source for the NTP daemon which is
shipped with most Linux distributions. This also
turns the computer into a NTP time server which can
also provide accurate time to other NTP clients on
the network. Some command line tools can be used to
setup configurable parameters and monitor the status
of the board.
Additional drivers packages are available for
DOS, Novell NetWare, and OS/2.
At the bottom of this page there's a link to the
download area.
The device's serial port can be used to update the
card's firmware. Additionally it can be connected to
the serial port of a computer to use the card as
reference time source under operating systems where a
serial time string is supported, e.g. by NTP, but no
kernel device driver is available. If you are going
to use the TCR167PCI in your own applications, please
download our SDK which shows how to access the card
from within your software.
All drivers and API sample source code can be
downloaded free of charges from our website and we
are happy to assist you if you face any difficulties
in using the Meinberg driver API in your software
development process.
Characteristics
| Status
info: |
2 status LEDs for
indication of: detection of a correct code,
synchronization of the internal timing and
holdover mode |
| Input
signal: |
Modulated IRIG A/B,
IEEE1344 or AFNOR signal, input insulated by
transformer, input impedance 50 ohm, 600 ohm or 5
kohm selectable by jumper
unmodulated (DC level shift) IRIG A/B, IEEE1344
or AFNOR signal, input insulated by
photocoupler |
| Accuracy free
run: |
±1·10E-8 if the
decoder was synchronous for at least 1 h |
| IRIG Time Code
Input: |
IRIG-A133, A132, A003,
A002, B123, B122, B003, B002, IEEE1344 and AFNOR
NFS 87-500 (other codes on request) |
| Pulse
outputs: |
Pulses per second
(RS-232/TTL level) and per minute (TTL level),
pulse duration 200 msec |
| Precision of
timebase: |
±5 µsec referred
to IRIG-reference marker |
|
Interface: |
Single serial RS232
interface |
| Data format PC
interface: |
Binary, byte
serial |
| Data format of
interfaces: |
Baudrate: 300, 600, 1200,
2400, 4800, 9600, 19200, 38400 baud
Framing: 7E2, 8N1, 8E1, 8N2
Output string: 32 ASCII characters with date,
time and status information |
|
Statusbyte: |
Information about holdover
mode, synchronization since last reset and the
validity of the RTC data. |
| Generated time
codes: |
IRIG-B123, B122, B003,
B002, IEEE1344 and AFNOR NFS 87-500 (other codes
on request) |
| Output
signal: |
Modulated IRIG-B or AFNOR
signal, 3 Vpp (high) and 1 Vpp (low) into 50
ohm
unmodulated (DC Level Shift) IRIG-B or AFNOR
signal, TTL into 50 ohm and RS-422, active high
or active low selectable by jumper |
| Time-Trigger
inputs: |
Triggered by falling TTL
slope
Time of trigger event readable via computer slot
or optional second RS232-interface |
| Status
inputs: |
2 status inputs, TTL level,
readable via PCI/PCI-X bus |
| Electrical
connectors: |
Female BNC-connectors
male 9-pole D-Sub connector |
| Computer
interface: |
33MHz- or 66MHz-PCI BUS
(PCI-X) 32 Bit/3.3V or 5V card slot |
| Backup battery
type: |
When main power supply
fails, hardware clock runs free on quartz basis,
life time of lithium battery min. 10 years |
| Board
type: |
PCI card short |
| Ambient
temperature: |
0 ... 50°C / 32 ...
122°F |
|
Humidity: |
Max. 85% |
|
Options: |
- Optical input and/or
output for time codes, ST connector for GI
50/125µm or GI 62,5/125µm gradient
fibre
- DDS frequency synthesizer 1/8 Hz up to 10 MHz,
TTL into 50 ohm, sinewave 1.5 Vrms
- OCXO LQ (specifications look at
oscillator options) for higher accuracy in
holdover mode |
| RoHS-Status of the
product: |
This product is fully RoHS
compliant |
| WEEE status of the
product: |
This product is handled as
a B2B category product. In order to secure a WEEE
compliant waste disposal it has to be returned to
the manufacturer. Any transportation expenses for
returning this product (at its end of life) have
to be incurred by the end user, whereas Meinberg
will bear the costs for the waste disposal
itself. |
|
