Building Automation Knowledge Base

Issue Failed to initialize view, access denied or type mismatch when logging in to workstation with some users. Environment TAC Vista Cause When you log in to TAC Vista workstation a default alarmview is always opened (if you are using user profiles you can specify other alarm views. All users that are using the default alarm view have to have at least read rights to $AlarmColumns, $AlarmView and $DisabledView Resolution Log in with a system user Right click on the $AlarmColumns and select authority. If everyone is not in the access control list with at least read rights drag everyone from the Group/users list. Repeat for $AlarmView and $DisabledAlarms

Issue Wrong XIF is used for device when updating from system plug-in. SNVTs are there but not the SCPS XIF has a name like TACCab6.xif instead of the real name if you look in the XIF tab in the device properties Environment TAC Vista System plug-in Cause This happens when the system plug-in can't find the XIF file in the directory it was when the device was created. Then the system plug in creates a XIF from the information it can get from LNS. If the device was created using a template then the path is C:\lonworks\import, you can see the path by clicking on the device in the LNS network pane in the system plug-in This is typical if you have moved the LonMaker database to a different PC that does not have  plug ins installed. Resolution There are two different steps you can take to try to correct this issue. Delete the device in TAC Vista, install the plug in (or copy the XIF to the correct location) and update from the system plug-in again. Manually browse in the correct XIF file into TAC Vista workstation under the XIF tab in properties of the controller. Sometimes this must be done twice in order to bring in all configuration points and SNVTs. Once the XIF is in the right place any new device added will get the right XIF

Issue What is the maximum value that the BITAND function able to process. Environment Continuum BCX NCII CX Plain English Function Cause BITAND function is not working as expected. Resolution The largest value that the BITAND function is able to process is 65535 or 1111111111111110.

Issue Can a Continuum LAN Security Key be upgraded to a WEBC key? Environment Continuum Security Key Cause A customer wants to add WebClient capability to their existing LAN setup and is replacing one of the LAN Cyberstations with the WebClient Server but wants to use the existing Security Key.   Resolution A Continuum Security Key cannot be upgraded from LAN to WEBC, you'll need to purchase a new WEBC key to enable WebClient on a LAN system.

Issue Which damper actuators are available with 3-point control? Environment 8751001000 Actuator Damper MD5B-230 8751003000 Actuator Damper MD5B-230-S 8751005000 Actuator Damper MD5B-24 8751007000 Actuator Damper MD5B-24-S 8751011000 Actuator Damper MD10B- 230 8751015000 Actuator Damper MD10B-24 8751021000 Actuator Damper MD20B- 230 8751025000 Actuator Damper MD20B-24 8751035000 Actuator Damper MD40B-24           Cause Both modulating control (0-10V) and On/Off 3-point control damper actuators are available. Resolution All MDX(X)B damper actuators are On/Off or 3-point control.

Issue Modbus TCP/IP Server is not an option when programming a Modbus Gateway in an Xenta Server. Environment Xenta 913 Xenta 7xx XBuilder Cause There are only 3 Modbus Interface configurations for Modbus in an Xenta Server. Modbus RTU Client ("Master"), Modbus serial line master on a network Server ("Slave"), Modbus serial line slave on a network Modbus TCP Client ("Master"), Modbus TCP client to a server or router on a network Modbus TCP Server is not possible. Resolution Modbus TCP/IP can only be configured to be a Client (Master) in an Xenta Server. A solution if TCP Server is absolutely necessary would be to use an IP to 485 converter, such as an EGX100, and use the RTU interface.

Issue What is the difference between the UNC-510-2 and the UNC-510-21? Environment UNC-510-2 or UNC-510-21 Cause Product part number difference specifies additional option. Resolution The UNC-510-21 is a UNC-510-2 that includes WebUI support.

Issue Calibration requirement? Environment STD300: 006920121 STD300-300 -50/50 006920141 STD300-300 0/100 Cause Some sensors on the market requires calibration when connected to the controller, in order to function properly. Resolution No calibration is required when connecting the STD300 to a Xenta controller. The sensor is using a 4-20mA output signal, so the controller needs to be configured for this type of signal in order to work with this sensor.

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.