Building Automation Knowledge Base

Issue Save time in the field by using the different functions Newron NL220 has to offer. This article contains some tips, tricks, suggestions and ideas. Product Line TAC IA Series, TAC Vista Environment NL220 Cause By not using all of the different tools within NL220 it can take much longer to complete a checkout of a database or resolve a problem. There are a number of shortcuts and hotkeys that can save a substantial amount of time. Some examples include database searches, browser window functions, filters, attaching documents, and meanings behind network menu options. Any addition questions or information can be found by contacting Newron here. Resolution Other Helpful NL220 Articles and PDFs NL220 Manual - Click here Starting a NL220 database - Click here Echelon LonMaker and Newron NL220 on 64-bit operating systems Ordering more LNS credits Ordering more Newron NL220 credits The difference between NL220I and NL220M dongles How to Rehost an NL220 Dongle to another PC LOYTEC NIC-USB in NL220 Creating LNS database in NL220 and transferring it into TAC Vista procedures outline Adding a Xenta Programmable Controller to an NL220 System Downloading new NXE or APB files using NL220   Searching the Database There are multiple ways to perform a search in the NL220 database depending on what is trying to be found. At the top of the NL220 window there is a search bar as seen above. The buttons found on this toolbar are defined below. When performing a search there are four different ways that a name can be searched. Using an asterisk after the name means that NL220 will search for anything that begins with those characters. Example: Name*   Using an asterisk before the name means that NL220 will search for anything that ends with those characters. Example: *Name   Using an asterisk before and after the name means that NL220 will search anything with those characters somewhere in the name. Example: *Name*   If no asterisks are used then NL220 will search for an exact match of those characters. Example: Name   General Toolbar The general toolbar at the top of the NL220 window has many useful shortcuts and features. Descriptions of some of these tools can be found below.    To use the automatic browser feature , the desired network variables must first be selected in the device templates. Select the template tab at the bottom of the database tree window.   Double click on the template that is desired for automatic browse. This example is using the 102-AX template.   Select the NVs tab in the device template settings window. Check the box in the browse column next to all network variables to include in automatic browse.   Click on the Subsystem tab  at the bottom of the database tree window.   Select the automatic browse button and click on a controller that is using the template that was modified. It will automatically open up the browse window with only those network variables.   Filter Toolbar The filter toolbar seen above is found at the top of the tree window. This toolbar contains the ability to look at nodes in a specific state like commissioned or uncommissioned, only display specific types of network variables, or even filter nodes and variables by name.    Network Functions Right clicking on objects in the tree window gives the pop up menu that contains the Network menu.  The functions of these icons are defined in the chart below.       Network Variables If changes have been made to the XIF file of a controller, the change needs to be applied to the network variables of the application devices that use the template. Click on the Templates tab at the bottom of the tree window. Right click on the template that needs to updated and select "Rename variables of all application devices" A prompt will open that says "Do you want to rename all network variables of the application devices with the template name?". By clicking yes, this will rename all of the network variables of the devices that reference this template to match the names found in the template. Note: Once this has been completed double check the SNVT connections that have been created already. After the rename, it may change the SNVT order if a SNVT was renamed or removed  from the programming. This will cause connections to be binding the wrong variables together.   Creating a New Device Template If adding a new device to the database, a new device template may need to be created. See Adding a Xenta Programmable Controller to an NL220 System for instruction on how to add a Xenta programmable controller to a NL220 system. Click on the Templates tab at the bottom of the tree window. Right click anywhere in the Templates pane and click on "New device template..." In the New device template box, enter the name of the new template and browse the XIF file into the "Description file" box.    

Issue Java is no longer available or supported in most web browsers so accessing Niagara using the Java Applet is no longer possible Product Line TAC IA Series Environment I/A Series G3 Enterprise Server/Jace 3.8U4 I/A Series N4 Enterprise Server/Jace 4.4U3 and subsequent Cause Oracle announced the end-of-life of Java SE 8 (Standard Edition). As of January 2019, free public updates for commercial users are no longer available. Customers accessing Niagara with the Java Applet/Web Start are impacted by this change. Those who have upgraded to full HTML5 versions for your browser front-end will not be affected. For customers who use the Java VM and Java Web Start for their legacy systems, Tridium has developed a suitable alternative, the Niagara Web Launcher. Resolution The Niagara Web Launcher application is now available. You can download Niagara Web Launcher using the following link: 64-bit systems: Web Launcher for 64 bit, 32 bit OS 32-bit (-x86) systems: Web Launcher for 64 bit, 32 bit OS Niagara Web Launcher download links are also available from the Niagara station login page. Niagara Web Launcher support is included in Niagara versions: 4.4U3 –Included in (4.4.94.14). 4.7U1 - Included in (4.7.110.32) Subsequent releases of Niagara 4 will include Niagara Web Launcher support. A patch for Niagara 3.8 U4 can be downloaded from here.  Copy web.jar module version 3.8.403.1 into the modules folder of your Niagara AX 3.8 U4 workbench or supervisor station.  This module may also be installed on JACE platforms.  To use Niagara Web Launcher, Web Start must be enabled in the Web Service of the station.

