Building Automation Knowledge Base

Issue Can additional resources be added to an ENC-SW (Soft JACE) to increase the resources over the 30,000 KRu (30 Million) limit? Environment I/A Series G3, ENC-SW Cause Can additional resources be added to an ENC-SW (Soft JACE) to increase the resources over the 30,000 KRu (30 Million) limit? Resolution The I/A Series G3 Soft JACE can be initially purchased to support 10,000 KRu (10 Million) resources.  Additional resources can be added to the 10,000 KRu (10 Million) version to increase the total to 30,000 KRu (30 Million).  The maximum number of licensed resources per ENC-SW (Soft JACE) is 30,000 KRu (30 Million). ENC-SW-1M  >> Support for 10,000 KRu (10 Million) resources ENC-SW-2MU >> Upgrade ENC-SW-1M to increase total to 30,000 KRu (30 Million) resources

Issue Can I remove the permanent override feature or limit the maximum override duration from the station or an individual point in I/A Series G3? Environment I/A Series G3 Cause Can I remove the permanent override feature or limit the maximum override duration from the station or an individual point in I/A Series G3? Resolution Starting in version 3.4.51, the permanent override can be removed globally from the station by adding a facet to the SysInfo facets property on the root of the station. Add a new BRelTime value to the SysInfo facets and assign it the name "maxOverrideDuration." This enables a station global limit on the duration for any control point. The value of this BRelTime should be the MAX duration allowed. A value of zero means that 'Permanent' is allowed. A non-zero value limits the custom to a maximum time value.  Note that 'Permanent' is the default if no "maxOverrideDuration" facet is found. Starting in version 3.5.25, the feature was enhanced to allow specifying the max duration on an individual control point basis. Follow the same procedure as defined above but add a new BRelTime value to the individual point's facet. Example: Right click on the station's Config container and select View - Property Sheet. Click on the Sys Info >> to open the Config Facets dialog box. Select + to add a facet. Click inside the Key area and enter the new key name maxOverrideDuration. Click on the Type drop down and select RelTime. Click on the Value ... and enter the desired time. Select OK

Issue What is the maximum number of TCP connections on an I/A Series R2 UNC running a Modbus TCP driver? Environment I/A Series R2, UNC-410, UNC-520 Cause What is the maximum number of TCP connections on an I/A Series R2 UNC running a Modbus TCP driver? Resolution The recommended maximum number of connections is 24.  The Modbus document specifies the following. maximumConnections: Default is 1 (one). If multiple Master TCP devices need to simultaneously access the station as a Modbus slave, set this to that number. Note Each Modbus TCP device and/or Modbus TCP gateway shadowed in the station uses a separate station processing thread for device communications. Only finite amount of processing threads are available. To ensure proper performance, these maximum limits of Modbus TCP devices or gateways are recommended in any station, by JACE (UNC) platform. JACE-4 (UNC-410) and JACE-5 (UNC-510 and UNC-520): 24 maximum  

Issue Can I set up a door in Continuum which allows either a card validation OR a general code validation? Environment AC-1 family HID RK40 Reader/Keypad Cause Customer wants employees to access a gated area using their badges and the garbage company to enter a general code to get to the dumpster (they don't want to have to issue the garbage company a badge.)  Can the door object be set up to do this? Resolution No, the access validation is coded as an "AND" not an "OR". What is meant by this is that when a door object is configured with the checkboxes for Validate Site, Validate Card and Validate General Code, the person must present a valid card and enter a general code - it is not either/or. The easiest workaround for this is to add another AC-1,  another reader and create a second door with a different configuration. Different groups of people will be instructed to use different readers.     

Issue What is the part number for the female connectors to plug in the right side of a Netcontroller or I/O Module Environment Netcontroller CX9900, CX9940 Netcontroller II, all I/O Modules Cause The part number for the I/O Module connectors is not listed on the I/O Systems reference guide. Resolution The part number for the Female (Right hand) connectors for I/O Modules and Netcontrollers is: P/N - 01-0010-840 bag of 20 connectors

Issue User account with read rights have admin access to all Xenta web pages webserver access thru Vista Environment Vista Xenta   Cause When the default settings are used, all users in TAC Vista Workstation have full access to all pages in Xenta Server regardless of their rights in Vista. This is due to the fact that the Vista Workstation user uses the root account to access Xenta Server. The root account always has full permissions to objects in Xenta Server. Resolution Enable Enhanced Xenta Server web access Under Vista server right click on $system object and choose properties (Need to have admin rights) Enable "Enhanced Xenta Server web access" Click ok and log in the user that should only have read rights.

Issue Values are not updating in a specific TGML graphic in webstation. Red x on all values in a TGML graphic, other graphics working fine. Crossed out values in TGML graphic. String value (text) with " in the text not displaying Product Line TAC Vista Environment TAC Vista 5.1.6 TAC Webstation 5.1.6 Cause If there is a string value (text value) in the graphic with the a double quote quotation mark (") in the text, all signals stop updating on that graphic. Resolution Make sure there are no " in any string on the graphic.

