Building Automation Knowledge Base

Issue The electrical contractor failed to pull an ground conductor with the controller power conductors.   Environment Controller installation. Controller Power. Cause Electrical contractor neglected to include a ground conductor when running power to the controller panel. Resolution All installation for the entire Continuum and Infinity controller product lines indicate that the controller power terminal must have a true earth ground connected to the ground terminal. Continuum controllers require a true earth ground connected to the ground terminal of the controller power strip.  Controller grounding is essential and impacts the controller in several ways including sensor bus communication, input accuracy, processor function and output performance. Improper grounding can also, in some cases, cause damage to the controllers.   The problem with grounding to the electrical enclosure or to the building structure is that each grounding point can have different  a ground potentials. This will especially cause issues with bus communication since all controller signals must be established with respect to the same ground reference. If each controller has a different ground reference the wave forms will be inconsistent.  

Issue Is there a way to display the value of a doors ADA output or to use this value in a Plain English program? Environment ADA output Door attributes Cause Need to display and track the value of a doors ADA output. Resolution There is no sanctioned way to access or use the value of a doors ADA output.  While in some cases it may be possible to create a separate output object with the same channel number to track this value, this kind of configuration is known to have issues and it is not recommended.

Issue The configuration in "License Setup" changes autonomously meaning that you open "License Setup", make a change, close "License Setup", open "License Setup" and the configuration has reverted to what is was before the change was made. It reverts back to what it was before making the change. Environment TAC Vista 5.1.9 Cause The cause of this is unknown. TAC Vista Server is supposed to set some values in the registry while running also regarding licensing, but not like described here. Resolution Make sure TAC Vista Server is stopped while changing the license setup: Stop TAC Vista Server Change the license setup Start TAC Vista Server

Issue Windows reports that RAM services do not start or stop in a timely manner Environment RAM 2.1.025 Cause Windows reports that RAM services do not start or stop in a timely manner. Re-installing RAM does not resolve the issue Resolution The issue may be with the RAM configuration file (setup.mdb). Note: If possible, record the RAM setup by opening the RAM console. Uninstall RAM and locate and delete or save the Remote Alarm Manager folder to a different location. Reinstall RAM. RAM will need to be re-configured with the site setup.

Issue On a MULTICAL 66, the Lon card is broken and needs to be replaced. Does the MALON BASE card fit the older heat meters? Environment MELON BASE MULTICAL Cause Unfortunately the LON card we have today for the newer MULTICAL 601/602 will not function with the old MULTICAL 66 meter types. Resolution Please contact local Kamstrup Service channel.

Issue I/A Series G3 Enterprise Network Server output window displays the following error: java.io.IOException: Negative seek offset. java.io.IOException: Negative seek offset at java.io.RandomAccessFile.seek(Native Method) at com.tridium.history.io.FileRandomAccess.seek(FileRandomAccess.java:118) at com.tridium.history.file.recstore.RecordStore.writePage(RecordStore.java:561) at com.tridium.history.file.recstore.RecordStore.newLastPage(RecordStore.java:631) at com.tridium.history.file.recstore.RecordStore.getWritePage(RecordStore.java:606) at com.tridium.history.file.recstore.RecordStore.append(RecordStore.java:222) at com.tridium.history.file.recstore.BRecordStoreHistoryTable.doAppend(BRecordStoreHistoryTable.java:175) at com.tridium.history.file.BFileHistoryTable.append(BFileHistoryTable.java:803) at com.tridium.history.db.TableHandle.append(TableHandle.java:203) at com.tridium.history.db.BLocalDbHistory.append(BLocalDbHistory.java:393) at com.tridium.driver.file.history.BDelimitedFileImport.appendToHistory(BDelimitedFileImport.java:796) at com.tridium.driver.file.history.BCsvFileImport.executeFileImport(BCsvFileImport.java:212) at javax.baja.driver.file.history.BFileHistoryImport.doExecute(BFileHistoryImport.java:90) at auto.com_tridium_driver_file_history_BExcelCsvFileImport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1217) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1046) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.Worker.process(Worker.java:161) at javax.baja.util.Worker$Processor.run(Worker.java:134) at java.lang.Thread.run(Thread.java:619) Environment I/A Series G3 Enterprise Network Server (versions prior to 3.4.54) Cause The error indicates that a history has become too large where the source .hdb file has exceeded 2GB making the history become inaccessible.  Versions prior to 3.4.54 used a Java integer as the offset into the page file of a history and the negative seek offset error is caused by a math rollover calculating a negative number. Resolution Two options to correct: Review the current size of the audit histories, log histories and any string logs to see which one is at the 2GB limit and perform some history database maintenance to trim the size down. Upgrade to the latest maintenance build of I/A Series G3 (3.4.54 or higher) where Java long calculations are used for the offset.

