Building Automation Knowledge Base

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.

Issue Integration to the Veris H80xx Entercept power meter with the Xenta 5/7/9xx and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Veris H80xx Entercept Power Meter Cause Integration instruction and programming example for integration to the Veris Entercept power meter. Resolution Please use the following .dev files as a starting point and a guide to the integration of a 100 amp or 200 amp Veris Entercept meter. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes to the modbus mapping or this supporting document for data scaling changes. If mapping for larger amp meters is needed, please contact product support.   100 AMP .dev file 200 AMP .dev file   To use these files in XBuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on the harddrive. In Xbuilder, right click on the Modbus Master device and choose Add Device Browse to the needed .dev file and click Open. Rename the newly added device to a unique name within the Modbus Master network.   Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template.  

Issue Sigma Web Graphics must be installed as an Administrator, but most users do not have these rights. Environment Sigma Sigma Web Server Cause As most network users do not have Admin rights, there is a need to install Sigma Web Graphics across the network. Resolution The following text has been provided by the Sigma programmers and should be understood by the IT professionals. First you need to create a response (answer) file Then play back the response (answer) file  in silent mode To review the InstallShield Setup Parameters.pdf, please Click Here.

Issue Configuration of the OPC Server PC DCOM settings. Environment Sigma ModBMS OPC Server DCOM Matrikon Cause The OPC values could be viewed correctly via an OPC client on the local PC, but could not be viewed by another OPC client across the network. Resolution Configure the OPC Server PC as detailed in the Matrikon OPC document. Click HERE to download this document. To download the Matrikon OPC Client software, please click HERE. Having configured the OPC Server PC DCOM settings, start the MatrikonOPC Explorer programme. In "Network Neighborhood" locate the OPC server PC, and select "ModBMS-OPCserver" Using the RH mouse button, select "Add Group" from the menu. Name as required. Add the required tags to the group. Validate the Tags Using the RH mouse button de-select "Use Async I/O"   The OPC value is now displayed.

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 Continuum cardholders with PINs that start with "0" (zero) are not importing into Security Expert using Data Sync Tool Product Line EcoStruxure Security Expert Environment Security Expert Continuum Transition Cause Due to the database's configuration, Any PIN in Continuum starting with a "0" (zero) will be truncated. When DSS runs, the personnel (cardholders) with truncated PINs will be rejected by the PIN length restriction and sent to the error folder. Example: If you have a Continuum site with four-digit PINs and a PIN is entered into Continuum as 0123, will be truncated to 123 in Continuum (Continuum ignores the zero at the reader keypad as well). If you have SX configured for a 4-digit PIN length. This cardholder will not import. Resolution Option 1: Identify the truncated PINs in the Continuum database by running a query and have those users' PINs updated before running CTT and DSS. This should be done as part of your system cleanup before transitioning. Option 2: If you have a minimum PIN length configured in Security Expert, Stop DSS if running. Go to Global|Sites|Site Defaults tab and scroll to Site security enhancements. Set minimum PIN length to "0". Save changes. Start DSS. You will still have to correct any PIN that are less than the site minimum before enabling this feature again.       Note: This option should only be chosen for a one-time sync. If you are running a continuous/lengthy transition, you should use Option 1. Otherwise, you will run into this problem again.

Issue Search for all inputs and outputs in a system that are forced by operator Find IOs that are set in manual override Product Line TAC Vista Environment TAC Vista Workstation Cause Need to find all Inputs/outputs that are set to Forced by operator (manual override). Resolution In Workstation, right click on the Lonworks object and select search. In type of devices or objects select Analog/Digital input and/or Analog/Digital outputs.     Select property value 'Forced by operator' and Select equal to 1.     (To be able to set the property value 'Forced by operator' specify Analog/Digital input and/or Analog/Digital outputs, not just Points in 'type of devices or objects'.)

