Issue Is a controller reload required when upgrading from v1.74 to v1.93 or 1.94 to 2.02? Environment CyberStation v1.74,1.93 1.94 and 2.02 NetControllers, Infinet controllers Cause We will be performing an upgrade on a site from v1.74 to v1.93. or  v1.94 to 2.02 Do we need to reload every network controller? Resolution In this case it is not a requirement of the CyberStation upgrade that dictates if a controller reload will be required. However, in order to keep the CyberStation and controller versions compatible, a flash upgrade of some controllers may be required. (Refer to Continuum Software and Firmware Compatibility Matrix)  The process of doing a flash upgrade usually requires a reload and is generally a good idea. There are some cases where a minor version upgrade (for only a bug fix, for example) in a controller with a valid flash backup will not require a reload because the controller will reload itself automatically from flash. Even if you think a reload is not required make sure you edit a few objects in the controller after the flash upgrade. If you get an error that the object cannot be found, reload the controller and then do a flash backup. Additionally, a planned "outage"  is a good opportunity to reload a controller that may not have been reloaded in a while. It would be better to know right after the upgrade if there is a problem, than to find out after you leave the site. The Infinet controllers typically do not need to be reloaded - but make sure you test a few infinet controller alarms on all upgraded network level controllers.  

Issue When trying to change the value of point or change the description of a point and save and refresh, Continuum gets Save Object Error with the message of "You have attributes that have not been applied. Do you want to apply them  now?" Environment Continuum LAN Workstation Continuum SU Workstation Cause There is not enough disk space available on the SQL DB Server. Resolution Secure disk space by deleting old log data in ContinuumDB or delete unnecessary files from the SQL DB Server.

Issue Stencils not loading after installing WorkPlaceTech 5.8 Environment WorkPlace Tech 5.8 Cause The stencils are not loaded because they are now under a new path: C:/PrgramFiles/Schneider Electric/WorkPlaceTech Dispatcher. Resolution To resolve this issue perform the following step:  Open WorkPlaceTech.  Select  Application menu and click Hardware Wizard command.  Stencils should be loaded after opening the Hardware Wizard. If rebuilding the application did not load the stencils perform the following steps: Open WorkPlaceTech Select File menu click shapes Under shapes click open stencils Browse to the following path C:/ProgramFiles/Schneider Electric/WorkPlaceTech Dispatcher. Select the following stencils using the ctrl key: WPBO.vss WPCO.vss WPIOC.vss WPLMC.vss WPLPC.vss WPMN8NV.vss WPTANNO.vss WPTSC.vss WPSC.vss The stencils should now be loaded anytime you open or close WorkPlaceTech.

Issue When a controller undergoes a cold start and has a valid backup archive, it defaults to retrieving files from the archive rather than requesting updated files from the server. Product Line Satchwell BAS & Sigma Environment Sigma UNC controller Cause The controller prioritizes its local backup archive during a cold start. This behavior prevents it from fetching potentially updated files from the server, which may be necessary in certain operational or troubleshooting contexts. Resolution There are two recommended methods to ensure the controller retrieves new files from the server: Option 1: Clear the Controller’s Archive Using SDCU Launch SDCU (Sigma Device Configuration Utility). On the main screen, click the Advanced button. Select Clear Archive to remove the existing backup. Upon the next cold start, the controller will request files from the server since no local archive is available. Option 2: Use Sigma System Diagnostics to Re-trigger File Download Open Sigma System Diagnostics. Initiate a file download from the server to the controller. Re-trigger the archive time schedule to ensure the new data is added to the controller’s archive.

Issue When performing Continuum Database Initialization from a CyberStation workstation, the workstation cannot connect to the SQL Server with the following error message: "Microsoft SQL Server Login Connection failed or server not available or access denied" Product Line Andover Continuum Environment LAN workstations Single User workstations Cause Possible Invalid Server Name is being used in Continuum Database Initialization:   For Continuum LAN systems, the Server Name attribute of Continuum Continuum Database Initialization includes invalid characters.  For Continuum Single User systems, the Server Name attribute of Continuum Continuum Database Initialization does not include the \SQLExpress attribute after the Computer name.  Resolution For Continuum LAN systems, type the correct computer name of the SQL Server in the Server Name attribute field of Continuum Database Initialization screen such as "MyDBServer". Check that the required strong password is being used, such as "ABCabc123" For Continuum Single User systems, add the qualifier "\SQLExpress" at the end of the computer name in the Server Name attribute field of Continuum Database Initialization screen such as "MySUServer\SQLExpress" . Restart the SQL Server  Service and/or SQL Agent Service Check that the Windows Firewall on the Windows Server PC is turned off. Check Connection with sa Admin account on MS Management Studio and via ODBC.

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

