Building Automation Knowledge Base

Issue When attempting to detach an AS, PCT continues to shown the server as being attached to the ES.   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool 1.x (PCT) Cause In PCT, when an AS is detached from its parent ES, the ES name still appears in the Added to parent column of the Servers list. Resolution Once the AS has been detached from an ES it can be added to another ES though Workstation using the following steps even though the "Added to parents" column shows otherwise.   To create a SmartX server In WorkStation, in the System Tree panel, select the Servers folder. On the File menu, point to New and then click Server . In the Create Object wizard, in the Name box, type a name for the SmartX server. In the Description box, type descriptive information about the SmartX server. Click Next . In the Configure IP/DNS Address and Port page, in the Address box, type the IP address or fully qualified domain name of the SmartX server. Notice If the SmartX server has been assigned a dynamic IP address, use the fully qualified domain name of the SmartX server instead of the IP address. In the Protocol box, select a protocol for the SmartX server. For more information, see EcoStruxure BMS Server Communication . In the Port box, enter a port number. Click Create. In the Log on dialog box, in the Password box, type the custom password if required. Click OK.   For more information, see Creating a SmartX Server

Issue How can a webpage be integrated into Vista graphic pages for a seamless transition between a graphic page and a 3rd party website such as: Static information, such as a site webpage Device webpage (power meters, sensor, etc. Product Line TAC Vista Environment Vista Server 5.x.x Cause The Hyperlink database object in Vista can store a URL address. By linking to this Hyperlink object with a standard link in a Vista graphic page, standard components can be used and support common graphic pages for different sites and reusability. Note:  More complicated integration can be accomplished with javascript, but this requires custom components such as accessing web services such as weather.com data for actual display on your graphic page. Resolution Create a Hyperlink object in the Vista database for each page you want to make available. Use a link in the TGML graphic page to access this Hyperlink object. Clicking the link on your graphic page will display the webpage in the Vista Workstation window. Target Property The target property can be configured for Webstation display to control the window or frame the link is opened in. The options _top, _self, and _parent will be ignored in WebStation and treated as _blank, which will open a new tab or frame depending on your browser settings. If you specify a target frame you must match the exact syntax of the WebStation frame names from the following list: TAC_WebStation_header TAC_WebStation_left TAC_WebStation_contents TAC_WebStation_footer

Issue Extended Elevator control (Step by step instructions) Product Line TAC INET Environment I/NET Seven DPU Firmware 3.20 or above. (DPU7920 with 48k MIP or SCU1284) Cause Extended elevator control allows support up to 79 floors and easier programming methodology than the traditional method.  This has been added to I/NET Seven software and DPUs as detailed in the environment.  Resolution To use any of these features requires that the DPU be a 7920 w/ MIP board or the new SCU1284. 7910 and 7920 w/o MIP board will still work with the I/Net system but they cannot use these functions. The host prevents the download of these features to any DPU revision prior to 3.10.   Extended Elevator Control Setup Example This is based impart on basic prior knowledge of InetSeven Host software setup and configuration to include but not limited to Controller Station Parameters, Resident I/O, Point Extensions, Operations of Network Configuration, and Access Configurations (Doors, Tenants, Groups, Individuals and Personnel Schedules). Hardware required: DPU 7920 48k (The following control will only apply to the 7920 48k) Please follow these steps to configure extended elevator control. Resident I/O Editor Edit / Controller / Resident I/O – Add the following Internal DO Door Reader point Internal DI point for each Floor DO External DO point for each Floor button DI Note – Save Door in the Network Configuration editor. Controller Door Editor Edit / Controller / Door Editor Select Door to add Elevator Control Modify – check Elevator Control box Select “Message type” Alarm / Transaction Note – Ensure a Schedule (s) has been assigned to the Door reader point. Controller Elevator Parameter Edit / Controller / Elevator Add Elevator Extension to reader point. Add Floor parameters. Complete the following; Floor Index Selection Floor designation Button Enable (DO) Button Selection (DI) Note – When finished “STOP” Do not select floors, Select OK and Close. Network Configuration  Edit / Host Computer / Network Configuration. Penetrate down to the DPU (Door Read Point) with Elevator Control Penetrate one more level and SAVE all your floor extensions. Tenants Access / Tenants Select Tenant Locate Door Reader point – Remove “X” (Unselect). Place an “X” next to all floors that tenant will have access to – Select Ok At this time I would suggest performing a save function followed by an SLI and DPU restore. Individual Editor You are now ready to add individuals or assign individuals access to floors.

Issue 'Program interface does not match previously defined interface' when downloading/commissioning a Xenta 400/300 controller. NS, #59 Environment Vista System Plugin TAC Xenta Programmable Controllers LonMaker/NL220 Cause You get this error if you have 2 controllers that are using the same device template (XIF file) and one is system program version <3.5 and one is >3.5. Typically you will get this when you are replacing an older controller or adding a new controller to an older network. Controllers can share device template even if they have different applications as long as the are using the same SNVTs. Different types of Xenta controllers can also share the same XIF file. Resolution To fix the problem you have to make sure that the new controller you are adding (replacing) gets a new XIF file and it’s own template. Open the application form System plug-in by right clicking on controller and select configure-edit. To give the application a new XIF either add a “dummy” SNVT or go to device configuration and uncheck the tick box for “XIF header generated according to LonMark standard” Hit F12, select commands and generate. F12 again and save the application to the hard drive by selecting File-save as. In system plug-in, browse in the application that you just saved on the hard drive. Update TAC Network and TAC Database. If you are asked to resynchronize, do so. In Menta create a new application with just one PVR block in it. Go to the controller, connect a serial cable and download the small application that you just created. Go back to the system plug-in and download the controller. Commission in LonMaker.

Issue Using STR-350 Bypass button as On/Off button in LNS Network Product Line TAC Vista Environment Vista STR-350 STR-351 Cause The Bypass button will only toggle the output of the nvoOccManCmd if the input nviEffectOccup matches the current button value. Resolution The STR-350/351 Sensors allow you to configure the Bypass button as an ON/OFF button but if it is not setup correctly it can get stuck in a single position. If using an application specific controller, the effective occupancy of the controller should be routed back to the STR-350 and bound to the nviEffectOccup. If using a 3rd party controller that does not have a SNVT for the effective occupancy, follow the step below. If using a programmable Xenta controller the nvoOccManCmd coming from the STR-350 should be bound to the programmable controller that with some logic programmed to follow the toggle of the button. Then that signal should be sent back to the nviEffectOccup of the STR-350. For the application used in the Classic network, refer to the Using STR-350 Bypass button as On/Off button in Classic Network.

Issue Some things to look for when you get ID 0 errors when doing a Save to Database Product Line Andover Continuum Environment Continuum Database Cause There are several causes such as date and time settings, scan variables, IP addresses, etc. Some troubleshooting steps are listed below based on different possible causes. Resolution Confirm that the date has been set in the controller. Edit the scan system variable and put a description in the description field. Doing this will update the LastChanged attribute of the Scan system variable. Verify that an IP address has been configured in the controller. If you are saving a remote site back that is earlier than revision 1.52 you need to set an IP address in the remote controller. Verify that the CX controller is at least revision 1.5 Verify that the controller is not reset. In some rare cases we saw that you would have a problem if you created the CX controller while offline editing. The correction in this case was to go offline edit, delete the CX in Cyberstation, go online, recreate the CX and then do the save to database. If the controller you are saving back has to go through a firewall and the firewall has blocked the access to the other IP addresses of the other controllers this controller knows about. Port numbers 33487, 33440, and 33456 are blocked in a router. Specifically port number 33456 is used for the save to database functionality. Make sure Firewall programs are not blocking the network connections. Disable any firewall programs before doing a “Send to DB”. Create a debug file (Acc_Dump_Debug.txt). See the Infinity-to-Continuum Upgrade document. Look in the debug file and see where it failed and act accordingly. 

Issue Changing the MSDE SQL Server Sys Admin account password is not supported by the I/NET Seven DbCreate Utility. Users have been advised to uninstall and then reinstall MSDE to change the password. Product Line TAC INET Environment I/NET Seven MS SQL Server (MSDE) Cause Need to change password Resolution Use the Microsoft OSQL Utility to change the Sys Admin account (user name, SA). Developed for Course 2002 I/NET Seven Installation and Startup - MSDE SQL Server OSQL Utility; Rev. 1/4/2007, by: M. Myers, TAC-KSG How to change your INetDb SQL Server SA account password using the OSQL Utility: On the I/NET Seven host workstation computer, shut down I/NET Seven completely, including the I/NET Seven I/O Server. Open the command prompt window. Select Windows Start > Run. Type the command, cmd, in the Run window, Open the dialog entry space, and click on OK. Enter the text exactly as is between the quotations. Connect to the I/NET Seven MSDE instance using the sa account. At the operating system drive, command prompt (i.e. C:\>), type the following OSQL command and press ENTER: osql -U sa Enter the command text exactly as it appears, including a dash before the capital U, and the spaces after the l and the U. OSQL will reply with the following prompt: Password: At the Password: prompt, type in the current SQL Server sa account password, and press ENTER. If the log-on command is correct, OSQL will return a line prompt:1>. Type the following string command at the 1> line prompt and press ENTER: sp_password @old = ‘old password‘, @new = 'new password', @loginame = 'sa' Enter the old and new passwords and the SQL System Administrator account name, sa, in apostrophes. Be sure to type each space and comma in the command. OSQL will return a second line prompt: 2> Type the go command at the 2> line prompt and press ENTER: go OSQL will return the password changed message and the 1> line prompt: Password changed.1> To close OSQL, type Exit at the 1> prompt and press ENTER. The Command Prompt will appear: C:\>_ To close the Command Prompt window, type Exit at the command prompt and press ENTER.  

Issue Unable to use plug-ins to configure devices in LonMaker or NL220, even after installing the DRF kit. Product Line TAC Vista Environment LonMaker NL220 Device Plug-in Cause The DRF (Device Resource Files) kit is not installed before devices are added in Lonmaker or NL220 (and other tools) Resolution The DRF kit must be installed and properly registered in the PC before any devices are created. If you are in this situation you will need to remove all devices and the device templates and you need to start all over. It is therefore recommended that the DRF kit are installed before adding any device and that you create one device and test the plug-in to make sure that the DRF kit are properly registered before adding a number of devices into the database.

Issue How to find out the Continuum serial number if it cannot be seen on the key or software licensing is used? Environment Cyberstation Security Key, Dongle Software licensing Cause When upgrading features or version on a Continuum system the Serial Number is required by Order Entry / the factory to process the upgrade and generate the upgrade file. If using software licensing or the number is not on the workstation key, it can still be found using a separate application. Resolution Run the application "CyberKeyWriter2.exe" that can be found in the Program files \ Continuum directory on the workstation (or WebClient Server). The following screen will appear showing the serial number:

Issue Upgrading to a MicroNet 50 series, the  option is grayed out in VisiSat. VisiSat version 2.0 stencils held no information regarding the 50 series controllers. Product Line Satchwell MicroNet Environment VisiSat version 2.0 VisiSat version 2.1 Cause VisiSat 2.1 introduced the option to upgrade a MicroNet legacy controller (MN300, MN440, MN500, and MN620) to a 50 series type (MN350, MN450, MN550 and 650). When the original project was created in version 2.0 VisiSat or older, the option was grayed out. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Save the MicroNet *00 series controller's configuration to disk. Delete the controller. Drop a new MicroNet legacy controller onto the main page. Address the controller with the original address. Load the configuration saved in step 1. Now the option to upgrade is available.

Issue Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.) Windows Event log reveals the following error:   Product: Microsoft SQL Server 2005 Express Edition -- Error 28001. The sa password must meet SQL Server password policy requirements. For strong password guidelines, see Authentication Mode, in SQL Server Books Online. Product Line TAC Vista Environment Vista Server Microsoft SQL Server 2005 Express Edition Windows Server 2003 Cause When installing TAC Vista 5 on a 2003 Server you can get an error if the group policy require a certain complexity on the sa password. Resolution One possibility is to edit the group policy Go to Start > Run and type gpedit.msc In the Local Group Policy Editor, navigate to Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Account Policies > Password Policy Set Password must meet complexity requirements to Disabled.     The other option is to install the SQL 2005 Express SP3 yourself. It is downloadable from Microsoft. Remove the checkmark in "Hide Advanced Configuration" Set the instance to TACVISTA. Use the "custom" option in TAC Vista Server setup, and select the local SQL server.