Issue If the WorkPlace Tech Tool application file has been modified when you attempt to monitor a controller containing that application, blank or incorrect monitor tag values will be displayed. Environment WorkPlace Tech Tool software versions 5.0 through 5.8.2 or 5.8.6 MNL or MNB controller loaded with an application downloaded from WPT Visio 2003, Visio 2007 or Visio 2010 Cause There are two causes: First, the WPT software, release 5.8.3, 5.8.4 or 5.8.5 will modify the application when it is opened making it appear to be different than the previously downloaded application Second, failure to observe the following three constraints, regarding the application .vsd file will make the application file appear different than the application previously downloaded: The application file (.vsd) must not have been modified and/or re-saved in any version of the WorkPlace Tech Software since the application was downloaded. The application file (.vsd) must not have been modified directly in Visio and re-saved. The application file (.vsd) must have been last saved, compiled and downloaded using any version of the WorkPlace Tech Tool software, 5.0 through 5.8.2 or 5.8.6, running in Visio 2003, 2007 or 2010.   Resolution An application downloaded to an MNL (or with the compatible WPT version, MNB) controller can be monitored provided that the application .vsd file has not been modified or re-saved after download and that the current version of the WorkPlace Tech Tool software, versions 5.0 through 5.8.2 or 5.8.6 (not versions 5.8.3, 5.8.4 or 5.8.5)  is being is being used with a compatible version of Visio (2003, 2007 or 2010). NOTE: For MNB controllers this applies only to WPT versions 5.7.0 through 5.8.2 and 5.8.6 as the earlier versions are not compatible with MNB application development.

Issue The value of DateTime will different depending on how the variable is declared Differences between DateTime declared as a local variable and as input, output or public in Script program Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Script Editor Cause Local and bound variables will initialize differently Resolution Local DateTime variables are local and known only to the Script program or function, and are initialized to the current local date-time value of the sever in which they  execute. Binding variables, including Input, Output and Public variables, are not effected by the Script engine by default. The EBO system uses the 1/1/1970 date as default and the Script simply uses that. If a different initial value is required then one can be set in the script

Issue "No license available" message appears some while after having logged in to Webstation. Product Line TAC Vista Environment Vista 5.1.6 Windows 2008 Server Internet Information Services (IIS) IIS 7.0 or higher Cause This is most likely due to a corrupt IIS installation. Resolution Reinstall IIS Reinstall Webstation The steps for this are outlined in Problems installing Vista Webstation 5.1.5 or newer.

Issue When reloading a Net Controller II you receive an OMS error. A send to database doesn't complete Environment Continuum 1.92 Windows XP NetController 1/II Cause Programming Busy Controller Resolution First Method: Go to off line editing. Export the programs and save them to the desktop. Delete the programs. Go onLine. Reload the controller. Go to off line editing. Import the programs for the saved export file. Go onLine. Reload the controller. Second Method: Go to off line editing. Web over to the NCII  http://ip-address Select  "Clear Database Backup" Commit Changes. Go Online. Reload the Controller. Note: At times if the reload is still not working and is failing on certain objects, reloading class by class allows the reload to go through. Delete programming half of the code at a time to find out what code is causing the issue by process of elimination. Use a laptop with wireshark installed and a hub and connect to the NC directly and try the reload or send to db and examine the capture. Replace the controller and see if it works, if so, the controller may need to be permanently replaced.

Issue When integrating a Integral DVR system Vista crashes Video does not work in Vista CCTV video loss in Vista Product Line Pelco, TAC Vista Environment Vista 5.1.3 Vista Integral DVR SDK v6.6.1.57 Integral DVR SDK v7.0.8 Cause Vista uses the same SDK as Controlpoint uses for an Integral DVR system, this mainly means that Vista SDK needs to be at the same versions as Controlpoint's SDK. A good example of this would be that Vista 5.1.3 use SDK v6.6.1.57 and Integral Digital sentry 7 use a newer version of SDK that is not compatible with SDK v6.6.1.57, a integration of this system then causes Vista to crash. An integration with Vista 5.1.3 would need Integral Digital Sentry 4.1/4.2. Please reference Vista Video Compatibility for more information. Vista 5.1.5 has SDK 7.0.8.0 and it appears that HD support was not included prior to SDK7.0.24.0 Resolution Make sure you have the correct version of Integral Digital version versus Vista version.     5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0   Integral Digital Sentry 4.1/4.2 X X X X X X           Integral Digital Sentry 7 X X    

