Building Automation Knowledge Base

Issue In a Niagara R2 UNC, the standard output window displays this error message every few minutes: Node.set Cast exception: nvi_7238 DsEnum <- DsFloatStatus [/DeltaHotel/lonTrunk/localLonDevice] java.lang.ClassCastException    at tridium.foundation.dataspecies.DsEnum.copyFrom (bytecode 2)    at tridium.foundation.node.Node.commitPropertyChange (bytecode 42)    at tridium.foundation.node.Node.doPropertyChange (bytecode 31)    at tridium.foundation.prism.Prism.commitEvent (bytecode 77)    at tridium.foundation.prism.Prism.dispatch (bytecode 50)    at tridium.foundation.node.Node.dispatch (bytecode 15)    at tridium.foundation.node.Node.set (bytecode 36)    at tridiumx.lonworks.devices.LocalLonAppDevice.setNvValue (bytecode 39)    at tridiumx.lonworks.services.NvManagerService.setLocalNvValue (bytecode 7)    at tridiumx.lonworks.LonNvDevice.writeProperty (bytecode 62)    at tridiumx.lonworks.LonNvDevice.asyncPropertyChange (bytecode 24)    at tridiumx.lonworks.devices.ForeignLonAppDevice.asyncPropertyChange (bytecode 132)    at tridiumx.lonworks.services.LonAsyncEventService.processAsyncEvent (bytecode 16)    at tridium.services.helpers.AsyncEventHelper.run (bytecode 49)    at java.lang.Thread.run (line 5) Environment Niagara R2 LON Cause The error indicates that the link between the DSEnum and DsFloatStatus are not compatible – even though a link was allowed between them.  The link may work but not all the time.   That may be why it is not a frequent error. Resolution Locate a conversion object that can be placed in between them (an object that converts float to enum or vice-versa depending on the link’s direction).

Issue In Niagara R2, master-slave schedules are not working. The slave schedule goes into fault and will not clear.  The following error appears in the standard output window of the UNC:   ERROR: Could not init node [/OZS_UNC1/IbsAsdNetwork/AHU_9/MZ2_93/Schedule_8] Environment Niagara R2 Cause This error, and subsequent fault condition on the schedule object, can occur when the Enterprise Server has a holiday calendar and a master schedule and the UNC only has a slave schedule. When the UNC is rebooted (for other reasons), the slave schedule object checks the master schedule object in the server to see if it's a holiday.  If there is a communication issue, the slave schedule object goes into fault. Resolution Delete and re-create the slave schedule object. Add a master/slave schedule AND master/slave calendar objects in the server and UNC stations.

Issue Received Elevator Control Software but no activation code for Continuum Security Key. Unable to use the software without the key. Environment Elevator Control Add-on Software Cause Instructions on how to obtain the activation key have been missed or did not arrive with order. Resolution The packing slip that comes with delivery of the Elevator Control Software CD has instructions on how to obtain the activation code. At the bottom of the packing slip you will see something similar to below. ***************************************************************************** ** Please email Continuum Key S/N to                                       ** ** COE@buildings.schneider-electric.com requesting                         ** ** Software Activation Code for CUSTOMER PO# xxxxxxxx                      ** ***************************************************************************** You will need to send an email to the Center of Excellence Support team with the serial number of the Continuum Security Key you want to activate and the Purchase Order number that the software was purchase on. You will then be sent a serialized code that is used with the "KeyCode_KeyWriter.exe" to activate the key. Detailed steps are described in the Elevator Control Installation and Operation Guide that comes on the CD.

Issue R2 Cloudscape and Microsoft Excel 2010 user name and password are requested each time. Environment Niagara R2 Cause Basic Authentication: By default, file operations that use Basic authentication over a non-SSL HTTP connection are disabled in Office 2010 applications.  Resolution Install Microsoft update: http://support.microsoft.com/kb/2123563

Issue COV values are stale Environment Niagara G3 Cause Recent changes have been made to the BACnet jar file to address this issue Resolution Go to The Exchange Download Center and download the latest niagara BACnet jar file 3.6.47.9

