Building Automation Knowledge Base

Issue  A temperature input will not go into alarm when it's value falls outside of the temperature range specified in its associated Out of Range alarm. When changes are made to the input (requiring the input to be saved) either of the following errors is displayed. The object attribute specified is invalid. The referenced attribute for an out of range or floating limit alarm must be either a REAL or smaller numeric type. Environment Alarm Enrollment Event Notification Alarms Cause While the High and Low limit parameters appear to be whole numbers, one or more of the values are either corrupted or of an incorrect data type. Resolution Record the parameters specified in the Algorithms page of the Alarm Enrollment. Clear the values in the Out of Range parameters by changing the alarm type to Expression. Apply the changes. Change the Alarm Type back to Out of Range. Enter the alarm parameters recorded in step one. Apply the changes and test.

Issue A MSC-MPC MicroSmart controller (revision 10) was replaced with the only available MSC-MPC on-site.  The replacement is a revision 11 controller.  Will a backup copy of the database from the revision 10 controller work in the revision 11 controller? Environment DMS MicroSmart MSC-MPC MSC-MPC-001 Cause No available revision 10 controllers Resolution Yes, the revision 10 database will work in the revision 11 controller.  OPRIF (the DMS-MicroSmart) programming tool) will prompt the user with a warning that the database file is not for the revision 11 controller.  Go ahead and continue with the download. Once complete, the unit displays in the MicroSmart controller may show up blank in OPRIF but the points are there and working.  Use the Point Configuration screen to scroll through all the points.  The only way to correct this display issue is to re-create each point from scratch which is time-consuming.  All the MicroSmart points linked to the DMS will restore properly.  So, from the DMS level, all the points will work normally and display normally.

Issue After upgrading a station to version 3.7,  saving and backing up the station fails every time. Any changes made in the station are erased once Workbench is closed Environment Niagara G3 version 3.7 Cause This is a new bug in 3.7, and should be fixed with next major release (3.8).  Control points copied from inside the BacnetNetwork to outside the BacnetNetwork causes the issue.   Resolution Control points with BBacnetProxyExt who are descendants of any Bacnet Network should be fine. You need to look for places you copied a control point from inside the BacnetNetwork to outside the BacnetNetwork.  There is a workaround: 1. In the station, go to Config > Services > ProgramService. Click the "Find Objects" button 2. In the Bql Query Builder window click the "Of type" drop-down, and select (Custom Type) 3. In the middle drop-down, select bacnet. In the right-most drop-down, select BacnetProxyExt. Click OK. A list of BACnet objects will appear 4. If any BacnetProxyExts show up outside the bacnet network, then their parent control point needs to be deleted, or replaced with a regular control point without a BBacnetProxyExt Proxy Extension  

Issue Changing one Filemaster to another Environment All versions of I/Net Cause Possible corruption on Filemaster and needs to be changed to a different Filemaster then repromote as a client. Resolution To resolve this the following steps needs to be followed: Demote the original Filemaster to a stand alone option and backup the database Demote all the clients to stand alone option Restore the backup from the original filemaster to the PC that will be the new Filemaster Promote to Filemaster Option and allow the icon to change states to where it allows clients to connect Promote all other clients to Equalized Clients by pointing to the new Filemaster Once Equalization is online again, the system should be working again.

Issue Job site has a Niagara G3 station integrated with several Xenta 301 controllers.  Can the Menta programming tool be used via LON tunneling through the station to re-program the Xenta controllers on an as-needed basis? Environment Niagara G3 Xenta controllers Cause Field request for ease of programming Resolution Tunneling via a Niagara G3 station to Xenta controllers is not possible.  A direct-connection is required.

Issue There are a couple of part numbers available for the expansion module cables, which ones are for which devices? Environment xP modules Cause Not sure which cables are for which xP modules. Descriptions and documentation on iPortal is inadequate. Resolution There are three xP module cables available: The 01-0100-484 cable is a replacement for the xP-Display module cable and this is meant to be for the xP-Display only, not for any of the other xP I/O modules. The xP I/O modules such as xPDO4 require either the xP-Mod-Cable-3 or xP-Mod-Cable-10. Be aware that you will only be able to extend the xP network for a maximum of 10Ft. See this iPortal datasheet or on Exchange Extranet for details.

Issue When configure a door with both reader channels as 0, only want to monitor the status of door switch, when the door is opening for a long time, the door ajar alarm should be triggered if the alarm has been configured, but on this condition, the door ajar alarm will never be triggered. Environment Cyberstation ACX AC-1 Cause Maybe it is a design, the controller not consider is a door when the reader channel is 0 Resolution Set a valid channel number for EntryReader although it is not connected, then try again, that should be OK.

Issue A 3rd party BACnet/MSTP controller was added to an existing ENC-520 running version 3.5.25.  All points from the controller were added to the ENC station successfully.  When adding these new points to the server, most of the points added except for two.  An 'invalid facets' error gets generated for the two points.  The points that were added successfully were pressure, temperature, and speed points.  The two points that did not add were flow points.  The server is running version 3.3.22. Environment Niagara G3 3.3.22 and 3.5.25 Cause The default engineering units changed between versions 3.3 and 3.5. Resolution Replace the units.xml file (lib folder) in the 3.3.22 server with the units.xml file from a 3.5 server.  Restart the station.  The points should now add successfully.