Issue How can objects of a SmartStruxure™ Lite network be made available as BACnet points to third party BACnet building management system (BMS)? Product Line EcoStruxure Building Operation Environment SmartStruxure Lite BACnet Cause The BACnet protocol is always active, as long as the network cable is connected. However, two different BACnet options can be selected: IP or Ethernet. The default option is Ethernet and this will need to be changed if BACnet over IP is required. Resolution The BACnet protocol is always active, as long as the network cable is connected. However, two different BACnet options can be selected: IP or Ethernet. The default option is Ethernet. To verify or to change which BACnet protocol is currently in use, select the SmartStruxure Lite Manager that you want to configure from the left-side Network panel. Then choose the BACnet configuration list item. Define the Network Number (if the protocol selected is BACnet IP). Note: The Network number must be defined only on the monitor Manager. It shall be different then the Parent Network where the monitor is connected. A BACnet Device is uniquely located by a network number and a MAC address. Creating two or more B/IP networks, each with a unique network number, can be useful for limiting the propagation of local broadcast messages and for providing security by confining traffic to a particular geographic or logical area. Select the desired protocol type from the drop-down list between BACnet IP and BACnet Ethernet. Then choose an optional port number (if the protocol selected is BACnet IP). Default is 47808. Select the BACnet Priority of the BACnet write action of the SmartStruxure™ Lite's network monitor. Default is 10. Note: SmartStruxure™ Lite does not support BACnet Write Priority, per se. However, in Firmware version 2.4.x and newer, it is possible to assign the write priority for all SmartStruxure™ Lite BACnet points. Default value is 10, except if you upgrade a Manager using a version 2.3.x or older, BACnet priority will be 8, but can be changed. Click the Save button to apply the configuration changes. Click hit the Save All button to make the modifications permanent and reboot the Manager for the new options to enter into effect. Change the BACnet instance number of the Manager if required. IMPORTANT Each Manager must have a unique BACnet device instance number. A Manager device instance number can be changed by selecting the top-left icon inside the left-side Network panel.

Issue The Device ID and name in a BACnet SE7000 room controller is factory set to the model number plus the MAC address. By default the MAC is set to 254 in the room controller, meaning the device does not communicate since valid MAC addresses need to be in the range 0-127. In cases where multiple BACnet networks containing SE7000 BACnet room controllers are connected to the same BACnet internetwork there could be duplicate ID's when using this schema. In these instances a T7600 Device Configurator Tool can be used to change these fields. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment • Building Operation Workstation • Building Operation Automation Server • SSL SE7000 Cause The Device ID and name in a BACnet SE7000 room controller is factory set to the model number plus the MAC address. By default the MAC is set to 254 in the room controller, meaning the device does not communicate since valid MAC addresses need to be in the range 0-127. For example when a VT7200F5000B room controller with a MAC address of 41 is connected to a network, its default Device Name will be VT7200F5x00B-41 and its default Device ID will be 72041. The device ID and name will change as soon as the MAC address is changed at the controller. The MAC address is set in the Installer configuration parameter menu using the Com Addr parameter. These fields can also be set by any BACnet management tool that can access these properties. Resolution The goal of this document is to give simple instructions on how to change the Device Instance of the VT7000 series thermostats using the T7600 Device Configurator tool and the recommended connections and wiring. 1. Converter (can be other models): Model 485OT9Lor USOTL4 from B&B Electronics. A USB-to-RS485 converter, like one used for MSTP captures, will work as well.  2. Recommended wiring for the configuration of Device Instances: The SE7000 room controllers have to be connected only to the converter (which has to be powered up) and disconnected from the network controller. The EOL resistors should remain at both ends of the trunk. 3. Setting up the software The software is supplied as a simple installer file download the software from here and run the installer. Prior to running the program for the first time setup steps 4 and 5 must to be accomplished. 4. Setting Windows Compatibility mode The T7600 Device Configurator Tool is legacy tool and therefore is only supported in a Windows 9X operating system, It has been tested and found to work in later versions of Windows by setting the compatibility mode to Windows 95 Locate the executable file T7600_MSTP_Config.exe in the C:\Program Files\Fastek\T7600 Config\ folder. Right click the file and select properties Go to the compatibility tab and change select Run this program in compatibility mode for: "Windows 95" from the drop down menu then click OK 5. Set the PC communications port Open the BACDOCM.ini located in the C:\Windows folder and enter communications port number in the line highlighted below and save the file. If a valid com port is not entered here the program will generate errors when launched and will not operate. Instructions on how to use the converter (file T7x00 MSTP Config.exe): 1. Open the configuration Tool 2. Double click on the BACDOOR icon in the icon tray on the bottom right of the PC. 3. On the window BACDOOR OEM MSTP Client status, click configure and in the configuration window set the Device instance to any number that does not conflict with any other device instance on the network.: 4. Close the BACDOOR configuration window and in the T7000 Device Configurator, click refresh device list. 6. All the devices on the trunk should appear and you can start changing the device instances one after the other. To do that: a. A- Select the first device.     B- Click Connect to device. The connection process can be long, wait for all the objects to be discovered.     C- change the instance ID using the keyboard.     D- click Apply changes. b. Select the next device and do the same. c. Repeat this action for all the discovered devices. 7. After making all the recommended changes, remove the RS-485 to 232 converter and reconnect the network.

