Building Automation Knowledge Base

Issue If using V231 DN25 and a Forta M800, what is the max ΔPc? Environment Forta M800 V231 DN25 Cause In case the ΔPc is too high, the Forta may not be capable of controlling the valve properly. Resolution The combination of V231 DN25 and M800 should have a max ΔPc of appr. 1150kPa (11.5Bar) For more information and details regarding the different applications, please see the data sheets for each product involved.

Issue Points can be overriden in the field using PSI; have verified the standard 'USER' and 'PASS' login for all Microzones and the LCM; the GCM is able to be downloaded successfully. Still having trouble with overriding points in a Microzone II via TreeTech. It returns error 'no user found'. Environment TreeTech Network 8000 Microzone II under GCM Cause The date in the GCM & any Microzone/PEM controllers must match that in the PC with TreeTech since the password to access the controller is calculated based on dates. Resolution The date in the GCM & any Microzone/PEM controllers must match that in the PC with TreeTech since the password to access the controller is calculated based on dates. If TreeTech can't Login, you can't override the MZ2. Check the dates in the PC and all devices match and correct if necessary.  

Issue Is there any Belimo PICCV equivalent in Schneider Electric portfolio? Environment Belimo PICCV Cause Looking for a SE equivalent product to the Belimo PICCV line. Resolution Unfortunately we do not have any matching products in the Schneider Electric portfolio

Issue Get "An unhandled exception occurred in the application" when browsing objects from Vista's OPC server. Vista OPC server (TACOPC.exe) crashes when browsing tags on an OPC client. When checking with OPC tool, the server (TAC Object Server OPC DA) can be browsed but when opening folders the Vista OPC server crashes. Environment TAC Vista 5.1.X Vista OPC server 1.6.X OPC tool 3rd Party OPC client. Cause Incorrect characters such as '\" (backslash) have been used in either the folder names in Vista or the variable names. Resolution Rename the variables/folders avoiding special characters such as '\', '#', '/ ' etc.

Issue How many LonWorks groups is it possible to have in one LON network in Vista? Environment LNS Vista networks Cause When designing a LON network, it is important to consider both the physical and the logical organization of the network. When dividing controllers into logical LonWorks groups, the limitations should not be exceeded. Resolution There is a limitation of 50 LonWorks groups in one LON network.

Issue What is the best way to remove a version of R2 software from a PC? Environment I/A Series Niagara r2 Cause A formal uninstaller does not exist. Resolution Stop the Niagara service Delete the r2.301.XXX folder containing the version you wish to remove.

Issue Attempting to view I/A Series G3 graphics via browser. Error indicates HTTP 501 "Not Implemented" error with the message "Module content filter excludes user interface packages." Environment I/A Series G3, ENC-410, ENC-520 Cause When an ENC is accessed from a browser, it is necessary that the user interface packages be available to correctly render the web-based display.  When these packages have been filtered out, the browser will report an HTTP 501 "Not Implemented" error with the message "Module content filter excludes user interface packages." Resolution To correct the module content filter must be changed to include the UI package and the associated modules must be re-installed. Open the platform for the ENC and run the Commissioning Wizard. Clear all selections and enable "Select module content filter level." Step through the commissioning process and change the Module Content Filter Level to UI+RUNTIME. Continue through the commissioning process and Finish to install the UI modules.

Issue Modbus values are not not working reliably and are not updating as expected. Product Line Andover Continuum, TAC INET, TAC Vista Environment Xenta controllers 511, 527, 701, 711, 721, 731 and 913 Cause The amount of Modbus points being polled is excessive for the controller. Resolution The product data sheets indicates no limit to the Modbus points but only 31 Modbus devices over RS-485. With a practical install, a limit of 300-400 Modbus points per Xenta server  would be applicable. If you exceed this level, communications become slower than acceptable. Network performance can be affected when a large number of connection objects are in use ( direct transfers between Modbus and other protocols). There is no documented limitation, but the recommendation is not to exceed 300 connection objects per Xenta Server. Connection polling period should also be considered with a large amount of connection objects.

