Building Automation Knowledge Base

Issue "Network interface is being initialized" when using Remote Serial Port Driver in Vista Environment Remote Serial Port Driver (RSPD) Cause If using the Remote Serial Port Driver and seeing a "network interface is being initialized" error message in Vista when viewing points, then it might be an issue with the operating system and its Data Execution Prevention (DEP) setting. This problem is most likely found in Windows Server 2003 due to Microsoft using the wrong value as default in SP1. Resolution Verify that the Data Execution Prevention settings are configured for "Windows Services only" rather than "all programs" Reinstall the Remote Serial Port Driver program

Issue Direction of data transfers between Xenta Servers is important in versions 5.1.4 and later.  Stable communication over TCP/IP, UDP requires management of the data flow.  In XBuilder 5.1.6 and later, it will give an error on any connection objects not created using this standard: "It is not allowed to connect a signal to an output that results in a write over the IP network." Product Line TAC Vista Environment Xenta Servers v 5.1.4 and later XBuilder Cause Properly managing data flow will cause the TAC Xenta Server to poll for data, rather than accept an asynchronous write command. This will result in a more stable TCP/IP connection. Resolution See TAC Vista 5.1.5 Release Notes for more information. When importing another TAC XBuilder project to the current TAC XBuilder project in order to create data point transmission between two TAC Xenta Servers, make sure to import the data producing project into the consuming project. In the above example, because Xenta Server A is sending the Outside Air Temperature point to Xenta Server B, it is Xenta Server B's XBuilder project that should be edited.   In XBuilder, right-click on IP Backbone under the Network pane Select New > Other Projects Network In this example, Browse the sending project, Xenta Server A, into the receiving project, Xenta Server B Bind all data using connection objects into the receiving project's network. If bi-directional data flow is desired, the same steps must be performed on Xenta Server A's XBuilder project. The proper way to connect signals in this scenario can be found in Polling data over IP from the System pane of a 700 project.

Issue The VZ21 is obsolete and no longer available. Environment VZ21 VZ22 Cause Obsolete product needs to be replaced. Resolution The VZ21 series valve is replaced by VZ22.

Issue After an attempt to cold start the controller by removing AC power with the batteries disconnected, the unit started up with its CPU light flashing very rapidly (hard failure mode) Environment ACX780 ACX781 Cause Partly cleared memory. The random access memory  (RAM) on the ACX78x take a long time to erase. Resolution Remove the batteries Power down the unit Wait 5 minutes Power up the unit

Issue On a DMS jobsite, Operator Interface (OPRIF) does not display the MicroSmart controllers on the screen.  There are a dozen controllers and they are confirmed as communicating to the DMS but they do not appear in the controller list in OPRIF. Environment OPRIF DMS MicroSmart Cause In OPRIF, the MicroSmart controller list displays 32 controllers per screen and it reserves spaces even if that controller address does not exist on the jobsite. If the controller addresses begin with number 33, then the first screen will appear as blank.  However, the second screen will list controllers 33 to 65. Resolution Use the Page Down and Page Up buttons to move back and forth between controller lists 1-32 and 33-65.

Issue The shadow objects are showing orange "fault" but the values continue to update? Environment G3 (Niagara) ENC, R2 UNC Cause A shadow object will go into fault (orange) condition when the LonWorks service is reading a value that it cannot properly decode.  This "fault" condition is usually related to a SNVT enumeration that is receiving a value out of the standard SNVTs range.  This is typically seen with enumerated SNVT types (e.g. SNVT_occupancy, SNVT_lev_disc, etc.).  For example, an application in the controller is programmed to show occupancy as a value of 0 or 100. The user directly connects the object in the application to the nvoOccupancy tag.  Valid enumeration values for this SNVT are 0, 1, 2, 3, etc.. When the value of 100 is read the shadow object will go into fault (turn orange) because a value of 100 is out of the enumeration range the SNVT_occupancy understands.       Resolution Use WorkPlace Tech to evaluate the controller program and correct any object  to SNVT links that could receive a value outside of its acceptable values.  

Issue A new utility is being used to record log data and store it in the "cloud". It has been requested that the log data have timestamps every 15 minutes synchronized to the hour.  Environment Sigma Trend Log Log data Log set Logging Timestamp Cause There is no mechanism with Sigma to specify when a log set starts to process the logging data. When set to log at timed intervals the log bucket file is downloaded to the controller and processed. The timed interval then starts from that time. There have been some requests for data to be synchronized to the hour with 15 minute log intervals. Resolution There is a engineering workaround to make Sigma do this. A prog point will be needed for every value that is required to be logged. The text is below. 10 XFlo = POINT 0|41 - Object to be logged 20 IF MINUTE = 0 OR MINUTE = 15 OR MINUTE = 30 OR MINUTE = 45 THEN GOTO 40 30 RETURN VIA TEXT 92 VALUE YFlo 40 IF SECOND DOWN THEN GOTO 60 50 RETURN VIA TEXT 92 VALUE YFlo 60 YFlo = XFlo 70 RETURN VIA TEXT 92 VALUE YFlo Then setup the log set with the log data set to "change of value".

Issue With a 10K Ohm resistor wired across the controller input (at the controller) the supervised input reads trouble with the door switch in either the closed or open position.  Environment UI Supervised Input IO Modules 10K Ohm resistor Cause The input voltage selector switch was set to 5 volts instead of 10 volts. Resolution Changed the voltage selector switch from 5 to 10 volts and power cycled the IO module.