Issue An "Internal Server Error 500" message appears when attempting to access a Niagara G3 ENC station via a web browser. Environment Niagara G3 ENC station Web browser Cause Typically, this issue is caused by the Module Content Filter Level in the ENC being set to "RUNTIME". In order for an ENC to host Web Services, the ENC needs to have the Module Content Filter Level set to "UI+RUNTIME". Resolution Use the Commissioning Wizard in the Platform Administration section of the ENC's Platform to set the Module Content Filter Level to "UI+RUNTIME". In some cases, the error message persists even after re-commissioning per the above instructions. To correct this problem, go to the Software Manager in the ENC's Platform, highlight all the modules that are marked "Up To Date", and re-install them.

Issue Sub Device unable to come online when added to an SSC Controller on a system. When the controller that is offline is selected the save option is not available. Product Line Access Expert Environment Access Expert in Cloud or Premise Installations Microsoft Windows 7, Windows 8, Server 2012, Server 2014 Cause The controller is not  configured correctly (MR50) The controllers IP address is incorrectly configured,  or is not saved or made active on the system. (MR 51E) Resolution To resolve this, the following steps need to be followed: Add the interface type to the SSC Configure the interface for DHCP, Static or MAC address (MR51e) Once complete, select Save or Save & Close to save to the controller If multiple devices are being added, follow previous steps 1-3 above then:  Open up the Live Monitoring Window to check the status of the controller If the devices show offline, Right Click on the controller and select Reboot The Live Monitoring Window will show what is actually being sent to the controller Once completed the status will change to reflect what state the controller is in If correct it will be Online (Green), if not check the configuration again

