Issue Gets error message "GCM Not responding" when he attempts to make a connection to a device on the ASD bus under the UNC. Product Line TAC IA Series Environment I/A Series R2 UNC I/A Series R2 TunnelAX jar file, version 2.301.534a or later I/A Series ibsASD jar file, version 2.301.534a or later I/A Series G3 Serial Tunnel 2.0 Client Cause Misconfiguration of tunnel name Resolution Before attempting to configure the AX Tunneling, verify that the correct versions of the R2tunnelAX and ibsAsd jar files have been installed as documented in How to install an I/A Series R2 JAR File. Tunnel Name in AX Tunnel Client must match the Tunnel Instance name in the ASD Service. When you add the AxSerialTunnel to the ibsAsdService, the identifier is automatically assigned based on the port defined in the communications configuration of the IbsAsdService itself.  This name is displayed under the Status tab of the AxSerialTunnel: Figure-1 When configuring the "Niagara AX Serial Tunnel 2.0", the following window is displayed. Figure-2 The tunnel name (See Figure 2) entered in this window must match the port identifier shown in the AxSerial Tunnel definition (See Figure 1).  If these identifiers do not match, the Ax Serial Tunnel Client will not be able to connect to the tunnel in the I/A Series R2 station. NOTE: When installing the I/A Series G3 Serial Tunnel 2.0 Client, no control panel applet is created as with the earlier version of the I/A Series R2 Serial Tunnel Client.   To configure the I/A Series G3 Serial Tunnel 2.0 Client,  run the program C:\niagara\VserAx\vseraxConfig.exe.  If you need to frequently reconfigure this client, you can create a Window Start Menu shortcut or Desktop shortcut pointing to this file.

  Issue When adding an onboard downstream device (Ex. LP1502) with 4 Engage wireless gateways installed the onboard downstream device shows as 'Unknown' and will not come online Product Line EcoStruxure Access Expert Environment Access Expert v3 Hosted Cause If the onboard downstream controller(Ex. LP1502 - onboard) was not being used prior to commissioning and addressing the Engage Gateways then it is likely there is an address conflict. Resolution Check all the downstream device addresses by going to Hardware Provisioning> Downstreams If one of the Engage addresses is 0 then it is likely conflicting with the onboard downstream controller's address 0. Go back through commissioning the Engage gateway devices and re-address them. Before After Once the gateway devices have been re-addressed not using address '0' they should all come online as well as the onboard downstream controller and it should not show as 'Unknown'.

Issue What camera conditions does Continuum support being shown as a Continuum alarm? Product Line Andover Continuum, Pelco Environment Continuum v2.0 Pelco Video Server Digital Sentry Endura Cause Available documentation is a bit bare on specifically what camera conditions can be monitored / setup to be displayed as alarms in Continuum. Resolution According to the latest Video Compatibility Matrix, only the following video alarms are supported: Video server online/offline Camera video loss (cable connection loss only, not covering of camera lens) Motion detection (per camera) Note: Video loss and motion alarm functionality are not supported on DVX and DVXi Video Servers.

Issue Adding a device through the System Plug-in results in missing SNVTs, SCPTs, or Module/Functional Block Names in the Vista database. Environment Vista 5.x.x Cause The XIF file is either incorrect or parsed improperly. Resolution Right click on the device and select properties. Click on the XIF file tab. View the XIF file name (this can be found in the $thisfil directory of the Vista database) and either browse in a renamed copy of the existing file or an independent copy of the file by clicking the ... button. Click Ok Log out of Workstation Log into Workstation to see the changes. Note: For a change to be detected the filename or location of the file must be different.

Issue Shadow Schedule in the Automation Server is not syncing to the Lead Schedule in the Enterprise Server Shadow Schedule in the ES syncs successfully to Lead Schedule in the AS Lead and Shadow Schedules in different AS are syncing successfully Product Line EcoStruxure Building Operation Environment SmartStruxure 1.x Cause Traffic is blocked by Windows Firewall.  Resolution Disable Windows Firewall. Disabling the firewall may not be possible due to security concerns, Exceptions can be added to Windows Firewall for ports that are used by SmartStruxure. Refer to Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port for details. If this doesn't work, please refer to Shadow Schedule in AS isn't synchronized with the Lead Schedule in ES.