Issue When editing a Xenta Server from Vista, an old version of the XBuilder project will open and you will be asked to convert it. Environment TAC Vista TAC Xbuilder Cause Under some circumstances, after upgrading a Xbuilder project the old xbp file will still remain in the project folder. When one does Edit in Vista Workstation the XB project is unpacked in a Windows user temp folder. After that XB searches for *.xbp files and take the first one found to open. If you for example have converted a 5.1.5 project to 5.1.6, there may be both a .xbp515 file and a xbp516 file. It is  the old one (.xbp515) that will be opened, since it's alphabetically first.   Update: In v5.1.7 and later, Xbuilder will always open the latest version of the project. Note that it will go for the latest file extension (xbpXXX) and not by the date of the files. Resolution Find the zip fie associated with the Xbuilder project, for example C9F20001.zip located in the db\$thisfil, and extract it to a temporary folder. Once extracted delete or rename the old xbp file (project.xbp515 in the example above). Zip the folder that has all the previous project version removed back to db\$thisfil folder using the same name, overwriting the old one.   Update: In v5.1.7 and later, Xbuilder will always open the latest version of the project. Note that it will go for the latest file extension (xbpXXX) and not by the date of the files.

Issue Is the b4920 still available for new purchase and is it still supported? Environment b4920 Cause Is the b4920 still available for new purchase and is it still supported? Resolution Yes, the b4920 is still available as of this article publication (October 2011). However, the same functionality can be obtained less expensively by purchasing a bCX1 with 127 node support AND a b3920. In addition you get the added reliability of distributing the combined functionality across two different devices. If a b4920 goes down you lose control of your on-board IO and communication to your Infinet or MS/TP bus. If you lose one of two devices the other will continue to operate. On the other hand, the b4920 takes up less physical space than the two devices.

Issue Even though Windows Server 2008 R2 is exclusively a 64-bit operating system, 32-bit applications are supported by enabling the WoW64 optional feature. NOTE: These are general instructions for utilizing the WoW64 function. Not all Schneider Software will be able to run in an emulated environment. If uncertain, please check with Product Support Services to ensure proper installation. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows Server 2008 R2 WoW64 feature. All 64bit OS Cause If the WoW64 feature is not enabled and you try to run a 32-bit application, the application will fail to execute. WoW64 option in in undesired state. Resolution If the WoW64 feature is not enabled and you try to run a 32-bit application, the application will fail to execute. The WoW64 execution layer is an optional component that is installed by default on R2 releases. You can save resources by removing the feature if you are not going to be running 32-bit applications on your Server Core install. Install the WoW64 Execution Layer using the following command: dism /online /enable-feature /featurename:ServerCore-WOW64 If your solution has a .NET 32-bit dependency, then also invoke the following sequence: dism /online /enable-feature /featurename:NetFx2-ServerCore dism /online /enable-feature /featurename:NetFx2-ServerCore-WOW64 Note: In Windows Server 2008 R2 RC1, WoW64 is enabled by default. If you don't want WoW64 enabled, just disable the feature as follows:  dism /online /disable-feature /featurename:ServerCore-WOW64

Issue My customer does not want to have to make changes to schedules in different controllers when changing door unlock times or personnel access times to areas. How can this be solved? Product Line Andover Continuum Environment CyberStation ACX5720, ACX5740 NetController Refresh Cause How to consolidate door unlock schedules in different controllers. Resolution Multiple solutions: 1. The easiest and recommended method is to create the schedule in one controller and simply enter the numeric being set by that schedule in all the applicable door objects, whether in that controller or other controllers.  When you look at the point in the door editor, if it's in another controller it will include the path to the point. This "remote" point becomes part of the import/export (aka IE) table in the controller in which the door is programmed. Even if communication to the remote controller is lost, the import/export table in the door controller will hold the value obtained from the last successful IE table update.  The IE system is very efficient - when the point in the "host" controller changes, that controller knows to update the other controllers to which it exports the point. There is only one downside to this - for a digital point, like a schedule numeric, which  does not change often, if the controller looking for the change misses it, the value there will not be updated. To eliminate this problem always include in the controller with the schedule numeric(s) a program that "refreshes" the value of the schedule numeric(s). A simple fallthru program triggered by minute works great. The syntax is: ++++++++++++ Set ScheduleNumeric1Name refresh to true Set ScheduleNumeric2Name refresh to true  etc  ++++++++++++ 2. Another solution is more complicated but will also work. Set up a schedule and schedule numeric point in one controller. We'll call this the schedule host controller. Then set up a schedule numeric point and program in all the other applicable door controllers that synchronizes (mirrors) the local numeric point to the host controller point. Make sure you use a Line E in the program and alarm if the program becomes, or keeps trying to become disabled.  Also, for the "next guy" who is trying to understand the system, you may want to enter, in the description field of the local flags, what is setting the flags, ie, the program name. 

