Building Automation Knowledge Base

Issue Crystal Reports with I/NET 2.41 and higher Design tab is no longer available (missing) within SevenReports. Can no longer edit Crystal (Seven) Reports Product Line TAC INET Environment SevenReports (Crystal Reports) with I/NET 2.41 and higher Cause I/NET will no longer have the "Crystal Reports" Modify and Design license after May 2012. After 2.41 you must buy a separate CD for this function. Upgrades are not affected by this change. Any SAP Crystal Reports licenses used at existing installations will remain active after an upgrade. Resolution RDC version will no longer be supplied on the I/Net CD.   The NON_RDC version will still allow reports to be Viewed and Printed, as always. Modifying a "Canned" report or designing a "New" report will be impossible unless the new RDC version is installed.   This removal of the Crystal report function will start with I/Net Seven rev 2.41A and beyond.   To receive the Crystal Reports application files and license certificate, the SEVEN-REPORTS-RDC part will need to be ordered in addition to the standard I/NET SEVEN software part for each workstation requiring SAP Crystal Reports. Refer to Unable to install the RDC version for additional information and a copy of the necessary software for upgrading and installing this software.   Upgrades (from I/NET Seven Version 2.21 and above) are unaffected by this change. Any SAP Crystal Reports licenses in use at existing installations will still be active after an upgrade as long as you perform an upgrade of the existing I/NET installation.  If you perform a clean install, so you have uninstalled the previous version of I/NET, you will lose this licensing.      

Issue User names and passwords are not accepted by the AS's. Environment Domain Password Users Cause A new Domain was configured on the ES, this configuration was then exported, the export was then imported to each AS. Resolution Note;- By importing and exporting copies of the Domain, Domains that are not related to each other, are created, which is unlikely to be the operational intent. Exporting/Importing will duplicate user accounts etc. Having multiple accounts with the same name (potentially with different passwords) throughout the system can lead to an overly complex and un-manageable configuration. To create a new Domain configuration, carry out the following. Add the Automation Servers (AS) to the Enterprise Server (ES) in the normal way. With the Workstation connected to the ES, select "Control Panel" and "Domains"     "Add" a new Domain, giving it a suitable name, and then select the AS's that will share this Domain with the ES.       Now Create the Domain. At this stage, if the AS's are reviewed, the New Domain can be seen, (Note - Nothing is shown in the Domain folder on an AS).                           If required, you can choose to set the new Domain as the default Domain,  this is achieved by right-hand mouse clicking on the Domain and selecting the option. This must be done on each Server.                                       Confirm that the ES IP address is correct in all servers.     Finally create the User Groups, Users, and Workspaces required for this Domain. Log off the Workstation, and restart  the ES. Once the ES has restarted, log back on using the new Domain information.   Log on to an AS using the new Domain information.     

Issue Do 3rd party BACnet MSTP devices count as nodes on a BCX controller that is node limited? Environment BCX controller Third-party BACnet MSTP devices Cause Knowing the information will ensure there is not more node than the BCX controller specifies. Resolution Yes they do count as nodes. If you do go over the node count you will see operational problems with the BCX BACnet controller. The BCX controller will scan lock when it tries to perform a time sync to the MSTP network. Modbus nodes communicating via xDriver are not part of the node count.

Issue Key for the standard Door Control Graphic Product Line Andover Continuum Environment Door Control Graphic PinPoint Cause Require a key for the standard Door Control Graphic Resolution