Issue "Software file not found: 7797**.bin" when downloading bin on a 7797 ICI Product Line TAC INET Environment I/NET site with 7797 Cause Error Message in software file not found: 7797**.bin when downloading bin on the 7797 ICI Resolution The reason the Software Restore command is looking for a 7797**.bin file during the download is due to one of two reasons. The ICI has not been configured in the Edit->Controller->Configuration screen to specify the ICI type. Example: 12 for BacNet, 15 for Modbus. Copy corresponding bin file under /Support/Bin/ in the installation CD of I/NET to the Data directory. The download should be OK now.

Issue When evaluating Inet Transition sites, a common error seen when uploading I/NET controllers under the  Inet Interface is an upload failure.  The Background Status and trace log will contain a changeset error as shown below: UploadDevice failed to process changeset on link: 93 station: 10, type index: 17 cannot continue upload Product Line EcoStruxure Building Operation, TAC INET Environment Ecostruxure Building Operation Inet Interface  Cause Understanding the ChangeSet Indices used by the developers will help pinpoint where the issue is originating from.  The message typically isolates the Link and Station but does not identify where within this controller the problem may lie.  Resolution The current list of ChangeSet Indices are listed below and attached Changeset_index.txt Index Affected 9 DCU passwords, States, Eng units, Conversion Coeff., Controls, Holidays, DDC history, Override access, Sunrise/Sunset 11 Points 15 Action message, DCU DDC, Event sequences 17 Calculation 19 Event extension 21 Extension general (can be one of: Runtime, Consumption, or Alarm inhibit - depends on DCU type) 23 ATS 25 ATC 27 Extension application (can be one of: Demand, ORB, ORBEM, UC, LZ, LC, Elevator - depends on DCU type) 29 Trend 31 Lookup table (raw data) 33 Demand load (raw data) 35 MCU 37 MR DDC 39 AIC sequence (raw data) 43 LCD page, Istat param, IAS (raw data) 45 Access control (raw data) Note: "raw data" indicates user cannot manipulate in EBO but it is uploaded and save in raw form to allow for a download/restore Working with the example shown in the Issue, the message indicates a changeset value of Index: 17.  Using the attached list, Index 17 indicates that the issue is within the Calculation Editor. Using the SAV file from the site and working offline within I/NET open this SAV file and check each of the editors, in this case, calculations. In most cases, it will either be an invalid character or invalid point address - which will be shown as 'blank' as seen below: Correcting this and updating the SAV file to the controller (Station Restore) will typically correct this issue. If the same error persists then please provide an Export of the Inet Interface and the SAV files of the controllers having this problem through your local support channel.   

Issue Adding a Xenta Programmable Controller to an NL220 System Product Line TAC Vista Environment NL220 Cause Commissioning a Xenta programmable controller in NL220 needs to follow a certain procedure in order to prevent various issues from occurring, such as controllers not showing online in Vista Workstation, etc. Resolution Adding a Xenta Programmable Controller to an NL220 LNS system. Preparation: Create the Menta File Install the Controller Adding the Device to the LNS database NL220:Create a Template for the device type. See NL220 Useful Functions and Shortcuts on how to create a template. NL220:Add a node using the correct device Template System plug-in: Assign Neuron ID and Menta file Add and match I/Os if applicable Bring the Device to the Vista Database System plug-in: Update TAC Network Drag controller to an existing group if desired, and delete the now empty group  Create group bindings Assign Neuron ID for the I/O modules Update the TAC Network again Check TAC Network Update Vista Database Check that your network is attached and OnNet  Download Application and Parameters Bring Vista Db online NL220: Commission and download the device (ignore I/O modules.) System plug-in: Commence Communication (if needed) NOTE:  It is very important that you Download Application and Parameters in the Vista system plug in THEN Commission the device in NL220. 

Issue Receiving error “Could not connect to server. Cause: System.Runtime.Remoting.RemotingException:Requested Service not found opening graphics in webclient Environment Windows XP Windows Server 2003 Windows Server 2008 Cause This issue usually happens after uninstalling and reinstalling IIS. The webclient and newgraphicsfiles virtual directories may have been added, but DNWACServerFactory was not. Since the DNWACServerFactory virtual folder is missing, it keeps trying to create itself, but it can't and it generates the error. Resolution Get all users out of webclient In IIS (Internet Information Services Manager) Right click on Default Web Site, select New> Virtual Directory Click Next In the Alias field type: DNWACServerFactory, Click Next Click Browse and navigate to C:\Progam Files\ Continuum\DNWACServerFactory Click Next For access permissions, keep read, run scripts and select browse Click Next, Click Finish Restart webclient and test out graphics