Issue Basic Modbus RTU configuration to read a register from PM800 Power Meter. Product Line EcoStruxure Building Operation Environment Automation Server Modbus RTU PM800 Power Meter Cause Integrate power meters to a Building Operation front end for the user to view data and trend logs. Resolution Here are the steps to Configure a ModBus RTU interface in Building Operation to read the Line Voltage register from a PM800 Power Meter. (Assuming meter has already been properly wired to one of the serial ports on the AS) Create the Modbus Interface, in this case a Modbus Master Network.   Link the interface to a serial port in the AS in the Port Reference field, in this example to RTU device is wired to RS485-COMB   2. Under the interface create the RTU device. In this example the device id is 11, enter the appropriate id for the device. Once the device object is saved, the status should show 'Online' unless there is a communications issue. This is provided you have the online poll interval set. If this is disabled the device will stay offline until a Modbus register is polled and a valid response is received.    You can confirm that Building Operation is able to correctly detect the communications status of the device by disconnecting it from the commport and observing the status change to 'Offline', upon re-connection the status should once again display 'Online'   3. Under the device create a Modbus Point of type AnalogInput to get the value of the Line Voltage from the device. According to the documentation for the PM800 the register holding the line voltage is Function Code 3  and register  1124 The value of the point should now correspond to the line voltage in this case 125 volts.

Issue How do I change the Baud Rate of a field bus (either Infinet or Bacnet MSTP) if there is either an Infilink or B-link on the network? Product Line Andover Continuum, EcoStruxure Building Operation Environment Infinet BACnet Cause The Infilink and B-link must have their baud rate set manually. Resolution All Infinet or Bacnet B3 controllers autobaud on initial startup or when the fieldbus commport is changed from the parent controller's commport editor. The Infilink and B-link must have their baud rate set manually. The proper procedure to change the fieldbus baud rate is to first go to the commport editor and change the fieldbus baud rate. At this point a message is sent to all field bus controllers to change their baud rate. They will all change immediately, however the Infilink and B-link have not yet changed, so the bus will now be in a confused state and there will be offline issues. The next step is to go to the Infilink or B-link repeater and manually change the baud rate to the new setting. At this point the network should work normally, however if the procedure is not followed there may be network issues where you have some controllers that are running at different baud rates causing the network to be totally shut down. If this is the case the way to resolve the issue is to make sure the Infilink or B-link repeater is set to the desired baud rate and power down or reset those controllers on the network so that they will all synch up to the correct Baud Rate upon power up. ** Changing many controllers A method that may help when needing to change the baud rate of many controllers is to bypass the b-link Connect segment 1 of the b-link directly to the BCX comm port and change the baud rate Reconnect the B-link and verify the controllers are now online, repeat the baud change if necessary. Repeat this process for each segment You may still have some isolated controllers that need to be powered off/on. Related: BACnet bCX MSTP network loses communication when a b-Link is added or removed

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 Services for assistance. Issue Failed to read events from the event log database. Product Line TAC Vista Environment TAC Vista Workstation Cause This error is sometimes displayed upon login to the TAC Vista Workstation. It indicates there is a problem with the connection between the Vista Server and the SQL database that stores event data. Resolution Before making any further tests, make sure you have MSXML 4.0 SP3 installed and then check if it works. It can be downloaded here: https://www.microsoft.com/en-us/download/confirmation.aspx?id=15697 The first thing to check is the SQL connection. Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab In the lower right-hand corner of the tab, press the Test Connection button. If it pops up a window that says "Connection test succeeded!" then your SQL connection is okay. If it fails the connection test, check the instance name. If you are using default settings it should be: SQL Server name: PCname\TACVISTA or (local)\TACVISTA Log database name: taclogdata If these are set correctly and the connection still fails, one method for reestablishing the connection is to uninstall/reinstall the Vista software. Make sure SQL Server Agent is running. Right-click on My Computer and select Manage Navigate to Computer Management (Local) > Services and Applications > Services Find SQL Server (TACVISTA) -- assuming the default SQL instance is being used. Make sure the service status is running.  Start the service if needed. If there is no problem with the SQL connection, check the Server object's Network Master. In Vista Workstation, right-click on the Vista Server object and select Properties On the General tab, in the Network pane, check the Master: name In a one-server network, the Network Master must be set to the Server object name. Check for queued files in the $queues folder Navigate in a Windows Explorer window to the Vista Database. (If you are unsure of the location, you can verify it in the TAC Vista Server Setup Vista Database tab). Go to the $queues folder Look inside the insertevents and insertlogvalues folders. Are they empty or are they consistently growing with files? This is where data is stored temporarily before it is written to the SQL database. Having queued files is not necessarily a sign of a problem. However, if there is a connection problem, these folders will continually grow in size without older queued files being written from the folder. In the case of the error "Failed to read events from the event log database", it is possible that a queued file is causing the error prompt and that deleting it will fix it. If the data is not of dire importance, delete all the files inside both of the $queues folder. For more information see An efficient method for deleting all queued files in the $queues folder. Reconfigure the log database Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab Change SQL configuration from Typical to Custom Change the Log database name Hit Apply. It will warn you: "TAC Vista integrated SQL backup/restore function will not be available in custom configuration." Hit OK. It will then warn you: "No log database was found on SQL Server. Create and configure a log database?" Hit Yes.   At this point, if no backup features are necessary, and the error has cleared, this is a viable solution. It is not, however, recommended to maintain a site without any log backups. The next step would be to switch the Vista Server Setup SQL configuration back to Typical. Hit Apply. You will be warned: "Log database was found but needs to be reconfigured. Reconfigure log database?" Hit Yes.   After reverting to typical SQL settings, the error should clear. If it has not, it may be time for some database management. Performing Database Maintenance Follow the steps in the article Performing database maintenance with Vista 4.5.0  to set up a log and event backup and to clean up old data. Schedule a backup to occur (now or soon after) The next time you log into Vista Workstation, the error should be cleared. If the error is sporadic, it could be the event viewer has too many events If the error only occurs when logging in to Vista Workstation, and doesn't happen every time, it could be that too many events are being brought into the Event Viewer on login. All events specified in the filter for the event viewer are uploaded to the Workstation. If too many events are specified, problems occur. In Workstation, go to the root TAC Vista folder Right-click $Eventview and select properties Go to the Date and Time tab Set the Time period to Last 1 Hour(2) instead of Last 1 Week(s), which is default Check the Windows Event Log If all else fails, check the Windows Event log for more information about the error. Checking this may provide you with the answers you need, or at least give you more information to provide to Product Support if you need further assistance. Instructions available in Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes. Right-click on My Computer and select Manage Browse to Computer Management (local) > System Tools > Event Viewer > Application Look for Type Error events with Source Vista. This may help you determine the source of the error.

