the UL1076 document. - DSX Access Systems, Inc.

DSX-RMS1076Redundant Monitoring SystemUL 1076 Installation ManualAugust 2009Part # DSX-RMS1076 Manual Rev ADSX Access Systems, Inc. 10731 Rockwall Road Dallas, Texas 75238888-419-8353 Sales, Shipping and Accounting 800-346-5288 Technical Support214-553-6140 Phone www.dsxinc.com 214-553-0689 FAXDSX-RMS1076 12/09

ComplianceYou must consult your local fire codes before installing any locking device on doors, gates, or barriers.A construction and fire approval permit may be required before installing any equipment. Call yourlocal Fire Marshall for building code requirements in your area. For UL installations, you must installthe DSX System according to the UL Installation Manual and in accordance with the National ElectricCode, ANSI / NFPA 70 regulations and recommendations for US Installations. Canadian installationsmust be in accordance with the Canadian Electric Code C22.1.The DSX-1022, DSX-1040CDM, DSX-1040PDM, DSX-1042, DSX-1043, DSX-1044, DSX-CKI-C,DSXCKI-K, DSX-DP485 and DSX-FRB8 have been tested and found to conform to the requirementsof UL 294.The DSX-1022, DSX-1040CDM, DSX-1040PDM, DSX-1042, DSX-1043, DSX-1044, DSX-1040-PE-B,DSXMCI, DSX-LAN, DSX-SPS and DSX-2PC have been tested and found to conform to therequirements of UL 1076.Camera and DVR integration was not tested by UL.

Table of Contents1076 and High Availability OverviewsUL-1076 Requirements ..................................................................................................................... 3High Availability of Communications through DSX-RMS1076 Redundant Monitoring System.......... 5High Availability of DataBase using SQL Server 2005 Fail Over Clustering...................................... 6How Failover Clustering Works ......................................................................................................... 7Client Connections and SQL Server 2005 Virtual Server.................................................................. 7DSX-RMS1076 Typical Application................................................................................................... 8DSX-RMS1076 and SQL ConfigurationExample of Clustered SQL Servers................................................................................................... 9Important Configuration Facts........................................................................................................... 9Create a File Share on the Virtual Server.......................................................................................... 10Install WinDSX SQL into the File Share ............................................................................................ 11Configure SQL 2005.......................................................................................................................... 12Loading WinDSXSQL on Primary Comm Server............................................................................... 15Loading WinDSXSQL on Backup Comm Server............................................................................... 15Configuring WinDSX on Backup Comm Server ................................................................................ 16DSX Serial Port Switcher and DSX-MCI connectionsDSX Serial Port Switcher .................................................................................................................. 17DSX-SPS .......................................................................................................................................... 17DSX-SPST ........................................................................................................................................ 17DSX-2PC........................................................................................................................................... 17DSX Serial Port Switcher Typical Application drawing ...................................................................... 18DSX Serial Port Switcher Wiring Diagram......................................................................................... 19DSX-MCI Master Communications Interface module........................................................................ 203

