Building Automation Knowledge Base

Issue Straight S-Cable and angle (L-shaped) S-Cable difference Product Line EcoStruxure Building Operation Environment Automation Server Automation Server Power Supply Automation Server I/O Modules Cause The description in the datasheets / installation instructions may not be sufficient to understand the difference(s) between the two types of S-Cables. Resolution January 2013 Update - The straight connector S-Cable has been discontinued. Refer to Product Announcement PA-00238 for details. The straight S-Cable (part number SXWSCABLE10001) and the angle or L-shaped S-Cable (part number SXWSCABLE10002) works the same in terms of functionality. Both are 1.5 meters in length. The difference is whether the connectors is a straight out type or an angled type. This will probably affect the installation. See the images below Straight type Angle or L-shaped * Note: The straight S-Cable is currently not available and all existing and coming orders for straight S-cable (SXWSCABLE10001) will be replaced with the L-shaped S-cable (SXWSCABLE10002) until further notice. Refer to TPA-SBO-12-0004 01 for details.

Issue Controller Error Log shows error code 5128. Environment Error Log Error Code NetController BCX ACX Cause An Infinity Controller is dropping offline. Resolution Controller error code 5128 (0x00001408) is an indication that the controllers network comm buffer is out of memory.  Normally the network transceiver will shut down when this happens to protect the controller.  This is generally an indication that the controllers comm buffer is being overtaxed.  This can happen when there is a data storm present on the network. 

Issue Unifact Pro - Master and Slave controller ratio Unifact Pro - Number of controllers on a LAN Environment Unifact Pro Cause What is the Master to Slave controller ratio of Unifact Pro controllers on a LAN? What is the maximum number of Unifact Pro controllers on a LAN? Download here the Unifact Pro Datasheet Resolution There is 1 master to a maximum of 3 slaves. A single Unifact Pro LAN can support up to 80 controllers. Note: A S-Link sensor wired to the master can be shared by up to 3 slave controllers. If fan speed control is used then S-Link sensors cannot be used on the slaves.

Issue When copying any type of object or value in SmartStruxure the following error is given. Environment  Workstation Virtual Machine Cause This is a Windows error that results from multiple application trying to access the clipboard at the same time. This issue is common to a virtual machine environment. Resolution To prevent this error from occurring,  the settings of the virtual machine must be changed. These settings will be located in different location depending on the type of virtual machine software you have. The Shared clipboard feature needs to be set to disabled.

Issue Graphics updates are very slow, it takes over 1 minutes to load a graphic, Opening objects from Continuum Explorer is slow, sometimes it will failed to open an object if clicked too frequently. When using the BACnet path for objects on graphics it is fast. Product Line Andover Continuum Environment b4920 version 4.2000026 b3s version 4.5000035 Cyberstation 1.81 or above Cause For the old BACnet IP controller b4920, versions prior to 4.200029 could have some communication issue with b3s MSTP enhance mode not enabled on b4920, Resolution Upgrade b4920 to version 4.2000029 or above, preferably the latest version  Go to the webpage of b4920, check "MSTP Enhance Mode" and then click submit Wait for b4920 to go back online and test graphics operation

Issue Sigma BAS Cabling Guide Product Line Sigma Environment Sigma BAS Cause Cabling Guide Resolution Cabling guide for BAS and Sigma.

Issue A BCX4040 is brought online on the Infinity side, but the device cannot be found when running Find New BACnet Devices. Product Line Andover Continuum Environment BACNET Cyberstation Find New Bacnet Devices Cause BACnet is disabled in the BACnet preferences. Resolution Under BACnet preferences, set item #1 - Enable BACnet to true.

Issue Reassigning a USB Serial Adaptor to a desired COM port Reassigning a USB to DB-9 Adaptor to a desired COM Port Product Line TAC Vista Environment Windows OS Cause It is common for newer laptops to come without DB-9 serial connections. USB to DB-9 adaptors have to be used instead. When this USB device is installed, Windows will allocate the first COM port available in the system. In most cases, this will not be COM1, which is the default port designation for both Menta and the Download Wizard. If COM10 or greater is assigned, then it cannot be used with Menta for a direct download because Menta's COM port designation drop-down list only goes to COM9. Resolution Reassign the USB to DB-9 adaptor to the desired COM port: Right-click on My Computer and select "Manage" In the left pane of the Computer Management Console, select Device Manager. This will populate the right pane with system information. Expand "Ports (COM & LPT)." There will be a list of ports in use and which device is associated to the COM port. Look for the USB to Serial Bridge (COMx). If the USB to DB-9 adaptor is not assigned to the desired COM port, right-click on it and select "Properties." From the Port Settings tab, select "Advanced." In the Advanced Settings is a drop-down menu for assigning the COM port number to this device. Select the desired COM port. If it is noted that the COM port is "(in use)," find the device using that port Reassign that device to another open port. This will free up the desired COM port for the USB to DB-9 adaptor. Changing COM port may take some time for Windows to process and put into effect. Monitor "Ports (COM & LPT)" in the Computer Management Console. This will show the reassigned COM port when the operation has finished. *it is also possible to assign to a port in use which should move the previous device to another com, however this should be used as a last resort.