Issue When a Vista Master Slave network is setup the Slaves folder list appears but no objects in the folders. Environment Windows 7 32 bit Vista 5.1.X Cause Sometime the synchronies process does not fully complete between the Master and Slave servers. Resolution A restart of the Sever and Slave helps this process to complete. Shut both computers down and then start the master computer and Vista server. Once the master server has been started and checked for correct local communication start the slave computer and Vista server. Wait for the master to pickup the slave and recheck that the objects are being displayed. Also check that the Vista server name matches the computer name as this can cause similar problems.

Issue Is there a wireless version of the BCX Environment BCX 9640 BCX 4040 BCX 4000 Cause Looking for wireless model for BCX Resolution In order for a BCX to support field bus controllers, the commport must be selected for wireless and also an adapter installed for wireless support.

Issue When logging into SIGNAL, a pop-up error appears: Path not found. Error, Btrieve #915.  A local or shared drive cannot be found.  Correct the problem and try again. Environment SIGNAL Cause The SIGNAL.INI file located in the WINDOWS folder contains folder paths that no longer exist or were changed. Resolution Replace this file with a copy containing the default directories. The file can come from a database backup, another installation of SIGNAL, or from the link available in the previous line above.

Issue Niagara R2 UNCs using the bacnet-2.305.523b.v1 (or newer) jar file may need  have the bacnet.properties file modified in order to work properly. Environment Niagara R2 UNC with bacnet-2.305.523b.v1 will need the bacnet.properties file modified in order to work properly. If the station is upgraded to bacnet-2.305.527i.v1, -2.305.529.v1, or -2.305.232.v1, the bacnet.properties file modified in order to work properly. New stations created with bacnet-2.305.527i.v1, -2.305.529.v1, or -2.305.232.v1 will have the correct bacnet.properties file  by default. (revised 9-23-2011) Cause Upgrading bacnet jar files. Resolution Two lines near the end of the file must be un-commented by removing the leading # sign. The two lines are: pollHeartbeatCheck=true PollRestartEnabled=true No other modifications to the file are recommended. The UNC must be rebooted to utilize the revised settings. (revised 9-23-2011)

Issue Installing an updated I/A Series G3 license does not enable options updated in the new license. Environment I/A Series G3 Workbench or G3 Enterprise Network Server (all versions) Cause When installing a new I/A Series G3 license, it may be necessary to restart the NiagaraD service before the updates contained in the license take effect.  This issue is most often noticed when a demo license update is installed after the previous demo license has expired. Resolution After installing an upgraded license, regardless of whether the license was installed automatically from the license server or manually, stop and restart the NiagaraD service.  The NiagaraD service can be restarted either from the Windows Services control panel applet or by using the Install Niagara Platform Daemon.

Issue What type of surge protection comes with a MNB controller? (e.g. from a lightning strike) Environment MNB controllers Cause Job specification requirement Resolution All of the MNB controllers are tested to the IEC EN 61000 standard which is a rigid test for surge protection where all I/O, Power, and Communications are subjected to a 20KV surge. During design, this normally results in having to add in extra protection so as to pass the test. Communications within the controllers have optical isolation which protects the communications transceivers to transients.  

Issue Is the TAC228R controller still available? Environment TAC228R 2281084000 Cause Availability of old controller Resolution The TAC228R was withdrawn in 2011 and is no longer available for ordering for new projects. It will still be available as a spare part until 2021-12-31 when it will be terminated. A suitable alternative is the SE8300 series of room controllers. The TAC228R had the ability of a remote setpoint using a 0-10V signal, by using lua script and utilizing the input UI23, the same operation can be achieved.

Issue Cannot learn EnOcean thermostats into the MPM. Environment MPM, EnOcean Cause Purchased the wrong EnOcean frequency MPM. Can the antennas just be changed?  Resolution No, just replacing the antennas will not resolve the problem. The MPM controller and antenna must be replaced to match the frequency of the Enocean thermostats. Note: the 315 MHz EnOcean MPM uses an antenna with green stripes; the 902 MHz EnOcean MPM uses an antenna with yellow stripes. 

Issue In the MPM, it is possible to creat a new Calendar object, but it is not possible to change or add information, it is not possible to Save. Environment MPM Cause The User Rights does not allowed you to Save your changes in the Calendar objects. Resolution In the MPM, right click on the top right, where it says Management. Select Permissions, and verify that the user that are logged in at the moment have permissions to Edit/View Calendar Objects.

Issue Are MNL controllers RoHS compliant? Environment MNL Controllers Cause Restrict dangerous substances commonly used in electronic and electronic equipment. Resolution All controller final assemblies will be RoHS compliant by the end of the 1st quarter of 2010.

Issue After reviewing a DMS installation, the red end-of-line (EOL) termination modules are not installed on the Microsmart trunk. The original part number was N406-032. Are they available for purchase? Product Line TAC IA Series Environment DMS Cause Part number cross reference Resolution The part number is changed to RBSC-16. Use this number when contacting customer support services.

Issue I/A Series G3 ASD driver exhibits excessive device initialization and recovery times upon a restart of the station or a power cycle of the ASD devices. Environment I/A Series G3, ASD Cause Driver not synchronizing baud rates to efficiently recover the devices on the bus. Resolution The tacAsd 3.6.47.4 module resolves this issue by improving the mechanism that synchronizes the baud rates between the station and the ASD devices. Download the file tacAsd-3.6.47.4 from The Exchange Download Center.