Issue When logging into TAC Vista Webstation or ScreenMate, error message: Error Information The following errors have occurred. Please correct these errors and/or contact the system administrator. The Vista.Server.WebApps.Access license is missing. This license is required for the Vista Server to allow connections to the Web Applications. Product Line TAC Vista Environment TAC Vista 5.1 Vista Webstation 5.1 Vista ScreenMate 5.1 Vista Standalone package license Cause If the customer purchased the Vista Standalone license package, the Server-to-Server network and ability to be used with Webstation and ScreenMate is disabled. Two licenses are required in order to use Webstation or ScreenMate. Vista Server web function ability license: This license is required for Vista Server to communicate with Vista Webstation or ScreenMate. This license comes with the Vista Server license or some Vista package licenses, and cannot be purchased individually. It should look like something below in your license file: INCREMENT Vista.Server.WebApps.Access  taclic 5.1   Actual Webstation or ScreenMate seats. This license is required for users to log into Webstation or ScreenMate. This license comes with the Vista Enterprise package license or being purchased separately. It should look like something below in your license file: INCREMENT Vista.Webstation taclic 5.1, or INCREMENT Vista.ScreenMate taclic 5.1 Vista Standalone license package does not include the first type of license; therefore, when user log into the Webstation or ScreenMate, license is missing error message is displayed. Resolution Customer has two options to solve this issue: Purchase a full version of  Vista 5.1 Server license. Part number: 000882501 Part name: VISTA 5.1 SERVER   Purchase another package license which includes the full version of Vista Server license and replace it with the Vista standalone license. The standalone license can be rehost to another computer which does not need the web function for future usage. Read additional package license information in the “Software License Packages” document.

Issue Lost the password to login to the different media I/NET, SQL, SAV Environment I/NET site Cause Lost Password Resolution I/NET login: Please send the database with version number and SQL version used to ProductSupport.BMS@schneider-electric.com. SQL login: Please see Loading I/NET on a PC that has full SQL and the Password is not known and Changing the MSDE SQL Server Sys Admin account password is not supported by the I/NET Seven DbCreate Utility. DCU login: Please see Recover an I/NET Controller's DCU Password.

Issue Investigating event with EBO Webstation and need to collect logs for Product Support to assist. Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause Product Support requests logs to investigate an event in EBO Webstation Resolution Opening Developer Tools in Google Chrome or Microsoft Edge Open browser Hit F12 or Ctrl+Shift+I to toggle open and close the Developer Tools section Note: In Microsoft Edge, one can use F12 if you check to Remember my decision and click the Open DevTools button                                                                                                      Collect Information from Developer Tools - Console Open the browser's Developer Tools Select the Console tab. NOTE: Exceptions from the server or client-side issues will be shown in the console. Select inside the console tab, hit Ctrl-A to Select All, hit CTRL-C to Copy, and in any text editor, hit CTRL-V to Paste. Save the file. NOTE: In this example, there are no exceptions to be saved.  Collecting Network Logs The communication between the server and client can be logged. This can provide essential information about the information sent from the client to the server and how the information is parsed by the client. It can be useful to: take a network log while reproducing the issue clear the application cache then take a new network log.   Preparing and saving the network log Click the Network tab. Make sure network traffic is being recorded (toggled with ctrl+E) Clear the network log by clicking the Clear symbol in the upper left Open the page or object representing the issue Carry out steps to reproduce the issue Stop the recording (toggled with ctrl+E) Click Export HAR... to save the HAR file  Clearing the application cache and type information Click the Application tab Click the Application - Storage section Ensure ALL boxes are checked Click Clear site data.  NOTE: This will log you out and you need to log back in 