Issue Connected to a remote site network via WorkPlace Tech and a VPN connection, but unable to see the sites BACnet devices. No I/A Series MNB-1000s, or any 3rd Party BACnet devices, are found in Workplace Tech or the Commissioning Tool. Product Line TAC I/A Series Environment MNB-1000 WorkPlace Tech (all versions) Cause The VPN does place the connecting WorkPlace Tech PC on the site network, but the BACnet/IP (MNB-1000 and 3rd Party) devices are on a different subnet then the subnet assigned to the WorkPlace Tech PC. Resolution When BACnet/IP devices are on different subnets, BBMD must be used in order for the BACnet/IP devices to communicate across IP subnets. Only one BACnet/IP device can be enabled as BBMD per subnet.   Setup the MNB-1000 as a BBMD device using the Commissioning Tool Open Device Properties of the MNB-1000 controller and select the IP tab. For Device Type select BBMD and save change. Setup WorkPlace Tech to connect to the BBMD device Select Tool from the WPT Select Configure Communication… Select BACnet and click on Change Select IP and click next Select Access a remote internetwork. For Host BBMD Address, enter the IP address of the MNB-1000 which was setup as a BBMD device. Click the Finish button to save changes. You should now be able to see and connect to the I/A Series and 3rd Party BACnet devices using WorkPlace Tech.

Issue DuraDrive actuator feedback is 0-10 VDC or 2-10 VDC, controllers accept 0-5 VDC. Environment DuraDrive actuator (MS4x / MS5x series) MNL / MNB controllers Cause The voltage feedback output was designed for controlling slave actuators configured for 0-10 VDC or 2-10 VDC control signals. Resolution Use two 10k resistors as a voltage divider across the feedback leads with the center point connected to the controller input and the actuator common connected to the controller common. NOTE: Not all actuators in this product family use the wire colors shown for the feedback output. Please refer to the actuator GI sheet for the correct colors.    MNL / MNB Controller Analog Input Configuration For actuators with a 0 VDC to 10 VDC feedback output: Type= Volts Linput = 0 Lscale = 0 Hinput = 5 Hscale = 100 This input configuration provides a 0 - 100% output corresponding to the Actuator Position, based on feedback voltage 0 VDC = 0% and 10 VDC = 100% of actuator travel.  For actuators with a 2 VDC to 10 VDC feedback output: Type= Volts Linput = 1 Lscale = 0 Hinput = 5 Hscale = 100 This input configuration provides a 0 - 100% output corresponding to the Actuator Position, based on feedback voltage 2 VDC = 0% and 10 VDC = 100% of actuator travel.