Issue When using the I/A Series R2 (Niagara) WorkPlace Pro to commission LON controllers under an existing LNC-100, configure the Local LON device to match the Domain Length, Domain ID, and Subnet ID programmed in the LNC. Product Line TAC IA Series Environment I/A Series R2 (Niagara) WorkPlace Pro I/A Series Network 8000 LNC-100 Cause When a third-party network management tool is used to define and commission a LON network, the commissioning tool frequently uses specified domain address instead of the default "zero-length" domain address.  When using the I/A Series (Niagara) R2 WorkPlace Pro to learn a previously commissioned network, Workplace Pro will not be able to discover the LON devices until it has been configured to match the domain address of the network. Resolution Click here to see this procedure including screen captures. If the LNC-100 is already communicating to existing controllers on the LON trunk, document the Domain0, Subnet0, and Node0 addressing in either the SYS:SIM or SYS:SIM2 blocks. You don't need to change the existing address in order to add new LON controllers. If you will be using Niagara to commission the new LON controllers, set up the LonWorks Service so that the Local LON device is on the same Domain and Subnet as the LNC-100. Set the Domain length and Domain ID; go to the Properties of the LonWorksService, Netmgmt tab, Engineering tab, domainId, length, domainId. For example, if the SYS:SIM block in the LNC-100 has "DOMAIN0=0D, SUBNET0=01,NODE0=120,..." then in the UNC, it should be domain length = 1 (byte), and domainId = 0D. Apply the changes. Set the Niagara subnetNodeId properties: subnetId = 01, nodeId = 127. The subnet matches SUBNET0 in the SYS:SIM block. Leave the Node ID set to 127 Apply the changes Recommission the Local Lon Device. (Remember to disconnect the LNC-100 from the trunk before commissioning!) With the new controllers connected to the LON trunk, go to the Lonworks service, Lon Device Manager, and run the “find” command; the new controllers should be added to the list of nodes. You can use the Lonworks Utilities, command = identify, SubCommand = service pin to be sure you have the correct node. Then commission the new nodes. Note: Should the LNC-100 be accidentally commissioned, refer to Network 8000 LNC-100 cannot communicate to LON devices under it but can be accessed with WorkPlace Tech or a LON commissioning tool.

Issue When using the DOS command Ping from a server to an ARC-net controller it fails and returns a 'Destination host unreachable' error Product Line Satchwell Sigma Environment Ethernet Network Communications Sigma RIP v1 Cause Routing has not been set-up correctly and the route to the sub-net networks is not defined Sigma DNN broadcast RIP v1 messages for the Sigma server to read, by default RIP Listener is disabled on Windows XP Resolution Enable RIP Listener on the Server.  See Sigma server communication to ARC-net/Ethernet sub-nets via a DNN failing. AND/OR   Add persistent routes to the Sigma server. See Persistent routing on the Sigma server.

Issue What will happen with the EBO license when used with cloned Virtual Machines in a fail-over scenario to another host? Product Line EcoStruxure Building Operation. Environment Building Operation Enterprise Server Cause Even if the Virtual Machines are "cloned" the licensing will show as "Damaged" Since Virtual Machines don't have unique hardware and the software images can be identical, another identifier called UMN3 (Unique Machine Number 3) is provided by the Virtual Machine. This is, as the name indicates, unique for each Virtual Machine. Without this feature, it could be possible to cheat the licensing system and run many instances of software without a license being purchased for each instance.   See the following technical description of the virtual machine image identifier (VMID) that provides the UMN3   A hash of the universally unique ID (UUID or SMBIOS3) that the hypervisor issues whenever a virtual machine is created or cloned. SMBIOS is commonly virtualized by hypervisor providers such as VMware and Microsoft. In addition, virtualization management systems such as VMware’s VMotion ensure that all virtual machines being managed have a unique SMBIOS value. Resolution If Virtual machines are being utilized to provide a fail-over or "hot swap" of the EBO Server then licenses need to be purchased for each Virtual Machine, just as if two physical computers were used. Each Virtual Machine will require its own License Server installation and have the required licenses activated.