Issue Can a MN-Sx differential setpoint be defined using the WPT Hardware wizard? Environment MNL or MNB controller with any MN-Sx sensor Cause Project specification requires that all temperature setpoints for a site be fixed and the facility users be allowed to adjust the setpoint  with a relative positive or negative offset. Resolution In the Workplace Tech Tool use the hardware wizard to configure the setpoint with an initial value of 0.0, one decimal place and no limits. Configuring the setpoint in this manner allows the setpoint to be changed over the range of -99.0 to +999 without limit. If limits are required by specification, such as a +/- 3 degree limit, the setpoint value from the sensor would need to be passed through a Limit control object to prevent extreme setpoint offset adjustment.

Issue Online Help states that a String can be 255 characters in size but an error is seen when trying to set the size to this number. Changing the String Size of a String object results in an error "Cannot set the StringSize. Attribute value is invalid". Environment Continuum Controllers Cause The size of String objects depends on the controller that the object is being created in. bCX1 and Netcontrollers support String objects with a size of 132 characters, i2 and b3 controllers only support String objects with a maximum size of 32 characters. Resolution The documented value of 255 as the maximum String Size, as stated in the online Continuum Help, is not correct. Network controllers can support String objects with a maximum size of 132 characters whereas subnet controllers can support a maximum of 32 characters.

Issue Unable to find an object in the Database error when Alarm Page is selected in the object editor. Environment Alarm Functions Alarms Cause Alarm Function keys still present in the registry after Alarm Functions have been removed from Continuum. Resolution In order for Alarm Functions to work, special registry keys are created under the Andover Controls HKEY_LOCAL_MACHINE\Software\Andover Controls\Continuum\Settings folder. To resolve this issue on systems where alarm functions are no longer used... Make a backup of HKEY_LOCAL_MACHINE\Software\Andover Controls\Continuum\Settings Delete the unused registry keys per Continuum online help article User-Defined Alarm Functions.

Issue How to use secondary values in programmable points. How to use forecast in programmable points. Environment BAS SIGMA Cause Some objects in Sigma and BAS have secondary values: Time Schedule - minutes to next switch (when the time schedule is going to change state) is displayed. An example of this is to bring on the heating plant 30 minutes before an AHU starts. Optimiser - minutes to next switch (when the optimiser is going to change state) is displayed. An example of this is to bring on the boiler plant 30 minutes before an VT cct starts. Rotation - the lead load no. is displayed. An example of this is to determine the lead load when a modulating burner signal is used. DO and DI - the hours run is displayed. An example of this is to do pump changeover on hours run. Resolution Example: For a Time schedule: 10 xflo =  P100 (timeschedule object) forecast 20 if P100 off and xflo < 30.0 then return true "Plant PreHeat" 30 if P100 on then return true "Time On" 40 return false "Time Off"   For a Rotation object with 2 loads: 10 xflo = P120 (rotation object) forecast 20 if aflo=1.0 then return true "Boiler1 Lead" 30 if aflo=2.0 then return true "Boiler2 Lead" 40 return false "false" Note: aflo is used as a global variable to another object in the same controller, if not required then substitute with xflo.

Issue What is the BACnet address and BACnet object ID for the Xenta 913? Environment TAC Xenta 913 Cause The Xenta 913 does not have those features since it's not a BACnet device. Resolution The Xenta 913 is a gateway that translates the BACnet objects so that they can be read by for example Lonworks devices. It is not a native BACnet device itself, hence it doesn't have a BACnet address or a BACnet object ID.  