Issue A Network 8000 LNC-100 cannot communicate to LON devices under it even though all the devices can be accessed with WorkPlace Tech or a LON commissioning tool. Product Line TAC IA Series Environment NETWORK 8000 LNC-100 LON devices WorkPlace Tech Cause If the LON network is known to be good and otherwise functioning, this issue indicates a problem with the LON interface in the LNC-100. This is typically caused by accidentally attempting to commission the LNC-100 using LonMaker or other LON commissioning tool. Attempting to commission the LNC-100 will result in its LON interface being set into a network state called HARD - OFFLINE. Resolution The condition can be corrected using the Echelon NODEUTIL program to set the interface network to the required CONFIGURED - ONLINE state. NodeUtil can be downloaded from The Exchange Download Center. After downloading NodeUtil to your computer, open a command prompt window and launch NodeUtil in that window.  After launching NodeUtil, perform the following steps to correct the problem. Press the F key to execute the Find function.  This will browse the connected LON network for all attached LON devices.  In the list of found devices, the LNC-100 will be identified with the program id "C 1 11.0A". Press the G key to execute the Go To Device function.  Enter the device number of the LNC-100 (program ID "C 1 11.0A") as displayed in the list of discovered devices.  The device menu will then be displayed. Press the S key to display the status of the device.  Typically 17 lines of status information are displayed followed by the "Device Status" menu.  Press Y to clear the error status.  The "Device State" line will usually show a state of either Configured, Off-line or Hard, Off-line. Press the  M key to change the device mode and state. After selecting the M command, the list of mode options is displayed.   Press the S key to select the State menu. The list of State options will be displayed.  Press the C key to set the device to the Configured state. A status message will be displayed followed by the DEVICE prompt. Press the M key again to display the Mode options then press N to set the device into the OnLine mode. A status message will be displayed followed by the DEVICE prompt. Press the S key again and verify that the Device State is now Configured, On-line. Press the D key to display the domain address table of the LNC-100.  One or two lines of device domain address information will display.  If two domain addresses were defined in the SYS: SIM block of the device, two lines of information will display, otherwise only one line will display.  Verify that the address information (Subnet, Node and Domain ID) are as set in the SYS: SIM block. The data entered for Domain0, Subnet0 and Node0 will be displayed on the Index 0 line. The data entered for Domain1, Subnet1 and Node1 will be displayed on the Index 1 line. Press the E key to exit the Device level and press the E key a second time to exit the program.