Issue Clarification on dip switch six and station addressing for the SCU1200, SCU1280, or SCU1284 Product Line TAC INET Environment I/NET Seven with Access Control using an SCU SCU1200, SCU1280, or SCU1284 Cause Clarification on SCU and dip switch settings being open, enabled for dual or single station addressing (2 or 4 doors) Resolution If the Device Type is SCU1200, SCU1280, or SCU1284: set the Number of points to either 1 or 2. Choose 1 if the SCU is configured to operate in the “single-address” mode (DIP switch S1-6 = OFF). Choose 2 if the SCU is configured to operate in the “double-address” mode (DIP switch S1-6 = ON). In order to control more than two doors, the SCU1284 must be configured to operate in the double-address mode. Though the TCON312 shows the dip switches for 1-6, there is still a bit of clarity which can be provided on how that looks on an actual SCU. The example from the TCON is shown here: And this is a photo below of an SCU which is setup as 0101 with dual addressing since Dip Switch 6 is in Dual Address mode shown in the picture below. When penetrating down to it using Edit, Host Computer, Network Configuration, SCU 1284 is shown with 2 Points with door addresses: 010108 Door1 010109 Door2 010208 Door3 010209 Door4 After checking MCU Configuration, I added the points in the Network configuration. The main point here is that Dip Switch 6 is up on the Open side of the Switch bar shown in red which is the dual point and 4 door configuration.   Note: Concerning the numbering scheme for addressing the SCU, it is important to number your SCUs with an address then skip the next number so in the event you dual addressing for four doors, the second address is available. Don't use addresses 28, 29,30, and 31 as those are reserved for the Remote Arming Terminal.  Overlooking this can result in future headaches of moving SCUs around in the addressing scheme which is never recommended. Example for a site containing 4 SCU door controllers: SCUa address 2, SCUb Address 4, SCUc Address 6, SCUd Address 8.  Another example configuration: One reader inputs to READER1 and READER2? Here is that wiring example. In order to use more than the first eight inputs on the SCU, you must configure the SCU as a double-address controller. When you enable the double-address mode (DIP switch S1-6 = ON), inputs 1 through 8 are monitored on the selected subLAN address (i.e., the primary address) and inputs 9 through 12 are monitored on the next consecutive subLAN address (i.e., the secondary address). The input points are defined in the I/NET host using two separate SCU controller assignments, the first providing eight input point definitions and the second providing 4 input point definitions. The SCU’s outputs are also divided across two LAN addresses when the SCU is operating in the double-address mode. The first four outputs are assigned to bit offsets 00 through 03 on the SCU’s primary address. The last four outputs are assigned to bit offsets 00 through 03 on the SCU’s secondary address.

Issue PE program in i28xx controller controls the VAV with TriState Triac output, and the Triac output gets damaged randomly. Environment i2 controller ( i28xx , i28xx-V ) with Triac output. Cause The output channel can get damaged / burned when Triac output value is changed to +ON from -ON ( or to -ON from +ON ) without setting the output value to OFF before the change. Resolution Check the VAV control PE program and make sure the program sets the Tri-state Triac output value to OFF before changing it to the opposite value.

Issue A license is needed for using the Roam IO2 with ethernet Product Line Andover Continuum Environment Roam IO2 Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause A license is required to use the ethernet feature with the Roam IO2 Resolution Follow the instructions for Generating a License request in the BACnet Service Tool Generating a License manual, (PDF attached). Include your contact information, PO (purchase order) and RA numbers for the RoamIO2. Send that information to Upgrades.Continuum@schneider-electric.com to process the request.

Issue The Save to Flash exclamation point (bang) shows on a Continuum BACnet controller object. Hovering over the icon, a tooltip comes up indicating that the controller 'requires flash backup'. However when performing a backup to flash, a result comes back that the 'controller doesn't need flash backup' and the exclamation icon remains. Re-loading the controller and performing a send to database have no effect. Product Line Andover Continuum Environment bCX4000 bCX4040 B3 Field Devices Cause Controller's restart mode not configured to use cool start (cool start = restoring DB from flash backup) Resolution Set controller's ACCRestartMode system variable to one of the modes below that includes cool start. The available re-start modes are (except in the b3885 and b3885-V): ACCWarmStartOnly (0) ACCCoolStartOnly (1) ACCWarmToCool (2)

Issue How can you find the Trend Log ID / GUID of trend logs in the Vista Server for use with custom reporting or querying of the SQL database? Environment Vista 5.x.x Cause The Vista database uses a Global Unique Identifier (GUID) for trend log storage in the SQL database. This Trend Log ID/GUID is stored in an property not immediately visible in the property window of the Vista Workstation environment. In Vista 5.1.7 a new database layout was introduced, database  layout version 2. The version of the layout  for the log database is possible to see from the Vista server setup. And it is possible to upgrade the database to version 2 with a tool called SQL Database Upgrade tool which is included in the Vista installation from Vista 5.1.7.    If using the new layout of the SQL database in Vista version 5.1.7 both the name of the trend log and the trendlog GUID is included in the TrendLog table. Resolution Single Trend Log Hold CTRL + SHIFT + right click and select properties of the trend log object. The Trend Log ID is one of the visible properties. Multiple Trend Logs Start a new search in Vista Workstation. Change the object types to Files\Trend Logs. Change the property to Trend Log ID. Leave the string as "*" for all trend logs. Click Search The results can be printed listing the database path, object name, and trend log id for use by the individual building the SQL reports. If using the new layout in Vista version 5.1.7 both the name of the trend log and the trendlog GUID is included in the TrendLog table.