Issue Reload of BCX receives error "Infinity controller error: Controller has no assigned Infinet port An error was detected while attempting to set an attribute in a remote Infinity object" Product Line Andover Continuum Environment Continuum Cyberstation BCX 9640 BCX4040 Infinet controller b3 Cause Reloading of a BCX 9640 resulted in error "Infinity controller error: Controller has no assigned Infinet port.  An error was detected while attempting to set an attribute in a remote Infinity object"   Suspected that a learn on the commport was performed or infinet controllers were manually created causing no assigned comm port. Resolution As with any edit of the Continuum system, please make sure to backup the database.   Follow these steps: Send BCX to text file  Add commport to each Infinet controller entry as below Import newly edited text dump file into the BCX. Reload BCX   Example of an original dump file exported in step 1 and the new dump file after the commport is added in step 2. Original Dump File New Dump File Object : Spare   Type : InfinityInfinetCtlr   LastChange : 1/11/2011 4:01:19 PM   DeviceId : Zoo\GreenHouse   Alias : Spare   CreateTime : 8/24/2010 8:28:22 AM   CreatedBy : Root\Acc   TimeLocked : 2/15/2011 12:53:26 PM   InstanceId : 7015/7167   CntrlType : 851   Description : Spare Controller No Points   InfinetId : 1   Location : Control Cabinet   NetworkId : 11   SerialNum : 12345   VersionNum : 2.160000  EndObject   Object : Spare   Type : InfinityInfinetCtlr   LastChange : 1/11/2011 4:01:19 PM   DeviceId : Zoo\GreenHouse   Alias : Spare   CreateTime : 8/24/2010 8:28:22 AM   CreatedBy : Root\Acc   TimeLocked : 2/15/2011 12:53:26 PM   InstanceId : 7015/7167   CntrlType : 851   Description : Spare Controller No Points   InfinetId : 1   Location : Control Cabinet   NetworkId : 11   Port : comm2   SerialNum : 12345   VersionNum : 2.160000  EndObject  

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Product Line EcoStruxure Building Operation, Project Configuration Tool Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP-server from the virtual machine. Resolution To configure a port group or virtual switch to allow promiscuous mode: 1.Log into the ESXi/ESX host or vCenter Server using the vSphere Client. 2.Select the ESXi/ESX host in the inventory. 3.Click the Configuration tab. 4.In the Hardware section, click Networking. 5.Click Properties of the virtual switch for which you want to enable promiscuous mode. 6.Select the virtual switch or port group you wish to modify and click Edit. 7.Click the Security tab. 8.From the Promiscuous Mode drop  down menu, click Accept. Note: The setting on the port group overrides the virtual switch setting. For more information, see How promiscuous mode works at the virtual switch and portgroup levels (1002934).  