Issue How to sound a buzzer when a Request To Exit (REX) button is pressed on a Continuum Access system? The inputs to a door are not defined as regular Infinity inputs so how can they be programmed by Plain English programming? Environment ACX57xx (ACX5740, ACX5720) and AC-1 IOU modules (AC-1, AC-1A, AC-1 Plus) Cause When engineering an access control project, there is sometimes the requirement to sound a buzzer or turn on a light when the door is unlocked, or when a Request To Exit button is pressed, as the input points used within the door object configuration are not defined as a regular Infinity Inputs, so how to achieve this functionality? Resolution To use a Request To Exit (REX) switch on any of the ACX controllers or AC1 Modules:  It has to be a supervised input wired with the appropriate resistors in one of the 6 standard configurations defined in the installation guides (All available on the Extranet). You can not use a simple digital input switch without resistors. Incorrect circuitry or missing resistors will result in a Trouble indication on the door. The REX input is not a regular Continuum input point as it is defined within the door configuration, as it is not a Infinity input point directly accessible from Plain English but can be read via the "ExitRequest" attribute of the door. To sound a buzzer from the from the door there are 3 options: Use the existing door output and slave a buzzer circuit from the output that drives the Magnetic lock, so will sound when the door unlocks. If you want the buzzer to sound when the REX button is pressed then use a button with a 2 pole switch (2 separate contacts): Wire one to the REX input with appropriate resistors. Wire the other switch to a spare Input Configure it as either a Digital input or a Supervised input with resistors. This point can be used in your PE programming to drive the buzzer output. The third option is to use a Plain English program to read the "ExitRequest" attribute of the door and turn on an output for a defined time. The ExitRequest attribute may only be on for a short period of time so the program must be constantly looking for this attribute to change as well as keeping the controller Scan time low.  