Issue Is a Menta License required in order to program  the Menta in a Xenta 711? Environment 711 Vista Menta licensing Cause Licensing is unlocked from the factory for "711 Menta." Resolution No License is necessary.

Issue Following a clean upgrade from Continuum 1.74 to 1.93, all ACX78x controllers show their No Server LED illuminated.  Environment ACX780 ACX781 Cause The SystemStatus system variable value is No Database. The AccessServer system variable on the ACX78x controller is not set to the ACCID of the primary access server workstation. Resolution Set the value of SystemStatus to Normal. An ACX78x controller must have it's AccessServer system variable set to 0 or to it's own ACCID.  While setting it to any other value, including the value of a workstations ACCID will cause the No Server LED to illuminate. 

Issue How to erase all data from EEPROM in a Microsmart controller. Environment Any DMS Microsmart controller - firmware revisions 9.x, 10.x, 11.x Cause Preparing a Microsmart controller for a database installation. Resolution The database of a Microsmart controller is held in nonvolatile memory (EEPROM).  The address switch may be used to erase all information held in EEPROM.  To clear the database, set all address switches ON (positions 1-8 closed).  Remove and subsequently restore power to the controller.  After several seconds, the controller database will be cleared. Remove power from the controller and reset the address switch configuration to its proper setting.  Restore power to the controller.

Issue The Sigma Log configurations are not visible in the configuration window. Environment Sigma Logging Configuration LogCNF.rec Cause The LogCNF.rec file has not been upgraded when the site was upgraded to Sigma 4.05 SEB. Resolution Shutdown the Sigma client and server. Copy a backup of  the LogCNF.rec file to  the C:\Sigma\Data\Server???\ folder. Where ??? is the server number. Run C:\Sigma\BinUtils\SigUpgrade.exe Restart the Sigma server and client and check the log configuration.

Issue How to create a local String Variable in a Xenta 731. Data Type String is not allowed in this node. When trying to set data type to string. Environment TAC Xbuilder Cause The datatype string can only be used for SNVT str_asc and signals connected to SNVTs of this type. Resolution To get a String signal you have to use snvt_str_asc.

Issue Customer would like to eliminate using a relay on a digital input by monitoring for 24V directly.  Environment i2 / b3 terminal unit controllers Cause Customer would like to eliminate using a relay on a digital input by monitoring for 24V directly.  Resolution The input protection is rated for "24 VAC or 24 VDC temporarily on any single channel, +/- 1000V transients". Beyond a temporary 24V on an input will likely cause all the inputs on the controller to read incorrectly and prolonged exposure will likely cause permanent damage to the input circuitry on the board. A 24V relay with a contact wired to the input must be used.   

Issue Graphics screens that used piping widgets in releases prior to 3.5.34 look misaligned when upgraded to 3.5.34 or greater. Environment Niagara G3 software Cause All releases prior to 3.5.34 had an alignment issue with the pipe widgets. This was overcome by manually moving the pipe widgets until they lined up.  Release 3.5.34 is the release in which this alignment issue has been corrected.  Therefore the manual adjustments made during creation are no longer needed.    Graphics with piping brought forward by a software upgrade to 3.5.34 or greater will look misaligned due to the manual adjustments that were made when they were created. Resolution Release 3.5.34 and 3.6 have correct pipe widget alignment so upgrading older piping graphics (created prior to 3.5.34) to this level will require manual alignment correction.

Issue Generating a Xbuilder project results in the error message "The size of the generated project is xxxx KB, which exceeds the maximum size 8192 KB". Environment Xbuilder 5.x.x Cause The generated project size exceeds the maximum limit due to the following reasons: The project contents made up of graphic pages, inserted networks (LON, I/NET, etc), large images (BMP, GIF, etc), or imported files in the UserTargetImage directory cause the project to exceed the limit. The option "Send Project backup file to target device" is checked and this causes pushes the project size over the limit. Resolution Generate the Xbuilder project to see how far above the limit the project currently is. Open the Project\Settings and uncheck the "Send Project backup file to target device" and regenerate the project to see the difference in file size. If the size difference is significant then check for large files in the project directory that should not be sent to the device such as project or device documentation files such as PDFs. Remove these files from the Xbuilder project directory and generate the project again.  Search the Xbuilder project directory for the largest size files such as graphic pages and try to find way to reduce the size by converting background image formats that will result in smaller file sizes. Example convert BMP file to PNG or JPG format.

Issue Xenta 913 will not communicate with the Bacnet device. Wireshark does not show any packets between 913 and Bacnet device Environment Xenta 913 Cause The Xenta 913 has been installed on a TCP/IP network with a switch between the Xenta 913 and Bacnet device. Resolution A basic switch does not pass broadcast messages that a Xenta 913 uses to talk to Bacnet device. The solution to this issue is to replace the switch with a Hub or use a managed switch. If a managed switch is used it will need to be configured to pass broadcast messages from the Xenta 913 to the Bacnet device.