Issue SmartSensor Display blank with i2/B3-920s controllers Environment SmartSensor, 10K OHM (Type 3) Thermistor for Andover Continuum, LCD, 4-button (on/off, up/down, Celsius/Fahrenheit), blank cover (no logo) with i2/B3-920s controllers Smart Sensor Part number - TTS-SD-LCD-1 Smart Sensor, Lcd Display, 10K OHM (Type 3) Thermistor For Continuum TTS-SD-LCD-1 Infinity Smart Sensor 6-Button Keypad TTS-SD-LCD-4-2 Infinity Smart Sensor 4-Button Keypad Accurate, reliable 10K Type III Thermistor • LCD display • Programmable Keypad • Built-In service port to be used with the RoamIO-2 Service Tool • Powered directly from an i2 or b3 Field Controller Cause Connect new version SmartSensor to i2/b3-920 and write PE Program to display any character. This will render a blank SmartSensor display. Resolution New controller revision of software is expected to correct the SmartSensor with LCD display . i1 controller are still awaiting a change to the smart sensors (21 July 2014) Update Sept 2015 Firmware versions 4.500076 (b3920) and 3.300009(i2920) include this fix. Smart Sensor also modified for use with i1

Issue Users or engineers may be unsure of how to obtain the Smart Connector itself, as they are not generally available for download from the Exchange Download Center or the Smart Connector Forum on the Community. Product Line EcoStruxure Building Operation Environment SBO/EBO and general integration projects SXWSWSCDL100001 Cause Smart Connectors are not freely available and will require a license obtaining in order to download and use them. As Smart Connectors can be developed by a number of teams around the world that are not part of R&D, these teams will define the costs and requirements for using their software. Resolution A Product Announcement PA-00546 is available that details the concept and use of Smart Connectors. To order the Smart Connector Framework for a project, use part number: SXWSWSCDL100001  Then go to the Smart Connector Server licensing portal to obtain your required license for the specific Smart Connector you require. The URL for the License Portal is: https://www.smartconnectorserver.com/ A login is required for this portal which can can be obtained through the "Sign Up" button. Once logged in the user may browse through the available Smart Connectors and request to download a license. For support information on Smart Connectors, see the article "Support route for Smart Connector Framework issues".

Issue Previously online Xenta Servers are now offline in Vista. They can still be reached via the web interface, and "telnet [ip address] 443" also works fine. Product Line TAC Vista Environment TAC Vista Xenta 511, 527, 701, 711, 721, 731, 913 Cause By default, when you add a Xenta Server in Vista, the checkbox "use browser proxy" is ticked. Even though there is no proxy server defined in Internet Explorer's settings (Tools > Internet options > Connections > LAN settings), in some rare cases this tick may cause Vista to lose the connection to the Xenta Servers (i.e. even if set to "use automatic settings"). This may be due to some changed firewall or network settings at the Vista PC. Resolution In Vista, right-click the Xenta Server and choose Properties Untick the checkbox "use browser proxy" The Xenta Servers should now go online immediately.

Issue Error displayed "Array index too large or too small" when reloading a controller with SmartSensor (Smart Sensor) program created, or saving the SmartSensor (Smart Sensor) program to the controller. Environment Infinet Controllers (i28xx) Bacnet controllers (b38xx) bCX4040 bCX9640 Cause SmartSensor (Smart Sensor) control program uses 7 arrays of the LCDDisplay (or LEDDisplay) InfinityNumeric object to get the keypad input data, display data, change the display format and control the point.  When the point is created with no array, the SmartSensor program fails in saving.  Or, if the LCDDisplay (or LEDDisplay) InfinityNumeric object has been changed from 7 manual entries to no array since the SmartSensor program was created, it fails when reloading the program or the reloading the controller. Resolution Edit the LCDDisplay (or LEDDisplay) InfinityNumeric object and set the 7 manual entries in the Logs tab of the point editor and resave the program or reload the controller.

Issue Is a Menta License required in order to program  the Menta in a Xenta 711? Environment 711 Vista Menta licensing Cause Licensing is unlocked from the factory for "711 Menta." Resolution No License is necessary.

