Building Automation Knowledge Base

Issue When ordering Veris products through Schneider Electric, SE part numbers must be used. Environment Veris products Cause Cross reference needed between Veris and Schneider Electric part numbers. Resolution   Veris Part no SE Part no H708 3240100000 H709HV 3240101000 H308 3240102000 H608 3240103000 H908 3240104000 H909HV 3240105000 H800 3240106000 H300 3240108000 H600 3240109000 H900 3240110000 H721LC 3240201000 H721HC 3240202000 H921 3240203000 H722LC 3240204000 H722HC 3240205000 H723LC 3240206000 H723HC 3240207000 H922 3240208000 H923 3240209000 H221 3240210000 H321 3240211000 AH01 3240301000 AH-27 3240302000

Issue The UNC and Enterprise server, as well as many other Schneider-Electric Buildings products, use a TIME protocol server to provide clock synchronization. The address of that Time Protocol Server no longer works. NOTE: The nist.gov sites will no longer be providing TIME protocol services over TCP port 37 as of March 1, 2013. Product Line Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Schneider Electric Buildings products that rely on the use of TCP TIME protocol servers for time synchronization. This includes the I/A Series R2 UNC & ES and the I/A Series G3 ENC & ENS as well as other IP ethernet based products. Cause Many server sites are discontinuing support for the TCP TIME protocol because it is so bandwidth intensive. NOTE: The nist.gov sites will no longer be providing TIME protocol services over TCP port 37 as of March 1, 2013. The site http://tf.nist.gov/tf-cgi/servers.cgi lists most of the currently available TIME protocol servers as well as the status of the entire TIME protocol system. Resolution If the product supports the use of the NTP time sync protocol, switch to the use of that protocol. If the device only supports the TIME protocol, consult the web site http://tf.nist.gov/tf-cgi/servers.cgi for currently available sites.

Issue Error "Job Failed  java.lang.NoSuchMethodError: com/tridium/install/BDaemonPlatform.getNiagaraR2Enabled()Z" when attempting to perform an I/A Series G3 Station Backup in version 3.6.31 after having installed the August 2012 security updates. Environment I/A Series G3 JACE or ENC with release 3.6.31 and security patches 3.6.47 installed. Cause Internal software error in the backup.jar file, version 3.6.47.2 Resolution Remove the backup.jar file, version 3.6.47.2 from the modules folder on the I/A Series G3 WorkBench computer. Remove the file backup.jar from the \niagara\niagara-3.6.31\sw\3.6.47.2 folder. Verify that the original 3.6.31 backup.jar file is in the  \niagara\niagara-3.6.31\modules folder.  Note that when replacing the backup.jar file, the 3.6.47.2 file should be renamed so that it can be restored later. Open the 3.6.31 Workbench and open the platform of the ENC / JACE. Run the Software Manager and note that a newer version of the is shown as installed as compared to the avail. version. Select the "backup" module by clicking on it then click the [Downgrade] button then click the [Commit] button. Acknowledge the warning that a reboot will be required by clicking the [Yes] button. Wait for the module commit process to complete, the station to reboot and restart. After the station has restarted you can log into the Station through Workbench and perform the backup to a .dist file using the standard station backup procedure (by right-clicking on the station name and selecting "Backup Station").

Issue ES will not start because only the WorkStation Software Professional license is installed and not the Enterprise Server License. Can both licenses be installed on the same computer ? Environment Enterprise Server Workstation License Cause The enterprise server will not run because only the workstation license is installed. Resolution Yes both the WorkStation Software Professional license and the Enterprise Server license can be installed in the same computer.  

Issue Schneider Electric part number equivalent to Belimo SGA24 Environment SGA-24 AM-705 Cause Internal purchasing instead of external. Resolution No cross reference is available for the European market. The Belimo positioner in question is not represented in our portfolio and needs to be purchased from the manufacturer directly. For US market, please refer to AM-705.  

Issue Schneider Electric part number equivalent to Belimo SGF24 Environment SGF-24 AM-706 Cause Internal purchasing instead of external. Resolution No cross reference is available for the European market. The Belimo positioner in question is not represented in our portfolio and needs to be purchased from the manufacturer directly. For US market, please refer to AM-706.