Issue The local time inside a Xenta programmable unit is dependent upon server time, time zone, and daylight savings time settings.  Incorrect DST settings result in incorrect times in the controller which causes problems from incorrect start times on HVAC equipment, to incorrect alarm time stamps in alarm queues. Product Line TAC Vista Environment Xenta Programmables version prior to 3.74 Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In 2007, most of the United States and Canada changed when DST is observed to the second Sunday in March to the first Sunday in November.  Because it had never changed prior to that, programmable controllers retained the old settings (first Sunday in April to last Sunday in October). Resolution The issue was resolved with the release of firmware MOT version 3.74.  Upgrading your controllers to 3.74 is a viable solution, however not always cost effective.  There are two ways to work around the issue. Note: For information on how to download firmware to Xenta programmable devices using the Download Wizard please see Download an .MOT file into a Xenta Programmable controller. Configure TAC Xenta Central DST Settings Refer to the TAC Vista Technical Manual Chapter 19.6 In the folders pane, right-click the folder where you want to place the time event object. Point to New, point to Object, and then click Time Event – Object. Type the name. Open the time event object. On the General tab, type a description. On the Time Event Settings tab, set a suitable repeat interval, for example, first Monday in each week. Click OK. In the folders pane, right-click the folder where you want to place the Central Daylight Settings – Xenta object. Point to New, point to Object, and then click Central Daylight Settings – Xenta. Type the name. Open the Central Daylight Settings – Xenta object. Two options are available. You can use Windows start and end times for the daylight saving time or specify your own start and end times. If you want to specify your own start and end times: Clear the Use Windows settings check box. In the Daylight saving starts box, set the start time for the daylight saving time. In the Daylight saving ends box, set the end time for the daylight saving time. In the Update schedule box, browse to the time event object that triggers the push to the TAC Xenta devices. Click Select. Click OK. Note: You must select Manual DST Mode and Central DST for each controller in the system for a global change to take effect. Manually set DST Settings for each controller The DST Xenta object is not available in all versions of Vista.  If that is not an option, DST settings on each controller can be manually set for the start day and stop day.  Unfortunately, time settings do not allow for designations of "first Sunday" or "last Sunday," only calendar dates.  So each controller will have to be edited each year to maintain correct time settings. In order to facilitate this, this utility:  ODXentaTimezoneChanger was created.  It must be used each year to update the settings, but it will allow you to change all time settings on all controllers in a Vista database simultaneously, greatly reducing the time it takes to correct a system. NOTE: If the Lonworks network has not been properly commissioned & downloaded the tree will not properly communicate with the Vista Server. Check your network tree for asterisks to see if any downloads are required.

Issue Cannot establish communications to Modbus RTU using BCX X-Driver on Comm2 Environment BCX 4040 Modbus RTU Cause Configuration of BCX to communicate with Modbus RTU device Resolution This excerpt from the Modbus RTU guide describes the parameters to configure the X-driver for Modbus RTU communications using the BCX. Click Here

Issue When viewing a graphic (or other object requiring a Java plugin) in Google Chrome you get the message "This plug-in is not supported" where the graphic should have been shown Environment Webstation Xenta Server I/A Series G3 version 3.8.xx or earlier Cause Google Chrome has disabled Java in version 42 and above Resolution 1: Open Google Chrome 2: In the address field, enter the following: chrome://flags/#enable-npapi 3: Click on "Enable" to enable the feature so it looks like this 4: Click on relaunch to restart Chrome   More information from Java's web site

Issue When printing access control cards, there is a need to print the a card number bar code on the card as well as photo's, names, text, logos etc. Environment Continuum Access Control systems, all versions. All Security and Integrated Workstations (with SEC or INT in the part number). Photo badging option (append -B to the part number). Cause As well as a photographs, text, numbers and graphics, barcodes may be added to the card design using the EPI Designer software. To use card badging the system requires that the Continuum Security Key (Dongle) has the badging option enabled (-B in the part number), otherwise the "Create/ Edit Badge" option will not be available to select. Resolution From the EPI Designer menu select the "Draw", "Bar Code" option and the following screen will be displayed allowing the barcode to be configured: The configuration page above allows the type of barcode to be defined, the Personnel "Field Name" to be linked to the code as well as other barcode options shown. Custom fields can also be used.