UL-1076 RequirementsBasic Requirements1) Data Processing equipment and officeappliance and business equipment usedas central supervisory station equipmentshall comply with:A) The Standard for OfficeAppliances and BusinessEquipment, UL114B) The Standard for Information-Processing and BusinessEquipment, UL478 orC) The Standard for InformationTechnology Equipment, UL19502) The minimum PC Requirements are asfollows:SQL ServersA) Microsoft Server 2003B) SQL Server 2005 Enterprise Sp3C) Pentium 4 - 3GHzD) 1 G MemoryE) Dell Power Vault 220F) 20 Gig disk storage spaceComm ServersA) Microsoft XP SP2 / VistaBusiness Sp1G) Pentium 4 - 3GHzH) 1 G Memory3) The system shall utilize supply linetransient protection complying with theStandard for Transient Voltage SurgeSuppressors, UL1449 with a maximummarked rating of 330V.4) The system shall utilize signal linetransient protection complying with theStandard for Protectors of DataCommunications and Fire AlarmCircuits, UL 497B, with a maximummarked rating of 50V.5) Modem and Telco communicationsshould not be used for UL Installations.6) The DSX Communications Servers andall other PC related equipment shall beinstalled in a temperature controlledenvironment. The TemperatureControlled Environment must bemaintained between 13-35C (55-95 F)by the HVAC System. The HVACSystem must have 24 hours of standbypower. The Standby Power System forthe HVAC System may be supplied byan Engine Driven Generator alone. Astandby battery in not required to beused.7) All receiving equipment shall becompletely duplicated with provision forswitchover to the backup system within30 seconds. The backup system shall befully operational within 6 minutes of theloss of the primary system. This allows30 seconds for the backup system to befully energized and connected tonecessary communication lines andother devices, followed by 51/2 minutesfor the system to boot up, conductmemory tests, file system check,security verifications and prepare for fullsystem operation. The Backup computershall have the capabilities of thePrimary, such as memory, speed andthe like.8) There will be a minimum of one ULListed Reports Printer.9) Failure of the Main Computer System,hard disk, and alarm monitor shall resultin switchover to the backup system andshall be indicated by an audible orobvious visual indication.10) A Fault Tolerant System may be used inplace of complete duplication of thesystem if every component in the fault4

tolerant system, including the softwareand the power supply, is duplicated.11) In addition to the main power supply andsecondary power supply that arerequired to be provided at the centralsupervisory station, the system shall beprovided with an uninterruptible powersupply (UPS) with sufficient capacity tooperate the computer equipment for aminimum of 15 minutes. If more than 15minutes is required for the secondarypower supply to supply the UPS inputpower, the UPS shall be capable ofproviding input power for at least thatamount of time.12) The UPS shall comply with the Standardfor Uninterruptible Power SupplyEquipment, UL 1778, or the Standard forFire Protective Signaling Devices, UL1481.13) There shall be a means fordisconnecting the input to the UPS whilemaintaining continuity of power to theautomation system.14) The communications polling from theComm Server to the Location Mastercontroller cannot be less than onceevery two hundred seconds.15) Signal Priority must always be Alarmfirst, Trouble second, andSupplementary third.16) Abort Delay Time of Entry Exit Doorsshall not exceed 60 seconds.19) Protection for the system is intended tobe set from the monitoring equipmentonly.20) This application requires WinDSX SQLSoftware 4.8.73 or higher.SQL Server RequirementsThis product requires advanced knowledge ofMicrosoft Server 2003 and Microsoft SQLServer 2005 . It is the responsibility of youthe Dealer, or your customer the End User, tohave the personnel or access to the personnelthat are qualified to Install, Configure, andMaintain Microsoft SQL Server in a clusteredenvironment. DSX provides documentation thatwill assist in creating and configuring theMicrosoft SQL Server database required bythe WinDSX SQL software.DSX tech support CANNOT provide support forMicrosoft SQL Server in a cluster. You musthave someone on hand that can provide theSQL Server and networking expertise that willbe required. You will not be able to just “Figure ItOut When You Get There”. SQL Server in acluster is complicated; you cannot just wing itand expect the system to perform properly. Ifyou do not have someone on staff with thisknowledge it is strongly recommended that youpay someone to help you.17) The number of Monitored Inputs cannotexceed 1000 per location.18) Any Communications Failure shall betreated as a compromise of theStandard Line Security of the proprietaryburglar alarm system.5