Issue Communication status between Continuum BACnet device can be verified by checking controller's CommStatus attribute in InfinityView(Infinity View / Infinity Path).    But how can I check the communication status of other 3rd party BACnet devices? Environment BCX4040 BACnet controllers B3xxx BACnet controllers. Continuum Workstations. Cause Having unstable BACnet  IP or MSTP connections and want to check the communication status of the target devices before read/write data from/to the them. Resolution Create a PE program in the our BCX (or B3) controller as below: '= = = = = = = = Line Checking    If BACnetDevices\BNet_2765\MyB3VAV System_Status = Operational then Goto Wait15Secs Line Wait15Secs    If TS > 15 then Goto Checking Line E    ' Do something to set off the alarm from the b3 controller.    Goto Wait15Secs '= = = = = = = =

Issue Network 8000 Ethernet networks experiencing the following symptoms should be upgraded: GCM panels reporting repeated off-line / on-line messages NIM lock-ups requiring power cycling to recover Loss of global data sharing with Network 8000 (RNET and SNET transmissions fail) Product Line TAC IA Series Environment Network 8000 GCM Ethernet NIM, part number GCM-ETH-001 Network 8000 GCM-86000 Series controller (GCM-86120, GCM-86110, LNC-100, SIM-CCN, SIM-MTECH, SIM-YORK, SIM-TRANE) 802.3U Ethernet (100 Mbps) or 802.3z gigabit Ethernet (1000 Mbps) backbone network Cause Ethernet NIM performance was enhanced in revision 11.2T. Resolution Upgrade all NIMs on the network to firmware revision 11.2T, with the single exception of any with revision 11.2P firmware. Click here to see Announcement 01-105 for more details. For details on the REVISED Flash clear procedure, see the NIM Networking and Configuration Guide, F-25955-4, Chapter 2, section titled "Special NIM Address Switch Functions". Click here to see the procedure. Please reference Verifying the current firmware revision of a Network 8000 GCM and if an upgrade kit is available regarding Network 8000 firmware, including current revisions and upgrade kit part numbers.

Issue Get "Error: Device type specified in MTA file is not what TAC Vista expected, Info: Download Application and Parameters"  when downloading to a Xenta controller from TAC Vista. Environment TAC Vista TAC Xenta 30x, 28x, 401 Cause The type of controller that you specify in the device specification in the Menta application have the be to exact type you are downloading to. So either there is a mismatch or there is another controller on the network with the address you are using. Resolution Right click and Edit the controller in TAC Vista Workstation. Log in to view the Menta application Check in Options > Device Specification that it is the right type. If not, change to the right type.