Issue As a last resort when a Cyberstation is offline or there are difficulties connecting to a database, it is necessary to change the Workstation Initialization fields using the Windows registry. Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Partial objects in a database and registry entries occasionally get out of sync. Resolution Caution! Editing of the registry can be potentially dangerous, make sure someone who is familiar with using regedit completes this procedure. It is best to get a restore point of the Windows PC, if the version allows, prior to taking the following steps. Shutdown Cyberstation From Windows, Start> Run> Regedit Expand the hives(folders) to HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls Right Click on Andover Controls and select export, name the file and save. (This file can be used to restore the original settings of this branch) Expand the folder to HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls\Continuum\Settings Double click on Workstation Name (Change this to the name required Ex. WS1) Double click on Network Id and select decimal (Change value data to the number needed Ex. 192) Double click on Device Node Id and select decimal (Change value data to the number needed Ex. 192) Double click on Container Name (Change this to the name required Ex. WS1folder) Close Regedit Go into database initialization and select Workstation and you will now see those settings there. Go to the database tab and enter in the password for andover97 and click Ok. If the database initialization screen comes back(resolves to the database)with no errors, then this new instance of the Workstation was successfully created in the database. Launch Continuum Note: On a 64- bit system the registry location is slightly different. HKEY_LOCAL_MACHINE\SOFTWARE\WoW6432Node\Andover Controls\Continuum\Settings   Continuum queries to get some of the Workstation Initialization parameters (Comments in parenthesis are not part of the query) select  * from device  (Device is the table name, uiname is the column where the Workstation Name can be found) select * from container (Container is the table name, uiname is the column where the Folder Name can be found) select * from device (Device is the table name, networkid is the column where the Network ID can be found) Device ID is not available, but is often the same as the Network ID

Issue Operating Systems and SQL Supported in I/NET Seven 2.40, 2.40A, and 2.41 Environment Windows Server 2003 w/ SP1 Windows XP Professional w/ SP3 Windows Vista Enterprise w/ SP1 Windows 7 Professional 32-bit SQL Server 2000 Desktop Engine(MSDE 2000) SP4 SQL Server 2000 Standard SQL Server 2000 Enterprise SQL Server 2005 Express SP3 SQL Server 2005 Standard SP3 SQL Server 2005 Enterprise SP3 SQL Server 2008 Express (32-bit) SQL Server 2008 Standard (32-bit) Cause Issues may arrive if the I/NET software and SQL Server versions do not follow the below guidelines. Resolution  Click here to download this document in PDF format.     Operating Systems     Windows Server 2003 w/ SP1  Windows XP Professional w/ SP3  Windows Vista Enterprise w/ SP1  Windows 7 Professional 32-bit  SQL Server  SQL Server 2000 Desktop Engine (MSDE2000) SP4   Yes   Yes       SQL Server 2000 Standard   Yes         SQL Server 2000 Enterprise   Yes         SQL Server 2005 Express SP3   Yes   Yes   Yes   Yes   SQL Server 2005 Standard SP3   Yes   Yes   Yes   Yes   SQL Server 2005 Enterprise SP3   Yes         SQL Server 2008 Express (32-bit)         Yes   SQL Server 2008 Standard (32-bit)         Yes  General Notes: Do not mix versions of SQL server among equalized or client/server workstations in your TAC I/NET Seven system. Ensure that the edition of SQL server installed on each workstation used in a client/server or equalized setting are based on the same version of Microsoft SQL, either 2000, 2005, or 2008. It is strongly recommended that you defragment the PC's hard drives on a regular basis. Severely fragmented hard drives can cause poor system performance and in some cases can introduce data errors. The use of Microsoft SQL Server 2005 Standard or Enterprise edition, or any edition of Microsoft SQL Server 2008 will require that the PC have at least 2 GB of RAM. Microsoft SQL Server 2005/2008 Express Edition cannot be used on a TAC I/NET Seven filemaster.

Issue Receiving "Deny Entry Sched." (Schedule) transaction message for all individuals on a single Interface (SLI). Receiving "Deny Entry Sel." (Select) transaction message for all individuals on a single Interface (SLI). Product Line TAC INET Environment I/NET Seven Traditional Elevator Control Cause In traditional elevator control, the Reader (Door Point) must have a schedule assigned for the Group / Individual to allow access to the Lift (reader) itself. Then in Floor Maps you can allocate access to the individual Floor Points. In the floor mapping you must also remember to allocate the associated floor points otherwise the Individual is not Scheduled to have access to the floor (Hence a Deny Entry Sched message is received). Recommendation is to migrate sites to Extended Elevator Control which makes this process much simpler. For details of this refer to Extended Elevator control (Step by step instructions). Resolution Under Access Elevators check that the Floor mapping is correctly set for each Floor DO point. If no DO 's are selected for that particular Tenant Schedule, the individual will receive a Denied Entry Sched when attempting to gain access to the floor. Deny Entry Sel (Selection) is received when the Elevator Reader is not selected for the Tenant / Group or Tenant / Individual. A schedule (Group or Personnel) must exists on the reader (door ) point for the Group or Individual in question. A list of all Event messages, and their descriptions, received in AMT is available in AMT Event message definitions.