Issue PIR Passive Infrared Sensor, Motion Detector with I/NET Environment Remote Arming Terminal(RAT) or OP5 site with PIR or Passive Infrared Sensor or Motion Detector Cause Site has an Intrusion Alarm System with OP5 arming terminal, the problem is that they want to disable messages from PIR (Passive Infrared Sensor detectors when the zones are disarmed. The goal is to only have alarms when zones are armed. One reason is that there are many PIR changes in the time when the building is occupied. They set the input of PIRs as an DA.   Resolution The best solution is to use an event sequence or sometimes referred to as an event definition. In other words there needs to be a relay which enables or disables the PIR. Some use the Shunt relay on the SCU(if the SCU is not double addressed) for this and it is on either one leg of the power or a contact on the PIR to enable-disable/arm-disarm the PIR.  

Issue Will we be able to use our TAC Workbench (Tech Laptop) to connect to the Honeywell Supervisor? Environment I/A Series G3 (all versions) Cause The NiCS statement within the license controls the sharing of data and usage of Workbench on a G3 (AX) platform. Resolution The answer depends upon the NiCS statement within the Honeywell Supervisor license. If the Honeywell license accept.wb.in statement is open, the TAC brand Workbench would be able to connect and engineer. Based on past experience, the accept.wb.in statement is typically set to webs and can only be accessed by a Honeywell licensed Workbench. The NiCS statement for the ENC is setup to prevent connection by a non-TAC brand Workbench. The statements that control sharing of data (accept.station.in and accept.station.out) have always been open. Unfortunately prior to G3 version 3.6, the Niagara driver point discovery process utilized some Workbench functionality to perform the connection and use basically defeating the main purpose of the NiCS statement. This meant that the points needed to be added manually. The software was corrected in 3.6 to allow discovering of points regardless of the NiCS accept.wb.in statement. The points will be able to be discovered with the Honeywell Supervisor as long as G3 version 3.6 or higher is being used.

Issue What version of I/A Series G3 is compatible with the new JACE-600E (TRD-J-600E)? Environment I/A Series G3, TRD-J-600, TRD-J-600E Cause The original JACE-600 is no longer available for purchase and is replaced by the JACE-600E. Resolution The TRD-J-600E is compatible with I/A Series G3 version 3.6.47.1 or later.  Please review Product Announcement PA-00223 for more details.

Issue Since the MZ18 is only 180N torque spec, is there a higher torque version available? Environment MZ18 in various versions. Cause Some applications require a higher torque actuator. Resolution Unfortunately, the MZ18 is only available in a 180N version through Schneider Electric.

Issue In some heat / cool / flow meter installations, the customer is also requesting a billing software to be used together with the meter Environment heat / cool / flow meters Multical 601 602 Billing software Cause Being able to provide a complete package of meter hardware and billing software. Resolution Unfortunately, Schneider Electric does not have any billing software for heat / cool / flow meters in the product portfolio. Our recommendation is to look at what the Kamstrup brand has to offer.

Issue Using a terminal mode connection, where is the network number for a GCM located? Environment GCM-84000 series GCM-86000 series Cause Attempting a serial connection with Treetech for the purpose of uploading the GCM database (for backup) Resolution After logging into the GCM, follow the menu path below: SYSTEM > DATABASE > INSTALL DATA > NETWORK NUMBER

Issue When is the Niagara R2 product line being phased out? Environment Niagara R2 Cause Pre-planning for customer retrofits Resolution No "new project" purchases will be accepted as of July 1, 2013. No purchases of any kind will be accepted as of December 1, 2014. See PA-00221 TAC IA Series R2 Availability for full announcement.

Issue When an alarm comes into Active Alarm View the wav file keeps playing after the alarm has been silenced. Environment Alarm Enrollment Event Notification Wave File Cause The wave file location has been moved. Alarm Enrollment or Event Notification wave file association has been lost. Resolution Re-point the Alarm Enrollment or Event Notification to the wave file and retest.

Issue What protocol of the Ziton ZP3 Fire Detection System does our Xdriver utilize? Environment Continuum Xdriver - Ziton Fire Panel Cause Need to confirm that the XDriver is able to communicate to third party fire panel. Resolution The Ziton XDriver has been developed to the ZCP2 communications protocol V2.01. Contact the manufacturer to confirm whether the panel supplied supports this version of the protocol.   Further information on the XDriver can be found at the link below. Clymac - Ziton Fire Panel

Issue Unable to create a new i2/b3 Device object. Getting an error "Cannot set the handle. Duplicate Infinet Id and comm port" when trying to create a new Device object. Environment Continuum i2xxx and b3xxx controllers. Cause The error is seen when trying to create a Device object with an Id that already exists on the network or in the Database. Resolution 1. Create the Device object with a different / unused node Id. 2. Check the Database to see if there any ghost entries for this Device object that may not have been deleted properly. Running the Continuum Analyzer tests may show, and clean, these ghost entries.