Building Automation Knowledge Base

Issue An Alarm object in an XBuilder project has two outputs - digital and state.  The state output corresponds to the acknowledged state of the alarm.  To use this output programmatically, the enumeration values must be known. Environment Xenta 511,527,555,701,711,721,731 Cause Not knowing meaning of Alarm State output values in Xenta 700 Resolution The Xenta 700 alarm state enumeration is: 0 - Normal 1 - Passive_unacked 2 - Active_unacked 3 - Active_acked

Issue UNC was upgraded to R2 release 529 from an older version and when the station was started, the following error message was displayed in the Standard Output Window: ---------- Station Starting:   THU MAR 26 14:43:09 2009 ---------- Tridium Niagara Station, r2.301.529.v1 [GafbBldg857] ERROR: Reading FlexSnvtTempSetpt [3928] FlexSnvtTempSetpt#link: 60 *************************************************************** FATAL: Cannot boot station from sns java.io.UTFDataFormatException   Environment UNC-520 with release 522 or 529 software installed. Cause Incompatibility in the FlexSnvtTempSetpt object between the release 514 and release 529 versions of the jar file. Resolution The best way to correct this issue is to perform a manual upgrade of the existing version 514 station. Use the release 514 WorkPlace Pro "Admin Tool" DbAdmin function to backup the running station and get the station as a .sns file to the computer. Use the DbAdmin function to convert the station from .sns to .xml. In the release 529 installation folder, use the AdminInstall command to start the release 529 version of the NiagaraD service. Copy the station folder containing the station to be upgraded from the release 514 stations folder to the release 529 stations folder. Start the release 529 AdminTool and open the Localhost. Highlight the station to be converted. Select the DbAdmin tab and use the convert local function to convert the station from .xml to .sns The converted station is now ready to be installed into the UNC that has already been loaded with I/A Series R2 release 529 software. This same procedure can be used to convert a 514 station to 532 by substituting release 532 for the release 529 references. above.

Issue Parameters, configurations, calibrations and other settings are not stored within the M/STAT, I/STAT, or any of the STR series wall sensors with the exception of the STR-350. No data can be carried with the stat from one controller to another. Environment M/STAT I/STAT STR-150 STR-250 MR-VAV Xenta 102-AX Xenta 121 Xenta 104-A Various other STR series sensors and Xenta controllers Cause The aforementioned stats use only key code to communicate with their associated controllers and do not store any of their own parameters or settings. Resolution These stats may be moved from one controller to the another or a controller may be replaced while maintaining the original stat without carrying over any settings from the original controller.

Issue A jobsite of MNL controllers was done with WorkPlace Tech 4.x.  The original databases are no longer available.  Can they be uploaded with WorkPlace Tech 5.x and will the upload convert them from 4.x to 5.x? Environment WorkPlace Tech versions 4.x and 5.x MNL controllers Cause Loss of original controller databases Resolution Uploading a MNL controller's program does not change anything within the controller.  Only downloads do. If a MNL controller was programmed with WorkPlace Tech 4.x and is uploaded with WorkPlace Tech 5.x, the uploaded file can only work with version 5.x.  If the resulting file is then downloaded to the same controller, the program version in the controller will then be at 5.x.  It will no longer work with 4.x.

Issue Personnel distributions failing due to illegal card numbers configured in personnel objects. Environment CyberStation Personnel Objects Cause Each card type has restrictions as to what site codes can be used and the maximum card number that can be used.  Resolution  The following is a summary of card types and the site codes and card numbers that are available to each. Card Format Site Code Card Number Wiegand26 0 – 255 (8-bit) 0 – 65535 (16-bit) Infinity_37 0 – 4095 (12-bit)    0 – 524287 (19-bit) HIDCorp1000_35 0 – 4095 (12-bit)  0 – 1048575 (20-bit) CustomWiegand 0 - 65535 (16-bit)    0 – 4294967295 (32-bit)   Note: Site codes of 0 cannot be entered through the old style Personnel Editor, use Personnel Manager or set attributes through a list view.

Issue Function Blocks as object controller Environment StruxureWare Building Operation FB Program at site Cause When commissioning the local node with a LNS tools (NL220), one cannot see the functional blocks as object controller in the LNS tool, but rather have all the SNVT in the static node. Is it normal? The problem is, if one has a lot of SNVT, it is not clear. Resolution Functional blocks created do not have a functional block index to be able to present them correctly. All Functional blocks have same index causing the presentation issue mentioned above.