Issue What to do and who to contact when a controller needs to be repaired or upgraded. Environment All Product Repairs Cause Require information on what to do and who to contact to arrange repairs of defective product, order Controller option upgrades, order Cyberstation option or software version upgrades. Resolution   PROCESS FOR CONTINUUM REPAIRS   NOTE: Repaired items are set-up in Pronto with the part number prefixed by “4-“. This is done to allow visibility for follow-up if required and costing.   Engineer completes “Andover Continuum Hardware Return Authorisation Form”; one for each controller requiring repair. Email completed form/s to TAC AP – Logistics Replenishment ( NOT the US Repair Centre). Do nothing with the controller/s at this stage. Logistics email the completed forms to US Repair Centre requesting cost to repair and turn-around time. Repair Centre replies with cost, turn-around time and RA number/s Logistics pass this information to the requesting engineer who will decide Y or N. If yes, the engineer enters a Sales Order in Pronto, informs Logistics and forwards the goods to Melbourne DC. Logistics raise a Purchase Order on Repair Centre and instruct Melbourne DC to despatch goods. After the goods are repaired they are returned to Melbourne DC where they are receipted and despatched to requestor.   Repair Forms Fill out one of the forms below (whichever applies) and send to local Logistics. Andover Continuum Return Authorization Forms - Americas & APAC OR Andover Continuum Controller Upgrade Forms - Americas & APAC

Issue Material specification for nickel plated brass sensor pockets Product Line Field Devices Environment Sensor pockets Cause Some customers require a specification on the material used for the sensor pockets in nickel plated brass. Resolution Brass nickel plated: Turned part: Ms 58 (Cu Zn 39 Pb3) Pipe + lid: Ms 63 (Cu Zn 37) Surface nickel plated. Guidelines for nickel plating: Galvanica nickel plated ( ca. 6 – 12 µm)  

Issue Cannot login with Admin level Continuum user.  Password either lost or restricted by Object Level Security. Environment Continuum CyberStation WebClient Cause Admin level user password has been changed and/or forgotten. Object Level Security is inhibiting access to Continuum Users. Resolution Contact Schneider Continuum Product Support Services to arrange to have database sent in for repair.  The cost of this repair varies depending on the nature of the problem.

Issue A project specification requires compliance with BACnet Specification Annex J. Is Continuum compliant? Environment CyberStation B-OWS bCX Cause A project specification has the following in it: Operator Workstation: Provide operator workstation that complies with Annex J of the BACnet specification for IP connections. This device shall use Ethernet to connect to the IP internetwork, while using the same Ethernet LAN for non-IP communications to other BACnet devices on the LAN. Workstation shall support Foreign Device Registration to allow temporary workstation connection to IP network. Resolution This is saying the BACnet workstation (B-OWS) must communicate to both BACnet IP devices and BACnet MSTP devices. CyberStation communicates over IP to BACnet IP devices and through a bCX or other BACnet gateway to the BACnet MSTP devices. CyberStation does support Foreign Device Registration. CyberStation does meet this specification.  