Issue Can 2 comm ports be enabled when using the RTU Xdriver? Product Line Andover Continuum Environment Continuum 9680 99xx 9640 4040 Xdriver Modbus RTU Cause At times it is necessary to have multiple ports enabled for Xdrivers Resolution The ability to enable 2 comm ports using Xdrivers can be done, but is not recommended by the Xdriver developers or supported by PSS. The RTU Xdriver is poll on demand. This type of driver can request a lot of data and starve the CPU on the controller which then makes the polling irregular. If 2 ports are being used then there are typically more devices being added and therefore more points increasing the requests and demand on the controller's CPU. Use one program to control the polling on both ports. Two programs attempting to control the polling asynchronously will cause communication issues.

Issue Documentation on memory usage for the 7910 and 7920 DPUs Product Line TAC INET Environment I/NET site Cause Documentation on memory usage for the 7910 and 7920 DPUs Resolution Yes. TCON 237 pages 9-4 through 9-6 refers to INET 2000, 2.xx systems. Tech tips 039 and 035 were written for older I/NET systems.

Issue Sending the results of a Listview to a Report.   Product Line Andover Continuum   Environment CyberStation   Cause Available options are not commonly known   Resolution There are two ways to display the contents of a Listview in a Report.   The first method is to create a Report and set its data source to 'Listview'.  Then in the filter tab add the desired Listview as a filter. Please note that only ONE list view can be added. When the Report executes it populates data from the Listview object.   The second method is to create an HTML Report template Then the HTML Report in the Listview's Report Template field In this case the report can be invoked right from the Listview

Issue The Continuum icon in the system tray does not respond to a right click when attempting to logon to Cyberstation  via a remote desktop connection. Restarting the Cyberstation application will temporarily correct this issue. This problem is usually found when multiple remote machines are accessing the same Cyberstation workstation via Remote Desktop. Product Line Andover Continuum Environment Microsoft Windows 10 Cause Windows Remote Desktop behavior can be affected when several RDU hosts whose screen resolutions are not the same and connecting to a remote workstation.  Resolution Ensure the various machines accessing Continuum Cyberstation over Windows Remote Desktop use the same windows resolution aspect ratio.

Issue DBCreate backup access denied using Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2 'Cannot open backup device ' C:\Users\Administrator\Desktop\20120919'. Operating System Error 5( Access is denied). [Microsoft][ODBC SQL Server Driver] [SQL Server] BACKUP DATABASE is terminating abnormally' Product Line TAC INET Environment I/NET loaded on Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2 Cause The cause is insufficient rights to perform this function based upon a local policy of not allowing users to see the 'C' drive. Resolution Although when Using a Network Administrator account or Administrator for the local machine, you cannot open backup to either the local machine 'C' drive or a network share, you should be able to backup to a thumb drive.  Go to local disk properties - security tab Users do not have permissions to modify or write to the 'C' drive. Windows UAC may over ride the administrator permissions. Check your permissions and make sure you have rights to a folder and perform the backup. Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.  

Issue Creating a Listview/Report to show all the personnel objects which have access to a given area.   Product Line Andover Continuum   Environment CyberStation   Cause Reports can be used to do a security audit of which individuals have access to certain Areas in a building.   Resolution Create a Listview object In the class field select AreaLink Add columns for PersonID and AreaID (Add any other column as needed) In the Qualifier tab enter the following qualifier: AreaID Is XXX Id where XXX = full path to area Example: AreaId is Root\AreaFolder\Lobby Id **NOTE Use folder\area aliases ONLY in the qualifier, do not use names. Save and run the Listview.  The Listview should show all Personnel objects that have the Area specified by AreaID in their Area list. To generate actual Report Object from the list view see How to create a Report from a Listview.

Issue A change is made to a public signal in TAC Vista Workstation, which was created in a Xenta Server XBuilder project, changed back to the initial value after performing a download to this Xenta Server. Environment Xenta Servers (Xenta 511, Xenta 515, Xenta 555, Xenta 527, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913) XBuilder Tested with Windows Server 2003, Window XP SP3 Cause If a path name is changed of a signal, for example, change the "the site name" folder name to another name, Vista consider this change as a major change, and Workstation will not be able to find the new path of the signal. Therefore, the signal will return to the initial value which is initialized in the Menta object. Resolution Suggestion is making all the infrastructure change at the beginning if you can. If there is a need to change the path, make sure all the initial values are reflect to the current values in Workstation. Then, make the download to the Xenta Server.