Issue A MN-Sx sensor is installed more than 200 feet away (the maximum specified) from a MNL controller. The dynamic temperature value drops in and out at the controller.  Is there a repeater that can be installed to improve communications? Environment MNL MN-Sx Cause Cable run extends beyond the specified 200 feet. Resolution There is no repeater available that can be used for the MN-Sx cable run.

Issue Errors variable increasing rapidly and frequent 182a errors seen in the Controller Error Log. 0x0000182a - COMM_ERR_IV_IPADDR (Invalid Internet network address) Product Line Andover Continuum Environment All IP Level Controllers bCX ACX57xx Netcontroller Netcontroller II Cause The 182a error indicates that there is an issue with the controller IP Address settings. Some potential causes of this are: Duplicate IP Address, improper subnet mask, improper gateway, BACnet routing issues. It seems that it is logged when trying to change the IP address or use an encode id already used by another device. This error can be caused by misconfigured IP address information including mask and gateway addressing.  Can also be due to improper BACnet routing. In one specific scenario the issue was the default router setting in the Controller. This was set to a device that was not a router to the network. Confirming the configuration of all IP Devices on the network and getting a Wireshark capture can help to identify the potential cause.  Resolution Removed the invalid IP address from the Default Router field and the 182a errors stopped appearing in the Controller Error Logs.

Issue UNC stops communicating with LonWorks devices. The following messages are seen in the UNC's standard output. Opened lon / LON1 >>> Lon Driver opened!   ERROR: readProperty() failed for property tridiumx.lonworks.LonException E_LON_INVALID_MSG_CODE Opened lon / LON1 >>> Lon Driver opened! Opened lon / LON >>> Lon Driver opened! Opened lon / LON1 >>> Lon Driver opened! Environment I/A Series UNC-520 LonWorks communications Cause The standard output of the UNC shows that the UNC LON port and LON driver were successfully opened and indicates no error. The cause of the problem is unknown at this time.  Resolution Current workaround is as follows: In the UNC station, go to Services > LonWorksService > LonDeviceManager. Select the LocalLonDevice and Commission it. 

Issue Do we have any UV intensity sensor available in the Schneider Electric portfolio? Environment Ultra violet sensor UV Cause Some applications require a UV intensity sensor. Resolution Unfortunately, no such sensor is currently available in the Schneider Electric offer. If required, it needs to be purchased locally.

Issue ACX781's are still installed on some older sites but the cabinet keys cannot be found. Can these be replaced? Environment ACX781 Cabinet Enclosure Cause No one has the cabinet key and it needs to be replaced. Resolution The ACX781 controller has been discontinued since 2007. The stock on the cabinet lock/key assembly has been depleted since then and there are no replacements available.

Issue Is it possible to configure a SE7200F5545E to be used with an external CO2 sensor input? Environment SE7200F5545E SCD110 Cause Customer requesting a CO2 input and read out of CO2 value. Resolution Unfortunately this is not an option on the SE7200F5545E controller. See SE7600 series where this might be possible in some applications.

Issue New pc hardware was supplied for the server.  A new IP address was configured in Windows.  Tried adding it to the Network Settings tab in Admin Tool.  The numbers added to the fields are not retained. Environment Niagara R2 Cause new  pc hardware Resolution The IP address entered into Windows is sufficient.  Adding the same information to the Network tab in Admin Tool is NOT required. Treat the Network tab for a server station as 'read-only'.

Issue ROAMIO2 fails to connect to Controllers using either the BACnet or Infinet service tool.  ROAMIO2 without batteries fails to power up when connected to Controller's service port. Environment NetController II, bCX 4040, bCX4690, i2 controllers, b3 controllers. Cause Incorrect RJ11 cable type.  If using an RJ11 cable that is not a straight thru cable then ROAMIO2 will not function properly. Resolution Troubleshooting: Check the RJ11 cable to verify that it is a straight thru cable.  If it is a reverse or crossover cable it will not work.  To test this issue you can connect the ROAMIO2 device (without batteries) to a controller's service port.  If the ROAMIO2 will not power on, this is an indication that the cable may be the wrong type. Solution: Replace with straight thru RJ11 cable.

Issue An error stating "Cannot change directory to Continuum" is thrown when trying to install Cyberstation. Environment Installation Cyberstation WebServer Cause This error usually occurs when the install executable is run from inside the compressed (Zip) file folder. Resolution Copy the contents of the compressed folder (zip file) onto the PC, then launch the setup application.

Issue Can I edit the "covIncrement" of a BACnet point in a BACnet controller from the ENC? Environment G3 ENC's Cause This may be necessary to increase the covIncrement of a BACnet point if it is triggering excessive "cov notifications" to the ENC. Resolution In revision 3.2 and newer under the Device object a new selection called “Virtual” was added. BACnet virtual points are transient and are created and subscribed only when accessed. Expand Virtual and all the BACnet objects in the device are listed. Right click the object of interest and all of its properties are displayed, including covIncrement. Expand covIncrement and its value can be changed. When the Save is done the value is written to the controller.  

Issue Can the WorkPlace Flow Balance Tool (for BACnet) override the fan in a fan-powered VAV box? Environment WorkPlace Flow Balance Cause Balancing requirements Resolution The fan cannot be controlled from within the Tool.  It will have to be powered on or off using another tool like WorkPlace Tech or from the networked controller (i.e. UNC/ENC)

Issue Which auxiliary switch is used on with the MV15B actuator? Environment MV15B S2-MV15B 8800469000 Cause Some applications requires an aux switch to the actuator. Resolution The S2-MV15B, part no 8800469000, is the correct auxiliary switch for this application.