Issue "Cannot paste. /tridium/props/error.properties#error.E_RC_TO_NODE" when trying to paste a Lon shadow object into the workspace of an UNC. Environment Niagara R2 UNC-410 UNC-520 Cause There could be two possible causes for the error message. One possible cause is that the Lon jar file which contains the shadow object was updated on the WorkPlace Pro PC, but the updated module was never installed to the UNC. The other possible cause is that the updated Lon nt jar file was not installed in the \nre\modules folder of the WorkPlace Pro PC. Resolution There are two things to look into. Perform both procedures 1 and 2 only if the lon nt jar was not installed/upgraded to the nre\module folder.  If all of the Lon jars are installed/upgraded correctly (Lon nt jar file installed to nre\modules folder) on the WorkPlace Pro PC, then only procedure 2 needs to be performed. Procedure 1 If the lon nt file was not installed/updated to the \nre\modules folder, use the following steps to do so. These steps assume that the updated Lon nt jar is already installed on the WorkPlace Pro PC, but not it was not installed to the nre\modules folder. Stop WorkPlace Pro. Open the Niagara\build\nt and copy the Lon jar Open the niagara\build\nre\module folder and rename the Lon jar in question “.old”. Paste the copied Lon jar to the module folder and restart WorkPlace Pro. The module will now need to be upgraded to the UNC. See above steps for procedure. Procedure 2 If the UNC Lon module has not been installed/updated to the UNC, use the following steps to do so. Open the Admin Tool. Open a connection to the UNC Select the "Installation" tab then click the [Installation Wizard] button. Select the "emb" folder in the "Select Distribution Directory" window then click [Install] In the "Niagara Remote Installation" window, select the "Configure Modules Only" radio button then click the [Next >] button. Verify that there is a checkmark in the "Upgrade/Add" column for the updated lon jar file. Click the [Next >] button to continue. Make sure that on the "Database Backup" screen that you do backup the existing database. Continue through the remaining steps and allow the upgrade to install and the station to restart. You should now be able to paste the shadow object to the WorkspaceEditor view.

Issue A Niagara R2 station is being upgraded from version 431 to 529.  A copy of the station from 431 is successfully converted to xml.  However, the config.xml does not convert to a config.db or a config.sns in version 529. The following error appears in the conversion window: ------- Errors ------- ERROR: c:\niagara\r2.301.529\stations\Blake\config.xml(630110,66):    Could not parse value.    Invalid dateTime "60356-06-20T10:54:24.17-7". Parse of XML failed. ----- End of input ----- Environment Niagara R2 all versions Cause Somehow, an incorrect date reference was registered in the station.  It may have occurred during the creation of the config.xml. Resolution Using a XML editor utility (ie: Notepad++), modify the date so that it reads "2011" instead of "60356". from:  <lastDailyArchive>60356-06-20T10:54:24.17-7</lastDailyArchive> to:      <lastDailyArchive>2011-06-20T10:54:24.17-7</lastDailyArchive> Run a conversion again.

Issue Need an indication when the SQL Server has a hardware or a network failure and is unable to communicate to the Continuum Cyberstation's. Environment Continuum Cyberstation SQL Server Cause Customers IT Department wants to know when the Continuum SQL Server has a hardware or a network failure and is unable to communicate to the Continuum Cyberstations. When Cyberstation loses the connection to the SQL server it loses all functionality and will not be able to send alarms as emails to annunciate that there is a problem. Resolution The best solution for this is to monitor the Server and/or Workstations to determine if they have failed by using SNMP traps that feed back each systems status into the existing IT monitoring systems (assuming they already monitor SNMP traps on their other equipment). On Windows Server you can setup traps to monitor specific applications on remote PC's as well as the general on/off state of that PC. See Microsoft article below as an example of this. http://support.microsoft.com/kb/324263 Alternatively, when the SQL server goes offline to the Workstations running the Continuum application, the workstations will see that the server has gone offline and raise a disconnection message at the Workstation. Continuum will attempt to re-establish this connection to the server, if it is unsuccessful then the application will close. If they monitor the Workstations continuously then this message can be seen on the Cyberstations and would be another visual indication that the connection to the server has been lost.  