Issue What are the correct settings for the i2 controller input reference resistors for different input types? Environment i2 Controllers Cause What are the correct settings for the i2 controller input reference resistors for different input types? Resolution See the section starting on page 71 of the i2 Controller Technical Reference. As a general rule, the reference resistor switch is ON for 10K thermistors, contact closures (including supervised) and counters; it is OFF for voltage inputs (which includes 0-20mA and 4-20mA current inputs since the use of the external resistor makes the input signal a voltage).

Issue Unable to save any program in a workstation giving error  "Unable to lock an object because it is already locked"   Environment Cyberstation Programs Cause This is usually caused by the FiringOrder attribute being locked, often due to a PC crash or other unexpected operating system shutdown. Resolution This is due to the firingorder attribute being locked, start the Continuum Command Line application, select the problem workstation from the network button. At the R> enter: firingorder editlock = false This should clear the edit lock and allow the programs to be saved. **Check to make sure that another program that accesses this program is not disabled.

Issue There are many issues that can happen at Cyberstation and methods are needed to troubleshoot. Product Line Andover Continuum Environment Cyberstation Cause There are software updates and environmental reasons for issues coming from Cyberstation and there are a number of tools to help troubleshoot. Resolution This guide covers both software and hardware troubleshooting steps for Cyberstation and webClient issues. Use these methods and tools to diagnose problems: Determine Scope Is the issue isolated (one workstation) or system-wide (multiple workstations)? Isolated issues may relate to: Installation problems Windows OS or hotfixes Hardware failures Check Continuum Compatibility Verify versions of: Continuum Service Packs Windows OS (including Service Packs) Microsoft SQL Server Internet Browser webClient Software and Firmware Compatibility Matrix Version 2.03  Review Cyberstation Error Messages Look for error messages displayed on screen. Access help: Press F1 in Cyberstation → Index → Type “Error” → Select “Error Messages” Locate Cyberstation error messages How do you locate error messages in Cyberstation?     4. Check Windows Event Viewer Look for errors or event IDs at the time of the issue. Use logs to: Search online for solutions Share with support Sharing Windows Event Logs for Troubleshooting Purposes  Verify Windows Updates Were any Service Packs or hotfixes recently applied? List all updates: Windows: How to List All of the Windows and Software Updates Applied to a Computer Check Installed Software Review recently installed programs: Windows XP: Control Panel → Add/Remove Programs Windows 10: Control Panel → Programs and Features Scan for Viruses/Malware Ensure Anti-Virus and Malware tools are updated. Run full scans to clean infected PCs. Inspect Hardware Common failure points: Memory: Use BIOS diagnostics Hard Drive: Run CheckDisk; reformat if needed NIC (Network Interface Card): Swap if faulty Graphics Card: Update drivers or replace Use Windows Device Manager Look for devices with an exclamation point. Error codes in Device Manager in Windows Gather System Information System Info (Msinfo32): Description of Microsoft System Information (Msinfo32.exe) Tool  Restore Point or Reinstall Use Windows Restore Point (XP, Vista, 7): What is System Restore? If unsuccessful: Reformat hard drive if necessary and Reinstall Cyberstation or Windows OS

Issue DCX 250, backlight is working but no text or splash screen is being displayed. Product Line Andover Continuum Environment DCX250 Cause Failure of controller hardware. Resolution Replace DCX250.