Issue Schneider Electric part number equivalent to Controlli MVT44 Environment Controlli MVT44 (Previously badged as TAC) MZ20B-24 (8455001000) Cause Internal purchasing instead of external. Resolution Schneider Electric MZ20B-24 (8455001000) is the equivalent of Controlli MVT44.

Issue Need to control six fans at same speed. Environment b3920, ABB VFD Cause How to properly calculate the load on the analog output.  Resolution The b3920 has a 0-10V output and the VFD has a 0-10V input. The VFD data sheet indicates the input presents a resistance of 2 Megohms. The b3920 data sheet indicates the output load resistance must be greater than 2Kohms. When resistors are wired in parallel (like when sending the same signal to multiple VFDs) the total resistance is always less than the smallest resistance. When the resistors are the same size the calculation of the total resistance is simply the resistance divided by the number of resistors. In this case we have 2,000,000/6 = 333,333 ohms - way more than the 2000 ohm minimum. So, the b3920 output should be able to send a proper signal to the six VFDs. For more info on the math see http://en.wikipedia.org/wiki/Series_and_parallel_circuits#Parallel_circuits

Issue Is it possible to connect the thermistor input to U1 & AI (actuator position 0-10Vdc) to U2 using the same "M" terminal?   Environment TAC Xenta 280 TAC Xenta 300 TAC Xenta 400 Cause All M terminals are internally connected. There are fewer M terminals than inputs. Resolution Yes, you could use the very same M connection to both inputs, however you should have separate cables connect to M. It is also important that the M connections are only used as reference for inputs, so there are no current in this connection, like you need to have separate connection for powering the actuators.  

Issue I have to replace a faulty Xenta 301 but found that the existing Xenta 301 was system version 1. The system consists of about 12 Xenta controllers sitting on a Menta only network using .nwc,ndb network configuration tool. Environment TAC Xenta 300 TAC Menta Cause New devices are delivered with version 3. Resolution As TAC Xenta system program version 1 and version 3 can not work on the same network, downgrade the new device to replace the faulty one. Download TAC Xenta 300 system program version 1.17 Use Download Wizard as normal to download the system program, however, going from version 3 to version 1, do NOT keep old application in the Download Wizard. Select Clear Application. Download the Menta application and network configuration manually via the serial cable. You could use the actual TAC Menta versions to do this.

Issue Procedure to activate the Add-on reports module. Environment Continuum Add-on reports module. Cause Received an Activation Code from the COE Team, need to know the procedure to activate the Add-on reports module. Resolution You will receive an Email from the COE Team with the Activation Code along with Instructions on how to activate it. For your Convenience the instructions are below. ACTIVATION INSTRUCTIONS - CONTINUUM REPORTS INSTALLED IN C:\PROGRAM FILES Make sure Continuum is not running Make sure Continuum Reports is not running Launch a DOS Command Window CD "Program Files\Continuum_Reports" Enter in lower case: reports key writer Enter the activation code. (Note: Case sensitive)   -(OR)-   ACTIVATION INSTRUCTIONS - CONTINUUM REPORTS INSTALLED IN C:\PROGRAM FILES (X86) Make sure Continuum is not running Make sure Continuum Reports is not running Launch a DOS Command Window CD "Program Files (x86)\Continuum_Reports" Enter in lower case: reports key writer c:\progra~2\continuum_reports 6. Enter the activation code. (Note: Case sensitive)Activation Instructions - Continuum Reports installed in C:\Program Files 1. Make sure Continuum is not running 2. Make sure Continuum Reports is not running 3. Launch a DOS Command Window 4. CD "Program Files\Continuum_Reports" 5. Enter in lower case: reports key writer 6. Enter the activation code. (Note: Case sensitive) -or- Activation Instructions - Continuum Reports installed in C:\Program Files (x86) 1. Make sure Continuum is not running 2. Make sure Continuum Reports is not running 3. Launch a DOS Command Window 4. CD "Program Files (x86)\Continuum_Reports" 5. Enter in lower case: reports key writer c:\progra~2\continuum_reports 6. Enter the activation code. (Note: Case sensitive)