Issue Pinpoint will not open on one workstation or some parts of a graphic will not work Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Due to Microsoft updates, file redirection and/or file corruption, Pinpoint will not open when the configuration / ini file is damaged or corrupt. The points or the whole controller may need to be reloaded. Resolution Shut down Continuum Open MS Explorer Path to C:\WINDOWS Delete Pinpoint.ini Start Continuum (Starting Continuum will recreate the file) Ensure that user account control slider is turned off and/or Write/Read permissions are granted to the C:\program files\Continuum folder Reload individual points or reload the entire controller(if the issue is isolated to certain points) If these steps do not work, Go to Windows Control panel and uninstall/reinstall Pinpoint

Issue Error message when starting SigmaX, says "Failed to Create Object", once accepted SigmaX works correctly. Product Line Satchwell Sigma Environment Sigma SigmaX Tools Utilities Cause Sigma Graphics has not correctly registered in the system registry. Resolution This issue is rectified as detailed below. 1 - Close SigmaX if running. 2 - Start the Sigma server and client. 3 - Open the Sigma graphics editor, and either open an existing graphic, or start a new one. 4 - Modify the graphic and then save the changes. 5 - Shutdown the Sigma client and server, Start SigmaX and confirm its operation.

Issue Tables needed for linearizing a 10K thermistors for an I/Net 7716, 7718, 7728 and 7756 (upper board). Product Line TAC INET Environment 7716 7718 7728 7756 Cause Thermistors require the use of a look up table to linearize the data. Resolution Thermistor Inputs on PCU's 7716, 7718, 7728 and the upper board of a 7756 Enter the Temperature data in °C (First Column - 31 entries) Enter the corresponding resistance data in Ohms (Second column - 31 entries) Enter the dissipation constant in milliwatts per °C: 2 Low Temperature: -22.11°F (-30.06°C) High Temperature: 247.92°F (119.95°C) Point Value in °F: M=0.065942; b=-22.11377 Point Value in °C: M=0.03663447; b=-30.063207 Look Up Table: °C Ohms Current Self Htg Adj °C Adj °F VDC Counts Adj Cts 120 389 0.000481 0.045052 119.95 247.92 0.1872172 153 4095 100 680 0.000468 0.074521 99.93 211.87 0.3183521 261 3548 90 917 0.000458 0.096177 89.90 193.83 0.4199872 344 3275 80 1258 0.000444 0.12407 79.88 175.78 0.5587138 458 3001 70 1753 0.000425 0.158633 69.84 157.71 0.745767 611 2727 60 2489 0.0004 0.199471 59.80 139.64 0.9964769 816 2453 55 3045 0.000383 0.223671 54.78 130.60 1.1671138 956 2316 50 3602 0.000368 0.243359 49.76 121.56 1.32407 1084 2179 45 4368 0.000348 0.264484 44.74 112.52 1.5200445 1245 2042 40 5326 0.000326 0.283435 39.72 103.49 1.7375701 1423 1905 35 6691 0.0003 0.300218 34.70 94.46 2.0043736 1642 1768 30 8056 0.000277 0.308878 29.69 85.44 2.2308374 1827 1631 28 8777 0.000266 0.311174 27.69 81.84 2.3371678 1914 1576 26 9572 0.000255 0.312351 25.69 78.24 2.4453301 2003 1522 25 10000 0.00025 0.3125 24.69 76.44 2.5 2048 1495 24 10450 0.000244 0.312349 23.69 74.64 2.5550122 2093 1467 22 11420 0.000233 0.311127 21.69 71.04 2.665733 2183 1413 20 12490 0.000222 0.308669 19.69 67.44 2.7767897 2274 1358 18 13680 0.000211 0.304953 17.70 63.85 2.8885135 2366 1304 16 15000 0.0002 0.3 15.70 60.26 3 2457 1249 14 16470 0.000189 0.29383 13.71 56.67 3.1110691 2548 1195 12 18090 0.000178 0.286579 11.71 53.08 3.2200071 2637 1140 10 19900 0.000167 0.278241 9.72 49.50 3.3277592 2725 1086 8 21920 0.000157 0.268921 7.73 45.92 3.433584 2812 1032 6 24180 0.000146 0.258715 5.74 42.33 3.5371562 2897 977 0 32660 0.000117 0.224329 -0.22 31.60 3.8279419 3135 815 -4 36200 0.000108 0.211999 -4.21 24.42 3.9177486 3209 706 -10 55340 0.0000765 0.162028 -10.16 13.71 4.234772 3468 543 -14 69000 0.0000633 0.138199 -14.14 6.55 4.3670886 3577 435 -20 97130 0.0000467 0.105789 -20.11 -4.19 4.5332773 3713 272 -30 177200 0.0000267 0.063207 -30.06 -22.11 4.732906 3876 0 This spreadsheet is for a thermistor rated at 10,000 ohms at 25°C. Install a 10K Ohm Resistor in the "B" terminal (consult the TCON for the controller you are using for details) This look up table program is based on using 31 entries The data points do not have to be evenly spaced For the look up table to the 7756 lower board, see 10k Thermistor Look Up Table for an I/Net 7756 (lower board).