Issue Binding SNVT to AS-L  Environment StruxureWare Building Operation AS-L site Cause About the SNVT, when one binds a SNVT from the AS-L to the LNS network (nvo in AS-L), the AS-L doesn't propagate the value on the LON network. But, when binding a SNVT from the LNS to AS-L (nvi in AS-L) and when one changes the value, the AS-L receives it well and then can use the value in AS-L. Resolution The problem is that we “own the world” that is StruxureWare Building Operation owns the AS and Local Node, so we don’t know that we need to propagate something to someone. This really falls under design issues. A local node is typically only available for LNS network management tools and front ends. It seems this is not the design of the device to be used in another LNS network management tool since StruxureWare Building Operation and the AS-L is a LNS network management tool. Using two different tools complicates systems greatly since there should be only one.

Issue AS-L Loses LON Configuration Environment StruxureWare Building Operation LON environment Cause After commissioning the local node with a LNS tool and if one switches off the power supply of the AS-L, the local node loses the LON configuration and it return in factory configuration 'Domain 18 Subnet 1 node 254'. Now you can just change the domain.  Resolution It seems the local node updates the domain if the domain is updated from LNS. So if you do a Local Node commission than the LNS will not work and if you commission it from LNS local node is not going to update the domain. This really falls under design issues. A local node is typically only available for LNS network management tools and front ends. It seems it is not the design of the device to be used in another LNS network management tool since StruxureWare Building Operation and the AS-L is a LNS network management tool. Using two different tools complicates systems greatly since there should be only one.

Issue The Xenta 913 can only be used for both Modbus and BACnet at the same time if they are being used on separate ports or are both on the IP port. BACnet and Modbus can not both be used on the RS-485 A port at the same time. Environment Xenta 913 XBuilder BACnet Modbus   Cause Only the Ethernet 10 Base-T port on a Xenta 913 may have more than one interface at a time. Resolution The Xenta 913 may interface with BACnet and Modbus at the same time only if: The RS-485 A port is being used for Modbus and the Ethernet 10 Base-T port is being used for BACnet The RS-485 A port is being used for BACnet and the Ethernet 10 Base-T port is being used for  Modbus The Ethernet 10 Base-T port is being used for both BACnet and Modbus and the RS-485 A port is either unused or is being used for only BACnet or Modbus but not both The Xenta 913 may not interface with both BACnet and Modbus if they are both connected to the RS-485 A port.

Issue Mapping a 3rd party bacnet point to a numeric gives 'object attribute not available' Environment Continuum BCX Viconics Stat Cause The path to the object couldn't be found Resolution Deleted the bacnet network Deleted the BCX Find new bacnet Able to map the 3rd party object to the numeric using ReadProperty with no error Note: Mapping a 2nd Viconic stat to the original BCX gave the same error, but mapping either stat to another BCX on the same subnet worked without error prior to the delete/Find.

Issue Can Continuum store a database of biometric data and authenticate based on it without needing an access card? Environment CyberStation Access Controllers Biometrics Cause Desire to use fingerprint only authentication (no card required) with Continuum. Can Continuum store a database of biometric data and authenticate based on it without needing an access card? Resolution Continuum can not store biometric data and authenticate based on it alone. However, Continuum can be integrated with biometrics in several ways. The two most common are: Using smart cards to store the biometric templates. When the card is presented to the biometric reader it transfers the biometric data to the reader and the person's biometric is validated against that stored on the card. Then the card Wiegand data can be sent to the controller for authentication and entry or denial. Using the Security COE Continuum Bioscrypt Integration. Refer to the Continuum - Bioscrypt Integration data sheet.

Issue A Niagara G3 ENC is not communicating via the ethernet (RJ-45) jack.  Here is the output from a serial system shell connection: Press to stop autoboot... Autobooting... Loading image from on-board nand flash ppc824x(james) booting Amic29L040A starting /ffs0 filesystem ETFS_FS_2048 starting message queue handler i2c: Using 100Mhz freq divider DINIT Press ESC to restore factory default username and password... mount: Can't mount / (type io-net) mount: Possible reason: No such device or address if_up: retries exhausted ifconfig: SIOCGIFFLAGS en0: No such device or address writing to routing socket: Network is unreachable : Network is unreachable if_up: retries exhausted ----------------------TCP/IP Network Status------------------------------ ifconfig: SIOCGIFFLAGS en0: No such device or address ----------------------------------------------------------------------------------- Environment Niagara G3 Cause The output from the serial system shell connection indicates a on-board failure of the network communications. Resolution Replace the ENC.

Issue Getting "completion event failure" when doing a commission and download to a Xenta server running as a Lon device in Vista. Environment Vista 5.1.6 Xenta server 5.1.6 Cause If the Xenta 913 have the same IP address(which can happen if it is used as a Xenta server with lon units under it before the Vista will set subnet/node to either 1/126 or 1/127 ) as the lon network typically 1/126 or 1/127 you need to change it using for example Lonmaker. It is not possible with Vista or webpage in Xenta server. You can check the subnet/node in the webpage for the Xenta server under Utilities-Lonworks-domain table. Resolution Change the subnet/node either for the lon network in Vista or for the Xenta server