High Availability through DSX-RMS1076Redundant Monitoring SystemCommunications OverviewThe DSX-RMS1076 Redundant MonitoringSystem provides continued availability ofSystem Communications and Control throughthe implementation of Primary and BackupCommunication Server PCs. Available only withWinDSX SQL the Hot-Swap Supervisorprogram runs on the Backup Comm Server PCand monitors the Primary Comm Server. Whenthe Primary fails all communications areredirected to the Backup (Redundant) CommServer.LAN connected locations are transparentlytransferred to the Backup Server and with theuse of a DSX-SPS Serial Port Switcher alldirect serial port connected Locations are alsoswitched automatically. WinDSX SQLWorkstations automatically switch to theBackup Server and continually display whichComm Server they are talking to. This featurerequires the purchase of the Hot Swap CommServer software and optionally the DSX-SPSSerial Port Switcher.Both Comm Servers are defined in the system aseither the Primary or Backup Comm Server andboth PCs have static TCP/IP addresses. BothPCs are running at all times. The Backup CommServer PC runs the Hot Swap Supervisorsoftware. The Supervisor Software polls thePrimary Comm Server. Once the polls have failedfor a predetermined amount of time theSupervisor Program starts an instance of CommServer on the Backup PC. The SupervisorSoftware also initiates any hardware switch overthat needs to take place (direct connects) bysending the appropriate commands out a serialport to the DSX-SPS Serial Port Switcher.The Workstation program on all PCs inthe system will automatically switch to theBackup Comm Server when the PrimaryComm Server fails. The Workstationprogram has a real time status displaythat shows which Comm Server is online.The Hot Swap Supervisor Software has aStop button that allows the BackupComm Server to be shut down, thePrimary Comm Server to be restarted,and the serial port connectedcommunications to be returned to thePrimary Comm Server.LAN connected Location MasterControllers must have a Dynamic IPMode connection that automaticallycommunicate with the Backup CommServer PC.Each DSX-SPS will accommodate theswitching of up to 20 serial ports from thePrimary Comm Server to the BackupComm Server. More than one SPS canbe used where more than 20 serial portsare required.Requirements1. DSX-RMS1076 only works with WinDSXSQL.2. Backup Comm Server must have 1 moreserial port than what is required for the PrimaryComm Server when switching communicationsto direct serial port connected locations.3. The shared WinDSX SQL folder must be onthe SQL Virtual Server.4. The Primary and Backup Comm Server PCsboth require Static TCP/IP addresses.5. LAN modules must be programmed forDynamic communications so that they canrespond to both the Primary and BackupComm Servers.6. The Hot Swap Comm Server program isloaded on the Backup Comm Server PC.7. The USB Key and Keymon are also run onthe Backup Comm Server.6

High Availability of DataBaseusing SQL Server 2005 Failover ClusteringFailover Clustering OverviewContinuous uptime in a production environmentis becoming a common security requirement.This information describes Microsoft® SQLServer 2005 failover clustering, one methodof creating high availability. Failover clusteringis available only in SQL Server 2005 EnterpriseEdition.Failover clustering is a process in which theoperating system and SQL Server 2005 worktogether to provide availability in the event ofan application failure, hardware failure, oroperating-system error. Failover clusteringprovides hardware redundancy through aconfiguration in which mission critical resourcesare transferred from a failing machine to anequally configured server automatically.Failover clustering also allows systemmaintenance to be performed on one computerwhile another computer (node) does the work.This benefit can also ensure that systemdowntime due to normal maintenance isminimized.The goal of failover clustering is to provide highavailability for an overall solution thataccommodates backups, redundancy, andperformance. If software and/or hardwareproblems occur, failover clustering can enablea production environment to stay up andrunning.7

