Building Automation Knowledge Base

Issue When installing I/NET on a 64 bit machine, two parts will be installed: main part and 64 bit part. Sometimes when attempting to uninstall the 64 bit part in the Control Panel, it will show an error: There is a problem with this Windows Installer package. A problem required for this install to complete could not be run. Contact your support personnel or package vendor. It cannot be solved even when trying to reinstall the whole software. The software installer goes into continuous loop and does not complete. Environment I/NET 64 bit OS Cause The main part of I/NET on 64 bit machine is under C:\Program Files (x86)\INET Seven\ and another 64 bit part is under C:\Program Files\INET Seven\.The cause of this issue is when you tried to uninstall the main part in Control Panel first, it will also delete the files under C:\Program Files\INET Seven\, which makes the uninstall program unusable for 64 bit component. When trying to reinstall the software, I/NET will regard the 64 bit part has been installed and skip this step, which forces the software installer into a continuous loop. Resolution The correct order to uninstall I/NET on 64 bit machine should be to uninstall 64 bit component first, and then the main part in the Control Panel. If the main part has already been uninstalled, try to download MyUninstaller from here. After opening the software, right click on the I/NET 64 components and choose Delete Selected Entries. That will force uninstalling this component.  After that, try to install another version and it should be fine.

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 Xenta Server is offline in Vista and can not be reached via web interface. Product Line TAC Vista Environment Vista 5.1.9 Windows 7 Cause The PC has proxies configured. Resolution Open Internet Explorer Go to Tools > Internet options > Connections > LAN settings Disable "use a proxy server" Related Article: Xenta Servers are offline in Vista, although they can be reached via the web interface

Issue The documentation for the SED-THSU5045 thermostat states that the super capacitor voltage can be measured across terminal strip TB1 terminals 1 and 2.  However, there is no mention of what an acceptable voltage reading would be.  Environment Super capacitor voltage specification is not published on the thermostat documentation. Cause A minimum voltage of 5.5 VDC should be present across TB1 terminals 1 & 2. Resolution If a 5.5 Volts DC charge cannot be maintained on the super capacitor, the device may require either an auxiliary light collector or external 24 VAC.  The Thermistat battery is not designed to run the thermostat for extended periods.

Issue PE Script program created in b3 or i2 has no error but its not executing. Product Line EcoStruxure Building Operation Environment Infinet i1, I2 BACnet b3 Automation Server, AS, ASP, ASB Cause Program compilation was not valid. Resolution Examine the code and determine what is causing the compilation issue. Known causes... 1. Variable declared in the code but not used (unbound)

Issue An analog Modbus value has specific values when the system is in error. For example: 0 = No Error 1 = Over Current Acc 2 = Over Current DeAcc 3 = Over Current Constant Speed How could an alarm be defined to trigger when the object has Value = 2? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.5 Cause When using a Modbus analog value, it is not possible to create an alarm on a specific value. Resolution Instead of a Modbus Analog Value, create a Modbus Multistate Input. With a Modbus Multistate Input, it is possible to connect a multistate alarm which gives the option to create an alarm on a specific value.

Issue According to the documentation the max cable lengths for the sensors connected to a Multical device are : Temperature sensors : 10m Flow Sensor : 2,5m Is it possible under any circumstances to extend the cable length up to 15m?   Environment Multical Cause The sensors come in pairs and are calibrated. They must never be extended. The longest length available is 10 metres. Resolution It is not possible to extend the cables to the sensors, as the devices are calibrated with the sensors delivered from the factory.

Issue Are the BCX4040, BCX4000 and b3 line of controllers compliant with the most recent BACnet specification, ASHREA 135 2012? Environment Continuum Controllers Cause The consultant is requiring that all BACnet controllers be compliant with ASHREA 135 2012. Resolution As of August 27, 2014 the BCX1 and b3 family of controllers do not comply with ASHREA 135-2012. This is noted in the PICS statements as the Protocol Revision. The 2004 version of the spec correspond to Protocol Revisions 4, 5 & 6. The 2012 version is Protocol Revision 14 & 15. As of August 27, 2014 the BCX1 and b3 family of controllers comply with ASHREA 135-2004 spec revision.  