Issue When upgrading to a different revision of software in I/NET Seven, there are a few steps that are highly recommended to ensure that the database doesn't get corrupted during the upgrade. Product Line TAC INET Environment I/NET Seven Cause Performing an upgrade of I/NET Seven software. Resolution Close I/NET Start DB Create and select the Verify Database option. Verify that the database has 0 differences. Select Upgrade Database to force an upgrade Select the Verify Database option again. Now back up the database to the local drive or media and proceed with the upgrade. Once completed, Select Restore database and proceed to where the back up is and restore the database to the system.  Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue Operation of multiple Satchwell CZU Fan Coil Unit Controllers from a common Temperature Sensor. Product Line Field Devices Environment Fan Coil Unit installations comprising multiple Satchwell CZU Fan Coil Unit Controllers. Stand alone discreet Satchwell CZU Mk 1, Mk2, Mk3 and Mk4 Zonemaster Controllers CZU1201 CZU1202 CZU1203 CZU2201 CZU2202 CZU2203 CZU3201 CZU3202 CZU3203 CZU4201 Cause From time to time the need arises for office partition layouts within a building to be revised in order to reflect changes in occupancy requirements. This can result in the combination of numerous individual controlled spaces into a common controlled space. This in turn may result in the need to revise associated Fan Coil Unit control systems installed in the controlled spaces affected. Such revisions may require multiple Fan Coil Unit control systems to be controlled from a common Temperature Sensor installed in the common controlled space. This form of control may be achieved by adopting the installation method described in the Resolution. Should the common controlled space be of such a size as to benefit from the installation of averaging Temperature Sensors then this may be achieved by installing 4 non-adjustable Temperature Sensors.  The 4 non-adjustable Temperature Sensors should be wired in a series-parallel configuration in order to ensure compatibility with the associated Satchwell CZU Fan Coil Unit Controller. The series-parallel wiring configuration may be achieved by adopting the installation method described in the Resolution. Resolution 1.  Operation of multiple Satchwell CZU Fan Coil Unit Controllers from a common Temperature Sensor.  Multiple Satchwell CZU Fan Coil Unit Controllers should not be connected directly to a common Temperature Sensor. Instead the common Temperature Sensor should be connected to a single Satchwell CZU Fan Coil Unit Controller. The single Satchwell CZU Fan Coil Unit Controller should then be connected to the associated Fan Coil Unit Heating Coil Control Valve Actuators and / or Cooling Coil Control Valve Actuators. Up to 7 Heating and / or 7 Cooling Control Valve Actuators may be wired to a single Satchwell CZU Fan Coil Unit Controller in accordance with the method shown here 2.  Averaging Temperature Sensor control. Should the controlled space be of such a size as to benefit from the installation of averaging Temperature Sensors then 4 non-adjustable Temperature Sensors may be wired in series-parallel configuration in order to ensure connection compatibility with the associated Satchwell CZU Fan Coil Unit Controller. The 4 non-adjustable Temperature Sensors may be wired in series-parallel configuration to a common Satchwell CZU Fan Coil Unit Controller in accordance with the method shown here