How Failover Clustering WorksThe clustered nodes use a heartbeat (seediagram on previous page) to check whethereach node is alive, at both the operatingsystem and SQL Server level. At the operatingsystem level, the nodes in the cluster competefor the resources of the cluster. The primarynode reserves the resource every 3 seconds,and the competing node every 5 seconds. Theprocess lasts for 25 seconds and then startsover again. For example, if the node owningthe instance fails due to a problem (network,disk, and so on), at second 19, the competingnode detects it at the 20-second mark, and if itis determined that the primary node no longerhas control, the competing node takes over theresource.From a SQL Server perspective, the nodehosting the SQL Server resource does aLooks-Alive check every 5 seconds. This is alightweight check to see whether the service isrunning and may succeed even if the instanceof SQL Server is not operational. The IsAlivecheck is more thorough and involves running aSELECT @@SERVERNAME Transact SQLquery against the server to determine whetherthe server itself is available to respond torequests; it does not guarantee that the userdatabases are up. If this query fails, the IsAlivecheck retries five times and then attempts toreconnect to the instance of SQL Server. If allfive retries fail, the SQL Server resource fails.Depending on the failover thresholdconfiguration of the SQL Server resource,Windows Clustering will attempt to eitherrestart the resource on the same node or failover to another available node. The executionof the query tolerates a few errors, such aslicensing issues or having a paused instance ofSQL Server, but ultimately fails if its thresholdis exceeded.Virtual Server will take a short time (probablyseconds). After the service is started and themaster database is online, the SQL Serverresource is considered to be up. Now the userdatabases will go through the normal recoveryprocess, which means that any completedtransactions in the transaction log are rolledforward, and any incomplete transactions arerolled back. The length of the recovery processdepends on how much activity must be rolledforward or rolled back upon startup.Client Connections and SQL Server2005 Virtual ServersWinDSX SQL connects to a SQL Server 2005Virtual Server with the SQL Server Name or IPaddress of the SQL Server 2005 Virtual Server.The Cluster name, the Cluster IP address, oreven the individual node names are not usedby the connections. From a client or applicationperspective, it does not need to worry aboutwhich node owns the resources, becauseconnecting to the SQL Server 2005 VirtualServer appears as a normal SQL Server.During the failover process, any activeconnections are broken. WinDSX SQL checksto see whether the connection exists, and ifnot, reconnects.During the fail over from one node to another,Windows clustering starts the SQL Serverservice for that instance on the new node, andgoes through the recovery process to start thedatabases. The fail over of the SQL Server8

DSX-RMS1076Typical ApplicationThis drawing shows the typicaldeployment of the DSX-RMS1076Redundant Monitoring System. Thisapplication depicts two Clustered SQLServer PCs and two Comm Server PCs.The Clustered SQL Servers provide highavailability to the DataBase for bothComm Servers and all Client PCs.The Hot Swap Comm Servers providehigh availability to systemcommunications and control betweensystem controllers and all Client PCs.LocationOneControllersFileServerDSX-LANModulesLocationTwoControllersBackupFile ServerCommunications to the LAN connectedcontrollers is seamlessly switched fromone Comm Server to the other.Communication to the direct connectedcontrollers is handled by the DSX-SerialPort Switcher.PrimaryComm ServerCommPortsBackupComm ServerNot requiredfor LANConnectedLocationsDSX-SPSLocationThreeControllersLocationFourControllers9

Example of Clustered SQL ServersImportant Configuration FactsDSX configured and tested Clustered SQLServers in the following manner. Listed belowis the equipment used and the configuration.PCs - 3 GHZ with 1G of RAM OS – Windows Server 2003 and MS SQLServer 2005 Enterprise. Dell Power Vault 220 shared drive array.The Power Vault can handle up to 14 drivesbut you lose 1 slot when you cluster the array.The Power Vault has two drives that aremirrored for the quorum files that the Clusteradministrator uses. It also has 3 drives that areconfigured Raid 5 for the SQL server data files.This raid drive also has our file share resourceso that when the SQL server fails over so doesour shared folder. You could also have another3 drives for the SQL transaction logs if youwanted. There are several hotswap drives forfailover redundancy. Each PC has an LSI MegaRaid card thattalks to the PowerVault controller. You couldalso use a Perc Raid controller from Dell. Theimportant thing with these cards is that they areCluster aware and cluster capable. When youconfigure the cards they must have a uniqueLUN so one card is LUN 6 and the other cardis LUN 7. WinDSX is not compatible withWindows 95, Windows 98, Windows ME,or Windows XP Home Edition, Linux, orthe MAC operating systems. WinDSX SQL must use theEnterprise Edition of SQL Server. When using Windows XP turn offSimple File Sharing. You must have Administrator Rightsto properly install the WinDSX software. To run the programs, the User musthave Full Control over the local folderwhere the WinDSX software is installed,Full Control over the shared resource(Database Path) folder, Full Control overtheir Temp folders, and Read rights onthe local System32 folder underWindows. UNC (Universal Naming Convention– ie \\FileServer\WinDSX ) must beused for the database path. The Comm Server must have a staticTCP/IP address. The Workstations canbe DHCP.\\\ Both PC’s run the cluster administrationprogram and are capable of taking control ofthe cluster. We are using SQL server in anActive/Passive setup. Since this is a standalone system both PC’s are domain controllersand run Active Directory as well as DNSservers. The Heartbeat is facilitated by using asecond Network card in both PCs connectedtogether via a network HUB.10