Issue Enhanced and Standard Alarm Delivery Explained Product Line Andover Continuum Environment Cyberstation Cause Information on the difference between Enhanced Alarm Delivery and Standard Alarm Delivery feature. Resolution Standard Alarm Delivery:   Prior to Continuum 1.7, alarms were delivered from the controller to each workstation on the network as long as a  Cyberstation is online (from the controller's perspective) AND if the Cyberstation is a recipient of the alarm or not.   The first workstation which receives the alarm logs it to the SQL database. The alarm is broadcast and if for some reason it doesn't get logged there is no guarantee it will be delivered to any Cyberstastion. It gets broadcast once.   Enhanced Alarm Delivery: The alarm engine was changed so that alarms could be delivered to Workstations that were temporarily offline. To accomplish this Continuum implemented Microsoft Message Queuing (MSMQ).   The controllers generate alarms based on criteria set up in alarm enrollments. These are logged in the database by the first workstation that receives the alarm which then hands it off to MSMQ for delivery to all workstations in the recipient list. The controller still sends the alarms to all online workstations. If a workstation is offline, alarms are stored in an outgoing MSMQ queue that will be delivered once the Cyberstation is back online.   Acc.App.AlarmServer.exe (Alarm Delivery Server) is the process that handles alarms and hands them off to MSMQ which is handled by the Windows Message Queuing service.   To view MSMQ queues, go to [Windows Control Panel>Security Settings]> Administrative Tools> Computer Management> Services and Applications> Message Queuing   Enabling Enhanced Alarm Delivery when upgrading or with a new install This is accomplished by leaving the default checkbox for Enhanced Alarm Delivery selected in the database initialization step on a new install or when upgrading to a version greater than 1.7x. MSMQ will then be installed as part of the Cyberstation installation or upgrade.   Note: If the Enhanced Alarm Logging checkbox is not checked initially, the Enhanced Alarm Delivery checkbox may become unselectable. See Installing Continuum Database for the First Time on a Multi-User LAN System in the Installation Guide   Enabling enhanced alarm delivery in a system that doesn’t have the checkbox selectable 1. Manually Install MSMQ Start> Run> type cmd then click OK (to open a command prompt) At the DOS prompt type cd\ then enter (places the cursor at the root) cd \program files\continuum\install then enter Type cscript MSMQInstall.js then enter (Windows component wizard Installs MSMQ) When the script is finished, one of the lines will indicate that MSMQ started successfully Type exit 2. Updating the database Note: Ensure you have a recent database backup before the next step Run Database Initialization Select Server if LAN or Stand Alone accordingly Select Enhanced Alarm Delivery checkbox Select update existing database and then click continue Restart all Cyberstations (If ALL aren't restarted, the system can still be in mixed mode)   3. LAN installation  Manually install MSMQ on each Cyberstation according to the instructions above (step 1). MSMQ will now be used for guaranteed alarm delivery.     Caution: Make sure that all Cyberststations in the database are restarted after Enhanced Alarm Delivery was selected and the DB Update performed!    Not restarting a Cyberstation puts the system at risk of using workstations with both types of alarm delivery (PSS may refer to this as MIXED MODE).   If all but one of the Cyberstations gets restarted and a Continuum User changes the alarm delivery mode and then a Cyberstation gets restarted later, the system  will be in mixed mode.   Uninstalling MSMQ Uninstalling MSMQ on a workstation (if needed at some point) Go to Control Panel> Add/Remove Windows Components> Deselect Message Queuing Say Yes to the warning message Reboot Also, check the following: Add a column to the alarm list view check the loggingWSId and see if the alarms are being delivered to another workstation that is no longer used. If it is no longer needed delete that Workstation which should correct this issue.