Building Automation Knowledge Base

Issue How to back up a full version of SQL (not express)? Product Line TAC Vista Environment SQL 2005, 2008 full versions, i.e. Enterprise, Standard etc. TAC Vista 5.1.X Cause A customer may wish to backup the TAC Vista log database to prevent data loss if the SQL server crashes. Resolution There are 2 options available, depending on the TAC Vista SQL configuration the customer has configured. If the customer has selected "Typical" on the TAC Vista Server setup "SQL" tab, you can configure this through Vista workstation. Right-click on the Server object in Workstation and select "Properties". Select the "Log Backup" tab and configure the backup schedule there. If the customer has selected "Custom" on the TAC Vista Server Setup "SQL" tab, this can be configured through SQL Management Studio (which is free to download from Microsoft, if the customer doesn't already have it). Start SQL Management Studio and connect to the SQL server instance that is being used for TAC Vista. Expand the SQL server in the tree (in SQL Management Studio) and locate the "Management" folder. Expand that folder and locate the "Maintenance Plans" folder. Right-click on the folder and either select "Maintenance Plan Wizard" or "New Maintenance Plan". Configure as required.    

Issue By default, you are not allowed to shut down/restart the TACLIC/TAC License server when logging in to the Flexnet license admin web application from another PC than local. Product Line TAC Vista  Environment TAC Vista versions 5.1.8 and higher, using the web-based TACLIC tool.  Cause A remote shutdown/restart is required when adding/removing/editing license files in the License Files folder. Resolution The following steps should be done on the PC where the license server is located: In the "server.xml" file located in the "conf" catalogue (...\License Server\conf), edit the following string from " stopServerRemoteAllowed="false" "  to  " stopServerRemoteAllowed="true" " Then save the file and restart the license server.   The setting can also easily be changed using the tool called "TACLicenseServer Settings."

Issue Is it possible to save a copy of a TGML graphic in a standard format such as jpeg, bmp etc? Product Line TAC Vista Environment TGML graphics editor 5.1.X Cause For documentation purposes a customer may wish to have an image of a TGML graphic, perhaps in a system reference guide, with explanatory text. Resolution Open the graphic in TGML graphic editor. Select "Export..." from the file menu and then select the file format in the dialogue that appears.

Issue Specific Trend log stops working in TAC Xenta Get estimated values in some trend logs; others are working Trend log is not retrieved from TAC Xenta Product Line TAC Vista Environment TAC Xenta 301 TAC Xenta 302 TAC Xenta 401 TAC Xenta 282 TAC Xenta 283 TAC Vista Cause The issue can be that there is a "Non value" in the log. For example, if you are logging an expression block with division in it and there is a division by 0. This seems to lock the trend in TAC Vista, and no other values can be collected. Resolution In the properties for the log, click on erase log. This will delete all values in the device. Open your menta and make sure that there is no possibility of division by 0.

Issue When trying to activate an embedded license on a SmartX Server using Device Administrator, the activation fails with the following error message: Failure (error) received when reclaiming an embedded license on an Automation Server   "Embedded operation: Activate failed: ASEmbeddedAPI internal error: Capability request could not be created." Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) All of the above v. 3.0 or higher Cause The cause of this problem is that the trusted storage, i.e., the embedded license database on the SmartX server, is corrupt. The embedded licensing framework undertakes internal checking and if it determines there is a consistency problem, it will consider the trusted storage to be corrupt. This means that no operations to the trusted storage, such as activating licenses, will succeed. At the time of writing, it is unclear why the consistency problems happen. In the server log, you may also observe the following error message: 10:08:06: Executing licensing command 10:08:06: Executing embedded operation: Activate ActivationID: ACT-XXXXXXXXXX-XXXXXX-XXXXXXXX 10:08:11: Embedded operation: Activate failed: ASEmbeddedAPI internal error: Capability request could not be created 10:08:11: Licensing command completed 10:08:11: Activating licenses failed (Real Activation ID replaced with ACT-XXXXXXXXXX-XXXXXX-XXXXXXXX)   Although this process is specific to the "Capability request could not be created" error, similar errors can be corrected by following the steps shown in the resolution. Please attempt all steps before contacting support.   Resolution   Building Operation 2022 v4.0.4  and above Upgrading to the above versions will now resolve the trusted storage corruption and inhibit license activation. Building Operation 3.2.X and up to EBO 2022 v4.0.3   Note: Although this process is specific to the "Capability request could not be created" error, similar errors can be corrected by following the below steps. Please attempt all steps before contacting support.    Clear trusted storage within the server Using Device Administrator select the affected server and Open a PuTTY Console An alternative way of connecting to the server is to use WinSCP. Use File protocol SCP and the admin user. When connected, follow the instructions as per the Word Document also attached below Warm or Cold Start the AS-P If failures still occur, attempt the Offline Activation of Licenses Workflow; The key step is that the license is activated offline and then transferred to the server in two different steps, allowing the license activation process to complete successfully.   Warm or Cold Start the AS-P If there are still failures with either of these options, send a support request through your local support center including the errors seen with each activation attempt.     Building Operation version lower than 3.2.X   If the embedded license is a Client license, there is no need to activate the license. Install the EBO Hotfix 3.0.3.2001 (CP1) or later. This will remove the enforcement of SmartX server Clients in the licensing system. See also article Embedded WebStaion client license when logging directly into a SmartX server no longer needed. Other licenses like SmartDrivers, SNMP, and Personal Dashboards may still need to be activated. Contact your local support center to fix this problem.