Issue How can I delete logging configuration from a controller, in release 4.04? Environment Sigma Release 4.04 4.04 Logging Data set Cause Sigma 4.04 does not provide an option to download an empty logging configuration file. Resolution The easiest way is to delete the logging configuration from a controller is as follows; Select the Sigma "Logging configuration" option and then delete the unwanted logging data set. Using Explorer, go to the appropriate controller folder and delete the logging config file, ( an example of this file could be  T0025400.100, where T00254 is the server and 00.100 is the controller). In Sigma "System Diagnostics" select to download the logging config to the appropriate controller. Another way to delete the configuration could be; Select the Sigma "Logging configuration" option and then select and open the required log data set. Delete all of the objects in the log dat set, except one, and then set that to log very infrequently, save and download in the normal way. If you wished, you could then delete the log data set. This will mean that the controller will still be logging one object, but very infrequently. If you have deleted the data set, then the next time the controller files are downloaded, the logging will be removed. 

Issue Is a Continuum Security Key required on every Continuum Cyberstation? Environment Continuum Cyberstation Cause Several workstations on site and only purchased one key. Resolution One Continuum Cyberstation security key is required for each Continuum workstation.

Issue Unable to commission an I/A Series JACE-6 or JACE-7. The commissioning wizard cannot locate the sun-jre-qnx-ppc distribution file required for the installation process. Environment I/A Series G3, JACE-6, JACE-7 Cause The sun-jre-qnx-ppc distribution file was not included in the initial TAC release of build 3.6.31.6.  in addition, the Sun Hotspot Virtual Machine (JVM) for the QNX operating system included with the 3.6.31.6 build was found to have timing issues. Review TPA-IA-11-0005.00 for more details. Resolution The initial TAC release of build 3.6.31.6 was removed for download within a few days of original release.  The software was replaced by TAC build 3.6.31.7 (dated 09/29/2011). For those using I/A Series G3 Release 3.6 you must take the following actions: Discontinue using G3 release build 3.6.31.6.   Download and install the latest build, G3 release 3.6.31.7 from The Exchange Download Center.   For those instances where deployment has already occurred in the following JACE platforms JACE-6 or JACE-7, an upgrade to G3 3.6.31.7 is required. Note: The version of the Sun Hotspot JVM can be verified using the Workbench Platform tool – Platform Administration. The Java Virtual Machine (sun-jre-qnx-ppc) should indicate Sun Microsystems Inc 1.5.0.16.21 or higher.   The Enterprise Network Server, ENC-410, ENC-520, and JACE-2 platforms do not utilize the Sun Hotspot Java Virtual Machine (JVM) for QNX.  These platforms are not affected by the issue. However, it is strongly recommended to upgrade to G3 3.6.31.7 to maintain compatibility with the same version of Workbench and associated files.

Issue This problem happens when all the machines located in the same domain, but there is something wrong with the domain configuration, you can also access the data directory under Microsoft SQL server and you can ping the server machine ,even you can update the database successfully, but when you set up the workstation you will fail and get an error like this "Continuum Initialization encountered a problem, need to be closed......" Environment Windows 2000 server sp4 SQL server 2000 sp4 Windows XP professional Continuum1.52 Cause There might be something wrong in the configuration of the domain server Continuum 1.52 can't be supported by Windows XP Resolution Quit out all the machines from the domain and add them into a workgroup to verify the problem caused by wrong domain configuration. Rebuild the machine and install Continuum 1.52 on Windows 2000 Make sure you can set workstation correctly on Windows 2000 and have all the machine in a workgroup Re-configure the domain correctly Re-install SQL server on the server machine Try to set up the workstation again.

Issue Vista - Log database offline Access denied Environment Vista SQL Cause Receiving an alarm in Vista about "log database offline," means that the DSS writer has somehow failed to read to SQL Database. Every time this happens,  an application event should be created in the Windows Event View. It can be caused by several different reasons, but the most common are: SQL is not reachable A virus scan is under progress for the created event under the $queue folder Resolution These steps may vary slightly depending on the operating system installed on the PC. These steps describe the process in Windows XP. Highlight "My Computer," right-click, and choose Manage Choose Event Viewer and click on "Application" Check for Type "Error" and Source "Vista" at the same time range as the alarm in Vista Double click on the alarm and read the explanation for it If a virus program is installed, make sure the $queue folder is in the exception list.