DSX-SPS Create Serial a File Port Share Switcher &on Two the Port Virtual Controller ServerAt this point you have the two SQL ServersClustered together and ready to start withthe WinDSX specific configuration.First create a file share on the virtual serverthat was used for the SQL Server DataFiles.1. Open Windows Explorer and create afolder on a shared disk that you want toshare out for users.2. Assign the appropriate NTFS file levelpermissions on the folder. Make sure thatthe account used to start the Cluster Servicehas at least READ rights to the folder.Note Do not share the folder in WindowsExplorer as you normally would for a fileshare. If you do not grant the Clusteraccount the appropriate permissions orshare the folder through Windows Explorer,it may cause the cluster file share to fail.This also includes any administrative sharesthat already exist, you do not want to createshares for the root of the drive (Q$) forexample.3. Start Cluster Administrator(CluAdmin.exe).4. Select a group that has an existing IPAddress and Network Name resources. If youdo not have these resources created, you willneed to complete this before continuing. Foradditional information, see the article numberbelow in the Microsoft Knowledge Base:257932(http://support.microsoft.com/kb/257932/)Using Microsoft Cluster Server to create avirtual server.5. Right-click, and select New, thenResource.6. Fill in an administrative name anddescription for the resource. From the11Resource Type pull down, select "FileShare", click Next.Note This is the name that will be displayedin Cluster Administrator and is only used foradministrative purposes. This is not theshare name that users will connect to, givethe resource a name that will be easy toidentify and manage.7. Select the nodes that you want to bepossible owners of the resource. Click Nextto leave all nodes as possible owners.Note Possible Owners defines whether aresource is ever able to failover to a specificnode. Use extreme caution in definingPossible Owners because defining apossible owner for a single resource willaffect the failover for the entire group.8. Select a Network Name and Physical Diskresource that the file share will be dependenton.Note Dependencies serve two functions.a. They define the bindings for a resource. Youwant the file share to be dependent on theNetwork Name resource that clients are goingto use when connecting to the file share. TheIP Address resource that the Network Nameresource is dependent upon is the IP Addressthat will be used when connecting to this share.You never want a file share resource to bedependent on the "Cluster Name" resource.b. They define the start order for a resource.You want to make sure that the network namethat the share is going to be created under andthe physical disk where the folder resides thatis going to be shared are online and availablebefore attempting to bring the File Shareonline.When creating a dependency 'Tree' it is best tokeep it as simple as possible. A file shareresource should always be dependent on aNetwork Name that the clients will use toconnect to this share and Physical diskresource where the folder is located. ThePhysical Disk resource should never be

dependent on anything. The Network Nameresource should be dependent on a IP Addressresource which the virtual server will beassociated with. The IP Address resourceshould not be dependent on anything. See thefollowing article for additional information:171791(http://support.microsoft.com/kb/171791/) Creating dependencies in MicrosoftCluster Server)9. On the File Share Parameters screen fill inthe following information and click Finish:a. The "Share Name" is the name of the sharethat will be created for the UNC when clientsconnect. This needs to be a valid NetBIOSname, and is recommended to be a valid URLname as well.b. The "Path" is the full path on the localnode to the shared disk where the folder islocated. For example: T:\Users.c. The "Comment" is the information aboutthe share that will appear when a clientbrowses the share.10. By default, when resources are created,they are in an offline state. The following stepsare a best practice. Follow them to isolate theeffect of the resource failure on otherproduction resources. This will help until theresource is ready to be brought into productionfor users.Install WinDSX in File ShareBefore Installing the Software in the VirtualServer File Share you must login as a user withfull administrator rights. Make sure that theTemp and TMP settings are pointed to anactual directory. This is found in ControlPanel/System/Environment.1. To load the software, place the WinDSX CDin the CD-ROM Drive. Select “My Computer”on the desktop then right click on the CD-ROMDrive and select explore. Navigate to the InstallDirectory. Open the Install Directory anddouble click on Setup.exe. Follow theprompts and allow setup to install the softwareinto the WinDSX directory on the file share thatwe just created.2. After loading the software be sure and runthe Database program (DB.EXE) first from thedirectory where the software was just loaded.After starting the database program for the firsttime, set the DataBase Path to the file share onthe virtual server. Also be sure to assign thePC a unique Workstation Name and Numberother than Workstation 1 and #1. The defaultuser name and the default password aremaster - both entered in lower case.a. Right-click the resource, and then clickProperties.b. Click the Advanced tab, click to select theDo not restart button, and then click OK.c. Bring the resource online. Make sure that itfunctions correctly.d. After you confirm that the resource functionscorrectly, and you are ready to bring it intoproduction, take the resource offline. Then,click to select the Restart button.e. Bring the resource online.12

Configure SQL 2005Use these instructions for setting up WinDSXon a Microsoft SQL Server 2005.2. Using the Management Studio create anew database called AcsData and save. Setthe initial size to be 100 Meg. Turn on theAutomatic File Growth and set the growth tomegabytes and 1 Meg. Select unrestricted filegrowth.This product requires advanced knowledge ofMicrosoft SQL Server and Networks. Thisproduct requires advanced configuration. TheDealer or End User must have a Microsoft SQLServer Administrator to install, configure, andmaintain the SQL Server on site.1. Using the Management Studio, right clickon the Name of the Server and selectProperties. Make the following settings.3. Using the Management Studio create anew database called AcsLog. Set the initial sizeto be 200 Meg. Turn on the Automatic FileGrowth and set the growth to By Percent andset the percent to 10. Select unrestricted filegrowth.Set for Windows Authentication13

4. From the Management Studio right click onAcsData and select New Query.7. From the Management Studio right click onAcsLog and select New Query.5. Next Select File/Open and navigate to thevirtual server directory where you installed theWinDSX SQL software. If you have alreadyattempted to run the WinDSX databaseprogram you will find a sub directory nameMdbStruc. Inside this directory you will find afile called SqlDb.sql. If you do not see the subdirectory then we need to run the DBSQL.exefile and then cancel at the login screen. Nowopen the SQLDB.sql file with the queryanalyzer.6. Once the file has been loaded click onExecute Script in the tool bar. This will instructthe Query Analyzer to run the script. The scriptwill create the structures of the AcsDatadatabase.8. Next Select File/Open and navigate to thevirtual server directory where you installed theWinDSX SQL software. In that directory youwill find a sub directory name MdbStruc. Insidethis directory you will find a file calledSqlLog.sql. Open the SqlLog.sql file with thequery analyzer.9. Once the file has been loaded click onExecute Script in the tool bar. This will instructthe Query Analyzer to run the script. The scriptwill create the structures of the AcsLogdatabase.10. From the Management Studio selectSecurity/Logins. Right click and select NewLogin.14

11. Provide a Name that you wish to use forlogging into the SQL server from theworkstations. Select AcsData as the defaultdatabase.13. The first time that you run the DbSql.exeprogram there will be a short delay and it willpresent a SQL login screen. You enter theEXACT name of the SQL Server. Once thisdata is entered successfully the system willstore it and you will not need to login again.This will need to be done at each Workstation.Note /// WinDSX SQL Version 4.7 and higherrequires the Software Key Monitor program(KeyMon.exe) and the USB Software Key to beinstalled on any PC in the System but in thisapplication it must be on the Backup Comm.Server.12. Select User Mapping and assign thefollowing databases to the Login and set theappropriate permissions as below.Note/// For Windows Authentication or NamedPipes select Windows Authentication. Thisrequires more setup in Windows and AD. Whensetting up the Client PCs the first timeDBSQL.exe is started it will launch SQLSetup.Enter the Name of the SQL Server. Do notenter a User Name or Password. Rights andpermissions must be given to the user in AD.This will be done on all PCs the first time theprogram is run.15

Loading WinDSX onPrimary Comm ServerLoading WinDSX onBackup Comm ServerBefore Installing the Software you must loginas a user with full administrator rights. Makesure that the Temp and TMP settings arepointed to an actual directory. This is found inControl Panel/System/Environment.1. To load the software, place the WinDSX CDin the CD-ROM Drive. Select “My Computer”on the desktop then right click on the CD-ROMDrive and select explore. Navigate to the InstallDirectory. Open the Install Directory anddouble click on Setup.exe. Follow theprompts and allow setup to install the softwareinto the local hard drive of this pc.2. After loading the software be sure and runthe Database program (DBSQL.EXE) first fromthe directory where the software was justloaded. After starting the database program forthe first time, set the DataBase Path on eachPC to the file share created in step 1. Also besure to assign the PC a unique WorkstationName and Number other than Workstation 1and #1. The default user name and the defaultpassword are master - both entered in lowercase.Before Installing the Software you must loginas a user with full administrator rights. Makesure that the Temp and TMP settings arepointed to an actual directory. This is found inControl Panel/System/Environment.1. To load the software, place the WinDSX CDin the CD-ROM Drive. Select “My Computer”on the desktop then right click on the CD-ROMDrive and select explore. Navigate to the InstallDirectory. Open the Install Directory anddouble click on Setup.exe. Follow theprompts and allow setup to install the softwareinto the local hard drive of this pc.2. After loading the software be sure and runthe Database program (DBSQL.EXE) first fromthe directory where the software was justloaded. After starting the database program forthe first time, set the DataBase Path on eachPC to the file share created in step 1. Also besure to assign the PC a unique WorkstationName and Number other than Workstation 1and #1. The default user name and the defaultpassword are master - both entered in lowercase.16

Configuring WinDSX onBackup Comm ServerOn the backup Comm Server we need to runDBSql.exe from the local hard drive and enterthe SQL Server Login and password. When theWinDSX Login appears select cancel to close.1. Load the USB Key – Hasp Driver –Hdd32.exe located in the WinDSX SQLfolder on the Backup Comm Server.After the driver has been loaded plug theUSB Key into an available USB port onthe Backup Comm Server.2. Run the Keymon.exe program located inthe WinDSX SQL folder on the BackupComm Server.3. Copy the HotSwap.msi installation filefrom the \Utilities folder located on theWinDSXSQL CD to the WinDSXSQLfolder on the Backup Comm Server andinstall it into that same folder.C. On the CommunicationsServer Tab enter the “TCP/IPAddress” of this Backup CommServer PC.D. Close and restart the program.6. Start the HotSwap.exe program in theWinDSX SQL folder on the BackupComm. Server by double clicking on it.A. Close the program.B. In the WinDSX SQL folderthere will now be aHotSwapIni.txt file.C. Edit the file and change the P0to a P1 or P2 to reflect thecomm. Port that is connectedto the DSX-SPS.D. Save the file and close it andthen Restart the HotSwap.exeprogram.7. If using the DSX-SPS Serial PortSwitcher for direct connected locationsmake those connections now as shownin the next section.4. From the WinDSX SQL folder on theBackup Comm Server start the databaseprogram by double clicking onDBSql.exe. Login and selectSystem\Setup\DataBase Path and setthe SQL Server name and the path tothe shared folder. Close and restart theprogram.5. Start and Login to the WinDSX SQLDataBase program. SelectSystem\Setup\System Parameters andedit the Workstation Name.A. On the General Tab make surethe Workstation Name andNumber are unique to all otherWinDSX SQL softwareinstallations.B. On the Yes/No Options Tabselect “This PC is BackUpComm Server”17

DSX Serial Port SwitcherDSX-SPSThe DSX-SPS Serial Port Switcher is thehardware that physically switches serial portsfrom a Primary Comm Server to a Backup(Redundant) Comm Server. This occurs inconjunction with the Hot Swap Comm Serversoftware that monitors the Primary CommServer. When the Primary Comm Server fails,the Backup Comm Server computer takes over.The HotSwap program running on the BackupComm Server sends an ASCII string to theSPST module telling it to activate. The SPST inturn signals the individual 2PC modules toswitch from Primary to Secondary serial ports.When the HotSwap.exe program is instructedto return to the Primary Comm Server, theBackup Comm Server sends another string tothe SPST to deactivate, thereby switchingeverything back to the Primary serial ports. Upto 10 DSX-2PC modules can be used to switcha total of 20 serial ports per SPS.DSX-2PCThe DSX-2PC (Two Port Controller) is whereeach serial port from the Primary Comm Serverand the corresponding serial port from theBackup Comm Server connect. The output ofthe 2PC then goes to a direct connect DSXcontroller. This board physically switches thecircuits from one PC to the other. Each 2PCmodule can switch 2 serial ports. The 2PCrequires +12VDC@56ma for power and has 2trigger inputs that connect to the SPST module.Each port on the 2PC can be triggeredindependently.Power RequirementsDSX-SPST – 616ma @12VDCDSX-2PC – 56ma@12VDCDSX-MCI – 30ma@12VDCDSX-LAN – 300ma@12VDCDSX-SPSTThe DSX-SPST (Serial Port Switch Trigger)board is the power distribution and BackupComm Server monitoring board. It recieves+15VDC (Class II Power Limited) from theDSX-1040PDM board and distributes it to the2PC boards through 4 - 12VDC, 1A fusedoutputs. The SPST board has an RS-232 portthat connects to an extra port on the BackupComm Server. This is the port which sends the“activate” command. The SPST also has 4relay outputs that are used to “trigger” the 2PCboards when the “activate” command isreceived.18

DSX Serial Port SwitcherTypical Application19

DSX Serial Port SwitcherWiring DiagramConnectionsDB-25 DB-9TX -2 -3RX -3 -2Gnd -7 -5DTR-20 -420

DSX-MCI MasterCommunications InterfaceThe DSX-MCI is a protocol independentcommunications device that converts RS-232data to RS-485.Mounting and PowerThe DSX-MCI is powered by the battery backedup 12VDC fused power of the DSX Controller it isconnected to.The DSX-MCI should be located in the DSXController Enclosure. The module can be easilylocated in the bottom of the enclosure.DSX-MCI to DSX-1022 ControllerPC to Master RS-485 Terminalsof DSX-1022 Master ControllerUp to 4000 feet using2 twisted pair 22 AWGTX+TX-1022PC-MASTER RS-4855150494851504948RX+RX-TX+TX-RX+RX-1Up to 50 feetUsing 2 pairshielded 22 AWG6 7 8 92 3 4 5RXTXGNDFemale12VDC Source12V+GNDRS-232 RXRS-232 TXRS-485 RX-RS-485 RX+RS-485 TX-RS-485 TX+PC / MODEMMCIDSX-MCI to DSX-1040 Series ControllerPC to Master RS-232 Terminalsof DSX-1040 Master Controller6 7 8 9Up to 50 feet using22 AWG, 2 Pair ShieldedMCIPC / MODEMRS-485 TX+RS-485 TX-RS-485 RX+RS-485 RX-RS-232 TXRS-232 RXGND12V+1040 SeriesMasterTX RX GNDMASTER12V+12 3 4 5RXTXGNDUp to 4000 feet using2 twisted pair 22 AWG12VDC of Source12V+GNDRS-232 RXRS-232 TXRS-485 RX-RS-485 RX+RS-485 TX-RS-485 TX+PC / MODEMMCI21