Issue Site Access Control lockdown for the entire complex. But, also allow certain cards to override certain doors during an emergency situation. Environment I/NET site with access control Cause There is a requirement to lockdown an entire complex with a single toggle switch, but allow First Responders access to certain locked doors in the building. Resolution  There are two different Demo programs for this process One Link program (Download One Link Zip file): MCI -- 7798 DPU – SCU1284 (2 addresses) A maintained switch SPDT   Two or more Links program (Download Two Link  Zip file) MCI – 7798 Link1 MCI – 7793 Link2 – Channel “B” SCU1284 (2address) Link1 SCU1284 (2address) Link2 – On second channel A maintained switch SPDT Each of the above zip files have the following inside: Note: This would be restored to your test bench, and then configuration implemented into a production site.

Issue User Permissions Path needed to be modified to reflect the renaming of Server, Folder and Object Names. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server  Building Operation Automation Server Premium Cause Following the renaming of a server (or Folder or Object), a User has different access to the system via WorkStation or WebStation. This may be no access to a server and new access to a server. The changes seen by the user will depend on the Permissions set for the Group or User. The Permissions are not updated in line with renaming of Servers/Folders/Objects. Resolution Following any changes to Servers/Folders/Objects, all the User and Group Permissions should be checked and corrected as required. See WebHelp for extra details

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Uninstall PCT doesn't uninstall Oracle VirtualBox Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The uninstaller of PCT doesn't include VirtualBox as part of the uninstallation. Resolution 1. Uninstall PCT from “Control Panel\All Control Panel Items\Programs and Features”. 2. Uninstall PCT Client. 3. Uninstall Oracle VM VirtualBox.

Issue What do the HVAC, SEC, and INT options on the Continuum Security Key provide access to? Product Line Andover Continuum Environment Continuum Security Key Continuum Cyberstation Cause Unsure as to what restrictions these various Security Key Options place on the activity that can be performed and what can be viewed within Continuum. Resolution HVAC - Provides access to HVAC specific objects such as viewing BACnet controllers, creating BACnet objects and polling for new BACnet Devices. SEC - Provides access to viewing and creating Security specific objects such as Door, Area, and Personnel objects. INT - Provides access to all of the above. This key will be able to view/create both HVAC and Security related objects. Any Workstation with a SEC key will not be able to view any BACnet Devices or objects in the database and any with an HVAC key will not be able to view Security related objects in the database. For more information see Different options on the CyberStation security key.

Issue Unable to get modbus to communicate with the automation server and LC&D GR2400 lighting controller. Environment Modbus Automation server LC&D GR2400 SmartStruxure Solution 1.5 Cause The LC&D GR2400 lighting controller will ONLY allow 1 stop bit in it's modbus communication. Normally the stop bit setting in a modbus slave device is an "at least number", meaning the GR2400 should except 1 or more stop bits, but it does not. The problem comes from the automation server by  default sends the 1 stop bit and addition "guard bits" for modbus communication. The guard bit setting was not available in versions prior to 1.5 and by default the automation server would send 3 stop bits causing the modbus communication to fail with the GR2400lighting controller. Resolution In SmartStruxure 1.5 right click on the Modbus Master Network and select properties. Click the advanced tab:         3. Here you see the guard bit setting. This value should be a 0 if the automation server is to ONLY send 1 stop bit. If this number is left at default the automation server will add the number of guard bits to the user       setting of stop bits. By default that makes 3 stop bits from the Automation Server. To properly communicate to the GR2400 the guard bit setting should be a 0 and the user selected stop bit should be a 1 in order to ONLY send 1 stop bit.

Issue Graphics not working in Webstation. Only the menu bar is shown. Some graphics might work. The graphics are working fine in the Workstation and in the editor. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation TGML Cause Some images (PNG, JPEG, BMP) can have wrong information in the image file. In some cases, this corrupted image information will block the graphic from being rendered in Webstation although it works fine in the editor and in Workstation. Resolution Make a copy of a graphic that is not working and delete all the images in the graphic. If the graphic can now be viewed in Webstation, delete the images one at a time viewing the graphic in Webstation after each save.  This will allow the location of the image(s) having the issue. Open the image in a graphics editor such as PaintBrush and save it with a new name. Import the new image and save the graphic. Check that the graphic can be viewed in Webstation Another option to easier find the file image having the issue, is to extract the images from a graphic that is not working in Webstation with the "TGML Image Extract" tool, and run all the images through an image checker, such as "Bad Peggy" or "Corrupt JPEG Checker"