Issue The paper version of the WorkPlace Tech Tool license request form includes the 815-637-5331 fax number.  This number has been disconnected and is no longer in service. The Schneider Electric Park Plant Customer Care Center has been relocated and the 815-637-xxxx series phone numbers have been disconnected. Environment WorkPlace Tech License Request Fax and email information Cause Incoming faxes to the Schneider Electric Buildings Customer Care Center are now handled electronically. Resolution Use of email is the preferred method for submitting a WorkPlace Tech Tool license request form although a fax number is still available. The preferred email address is IASeries.License@schneider-electric.com If it is necessary to fax the license request please use +1 888-560-3636.

Issue When backing up user names and passwords, what files / folders need to be copied? Environment User Names Passwords Cause Replacing the Sigma server PC and upgrading at the same time, what files should be copied? Resolution The Passwords / User names are stored in two locations in the Sigma/Data folder.   The following files / folders should be copied; All files located in the User folder. GenCNF.rec

Issue The customer reported the schedule not work properly randomly, especially the holiday events not executing correctly. One item of error log 1465 was logged every 10 minutes. Environment CX9900/9940 i2 controller with version 3.2x Cause Some controllers with special version contribute to error log 1465 significantly, possibly impacting on the schedule event downloading Some i2 controllers with lower version firmware cause the schedule not to work correctly. Resolution Upgrade the CX controller to the latest version firmware. Upgrade all the i2 field controller to the late version firmware 3.300008

Issue The ACX57xx controller datasheet does not specify the AC power voltage range/ tolerance. Environment ACX ACX5740 ACX5720 Cause The DC power input specifies the voltage range on the datasheet. No documents specify the AC voltage range. Resolution You can power the ACX57xx controllers from either AC or DC power. The DC range is 12VDC - 28VDC. Max' power consumption = 50W. The AC voltage is 24VAC +10% -15% 50/60Hz. Max' power consumption = 90VA Giving an AC voltage range of  20.4VAC - 26.4VAC.

Issue Graphic pipes are missing from Px pages when viewed via a Web Browser, however pipes are displayed when viewed via WorkBench. Environment Niagara G3, ENC-520 Cause The needed kitPxHvac module was missing from the ENC-520. It seems the kitPxHvac module was not installed to the ENC. Usually all required modules are automatically installed to the ENC at the time of a station install, but for some reason the kitPxHvac module was not installed. Resolution Manually install the kitPxHvac module to the ENC - Open the Application Director window for the ENC hosting the graphics - Double-click on Software Manager - Select the kitPxHvac module from list and click the “Install” button at the bottom of the screen. - Click the “Commit” button to install the kitPxHvac module to the ENC A reboot of the ENC should not be required. Open a new Windows Browser and browse to the ENC. The pipes should now display correctly in the graphics.

Issue Automation Server stuck in Reboot Cycle Environment Automation Server Cause This experience is not typical so below is a list of solutions that have worked in the past. Resolution ES - AS Communication Issue - This fix works when the boot cycle only occurs while the ES is online. You can prove this is the case by stopping the Enterprise Server through software administrator, then attempting to log into the AS Log into the Enterprise Server Click on the Root Server Object in the System Tree Pane Click on the Communications tab Verify that the listed IP address for the Enterprise Server matches the IP address of the machine In the System Tree Pane, expand the Servers folder Delete the Affected Automation Server. NOTE: This will break all binds to/from this server. Log out of the Enterprise Server and Log into the Automation Server to verify that it is stable. Log out of the Automation Server and back into the Enterprise Server Re-add the Automation Server to the Enterprise Server

Issue Schneider Electric MTN881001 or the SVEA LON I/O Module DR-N 3DIM 1-10V. Changing the SNVT nviLALampValue_? does not give the expected output. Environment MTN881001 SVEA 36237-552 Cause Changing the SNVT nviLALampValue[i] to the following values, shows the following VDC volt on the analog output: nviLALampValue Analog output 100.0 1 -  9,94 VDC 80.0 1 -  7.65 VDC 60.0 1 -  6,75 VDC 50.0 1 -  6.25 VDC 20.0 1 -  4.86 VDC 1.0 1 -  3.97 VDC When nviLALampValue is 50.0 1, the analog output is 6.25 VDC (not proportional) and the minimum analog output value is 3.97 VDC, which does not make sense.   Resolution The module is using a logarithmic behaviour for the 1-10V output as default. This is because the device is mostly used for fluorescent lamps. You can change the behaviour by using the UCPTadaptationTable in the lamp Actuator object. UCPTadaptationTable consists of 21 values representing the digits (from 0 to 255) for the output value in steps of 5%. This means:   first value: 0% second value: 5% third value: 10% ... 21st value: 100% To get a linear behaviour you should set as follows: first value: 0 second value: 13 third value: 26 ... 21st value: 255