Issue The hostId for a computer running I/A Series G3 version 3.8u1 (or earlier) and N4 versions 4.2 (or earlier) may be changed from the result of a Windows update. Product Line TAC IA Series Environment I/A Series G3  I/A Series N4  Cause The hostId is automatically generated upon first install of the software and stored within the registry.  The location of the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update.The hostId is automatically generated upon first install of the software and stored within the registry.  The location of    the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. Resolution I/A Series G3 version 3.8.213 (or higher) and I/A Series N4 version 4.3.58.18 (or higher) have been modified to guard against Windows updates to prevent hostId changes.  Installations of N4 4.3 and/or G3 3.8u2 will continue to operate normally and will not assume a new hostid after a Windows update.  All previous versions of Niagara could generate a new hostid after a Windows update, requiring a license replacement.   Schneider Electric recommends updating I/A Series G3 and N4 installations to the latest released software in order to maintain the latest security protection and to gain benefit from the latest features.  These builds are:   I/A Series 3.8 Update 2 (3.8.213 and later) I/A Series 4.4 (and later)   Patch to address multiple Host IDs on a single Microsoft Windows© platform   A set of patch files have been created to stabilize the Host ID for cases where customers have not upgraded to the latest version of Niagara (see installation instructions below). Once these patches are applied to the older versions of Workbench the Host ID is stabilized and should not change if Windows updates are installed.   Note: This is a reminder that a 32-bit install will always generate a different host-id than a 64-bit install.   IMPORTANT NOTES REGARDING THE PATCHES   Patches are only supported for the latest update (maintenance) version for the relevant release. Patches are not available for I/A Series G3 release 3.5 and earlier, or I/A Series N4 release 4.0 or 4.1. Builds prior to G3 3.8.213 are considered unsupported. Customers applying these patches do so at their own risk. Newer versions of Niagara (3.8U2 and 4.3) have introduced a stabilized method of managing the Host ID and do not require any patch. The patches do not eliminate the issue of different Host IDs generated when installing 32-bit and 64-bit Niagara. Installation Instructions   The Host ID patch file is available for download on the EcoBuilding Exchange Download website.  Login to the Schneider Electric EcoBuilding Exchange Download Center and enter G3 and N4 Host ID Patches in the search area or the filename of the zip shown below.    Download the G3_N4_HOSTID_PATCHES.zip and unzip into a temporary folder. The archive contains 'nre.dll' for various versions of I/A Series G3 and Series 4.2 in a directory structure identifying them first by version and sub-directory identifying 64-bit or 32-bit Windows. The 4.2 folder also contains 'njre.dll' which will need to be copied only for 4.2 installations.  Follow these instructions:   Verify the installed java version to be either 64-bit or 32-bit. Start a Niagara Command Line (Home>/bin/console.exe) from the desktop of the platform to be patched. From the Niagara Command Line execute the command: nre -version One of the listed items will be java.vm.name. If the text contains “64-Bit” then the installation is 64-bit otherwise the installation is 32-bit. Stop any running station using Workbench's Platform Application Director on the platform to be patched. Exit Workbench if running on the platform to be patched. From the Niagara Command Line ... /bin/console.exe execute the command: plat uninstalldaemon  Prior to replacement, save a copy of the existing nre.dll located in /bin folder. If Niagara 4.2 is being updated also save a copy of the existing njre.dll located in /bin folder. Copy the version appropriate and OS appropriate (64-bit or 32-bit) downloaded version of nre.dll file to the Home>/bin folder. If Niagara 4.2 also copy njre.dll to /bin folder. Overwrite the existing file(s). From the Niagara Command Line (/bin/console.exe) execute: plat installdaemon Start Workbench.  Open a platform connection to the patched platform. Using the Application Director, start the station.  

Issue Users need to interpret the Diagnostic LED indicators on various UNC controllers and DNN modules to assess device status and troubleshoot effectively. Product Line Satchwell BAS & Sigma Environment Sigma Devices Controllers UNC X96 UNC 532 DNN3 Cause Diagnostic LEDs are designed to provide visual feedback on the operational status of the controller. Misinterpretation or lack of documentation can lead to confusion during diagnostics. Resolution Refer to the following LED behavior chart to understand the controller's current state: 

Issue XIF files for the standard MNL controllers are available on The Exchange Download Center.  Please do not use with SmartStruxure.  See XIF files for Version 1 and Version 2 of MNL controllers. Product Line TAC IA Series Environment I/A Series standard (fixed profile) controllers: MNLRF2 - Fan Coil profile MNLRH2 - Heat Pump profile MNLRR2 - Rooftop profile MNLRS1 - Satellite 1 / Rooftop profile MNLRS2 - Satellite 2 / Rooftop profile MNLRV2 - VAV profile MNLRF103 - Fan Coil profile MNLRH103 - Heat Pump profile MNLRR103 - Rooftop profile MNOTPVA3 - VAV profile MNLRF3 - Fan Coil profile MNLRH3 - Heat Pump profile MNLRR3 - Rooftop profile MNLRS3 - Satellite 3 / Rooftop profile (revised previous Satellite 1) MNLRS4 - Satellite 4 / Rooftop profile (revised previous Satellite 2) MNLRV3 - VAV profile Cause XIF files are available if needed. Resolution Download the file TAC_LLC.zip from The Exchange Download Center. Also see the accompanying Readme file.