FarSync T4E - 4 port Universal PCI multi clock source synchronous WAN communications card
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Table of internally generated clock rates supported by the T4E |
||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
300 |
600 |
1200 |
2400 |
4800 |
7200 |
8000 |
9600 |
12000 |
14400 |
16000 |
16800 |
|
19200 |
21600 |
24000 |
26400 |
28800 |
31200 |
32000 |
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 |
1024000 |
|
1088000 |
1152000 |
1216000 |
1280000 |
1344000 |
1408000 |
1472000 |
1536000 |
1600000 |
1664000 |
1728000 |
1792000 |
|
| 1856000 |
1920000 |
1984000 |
2048000 |
2112000 |
2176000 |
2240000 |
2304000 |
2368000 |
2432000 |
2496000 |
2560000 |
|
2624000 |
2688000 |
2752000 |
2816000 |
2880000 |
2944000 |
3008000 |
3072000 |
3136000 |
3200000 |
3264000 |
3328000 |
|
| 3392000 |
3456000 |
3520000 |
3584000 |
3648000 |
3712000 |
3776000 |
3840000 |
3904000 |
3968000 |
4032000 |
4096000 |
|
| 4160000 |
4224000 |
4288000 |
4352000 |
4416000 |
4480000 |
4544000 |
4608000 |
4672000 |
4736000 |
4800000 |
4864000 |
|
| 4928000 |
4992000 |
5056000 |
5120000 |
5184000 |
5248000 |
5312000 |
5376000 |
5440000 |
5504000 |
5568000 |
5632000 |
|
| 5696000 |
5760000 |
5824000 |
5888000 |
5952000 |
6016000 |
6080000 |
6144000 |
6208000 |
6272000 |
6336000 |
6400000 |
|
| 6464000 |
6528000 |
6592000 |
6656000 |
6720000 |
6784000 |
6848000 |
6912000 |
6976000 |
7040000 |
7104000 |
7168000 |
|
| 7232000 |
7296000 |
7360000 |
7424000 |
7488000 |
7552000 |
7616000 |
7680000 |
7744000 |
7808000 |
7872000 |
7936000 |
|
| 8000000 |
8064000 |
8128000 |
8192000 |
|||||||||
Many other frequencies can be synthesized to order, contact us to discuss your requirements.
![]() |
FarSync T4E Line Status Utility |
Externally sourced clocks
External clocks received from a serial port and used to a drive serial communications port can be any frequency up to 1000KHz.
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 T4E supports a subset of the CTBus (H.100) interface to enable synchronisation of serial ports(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
PC / Server PCI and PCI-X Compatibility
The FarSync T4E card is suitable for systems with a PCI or PCI-X bus, covering single processor systems, multi-processor systems and processors featuring HyperThreading technology. The card is PCI revision 2.2 compliant with support for both 3.3 and 5 volt signaling, the power for the card is taken from the 3.3 volt supply rail. The FarSync T4E card may be fitted in either 32-bit PCI bus slots or 64-bit PCI-X bus slots as this Universal PCI card 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 your System.
The FarSync T4E installs seamlessly under Linux kernel series 2.4 and 2.6 on both single and multi-core 32 and 64 bit systems. All the popular distributions are supported including Red Hat, SuSE, Slackware, Ubuntu, Mandriva, Debian and Fedora.
Installation is simple, the driver is dynamically loadable so a kernel rebuild is not required for the driver to be installed. The driver acts as a dynamically loadable module. 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 driver is supplied with source code.
The Raw Sockets API allows applications developed using the FarSync SDK to access the full feature set of the hardware, these include bit synchronous (HDLC framed) data, and transparent bitstream data in signal mode NRZ.
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.
The FarSync T4E installs easily under Windows Vista, Windows XP, Windows Server 2003 and Windows Server 2008 on single or multi-core 32 and 64 bit systems. A low level SDCI driver is installed with the optional installation of an NDIS (LAN) driver. The NDIS driver supports TCP/IP running over PPP with optional authentication by CHAP or PAP (RFC 1334) providing a standard point-to-point network interface. The drivers are signed by Microsoft for easy installation.
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.
The FarSync T4E enhanced SDCI API allows applications developed using the FarSync SDK to exactly control the type of data sent and received in bit synchronous (HDLC framed) data and transparent bitstream formats in NRZ signal mode.
The 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. The FarSync SDK is ordered separately from the FarSync 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.
Windows SDCI API
The SDCI API allows applications to exactly control the type of data sent and received in both bit synchronous data and transparent bitstream formats. The SDCI API manual in Adobe PDF format provides a comprehensive set of function call definitions and helpful advice on the best way to utilise the interface. The sample applications for HDLC and bitstream operation are written in C.
Synchronous data
The SDCI API has been extended to allow applications to exactly control the type of data sent and received in both bit synchronous (HDLC framed) data and transparent bitstream formats. The SDCI SDK contains everything a user needs to rapidly develop and test applications for such requirements as supporting specialist synchronous protocols or transparent data requirements such as Audio, MPEG Video T-DMB and DAB ETI. The unique clocking options are selectable and configurable from the API.
Asynchronous Data
To operate a port with asynchronous data under Windows the FarSync driver supports a subset of the standard Win32 COMM API as detailed in Microsoft's MSDN Documentation. This enables applications that currently interface to standard serial ports on Windows to be easily ported to use FarSync ports in asynchronous mode. As an alternative to using the Win32 COMM interface, SDCI clients also have the option of using much of the same code to support FarSync ports in either asynchronous or synchronous modes e.g. the same data transfer IOCTLs.
Sample Applications
A number of easy to follow sample applications are provided demonstrating the wide variety of features available with the card. This includes a kernel mode sample for those customers who require the ultimate performance. GUI based demonstration and test utilities are supplied capable of utilizing the wide range of features supported by the card.
Further information on the SDCI API
![]() |
Screenshot of SDCIDemo utility program that tests and demonstrates the FarSync T4E's capabilities |
Linux Raw Sockets API
The Linux API allows applications to send and receive HDLC format (bitsync) frames and also transparent bitstreams with the raw sockets based API. The sample application supplied with the Developers Toolkit demonstrates both modes of operation.
Data rates of up to 10 Mbits/s are supported, with all the ports individually selectable for speed, clocking direction and mode of operation (HDLC or Transparent). Frame sizes up to 32 Kbytes are supported in HDLC mode to allow support for a wide variety of specialist synchronous protocols. The transparent bit stream is suitable for transparent data requirements such as Audio, MPEG Video T-DMB and DAB ETI. The unique clocking options available with the FarSync T4E are selectable and configurable from the API. The API allow the full range of internal clock speeds to be selected. Asynchronous operation is not available from the Raw Sockets API.The source for the application and drivers is included, with the Linux API manual provided in Adobe PDF format. The driver is supported under kernel version 2.4 and 2.6 for both single CPU and SMP 32 and 64 bit machines.
This four port card uses 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 T4E card and splits out the four network interfaces into separate network connectors to provide support for EIA-530 (RS422) and RS232C. X.21, V.25 and RS449 are available through transition connectors. Details of the cables and converters available are listed in the order information. Crossover cables, sometimes referred to as null modem cables are available, they are also detailed in the table.
| Linux | |
| Distribution Support | Distributions by Red Hat, SuSE, Slackware, Mandriva, Ubuntu, Debian, Fedora and more. |
| Kernel Support | All sub versions of kernel releases from 2.4 and 2.6. |
| 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 XP, Windows Vista, Windows Server 2003, Windows Server 2008 |
| 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 |
| FarSync SDK - Developers Toolkit | |
| API reference manuals | Windows SDCI user manual, Linux Raw Sockets user manual |
| Sample programs | Sample applications supplied that use the SDCI and Raw Sockets APIs and card performance and function test applications |
| Source code | Sample C applications and Linux drivers source code supplied |
| Customer Support | We provide free email and telephone assistance to the application developer using the API as part of the package provided when the FarSync SDK is purchased. |
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 | X21, RS530, RS449: up to 8.192 Mbits/s internal clocked, 10 Mbits/s externally clocked, |
| 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 | 60 Mbits/s |
| Line signal modes | NRZ |
| 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 8.192 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 8.192MHz. 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. |
| 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 | The T4E 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. |
| RoHS Compliance | Yes |
| Cables | Cables are ordered separately, see the Cables section for details |
| Warranty | 5 years |
Microsoft, Windows, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.
All trademarks and registered trademarks are acknowledged.
Changes are periodically made to the information herein; these changes will be incorporated into new editions of the publication. FarSite Communications may make improvements and/or changes in the products and/or programs described in this publication at any time.
Last updated: 26-Nov-2008