Issue Netcontroller is running slowly or occasionally goes offline (bCX NC2 ACX CX) Product Line Andover Continuum Environment Continuum Netcontroller, Net Controller, Infinet, MSTP, Bacnet, Xdriver, x-driver Cause There are various reasons why the operation of one or more Netcontrollers and or attached controllers is slow and/or goes offline occasionally.  This guide is primarily to help collate the right information which may identify the issues.  If the reason cannot be identify then this information can be provided to support for further analysis. Resolution General troubleshooting techniques should be used. Define the exact problem. What exactly is slow? eg. Sending to the controller or its connected devices, opening or refreshing graphics, opening or refreshing points, updating Xdriver points, saving programs, creating new points. Is the controller slow from all cyberstations? Is the controller always slow? If not then try to find what makes it go slow, it is time related? Can certain steps be taken to cause the slowness or offline to happen? Get a screen capture of any errors. Gather site information. Continuum version, Continuum hotfixes and service packs applied, number of Cyberstation. Cyberstation operating system, details of Ethernet network and subnets used, with BBMD information of Bacnet sites (Asbuilt or a spreadsheet with IPs, etc.) Continuum Analyzer report, site controller map or spreadsheet or text dump Check the PCs running Cyberstation, do they meet the system specifications? Gather controller information What is the Scan rate? Is the controller time sync. correct? How many objects are on the controller, how many programs are running? What is the firmware version of the netcontroller and b3 or i2 controllers? Ethernet connection - Is the controller on the same subnet as the Cyberstations? A wireshark trace may help to establish the quantity of traffic on the Ethernet (See Using WireShark to analyze communications on an Ethernet network) Comms Ports - XDriver being used? What is on the comms ports? Xdriver (how much communications, points etc) Comms Ports - Bacnet MSTP - How many b3 controllers? How much extended logging? How many alarms being sent? How many 3rd party devices? Look at bacnet settings, how many values are being sent across the network? Check COV settings. Try removing the MSTP cable from the bCX (there could be an issue with an MSTP device causing the bCX to go offline/go slow) Comms Port - Infinet - How many infinet controllers? How much extended logging? How many alarms being sent? Look at infinet settings, how many values are being sent across the network? Check port reconfigs and errors. Try removing the infinet cable from the NetController (there could be an issue with an infinet device causing the NetController to go offline/go slow) Comms Port - other. Again try removing the comms cable from the NetController (there could be an issue with a device on this network causing the NetController to go offline/go slow) Run the Controller error log tool to gather the controller errors See Gather Continuum Controller error logs if requested by Product Support for troubleshooting If the controller goes offline, run the alarm listview.  Does it line up with the Controller error log? Check the CPU LED flash rate on all connected devices (i1, i2, b3 etc) as Can't bring bCX online in Continuum but do get a response to pinging its IP address, also the RD and TD LEDs should be checked for anything unusual This guide is primarily to help the on site engineer by helping them to assess the site. If there is still a need to contact support, please review and record as many items above as possible and send them to the case owner.  Further tests can be carried out including an ACCtrace to determine if the restriction could be at the Cyberstation, See How to capture Continuum Cyberstation activity using ACCTrace NOTE: Ensure all Cyberstations, Controllers and other laptops used for logging are in time synchronization before recording any logs. If it is believed there is an issue with the Infinet or MSTP network see Infinet and mstp bus troubleshooting If it is believed the problem is with extended logging see Extended Logging gaps, performance and load balancing It is possible that something connected to the controller causes the controller to go offline, try disconnecting all other cables and connections to the controller and then re-testing Where a controller is offline when connected directly to a PC/Laptop, try resetting the IP address, otherwise the controller will probably need replacing. NOTE Disconnecting all networks from the NetController is often a good starting point (reconnected IP/Ethernet cable)  

Issue If the Xenta Server IP address is unknown or lost, how can the user retrieve or reset the IP address? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Once the Xenta Server IP address is lost, the user has to use a serial connection cable to connect the Xenta Server to the HyperTerminal in order to retrieve the IP address. The serial cable is a RS-232 to RJ10 cable which can be purchase from Schneider Electric order entry (Part number: 00730920). For some reason, if the cable need to be home made, please follow the steps below to connect correct pins. Note: some third party IP search/scan software can be used to search all IP addresses in a range. User can also use this type of software to retrieve Xenta Server’s IP addresses. Resolution Xenta Server serial cable guide: Connect RJ10 pin 1 to RS232 pin 2. Connect RJ10 pin 2 to RS232 pin 3. Connect RJ10 pin 4 to RS232 pin 5. Connect RS232 pin 1, 6, 4 together. Refer to IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for how to set up HyperTerminal in order to retrieve/setup Xenta Server IP address.

Issue Access Expert On-Premise setup needs procedures and tools to backup and restore the database Product Line Access Expert Environment Access Expert Premise Software V3 MongoDB Cause The procedures for backing up and restoring the MongoDB is documented online at the link below. https://docs.mongodb.com/manual/tutorial/backup-and-restore-tools/ However, these instructions do not outline how to use the commands (mongodump and mongorestore) within the Windows OS environment using specific examples. Resolution The following procedures are designed to fill in the gap for Access Expert administrators who need to do manual MongoDB Backup and Restore. These procedures assume that Access Expert V3 has been installed and is functioning normally. You will need 2 separate Command Prompts, run as Administrator, open for these procedures. Mongo DOS Shell to attach to and run commands within MongoDB environment Standard DOS Shell to run the Mongo backup and restore commands MongoDB Backup Ensure MongoDB service is running (Start> Run> services.msc) Open a Command Prompt as Administrator (referred to as the Mongo DOS Shell) Type mongo(command) Type show dbs (command) - shown above, to give a list of the dbs available) If the MongoDB service is "Running," but the client cannot connect when typing mongo, it's probably because the path to the mongo bin folder hasn't been added to the PC's environment. To Add a local path locations variable to a PC environment https://docs.microsoft.com/en-us/previous-versions/office/developer/sharepoint-2010/ee537574(v%3Doffice.14) Ex. C:\Program Files\MongoDB\Server\3.6\bin (This will vary based on the version of Mongo) Open another Command Prompt as Administrator (Standard DOS Shell) Use the CD command to navigate to where you would like the backup files to be created Ex. C:\Data mongodump (command) The mongodump command creates the dump folder with admin, Keep, Signalr subfolders MongoDB Restore In the (Mongo DOS Shell) Prompt show dbs (command) use Keep (command) (Case sensitive) db.dropDatabase() (command) Use the Command Prompt as Administrator (Standard DOS Shell) mongorestore (command) The window should indicate "Finished Restoring Keep.Events," "done" and RESTORE COMPLETE If there are “E11000 duplicate key error collection” Keep.Events errors, it’s because the collection events are already in the folder and need to be deleted first.   Steps to correct the E11000 duplicate issue: (Stop the service, delete and recreate the DB folder, restart service) Right-click on the MongoDB service and Stop (you can’t delete files while the service is running) Delete C:\Data\db folder (not the Data, only DB) MANUALLY CREATE THE DB FOLDER - Right Click > New Folder and name it DB Restart the MongoDB service - this creates the necessary files in the DB folder Once these steps have been done, rerun the mongorestore command mongorestore (command) Verify that users can log into Access Expert with this database