Issue Following an upgrade or import of a graphic the canvas size becomes extremely large. Environment Cyberstation V1.94 Pinpoint Cause A defect in V1.94 has been found and corrected by a hotfix. Resolution Hotfix for Pinpoint issues 1.94 SP1 resolves this issue (TPA-BOST-12-0001.00). This should be installed on all workstations on the site.

Issue Error message  "No default Mail server detected" when installing Continuum Environment Windows 7 Windows XP Windows Vista Continuum Outlook Express Windows Live Mail IE Internet Explorer Cause When Microsoft released Windows 7 they removed the email program "Outlook Express"  As a result of this in IE (internet explorer), default Email program is left empty, as Continuum can send emails there needs to be a default program selected Resolution Solution for this is to first install "Windows Live Essentials" from the following link http://windows.microsoft.com/en-GB/windows-live/essentials-other-programs?T1=t2 In some cases you will get an error message which will stop you running the program, if you get this error then follow the next link on how to fix this http://answers.microsoft.com/en-us/windows/forum/windows_7-system/how-do-i-reinstall-wldcoredll/2075e9bf-2e5a-e011-8dfc-68b599b31bf5 On successful install of the above program you will now need to go into IE (Internet Explorer) goto "Tools" then "Internet options" then select "Programs" you will now see a list of options, next to the E-mail: option click on the drop down and select "Windows Live Mail"  Apply the changes and close the program, you should now be able to install and run Continuum without getting the  "No default Mail server detected"  error message This problem can also happen in other OS environments i.e XP and Vista, in this case you do the same as above but instead of using Windows Live Mail you would use "Outlook Express" or you could use "Office Outlook" if you have a MS Office package installed

Issue If using the "sym" jumper in a 100Pa configuration, will this mean -50Pa - +50Pa range? Environment 004700320 SPD310-100/300/500/1000 Pa 004700340 SPD310-1000/1200/2500/5000 Pa 004700360 SPD360-300/500/1000/2500 Pa Cause In some applications, the output signal, is requested to be symmetrical. Resolution The specified values we can grant is only down to 100 Pa. Using the Sym – jumper configuration would change the signal to -100 Pa …+100 Pa ( not -50…+50 Pa ), because the sensitivity of the sensor does not change by this jumper.

Issue The descriptions of the MN-S and MN-S1 sensors both state that they are temperature sensor only, what is the difference? Environment MN-S MN-S1 MN-Sx Micronet 2000 I/A Series Micronet Cause The part number descriptions of the MN-S and MN-S1 sensors both state that they are sensor only, what is the difference? Part # MN-S Description: MicroNet 2000 Wall Temperature Sensor with Temperature Sensor Only          Part # MN-S1 Description: I/A Series Micronet S-Link Sensor Assembly Providing Temperature Only.   Resolution While physically and functionally similar the two sensor belong to different product families and are not interchangeable since they utilize different communications protocols. The MN-S communicating sensor is compatible with the Micronet 2000 product family and is used with MN-FLO, MN-FLO3T, MN-HPFC controllers that use U bus communication protocol for sensor data. The MN-S1  communicating sensor is compatible with the I/A Series Micronet  product families and is used with MNL and MNB range of controllers that use S-Link communication protocol for sensor data.

Issue A sensor connected to a DMS system displays the letters INH to the right of the real-time display.  What does this mean and how can it be removed? Environment DMS Cause It is unknown how the INH appeared on the point.  There are at least three ways to do it with programming but none were found in the database. The INH is short for 'inhibit'.  It prevents a point from generating alarms or changing conditions even though an alarm or change of condition exists.  It is useful during times when maintenance is being done on the associated HVAC system or if the HVAC system is scheduled off.  It prevents nuisance alarms. Sometimes it gets applied after a database glitch during a loss of power or communications.  This situation is rare but it can occur. Resolution To remove the INH and allow the sensor to alarm and change condition, it must receive the ENINH command.  There are several ways to apply the ENINH command.  The quickest way is to use command mode. In OPRIF, - use the up and down arrow keys to highlight the sensor with the INH applied to it. - press F8 to enter command mode - type ENINH then enter - press F8 to exit command mode - allow OPRIF a few seconds to update and refresh the sensor on the screen