Issue The Application Director output window displays an Engine Watchdog Timeout by issuing a thread dump and displaying App Failed.  This condition can occur when installing an upgraded station, after a reboot of the existing station, or during normal station operation. Environment I/A Series G3, Niagara Cause The software watchdog mechanism is designed to periodically report the station's engine cycle count to the platform daemon.  The main purpose is to detect and restart a "stalled" station when the control engine is believed to be in a deadlocked condition.  If the station’s engine cycle count stops changing and/or the station does not report a cycle count to the platform daemon within this defined period, the platform daemon causes the VM to generate a stack dump for diagnostic purposes, then takes the action defined by the Engine Watchdog Policy. Depending upon station operation, the watchdog timeout may need to be increased to compensate for transient conditions where the NRE engine thread is temporarily busy during a single execution cycle.  These conditions include simultaneous execution of multiple objects or point extensions that occur on the same time interval, archiving of log history, custom objects, etc. during normal operation.  The default timeout is 1 minute. Resolution Tuning may be required (increase of the default watchdog timeout value). Open the running station, expand Config, expand Services, right click PlatformServices - View - Platform Service Container Plugin, locate the Engine Watchdog Timeout property.  Increase the value by 30 second or 1 minute increments and monitor controller operation (adjust as required).  If the condition continues, contact Schneider Electric Product Support for further assistance. Watchdog policy selections include: Log Only — Generates stack dump and logs an error message in the system log.   Terminate — (Default) Kills the VM process. If “restart on failure” is enabled for the station (typical), the station is restarted.   Reboot — Automatically reboots the host JACE platform. If “auto-start” is enabled for the station, the station is restarted after the system reboots.   Engine Watchdog Timeout — Default is 1 minute, and range is from 0 ms to infinity.

Issue How do the 7793 and 7798 handle retries?  Improving I/NET sublan communications Excessive MCU Lost messages in AMT Command Error messages in AMT Product Line TAC INET Environment I/NET sublan 7793, 7798 Cause If there are issues on the physical layer of the network, this will effect the reliability of I/NET communications. However, these risks can be lessened with some best practices. Resolution Best Practices and Troubleshooting measures to improve sublan communications: Ground the 24V line coming into MRs and ASCs Connect ground to the earth ground terminal of DPUs and SCUs. Bond the shield of the LAN cable all the way through the network, not landing it on any controller anywhere and then tie it to earth ground in one location. (see diagram)   SubLAN Communication Explained: The first packet to any sublan device goes out on the primary channel, terminals 1 and 2 of the sublan connector on the 93/98. If the device doesn't respond in time, a second packet is sent out on the alternate channel, terminals 4 and 5. If there is still no reply, a third packet goes out on the primary Finally, if there is still no reply, that device is marked as lost which generates an "MCU Lost" message. Optional Configuration for only using Terminals 1 and 2:  If you are using only Terminals 1 and 2 you could be missing 33% of it's retry capacity. If you follow wiring guides and best practices the device will answer on the first packet every time, however if you have not followed the guide all it takes is a little noise to make the retries necessary. If you are unable to use a loop configuration, or want to avoid the extra potential for noise and EMI, in stall a jumper on the sublan connector from terminal 1 to 4 and from terminal 2 to 5 The allows you to get the extra retry, without the extra cable This will also function if you have some controllers on channel A and some on Channel B The SLI doesn’t have to be at the end of line on sublan communication  

Issue In MNB-1000 (Plant Controller) firmware Revision 1.50E, the Spanning Tree Protocol is Disabled, by default. All previous versions were shipped with the Spanning Tree Protocol enabled. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, and later. Cause In some cases where multiple BACnet routers (eg, MNB-1000, UNC, ENC, etc) were installed on the same BACnet-IP internetwork, having the Spanning Tree Protocol enabled in the MNB-1000 would allow a "router loop". Resolution Be aware that in MNB-1000s with firmware Revision 1.50E and later, the Spanning Tree protocol is disabled, by default. Click here to see the Release Notes for firmware Revision 1.50E . It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue Loading or upgrading new firmware into a 102-AX VAV controller that resides under a Jace controller Environment Jace Vista Xenta 102-AX Firmware Cause Updating firmware in a 102-AX VAV controller that has previously been commissioned into an existing network Resolution Please click here to see a step by step procedure document on the recommended procedure for this task.