Issue What features are included in Building Operation evaluation (demo) licenses? Product Line EcoStruxure Building Operation Environment Building Operation evaluation license Cause The features included in evaluation licenses are not shown in the documentation. Resolution License Administrator (Software Evaluation License) After adding the evaluation license in License Administrator,   Click on the "Diagnostics" Tab. Click on "Refresh the list". Local licenses list generates. Example of generated list: Local licenses: -------------------------------------------------------------------- Trust Flags: FULLY TRUSTED Fulfillment Type: TRIAL Status: ENABLED Fulfillment ID: LOCAL_TRIAL_FID_498 Activation ID: SC_57LRIHRFBOXC28SGYTPKCH98WIRKMWE Product ID: NAME=EcoStruxure Building Operation Demo License;VERSION=5.0 Suite ID: NONE Expiration date: 01-Feb-2024 Concurrent: 0 Concurrent overdraft: 0 Hybrid: 0 Hybrid overdraft: 0 Activatable: 1 Activatable overdraft: 0 Repairs: 0 Feature line(s): server.mssql (Version 5.0) client.zoning (Version 5.0) client.dashboard (Version 5.0) server.ec.auth.saml (Version 5.0) server.ws.generic.consume (Version 5.0) server.dig.signed.docs (Version 5.0) server.alarms.snmp (Version 5.0) server.ec.es (Version 5.0) server.device.es (Version 5.0) server.ws.ews.history (Version 5.0) Sigma.Server (Version 4) server.mqtt.rw (Version 5.0) graphdb.base (Version 1.0) server.esignature (Version 5.0) server.enterprise.base (Version 5.0) server.ws.ews.consume (Version 5.0) client.cad.import.tool (Version 5.0) smartdriver.license (Version 5.0) server.timescale (Version 5.0) client.script (Version 5.0) server.es.as (Version 5.0) client.graphiceditor (Version 5.0) server.device.as (Version 5.0) server.ws.ews.serve (Version 5.0) server.es.auth.saml (Version 5.0) server.enterprise.central (Version 5.0) client.functionblock.view (Version 5.0) client.station (Version 5.0)   Refer to the Webhelp EcoStruxure Building Operation Software Feature License String Description topic for an explanation of the license feature strings. Device Administrator (Embedded Evaluation License) After adding the evaluation license to the Device Administrator (see the article How to activate a demo license on an Automation Server at EBO 2022) follow the steps to view the available features: Click on the Entitlements. Click on Product Licenses. - The individual features are then shown as column headings The best way to see all the features available is to right-click on the license name under Product Name and choose Add/Remove columns.   A Select columns popup is then shown, and the available features are much easier to read.  

Issue Site experiencing comm issues on the Infinet or MSTP bus. Controller error logs show many 1465 (Cyclical Redundancy Check) errors. Product Line Andover Continuum Environment Infinet MSTP b3 i2 Controller error log Cause CRC errors are check sum errors. Before a packet is sent, the sending controller calculates a checksum based on the packets contents. This checksum is then appended to the packet. When the packet is delivered, the receiving controller calculates it's own checksum based on the packets contents. If the check sums do not equal, this indicates that somewhere in the delivery process the packet has been altered, usually due to bad cable or connections, controller grounding, or a bad controller transceiver. For additional information on troubleshooting the infinet or mstp bus, see Infinet and MSTP bus troubleshooting. Resolution CRC errors usually indicate poor signal integrity on the physical bus. Infiltration of "noise" on the comm cable due to the presence of high voltage conductors, radio transmissions, etc. In some cases a failed transceiver may be involved but this is generally not the case. Poor controller grounding can also contribute to this issue. Generally CRC errors call for using a scope to assess the signal integrity on a bus.

Issue Procedures and processes to secure I/A Series G3 (AX) Systems Environment I/A Series Niagara G3 (AX) Systems Cause Users accessing system without permission Potential damage done by malicious entry to the system Resolution The attached document describes how to implement security best practices in an I/A Series Niagara G3 system. While it is impossible to make any system completely impenetrable, there are many ways to build up a system that is more resistant to attacks. In particular, this document describes how you can help make an I/A Series Niagara G3 system more secure by carefully configuring and using.  Passwords Accounts and Permissions Authentication TLS and Certificate Management JACE-8000 Settings Additional Settings Please note that while all of these steps should be taken to protect your I/A Series Niagara G3 system, they do not constitute a magic formula.  Many factors affecting security and vulnerabilities in one area can affect security in another; it doesn't mean much to configure a system expertly if your JACE is left physically unsecured where anyone can access it.  Note: Schneider Electric strongly recommends upgrading to the latest I/A Series G3 version 3.8 maintenance build that implements numerous security updates.  Before updating any system, make sure to review the build included documentation to understand the behavioral impacts of the security enhancements. Download the Niagara AX Hardening Guide for more details.

Issue When using Advanced Display and logging in to Webstation, it startups in kiosk mode with limited functionality. Example:   Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display Cause When running Webstation in Advanced Display it is by default started in kiosk mode Resolution Open SmartX HMI Kiosk in Advanced Display In "Webstation setup" delete the part ?kiosk# Example: https://192.168.42.116/?kiosk#  Webstation be started in kiosk mode https://192.168.42.116/  Webstation will start normally