Issue After upgrading a TAC Vista system on a site with high IT security you can end up with a wrong schema version in the SQL database causing issues such as failure to insert trend log data. Environment TAC Vista SQL Cause In some versions of TAC Vista, the SQL database upgrade carried out during the installation of TAC Vista doesn't upgrade the SQL database to the newest version. The first time you start TAC Vista Server, the server (TACOS) carries out the remaining upgrade steps. On a site with very high security standards, TAC Vista Server is however not able to apply the last SQL database upgrade scripts as those can only be carried out by the IT department directly on the SQL server, and as a result the SQL database is not fully upgraded. Resolution   1.      Note exactly what schema version the SQL database currently has This can be checked through SQL management studio with this query USE taclogdata; SELECT dbo.DSS_SchemaVersion() AS Db_SchemaVersion 2.      Note exactly what version of TAC Vista you have upgraded to 3.      Contact PSS to get a SQL upgrade script specific for the site and run that on the SQL database

Issue How to change the Standby image on a SE8000 controller to something other than standard factory image Product Line EcoStruxure Building Expert, Field Devices Environment SE8xxx range Cause The standard standby image for the SE8300 does not meet the customer requirements Resolution See the link below to the Exchange for the software and instructions on how to perform this process. Reference page 4 of the Uploader Tool - SE8000 Series Room Controllers.

Issue Reportserver does not delete the trend data when an extended trendlog is deleted in StruxureWare Building Operation. Environment StruxureWare Building Operation Webreport SQL Cause When an extended trendlog is deleted in StruxureWare Building Operation, its corresponding data in webreport server are not deleted. This means that when you want to look at a trend in the reportserver you will still see the deleted trendlog. No new data are collected but the previously collected data will be there. Resolution This is by design. The historical data are not deleted from SQL; however,  a side effect of this is that the webreport interface will still show the extended trendlog after it has been deleted in Workstation.

Issue Does the LCM driver support tunneling? Product Line TAC IA Series Environment R2 UNC with LCM driver Cause Tunneling is needed to make programming changes to the LCM's. Resolution It is possible to tunnel through the UNC to the LCM's, but it requires an RS-232 connection from the UNC to one of the LCM's.  See the LCM Integration Guide F-27422-2 for details.

Issue Need to use a controller that has no BACnet functionality due to network security limitations on site. Environment Continuum bCX1-CR-INF (bCX9640) Cause A customer has a site with restrictive network security requirements and BACnet devices (or any other open protocol) are not allowed. Resolution The bCX9640 is an Infinet protocol controller only. This version of the bCX firmware does not have the BACnet stack installed, and there are no BACnet points able to be created in this controller. You will be fine to use this controller where BACnet support is not required or allowed.

Issue One of the following errors is thrown by the Hasp Key Utility when attempting to update the Continuum License key using the V2C file received from Schneider Electric. Invalid Parameter Update failed: KeyIdNotFound Product Line Andover Continuum Environment Continuum 2.0 Hasp Key Utility License Cause The V2C file that was emailed to the customer is corrupted. When Web based email is used to receive the v2c file from Schneider there have been cases where the file is not received in its original form.  When this happens the file size of the attachment appears to be correct.  When the c2v file is save to a folder on the workstation PC however, the file size reported is 0kb.  Resolution The solution to this is to use a non-web-based email application like Outlook or Outlook Express. 

Issue Troubleshooting 4417 DEVICE_ERR_NOADDR_I2C errors seen in Controller's Error Log. Environment Continuum Controllers Cause 0x00004417 0x00002100 0x021046e2 0x00080002 0x000000200x00004417 0x00002100 0x021046e2 0x00080002 0x00000020 "DEVICE_ERR_NOADDR_I2C" errors are related to the internal bus to the peripherals and RealTimeClock.   DEVICE_ERR_NOADDR_I2C       (no address response)      “DEVICE_ERR_NOADDR_I2C” errors are not I2 errors they are I2C errors. These errors are related to the internal bus to the peripherals (like an onboard RealTimeClock or the expansion bus (modules)).   There may have been an expansion module installed that has been removed while a PE program is still accessing an I/O on the module. Resolution Possible causes can be:   1. A defect with the onboard RealTimeClock. Check for 4417 errors followed by TimeSync errors and/or indications that the time clock is not stable similar to the following error lines.   01/01/1989 00:00:00.00 0x00004417 DEVICE_ERR_NOADDR_I2C (no address response) 01/01/1989 00:00:00.00 0x00010000 Clock change   2. An issue with the expansion bus modules. There may have been an expansion module installed that has been removed while a PE program is still accessing an I/O on the module.