Issue Upgrading an end customer copy of WorkPlace Tech from version 5.8.1 to 5.8.2. Is there a charge for it? Environment WorkPlace Tech Cause Cost estimating for end customer's system upgrade Resolution There is no charge when upgrading WorkPlace Tech from 5.8.x to 5.8.y. Charges apply when upgrading WorkPlace Tech 5.7.x to 5.8.x.  

Issue PinPoint graphics crashes when creating or editing "Active Animation" or "Combo Box" Environment Windows 7 1.93 1.94 Cause If logged on to the PC as a Power User or other non Administrator account you may not have the correct permissions to run some items within Continuum Resolution If the user is required to modify or create PinPoint graphics or various other activities, full access to the Continuum Folder may be required ( or Graphics Folder if this is an a remote server) 1. Log on to the PC as an Administrator 2. Locate the Continuum directory (usually C:/Program Files/Continuum) or Graphics directory 3. Open Properties (Right Click) 4. Select Security 5. Add the required Group or user name, give the write permission

Issue Not getting the pop-ups or the sound when alarms are generated in the Vykon 2.50 Alarm Service (VAS).  However, alarms are being logged to the VAS. Environment  R2, Niagara version 529, 532, 535 Cause No cause stated. Resolution The new vas-2.301.536.v1.jar and vasClient jar files were created to correct the pop-up issue. This resolution applies to the VAS 2.50 Client and the vas-2.301.532.v2.jar. VAS 2.301.536.v1 JAR Files and Client can be downloaded from The Exchange Download Center. Installation of the new vas-2.301.536.v1.jar file Stop the Enterprise Server running the VykonAlarmService Open Windows browser and go to C:\niagara\nre\modules Rename the current vas-2.301.532.v2.jar with the “.old’ extension Copy the new vas-2.301.536.v1.jar file to C:\niagara\nre\modules Restart the Enterprise Server.   Installation of the new vasClient.jar file Stop the VAS 2.50 client. Open Windows browser and go to C:\Program Files\Tridium\Vykon Alarm Service Client 2.50\lib Rename the current vasClient.jar with the “.old” extension. Copy the new vasClient.jar file to C:\Program Files\Tridium\Vykon Alarm Service Client 2.50\lib Restart the vasClient. The vasClient alarm pop-up, along with its sound, should now be displayed when an alarm is generated.

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 For various reasons there will sometimes be a need to move a controller from its existing Continuum network to a different Continuum network. Environment CyberStation ALL CX master controllers Cause Configuration Resolution WARNING: MAKE SURE TO HAVE A FRESH BACKUP OF THE CONTINUUM SQL DATABASE HANDY IN CASE YOU NEED TO REVERT THE CHANGES FOR ANY REASON. Moving a controller from its existing Continuum network to a different network consists of copying the controller and its children to the destination Continuum network and then deleting it from the source network. Place CyberStation in offline edit mode. In the 'Copy' options make sure to select to 'Copy child objects and the children's children, this will ensure that all field devices get moved with the parent CX. Highlight the controller to be moved then drag it to the destination network and select 'Copy Here', please note that the IP address on the destination will be set to 0.0.0.0 to avoid a duplicate. On the original controller highlight the InfinityInfinetCtrl folder, select all the objects on the right side  and send to text file. Delete the original controller then set the IP address on the copy. Select the copied controller,  right click and select import into  and import the text file created on line 4. Return CyberStation to online edit mode, then reload the CX controller (not including the field devices) NOTES: a) After reload, the controller may have a different time if the original network was in a different time zone than the destination network. b) Controllers are only taught about other controllers in the same network, If you are moving multiple controllers move them all before reloading them. After reload controller will not know about any other controller that stayed in the old network and any references to such controllers will be lost.