Issue Automation / Enterprise Server configuration very slow Attempting to make any configuration changes in the AS such as creating a new point/value or modifying existing objects is extremely slow. Note: This applies to the ES as well although less of a problem since the ES has better resources than the AS. CPU usage as seen in the Status Information of the server is very high. (above 80%) Question marks are shown on many objects in the application folder of third party BACnet devices that have been uploaded to the AS Enterprise Server takes a long time to startup (15 minutes) before allowing users to log on with Workstation.  Deleting the BACnet Interface allows log on with 2 - 3 minutes on a restart. Product Line EcoStruxure Building Operation Environment Automation Server Enterprise Server BACnet Cause Uploaded BACnet devices contain unresolved references to notification class object(s) Resolution Ask for SE.SBO.ES-AS-1.5.0.1501-Hotfix. (SE.SBO.WS-1.4.1.16001-Hotfix for 1.4.1, there is no hot fix for versions before 1.4.1) After applying the hot fix the server should become responsive. The unresolved references can typically be cleaned up by creating a BACnet Notification object in the application folder of the third party BACnet device proxy that reside in SBO and manually setting the Instance ID to 0 (zero) NOTE: Cases have been seen where multiple notification class objects must be created using instance IDs 0,1,2,3,4 in order to clean up all the unresolved references. A few minutes after the notification class object with the proper instance ID is created the question marks should disappear from the icons and created notification class object will show up in the intrinsic alarm property as seen below.   If creating the notification class objects with the above instance IDs does not resolve all the references a backup of the server can be provided to PSS, a PSS/R&D engineer can look directly at the database to determine the proper instance IDs the unresolved references are looking for.

Issue In the Workstation, old alarms are showing in the alarm pane. Recheck does not remove, and the only option left is to "Hide". The same goes for disabled alarms. Is there a way to erase or scrub these 8-month-old alarms? When checking disabled alarms, there are a lot of alarms that have been disabled, but no one has disabled any alarms. When right-clicking on the alarms to get the context menu, most of the alternatives are greyed out. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation version 1.2 or higher Cause First, check the disabled cause to see what disabled the alarms. If it is "user," a person has disabled them. If it is "system," the system has automatically disabled them because the alarm object has lost its monitored value. Resolution Alarms in the alarm view "Recheck" command does not help then try the "Alarms Integrity Check" commend, please see LL Removing invalid alarms  Check the source path on the alarms, do they point to actual alarm objects? If the alarm objects that triggered the alarm in the first place still exist, you should be able to disable them then just enable them again. If you cannot, use the disable button in the alarm viewer then you can use the Disable alarm property in the editor (assuming version 1.2 or higher). If you can’t disable them then try to trigger them back and forth once. If the alarm objects don’t exist anymore, create alarms that would fit the source path, then just trigger those. After that, it should be safe to delete the alarm objects again. Basically, the alarms you create will take ownership of the old alarms in the viewer. Also, add the column Type in the alarm viewer and see what type they are. It would be helpful to know what the Source path and System alarm id (if there is one) are. Remove old Alarms in Alarm Pane Disabled alarms If the monitored values are not used anymore delete the alarm object that monitors the value If this is not enough make sure the path exists in the system, it can be needed to recreate the alarm in the correct path meaning the folder structure needs to be recreated. There is also the choice of right-clicking on the Alarm which gives the following menu: From this menu, one can Disable the alarm or alternatively, Hide the alarm. To view Hidden or Disabled alarms once they are not shown in the Alarms window, select one of the two Icons from the Alarms window icons as shown below:

Issue How to set up a Mantrap Product Line TAC INET Environment I/NET Access Control Site Interlocked Doors Person Trap Anti-Passback (APB) Cause What is a mantrap? A mantrap is a security device that monitors and controls two or more interlocking doors to a small room that separates a non-secured area from a secured area. These interlocking doors allow only one door to be open at any time. What are interlocking doors? “Interlocking doors” is a security term used to describe how two or more doors are interfaced with each other and locked. Doors that are interlocked cannot be opened at the same time. Either door can be unlocked and opened as long as the other door is locked and closed and no other alarm condition exists. What types of locations require a mantrap? Mantraps are used at high-value or critical security areas where only authorized persons are allowed to enter. Typical areas include sensitive data processing areas, cash handling areas, critical research labs, security control rooms, and automated airline passenger entry portals. Why would my company consider a mantrap? Typically, security personnel are posted in high-security locations to control access into the area. An automatic mantrap used in this same location would control the access to the area, allowing security personnel resources to be available for other tasks. What is the difference between a mantrap and an interlocking door control system? Regarding controlling two doors within a vestibule, “mantrap” and “interlocking door controller” can be used interchangeably. Once the number of doors controlled by a single controller exceeds two, then the term interlocking door controller should be used. Resolution I/NET has three ways to do a mantrap: Event sequences and calculations -- limit to 5-7 SCUs per 7798C due to system loading Use a "standalone" third-party device that is wired to the door and is not attached to I/NET at all Use the interlock wiring diagram that uses relay logic to function. This is also part of the I/NET System. I/NET Seven allows configuring a door to have both an entry and an exit reader and uses the selection of Anti-pass back/Anti-tailgate to set up Zones or areas with stricter control over access. However, even with the Anti-pass back option set to Hard, which denies access to successive reads at the same reader, it does not prevent multiple persons from entering and exiting together, and it does not provide real-time accounting for the number of people in a Zone. Besides having a guard at the door, the usual method of implementing Zones does not prevent violations.   The example below presents some thoughts about improving the Zone's security in an I/NET Seven system. There needs to be a way to restrict the number of people gaining access to the door. There needs to be a way to keep up with how many people are in the Zone. One method to accomplish the first goal is to use a two-door egress system, as is often used in jails and similar security setups. For a medium security setup where the intent is not to prevent people from leaving, only one door needs a card reader. Such a design is illustrated below: Notes: Electric strike normally energized. Low walls or fences. The area should be small enough to limit how many people or things are in it at one time. Gate with normally de-energized bolt. The gate could swing both ways, so one would only have to push it to open it. It should have a spring to close it. The door “a” would have both an Entry and Exit reader, so an Anti-pass back/Anti-tailgate can be implemented. The strike on the door “a” would normally be energized and opened by a valid reader transaction.   The bolt on the gate would be normally de-energized, allowing the gate to open freely. When the strike on the door “a” is de-energized, the bolt on the gate would be energized, preventing the gate from opening. This is designed to allow only one person to simultaneously move into or out of the Zone.   An added level of security would be accomplished by mounting IR emitter/receiver pairs along the low wall or fence at regular intervals. A person would interrupt the light at a limited number of receivers, so if more than expected are interrupted, it would violate one person at a time, and necessary action could be taken.   If material needed to be moved through the door, the gated area could be made large enough to allow for a dolly or whatever might be needed. A different access level would be provided to those who are moving material, thus preventing the alarm for too many people going through the door.   This approach would restrict movement into and out of the Zone, and the example given in the AIC note could be implemented to allow real-time monitoring of occupancy levels in the Zone.   Design thoughts:   To calculate whether more than one person is in the gated area, sum the number of receivers that are detecting and compare it to a minimum, e.g., four of six must be detecting if only one person is in the area. If material is in the gated area, generate an alarm if an authorized card is not read. Use the alarm delay for the point to give an individual time to make a card read before sounding the alarm. The AIC scheme described in the AIC note would have to be duplicated for the material mover individuals to change the calculation of a person in the gated area. For material movers, the detection would be (sum of detectors < minimum), whereas for regular individuals, the detection would be (sum of detectors > minimum). Remember, the SLI connected to this door can have only 64 AIC’s and this door now has used 2 of them. Use an inter-card delay long enough to let the person exit the gated area before another card can be read. For personnel safety, there must be a way to de-energize the strike. One method would be to mount an emergency exit button located far enough away from the door so a single person could not reach it and a second emergency exit button on the outside of the Zone so someone could keep the strike de-energized until everyone is evacuated. Most codes probably require that all strikes be de-energized in case of smoke or similar emergency to provide another fail-safe.   Here is a pdf document which explains the setup using an SCU Click here to download third-party ManTrap information.

Issue Tips for Configuring HID OSDP Reader LED Colors Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert OSDP Reader Cause Additional tips for configuring OSDP Reader LED Colors Resolution The Configuring LED Colors section of AN-254 Configuring OSDP Readers in Security Expert  details the basic steps for LED configuration. This article details some additional areas of the HID reader setup and Security Expert configuration that may be useful when configuring the LED colors.   Note: The steps in this article are specific to an HID Signo RP10 Reader BLE and may not apply to other HID reader models or other brands of OSDP readers.   Upgrade the Reader firmware to the latest version. Earlier versions of the reader firmware would not correctly allow LED control. The Bluetooth option allows the configuration of the reader using the HID Reader Manager App. For detailed information see HID Reader Manager App Information Note: To use the HID Reader Manager App to configure a reader, the Security Technician or Security Installer needs to create and register an account with HID. The Reader Manager Administrator for your organization or company needs to enroll this new account using the Reader Manager Service and issue an invitation code and key authorization for this and other readers. The Security Technician can then verify the key authorization has been received in the HID Reader Manager app. Detailed instructions for all of this are included in the HID Reader Manager App Information URL listed above.   HID Reader Manager App Firmware snapshots       In the HID Reader Manager App, change the Reader Options for LED color to "Host Controlled" in 2 places. The reader must be controlled by the Security Expert controller. Credential Reader AV LED Idle Color Ensure that the firmware for the following hardware is upgraded to these versions or greater in order for LED Color Output to work. Security Expert 4.3.308.46 SP-C 2.08.1234 MRDM2 1.2.590 In Security Expert the Outputs to control the LEDs need to be manually created. Programming> Outputs> Add A pop-up asking to Invert Output will display, select 'No' when prompted Output 3 (GreenLED Port 1) Output 4 (Red LED Port 1) Output 6 (Green LED Port 2) Output 7 (Red LED Port 2)   Name the Outputs whatever is appropriate Example:  GreenLEDPortON RedLEDPortOff LED Colors The default LEDs are Blue when Idle and Green when active. As an example, the LED colors will be changed to Red when Idle and Green when Active. Color Options:   Set the colors for both Red(idle) and Green(active) in the Security Expert Output Command Window for the newly created outputs RedLEDPortOff   GreenLEDPortOn Update the modules and wait for about 15 seconds before activating the output to test. Just saving the updated command setting doesn't work, the module must be updated.   Activate the GreenLEDPort1 - the color should change to what the output was set to in the command. In this case, green. Deactivate goes back to Off (idle) Red. GreenLEDPort1 = On State RedLEDPort1 = Off State   Note: The Off state if left at the default of Blue can't be used with the On state of custom(non-default). Both Outputs must be specified in the command window for the colors to work together.   Example: If the OFF state is left at the default of blue and the color of the ON state is set in the command window and Activated, the LED color will change to what it is set to(green), but when deactivating the Off(idle) output it will not turn blue.