Issue Enterprise Server ES crash Product Line EcoStruxure Building Operation Environment Enterprise Server ES Enterprise Central EC Cause The ES/EC runs on a Windows platform and there are circumstances that can lead to a single crash or multiple crashes leaving the ES/EC not running Background - The ES service is usually running. The service can be seen below under the Windows services and via "Building Operation Software Administrator"  The ES v4.0 has crashed and will not restart. The "Building Operation x.x Connect Agent" collects any core dumps and packages them, so they can be quickly analyzed. It also checks if an ES is registered and online, then uploads the core dump files for automatic analysis. If the site is not registered or is offline, then these files are stored locally at %ProgramData%\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\Enterprise [Server|Central]\db\Crash information (default for v4.0 "C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\db\Crash information") The "Building Operation x.x Connect Agent" is a Windows Service and installed with the ES, the service should be left to run continually. If it is not running during an ES crash, the core dump may still get created, but does not get packaged up in a way that can be easily analyzed. Each packed crash dump file may look like "ES_ES_MYCOMPUTER_20221104T121314Z.zip" and likely be between 40MB and 200MB in size. The individual core dump will look like "server_20230314_132853__r4.0.3.176.dmp", but is very time consuming to analyze, without the other associated files Resolution Following a crash,the EC/ES will usually restart and operate correctly, however in some cases the EBO database or install file structure may be damaged and the EC/ES may fail to restart correctly EC/ES has crashed and is now running correctly Send the following information to Support - All core dumps from the "\db\Crash information" folder - All data from the "\db\logs" folder - Ideally a full backup of the ES (with history), always zip before sending to Support If the "Crash information" folder is empty, then check the "Building Operation x.x Connect Agent" is running. It is possible the core dumps have already been uploaded and analyzed automatically EC/ES has crashed, tried to restart but just stops again. (as seen in the first screen shot, "The server has made too many unsuccessful attempts to start..." is seen It is important to gather all the data as stated above, but also collected the EC/ES and AS backups from "\db_backup" It can be useful to get full copy of the files in "/db" Ideally the EC/ES is not critical to the operation of a site, but it can still cause a big problem. Checking the Trace and System logs may give a clue to the problem, e.g. a lack of disk space, but often there are only a few options   Collect the files above, then wait for a reply from support. Please state if the EC/ES is stopped and a resolution is being sort. Reinstall the EC/ES at the same version and choose repair current version, or upgrade to a newer CP Fix version or maintenance version. Uninstall the EC/ES, then re-install the same version with an empty database, then restore the last good backup to the ES. If option 2 or 3 is used, it is still important to log a case with support, so the crash can be investigated. The backup can be checked for errors using the XBK Analyzer.

Issue A Niagara G3 server station was running well for a long time.  Then in a matter of a couple of days, the station began failing to run.  The error listed in the Application Director Output is:   ERROR [java.lang.OutOfMemoryError: GC overhead limit exceeded 13:46:17 20-Mar-14 EDTjava.lang.OutOfMemoryError: GC overhead limit exceeded][sys.leasejava.lang.OutOfMemoryError: GC overhead limit exceeded] Error in run Product Line TAC IA Series Environment I/A Series G3 Enterprise Server Cause There is not enough memory allocated to the Java Virtual Machine (JVM). The email service is keeping a very large outbox because the network email server's IP address was changed. Resolution Increase the Java Virtual Machine (JVM) memory allocation Using a text editor, open the nre.properties file (located in the niagara 'lib' subfolder on the server hard drive). Locate the line: java.options=-Xmx256M. Change it to java.options=-Xmx512M. Empty the outbox file (i.e. delete it) and/or update the email server's IP address.

Issue While editing a graphic, the editors components categories and menu options are too small to be used. This happens when Windows display scaling is not set to 100%. Product Line EcoStruxure Building Operation Environment Graphics Editor High Resolution monitor (4K) Scaling Cause An issue has been identified with how the default scaling used by Windows affects the Graphics Editor in EcoStruxure Building Operation 2.0 and later. Resolution Follow the steps below to work around the problem Update Windows with the latest available updates Update .NET Framework to latest version Change the compatibility settings of the Graphics Editor as outlined below   Open the Graphics Editor application file location   Open the properties for the Graphics Editor application   Override the DPI scaling 

Issue Is there a quick reference I can search to find out what features are included in a particular license When manually adding my Product during offline embedded license workflow, how do I know which Features is included and in what quantity?  Product Line EcoStruxure Building Operation Environment Building Operation EBO 2022 v4.03 and lower  Embedded Offline Licensing Offline Activation of Licenses Workflow Cause Currently, no information lists features for each Product name listed in the Part Number Summary for EBO 2022.  A documentation defect (QC 49762) has been raised, which should resolve this.  This article has been created to assist somewhat during this process while waiting for this to be corrected.  The recommendation, if possible, is to perform license activation online to avoid having to enter this detail.   Resolution Important Note: This information is no longer valid for EBO 2022 (Maintenance Release 4.0.4) and EBO 2023 and greater.  The details below are still provided for reference only and are not needed for these later versions.   Attached are two documents that provide version 3.0 and 4.0 License details.  The documents contain all searchable details, including: Product Name Features Part Numbers     Additional details required for Device Administrator "Feature Name" offline entry:   SpaceLogic Server license details Feature Name (seen in Device Admin) License name (seen in Features document) Description / Comments Automation Server server.as.base   SmartDrivers smartdriver.license   SNMP Notifications server.alarms.snmp   Personal Dashboard client.dashboard   TimescaleDB server.timescale   MQTT Publish/Subscribe server.mqtt.rw Enables EBO, as MQTT Client, to publish data on an MQTT Broker and to subscribe to the same data. Serial Modbus server.modbus.rtu Allows SmartX server serial communication - Modbus RTU Serial MS/TP server.bacnet.mstp Allows SmartX server serial communication - MSTP ES Connection server.connect.to.es Allows SmartX server to be hosted by an Enterprise Server Server I/O server.io Allows SmartX server to use IO Field Devices server.device.as Allows SmartX server to host one field device SAML Authentication server.as.auth.saml   Zoning client.zoning Enables use of zoning tools BACnet IP server.bacnet.ip Allows SmartX Server to communicate using BACnet IP Software Assurance software.assurance         Feature Name (Automatically included with bundle licenses)   client.webstation Allows Webstation to log on to an AS   server.cloud.customer Cloud connectivity - Checked by Cloud SMS (Production)   server.as.scalable Included in the license that allows SpaceLogic servers upgrades. i.e. Standalone to Standard etc.   Example: Product Name: ASP-NL Bundle upgrade - Full to ASP Full    Search the document for the product name in the attached document. In this case, the version 4 document.  Below is the result seen in the document: From this, the associated Features and Quantity are shown. In Device Administrator, then add the respective features and quantities when adding the product manually to the Entitlement. Use the above table to correlate between Feature Name and License Name. The example shown below:  

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue If the passphrase is incorrect when trying to install a station .bog, the following error message can appear; Transfer failed. com.tridium.platform.daemon.DaemonResponseException: Request to platform daemon at (stationName) failed: bad return code to commit file instance at com.tridium.platform.daemon.DaemonFileUtil.transfer(DaemonFileUtil.java:661) at com.tridium.install.InstallScenario.commit(InstallScenario.java:1444) at com.tridium.platDaemon.ui.stationtransfer.FinalStep.run(FinalStep.java:341) at java.lang.Thread.run(Thread.java:750) Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace Cause The .bog has not been properly placed in the User Home / Stations for copying into the device or the passphrase is not known. Resolution Always use the Station Copier to install the .bog from the User Home / Stations path If the error message appears, open Workbench and navigate to the "Stations" folder under the "User Home" Expand the station you are attempting to install Double-click the .bog (1) and locate the "Bog File Protection" icon at the top of the page (2) Select the (1) "Force the File to start..." radio button and (2) Update.  Note the information regarding existing passwords. If the message "Cannot display page" occurs when you double click the .bog, open the "Details" and look for missing modules "Cannot load module '......=.....'. Any missing modules will need to be available on the Jace or ES before attempting the force start operation.  

Issue WPT and WPTE require certain Microsoft Security updates for Visio and for Office running on the host machines. Issues currently observed: Different and various functions in the fluent ribbon do not work or the ribbon does not appear. The following error "Application compile failure during save operation" is seen when saving/compiling an application in WorkPlace Tech Editor Product Line EcoStruxure Building Operation, TAC IA Series Environment Visio 2010, 2013, 2016, 2019, 2021(.msi install)  Visio 2013, 2016, 2019, 2021 (subscription "Click to Run", Plan 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run", Plan 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Note: Visio 2019 and Visio 2021 are not supported in 5.9.4 or EBO versions before EBO 2022.  Visio 2019 and Visio 2021 are supported when using Workplace Tech 5.10.x and EBO 2022. Cause Interoperability of Visio and Office can cause problems with Workplace Tech and Workplace Tech Editor if these MS16-70 updates are not applied.  If the Office / Visio product is "Click to Run" the software has not been updated to the latest version. Resolution Install the updates from Microsoft Update Catalog To use the catalog, copy and paste the KB number into the "search".  Always select the 32-bit version of the update. Visio 2010 32 bit KB3114872                Office 2010  KB3115198 select 32 bit  Visio 2013 32 bit KB3115020                Office 2013  KB3115173 select 32 bit  Visio 2016/2019 32 bit KB3115041       Office 2016  KB3115144 select 32 bit Visio 2016/2019 32 bit KB4484333 NOTE:  If the Visio or Office is "Click to Run" (subscription such as Office 365, Plan 2) rather than from a Microsoft Office .msi, the product should be upgraded by using the Update Options feature If you try and install the KB/.msi install patches, you will get this message

Issue Creating an Extended Trend Log for b3 (Infinet i1/i2) Point and Value Logs Product Line EcoStruxure Building Operation Environment b3 BACnet Controller Infinet i1 & i2 Controller Building Operation Automation Server, AS, ASP, ASB Extended Trend Logs (ETLs) Cause Using an extended trend log to store log records for long periods of time. The extended trend log is often saved on a higher-level server with more storage capacity. This extra storage capacity enables the server to store more records before overwriting the old ones. For more information, see WebHelp. Configure extended trend logs for b3/i1/i2 devices the same way as configuring extended trend logs in other Building Operation devices. There is one difference, however. do not use smart logs when configuring extended trend logs in b3 BACnet devices. Instead of using smart logs, use the Maximum Transfer Interval property to specify the transfer interval. Resolution In Listview, select the b3/Infinet Object (point or value), click Properties/Advanced Multiply the "Log records" by the "Log interval" to calculate the maximum transfer interval. The "maximum transfer interval" is the frequency at which the extended trend log will transfer log records from the b3/Infinet Object before any entries in the b3/Infinet controller log are overwritten Right click the object, choose New then "Extended Trend Log" In the Create Object box, set Smart Log to False, Set the "Maximum transfer interval" to less than that calculated above (2) Click Create For Infinet systems always refer to Infinet under the hood otherwise the creation is as the Webhelp for creating BACnet B3 Logs In theory it would be possible to create the Extended Trend Log in an ES (where there is more storage capacity), but this could introduce other timing and bandwidth issues, so it is usually best to keep the first Extended Trend Log in the AS, then extend this to a second Extended Trend Log in the ES, as shown. (the second ETL in the ES scan use smart logging in the usual way) If significant logging is required then External Log Storage should be considered. (the B3 or i1/i2 logs still need to be collected via Extended Trend Logs)    

Issue Capturing packets from Zigbee Standard Security Network shows packets marked Bad FCS or Encrypted Payload Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Room Controller Cause Zigbee Standard Security Networks implement multiple keys to encrypt data for the Zigbee Network and each device Resolution This resolution assumes you have a Zigbee adapter that can capture packets in Wireshark.   Ensure zigbee_pc_keys are available in each profile you are going to use to analyze the Zigbee packets. The file location is generally: %AppData%\Roaming\Wireshark\profiles\<Profile Name>\zigbee_pc_keys   Open Wireshark and configure the Zigbee adapter NOTE: Please substitute your adapter name if not using the TI CC2531 adapter. Open Wireshark Click the gear next to the 'TI CC2531 802.15.4 packet sniffer' Select the known channel (11-26) and click Save Click on 'TI CC2531 802.15.4 packet sniffer' to start capturing Update formatting to resolve Bad FCS packets Go to Edit -> Preferences -> Protocols Select IEEE 802.15.4 Depending on your Wireshark version, check or "TI CC24XX FCS Format" or set FCS format = "TI CC24xx metadata" Add default link key for Zigbee Alliance Go to Edit -> Preferences -> Protocols Select ZigBee Set Security Level = AES-128 Encryption, 32-bit Integrity Protection Click Edit next to Pre-configured Keys Click + and Enter Wireshark Key from below, Byte Order = Normal, and Label Enter the Zigbee Alliance Default Link Key Key = 5A:69:67:42:65:65:41:6C:6C:69:61:6E:63:65:30:39 Key Value = 5A6967426565416C6C69616E63653039 Remove colons (:) for entry into Wireshark ByteOrder = Normal Label = ZigbeeAlliance09 Find and add Standard Network Key Ensure you have configured the default transport key (above). Use this display filter to find the request Key exchange: zbee.sec.decryption_key Find Standard Network Key Look in the Info column for the Transport Key and select it Expand Zigbee Application Support Layer Command Expand Command Frame: Transport Key to see Key Type: Standard Network Key and Key: shows the value Right-click on the key -> Copy -> Value Right-click on the Zigbee Network Layer Data -> Protocol Preferences -> Open Zigbee Network Layer Preferences Click Edit next to Pre-configured Keys Click + and paste under Key, leave Byte Order = Normal, and add Label. RECOMMENDED: Use Descriptive label because you will have Network Key per Zigbee Network, so includes Device, PAN ID, and NetworkKey, ie ASP087_12345_NetworkKey Find and add Trust Center Link Key PER device Ensure the following are configured: formatting, transport key, and Standard Network Key (above). Use this display filter to find the request Key exchange: zbee.sec.decryption_key Since this is per device, one can include the Network Address for the device. Example: If the network address of the device is 0x2074, the display filter would be: zbee.sec.decryption_key and zbee_nwk.addr == 0x2074 Find Trust Center Link Key per device Using the Info field, find the pair of Request Key and Transport Key. The Request Key will have Source = Device Network Address, and the Transport Key will have the Destination = Device Network Address. Click on the Transport Key packet Expand Zigbee Application Support Layer Command Expand Command Frame: Transport Key to see Key Type: Trust Center Link Key and Key: shows the value Right-click on the key -> Copy -> Value Right-click on the Zigbee Network Layer Data -> Protocol Preferences -> Open Zigbee Network Layer Preferences Click Edit next to Pre-configured Keys Click + and paste under Key, leave Byte Order = Normal, and add Label. RECOMMENDED: Use a Descriptive label because you will have a Key per device, so includes Device, Network Address, and Trust Center Link Key, ie TH907-01_0x2074_TCLK

Issue What diagnostic information is available within Niagara that can be sent to Product Support or acted on locally? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series Jace Cause Jace or Enterprise Server operating slow or specific problems are causing the need for debugging a station or platform Resolution There are several diagnostic tools available: Check the station Resource Manager Right-click on the station and select "Views - Station Summary" This will open up a resource monitor page where you can check CPU and memory usage.  The CPU should not be consistently above 80%.  Spiking is common as the process is executing and completing tasks.  There are other things easily referenced here also. Heap memory will vary as well.  It can slowly increase until a garbage collection cycle releases unused heap back to the pool.  You should never use more than 75% of the total available heap memory. Heap Memory is primarily used by station modules and java program objects, so if the memory usage is high, these 2 might be the main reasons Engine Hogs   Right-click on the station, and select "Spy". From the main view, click on "sysManagers". Click "engineManager" and then scroll down to find "Engine Hogs". Clicking Engine Hogs will open a list of the main components of the station and a column on the right-hand side will display the average execution time of the component. Review the top 10 or so and see if any are taking an extraordinary amount of time.  This can help to locate improperly executing objects. Driver Poll Rates Drivers that are based on polling data, like BACnet when COV is not enabled, or Modbus constantly run commands to read data based on the fast, normal, and slow configured rates.  Open the Poll Service under the network the points are being polled on. Looking at the property sheet of the driver, it is important to verify that the cycle time (1) for each rate (fast/normal/slow) is always equal to, or below the actual time configured (2) for that rate. The defaults are 1 second for Fast Cycle Time, 5 seconds for the Normal Cycle Time and 30 seconds for the Slow Cycle Time. Seeing a longer cycle time is usually an indication that the network is saturated with commands and may cause the Jace/Niagara controller to be slow with heavy use of controller resources.  There are several ways to correct this: changing the polling rate spreading the number of objects being polled at each rate, etc. In this example, all points (3) are in the "normal" bucket. Application Director console The "Application Director" (under "Platform") shows a live console output.  Open it by clicking the option under the platform Copy the content of the Application Director, or "stream to file" to send the content to support. It will be essential to help the support engineer to understand the problems in the station.  Add more debug information to the Application Director console You can add more granularity to the messages in the Application Director for a deeper look into possible issues. This can be accomplished in 2 different ways: Right-click on the station, and select "Spy". Then, select "logSetup" on the main view From the list that appears, you can scroll and find appropriate topics to log and you can select at what level you want the information to appear.  This will add traffic to the application Director window so be careful how "fine" and how many logs you enable.  It might be good to consult with support before enabling these logs. example; bacnet.debug/finest if you select this box. Debug Service   Select the "DebugService" from the station "Services" In the Log Category, type a few letters of the topic and scroll to find what you are interested in logging From the pulldown menu, determine the granularity of the log Click the plus Click "Save" Setting this logging and streaming the output to a file will allow information to be sent to support for better diagnostics if required.  Remember to set this logging back to "Default" when done so the Application Director is not overwhelmed with information when you are only trying to view normal station activity.

Issue How to add a third party LonWorks device? How to create a LonWorks device template? Why is a device template not available after import? Product Line EcoStruxure Building Operation Environment Building Operation version 1.8 and above Building Operation WorkStation Cause In order to add a third party device, need to create a device template (XIF file) for it. Device templates must be created in the server that the controller will created under. If a third party controller is going to be added to an AS-P that is associated to an ES, then the template must be created when logged into the AS-P directly. Resolution To import a device template   Log in to the SmartStruxure Server in which the device will be added underneath. In Workstation, Right mouse click on the Server and select LonWorks then import device Template. In the XIF file box, select the XIF file to import. Click Import. In the Template Name field, type a name for the template. Click OK. In the Import Device Template box, click Close. Now, this third party device template will be listed when adding a device into the LonWorks network. Note: If the device template refers to NVT or CPTs not on your system, you will be prompted to import necessary resource files. When the resource files have been imported, the device template import restarts. When finished, the device template is imported and available when creating a new device.

Issue Using Modbus TCP and Modbus Serial (EIA/TIA-485) on an AS together? Product Line EcoStruxure Building Operation. Environment AS-P Modbus TPC Modbus Serial Cause Communicating with two third party devices simultaneously. Both are using the Modbus communication protocol. One is Modbus TCP, the other Modbus Serial (EIA/TIA-485). Resolution Modbus TCP and Modbus Serial (EIA/TIA-485) can be used together on an AS-P. This configuration is supported and has been used many times.

Issue Can SLPSXC2 CO2 sensor calibration be used with both methods (ABC standard and Fresh Air process) at the same time? Product Line Field Devices. Environment Building Operation SmartX Living Space Sensor. Cause SLPSXC2 CO2 can be calibrated using two different methods. Automatic Baseline Calibration(ABC) The ABC algorithm constantly keeps track of the sensor’s lowest reading over a pre-configured time interval and slowly corrects for any long-term drift detected when compared to the expected fresh air value of 400 ppm. ABC calibration is enabled/disabled through coil 4 (invoke = enable ABC). Manual Calibration Coil 11 triggers the manual calibration (FRC 400ppm) => this will tell the sensor that the current level of CO2 should be interpreted as 400ppm. When setting this register to 1, it automatically goes back to 0 a couple of seconds later. Setting Coil 11 to value 1 is the same as pressing the calibration button. Resolution The both methods of calibration can be used simultaneously since one method is for correcting drift over time (1 week intervals), the other is a manually executed reset.   The only error would come if the unit was exposed to high CO2 concentrations at night, inducing abnormal averages. If ABC is disabled, manual calibration would need to be performed more frequently.

Issue What is the latest firmware version for the MNL-800? Product Line TAC IA Series Environment I/A MNL-800 Cause Upgrade the device to the latest firmware. Resolution The latest firmware version is 2.0 (p/n MNEA-810-200), which was released in January 2004. See Announcement 04-01 listing the features of this version. Announcement regarding the end of commercialization of this part 

Issue There is no built-in Credential Type for the HID 37-Bit badge with no site code (H10302). Product Line Security Expert Environment Security Expert Server Access Card Format Cause Security Expert does not have the HID 37-Bit badge (H10302) with no site code as a built-in available Credential Type. Resolution 1) In the Security Expert Client, select Sites -> Credential Types 2) Create a new Credential Type with a name of your choosing. 3) Under Configuration, select the Format as Wiegand. 4) In the field labeled Wiegand or TLV Format, enter the following exactly as written:                                                        A,FACILITY,0,MSB,BIN__B,CARD,35,MSB,BIN__PBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBP_EXXXXXXXXXXXXXXXXXX.................._..................XXXXXXXXXXXXXXXXXXO 5) Save   NOTE: This article assumes that the reader is familiar with creating and deploying Custom Credentials, If this is not the case, then please reference the Complex Transition Programming section of the Transitioning Continuum Sites to Security Expert - Transition Guide