Issue Many electrical power meters provide a high resolution Modbus or M-Bus output for cumulative parameters such as kWh, kVAh and kVARh.  This output can be displayed in Vista or on an Xenta Server web page, but the resolution can be degraded by inappropriate conversions in XBuilder and choice of display format.  This article shows how to maintain the full resolution of a meter reading from acquisition through to display on a Vista graphic or Xenta Server web page. Environment Xenta 511, 527, 555, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder PM710 Cause Applying scaling or connections in XBuilder, or processing in Menta, reduces the precision of a high resolution Modbus value to that of a Real or Float. Resolution The following comments refer to Modbus registers in the Schneider Electric PM710 energy meter, although many other meters deal with extended precision values in a similar manner.  Acquiring Data from the meter: 1. If you want to maintain the full precision of the meter 'Real Energy, Total' reading, use register 4000 which is a 32 bit signed integer, representing scaled kWh. The scale factor is stored in register 4108 as a 16 bit integer and the two registers should be used in conjunction for display purposes. The maximum full precision value that can be displayed this way is: 2147483647 - 10 decimal digits - before the scale factor is applied. 2. An alternative to register 4000 is provided in register 1000, which is of type 'Float'.  This equates to the REAL type in XBuilder, so it already has only 21 bit precision. However, there is no need to scale it as the exponent is built in to the Float type. Processing input in XBuilder: 3. For register 4000 in the device template, apply a gain of 1 and keep the converted value as INTEGER.  This will maintain the full 32 bit precision of the Modbus register.  If you apply any gain less than 1 or convert the value to a REAL, you will only end up with a 21 bit precision result.  This equates to a loss of 2 decimal digits approximately. 4. Avoid using Connection objects.  For example, a variable of type 'SNVT_elec_kwh_l' has theoretically the same precision as register 4000 in the PM710, so it would seem to be a direct conversion.  However, because you have to use a Connection object to link the two in XBuilder, the value is converted to a REAL internally and you end up with a 21 bit precision result. 5. Xenta Servers can provide full precision Modbus values for display in Vista. Create new Signal objects in the System pane in XBuilder and drag and drop the Modbus values from the Network pane onto the Signal objects.  The Signal objects will have the same precision as the original Modbus registers and are visible in Vista. Displaying values in Xenta Server and Vista: 6. Value pages in the Xenta Server and TGML graphics pages in Xenta Server and Vista can display a 10 digit integer. In the case of item 1 above, all 10 digits will be accurate. In the case of item 2 above, only the most significant 8 digits will be accurate. 7. A value page in the Xenta Server will display a real as 8 digits plus exponent. However, only the 7 most significant digits will be accurate. 8. The object view in Vista will display a real up to 8 significant digits, with only the most 7 significant digits being accurate.  Vista will attempt to show this as fixed point 6.2 and no exponent.  If the actual value is too big or small for this format it reverts to 3 significant digits plus 3 digit exponent.  

Issue An attempt to flash the firmware in the controller results in error, "The UPREV code could not communicate with the specified controller." Product Line Andover Continuum Environment bCX CX9680 ACX5720 ACX5740 Cause Uprev operation attempted using the wrong flash file. Resolution Re-try the operation using the flash file that matches the model number in the controller. Note that regardless of what the model number reads from the InfinityController editor in CyberStation, the verification is done at the controller level. Do not go by what you see in the CyberStation as this user configured field could have been entered incorrectly. Verify the model number from the controller's web page configuration.

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 Services for assistance. Issue When viewing a meter consumption report, the values shown in the report does not match the values in the extended trendlog in SmartStruxure Environment SmartStruxure 1.5 and below Web Reports Cause Generally this will happen if the meter is reset and that time the last value of that meter will set a BaseValue. To calculate the total consumption of the meter we are adding the BaseValue to the offset. This means that the value shown will be the logged value + the offset. In some cases however you would want to completely reset the log and just show the same values that are represented in the extended trendlog. It has been identified, that a defect causing a trend logging a 0 after each restart triggers this reset. Request the latest hotfix for 1.5 from Product Support in order to avoid this happening in the future.   Note: This issue (Defect #26360) has been fixed in 1.6.1 release. Resolution 1. Open "SQL Management Studio" and connect to the database "StruxureWareReportsDB" 2. Locate the log you want to reset using this query: SELECT * FROM tbLoggedEntities 3. Note the ID of the log you want to reset 4. Reset the log using the following query, replacing xxxx with the ID of the log DECLARE @id INT SET @id = xxxx UPDATE tbLoggedEntities SET BaseValue = 0 WHERE ID = @id UPDATE tbLogTimeValues SET FloatValue = OdometerValue WHERE ParentID = @id ##WARNING## The above script will reset BaseValue to 0 this may impact on any previous Meter Readings.  Please contact Product Support to discuss this if you have concerns before applying this script.