Issue How can the Niagara G3 ENC platform be accessed if the user name and password have been forgotten? Environment Niagara G3 ENC Cause Forgot username and password for the Niagara G3 ENC. Resolution To connect via the serial port of the ENC you will need a UNCC-405, an Ethernet cable 7' or less, and Hyperterminal (or another terminal program). In the upper right corner of the ENC-520 is a block of four pins marked J4 Mode. Using one of the bias jumpers from the board, temporarily short the front two pins. Using the UNCC-405 and short Ethernet cable connect the laptop to serial port one of the ENC. Open HyperTerminal and configure a connection as 57600, 8, none, 1, no flow control. Reboot the ENC. When this appears: "Press ESC to restore factory default username and password...", go ahead and press the ESC key. Enter "y" when prompted to force the platform user name and password back to "tac" and "niagara". After using WorkBench to verify the user and password have been changed, remove the jumper and disconnect the serial connection.

Issue When specifying the configuration of the SE7300 you can choose between "50" and "55" in step 5 of the part number. Product Line EcoStruxure Building Expert, Field Devices Environment SE7300 Cause Different options of configuration when defining the part no for the SE7300 Resolution The difference is that the "50" option is PIR Ready, but PIR cover of unit is not included. Option "55" is with the PIR cover already mounted upon delivery. 

Issue Can you disable the wireless in StruxureWare Lite Environment StruxureWare Lite site with wireless devices Cause Does the MPM emit radio waves if the Enocean & Zigbee is not configured (enabled) in the controller set up pages Resolution ZigBee is a wireless communication protocol that uses a mesh network between devices. It operates on the 2.4GHz band and is divided in 16 channels. The Zigbee Pro protocol has error-correction and can dynamically add or remove nodes to the mesh without interrupting the communication. A MPM set as a ZigBee Coordinator creates a network (more or less like a wi-fi router) and a MPM set as a ZigBee router will join an existing network. As a rule of thumb the practical distances are around 150ft in building and 300ft open air but heavily depends on the obstacles around. Disabling ZigBee through the Communication Configuration (C2G1) object will prevent data exchange between this MPM and the rest of the network. It will not disable the radio module, which could still be connected to a network. EnOcean is a 'broadcast' type of protocol that operates on 3 frequency bands. North America is currently using 315MHz and will soon be replaced by 902MHz. Europe operates on 868MHz. As a rule of thumb, the practical distances are about 50ft in building but heavily depends on the obstacles around. There is no way to disable the EnOcean module, however if no device is added or no reference to EnOcean commands are used in the scripts, the module will not transmit or receive packets. More info on wireless deployments can be found here: https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp

Issue Feature overview and tested platforms, operating systems, databases, and web browsers for AX/G3 version 3.8. Product Line TAC IA Series Environment Niagara AX / G3 3.8 Cause Field inquiries Resolution View the PDF files below.  They were obtained from Niagara-Central.com.  Feature Overview Test Summary Windows 8.1 is also supported (not listed in the Test Summary).

Issue PSI / XPSI Revision 4.0 will not tunnel, nor will it connect via modem. Product Line TAC IA Series Environment PSI / XPSI Revision 4.0 Cause Not supported in this release. Resolution Upgrade to PSI / XPSI Revision 4.1, which the file PSIv4.10.zip is available for download on The Exchange Download Center. Click here to see the Release Notes included in the zip file.

Issue When emailing reports there is no attachment. Environment Windows XP Continuum 1.7X, 1.8X. 1.90 Cause A Product defect. Resolution Contact PSS and request the Email Reports Patch. # 21527 1-978-975-9508

Issue Trying to add B3 controllers to BCX and they are not coming online. Product Line Andover Continuum Environment BCX 4040 Continuum 1.9X B3XXX  controllers Cause BacNet wiring can not be in a star configuration. There can not be more than two terminating 120 Ohm resistors. Resolution The Bus must be wired in series with end line 120 Ohm resistors. Install a B-Link if the bus path cannot be wired in series. Please see the BacNet Technical Reference manual for wiring examples.

Issue The preventDefault() JavaScript function does not work as expected when used with the Mouse Up event. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Users may attempt to override the default behavior of the Building Operation Properties Editor by using preventDefault() on the Mouse Up event. However, the editor is triggered by the Mouse Click event, not Mouse Up. Resolution To successfully prevent the default behavior and override the launch of the Properties Editor: Select the TGML Script where the interaction is defined. Use the onClick event instead of onMouseUp. Add the following line inside the onClick function: evt.preventDefault();​