Issue How to populate customized information on the SpaceLogic Sensor display Product Line EcoStruxure Building Operation Environment SpaceLogic Living Space Sensor Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation Workstation Cause Additional information required on how to customize information to be displayed on the SpaceLogic sensor Resolution Note: This feature may not work in controller FW V4.00.x, due to know issue Custom value text is not displayed and/or updated on the SmartX sensor device, in this case please upgrade controller firmware to V5.00.1 or higher. Before starting, make sure the Integrator Menu icon and the custom information page have been activated: The Integrator Menu icon can be configured under "SmartX Sensor Device/ Display/ Button and Scene configuration" as shown in the screenshot below: Turn on "Allow custom information page" under "SmartX Sensor Device/ Display /Advanced" tab. By doing this, the custom information page is created under the Integrator menu icon of SmartX Sensor Display:        To show how to add custom information to the custom information page of SmartX Sensor display, create a sample script program, where DI1 is a digital input and Status1 is a string output. numeric input DI1 String output Status1 If DI1 = on then Status1="running" Else Status1="not running"​   In this program, when DI1 is on, the Status1 gets the string value of “Running”, otherwise the Status1 gets the string value of “Not Running”. DI1 is bound to a Digital Value (Green Arrows) under the Application folder and Status1 is bound to the CustomValueText1 (Red Arrows) as shown below:   Open the Watch pane, under the View tab, and add Digital Value and CustomValueText1 (access it through the “SmartX Sensor Device/ Display/ Basic” tab) to it.  When the Digital Value is Active the Custom value text 1 shows “Running”. On the SmartX Sensor, navigate to the custom page through the Integrator menu icon, this will show the “Running” string. Likewise the “Not Running” string would be populated on the SmartX Sensor custom information page screen when the Digital Value is Inactive.