FarSync T4E & T4E+ - 4 port PCI multi clock source synchronous / asynchronous cards
The FarSync T4E and FarSync T4E+ Universal PCI cards are intelligent 4 port transparent bitstream / HDLC cards with multiple clock sourcing options with multipliers and dividers suitable for providing WAN communications for VoIP and also requirements where clock synchronisation across ports is required.
Overview
The FarSync T4E and T4E+ cards and software are designed to provide high performance hardware communications solutions for business, government and military requirements who need a Universal PCI synchronous communications card with externally sourced line clocks or highly adaptable control of line clocks. The product includes a low level driver that allows access to the communications features available in the hardware. The cards can optionally use the host's standard TCP/IP protocol stack to allow access to IP based networks such as the Internet.
The FarSync SDK provides a Developers Toolkit for the product.
The T4E and T4E+ are Universal PCI communications cards (PCI and PCI-X compatible) with four independently configurable sync/async serial ports with and external synchronisation capability (eg sourced from GPS). Sync operation supports transparent bitstream and bitsync (HDLC) of up to 10 Mbits/s per line with a total card bandwidth of 64 Mbits/s. The highly flexible universal network connector supports RS232C, X.21, RS530 (RS422 signalling), RS449 (RS422 signalling) and V.35 network interfaces.
The FarSync T4E+ is a superset of the T4E features plus supports Manchester encoding, Conditioned Diphase, FM0, FM1 up to 10Mbits/s as well as NRZ line signalling and soft selectable line termination.
One of the unique features of the T4E is the huge variety of clock source options, clocks can be:
- Internally generated using a local clock generator
- External from the WAN communications line
- External via a special CTBus (H.100) clock bus connector
- Sourced on one port then routed to the others
- Sourced from a T4E then routed down the CTBus to other T4Es (and other cards supporting the CTBus) to allow clock synchronisation to be maintained.
- Multiplied or divided per port to obtain the required rate
- Independently configurable for each line
The transparent bitstream option available with the APIs is suitable for VoIP (as a subsystem), video and voice such as T-DMB (Digital Multimedia Broadcasting), DAB (Digital Audio Broadcasting) ETI (Ensemble Transport Interface - ETSI EN 300 799).
Typical Applications
The FarSync T4E/T4E+ suits a very wide number of different applications these include:
- Reproduction of legacy Audio streams across the TCP/IP networks (VoIP) using Satellite (GPS) clock source synchronisation
- Interfacing DAB ETI (Ensemble Transport Interface - ETSI EN 300 799) transparent bit streams to Servers
- Interfacing high speed MPEG Video bit streams T-DMB ETI to Servers
- High speed multi-port HDLC framing.
- Use of bitstreaming for the implementation of non standard or specialist protocols
- Network clock synchronisation
- Multi purpose multi port communication card supplying a wide range of card generated clock speeds
- Line connection card for LabVIEW applications
- Use of Manchester Encoding or Conditioned Diphase on the T4E+ for long, reliable, high speed self clocking lines
Features under Windows:
The products include support for the Microsoft standard Windows SDCI API, providing applications with direct access to the card's communications port/s for bit synchronous (HDLC) framing, asynchronous and transparent bitstream operation. The special clocking features are all accessible though the SDCI interface. Async support is also provided by the Win32 COMM interface as well as the SDCI IOCTLs.
The card installs seamlessly under Windows 7, Vista, Windows XP, Windows Server 2003 and Windows Server 2008 on both 32 and 64 bit, single and multi-core systems. The FarSync drivers are signed by Microsoft for easy installation.
The cards can also be installed to appear as a NDIS (LAN) interface so it can simply use the TCP/IP stack to allow access to IP based networks such as the Internet or point to point. The NDIS driver supports TCP/IP running over PPP with optional authentication by CHAP or PAP (RFC 1334).
LabVIEW applications can access these cards.
The product is supplied with a comprehensive configuration utility, typical screens are shown below. The lines can be reconfigured and restarted without reloading the software. There is context sensitive help and an on-line manual should it be required. An advanced tab permits users to further specify the configuration of the line if necessary.
Configuration Utility Screens
The product is supplied with its own Line Monitor that allows the user to record, display and store line traffic with WAN protocol decoding for fast debugging.
Features under Linux:
The low level API is based on the raw socket interface and supports bit synchronous (HDLC) framed and transparent bitstream data. The cards can also use the TCP/IP stack to allow access to IP based networks such as the Internet. It also allows selection of the full range of clock modes.
The link level protocol can be PPP, Cisco HDLC or Frame Relay with optional authentication by CHAP, MSCHAP or PAP (RFC 1334) providing a standard point-to-point network interface.
The cards install seamlessly as a plug and play devices. The driver supports Linux kernel version 2.6, including the leading distributions supplied by Redhat, SuSE, CentOS, Debian, Ubuntu, Fedora, Slackware and more. Multi-processor systems are supported. The driver is dynamically loadable so a kernel rebuild is not required for the driver to be installed.
FarSite is committed to supporting the cards on new versions of Linux and Linux kernels as they are released. The source code for the driver is supplied with the product allowing rebuilding by the end user for use with almost any of the current or future Linux variants.
A configuration utility is provided to set the line speed, interface type and protocol, after which the ports may be configured with standard networking tools.
FarSync SDK - The Developers Toolkit
The FarSync SDK includes support for writing applications on both Linux and Windows and contains documentation, working sample applications, development and test utility applications. There is everything a user needs to rapidly develop and test a wide variety of applications such as specialist synchronous (HDLC framed) protocols or transparent bitstream data requirements including Audio, MPEG Video T-DMB and DAB ETI with bitstream encoder and decoder. The FarSync SDK is ordered separately from the FarSync T4E / T4E+.
Our Engineering department provides free email and telephone assistance to application developers using the API as part of the package provided when the FarSync SDK is purchased.
See details on the FarSync SDK Developers Toolkit and the APIs supported.
FarSync T4E / T4E+ Product Details
The cards are supplied with software drivers for Windows and Linux. This includes a low level driver that allows access to the communications features available in the hardware and an optionally installable driver that connects with the standard TCP/IP protocol stack to allow access to IP based networks such as the Internet.
The drivers supplied with Windows and Linux allow large numbers of ports to be supported by the installation of multiple FarSync T4E / T4E+ cards in a Server. Typically 12 or more cards (48+ ports) can be supported; the card limit is only dependent on the resources available in the host Server and the total bandwidth of the PCI bus.
Card Hardware
The card comprises a AMD processor with no wait state SRAM. The whole memory space may be mapped via the PCI / PCI-X interface to the PC/Server. The AMD processor contains a quad embedded HDLC / transparent controller with SDMA access (128 buffers per port) and a full range of timers.
The T4E supports four synchronous ports which can run to speeds of up to 10 Mbits/s full duplex internally clocked and 10 Mbits/s externally clocked. Total bandwidth supported by the card is 64 Mbits/s. A quad port UART (async controller) is included. Async or Sync operation is dynamically selectable on each port.
Network Interfaces
The multi function line drivers available on all the ports support RS232C (V.24), X.21 (V.11), V.35, RS530 (EIA530, RS422) and RS449 (RS422 signalling) network interfaces, all soft configurable and protected from static charges by ESD protection devices.
Clock Generation, Detection and Selection
Five on-board frequency synthesisers are configurable for generating clocks for the CTBus (H.100) and/or to the 4 serial ports.
Internally sourced clocks
Internally generated clocks to drive a serial communications port can be derived from either an on-board 8.192MHz clock (32ppm) or an CTBus bus clock and can be set to hundreds of different frequencies between 300 baud and 10 Mbits/s, the pre-programmed list is in the table below:
Internally generated clock rates supported by the T4E / T4E+
300, 600, 1200, 2400, 4800, 7200, 8000, 9600, 12000, 14400, 16000, 16800, 19200, 21600, 24000, 26400, 28800, 31200, 32000, 33000, 33333, 33600, 36000, 38400, 40000, 40800, 43200, 48000, 56000, 64000, 80000, 96000, 112000, 128000, 160000, 192000, 224000, 256000, 320000, 384000, 448000, 512000, 576000, 640000, 704000, 768000, 832000, 896000, 960000, 1000000, 1024000, 1088000, 1152000, 1216000, 1280000, 1344000, 1408000, 1472000, 1536000, 1600000, 1664000, 1728000, 1792000, 1856000, 1920000, 1984000, 2000000, 2048000, 2112000, 2176000, 2240000, 2304000, 2368000, 2432000, 2496000, 2560000, 2624000, 2688000, 2752000, 2816000, 2880000, 2944000, 3000000, 3008000, 3072000, 3136000, 3200000, 3264000, 3328000, 3392000, 3456000, 3520000, 3584000, 3648000, 3712000, 3776000, 3840000, 3904000, 3968000, 4000000, 4032000, 4096000, 4160000, 4224000, 4288000, 4352000, 4416000, 4480000, 4544000, 4608000, 4672000, 4736000, 4800000, 4864000, 4928000, 4992000, 5000000, 5056000, 5120000, 5184000, 5248000, 5312000, 5376000, 5440000, 5504000, 5568000, 5632000, 5696000, 5760000, 5824000, 5888000, 5952000, 6000000, 6016000, 6080000, 6144000, 6208000, 6272000, 6336000, 6400000, 6464000, 6528000, 6553600, 6592000, 6656000, 6720000, 6784000, 6848000, 6912000, 6976000, 7000000, 7040000, 7104000, 7168000, 7232000, 7296000, 7360000, 7424000, 7488000, 7552000, 7616000, 7680000, 7744000, 7808000, 7872000, 7936000, 8000000, 8064000, 8128000, 8192000, 9000000,10000000.
Many other frequencies can be synthesized to order, contact us to discuss your requirements.
Externally sourced clocks
FarSync T4E+ Line Status Utility
External clocks received from a serial port and used to a drive serial communications port can be any frequency up to 10,000,000Hz.
A CTBus (H.100 bus) clock may be generated from a received serial port clock for the following sub-set of frequencies: 38400, 57600, 64k, 128k, 256k, 512k, 1024k, 2048k, 4096k and 8192k.
Terminal Timing
Terminal Timing is supported to enable system-wide clock synchronisation.
Clock Routing
Clocks sourced from one port can be routed to drive the other ports.
Clock Speed Detection
A 16-bit timer enables differentiation between the clock frequencies, enabling auto-configuration of clock synthesisers when cables are connected.
H.100 Bus - Special clocking options
The cards support a subset of the CTBus (H.100) interface to enable synchronisation of serial port(s) to the H.100 bus (both master and slave modes), with CT_C8_A, CT_C8_B, CT_FRAME_A and CT_FRAME_B signals and jumper-selectable signal terminations. Serial port data is not frame aligned. This is of particular use in VoIP applications where a data on a line must be exactly reproduced at another location without slip.
In CT_Bus Slave mode, the CTBus clock (auto-selected with A being primary) can be used as a clock source to derive serial port clock(s).
In CT_Master mode, the CTBus clock (either A or B) can be derived from either a received serial port clock or an internal oscillator.
Use of the CTBus is supported by the Windows software only.
PC / Server PCI and PCI-X Compatibility
The FarSync T4E / T4E+ cards are suitable for systems with a PCI or PCI-X bus, covering single processor systems and multi-processor systems. The card is PCI revision 2.2 compliant with support for both 3.3 and 5 volt signalling, the power for the card is taken from the 3.3 volt supply rail. The cards may be fitted in either 32-bit PCI bus slots or 64-bit PCI-X bus slots as these Universal PCI cards will work perfectly well in both.
If you are not sure about your particular system, contact us and we can provide advice on the card that is most suitable for you.
FarSync T4E+ extra features
The T4E+ has all the features of the T4E plus the self clocking (clock for the data is decoded from the incoming data line) line signalling modes Manchester Encoding, Conditioned Diphase (Conditional Manchester), FM0 and FM1 at speeds of up to 10 MBits/s. This means separate clock lines are not required, these line signalling modes, they are a soft configurable alternative to NRZ and a reliable way of handling long high speed cable runs.
Line termination is supported on all the balanced pair signals for X.21 (V.11), V.35, RS530 (EIA530, RS422) and RS449 (RS422 signalling) operation. The line termination resistors may be soft selected on a port by port basis. The addition of line termination resistors can be helpful in improving signal quality on long high speed lines.
Cables
These four port cards use a single large high density 100 pin HIPPI type connector, all four lines are available though this connector. The quad port cable HCR4 attaches to the card and splits out the four network interfaces into separate network connectors to provide support for EIA-530 (RS422) and RS232C. X.21, V.35 and RS449 are available through transition connectors. Details of the cables and converters available are listed in the cables section of the order information table. Crossover cables, sometimes referred to as null modem cables, or DTE to DCE conversion cables are available, they are also detailed in the table below.
| Linux | |
|---|---|
| Distribution Support | Distributions by Red Hat, SuSE, Slackware, CentOS, Ubuntu, Debian, Fedora and more. |
| Kernel Support | All sub versions of kernel releases from 2.6.1 |
| Protocol Supported | TCP/IP, PPP, Cisco HDLC, Frame Relay, CHAP, MSCHAP, PAP (RFCs 1661, 1332, 1334) |
| API and Interfaces | Raw Socket API |
| Windows | |
| O/S Types | Windows 7, XP, Vista, Windows Server 2003, Windows Server 2008, LabVIEW running on a Windows O/S. |
| Protocol Supported | TCP/IP, PPP, CHAP, PAP (RFCs 1661, 1332, 1334) |
| API and Interfaces | Extended SDCI API, NDIS (LAN) where the line appears as a LAN interface |
| Utilities | Line Monitor to record, display and store line traffic included |
| Hardware Technical Specifications | |
|---|---|
| Card type and size | AMD processor with SRAM and quad port synchronous controller, Universal PCI (PCI-X compatible, PCI v2.2 compliant), bus mastering, DMA enabled, 100 pin HIPPI connector for the network connections, CTBus (H.100 bus) for external clocking connection, Suitable for 32 and 64 bit PCI bus slots |
| Physical characteristics | Short card (height 107mm, length 167mm) |
| Network connections supported | 4 synchronous or asynchronous ports |
| Link speed range Synchronous | T4E: X21, RS530, RS449: up to 10 Mbits/s internally or externally clocked, T4E+: X21, RS530, RS449, V.35: up to 10 Mbits/s internally or externally clocked, RS232C: up to 128 Kbits/s. |
| Link speed range Asynchronous | RS232C, X.21: 110, 150, 300, 600, 1200, 2400, 4800, 9600, 19200, 38.4K, 57.6K & 115.2 Kbits/s |
| Maximum total bandwidth | 64 Mbits/s |
| Line signal modes | On the T4E: NRZ; On the T4E+ NRZ, Manchester encoding, Conditioned Diphase, FM0, FM1 |
| Multiple cards | 12 or more; only dependant of the number of PCI slots available on the server |
| Line indicators | 4 LEDs one per port showing line connection status |
| ESD Protection | Yes, Littelfuse high speed ESD and over-voltage protection |
| MTBF | 141,438 hours calculated using Bellcore Method 1 Case 3, 40 deg.C ambient, 15 deg.C case temperature rise above ambient |
| Approvals | EN55022 class B, CE, FCC class B |
| Power requirements | < 1.75 A @ +3.3v, < 10mA @ +/- 12v (for ESD suppression) < 6 watt. Note: 5 volt supply not required |
| Line clocking - internal | Internal clock range: over 160 different frequencies between 300 baud and 10 Mbits/s. See the complete list. No special cables are required to use internal clocks. Internal clocking is supported on RS530, RS232C, X.21, V.35 and RS449 connections |
| Line clocking - external | External clocks received from a serial port and used to a drive serial communication sport can be any frequency up to 10MHz. For a specific sub-set of frequencies (38400, 57600, 64k, 128k, 256k, 512k, 1024k, 2048k, 4096k, 8192k) an H.100 bus clock may be derived from a received serial port clock. |
| Line Termination | On the T4E+ only line termination resistors can be configured in or out. |
| Terminal timing | Terminal Timing is supported to enable system-wide clock synchronisation. |
| Clock speed detection | A 16-bit timer enables differentiation between the clock frequencies listed above, enabling auto-configuration of clock synthesisers when cables are connected. |
| H.100 Bus - special clocking options | Supports a subset of the H.100 interface to enable synchronisation of serial ports(s) to the H.100 bus in both master and slave modes (Windows only). |
| RoHS Compliance | Yes |
| Cables | Cables are ordered separately, see the Cables section for details |
| Warranty | 5 years |
| Product Name | Description | Product Code | |
| FarSync T4E |
|
Intelligent Universal PCI 4 port synchronous bus mastering card (X.21 / V.35 / RS232C / EIA530 / RS422 / RS449) up to 10Mbits/s per port, bitstream, HDLC and asynchronous support. Provides an API and operation on TCP/IP links. For Linux and Windows. Highly flexible clocking options include external clock source via a H.100 bus and clock frequency multiplication and division. To develop applications that use the API order the FarSync SDK. Cables are ordered separately |
FS4444 |
| FarSync T4E+ |
|
Intelligent Universal PCI 4 port synchronous bus mastering card (X.21 / V.35 / RS232C / EIA530 / RS422 / RS449) up to 10Mbits/s per port, bitstream, HDLC and asynchronous support. Manchester encoding and NRZ selectable. Provides an API and operation on TCP/IP links. For Linux and Windows. Highly flexible clocking options include external clock source via a H.100 bus and clock frequency multiplication and division. To develop applications that use the API order the FarSync SDK. Cables are ordered separately |
FS4446 |
| FarSync SDK | Linux and Windows Developers Toolkit for the FarSync T4E / T4E+ and other FarSync cards - order this if you want to write software to use the card's API | FS9610 | |
| Cables for the FarSync T4E / T4E+ | |||
|---|---|---|---|
| HCR4 |  |
HCR4, Quad port EIA-530 and RS232C DTE cable, 2.0 metres for use with FarSync T4E cards, see pinouts. Also supports X.21, V.35 and RS449 interfaces with addition of conversion cables TCX1, TCV1 and TC449 respectively, | FS6076 |
| TCX1 |  |
TCX1, X.21 DTE (V.11) DB-15M 1 port HCR4 cable to X.21 transition connector, see pinouts | FS6052 |
| TCV1 |  |
TCV1, V.35 DTE V.35M 1 port HCR4 cable to V.35 transition connector, see pinouts | FS6053 |
| TC449 | TC449, RS449 DTE DB-37M 1 port HCR4 cable to RS449 transition connector, see pinouts | FS6054 | |
| Special Purpose Cables for all T-Series cards | |||
| Null-MX |  |
X.21 double shielded crossover cable, 15 pin D type female connectors, 0.5 metres. Converts DTE presentation to DCE. Suitable for FarSync T-Series cards, see pinouts |
FS6090 |
| X21-EXT |  |
X.21 double shielded 15 metre extension cable, 15 pin D type female to 15 pin D type male connector | FS6091 |
| Null-MR4 |  |
Combined RS530 (RS422, EIA 530) and RS232C (V.24) double shielded crossover cable, 25 pin D type female connectors, 0.5 metres. Converts DTE presentation to DCE. Suitable for FarSync T-Series cards. |
FS6097 |
17-Aug-2011
Legal Notice | Site Map | © 2011 FarSite Communications All rights reserved | Site design: Pureedesign.com