Issue Cannot commission an IC3 LON controller in LonMaker. It has become applicationless and the red service LED is flashing or is permanently lit.  Product Line Satchwell Sigma Environment Satchwell Sigma Controller IC3 IC LON FTT-10 NodeUtil Cause The Echelon chip has become 'locked' and requires resetting.  This can be caused by corrupted controller files, very high LON traffic (> 50% Bandwidth), or the controller has started from "start-up mode" or cold start.   Resolution The Echelon chip can be reset using NodeUtil.exe  .  This is a DOS-based program that can be loaded onto a laptop with an FTT-10 Echelon adaptor. A clean working set of controller files will be downloaded to the device. In the case of a flashing red LED - Download 'clean' files to the controller Start NodeUtil on the laptop and plug LON cable into the controller Reset controller (via onboard reset button) Activate the plug-in LON card service pin and the Neuron Id should appear on the laptop. Note: If further controller resets and service pin activations fail to generate the service pin echo then discard the plug-in card and replace with a new one. From the NodeUtil menu select 'R' and enter the Node Id number Confirm the reset of 3150 Node The service LED should stop flashing and the controller should now be 'Configured' that is not 'applicationless' In the red LED is permanently lit - Download 'clean' files to the controller, the Echelon chip will become locked again. Repeat the reset procedure using NodeUtil.exe, this will allow the controller to work, but the plug-in card will need to be replaced. Example of NodeUtil process; NODEUTIL> (H)elp with commands A -- (A)dd node to list. D -- Set the (D)omain of the network interface. E -- (E)xit this application and return to DOS. F -- (F)ind nodes in the current domain. G -- (G)o to node menu............. H -- (H)elp with commands. L -- Display node (L)ist. M -- Change node (M)ode or state. O -- Redirect (O)utput to a file. P -- Send a service (P)in message. R -- (R)eboot 3150 node. S -- Report node (S)tatus and statistics. T -- (T)ransceiver parameters. V -- Control (V)erbose modes. W -- (W)ink a node. Z -- Shell out to DOS. NODEUTIL> Received an ID message from node 2. Program ID is ICLON1a NODEUTIL> Received an ID message from node 2. NODEUTIL> (R)eboot 3150 node Enter node id for reboot (0-2) [2] :2 *** Neuron 3150: Rebooting will reset comm. params, node state on-chip EEPROM variables and buffer configuration Are you sure you really want to do this? (Y/[N]): Successfully rebooted node NODEUTIL> A second solution has been provided by a customer and could be considered if the above suggestions does not provide a solution. Alternative reset procedure provided by a customer is as follows: - 1. Removed the IC LON from both the LON and the Sigma network. 2. I used SCDU tool to re-node the ICLON to a random IP address, which I believe cleared the database and the files etc. 3. I removed the power form the ICLON and then removed the LON daughterboard card from the ICLON mainboard. 4. Re-instated power and re-installed the LON daughterboard card. 5. Connected with NODE Utility as per the product data-sheet below. And cleared the LON comms buffers as the suggested method. 6. Checked that the red constant service light ceased from the constant illumination. And witnessed that the Green LON heartbeat LED was operational. 7. Re-Node the ICLON to the original IP and check operation. * The Sigma IC-LON plug-in card can be purchased using the part number S-LON. The S-LON has been discontinued as of 29th December 2017 and it is now in the service period (limited quantities available for purchase). Refer to PA-00528 for details.

Issue What is the pin configuration for Modbus RTU when using a 9 pin comm port on a BCX controller. Environment BCX Modbus RTU Cause Connecting a BCX or CX controller to a Modbus RTU device. Resolution RS232 connection for a 9 pin BCX comm port.   BCX Comm 1 (9 Pin)            RJ 45 Connector @ Modbus device Pin 1 CXD        -->                 Pin 1 DTR Pin 7 RTS        -->                 Pin 2 CTS  Pin 4 DTR        -->                 Pin 3 CXD Pin 8 CTS        -->                 Pin 4 RTS Pin 5 GND       -->                 Pin 5 GND Pin 3 TD           -->                 Pin 6 RD Pin 6 DSR        -->                 Pin 7 DSR Pin 2 RD           -->                 Pin 8 TD