Issue A newly installed program does not run and could be using a port on the host computer that's already assigned to another running program or service.  How can current port usage on the host computer be determined quickly? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert, Satchwell MicroNet, Satchwell BAS & Sigma, TAC INET, TAC I/A Series, TAC Vista, Andover Continuum, CCTV, Field Devices Environment Microsoft Windows Cause A port conflict is suspected. Resolution Open a command prompt and type: netstat -a -n -p tcp -b This command will display all services running, protocol used, local and foreign address, state, and program name.   netstat -p tcp -ano This command will display all services running, protocol used, local and foreign address, state and PID (process identifier). Use Task Manager to match the PID to the program using the port. netstat -p tcp -ano | findstr :80 If a specific port number is necessary, this command will interrogate the system for the program currently using that port number:

Issue Using I/NET Audible Alarms with Remote Clients No audible alarms with Remote Client configuration Product Line TAC INET Environment I/NET Seven Software 2.42 and newer I/NET Remote Client or Remote Client with I/O Server Cause The functionality was changed with the following TrackRecord 5940 fix in I/NET 2.42: Alarms in a Remote Client do not get an audible alarm Only clients configured as "Remote Client w/IO" are capable of routing alarms/events to the server. The masking on clients configured as "Remote Client" will not cause alarms/events to be routed to the server. On these clients, you can use the masking to get audible alarms with no danger of getting duplicate alarms.   Resolution To receive and activate audible alarms on a Remote Client, set the Distribution Group and Masking of the alarm point within AMT.   Note: This setting is only the case for I/NET 2.42 and above.  If this is setting is made in earlier versions of I/NET, it will cause alarms / events / trends to be routed to the server and possibly can cause duplicate events / trends to be sent to the server.  The following information is noted in TCON300: "Limitations to TAC I/NET Seven on Remote Clients   Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features:   Network functions                 Automatic DPU restore                 Archiving                 Dial after edit   Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed." "Limitations to TAC I/NET Seven on Remote Clients" Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features: Network function Automatic DPU restore Archiving Dial after edit Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed."  

Issue SHR100-T is obsolete and needs to be replaced Environment SHR100-T Room humidity sensor Cause Replacement of obsolete sensor Resolution The SHR100-T is replaced by SHR110-T with part# 006903115

Issue While in "Edit in spreadsheet" mode for a Modbus device, changes made to the gain value are not accepted and cannot be changed.  Environment Workstation Modbus Network Devices 1.5.0 and prior Cause When the gain value of a Modbus point is changed to a decimal value in spreadsheet mode, the value will not be accepted if there is an integer in front of the decimal.  Resolution The workaround for this issue is to right click on each modbus point and go to properties of each modbus point to set the decimal gain value. Or you can copy and paste values from Excel into the SmartStruxure spreadsheet. For additional detail on this issue, see the below sections.   Edit in Spreadsheet All whole numbers can be entered using spreadsheet mode. If the gain value to be entered is greater than -1 and  less than 1 then it can be entered using the spreadsheet as well but the value must be entered by typing the decimal first. For example instead of typing 0.1 you would type .1 into the gain field. If the value 1.26 is typed into the gain field it will actually save it to 126. In this situation reference the bottom section "Edit in properties of Modbus point". Edit in properties of the Modbus point If the decimal value to be entered is less than -1 or greater than 1, then it must be changed in the properties of each individual Modbus point. For example if you need to change the gain to 1.26 then it must be entered as seen below. Right click on the modbus point and go to the properties.

Issue Cannot learn EnOcean thermostats into the MPM. Environment MPM, EnOcean Cause Purchased the wrong EnOcean frequency MPM. Can the antennas just be changed?  Resolution No, just replacing the antennas will not resolve the problem. The MPM controller and antenna must be replaced to match the frequency of the Enocean thermostats. Note: the 315 MHz EnOcean MPM uses an antenna with green stripes; the 902 MHz EnOcean MPM uses an antenna with yellow stripes. 

Issue How many SC2300 could be connected to one SE7300 or 8300? Environment SC3000 SE7300 SE8300 Cause Inputs from the relay packs could not be connected in parallel. Resolution It is not possible to connect inputs in parallel, therefore you could only connect one relay pack to one device.