Download Schweitzer Engineering Laboratories Port Devices Drivers
Download Schweitzer Engineering Laboratories Port Devices Driver Download

Documents Home :: current-stable :: drivers :: driver8.html	Download
Advanced Search

Schweitzer engineering laboratories SEL-787 Pdf User Manuals. View online or download Schweitzer engineering laboratories SEL-787 Instruction Manual. SEL-5827 Virtual Connect Client—Create a temporary serial COM port or Ethernet TCP port for engineering access applications with the SEL-3620 and SEL-3622 Security Gateways. SEL-5828 Virtual Port Service—Create multiple persistent serial COM ports or Ethernet TCP ports for automation applications. SEL provides complete power system protection, control, monitoring, automation, and integration for utilities and industries worldwide. SEL products, systems, services, and training make electric power safer, more reliable, and more economical.

Generic Reference Driver

Last update: 27-Jan-2014 05:31 UTC

Synopsis

Address: 127.127.8.u
Reference ID: PARSE
Driver ID: GENERIC
Download schweitzer engineering laboratories port devices driver license

Serial Port: /dev/refclock-u; TTY mode according to clock type
PPS device: /dev/refclockpps-u; alternate PPS device (if not available via the serial port)

Description

The PARSE driver supports 20 different clock types/configurations. PARSE is actually a multi-clock driver.

The actual receiver status is mapped into various synchronization states generally used by receivers. The driver is configured to interpret the time codes of Meinberg DCF77 AM receivers, DCF77 FM receivers, Meinberg GPS16x/17x receivers, Trimble SV6 GPS, ELV DCF7000, Schmid, Wharton 400A and low cost receivers (see list below).

The reference clock support in NTP contains the necessary configuration tables for those receivers. In addition to supporting several different clock types and up to 4 devices, the processing of a PPS signal is also provided as a configuration option. The PPS configuration option uses the receiver-generated time stamps for feeding the PPS loopfilter control for much finer clock synchronization.

CAUTION: The PPS configuration option is different from the hardware PPS signal, which is also supported (see below), as it controls the way ntpd is synchronized to the reference clock, while the hardware PPS signal controls the way time offsets are determined.

The use of the PPS option requires receivers with an accuracy of better than 1ms.

Timecode variables listed by ntpq (8)

The ntpq program can read and display several clock variables. These hold the following information:

refclock_format: A qualification of the decoded time code format.
refclock_states: The overall running time and the accumulated times for the clock event states.
refclock_status: Lists the currently active receiver flags. Additional feature flags for the receiver are optionally listed in parentheses.
refclock_time: The local time with the offset to UTC (format HHMM).
timecode: The actual time code.

If PPS information is present, additional variables are available:

refclock_ppsskew: The difference between the RS-232-derived timestamp and the PPS timestamp.
refclock_ppstime: The PPS timestamp.

Supported Devices

Currently, twenty-four clock types are supported by the PARSE driver and up to four (devices /dev/refclock-0 - /dev/refclock-3) of these clocks may be operational at any one time.
A note on the implementations:

These implementations were mainly done without actual access to the hardware, thus not all implementations provide full support. The development was done with the help of many kind souls who had the hardware and kindly lent me their time and patience during the development and debugging cycle. Thus for continued support and quality, direct access to the receivers is a big help. Nevertheless I am not prepared to buy these reference clocks - donations to (kardel <AT> ntp.org) are welcome as long as they work within Europe 8-).
Verified implementations are:
- RAWDCF variants
  These variants have been tested for correct decoding with my own homegrown receivers. Interfacing with specific commercial products may involve some fiddling with cables. In particular, commercial RAWDCF receivers have a seemingly unlimited number of ways to draw power from the RS-232 port and to encode the DCF77 datastream. You are mainly on your own here unless I have a sample of the receiver.
- Meinberg clocks
  These implementations have been verified by the Meinberg people themselves and I have access to one of these clocks.
- Schweitzer Engineering Laboratories SEL-240x clocks
  This implementation was provided and verified by SEL and Network Time Foundation has an SEL-2407 in one of its development labs.

The pictures below have been taken from and are linked to the vendors' web pages.

server 127.127.8.0-3 mode 0
MeinbergPZF5xx receiver family (FM demodulation/TCXO / 50μs)
server 127.127.8.0-3 mode 1
MeinbergPZF5xx receiver family (FM demodulation/OCXO / 50μs)
server 127.127.8.0-3 mode 2
MeinbergDCF C51 receiver and similar (AM demodulation / 4ms)
This mode expects the Meinberg standard time string format with 9600/7E2.
Note: mode 2 must also be used for Meinberg PCI cards under Linux, e.g. the GPS PCI card or the DCF77 PCI card. Please note the Meinberg Linux driver must be installed. That driver emulates a refclock device in order to allow ntpd to access those cards. For details, please refer to the README file that comes with the Meinberg driver package.
server 127.127.8.0-3 mode 3
ELV DCF7000 (sloppy AM demodulation / 50ms)
server 127.127.8.0-3 mode 4
Walter Schmid DCF receiver Kit (AM demodulation / 1ms)
server 127.127.8.0-3 mode 5
RAW DCF77 100/200ms pulses (Conrad DCF77 receiver module / 5ms)
server 127.127.8.0-3 mode 6
RAW DCF77 100/200ms pulses (TimeBrick DCF77 receiver module / 5ms)
server 127.127.8.0-3 mode 7
MeinbergGPS16x/GPS17x receivers (GPS / <<1μs)
This mode expects either the University of Erlangen time string format or the Meinberg standard time string format at 19200/8N1.
The University of Erlangen format is preferred. Newer Meinberg GPS receivers can be configured to transmit that format; for older devices, a special firmware version may be available.
In this mode some additional GPS receiver status information is also read. However, this requires a point-to-point connection. Mode 18 should be used if the device is accessed by a multidrop connection.
Note: mode 7 must not be used with Meinberg PCI cards; use mode 2 instead.
server 127.127.8.0-3 mode 8
server 127.127.8.0-3 mode 9
TrimbleSVeeSix GPS receiver TAIP protocol (GPS / <<1μs)
Pr electronics a/s port devices driver download for windows.
server 127.127.8.0-3 mode 10
TrimbleSVeeSix GPS receiver TSIP protocol (GPS / <<1μs) (no kernel support yet)
server 127.127.8.0-3 mode 11
Radiocode Clocks Ltd RCC 8000 Intelligent Off-Air Master Clock support
server 127.127.8.0-3 mode 12
server 127.127.8.0-3 mode 13
Diem's Computime Radio Clock
server 127.127.8.0-3 mode 14
RAWDCF receiver (DTR=high/RTS=low)
server 127.127.8.0-3 mode 15
WHARTON 400A S

Download Schweitzer Engineering Labratories Port Devices Driver