FarSync SDK (for Windows 10 [x64], Windows 8.1 [x64], Windows 7 [x64], Windows Vista [x64], Windows Server 2008 & 2012 [x64]) FarSite Communications Ltd (www.farsite.com) Release 6.3.0 25 Jun 18 ============================== CONTENTS 1. INTRODUCTION 2. INSTALLING THE HARDWARE AND DRIVERS 3. REQUIRED SERVICE PACKS 4. INTERNAL CLOCKING 4.1 Internal Clocking on V.11 (X.21) lines 4.2 Internal Clocking on V.24 (RS232C / X.21bis) lines 4.3 Internal Clocking on T1U 5. PORT IDENTIFICATION AND LEDS 5.1 FarSync T1U 5.2 FarSync T2U, T2Ue & T2Ee 5.3 FarSync T4U, T4Ue, T4E & T4E+ 5.4 FarSync TE1, TE1R & TE1e 5.5 FarSync Flex 6. LED STATUS (PCI cards) 7. ANOMALIES WITH LED OPERATION 8. VERSION INFORMATION 9 . KNOWN ISSUES 10. PORT CENTRIC AND DEVICE CENTRIC FLEX OPERATION 11. SUPPORT CONTACTS ============================== 1. INTRODUCTION The FarSync family is a range of PCI/PCMCIA cards that provides 1, 2 and 4 port adapters for synchronous data communications over lines with X.21 (V.11/RS-422), V.24 (X.21bis/RS-232-C), V.35, RS530/449 or E1 (G703/G704) interfaces. The family currently comprises of the following cards/devices: T4Ee a bus mastering 4-port PCI-Express card with frequency synthesizers T4E a bus mastering 4-port Universal PCI card with frequency synthesizers T4E+ a bus mastering 4-port Universal PCI card with frequency synthesizers (plus line termination and Manchester/Conditioned Diphase encoding support) TE1(R) a single port E1 Universal PCI card TE1e a single port E1 PCI-Express card incl. support for an external reference clock T1U a bus mastering single port Universal PCI card T2U a bus mastering 2-port Universal PCI card T2Ue a bus mastering 2-port PCI-Express card T2Ee a bus mastering 2-port Universal PCI card with frequency synthesizers (plus line termination and Manchester/Conditioned Diphase encoding support) T2U-PMC a bus mastering 2-port PMC card T4U a bus mastering 4-port Universal PCI card T4Ue a bus mastering 4-port PCI-Express card Flex a 1-port USB device Supported link speeds include: 1) 8Mbps for TxE and TxU cards using on-board or external clock sources. E2 data rates (8.448 Mbps) can be supported using an external clock. 10Mbps for T4E+ & T2Ue, using on-board or external clock sources. 2) 2.048 Mbps for the TE1 card. TE1 cards can either use the whole E1 bandwidth (un-channelised) or can use 1 or more timeslots, up to 31, to provide throughputs from 64 Kbps to 1984 Kbps in increments of 64 Kbps. 3) 2.048 Mbps for the Flex This release has been made to provide compatibility with FarSync Flex version 3 hardware. The new driver included in this release must be used with Flex V3 but is also backwards compatible with Flex V2. Every FarSync Flex is clearly labelled on the side. This label will contain the device serial number and the hardware version. For example U200/0001 V2 For a version 2 Flex U300/0001 V3 For a version 3 Flex 2. INSTALLING THE HARDWARE AND DRIVERS Install the hardware, drivers and SDK software/documentation as described in the install HTML file in the root directory of the SDK's release media. Ensure that you use the drivers from the same media as the SDK (rather than earlier ones) otherwise some of the SDK components may not be able to be installed. Once you have install the card and software you can test that the PC, card & cabling are operating as you require by using the sdcidemo utility available off the SDK's Utilties program menu. 3. REQUIRED SERVICE PACKS Windows 10 Windows Server 2012 - R2 Windows 8.1 Windows 7 - SP1 Windows Server 2008 - SP2 4. INTERNAL CLOCKING 4.1 Internal Clocking on V.11 (X.21) lines Internal clocking for V.11 lines generates the clock signal on pins 6 and 13. 4.2 Internal Clocking on V.24 (RS232C / X.21bis) lines Internal clocking for V.24 lines generates the clock signal on pins 15 and 17. 4.3 Internal Clocking on T1U Internal clocking is not available on the T1U. 5. PORT IDENTIFICATION AND LEDS 5.1 FarSync T1U, T1Ue The FarSync T1U is supplied with only one port connector, which is port A. Viewing the card on the vertical plane, the left hand LED is the status LED for the port. 5.2 FarSync T2U, T2Ue, T2Ee The FarSync T2U has a connector for each port. Port A is the one nearest the LED's. Viewing the card on the vertical plane, the left hand LED is the status LED for port A, and the other is for port B. 5.3 FarSync T4U, T4Ue, T4E & T4E+ There are 4 LEDs on these FarSync T-Series cards. They are located next to the connector for the cable. Port A is the top left LED (when viewed looking at the card on a vertical plan. Ports B to D are assigned in a clockwise fashion from Port A. 5.4 FarSync TE1, TE1R & TE1e The port's status LED is the top left LED (when viewed looking at the card on a verticle plane). The remaining LEDs, working clockwise are as follows: Loss of Signal (LOS) Alarm There is no signal detected. Alarm Indication Signal (AIS) Alarm There is no framing detected. Receive Remote Alarm (RRA) Alarm A signal indication has been received from the remote end. 5.5 FarSync Flex Please refer to the FarSync Flex Quick Start Guide for information regarding the device's LED operation. 6. LED STATUS (PCI cards) The status LEDs on the PCI cards are used to: # reflect the line status of each of the ports # identify which card (if any) is being configured When all LEDs are off, the driver has not been started (or has been stopped). If the LEDs are on without flashing, then the driver has been started, but no clock has been detected on the line. Or the line is not currently open (e.g. has been used to make or receive a RAS call). With a cable connected, if the LED flashes, then a clock has been detected (whether internal or external). If each of the LEDs flash out of phase then each port is generating/receiving a clock signal. If all LEDs flash in phase then this indicates that the card is currently being configured. 7. ANOMALIES WITH LED OPERATION It has been noted that in some cases, when there is an unterminated cable connected to the card (i.e. the cable is not connected to a network) the LEDs may flash out of phase - incorrectly indicating that a clock has been detected. Please only interpret the LEDs clock detection indication when the card is physically connected to your network. 8. VERSION INFORMATION This release (6.3.0) updates the FarSync Flex driver to provide compatibility with the FarSync Flex V3. Version 6.2.7 included the following fixes/enhancement(s): 1) Support for one-bit-insertion on FarSync Flex 2) New nrz_clk_rec encoding mode for FarSync Flex Version 6.2.6 included: 1) Support for T4Ee Version 6.2.1 included: 1) Flex V2 support including custom clock rates, encoded data (FM0, FM1, MAN and DMAN), RS485 (HDX/2-wire & FDX/4-wire) and Terminal Timing. 2) Custom Rate support for T2Ue, T2U-PMC, T2Ee, T4E(+) 3) New samples: fs485md (485 multidrop support), fswinclk (custom rate support) & fsserial (querying FarSync device serial number) Version 6.0.6 included: 1) T2Ee support including support for encoded data (FM0, FM1, Man and DMAN), RS485 (HDX/2-wire & FDX/4-wire) and Terminal Timing. Version 6.0.5 included: 1) LAPB/V.120 protocol support 2) G.704/ETI framing support (available in FarSync driver/API i.e. instead of requiring the use of the Encoder/Decoder usermode library) 3) Differential Manchester/Conditioned Diphase Encoding support for T4E+ 4) FsWinAPI support - see FsWinAPI User Guide 5) An example of how to interface to FarSync cards/devices from within LabVIEW. Please refer to the sample's ReadMe located in the LabVIEW folder on your SDK CD. 6) TE1e external reference clock support Version 5.7.4 included: 1) Support for the FarSync T4E+ which supports 10Mbps, line termination and Manchester encoding 2) Async support on the FarSync Flex 3) Extended monitoring support - including Internal, Passive and Peer modes 4) T-Series performance enhancements 5) RS530 support on TxU(e) and T4E cards - using the U530 cable 6) Encoder/Decoder enhancements • TE1 firmware updates inhibit unwanted G.704 Receive Remote Alarm, Framing Error and CRC Error reports in G.703 mode. • The Encoder/Decoder library includes improved synchronization and resynchronization logic. • The Encoder/Decoder sample programs are now provided as Visual Studio 6 and Visual Studio 2005 projects. • The Encoder/Decoder FrameRecv sample uses additional buffering to overcome Windows interrupt latency problems. Version 5.6.0 included: 1) RS485 support 2) NRZI clocking support This release also included support for the new Encoder/Decoder (user-mode) library - see the Bitstream Encoder Decoder User Guide for more information. Version 5.5.2 included: 1) Support for the FarSync T2Ue (PCI-Express card) Version 5.5.1 included: 1) FarSync Flex extended clocking support Version 5.5.0 included: 1) Single combined set of components to support for all FarSync cards Version 5.4.x included: 1) FarSync Flex external monitor support version 5.3.x included: 1) Support for the FarSync T4Ue (PCI-Express card) Version 5.2.x included the following enhancements made since Version 4.x.x : 1) Support for both x64 and X86 version of Windows (XP, Server 2003) 2) Support for Windows Vista (x64 & x86) 3) Support for FarSync Flex 9. KNOWN ISSUES a) FarSync Flex V3: Data reception stops after resuming from power save mode, i.e. sleep or hibernate. It is recommended that you disconnect the Flex before entering power save mode. b) When running multiple ports of a T4E(+) card at > 8Mb it is advisible to override the card's default DMA threshold value. This should be done by simply renaming the card's DMATHR registry entry (REG_DWORD) to be xDMATHR (you'll then be able to easily restore it later should you need to). This value is located under the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{E3056BE3-2149-47FA-81C3-2A46966658F4}\xxxx where is xxxx is the index of the required card instance. Ensure that no modifications are made to any other registry entries. Once you have applied this update, you should reboot the PC to enable the change to take effect. 10. PORT CENTRIC AND DEVICE CENTRIC FLEX OPERATION Every FarSync Flex has a unique serial number that Windows uses to identify a particular instance of the device. This allows devices to be swapped between USB ports on the same PC without any need to reinstall drivers etc. This default device-centric behaviour may be changed to be port-centric, so that any FarSync Flex may be plugged into the same USB port on a PC without the need to install drivers etc. To change the behaviour: a) Uninstall all FarSync Flex drivers/applications, b) Edit the registry, c) Reinstall FarSync Flex devices/applications. FarSite's fsclean utility is particularly useful for uninstalling all FarSync Flexes, including hidden (no longer attached) devices. Step b) requires you to use regedit to add a REG_BINARY value in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags called IgnoreHWSerNum1AFD0721 with a value of 01. After that change, each Flex plugged into a specific USB port will be seen by host software as being the same device instance. However, if you move a Flex from one port to another then it will be seen as a different instance of the device. 11. SUPPORT CONTACTS Support information and updates can be found on the FarSite web site at http://www.farsite.com For general support enquiries email or telephone +44 (0) 1256 330461 during normal UK office hours.