Issue Trend chart report does not show Trend Chart data Environment CyberStation Cause Maximum number of values in the report not properly set Resolution Make sure to set the 'Maximum number of values' property to include all the data in the log being plotted.

Issue Can 2 comm ports be enabled when using the RTU Xdriver? Product Line Andover Continuum Environment Continuum 9680 99xx 9640 4040 Xdriver Modbus RTU Cause At times it is necessary to have multiple ports enabled for Xdrivers Resolution The ability to enable 2 comm ports using Xdrivers can be done, but is not recommended by the Xdriver developers or supported by PSS. The RTU Xdriver is poll on demand. This type of driver can request a lot of data and starve the CPU on the controller which then makes the polling irregular. If 2 ports are being used then there are typically more devices being added and therefore more points increasing the requests and demand on the controller's CPU. Use one program to control the polling on both ports. Two programs attempting to control the polling asynchronously will cause communication issues.

Issue What is the acceptable range of tolerance for resistance on a supervisory input. Environment i1 controllers i2 controllers b3 controllers I/O modules Cause Doors are being retrofitted, and the resistors that are installed are not 10K ohm and are inaccessible. Resolution The tolerance for the resistance on supervisory inputs is +/- 3%.

Issue Using TimeSync Service in an UNC-520 to directly connect to an internet time sync service, but can not sync time in the UNC.  The following message is displayed in the UNC’s Standard Output Windows when the TimeSyncService debug is turned on: "Error: java.SocketException Message: Timesync aborting: not all servers responded."   Environment Niagara R2 all versions, UNC520, UNC-410, Enterprise Server Cause The port used by R2 TimeSyncService is typically blocked somewhere on the network. Niagara R2 TimeSyncService uses TCP port 37 by default.  Port is block by network domain security policy. Resolution Make sure that all three of the client’s TimeProtocolServer properties are filled in. If only one TimeSync server is being used, enter it for all three TimeSyncServer properties. If the UNC or Enterprise Server still do not sync to the time sync server, then the port may be blocked. The port used by the TImeSyncService must be open. Contacts the site’s IT department and make sure port 37, or whatever port the time sync is configured for, is opened.   NOTE:  I/A Series R2 utilizes TCP port 37 with the standard TIME format (RFC-868).  The official NIST website indicates the TIME protocol using TCP 37 will no longer be supported on March 1, 2013.  R2 does not support other formats (e.g. UDP or NTP).  The recommendation is to configure the Enterprise Server as a time sync server only and configure the UNCs to synchronize to the Enterprise Server's computer time.  The computer running the Enterprise Server will then need to use the standard Windows time sync mechanism and not the R2 time sync mechanism to maintain the time for the computer.

Issue Can the Anti-Passback rules be ignored for certain personnel cards? Environment Access Control: CX9702 CX9900 with AC1 modules CX9680 Netcontroller II with AC1 Modules ACX5720, ACX5740 Cause Often certain site personnel require free access around a site e.g. Security personnel or management. Resolution If Area Anti-Passback is being used then there is the “AllowEntEntEgr” attribute in the personnel object, it is named “Allow Passback Entry” in the Personnel Manager. This attribute is by default False, but can be set to True in any Personnel to ignore Area Anti-Passback rules. This attribute does not apply to Timed Anti-Passback.

Issue At times error logs are truncated from a controller Environment 9680 BCX 4040 BCX9640 ACX 57xx i2 b3 Cause There is a limited number of records that can be stored in controllers and if there have been a lot of error they will eventually get truncated. Resolution Flash memory for the controller error log is divided into 2 sections (A&B) When section A is filled with errors, section B begins to get filled Once both sections are filled, section A gets truncated and begins to fill with new records Once section A is filled, section B gets truncated and so on... There are approximately 8000-9000 records that can be stored in each section

Issue A requirement at some physical access control sites is that at the beginning of the day all access to an area/door is denied until a particular person shows up. Environment CyberStation CX9900 CX9702 CX9680 ACX5740 ACX5720 ACX781 Cause Requirements Resolution Write a PE program in the controller that disables the door at the end of the day and then uses the door's EntryLastSite and EntryLastCard to determine when the person that enables access has arrived in the morning at which point the door is enabled. Sample PE program 'Program is fallthru and triggered by the Second system variable 'Disable door at end of the day If Hour > 17 then   MainEntrance State = Disabled   Stop Endif 'Enable door when Elvis enters the building If MainEntrance State = Disabled then   If MainEntrance EntryLastSite = 123 and MainEntrance EntryLastCard = 456 then     MainEntrance State = Enabled   Endif Endif 'Keep program from getting disabled due to run time error E:   Stop   If door is a dual reader door the program can be modified to disable the door when the person leaves using door attributes ExitLastSite and ExitLastCard